Bug 115442

Summary:	USB iPod and Treo 650 are not recognized or mounted in beta 4
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Bryan Perry <bperry>
Component:	Other	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Beta 4
Target Milestone:	---
Hardware:	x86
OS:	SUSE Other
Whiteboard:
Found By:	System Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Output of lshal lshal without Treo plugged in lshal during sync attempt

Description Bryan Perry 2005-09-06 16:07:52 UTC

The Treo 650 is a new device, so I have not tried it on any other builds. The
iPod was successfully recognized and mounted in beta2 and 3. If I manually mount
/dev/sda2 with the iPod plugged in, everything is there and Banshee launches
automatically.

The USB jump drive secure and jump drive sport are both recognized and mounted
without problems. What info can I provide to help figure this out?

Comment 1 Danny Al-Gaaf 2005-09-06 16:14:16 UTC

- the mount problem with ipod is fixed for beta4plus/rc1
- for Treo: plugin the device and attach the output of lshal to this bug.

Comment 2 Martin Lasarsch 2005-09-06 16:23:19 UTC

*** Bug 115443 has been marked as a duplicate of this bug. ***

Comment 3 Bryan Perry 2005-09-06 16:25:45 UTC

Created attachment 48957 [details]
Output of lshal

Output of lshal with Treo 650 plugged in and turned on.

Comment 4 Bryan Perry 2005-09-06 16:27:21 UTC

(In reply to comment #1)
> - the mount problem with ipod is fixed for beta4plus/rc1
> - for Treo: plugin the device and attach the output of lshal to this bug. 

Sorry, Minor is what I meant to hit - not Major.

Comment 5 Danny Al-Gaaf 2005-09-06 16:39:21 UTC

Could you please also attach lshal output without the plugged in device? I can't 
see the device in lshal.

Comment 6 Bryan Perry 2005-09-06 16:41:22 UTC

Created attachment 48961 [details]
lshal without Treo plugged in

lshal without Treo plugged in

Comment 7 Bryan Perry 2005-09-06 16:47:16 UTC

Created attachment 48965 [details]
lshal during sync attempt

The stars were lined up enough once that I got kPilot to detect it after I had
hit the sync button. I'll try lshal while the device is trying to sync and see
if it shows up there. Maybe this will help.

Comment 8 Bryan Perry 2005-09-06 16:50:13 UTC

The device that was detected once under kPilot was /dev/ttyUSB3 if that helps.

Comment 9 Danny Al-Gaaf 2005-09-06 17:17:27 UTC

If this work with sync button all is o.k. This is the normal behavior for a pda.

Comment 10 Bryan Perry 2005-09-06 17:18:55 UTC

But it only worked once. I have not been able to get it to work again.

Comment 11 Danny Al-Gaaf 2005-09-06 17:26:13 UTC

What is the problem? If you plugin the device and press the hotsync button the 
device is found. Or not? This is the normal behavior for a pda device.

Comment 12 Bryan Perry 2005-09-06 18:12:34 UTC

I have only had the device found once. The rest of the time I get no response at
all. I have tried at least 20 times.

Comment 13 Bryan Perry 2005-09-06 18:15:30 UTC

Here's what I see in the KPilot log window:

Version: KPilot 4.5.4 (dreumes)
Version: pilot-link 0.11.8
Version: KDE 3.4.2 Level "b" 
Version: Qt 3.3.4

HotSync Log

18:15:34 Starting the KPilot daemon ...
18:15:34 Daemon status is `not running'
18:15:34 Pilot device /dev/ttyUSB3 does not exist. Probably it is a USB device
and will appear during a HotSync.

However, pressing the hotsync button does not make the device appear and sync.
It did once. Only once. I can't get it to sync again.

Comment 14 Danny Al-Gaaf 2005-09-06 18:27:35 UTC

This looks like a bug in kpilot in this case. I reassign the bug to the 
maintainer.

Comment 15 Bryan Perry 2005-09-14 17:35:32 UTC

Same results with RC3. No response when trying to sync a Treo 650 or Palm m505.

Comment 16 Will Stephenson 2006-03-28 14:42:55 UTC

Works now with downgraded pilot-link, tested with both of these models.