Bugzilla – Bug 11197
80GB iPod Video (5.5G) does not recognize when unmounted
Last modified: 2019-01-25 10:35:27 UTC
fab4 at r4447 correctly mounts my FAT32 formatted iPod 5.5G running Rockbox 3.1, but the iPod continues to show the message warning me not to disconnect even after I issue a 'umount' command on the fab4 and verify (via 'df -h') that the iPod is no longer mounted. My iPod behaves as expected with my Ubuntu 8.04 LTS laptop (kernel 2.6.24) -- after umounting the iPod on my laptop, it shows the "OK to disconnect" screen. So this looks like a fab4/SqueezeOS problem.
Same problem when Apple's firmware is used for mounting my iPod -- my Apple firmware level is 1.2.1. fab4 mounts the iPod but after manually unmounting and verifying with 'df' that it's not longer mounted, the iPod still shows "Do not disconnect."
Peter: any idea why that would be?
more on the firmware: the Apple UI says it's software version 1.2.1 but here's what my laptop dmesg reports in both Apple and Rockbox modes: scsi 8:0:0:0: Direct-Access Apple iPod 1.62 PQ: 0 ANSI: 0
Dean, no ideas over here. I do not recall seeing this behavior in earlier versions of Ubuntu, nor in Windows XP.
I'm guessing this is a problem in the usb driver, we may need to ask Freescale to comment.
FWIW, still seeing this behavior at r5007. Please let me know if there's anything I can do to help troubleshoot this. Here's what dmesg shows at r5007 when I plug the iPod in my SBT: usb 1-1: new high speed USB device using fsl-ehci and address 5 usb 1-1: device not accepting address 5, error -71 usb 1-1: new high speed USB device using fsl-ehci and address 7 usb 1-1: configuration #1 chosen from 2 choices scsi1 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 7 usb-storage: waiting for device to settle before scanning scsi 1:0:0:0: Direct-Access Apple iPod 1.62 PQ: 0 ANSI: 0 sd 1:0:0:0: [sda] 39075372 2048-byte hardware sectors (80026 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 68 00 00 08 sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] 39075372 2048-byte hardware sectors (80026 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 68 00 00 08 sd 1:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sda2 sd 1:0:0:0: [sda] Attached SCSI removable disk usb-storage: device scan complete UBIFS error (pid 1129): ubifs_get_sb: cannot open "/dev/sda", error -22 UBIFS error (pid 1151): ubifs_get_sb: cannot open "/dev/sda1", error -22 Here's dmesg from my amd64 Ubuntu 8.04 system, which umounts cleanly: [ 179.697642] usb 8-3: new high speed USB device using ehci_hcd and address 2 [ 180.952428] usb 8-3: device not accepting address 2, error -71 [ 181.934069] usb 8-3: new high speed USB device using ehci_hcd and address 4 [ 182.038265] usb 8-3: configuration #1 chosen from 2 choices [ 182.076259] usbcore: registered new interface driver libusual [ 182.083995] Initializing USB Mass Storage driver... [ 182.085097] scsi6 : SCSI emulation for USB Mass Storage devices [ 182.085708] usbcore: registered new interface driver usb-storage [ 182.085711] USB Mass Storage support registered. [ 182.085791] usb-storage: device found at 4 [ 182.085793] usb-storage: waiting for device to settle before scanning [ 186.117060] usb-storage: device scan complete [ 186.117640] scsi 6:0:0:0: Direct-Access Apple iPod 1.62 PQ: 0 ANSI: 0 [ 186.122340] sd 6:0:0:0: [sdb] 39075372 2048-byte hardware sectors (80026 MB) [ 186.123304] sd 6:0:0:0: [sdb] Write Protect is off [ 186.123307] sd 6:0:0:0: [sdb] Mode Sense: 68 00 00 08 [ 186.123308] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 186.125319] sd 6:0:0:0: [sdb] 39075372 2048-byte hardware sectors (80026 MB) [ 186.126320] sd 6:0:0:0: [sdb] Write Protect is off [ 186.126328] sd 6:0:0:0: [sdb] Mode Sense: 68 00 00 08 [ 186.126329] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 186.126331] sdb: sdb1 sdb2 [ 186.165780] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 186.165816] sd 6:0:0:0: Attached scsi generic sg2 type 0
I recently received the newer fab4 hardware, and unfortunately the bug is still present at firmware 7.4-r6026.