Bug #670
closedCan't burn in K3B anymore after the /dev changes
Added by elekktretterr over 17 years ago. Updated over 17 years ago.
0%
Description
Hi,
I used to use /dev/cd0c to burn stuff via k3b. Now, even though i can
still mount cd0c, k3b now says that it cannot find a burning device in
cd0c :S.
Any clues?
Updated by elekktretterr over 17 years ago
I don't have /dev/cd0.
I tried sh MAKEDEV cd0 but still dont have cd0.
Petr
Updated by elekktretterr over 17 years ago
By the way i am using running with NATA.
Updated by grzela over 17 years ago
k3b use cdrtools to write disk.
cdrtools v. 2.01.01.20 - 2.01.01.26 don't work under FreeBSD and DFly,
I haven't test it but in changelog for 2.01.01.27 is mentioned that this
version works again on FreeBSD (so should run also on DFly).
Updated by elekktretterr over 17 years ago
I am actually using cdrtools-ossdvd which has been working good since
march when i installed it.
Petr
Updated by dillon over 17 years ago
:Petr Janda wrote:
:> I used to use /dev/cd0c to burn stuff via k3b. Now, even though i can=20
:> still mount cd0c, k3b now says that it cannot find a burning device in =
:
:> cd0c :S.
:
:tried cd0?
There is no cd0. Just cd0a and cd0c, marked as the compatibility slice.
I wanted to make thses cd0s0a and cd0s0c but I didn't want to try to
fix all the boot code yet.
We may have to make a cd0 for burning purposes. I will throw a CD-R
drive into my test box and check it out.
-Matt
Updated by dillon over 17 years ago
:I am actually using cdrtools-ossdvd which has been working good since
:march when i installed it.
:
:Petr
I was able to build and install this baby from pkgsrc, and it seems to
work.
cdrecord -scanbus
cdrecord -v -dummy -data speed=4 dev=1,0,0 /usr/release/dfly.iso
cdrecord -v -data speed=4 dev=1,0,0 /usr/release/dfly.iso
mount ....
all works
burncd also works on /dev/acd0
cdda2wav works with this package too.
I haven't tried it with NATA yet, but it all seems to work with ATA.
I am working on a NATA build now.
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by dillon over 17 years ago
Petr, try creating a 'cd0' device as follows, and see if k3b works
via that.
cd /dev
mknod cd0 c 15 0x1e110007
--
Are you still able to burn the CD using cdrecord directly?
-Matt
Updated by elekktretterr over 17 years ago
doesn't work:(
cdrecord is also not working (it used to).
elevator# cdrecord scanbus) Copyright (C) 1995-2006 Jörg Schilling
Cdrecord-Clone 2.01.01a04 (-
NOTE: this is OSS DVD extensions for cdrtools and thus may have bugs
related to DVD issues that are not present in the original cdrtools. For
more information see http://crashrecovery.org/oss-dvd.html. The original
cdrtools author should not be bothered with problems in this version.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
cdrecord: Invalid argument. Open by 'devname' not supported on this OS.
Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Petr
Updated by dillon over 17 years ago
:doesn't work:(
:cdrecord is also not working (it used to).
It's working for me, with NATA and ATA. I think this may be a
recompilation issue. The CAM structures are shared with the kernel
and its really easy for them to change size. Try getting rid of
the package and its dependancies (well, at least the libraries it
uses), then rebuild.
Also make sure your world is completely synchronized with your kernel
before rebuilding.
-Matt
test28# cdrecord scanbus) Copyright (C) 1995-2006 Jrg Schilling
Cdrecord-Clone 2.01.01a04 (-
NOTE: this is OSS DVD extensions for cdrtools and thus may have bugs
related to DVD issues that are not present in the original cdrtools. For
more information see http://crashrecovery.org/oss-dvd.html. The original
cdrtools author should not be bothered with problems in this version.
Using libscg version 'schily-0.8'.
scsibus1:
1,0,0 100) 'TEAC ' 'CD-W54E ' '1.1B' Removable CD-ROM
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
test28#
Updated by elekktretterr over 17 years ago
Indeed recompiling fixed it.
Thank you Matt,
Petr