Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The only thing that held me back from upgrading permanently to kernel 2.6 is the way my external firewire disc and my ipod behave. They both work perfectly under 2.4. The first that gets plugged in is /dev/sda and the second /dev/sdb.
With 2.6.8, when I turn the disc on, I get 8 devices (sda to sdh) and when I plug in the ipod I get 8 more (starting from sdi).
I can mount both discs, though.
Is this strange or is this normal?
Thats the dmesg part after plugging the first disc in:
Code:
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050770e00071002]
ieee1394: unsolicited response packet received - no tlabel match
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: p1 p2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdb: 398297088 512-byte hdwr sectors (203928 MB)
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050770e00071002]
ieee1394: unsolicited response packet received - no tlabel match
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: p1 p2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdb: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdb: drive cache: write through
/dev/scsi/host0/bus0/target1/lun0: p1 p2
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdc: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdc: drive cache: write through
/dev/scsi/host0/bus0/target2/lun0: p1 p2
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
Attached scsi generic sg2 at scsi0, channel 0, id 2, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdd: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdd: drive cache: write through
/dev/scsi/host0/bus0/target3/lun0: p1 p2
Attached scsi disk sdd at scsi0, channel 0, id 3, lun 0
Attached scsi generic sg3 at scsi0, channel 0, id 3, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sde: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sde: drive cache: write through
/dev/scsi/host0/bus0/target4/lun0: p1 p2
Attached scsi disk sde at scsi0, channel 0, id 4, lun 0
Attached scsi generic sg4 at scsi0, channel 0, id 4, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdf: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdf: drive cache: write through
/dev/scsi/host0/bus0/target5/lun0: p1 p2
Attached scsi disk sdf at scsi0, channel 0, id 5, lun 0
Attached scsi generic sg5 at scsi0, channel 0, id 5, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdg: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdg: drive cache: write through
/dev/scsi/host0/bus0/target6/lun0: p1 p2
Attached scsi disk sdg at scsi0, channel 0, id 6, lun 0
Attached scsi generic sg6 at scsi0, channel 0, id 6, lun 0, type 0
Vendor: Maxtor 6 Model: B200P0 Rev:
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sdh: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdh: drive cache: write through
/dev/scsi/host0/bus0/target7/lun0: p1 p2
Attached scsi disk sdh at scsi0, channel 0, id 7, lun 0
Attached scsi generic sg7 at scsi0, channel 0, id 7, lun 0, type 0
Well, something is definitely not normal, because the ieee1394 / sbp2 system crashes with kernel 2.6.8 when I have a lot of processes doing something with the disc (i.e. having many copy dialogs by draging around some folders to or off the disc).
I wonder if this could have something to do with the udev thing, which I dont really understand.
Maybe I have a mix of udev and the old kernel 2.4-like device system?
with the 2.6.11.7 kernel it works allright, except for
Code:
ieee1394: Error parsing configrom for node 0-01:1023
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050770e00071002]
ieee1394: unsolicited response packet received - no tlabel match
The strange behavior with the multiple devices must have had something to do with a buggy firewire kernel module in 2.6.8.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.