[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in supported series, please file a new bug. ** Changed in: linux (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/279342 Title: External ieee1394 drive not recognized 2.6.27-5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in supported series, please file a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/279342 Title: External ieee1394 drive not recognized 2.6.27-5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Changed in: linux Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/279342 Title: External ieee1394 drive not recognized 2.6.27-5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Changed in: linux Status: Invalid = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/279342 Title: External ieee1394 drive not recognized 2.6.27-5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Changed in: linux Status: Confirmed = Invalid -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Tags added: intrepid -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
...is still an issue in Karmic RC (2.6.31-14-generic). In /etc/modprobe.d/blacklist-firewire.conf the newer drivers are blacklisted: /etc/modprobe/blacklist-firewire.conf # Select the legacy firewire stack over the new CONFIG_FIREWIRE one. #blacklist ohci1394 #blacklist sbp2 #blacklist dv1394 #blacklist raw1394 #blacklist video1394 blacklist firewire-ohci blacklist firewire-sbp2 ...but why? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Just came across this one and YES, it still is an issue on Jaunty 9.04, patchlevel of today! Problem must be in ohci1394 module, because unloading and reloading of the module results in normal operation. Before: Sep 1 16:55:55 kirk kernel: [69443.214943] scsi7 : SBP-2 IEEE-1394 Sep 1 16:56:16 kirk kernel: [69464.216269] sbp2: probe of 00d04b00e00093b1-0 failed with error -16 After # modprobe -r ohci1394 modprobe ohci1394 Sep 1 17:00:22 kirk kernel: [69710.761627] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[e4301000-e43017ff] Max Packet=[2048] IR/IT contexts=[4/8] Sep 1 17:00:24 kirk kernel: [69712.312587] scsi9 : SBP-2 IEEE-1394 Sep 1 17:00:25 kirk kernel: [69713.316634] ieee1394: sbp2: Logged into SBP-2 device Sep 1 17:00:25 kirk kernel: [69713.316930] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] Sep 1 17:00:25 kirk kernel: [69713.323786] scsi 9:0:0:0: Direct-Access-RBC ExcelSto r Technology J36 V22O PQ: 0 ANSI: 4 Sep 1 17:00:25 kirk kernel: [69713.325673] sd 9:0:0:0: [sdb] 120103200 512-byte hardware sectors: (61.4 GB/57.2 GiB) Sep 1 17:00:25 kirk kernel: [69713.330189] sd 9:0:0:0: [sdb] Write Protect is off Sep 1 17:00:25 kirk kernel: [69713.336389] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 1 17:00:25 kirk kernel: [69713.338075] sd 9:0:0:0: [sdb] 120103200 512-byte hardware sectors: (61.4 GB/57.2 GiB) Sep 1 17:00:25 kirk kernel: [69713.341544] sd 9:0:0:0: [sdb] Write Protect is off Sep 1 17:00:25 kirk kernel: [69713.347745] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 1 17:00:25 kirk kernel: [69713.347754] sdb: sdb1 sdb2 sdb5 sdb6 Sep 1 17:00:25 kirk kernel: [69713.397015] sd 9:0:0:0: [sdb] Attached SCSI disk Sep 1 17:00:25 kirk kernel: [69713.397111] sd 9:0:0:0: Attached scsi generic sg2 type 14 Hope this pushes this issue forward -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Re comment 33: No, this issue is not in ohci1394, it's in ieee1394's nodemgr thread and sbp2's device probe. Try the following: # modprobe -r ohci1394 # modprobe firewire-ohci modprobe firewire-sbp2 Then plug the device in. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Re #34 OK, your suggestion worked as expected - I just thought about ohci1394, because your #10 comment pointed on that module... -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Since this seems to fix it, you can permanently replace ohci1394 + ieee1394 + sbp2 by the newer drivers firewire-ohci + firewire-core + firewire-sbp2. Check for relevant configuration files with grep -r -e firewire -e 1394 /etc/mod* and have a look at http://ieee1394.wiki.kernel.org/index.php/Juju_Migration#How_to_suppress_auto-loading (I don't have Ubuntu installed here hence I don't know which particular config files need to be changed.) -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Hi clarkkent435, Since you are the original bug reporter, just curious if you could confirm if this issue is resolved with the latest Jaunty 9.04 release which contains a 2.6.28 based kernel - http://www.ubuntu.com/getubuntu/download . Please let us know your results. Thanks. ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=12572 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: Triaged = Incomplete -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Changed in: linux Status: Unknown = Confirmed -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
PeterNSteinmetz, this is different from the other reporters' issues. Yours is likely bad hardware, perhaps bad firmware. The drivers can't do anything about it. It could perhaps be caused by old revisions of 1394b physical interface chips (TI TSB81BA3 erratum without software workaround). If you have a 1394a (FireWire 400) device at hand, plug this into the bus too. This forces the bus to use slower and safer 1394a arbitration instead of 1394b arbitration. (But it can still work with 800 Mb/s data rate if the FireWire 400 device is located at an end of the bus, i.e. not between the FireWire 800 devices.) -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Also, should I be registering this as a new bug on 2.6.28-4, since it has to do with the new drivers, rather than the old? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Again, thanks Stefan for the suggestions. I followed up on this and tried getting the Tandberg VXA-2 tape drive and PacketLoader tape library to mount with the new drivers. Booted off a jaunty alpha 3 live cd, which gives kernel 2.6.28-4-generic. Then, with the tape drive not plugged in, did modprobe -r ohci1394 modprobe firewire-ohci modprobe firewire-sdp2 so far, this gives the following in the kern.log: Feb 4 00:07:14 ubuntu kernel: [ 152.065612] ieee1394: Node removed: ID:BUS[0-00:1023] GUID[003093412325] Feb 4 00:07:28 ubuntu kernel: [ 166.296014] firewire_ohci: Added fw-ohci device :03:01.0, OHCI version 1.10 Feb 4 00:07:29 ubuntu kernel: [ 166.796127] firewire_core: created device fw0: GUID 003093412325, S800 I then plug in the tape drive and the following shows up: firewire_core: phy config: card 0, new root=ffc1, gap_count=5 scsi3 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.0: 0x2 (firmware_revision 0x000201, model_id 0x00) scsi4 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.1: 0x2 (firmware_revision 0x000201, model_id 0x00) firewire_core: created device fw1: GUID 0010100319003177, S800 firewire_sbp2: fw1.0: logged in to LUN (0 retries) scsi 3:0:0:0: Sequential-Access EXABYTE VXA-2a 2152 PQ: 0 ANSI: 2 scsi 3:0:0:0: Attached scsi generic sg2 type 1 firewire_sbp2: fw1.1: logged in to LUN 0001 (0 retries) firewire_sbp2: released fw1.0, target 3:0:0 firewire_sbp2: released fw1.1, target 4:0:0 st: Version 20080504, fixed bufsize 32768, s/g segs 256 Driver 'st' needs updating - please use bus_type methods osst :I: Tape driver with OnStream support version 0.99.4 osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ Driver 'osst' needs updating - please use bus_type methods firewire_core: giving up on config rom for node id ffc1 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: giving up on config rom for node id ffc0 scsi5 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.0: 0x2 (firmware_revision 0x000201, model_id 0x00) scsi6 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.1: 0x2 (firmware_revision 0x000201, model_id 0x00) firewire_core: created device fw1: GUID 0010100319003177, S800 firewire_core: phy config: card 0, new root=ffc0, gap_count=5 firewire_sbp2: released fw1.0, target 5:0:0 firewire_sbp2: released fw1.1, target 6:0:0 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: giving up on config rom for node id ffc0 Looks like it initially figured out it was a VXA-2 and created the sg device, but then it was released and something went on with the tape driver. This seems to loop forever, creating two more devices, then giving up on them, over and over again. Is there something else I need to do about the tape driver? Other ideas for testing on jaunty? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
No, it wouldn't help... the only way is to reload ohci1394 or to plug on the disk at startup. if I once reloaded the ohci1394, then I am able to plug off the cable and on again and everything works like a charm. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Oliver: I could not reproduce the problem with a brand-new LaCie Little Disk 500 GB on a few different controllers. But I found a little oddness of that disk in the process: http://marc.info/?l=linux1394-develt=12334064382 However, at least I have got an older CD-RW which shows the same symptoms as you and clarkkent435 reported if I attach it to Texas Instruments controllers (sometimes also on other controllers) so that I can work on it when I have some time to spare. (Well, from my own perspective as upstream driver maintainer, it's all fixed in the new firewire drivers.) Oliver, would it help to power the Little Disk via the USB power cable, then plug it into FireWire? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
PeterNSteinmetz wrote on 2009-01-28: 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? No, it doesn't. This particular workaround only influences behaviour of the SCSI layer which only kicks in after a successful login. (the workaround seems to be chopping the length in the request to conform to some older windows bug) More precisely, it tells the Linux SCSI core how to set the ALLOCATION LENGTH parameter in the SCSI INQUIRY command. (See the SPC spec, section Commands for all device types, INQUIRY command, if you are interested in the details.) IIRC this was of more importance a few years ago in earlier revisions of the SCSI core. Nowadays the SCSI core sets it to 36 bytes in the first attempt of INQUIRY anyway. If the 36 byte INQUIRY is successful, the SCSI core will run a retry with a larger ALLOCATION LENGTH unless the device was blacklisted (because it returns wrong results with larger lengths or crashes or whatever). The reference to Windows in sbp2.c's comment basically means that popular Windows flavors apparently issue only 36 byte INQUIRYs, hence firmware authors don't easily notice if they made a mistake in their INQUIRY handler. So, the SBP2_WORKAROUND_INQUIRY_36 merely influences behaviour _after_ successful login and _after_ successful first INQUIRY SCSI transaction. Furthermore, an ALLOCATION LENGTH bigger than 36 bytes, if it is supported by the device, returns information that is mostly uninteresting for FireWire devices, except for marginally interesting claims of conformance to SCSI specifications in addition to the conformance claims made in the first 8 bytes of the INQUIRY response. And if this is true, is there a way to turn off the workaround? So, you don't need to turn the hard-wired workaround off; yet you can do so easily: # echo 0x100 /sys/module/sbp2/parameters/workarounds This, like any other echo command into sbp2's workaround parameter file, becomes effective at the next time a device is plugged in. # modinfo sbp2 has a brief overview of available workarounds flags. Note that usage of the workarounds module parameter is only meant as a measure of last resort, hence we don't provide actual documentation of it besides the sbp2.c source. Or perhaps modify this module to identify the devices for which the workaround is really needed? This is impossible because we don't know which Initio firmwares are affected and whether they have any identifiers that differ from unaffected variants. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
I wrote: This particular workaround only influences behaviour of the SCSI layer which only kicks in after a successful login. This is actually true for all currently available sbp2 workarounds. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Firstly, thanks for the extensive explanation Stefan. I tried setting the 0x100 option for sbp2, and you are correct, no other workarounds are now enabled, but that doesn't fix this. I also tried a modified kernel module, where there is a distinction between the first and second time out messages. This is the first message. I also tried increasing the timeout value to 40s, this also didn't help. In reviewing all of the dmesg logs however, I noticed there is an early complaintm after the host is added, there a large number of complaints that ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... Eventually this stops repeating. And then there is the complaint ieee1394: Error parsing configrom for node 0-00:1023 (where this node id is for the tape drive in question) Do these two items indicate that something else is actually going on here? I would certainly appreciate any other suggestions on what I could try to get this tape drive working under ubuntu. It is reported to work under FreeBSD, so perhaps I'll try that next. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
PeterNSteinmetz wrote on 2009-01-31: there a large number of complaints that ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... Eventually this stops repeating. Could be flaky hardware or an issue between driver and firmware. Try unloading the 1394 drivers, then modprobe ieee1394 disable_irm=1 modprobe ohci1394. And then there is the complaint ieee1394: Error parsing configrom for node 0-00:1023 These errors can be temporary (then they are harmless) or terminal (which would be bad). In your case its just temporary, otherwise the sbp2 driver would never be attached to the device. I would certainly appreciate any other suggestions on what I could try to get this tape drive working under ubuntu. It is reported to work under FreeBSD, so perhaps I'll try that next. Like everybody else who reported here at this bug, you should try the new alternative firewire drivers as mentioned in comment 21. These new drivers are meant to replace the classic ones eventually, when the new drivers became feature-complete and fully stable. (firewire- core replaces ieee1394, raw1394, video1394. firewire-ohci replaces ohci1394. firewire-sbp2 replaces sbp2.) The new drivers are smaller, more correct, more secure, and better performing than the old ones. The one CD-RW of mine which behaves like described in this bug when attached to Texas Instruments controllers (and sometimes also on other controllers) works perfectly with the new drivers. As I wrote in comment 21, you get these new drivers if you install a Jaunty test kernel package; see bug 276463. But since you already modified your kernel, you could also configure the new drivers in into your current kernel. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
I don't know yet when I be able to do something about this. Until then you could try the following if you want: Install the latest Jaunty kernel package (2.6.28 based). Boot that kernel. Then, # modprobe -r ohci1394 # modprobe firewire-ohci # modprobe firewire-sbp2 Then plug in the drive and hopefully enjoy smooth operation. -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Registered as upstream bug at http://bugzilla.kernel.org/show_bug.cgi?id=12572 -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
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=2product=62ref=166) The dmesg looks like: - [ 78.748200] ieee1394: sbp2: Workarounds for node 0-00:1023: 0x2 (firmware_revision 0x000201, vendor_id 0x001010, model_id 0x00) - [ 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
I have/had the same problem with my Lacie disk, but I was able to manually mount the disk after the following steps: # modprobe -r sbp2 # modprobe sbp2 # dmesg | tail -33 [ 5133.273353] ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... [ 5134.224157] ieee1394: Error parsing configrom for node 0-00:1023 [ 5134.224564] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0a0007e42002fee6] [ 5135.768775] ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d04b8a19091491] [ 5135.777460] scsi6 : SBP-2 IEEE-1394 [ 5156.781206] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 5156.787133] sbp2: probe of 00d04b8a19091491-1 failed with error -16 [ 5156.787365] scsi7 : SBP-2 IEEE-1394 [ 5177.788056] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 5177.792624] sbp2: probe of 00d04b8a19091491-1 failed with error -16 [ 5178.068553] ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... [ 5178.347593] scsi8 : SBP-2 IEEE-1394 [ 5199.353088] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 5199.357478] sbp2: probe of 00d04b8a19091491-1 failed with error -16 [ 6092.986845] scsi9 : SBP-2 IEEE-1394 [ 6114.004171] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 6114.006059] sbp2: probe of 00d04b8a19091491-1 failed with error -16 # modprobe -r ohci1394 (wait a few seconds) # modprobe ohci1394 # dmesg | tail -33 [ 6200.401162] ieee1394: Node removed: ID:BUS[0-01:1023] GUID[0a0007e42002fee6] [ 6200.406680] ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00d04b8a19091491] [ 6210.547841] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[e4301000-e43017ff] Max Packet=[2048] IR/IT contexts=[4/8] [ 6211.828193] ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d04b8a19091491] [ 6211.833650] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0a0007e42002fee6] [ 6211.843279] scsi10 : SBP-2 IEEE-1394 [ 6213.103374] ieee1394: sbp2: Logged into SBP-2 device [ 6213.104776] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] [ 6213.110287] scsi 10:0:1:0: Direct-Access LaCielittle Disk PQ: 0 ANSI: 4 [ 6213.116325] sd 10:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB) [ 6213.120356] sd 10:0:1:0: [sdb] Write Protect is off [ 6213.120368] sd 10:0:1:0: [sdb] Mode Sense: 10 00 00 00 [ 6213.123004] sd 10:0:1:0: [sdb] Cache data unavailable [ 6213.123014] sd 10:0:1:0: [sdb] Assuming drive cache: write through [ 6213.128087] sd 10:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB) [ 6213.131269] sd 10:0:1:0: [sdb] Write Protect is off [ 6213.131282] sd 10:0:1:0: [sdb] Mode Sense: 10 00 00 00 [ 6213.142059] sd 10:0:1:0: [sdb] Cache data unavailable [ 6213.142072] sd 10:0:1:0: [sdb] Assuming drive cache: write through [ 6213.142649] sdb: sdb1 [ 6213.169596] sd 10:0:1:0: [sdb] Attached SCSI disk [ 6213.170110] sd 10:0:1:0: Attached scsi generic sg2 type 0 I have a thinkpad R60 running intrepid 64bit: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 21) 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 15:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller 15:00.1 FireWire (IEEE
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
I have/had the same problem with my Lacie disk, but I was able to manually mount the disk after the following steps: # modprobe -r sbp2 # modprobe sbp2 # dmesg | tail -33 [ 5133.273353] ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... [ 5134.224157] ieee1394: Error parsing configrom for node 0-00:1023 [ 5134.224564] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0a0007e42002fee6] [ 5135.768775] ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d04b8a19091491] [ 5135.777460] scsi6 : SBP-2 IEEE-1394 [ 5156.781206] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 5156.787133] sbp2: probe of 00d04b8a19091491-1 failed with error -16 [ 5156.787365] scsi7 : SBP-2 IEEE-1394 [ 5177.788056] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 5177.792624] sbp2: probe of 00d04b8a19091491-1 failed with error -16 [ 5178.068553] ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... [ 5178.347593] scsi8 : SBP-2 IEEE-1394 [ 5199.353088] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 5199.357478] sbp2: probe of 00d04b8a19091491-1 failed with error -16 [ 6092.986845] scsi9 : SBP-2 IEEE-1394 [ 6114.004171] ieee1394: sbp2: Error logging into SBP-2 device - timed out [ 6114.006059] sbp2: probe of 00d04b8a19091491-1 failed with error -16 # modprobe -r ohci1394 (wait a few seconds) # modprobe ohci1394 # dmesg | tail -33 [ 6200.401162] ieee1394: Node removed: ID:BUS[0-01:1023] GUID[0a0007e42002fee6] [ 6200.406680] ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00d04b8a19091491] [ 6210.547841] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[e4301000-e43017ff] Max Packet=[2048] IR/IT contexts=[4/8] [ 6211.828193] ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d04b8a19091491] [ 6211.833650] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0a0007e42002fee6] [ 6211.843279] scsi10 : SBP-2 IEEE-1394 [ 6213.103374] ieee1394: sbp2: Logged into SBP-2 device [ 6213.104776] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] [ 6213.110287] scsi 10:0:1:0: Direct-Access LaCielittle Disk PQ: 0 ANSI: 4 [ 6213.116325] sd 10:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB) [ 6213.120356] sd 10:0:1:0: [sdb] Write Protect is off [ 6213.120368] sd 10:0:1:0: [sdb] Mode Sense: 10 00 00 00 [ 6213.123004] sd 10:0:1:0: [sdb] Cache data unavailable [ 6213.123014] sd 10:0:1:0: [sdb] Assuming drive cache: write through [ 6213.128087] sd 10:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB) [ 6213.131269] sd 10:0:1:0: [sdb] Write Protect is off [ 6213.131282] sd 10:0:1:0: [sdb] Mode Sense: 10 00 00 00 [ 6213.142059] sd 10:0:1:0: [sdb] Cache data unavailable [ 6213.142072] sd 10:0:1:0: [sdb] Assuming drive cache: write through [ 6213.142649] sdb: sdb1 [ 6213.169596] sd 10:0:1:0: [sdb] Attached SCSI disk [ 6213.170110] sd 10:0:1:0: Attached scsi generic sg2 type 0 I have a thinkpad R60 running intrepid 64bit: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 21) 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 15:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller 15:00.1 FireWire (IEEE
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
diefans, is this the LaCie Little Disk, USB 2.0 + FireWire 400, with shortcut button? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
it's this one: http://www.lacie.com/products/product.htm?pid=10978 -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
do I need to mount it manually? It can't be mounted because the sbp2 driver fails to establish the connection with the device. You could only mount it if sbp2 successfully logged in and the kernel's scsi and partition subsystems logged some in dmesg drive info (model ID, capacity, cache type, whether partitions were found). But the kernel never gets as far at the moment. Alas (1.) I have no idea yet what change in the kernel could have caused that regression, (2.) I'm afraid there is no further workaround that could be tried short of modifying the kernel. External firewire HD (WD 5000 - 1 TB) ... Model number is WD5000D032 Hmm, several web pages which I found for this model number list 500 GB drives, which makes some sense. Well, I guess they change specs faster than product numbers... -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
This bug was reported in the Intrepid development cycle; removing regression-potential and marking as regression-release. ** Tags added: regression-release ** Tags removed: regression-potential -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
The log looks strikingly similar to another report about of an Ubuntu 8.10 regressions with a Sony CD-RW: http://bugzilla.kernel.org/show_bug.cgi?id=12213 The modprobe -r ohci1394 + modprobe ohci1394 routine did help with that device though, sometimes at least. As I am not a Ubuntu user, can someone point me to the kernel .configs of 8.10 and 8.04? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Still no joy: [EMAIL PROTECTED]:~$ cat /sys/module/ohci1394/parameters/phys_dma 1 [EMAIL PROTECTED]:~$ modprobe -r sbp2 FATAL: Error removing sbp2 (/lib/modules/2.6.27-7-generic/kernel/drivers/ieee1394/sbp2.ko): Operation not permitted [EMAIL PROTECTED]:~$ sudo modprobe -r sbp2 [sudo] password for kevin: [EMAIL PROTECTED]:~$ sudo modprobe sbp2 [EMAIL PROTECTED]:~$ dmesg | tail -33 [89211.484502] [drm] Allocating FIFO number 0 [89211.487807] [drm] nouveau_fifo_alloc: initialised FIFO 0 [89211.45] [drm] Allocating FIFO number 1 [89211.491986] [drm] nouveau_fifo_alloc: initialised FIFO 1 [89249.397194] wlan0: authenticate with AP 00:0c:41:cb:39:69 [89249.402720] wlan0: authenticated [89249.402733] wlan0: associate with AP 00:0c:41:cb:39:69 [89249.405473] wlan0: RX ReassocResp from 00:0c:41:cb:39:69 (capab=0x411 status=0 aid=1) [89249.405484] wlan0: associated [89312.695429] type=1503 audit(1225161367.804:16): operation=inode_permission requested_mask=r:: denied_mask=r:: fsuid=7 name=/proc/29095/net/ pid=29095 profile=/usr/sbin/cupsd [89313.763396] type=1503 audit(1225161368.872:17): operation=inode_permission requested_mask=r:: denied_mask=r:: fsuid=7 name=/proc/29106/net/ pid=29106 profile=/usr/sbin/cupsd [89313.767677] type=1503 audit(1225161368.876:18): operation=socket_create family=ax25 sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.771102] type=1503 audit(1225161368.880:19): operation=socket_create family=netrom sock_type=seqpacket protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.774670] type=1503 audit(1225161368.884:20): operation=socket_create family=rose sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.778060] type=1503 audit(1225161368.888:21): operation=socket_create family=ipx sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.781422] type=1503 audit(1225161368.892:22): operation=socket_create family=appletalk sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.785150] type=1503 audit(1225161368.896:23): operation=socket_create family=econet sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.788631] type=1503 audit(1225161368.896:24): operation=socket_create family=ash sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [92790.164839] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. [174249.212460] ieee1394: Node added: ID:BUS[0-00:1023] GUID[0090a991e0014032] [174249.212583] ieee1394: Node changed: 0-00:1023 - 0-01:1023 [174249.219850] scsi5 : SBP-2 IEEE-1394 [174270.220040] ieee1394: sbp2: Error logging into SBP-2 device - timed out [174270.220310] sbp2: probe of 0090a991e0014032-1 failed with error -16 [174270.220510] scsi6 : SBP-2 IEEE-1394 [174291.225023] ieee1394: sbp2: Error logging into SBP-2 device - timed out [174291.227611] sbp2: probe of 0090a991e0014032-1 failed with error -16 [174291.499125] scsi7 : SBP-2 IEEE-1394 [174312.501023] ieee1394: sbp2: Error logging into SBP-2 device - timed out [174312.504597] sbp2: probe of 0090a991e0014032-1 failed with error -16 [174502.519632] scsi8 : SBP-2 IEEE-1394 [174523.520029] ieee1394: sbp2: Error logging into SBP-2 device - timed out [174523.521863] sbp2: probe of 0090a991e0014032-1 failed with error -16 [EMAIL PROTECTED]:~$ sudo modprobe -r ohci1394 [EMAIL PROTECTED]:~$ sudo modprobe ohci1394 [EMAIL PROTECTED]:~$ dmesg | tail -33 [89249.405473] wlan0: RX ReassocResp from 00:0c:41:cb:39:69 (capab=0x411 status=0 aid=1) [89249.405484] wlan0: associated [89312.695429] type=1503 audit(1225161367.804:16): operation=inode_permission requested_mask=r:: denied_mask=r:: fsuid=7 name=/proc/29095/net/ pid=29095 profile=/usr/sbin/cupsd [89313.763396] type=1503 audit(1225161368.872:17): operation=inode_permission requested_mask=r:: denied_mask=r:: fsuid=7 name=/proc/29106/net/ pid=29106 profile=/usr/sbin/cupsd [89313.767677] type=1503 audit(1225161368.876:18): operation=socket_create family=ax25 sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.771102] type=1503 audit(1225161368.880:19): operation=socket_create family=netrom sock_type=seqpacket protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.774670] type=1503 audit(1225161368.884:20): operation=socket_create family=rose sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.778060] type=1503 audit(1225161368.888:21): operation=socket_create family=ipx sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.781422] type=1503 audit(1225161368.892:22): operation=socket_create family=appletalk sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.785150] type=1503 audit(1225161368.896:23): operation=socket_create family=econet sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [89313.788631] type=1503 audit(1225161368.896:24): operation=socket_create family=ash sock_type=dgram protocol=0 pid=29106 profile=/usr/sbin/cupsd [92790.164839] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
The dmesg shows that this problem is very likely in the sbp2 + ieee1394 + ohci1394 kernel driver stack and possibly an upstream problem. Alas a quick look at the IEEE 1394 kernel subsystem changelog after 2.6.24 (which I presume was the major version number of the reporter's last known working kernel) does not show anything obvious that could lead to the login failure. clarkkent435, please check the following (can be done as normal user): # cat /sys/module/ohci1394/parameters/phys_dma The output should be 1. If it is 0, then the module configuration of Ubuntu would be to blame. Also try the following commands as root while the disk is connected and powered up: # modprobe -r sbp2 # modprobe sbp2 # dmesg | tail -33 If this still results in the same failure, try # modprobe -r ohci1394 (wait a few seconds) # modprobe ohci1394 # dmesg | tail -33 Furthermore, there seem to exist different versions of the WD 5000 series. Do you know the exact model number, or can you point to a detailed product specification? Is it FireWire 400 or 800; is it combined with eSATA? Do you happen to know whether the built-in mechanism is IDE or SATA? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Changed in: linux (Ubuntu) Assignee: Chris Coulson (chrisccoulson) = Ubuntu Kernel Team (ubuntu-kernel-team) Status: Incomplete = Triaged ** Description changed: External firewire HD (WD 5000 - 1 TB) not recognized in 2.6.27-5. I believe it was automagically mounted in all previous kernels - has worked fine since Gutsy, through Hardy, and Intrepid alphas 1-4. I noticed it disappear for the first time yesterday after my daily update. Not sure what was updated that would have affected it. It used to be here, and would also autopopulate the desktop: [EMAIL PROTECTED]:/media$ ls cdrom cdrom0 [EMAIL PROTECTED]:~$ lsb_release -rd Description: Ubuntu intrepid (development branch) Release: 8.10 [EMAIL PROTECTED]:~$ uname -r 2.6.27-5-generic [EMAIL PROTECTED]:~$ apt-cache policy linux linux: Installed: (none) Candidate: 2.6.27.5.5 Version table: 2.6.27.5.5 0 500 http://us.archive.ubuntu.com intrepid/restricted Packages Power is on and lit up; have tried cycling several times. Works fine using USB interface: [EMAIL PROTECTED]:~$ lsusb Bus 002 Device 009: ID 1058:0903 Western Digital Technologies, Inc. Bus 002 Device 005: ID 046d:09c1 Logitech, Inc. QuickCam Deluxe for Notebooks Bus 002 Device 004: ID 15a9:0004 Bus 002 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - [EMAIL PROTECTED]:~$ + [EMAIL PROTECTED]:~$ + + dmesg output when connecting the drive: + + [ 3784.246885] ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[0090a991e0014032] + [ 3784.248917] ieee1394: Node changed: 0-00:1023 - 0-01:1023 + [ 3784.250718] scsi9 : SBP-2 IEEE-1394 + [ 3805.253024] ieee1394: sbp2: Error logging into SBP-2 device - timed out + [ 3805.256129] sbp2: probe of 0090a991e0014032-1 failed with error -16 -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Sure: [EMAIL PROTECTED]:~$ sudo fdisk -l [sudo] password for kevin: Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x4a60f2a4 Device Boot Start End Blocks Id System /dev/sda1 * 1 29693 238508991 83 Linux /dev/sda2 29694 30401 56870105 Extended /dev/sda5 29694 30401 5686978+ 82 Linux swap / Solaris connect Firewire [EMAIL PROTECTED]:~$ sudo fdisk -l Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x4a60f2a4 Device Boot Start End Blocks Id System /dev/sda1 * 1 29693 238508991 83 Linux /dev/sda2 29694 30401 56870105 Extended /dev/sda5 29694 30401 5686978+ 82 Linux swap / Solaris [EMAIL PROTECTED]:~$ disconnect Firewire; connect USB [EMAIL PROTECTED]:~$ sudo fdisk -l Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x4a60f2a4 Device Boot Start End Blocks Id System /dev/sda1 * 1 29693 238508991 83 Linux /dev/sda2 29694 30401 56870105 Extended /dev/sda5 29694 30401 5686978+ 82 Linux swap / Solaris Disk /dev/sdf: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xffdcf9ec Device Boot Start End Blocks Id System /dev/sdf1 1 60801 4883840017 HPFS/NTFS [EMAIL PROTECTED]:~$ -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
Thanks. Could you please post the output of 'sudo fdisk -l', both before and after you connect the drive? -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
tail -f /var/log/kern.log change after reconnecting device: Oct 8 22:32:15 kevin-desktop kernel: [ 4029.582607] ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[0090a991e0014032] Oct 8 22:32:15 kevin-desktop kernel: [ 4029.584524] ieee1394: Node changed: 0-00:1023 - 0-01:1023 Oct 8 22:32:15 kevin-desktop kernel: [ 4029.586253] scsi10 : SBP-2 IEEE-1394 Other requested files attached. ** Attachment added: dmesg.log http://launchpadlibrarian.net/18357955/dmesg.log -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/18357959/lspci-vvnn.log -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Attachment added: lsusb.log http://launchpadlibrarian.net/18357976/lsusb.log -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Attachment added: proc_version_signature.log http://launchpadlibrarian.net/18357985/proc_version_signature.log -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Attachment added: uname-a.log http://launchpadlibrarian.net/18357988/uname-a.log -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
In addition to the information requested above, it would also be useful to open a terminal and run the following the drive disconnected: tail -f /var/log/kern.log Then re-attach the drive and post any messages that appear in the terminal. Thanks -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
hank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments. ** Changed in: linux (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Chris Coulson (chrisccoulson) Status: New = Incomplete -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Tags added: regression-potential -- 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
[Bug 279342] Re: External ieee1394 drive not recognized 2.6.27-5
** Description changed: External firewire HD (WD 5000 - 1 TB) not recognized in 2.6.27-5. I believe it was automagically mounted in all previous kernels - has worked fine since Gutsy, through Hardy, and Intrepid alphas 1-4. I noticed it disappear for the first time yesterday after my daily update. Not sure what was updated that would have affected it. It used to be here, and would also autopopulate the desktop: [EMAIL PROTECTED]:/media$ ls cdrom cdrom0 [EMAIL PROTECTED]:~$ lsb_release -rd Description: Ubuntu intrepid (development branch) Release: 8.10 [EMAIL PROTECTED]:~$ uname -r 2.6.27-5-generic [EMAIL PROTECTED]:~$ apt-cache policy linux linux: Installed: (none) Candidate: 2.6.27.5.5 Version table: 2.6.27.5.5 0 500 http://us.archive.ubuntu.com intrepid/restricted Packages - Power is on and lit up; have tried cycling several times. + Power is on and lit up; have tried cycling several times. Works fine using USB interface: + + [EMAIL PROTECTED]:~$ lsusb + Bus 002 Device 009: ID 1058:0903 Western Digital Technologies, Inc. + Bus 002 Device 005: ID 046d:09c1 Logitech, Inc. QuickCam Deluxe for Notebooks + Bus 002 Device 004: ID 15a9:0004 + Bus 002 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader + Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + [EMAIL PROTECTED]:~$ -- 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
