DVD Drive & Burner App Issues

Question

Hey guys, I've searched the forums for several days on this but can't see to find the fix.
I've been running Arch for about 2.5 years, upgrading daily, and all was going well, but yesterday I decided to do a fresh Arch install.  The new install went fine and I'm using it now, but I'm having some troubles with my DVD drive and any CD/DVD burner apps that I try to use.  Those same apps worked perfectly in my old install.
K3b now launches very slowly on the first start but it does detect both, my dvdr, and cdrw drives.  However, on a K3b restart during the same Linux session, it only sees the cdrw drive.  If I reboot and restart K3b, the process is repeated.
Graveman just hangs on trying to detect my drives on the first start, and it has to be killed manually.  It never gets past detecting the first drive.
cdrecord gives this:
$ cdrecord -scanbus
scsibus1:
1,0,0 100) 'PLEXTOR ' 'DVDR PX-740A ' '1.01' Removable CD-ROM
1,1,0 101) 'PLEXTOR ' 'CD-R PREMIUM ' '1.06' Removable CD-ROM
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
fstab looks like this:
$ cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/dvd /mnt/dvd udf,iso9660 ro,user,noauto,unhide 0 0
/dev/cdrom1 /mnt/cdrom udf,iso9660 ro,user,noauto,unhide 0 0
/dev/sdb1 /mnt/flash vfat user,noauto,noatime 0 0
/dev/fd0 /mnt/fd0 vfat user,noauto 0 0
/dev/sda6 / ext3 defaults 0 1
/dev/sda7 swap swap defaults 0 0
/dev/sda8 /home ext3 defaults 0 1
I didn't have any modules in rc.conf before the new install and all worked well, so I didn't put any there this time either.  I've tried reinstalling K3b, Graveman, and the kernel, but none of that helped.
It seems to me that this all has something to do with the new drive naming scheme, but I'm not sure.
Anyone have any clues on a fix for this one?
Thanks in advance.
oz

Answer 1

Hi, T-Dawg 
Yep, graveman still hangs, so it might not really be K3b's fault, but a possible kernel problem instead.  However, the current kernel works fine with the previous version of KDE.  In the bug report mentioned above, someone claimed this issue will be fixed with the 2.6.22 kernel, so I guess we'll know soon enough.
Command line burns work perfectly so I'll keep using that and skip on hard coding the device to sr0 for now.  Might do that if the new kernel doesn't work, though.
Thanks for your help.
oz
Edit:  I've tried k3b 1.0.3-1 that just came out earlier today, but it has the same problem.  Gotta go all the way back to version 1.0.1 to get things working again.
Last edited by ozar (2007-07-23 16:18:16)