If Ubuntu can't run cd burner, will Debian?

danbuter · 07-19-2007, 05:45 PM

The CD Burner on my acer aspire 3680 doesn't work in Ubuntu. Nautilus, Gnomebaker, Brasero, etc., just won't run it. It can read DVD's and CD's, and they play fine. But I can't burn any CD's. I was wondering if I switched to Etch if this might fix itself, or is it something I'm just stuck with? Thanks!

phantom_cyph · 07-19-2007, 06:00 PM

You tried K3B? What are the specs of your drive? Debian may be better, I don't know as I've never had a problem...

Quakeboy02 · 07-19-2007, 06:16 PM

You might try Knoppix. If Knoppix will burn for you, it's a good sign that Debian will.

jay73 · 07-19-2007, 06:53 PM

I don't want to be a killjoy but my experience is that the more extensive hardware support comes from Ubuntu. I recently installed a sata dvdrw and Ubuntu picked it up right away while Debian didn't. Even installing Debian testing doesn't seem to help.

Anyway, if Ubuntu can read, I don't understand why it shouldn't be able to write. How is your writer listed in /dev? Optical drivese nowadays can be sr, sg or scd. The latter supports both reading and writing while the other ones cover only reading and writing respectively.

Quakeboy02 · 07-19-2007, 07:11 PM

Quote:

Originally Posted by danbuter

The CD Burner on my acer aspire 3680 doesn't work in Ubuntu. Nautilus, Gnomebaker, Brasero, etc., just won't run it. It can read DVD's and CD's, and they play fine. But I can't burn any CD's. I was wondering if I switched to Etch if this might fix itself, or is it something I'm just stuck with? Thanks!

Is it CDs that you can't burn, or DVDs? The drive in one of my machines will burn either CDs or DVD-Rs. It won't burn DVD+R. Just a thought.

danbuter · 07-19-2007, 07:13 PM

It says scd0. The various burner programs try to burn, but they say the burner is too fast. However, they do not allow me to set it to a slower speed. Nautilus and Gnomebaker did this. Brasero said the cd burned, but then it would not mount when I put it back in the drive. I did not try K3B, because I don't know how well it will cooperate with Gnome. (And yes, I REALLY prefer Gnome).

danbuter · 07-19-2007, 07:15 PM

Quote:

Originally Posted by Quakeboy02

Is it CDs that you can't burn, or DVDs? The drive in one of my machines will burn either CDs or DVD-Rs. It won't burn DVD+R. Just a thought.

The drive is a DVD player and CD/RW.

Quakeboy02 · 07-19-2007, 07:45 PM

Quote:

And yes, I REALLY prefer Gnome

Heh, me too!

Wish I had something more constructive to offer. I was hoping it was a simple DVD+R vs DVD-R issue.

rickh · 07-19-2007, 09:19 PM

I use Gnome, but I run a few KDE apps including k3b. No problems.

jay73 · 07-20-2007, 12:42 PM

Quote:

The various burner programs try to burn, but they say the burner is too fast

I'm afraid I've never heard of something like this. Care to tell us the exact type of the burner in question?

As for the scd0, that sounds fine. Maybe the optical drive needs a firmware flash? Or maybe it really is something that can't be solved that easily - I have a cdrw drive lying around that simply refuses to burn whatever I throw at it. I tried it with Linux, Solaris, Windows, various brands of disks and it still won't work.

danbuter · 07-20-2007, 09:19 PM

Quote:

Originally Posted by jay73

I'm afraid I've never heard of something like this. Care to tell us the exact type of the burner in question?

As for the scd0, that sounds fine. Maybe the optical drive needs a firmware flash? Or maybe it really is something that can't be solved that easily - I have a cdrw drive lying around that simply refuses to burn whatever I throw at it. I tried it with Linux, Solaris, Windows, various brands of disks and it still won't work.

It is a DVD C DS 24 CZP. Looking over the Hardware, it does have storage.cdrom.write_speed listed as int 0 (0x0). Not sure why, and not sure how to fix this. storage.cdrom.write_speeds has str "". storage.physical_device has string /org/freedesktop/Hal/devices/pci_8086_27c4_scsi_device_lun0_0

jay73 · 07-21-2007, 06:21 AM

Has your system been updated yet? I seem to remember that some users reported similar issues in May. Some bug apparently that prevented people from burning anything until the problem disappeared again after an update. K3b also has an option to ignore burning speed, which was reported to get things going although not at less than optimal speeds.

By the way, try launching k3b from the command line - that should allow you to see any error messages.