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.
External DVDRW trouble with kernel 2.6 -- ???Kernel bug???
I just changed over from Slackware 9.1 to Gentoo. I decided to use the modified 2.6.8 kernel. I am having trouble getting my external TDK IndiDVDRW to work, when it worked fine before in slackware using rescan-scsi-bus.
When I connect the drive using firewire, the system detects the drive as a generic scsi device and links it to sg0. However, this does me no good, as I need it to detect it as a scsi cdrom (sr0). I have scsi cdrom support compilled into the kernel. What is going wrong here???
Below is the dmesg output when the drive is connected:
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0010100345c4bd87]
ohci1394: fw-host0: SelfID received, but NodeID invalid (probably new bus reset occurred): 0000FFC0
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node resumed: ID:BUS[0-01:1023] GUID[0010100345c4bd87]
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
scsi1 : 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: TDK Model: DVDRW840G Rev: 1.03
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 5
****EDIT****
I have since gotten the drive to work, but have a problem when reconnecting the drive. Scroll down to the bottom for details.
I upgraded my kernel to 2.6.8.1, and changed sbp2, sr_mod, and sg (scsi_generic) to compile as modules (were compiled into kernel previously). Now when I load sbp2, and plug in my dvdrw I get this in my kernel messages:
Code:
ohci1394: fw-host0: SelfID received, but NodeID invalid (probably new bus reset occurred): 0000FFC0
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node resumed: ID:BUS[0-01:1023] GUID[0010100345c4bd87]
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
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: TDK Model: DVDRW840G Rev: 1.03
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 5
sr0: scsi3-mmc drive: 62x/62x writer cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
However, I still wasn't able to mount the sr0 device. The symlink just seemed to point to sg0. So I looked through the scsi devices and found a device named cd (this device wasn't here previously), that was mountable, so I was able to mount the dvdrw drive:
Code:
root# mount /dev/sr0 /mnt/dvdrw
mount: /dev/sr0 is not a block device
root# ls -l /dev/sg0 /dev/sr0
lr-xr-xr-x 1 root root 36 Aug 21 11:50 /dev/sg0 -> scsi/host0/bus0/target0/lun0/generic
lr-xr-xr-x 1 root root 8 Aug 21 06:48 /dev/sr0 -> /dev/sg0
root# mount /dev/scsi/host0/bus0/target0/lun0/cd /mnt/dvd
mount: block device /dev/scsi/host0/bus0/target0/lun0/cd is write-protected, mounting read-only
Now here is the second problem, when I unplug the dvdrw drive and plug it back in, it no longer recognizes it. If I try unloading (rmmod) either sr_mod or sbp2, rmmod just hangs.
Code:
**AFTER UNPLUGING**
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0010100345c4bd87]
***AFTER PLUGING BACK IN***
ohci1394: fw-host0: SelfID received, but NodeID invalid (probably new bus reset occurred): 0000FFC0
So any ideas on how I can get this running smoothly???
Ok, I recompilled my kernel again... realized I was using devfs, so I changed over to using udev. Booted up with my drive plugged in, recognized it fine. This time sr0 pointed to scd0, and I was able to mount the sr0 device. k3b recognized the drive as well. However it only recognizes any burning devices when run as root, which seems to be a whole other problem.
However, I am still having the same problem if I unplug the drive, and plug it back in. I get the same kernel messages as shown in the previous post, and the device register. Also, rmmod still hangs if I try to remove the sr_mod module.
Anybody??? It seems I always have to answer my own questions
I switched to 2.6.7, it does fix the k3b problem. However I still have the problem of reconnecting the drive....
I found that I am able to 'rmmod sr_mod' while the dvdrw is still plugged into the firewire port, if I do that and unplug/replug the drive it will recognize it fine again. If I don't remove the sr_mod module, the drive will not be recognized when it is plugged back in, and 'rmmod -f sr_mod' tells me the modules is busy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.