I hate to bring it up after the mega thread on LKML, but I have some problems with CD burning.
First of all what is the Fedora Core political correct program to burn CD/DVD under gnome ? I have been using k3b, but that's an evil KDE program ;-)
Than when I try to re-burn an full CD-RW it gets automatically mounted, but the desktop context menu only has a "eject" entry, which is of no use, I need and "unmount" entry.
Of course I wouldn't need that unmount entry when k3b would unmount the drive when I use the "unmount" menu entry that k3b offers, but that doesn't seem to do a thing. So i have to unmount by hand in a terminal window.
Than the real trouble starts, I get interrupt lost messages, on a drive that used to work before. I already tried the acpi=noirq option without success. When trying the erase the disk, and burn and pretty much everything else that access the drive, i get the following errors;
Feb 5 01:25:49 xpc kernel: ide-cd: cmd 0x3 timed out Feb 5 01:25:49 xpc kernel: hda: lost interrupt Feb 5 01:25:49 xpc kernel: hda: request sense failure: status=0x51 { DriveReady SeekComplete Error } Feb 5 01:25:49 xpc kernel: hda: request sense failure: error=0x40 { LastFailedSense=0x04 } Feb 5 01:26:49 xpc kernel: hda: lost interrupt Feb 5 01:27:51 xpc kernel: hda: lost interrupt Feb 5 01:28:53 xpc kernel: hda: lost interrupt Feb 5 01:29:55 xpc kernel: hda: lost interrupt Feb 5 01:30:57 xpc kernel: hda: lost interrupt
The bad thing, is after this happens the machine pretty much has to be rebooted cause every program that now tries to access /dev/hda (for example a yum update kernel) hangs for ever in D-state.
So is this one of the "bad luck, you bought wrong hardware again" cases ? I have seen reports like this that go back many years, and the keep coming bad, which sounds to me that there is no real solution.
- Erwin
PS: This is all with today's rawhide.
Erwin Rol wrote:
I hate to bring it up after the mega thread on LKML, but I have some problems with CD burning.
I saw bits of it ...
First of all what is the Fedora Core political correct program to burn CD/DVD under gnome ? I have been using k3b, but that's an evil KDE program ;-)
Well for burning .ISOs I right click and let nautilus do it for creating a "quick" CD with a few files on it, again nautilus CD/DVD creator is ok, just drag them in then click thw write button, but for "important" stuff where I want to verify after write and have more control over it, I use k3b, I think gnome-baker is eventually meant to allow us to stop using k3b :-)
Than the real trouble starts, I get interrupt lost messages, on a drive that used to work before. I already tried the acpi=noirq option without success. When trying the erase the disk, and burn and pretty much everything else that access the drive, i get the following errors;
only "hard" error I get from k3b is when trying to burn a DVD+RDL, but I'm now fairly convinved it is an issue with my drive/firmware :-(
On Sunday 05 February 2006 05:03, Andy Burns wrote:
Erwin Rol wrote:
First of all what is the Fedora Core political correct program to burn CD/DVD under gnome ? I have been using k3b, but that's an evil KDE program ;-)
Well for burning .ISOs I right click and let nautilus do it for creating a "quick" CD with a few files on it, again nautilus CD/DVD creator is ok, just drag them in then click thw write button, but for "important" stuff where I want to verify after write and have more control over it, I use k3b, I think gnome-baker is eventually meant to allow us to stop using k3b :-)
xcdroast is another EvilKDEFree(tm) program for you CD writer.
On Sun, 2006-02-05 at 07:43 +0200, bogdan.mustiata@gmail.com wrote:
On Sunday 05 February 2006 05:03, Andy Burns wrote:
Erwin Rol wrote:
First of all what is the Fedora Core political correct program to burn CD/DVD under gnome ? I have been using k3b, but that's an evil KDE program ;-)
Well for burning .ISOs I right click and let nautilus do it for creating a "quick" CD with a few files on it, again nautilus CD/DVD creator is ok, just drag them in then click thw write button, but for "important" stuff where I want to verify after write and have more control over it, I use k3b, I think gnome-baker is eventually meant to allow us to stop using k3b :-)
xcdroast is another EvilKDEFree(tm) program for you CD writer.
Why is GnomeBaker not installed by default in the Gnome install?
k3b gets installed be default if you do a KDE install.
Michael
On Sun, 2006-02-05 at 18:59 +1300, Michael J Knox wrote:
Why is GnomeBaker not installed by default in the Gnome install?
k3b gets installed be default if you do a KDE install.
Michael
GnomeBaker is currently being reviewed for Extras.[1] Once that is done, we will be able to submit an RFE for it to be added as part of Core (hopefully).
[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170973
On Sat, 2006-02-04 at 22:59 -0800, Peter Gordon wrote:
On Sun, 2006-02-05 at 18:59 +1300, Michael J Knox wrote:
Why is GnomeBaker not installed by default in the Gnome install?
k3b gets installed be default if you do a KDE install.
Michael
GnomeBaker is currently being reviewed for Extras.[1] Once that is done, we will be able to submit an RFE for it to be added as part of Core (hopefully).
[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170973
Yes, I am well aware of it being in the review process, I guess I worded my question poorly.
The point was meant to be more, why no Gnome CD app when there is a KDE app?
There is no balance.
Michael
søn, 05 02 2006 kl. 21:42 +1300, skrev Michael J Knox:
On Sat, 2006-02-04 at 22:59 -0800, Peter Gordon wrote:
On Sun, 2006-02-05 at 18:59 +1300, Michael J Knox wrote:
Why is GnomeBaker not installed by default in the Gnome install?
k3b gets installed be default if you do a KDE install.
Michael
GnomeBaker is currently being reviewed for Extras.[1] Once that is done, we will be able to submit an RFE for it to be added as part of Core (hopefully).
[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170973
Yes, I am well aware of it being in the review process, I guess I worded my question poorly.
The point was meant to be more, why no Gnome CD app when there is a KDE app?
Because audio burning is integrated in rhythmbox and data burning is in nautilus (via nautilus-cd-burner), the same with CD copying.
- David
Peter Gordon wrote:
GnomeBaker is currently being reviewed for Extras.
OK, I noticed that GnomeBaker was accepted into Extras, so I installed it today, it erased and wrote a .iso to CD-RW for me OK, not tested anything else with it, I'd say it's a nice start, but it isn't going to deplose k3b for me just yet ...
On Sun, 2006-02-05 at 03:03 +0000, Andy Burns wrote:
Well for burning .ISOs I right click and let nautilus do it for creating a "quick" CD with a few files on it, again nautilus CD/DVD creator is ok, just drag them in then click thw write button, but for "important" stuff where I want to verify after write and have more control over it, I use k3b, I think gnome-baker is eventually meant to allow us to stop using k3b :-)
I tried to do the same, but every time I burned ISOs from nautilus, the result was corrupted (I only tried to burn the FC{34} ISOs, and then I checked them with anaconda's built-in tester). Of course, burning them with k3b (same box, same images, CDs from same batch) resulted in working CDs...
Did anyone encounter the same behavior?
On Sun, Feb 05, 2006 at 02:21:09AM -0500, Dimi Paun wrote:
I tried to do the same, but every time I burned ISOs from nautilus, the result was corrupted (I only tried to burn the FC{34} ISOs, and then I checked them with anaconda's built-in tester). Of course, burning them with k3b (same box, same images, CDs from same batch) resulted in working CDs...
Did anyone encounter the same behavior?
I don't know if this is the same problem, but... last month I used Nautilus on my new FC4 laptop to burn a CD with a few pictures on them. I quickly checked the contents of the disc after burning it and it seemed fine. Days later, my brother tells me that the last few pictures had problems. He could see their names in the directory, but neither a PC nor a Mac could read the actual files. Of course I had tested only a random sample of the first pictures.
That was the only CD I needed to burn in the past couple of years (I use the network otherwise), so I didn't think twice about it and blamed it on the media. A CD-R is so cheap these days that I just can't convince myself to trust it. Now I am having second thoughts; maybe it was nautilus (or the kernel) that messed up the final 4-5 MB of data. Ignoring the ISO checksum, can you actually compare the contents of the CD and its loop-mounted ISO image? You could use diff -qr to find out which files are to blame. cmp can tell you the offsets inside the files where the differences lie.
On Sun, 2006-02-05 at 08:39 +0100, Rudi Chiarito wrote:
On Sun, Feb 05, 2006 at 02:21:09AM -0500, Dimi Paun wrote:
I tried to do the same, but every time I burned ISOs from nautilus, the result was corrupted (I only tried to burn the FC{34} ISOs, and then I checked them with anaconda's built-in tester). Of course, burning them with k3b (same box, same images, CDs from same batch) resulted in working CDs...
Did anyone encounter the same behavior?
I don't know if this is the same problem, but... last month I used Nautilus on my new FC4 laptop to burn a CD with a few pictures on them. I quickly checked the contents of the disc after burning it and it seemed fine. Days later, my brother tells me that the last few pictures had problems. He could see their names in the directory, but neither a PC nor a Mac could read the actual files. Of course I had tested only a random sample of the first pictures.
That was the only CD I needed to burn in the past couple of years (I use the network otherwise), so I didn't think twice about it and blamed it on the media. A CD-R is so cheap these days that I just can't convince myself to trust it. Now I am having second thoughts; maybe it was nautilus (or the kernel) that messed up the final 4-5 MB of data. Ignoring the ISO checksum, can you actually compare the contents of the CD and its loop-mounted ISO image? You could use diff -qr to find out which files are to blame. cmp can tell you the offsets inside the files where the differences lie.
I've had similar problems. In my case, FC4 thinks my SATA DVD/CD burner is a ATA devices (sees it as hdc, not sdc) and when you burn too fast the drive can't keep up and does this.
I've bugzilla'd this, but it's really and issue of the kernel not detecting my hardware properly and it's being resolved slowly.
R.
On Sun, 2006-02-05 at 22:43 +1100, Rodd Clarkson wrote:
I've had similar problems. In my case, FC4 thinks my SATA DVD/CD burner is a ATA devices (sees it as hdc, not sdc) and when you burn too fast the drive can't keep up and does this.
But does it work properly from k3b, but not from nautilus? This is what is really confusing in my case...
On Sun, 2006-02-05 at 02:43 +0100, Erwin Rol wrote:
Feb 5 01:25:49 xpc kernel: ide-cd: cmd 0x3 timed out Feb 5 01:25:49 xpc kernel: hda: lost interrupt Feb 5 01:25:49 xpc kernel: hda: request sense failure: status=0x51 { DriveReady SeekComplete Error } Feb 5 01:25:49 xpc kernel: hda: request sense failure: error=0x40 { LastFailedSense=0x04 } Feb 5 01:26:49 xpc kernel: hda: lost interrupt Feb 5 01:27:51 xpc kernel: hda: lost interrupt
I found these bugs one kernel.org;
http://bugzilla.kernel.org/show_bug.cgi?id=5786 http://bugzilla.kernel.org/show_bug.cgi?id=4514
Those seem to be the same problems i have, and it is the same chipset, and in one case even the same Shuttle ST20G5 PC.
The fedora bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178121 looks a bit like it to, but it doesn't talk about a specific chipset. The two kernel.org bugs are about the Ali M15x3 Chipset.
Should i file a new bug ?
- Erwin
-
Andy Burns -
bogdan.mustiata＠gmail.com -
David Nielsen -
Dimi Paun -
Erwin Rol -
Michael J. Knox -
Peter Gordon -
Rodd Clarkson -
Rudi Chiarito