Comment 16 for bug 119258

I will try out the test later tonight. It does seem that the same device is
trying to be controlled by multiple methods, however. I can say that I've been
able to burn successfully (without rebooting) by using growisofs directly, and
that ejecting the "empty media icon" that appears on the gnome desktop (even
though I told it do nothing automatically) and reinserting the DVD has caused no
lock-ups, either. It seems to happen only when using GUIs... which makes me
wonder if part of the problem is the control that Gnome is exercising over the
device.

I have noticed, at the very least, that I have what looks like four (or five)
different device names in /dev for the same device: /dev/dvd, /dev/cdrom0,
/dev/cdrom, and /dev/sr0 (what Gnomebaker uses to burn an ISO image to DVD),
(and possibly /dev/cdrw -- I noticed that one exists, but haven't seen anything
try to use it. ... Then again, I haven't been burning CDRWs, either.)

Also thinking about booting into fluxbox and see if using K3b poses problems
that way.

Gareth Fitzworthington wrote:
> Can anybody still experiencing this problem test the following possible solution?
> http://linux-ata.org/faq.html#combined
> The slow down as a result of the PATA/SATA combination may be causing at least some of the above mentioned problems.
> This will probably only affect those with Intel chipsets.
>
> Another possible cause maybe an optical drive firmware bug. People may
> want to check to see if they have the latest firmware for their optical
> drive.
>
> I don't think this is a k3b bug but will wait to hear back from people
> before re-assigning.
>