DVD+RW in Slackware 10.1

gargamel · 05-14-2005, 05:43 PM

Hi,

first of all, forgive me, I know there are quite a few threads already on DVD usage on Slackware, but none of them seems to match my problem. Which is:

I'd like to burn (data) DVD+RWs with k3b, but can't.

Slackware 10.1 with Kernel 2.6.10 from /testing does not detect my DVD+RW drive. Now, I know is preconfigured to work with just one CD-ROM drive, while everything else has to be configured by hand. But I seem to be missing something as I can't get it working, so far.

Here's my /etc/fstab:
/dev/hdd /mnt/dvdrw auto noauto,user 0 0

Maybe this should be
/dev/hdd /mnt/dvdrw iso9660,udf noauto,user 0 0
or
/dev/hdd /mnt/dvdrw iso9660,ufs noauto,user 0 0

And then there are probably one or two changes in /etc/udev/... necessary. But I don't know, what to put where... and why!

Another point is permissions. I'd like to use k3b, although I know the power of CLI... ;-). In k3b there is an option to "use" a group named burning. I guess I should change the group for /dev/hdd from cdrom to burning, right?

I also think that I have a fundamental problem of understanding here. How do the settings for udev and /etc/fstab influence each other?

Finally, I think the configuration details mentioned above are relevant only after the device itself has been detected. But the setup wizard of k3b tells me that there is no /dev/hdd to be found. My secondary system on the very same machine, SuSE 9.3 Professional, on the other hand has no problems detecting that drive. So it's not a hardware problem. Why is it not "seen" by Slack? No trace of /dev/hdd in /var/log/messages.

Thanks for anyone providing a usefule hint or two that enables me to resolve Gordon's node... ;-)

gargamel

Bruce Hill · 05-14-2005, 06:37 PM

I'm running Slackware 10.1 and have a Pioneer DVD+-RW drive.
This is how I set it up in /etc/fstab:

Code:

/dev/hdb         /mnt/dvd         iso9660     noauto,user,ro   0   0

For the 2.6.x kernels you must use the physical device. K3B detected
it and the permissions are fine.

I've not written any udev rules yet, so I can't help there. What
is the output of "dmesg | grep -i dvd" ? If you don't find it there,
then it's not detected. You must have support for the drive in
your kernel. I would think Patrick's 2.6.10 would have modules
for your drive. I compile my own kernels, and have had no probs
with this drive or a Sony I had before it.

Did the default 2.4.29 kernel detect your drive? And have you
run "/opt/kde/bin/k3bsetup" as root to get your drive setup for
K3B yet?

P.S. If you think it might be a kernel issue, and don't want to
build your own, Patrick has testing/packages/linux-2.6.11.9/
in Slackware -current now...released Friday.

gargamel · 05-15-2005, 03:04 AM

Thanks chinaman. In fact I looked in the wrong place for my device. dmesg shows my LiteOn as /dev/hdd, quite right.

k3bsetup, however, does not "see" it. It's k3b 0.11.19. Could this be because I haven't installed any DVD writing progs? k3bsetup lists cdrdao 1.1.9 and cdrecord 2.1 only.

Which DVD writing tool do you use? Some recommend growisofs, others prefer something else (like a DVD enabled version of cdrecord). As I said I'd like to use k3b as the frontend, so I'd prefer a tool that can be used with it.

Looking at your /etc/fstab I see that you mount your burner ro (read-only). Really?

Regarding the kernel modules: I have no idea what modules I would possible need, or where to configure what, in this case. /etc/modules.conf seems to be no longer relevant with kernel 2.6.x, so I checked these:

/etc/rc.d/rc.modules
/lib/modules/2.6.10/modules.dep
/lib/modules/2.6.10/alias

DVD is not even mentioned there.

Thanks again.

gargamel

reddazz · 05-15-2005, 05:39 AM

There is a much newer version of k3b available, try upgrading to that and see if it solves your problem.

gargamel · 05-15-2005, 06:06 AM

No, unfortunately not. Same as before with k3b 0.11.23 from Slackware-current.

Probably not surprising, as k3b is mainly a frontend for other tools that I haven't upgraded beyond what's in Slackware-10.1/slackware/patches.

gargamel

Bruce Hill · 05-15-2005, 06:10 AM

Quote:

Originally posted by gargamel
Thanks chinaman. In fact I looked in the wrong place for my device. dmesg shows my LiteOn as /dev/hdd, quite right.

k3bsetup, however, does not "see" it. It's k3b 0.11.19. Could this be because I haven't installed any DVD writing progs? k3bsetup lists cdrdao 1.1.9 and cdrecord 2.1 only.

I believe K3B needs dvd+rw-tools as a backend. Got it? Issue

Code:

mingdao@james:~$ find /var/log/packages -iname "*dvd*" -exec ls -l {} \;
-rw-r--r--  1 root root 875 2005-03-31 02:03 /var/log/packages/dvd+rw-tools-5.21.4.10.8-i486-1
mingdao@james:~$

Quote:

Which DVD writing tool do you use? Some recommend growisofs, others prefer something else (like a DVD enabled version of cdrecord). As I said I'd like to use k3b as the frontend, so I'd prefer a tool that can be used with it.

If you want to use K3B only, then get that package. I've only used growisofs to burn DVD isos
from command line, but it's more efficient than K3B. I burned a 3.1GB Slackware-10.1 DVD.iso >
-rw-r--r-- 1 mingdao users 3.1G 2005-05-10 09:36 slackware-10.1-DVD.iso
in less than 15 minutes...ymmv

For the mount point, this is mine which shows you group and permissions:

Code:

mingdao@james:~$ ls -alh /dev/hdb
brw-rw----  1 root cdrom 3, 64 2005-05-10 08:32 /dev/hdb

Quote:

Looking at your /etc/fstab I see that you mount your burner ro (read-only). Really?

You can't mount it rw, and when you burn to it, you don't mount it, so ro is fine.

Quote:

Regarding the kernel modules: I have no idea what modules I would possible need, or where to configure what, in this case. /etc/modules.conf seems to be no longer relevant with kernel 2.6.x, so I checked these:

/etc/rc.d/rc.modules
/lib/modules/2.6.10/modules.dep
/lib/modules/2.6.10/alias

It's not a module. This is what I've got:

Code:

# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=y  <-- gotta have this 
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y  <-- my IDE chipset ... which one is yours?
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

Quote:

DVD is not even mentioned there.

Yes, apparently they're all just ATAPI devices...IDECD works. Do include the proper
chipset for your motherboard.

Quote:

Thanks again.

gargamel

My pleasure. Hope it works. If I left something out, post back until we get it working.

Nobber · 05-15-2005, 06:31 AM

The only time k3b ever failed to detect my DVD writer it turned out to be a permissions problem.

Make sure your normal user is a member of the "cdrom" and "disk" groups, then re-run k3bsetup. (The entries in /etc/fstab are not relevant to k3b finding optical drives.)

gargamel · 05-15-2005, 06:44 AM

Thanks.

Ok, checked that I have dvd+rw, and I do.

But I don't have /dev/hdd... 8-(
This is weird, as dmesg shows me this:

hdd: LITE-ON DVDRW LDW-851S, ATAPI CD/DVD-ROM drive

This is confusing to me, as I thought that udev would create such nodes on demand.

Now, I thought it would be simple enough to create a new device node /dev/hdd with the same features as /dev/hdc, which is my DVD-ROM reading device. But:

I don't know the right options for mknod. The man page for mknod pointed me to a device list /usr/src/linux/Documentation/devices.txt. But there all there is for DVD is this:

97 block Packet writing for CD/DVD devices
0 = /dev/pktcdvd0 First packet-writing module
1 = /dev/pktcdvd1 Second packet-writing module
...

and

204 = /dev/video/em8300 EM8300 DVD decoder control
205 = /dev/video/em8300_mv EM8300 DVD decoder video
206 = /dev/video/em8300_ma EM8300 DVD decoder audio
207 = /dev/video/em8300_sp EM8300 DVD decoder subpicture
208 = /dev/compaq/cpqphpc Compaq PCI Hot Plug Controller

Looking for hdd I find this:

22 block Second IDE hard disk/CD-ROM interface
0 = /dev/hdc Master: whole disk (or CD-ROM)
64 = /dev/hdd Slave: whole disk (or CD-ROM)

Which seems to be ok, for me, but I am willing to learn, if I am wrong, here.

So what would you advise me to do?

BTW, I'll save your hint on the performance advantage of growisofs for later... ;-)
For now, k3b would be what I'd like to go with, as GUI tools are better for occasional use. Should the need rise to burn DVDs more often, I'll certain reconsider the CLI.

Thanks again,

gargamel

gargamel · 05-15-2005, 06:47 AM

Quote:

Originally posted by Nobber
The only time k3b ever failed to detect my DVD writer it turned out to be a permissions problem.

Make sure your normal user is a member of the "cdrom" and "disk" groups, then re-run k3bsetup. (The entries in /etc/fstab are not relevant to k3b finding optical drives.)

Hmmm, my user is a member of cdrom. Why should I be a user of disk, too?
And: The setup wizard of k3b runs as root, so it should be able to detect a drive independent of any non-privileged users, I think. Am I missing something?

gargamel

Nobber · 05-15-2005, 07:02 AM

Quote:

Originally posted by gargamel
Hmmm, my user is a member of cdrom. Why should I be a user of disk, too?

Under kernel 2.4, the burner is usually /dev/scd* - belonging to the cdrom group. Under kernel 2.6, the burner is usually /dev/hd** - belonging to the disk group. When I moved from kernel 2.4 to kernel 2.6, this fact turned out to be important!

Quote:

And: The setup wizard of k3b runs as root, so it should be able to detect a drive independent of any non-privileged users, I think. Am I missing something?

That's true; I suggested re-running the setup wizard so it could configure things properly assuming your normal user could now "see" the drive. It might not be necessary, but it won't do any harm.

Nobber · 05-15-2005, 07:14 AM

Quote:

Originally posted by gargamel
But I don't have /dev/hdd... 8-(

Weird. The mknod command to create it would be:

mknod /dev/hdd b 22 64

gargamel · 05-15-2005, 07:44 AM

Thanks, Nobber, for both your replies.
I created a device node /dev/hdd with

# mknod /dev/hdd b 22 64

but k3b wouldn't see it, again. Not sure about all the runlevel things, what happens when and so on, I thought, maybe hardware detection is something that's done early. So I first went back to runlevel 1, and then to 3 again. But after startx k3b was still unable to find the device. Something even more radical was needed, so I did to my Slackware system what actually only Windows systems deserve: I rebooted! ;-)

Unfortunately it didn't help, probably because Linux isn't Windows...

In fact, after the reboot the device node /dev/hdd was gone, again. So it's probably something in the udev configuration. I just don't know, yet, what.

gargamel

Nobber · 05-15-2005, 08:02 AM

I would try turning off udev and using a static /dev instead. Then you can be sure that /dev/hdd will exist, and k3b might have a better chance of detecting your drive.

gargamel · 05-15-2005, 11:39 AM

Well, I'd actually prefer udev remaining turned on but creating the device. That's what udev is for, and it must be possible to configure it that way. I just don't know enough about it.

gargamel

gargamel · 05-15-2005, 03:50 PM

Solved!

The problem was a line in /etc/lilo.conf: append="hdd=ide-scsi"
This was left from my kernel 2.4.29 configuration that I used before upgrading to 2.6.10.
It seems that this prevented udev from creating the needed device node.

Thanks everyone! All your hints were very useful to track this down.

gargamel