You are not logged in.

#1 2009-06-05 17:10:24

markp1989
Member
Registered: 2008-10-05
Posts: 431

disk burning not working!

im trying to burn a cd. and i cannot get the disk burner to work, it worked last time i tried, but now it doesnt :S

i have tried k3b aswell as wodim, and both cannot detect a blank disk, even thou there is one there ,

[mark@markspc ~]$ wodim -v dev=/dev/cdrom /media/disk/ISO/ubuntu-9.04-server-i38
6.iso 
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsi
dev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
SCSI buffer size: 64512
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'LITE-ON '
Identification : 'DVDRW SHW-1635S '
Revision       : 'YS0W'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0000 (Reserved/Unknown)
Profile: 0x002B (DVD+R/DL) 
Profile: 0x001B (DVD+R) 
Profile: 0x001A (DVD+RW) 
Profile: 0x0016 (DVD-R/DL layer jump recording) 
Profile: 0x0015 (DVD-R/DL sequential recording) 
Profile: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x0011 (DVD-R sequential recording) 
Profile: 0x0010 (DVD-ROM) 
Profile: 0x000A (CD-RW) 
Profile: 0x0009 (CD-R) 
Profile: 0x0008 (CD-ROM) 
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size      : 4194304 = 4096 KB
Track 01: data   577 MB        
Total size:      662 MB (65:40.48) = 295536 sectors
Lout start:      663 MB (65:42/36) = 295536 sectors
Errno: 5 (Input/output error), test unit ready scsi sendcmd: no error
CDB:  00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.160s timeout 40s
wodim: No disk / Wrong disk!
[mark@markspc ~]$

what do i do?


Desktop: E8400@4ghz - DFI Lanparty JR P45-T2RS - 4gb ddr2 800 - 30gb OCZ Vertex - Geforce 8800 GTS - 2*19" LCD
Server/Media Zotac GeForce 9300-ITX I-E - E5200 - 4gb Ram - 2* ecogreen F2 1.5tb - 1* wd green 500gb - PicoPSU 150xt - rtorrent - xbmc - ipazzport remote - 42" LCD

Offline

#2 2009-06-05 17:55:49

btartsa
Member
Registered: 2004-07-26
Posts: 222

Re: disk burning not working!

K3b has been blowing up on me too. For some unknown reason Brasero works though...

Last edited by btartsa (2009-06-05 17:56:02)

Offline

#3 2009-06-05 18:15:16

markp1989
Member
Registered: 2008-10-05
Posts: 431

Re: disk burning not working!

btartsa wrote:

K3b has been blowing up on me too. For some unknown reason Brasero works though...

i tried brasero aswell, nothing works, i dont understand, it was working last time i went to use it .


Desktop: E8400@4ghz - DFI Lanparty JR P45-T2RS - 4gb ddr2 800 - 30gb OCZ Vertex - Geforce 8800 GTS - 2*19" LCD
Server/Media Zotac GeForce 9300-ITX I-E - E5200 - 4gb Ram - 2* ecogreen F2 1.5tb - 1* wd green 500gb - PicoPSU 150xt - rtorrent - xbmc - ipazzport remote - 42" LCD

Offline

#4 2009-06-05 18:29:34

markp1989
Member
Registered: 2008-10-05
Posts: 431

Re: disk burning not working!

when i run k3b, i get an error "there is an error in system configuration" doesnt tell me what the error is :@


Desktop: E8400@4ghz - DFI Lanparty JR P45-T2RS - 4gb ddr2 800 - 30gb OCZ Vertex - Geforce 8800 GTS - 2*19" LCD
Server/Media Zotac GeForce 9300-ITX I-E - E5200 - 4gb Ram - 2* ecogreen F2 1.5tb - 1* wd green 500gb - PicoPSU 150xt - rtorrent - xbmc - ipazzport remote - 42" LCD

Offline

#5 2009-06-05 19:35:45

markp1989
Member
Registered: 2008-10-05
Posts: 431

Re: disk burning not working!

Now i tried updating k3b, and it  wont even run :@

[mark@markspc ~]$ k3b
k3b: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /usr/lib/libkdecore.so.5)
[mark@markspc ~]$

and now when i run cdrecord i get the same error  and all it does it eject the disk , so now im stuck with 1 computer without a cd burner that wont burn disks ,and one computer with no OS on it (yay)

[mark@markspc ~]$ cdrecord -v -eject dev=/dev/cdrw Desktop/ubuntu-9.04-alternate
-amd64.iso 
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsi
dev: '/dev/cdrw'
devname: '/dev/cdrw'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
SCSI buffer size: 64512
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'LITE-ON '
Identification : 'DVDRW SHW-1635S '
Revision       : 'YS0W'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0000 (Reserved/Unknown)
Profile: 0x002B (DVD+R/DL) 
Profile: 0x001B (DVD+R) 
Profile: 0x001A (DVD+RW) 
Profile: 0x0016 (DVD-R/DL layer jump recording) 
Profile: 0x0015 (DVD-R/DL sequential recording) 
Profile: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x0011 (DVD-R sequential recording) 
Profile: 0x0010 (DVD-ROM) 
Profile: 0x000A (CD-RW) 
Profile: 0x0009 (CD-R) 
Profile: 0x0008 (CD-ROM) 
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size      : 4194304 = 4096 KB
Track 01: data   698 MB        
Total size:      802 MB (79:27.49) = 357562 sectors
Lout start:      802 MB (79:29/37) = 357562 sectors
Errno: 0 (Success), test unit ready scsi sendcmd: no error
CDB:  00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.002s timeout 40s
wodim: No disk / Wrong disk!
[mark@markspc ~]$

Last edited by markp1989 (2009-06-05 19:36:53)


Desktop: E8400@4ghz - DFI Lanparty JR P45-T2RS - 4gb ddr2 800 - 30gb OCZ Vertex - Geforce 8800 GTS - 2*19" LCD
Server/Media Zotac GeForce 9300-ITX I-E - E5200 - 4gb Ram - 2* ecogreen F2 1.5tb - 1* wd green 500gb - PicoPSU 150xt - rtorrent - xbmc - ipazzport remote - 42" LCD

Offline

#6 2009-06-05 20:00:42

markp1989
Member
Registered: 2008-10-05
Posts: 431

Re: disk burning not working!

grrr , things like this are why arch has a bad name, it was working fine last time i burned a disk, about a month ago, so now it doesnt work, for no aparent reason,


Desktop: E8400@4ghz - DFI Lanparty JR P45-T2RS - 4gb ddr2 800 - 30gb OCZ Vertex - Geforce 8800 GTS - 2*19" LCD
Server/Media Zotac GeForce 9300-ITX I-E - E5200 - 4gb Ram - 2* ecogreen F2 1.5tb - 1* wd green 500gb - PicoPSU 150xt - rtorrent - xbmc - ipazzport remote - 42" LCD

Offline

#7 2009-06-06 02:59:55

perbh
Member
From: Republic of Texas
Registered: 2005-03-04
Posts: 765

Re: disk burning not working!

Have you checked your device?
It should probably be something like /dev/sr0 and _not_ /dev/cdrom

run the following to check:

dmesg | grep sr

Offline

#8 2009-06-27 06:12:17

arnuld
Member
From: INDIA
Registered: 2005-12-19
Posts: 212
Website

Re: disk burning not working!

K3B is has blown up on my face too. Doing eject -rv and eject -v /dev/sr1 ejects both of DVD drives successfully, I even burned a CD ISO image using cdrecord  fine but K3B does not even recognize the devices. It says no CD/DVD wrtiers found or no optical devices found. (I have not tried burning a DVD from command-line yet)

Offline

#9 2009-06-27 09:19:17

FrozenFox
Member
From: College Station, TX
Registered: 2008-03-23
Posts: 422
Website

Re: disk burning not working!

markp1989 wrote:

grrr , things like this are why arch has a bad name, it was working fine last time i burned a disk, about a month ago, so now it doesnt work, for no aparent reason,

Sigh. Please don't throw around generalities about what people other than yourself think about Arch, especially on the Arch forums.. I'm sure I'm not the only one who would appreciate it. Such applies *especially* if you want people to *help you*. There are likely a few similar to me who thought / will think twice about even responding. If you are bothered that new things occasionally break (expecting otherwise seems irrational to me..), it would be wise to use a distro that keeps things old and in order for you rather than one that assumes you are linux-savvy enough to keep your own newer things in order (like reverting packages if there is a problem). The right tool for the job should always be used; there's no good reason to use Arch if such things bother you that much imo. Even then, on such a stable platform, however, some things will *still* occasionally break for some people. Shit happens. Such is the nature of software on every OS ever made, and I don't foresee it changing any time soon..

Btw... *someone* has to help sort out bugs to make things stable.. they don't magically fix themselves over time just by becoming old. wink

That said.. http://bbs.archlinux.org/viewtopic.php?id=30268  perhaps something in this thread will help you.

Also, regarding your issue with k3b.. 
http://www.archlinux.org/pipermail/arch … 05175.html
http://bbs.archlinux.org/viewtopic.php?pid=564062

Last edited by FrozenFox (2009-06-27 10:03:37)

Offline

#10 2009-06-27 12:36:05

arkham
Member
From: Stockholm
Registered: 2008-10-26
Posts: 516
Website

Re: disk burning not working!

markp1989 wrote:

grrr , things like this are why arch has a bad name, it was working fine last time i burned a disk, about a month ago, so now it doesnt work, for no aparent reason,

<offtopic>Does arch have a bad name? Oh my, I've never heard anything bad about it roll</offtopic>

Try using /dev/sr0 as device.


"I'm Winston Wolfe. I solve problems."

~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~

Offline

#11 2009-06-27 14:34:07

EVRAMP
Member
From: Czech Republic
Registered: 2008-10-03
Posts: 173
Website

Re: disk burning not working!

And try to get optical group membership.

Offline

#12 2009-06-27 23:26:47

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: disk burning not working!

markp1989 wrote:

grrr , things like this are why arch has a bad name, it was working fine last time i burned a disk, about a month ago, so now it doesnt work, for no aparent reason,

Why then, if I may inquire, are you running Arch at all?

Not some 'stable' distro like Ubuntu, Debian, Mandriva, ... Arch is a moving target. i'm sure you're familiar with that. I understand your frustration about things not working but don't go ranting on your distro, that says more about you than about the distro.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#13 2009-06-28 07:49:22

markp1989
Member
Registered: 2008-10-05
Posts: 431

Re: disk burning not working!

FrozenFox wrote:
markp1989 wrote:

grrr , things like this are why arch has a bad name, it was working fine last time i burned a disk, about a month ago, so now it doesnt work, for no aparent reason,

Sigh. Please don't throw around generalities about what people other than yourself think about Arch, especially on the Arch forums.. I'm sure I'm not the only one who would appreciate it. Such applies *especially* if you want people to *help you*. There are likely a few similar to me who thought / will think twice about even responding. If you are bothered that new things occasionally break (expecting otherwise seems irrational to me..), it would be wise to use a distro that keeps things old and in order for you rather than one that assumes you are linux-savvy enough to keep your own newer things in order (like reverting packages if there is a problem). The right tool for the job should always be used; there's no good reason to use Arch if such things bother you that much imo. Even then, on such a stable platform, however, some things will *still* occasionally break for some people. Shit happens. Such is the nature of software on every OS ever made, and I don't foresee it changing any time soon..

Btw... *someone* has to help sort out bugs to make things stable.. they don't magically fix themselves over time just by becoming old. wink

That said.. http://bbs.archlinux.org/viewtopic.php?id=30268  perhaps something in this thread will help you.

Also, regarding your issue with k3b.. 
http://www.archlinux.org/pipermail/arch … 05175.html
http://bbs.archlinux.org/viewtopic.php?pid=564062

sorry about that:
i have no problem with arch, its the main os on my computer, i was having a bad day, im used to updates changing things, then doing a quick google search or checking the wiki, and sorting it out,  just this one frustrated me more then usual for some reason, i had brought a new computer, and needed 2 burn a cd to install an os on it, its very very rare for me to need to burn a cd now i have finished distro hopping (i landed on arch btw big_smile).

thanks all other for your reply, even thou as you all sugested, my angry rant wasnt exactly helpfull or inviting a response.

Im gonna read through the links you have send me, and try your suggestions and report back.



Thanks Markp1989


edit: most reviews i have read of arch either love it or hate it , personally i love it .

Last edited by markp1989 (2009-06-28 07:59:47)


Desktop: E8400@4ghz - DFI Lanparty JR P45-T2RS - 4gb ddr2 800 - 30gb OCZ Vertex - Geforce 8800 GTS - 2*19" LCD
Server/Media Zotac GeForce 9300-ITX I-E - E5200 - 4gb Ram - 2* ecogreen F2 1.5tb - 1* wd green 500gb - PicoPSU 150xt - rtorrent - xbmc - ipazzport remote - 42" LCD

Offline

#14 2009-07-13 23:11:10

thetrivialstuff
Member
Registered: 2006-05-10
Posts: 191

Re: disk burning not working!

k3b also just died for me, after a pacman update cascade (you know, where you want to update one program and because of dependencies it causes this chain of events where everything else breaks... I can't do regular updates safely anymore because it might break my tenuous mix of KDE 3 and 4 stuff; I'm holding onto Konqueror 3.5 as long as I can).

It stopped detecting all of my drives; the solution was that the latest version of k3b now requires that HAL and Dbus be running (/etc/rc.d/hal start).

In response to someone saying Arch has a bad name; it's not Arch's fault, nearly all of the instabilities and random things breaking/disappearing are (in my experience) solely KDE 4's fault. I hate KDE 4 so much.

Offline

Board footer

Powered by FluxBB