SBP2 does not work with Apple iPod in versions later than 2.4.19
I have recently upgraded from 2.4.19 to 2.4.22, and have discovered that the SBP2 module no longer functions correctly with the Apple iPod (which should behave like a standard firewire disk drive). In the 2.4.19 kernel, it works perfectly, every time, however, it does not anymore. I have also tried every version after 2.4.19, and the same problem exists.
It detects the device fine, and it "logs into" it, and on the screen of the iPod, it has the "do not disconnect' sign, meaning that it did that step successfully, but its impossible to mount. In the old kernel version, I would use mount /dev/sda2 , and it would mount the volume just fine, but now, mount claims that sda2 is not a valid block device.
Here is the output from dmesg after I insmod sbp2. Note how there is no information regarding SCSI device assignment and the like:
ieee1394: Node added: ID:BUS[0-01:1023] GUID[000a2700020c8630]
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
sbp2: $Rev: 1010 $ Ben Collins <[email protected]>
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
I am sure that I compiled in SCSI support, and SCSI disk/CDROM/tape/generic support into the kernel. I have also compiled in support for ieee1394. No matter what, it does not work correctly. Am I missing something? Or perhaps this new SBP2 module requires me to pass something to it in order to enable the SCSI emulation or something?
Quoted 6 lines · [email protected] (Sraphim) writes:
I have recently upgraded from 2.4.19 to 2.4.22, and have discovered that the SBP2 module no longer functions correctly with the Apple iPod (which should behave like a standard firewire disk drive). In the 2.4.19 kernel, it works perfectly, every time, however, it does not anymore. I have also tried every version after 2.4.19, and the same problem exists.
[...]
Google rescan-scsi-bus.sh
Recent versions of SBP2 don't add the scsi devices automagically meaning you have to run this tool to manually add them.
Signature · 4 lines
Mathieu Chouquet-Stringer E-Mail : [email protected] Never attribute to malice that which can be adequately explained by stupidity. -- Hanlon's Razor --
Quoted 10 lines
ieee1394: Node added: ID:BUS[0-01:1023] GUID[000a2700020c8630]
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
sbp2: $Rev: 1010 $ Ben Collins <[email protected]>
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Quoted 5 lines
I am sure that I compiled in SCSI support, and SCSI disk/CDROM/tape/generic support into the kernel. I have also compiled in support for ieee1394. No matter what, it does not work correctly. Am I missing something? Or perhaps this new SBP2 module requires me to pass something to it in order to enable the SCSI emulation or something?
People really should start making a habit of reading documentation when upgrading things, especially when they know they have a problem. If you read the SBP2 section on linux1394.org, you'll see where it says that later versions of 2.4 need the rescan-scsi-bus.sh script. It also explains why, and links to the script.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/