You are not logged in.
Pages: 1
i always used cdrecord in the past, cdrecord -v dev=/dev/hdc blank=fast etc. i just installed Arch64, and cdrecord no longer works. i got some message about "wodim," so i tried that as a command (wodim blank=all) and it just hangs with the red burn light on and i have to reboot to stop it. no kill or kill -9 commands work.
so wth is "wodim?" how do i get cdrecord to work normally in A64? my user is in the optical group, and i even made a burning group. thanks
Offline
so wth is "wodim?" how do i get cdrecord to work normally in A64? my user is in the optical group, and i even made a burning group. thanks
Arch uses cdrkit instead of cdrtools. See
http://cdrkit.org/
http://www.archlinux.org/packages/12219
Don't ask me why using wodim as a replacement instead of having both to have the choice because i don't understand it. I can only suggest you to use the search function of this forum to get informations about how to get wodim work.
Offline
thanks, i have cdrkit. it turns out that Arch 64 uses weird conventions for the devices for some reason. i noticed when installing that hard drives are /dev/sdx instead of /dev/hdx, but cdrecord wasn't working with /dev/sdc, it needed /dev/sg2. :freak: my drives aren't SATA, so i don't know why it would be sdx or sgx. i guess now i'll search for why Arch 64 uses these weird designations. must be some new standard.
Last edited by slackhack (2007-05-21 15:57:14)
Offline
the weird device naming is due to libata which in the near future (and already in arch) handles SATA, and PATA(IDE) drives. It seems CD drives are now /dev/sgx while everything else is /dev/sdxy. I guess the drivers which made PATA drives /dev/hdXY are pretty old and need a re-do. Apparently you can still use the standard driver by having 'ide' but not 'pata' in your HOOKS in mkinitcpio.conf and rebuilding you initrd image.
Last edited by dmartins (2007-05-21 17:56:32)
Offline
i see, thanks.
Offline
ATAPI CD drives are now /dev/srX when using them as disks, but /dev/sgX when sending commands to them? Weird. I haven't burned a disc since moving to libata, I'll have to try.
Offline
having trouble burning in A64, actually. it failed 5 times with 2 different discs (CD-RWs), using graveman, gnomebaker, and k3b, but each burned perfectly the first time in 32bit Arch. not sure what the problem is yet...
Offline
having trouble burning in A64, actually. it failed 5 times with 2 different discs (CD-RWs), using graveman, gnomebaker, and k3b, but each burned perfectly the first time in 32bit Arch. not sure what the problem is yet...
There is a new version of cdrkit in testing, perhaps you give it a try. Sorry, i have no other hint for you.
Offline
i have the same problem mit k3b since kde 3.5.7
a lot of wodim messages from cdrecord
i found this:
chmod 4755 /usr/bin/wodim
and now it works
Offline
i found this:
chmod 4755 /usr/bin/wodim
and now it works
Better is from my view to do the old hint from cdrecord:
chown root:storage /usr/bin/wodim
chmod 4710 /usr/bin/wodim
gpasswd -a YOUR_USER storage
What i can't understand is that the big advantage of cdrkit should be that you can burn as normal user. And if this don't work than why we don't step back to the original or at minimum offer the cdrtools in /opt? So everybody can decide with what he wants to burn or see what works with his custom hardware.
But perhaps i'm not the right person to discuss this because i have big problems to understand the basic of why this fork was established. And no, i don't want to bring this negative discussion here to the forum.-)
Offline
Pages: 1