CD write error:
Brand new dvd-writer LG-DVDRAM GH22NS50
But it does not burn: Quote:
|
First, check the small print. Does the drive *do* dvd-r?
dvd+r and dvd-r are 2 different formats structurally different. There could be separate drives for them but usually not. There _are_ separate dvds for them. There are also a whole host of clever options to allow you to get over nearly everything. on dvd-r -dummy is a dry run option. |
Quote:
DVD-RAM works excellent. What are the names of the drivers/modules cdrecord wants to use? Maybe I don't compiled them in the kernel or they aren't loaded. But it also seams that cdrecord wants to controll the writing the same way this dvd-recorder wants controll the writing , too. Maybe this recorder has a version of cdrecord in its embedded controller ?? Can I set cdrecord to only set the recorder into write mode and sent then the/a datastream to it via DMA with no care of what the recorder does, except errors of course? |
My 2 cents.
For a DVD you may try Code:
growisofs -dvd-compat -speed=8 -use-the-force-luke=tty -Z /dev/sr0=/path/to/img.iso Code:
wodim speed=8 -tao dev=/dev/sr0 /path/to/img.iso Code:
cdrecord dev=6,0,0 speed=4 /path/to/img.iso From the man page Code:
-overburn Code:
burnfree |
So
being incorrigible - not much sympathy. Writing dvd+r @1x: usually the medium. control - the software actually has control but that doesn't mean the drive likes it. It's a funny relationship. They are both trying to preserve unecessary dud disks. |
Quote:
I only want to burn a simple CD !!! Two years ago it worked all fine with k3b. I thought it is the drive and bought this one (with DVD+-R DL support, both from LG -Super Multi writer) - NO The mediums are from intenso the same when it did yet work. Now I think I have to study how the writing of CDs work to get behind whats going wrong or do you have any other hints? |
Have you tried DVDRTools
It's a fork from cdrecord with a standard make system and all the extra code junked, along with hysterical warnings on running linux: "This is dvdrtools, not dvdlibc" |
Yes, with dvdrtools v0.3.1 its the same error.
And I now used different mediums - always the same error. |
I am beginning to think it's the drive.
A non standard drive can get away in windows with an m$ windows driver. Seagate did this in times past - disk drivers, and you couldn't get dma on linux. Mandrake (Now mandriva) had a 'disk drake' and it had a list of dodgy drives at the time. They couldn't get dma out of seagate drives (Back in the 90s) Presume things are better now. There are a lot of weird little options in cdrecord. If you don't want to replace the drive, read the cdrecord man page - in installments if necessary. Make sure /dev/pg0 & /dev/sg0 point to the cd drive (symlinks to /dev/whatever). Run it with -vv and see what it says. Try anything that sounds like a good idea. He does give you an accurate commentary on the drive "seems reasonable"means it's normal |
Yes, but not the way that it is broken, but more that it is used wrong by the (system) tools.
So the write error could be no write error but maybe a DMA request or so ? My dvd-recorder is SATA (/dev/sr0) Content of file /sys/block/sr0/device is: Quote:
And reading works also with all media. So the drive must be O.K.. Maybe I compiled something in the kernel that does interacts with the writing process? ??? |
dma error - I don't know.
I have slowish boxes and dma is 50-65mb/s on hard drive. If you don't have that, compile in the correct chipset driver into the kernel and get generic out - in case it nabs the chip first. access on cd/dvd devices is usually an awful lot slower, under 10 mb/s. write is slower again. You can read, you can write, just you want it to write faster, am I correct? BTW I can write faster, but I don't - because I have had access to a tester (Used in cdrom manufacturing). 2 clear rules came accross. 1. the faster you read a cdrom, the more mistakes are made 2. the faster you write a cdr, the more mistakes are made. |
Quote:
And yes, +R writing is too slow and also breaks with this error, but DMA continues writing, so DVD+R gets written with less than 1x speed. O.K I'll check my kernel. |
I can not find something wrong.
|
Have you experimented with cdrecord's -raw*, mmc_*, & forcespeed options?
It might be interesting to do an cdrecord <drive> -inq >file and post that. |
Yes, all the same.
Quote:
Quote:
And if cdrecord can talk with my CD drive, like it can obviously (s.a.), it should work ??? Could there be a PAM problem? Maybe I shouldn't use PAM with cdrecord? |
May be this can help:
cdrecord dev=6,0,0 -prcap > Quote:
|
Quote:
dev=6,0,0 is also weird. How many drives have you got? I'm normally 1,0,0 Translating from Schilling-speak, that's bus 6. Is there six scsi buses and does your cd only show on the 6th? Have you /dev/pg0 & pg1) and /dev/sg0 & sg1? If not, make symlinks every time you reboot |
dev=6,0,0 is /dev/sr0
Have a look on my cdrecord -scanbus: Quote:
Quote:
If you can give me major minor I could crate them Quote:
Make symlinks from sg to pg ? |
Quote:
|
Its a SATA burner, right?
I've never got any problems quite like what you are getting bastl, but I have had odd issues with SATA CD/DVD drives being used in 'IDE mode' (or 'legacy mode'). You could try changing to SATA mode, and see if that helps. Warning! If you have win2k/winXP installed an havent gone though the whole 'adding SATA drivers during the install process' changing the HDD/CD/DVD drives from 'IDE' to 'SATA' will make windows fail to boot. As long as you dont try to boot windows, and change the mode back before you do boot windows, everything should be fine. Linux should have no problems booting from IDE mode, SATA mode, or changing modes between boots. |
As for sg0 & pg0, symlinks are fine, in fact unnecessary. I don't have pg* but do have sg0 & sg1 and never had a problem. It does make the cd more visible to cdrecord, as you will see if you add symlinks. It's more Schilling-speak, and my comments on that should be moderated on any decent mailing list :-).
|
Quote:
What do you mean with changing to SATA mode ? Quote:
Just one moment I'll dry it ... - sg0 is a char device and sr0 (my burner) is a block device ?? ... - mknod --mode=660 sg0 c 11 0 Damn, No: Quote:
|
Quote:
You might already be using native SATA mode, its just something that is worth checking, and trying SATA mode if you arent using it now. |
I can set it to 'SATA -> AHCI', 'RAID', 'native IDE' or 'legacy IDE' mode.
But the error stays the same. It is the same error with my old P-ATA burner, the cause I bought this new one. It suddenly did break with this error. |
At this stage you should get one of your mates to try it and see how it goes. Just divide & conquer. Too many posts here, and you're getting nowhere.
|
Quote:
business_kid is right, testing the burner(s) in a different machine is easier than trying to work though all the possible software problems. You could also try loading a liveCD and burning a CD/DVD from the live CD (given 2 CD/DVD drives). Or making a USB flash drive linux distro install and doing a test burn from there. |
O.K. I'll try.
I also think it is a software problem. I must have changed something and don't know what. |
All times are GMT -5. The time now is 11:33 AM. |