I would like to add an additional device that seems to be having a very similar same problem, under a variety of kernel versions. (I am happy to move this to a new thread if people think that is better).
This is the Tandberg Data StorageLoader VXA-2 1U with firewire interface. (http://www.tandbergdata.com/us/en/products/search- result/?action=2&product=62&ref=166) The dmesg looks like: - [ 78.748200] ieee1394: sbp2: Workarounds for node 0-00:1023: 0x2 (firmware_revision 0x000201, vendor_id 0x001010, model_id 0x000000) - [ 99.737945] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 99.738104] sbp2: probe of 0010100319003177-1 failed with error -16 I am able to access the drive and tape library under MacOS X using the manufacturer provided tools and am able to upgrade the firmware, etc. The message above is under ubuntu hardy heron server (8.04 i386) kernel 2.6.24-19-server. It persists after unloading and loading the ohci1394 module or the sdp2 module. This message is also produced when booting off the LiveCD versions for either Ubuntu Intrepid Ibex or the Jaunty alpha 3 release. The controller chip on the host (a SuperMicro server) is a Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01). It appears that this tape/library is using an Initio Firewire-PATA controller bridge. Three are given on their site http://www.initio.com/Html/Products.asp. Given the age of the product, I might suspect the inic-1430. I understand this chip has had issues in the past under Linux kernels, and I see in the dmesg that a workaround is being used. The comments in the source (sdp2.c) for this workaround note, however, that this may have been only necessary for their older products, and the lookup is using a wildcard for the model_id. So is it possible, with the latest firmware upgrades, that this workaround itself is causing the timeout on login? (the workaround seems to be chopping the length in the request to conform to some older windows bug) And if this is true, is there a way to turn off the workaround? Or perhaps modify this module to identify the devices for which the workaround is really needed? -- External ieee1394 drive not recognized 2.6.27-5 https://bugs.launchpad.net/bugs/279342 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
