Re: Howto get k3b to detect my Burner
> Before you try to run k3b as root, from an xterm (or konsole) in KDE. > as your normal user, type: > xhost localhost > > (you should get a message like: "localhost being added to access control > list") > > then su to root and try running k3b. > > One note: I have had trouble allowing other hosts (or users) to connect > to my X server session when I've used kdm as a login manager. Rather > than dig through the configuration, I usually switch to xdm ( edit > /etc/ttys) when I need to allow other connections. > > Tim I tried this and k3b hung my entire machine. It would seem k3b just wont use the burner, an yet ironically basic proggys such as DVDRip can use it perfectly fine *g* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell wrote: I don't think that is the problem. Have you tried it as root just as a test even though it gives you warnings. I don't know what else to suggest right now. ed k3b wont run as root & i guess k3b just dosent like my burner # k3b Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kded: cannot connect to X server :0.0 kded: ERROR: KUniqueApplication: Registering failed! kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified k3b: cannot connect to X server :0.0 ERROR: KUniqueApplication: Registering failed! ERROR: Communication problem with k3b, it probably crashed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Before you try to run k3b as root, from an xterm (or konsole) in KDE. as your normal user, type: xhost localhost (you should get a message like: "localhost being added to access control list") then su to root and try running k3b. One note: I have had trouble allowing other hosts (or users) to connect to my X server session when I've used kdm as a login manager. Rather than dig through the configuration, I usually switch to xdm ( edit /etc/ttys) when I need to allow other connections. Tim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
> I don't think that is the problem. Have you tried it as root just as > a test even though it gives you warnings. > > I don't know what else to suggest right now. > > ed k3b wont run as root & i guess k3b just dosent like my burner # k3b Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kded: cannot connect to X server :0.0 kded: ERROR: KUniqueApplication: Registering failed! kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified k3b: cannot connect to X server :0.0 ERROR: KUniqueApplication: Registering failed! ERROR: Communication problem with k3b, it probably crashed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell <[EMAIL PROTECTED]> escribió: Your running kernel is compiled with the "device atapicam" option because AFAIK k3b only works with scsi. yes i have that in my kernel I have the following lines in this computers /etc/devfs.conf link acd0 cdrom link acd0 cd0 perm acd0 0777 perm cd0 0777 perm xpt0 0777 perm pass0 0777 i have the above in my devfs file I am running cdrtools-devel k3b-1.0.4_3 I also have vfs.usermount=1 set in my sysctl.conf I have a line in my fstab /dev/cd0/cdrom cd9660 ro,noauto 0 0 /dev/cd0/usr/home//cdrom cd9660 ro,noauto,nodev,nosuid 0 0 And yet with all this, it dosent detect it and wheni try to manually add the device through configure in k3b it dosent see it. Since adding atapicam in the kernel rather then a manual load my dmesg has this error... acd0: DVDR at ata2-master SATA150 pcm0: pcm0: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 991MB (2030592 512 byte sectors: 64H 32S/T 991C) cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: cd present [278528 x 2048 byte records] It doesn't look any worse than my working DVDR and DVDROM. acd1: FAILURE - READ_BIG HARDWARE ERROR asc=0x3e ascq=0x02 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 I don't think that is the problem. Have you tried it as root just as a test even though it gives you warnings. I don't know what else to suggest right now. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
> Your running kernel is compiled with the "device atapicam" option > because AFAIK k3b only works with scsi. yes i have that in my kernel > I have the following lines in this computers /etc/devfs.conf > link acd0 cdrom link acd0 cd0 perm acd0 0777 perm cd0 0777 perm xpt0 0777 perm pass0 0777 i have the above in my devfs file > I am running cdrtools-devel k3b-1.0.4_3 I also have vfs.usermount=1 set in my sysctl.conf I have a line in my fstab /dev/cd0/cdrom cd9660 ro,noauto 0 0 /dev/cd0/usr/home//cdrom cd9660 ro,noauto,nodev,nosuid 0 0 And yet with all this, it dosent detect it and wheni try to manually add the device through configure in k3b it dosent see it. Since adding atapicam in the kernel rather then a manual load my dmesg has this error... acd0: DVDR at ata2-master SATA150 pcm0: pcm0: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 991MB (2030592 512 byte sectors: 64H 32S/T 991C) cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: cd present [278528 x 2048 byte records] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell wrote: I was asking you to try k3b because internally it uses these commands to write. I don't currently have it installed (I am not really a KDE user, and I write most stuff from the command line anyway) but I think you probably have a permission problem of some kind. - Do you have the suid flag on cdrecord and cdrdao? -rwsrwsrwt 1 root wheel 406368 Jun 28 21:53 cdrecord -rwsrwsrwt 1 root wheel 603920 Jun 24 23:21 cdrdao - Do you have the fstab line suggested by 'showinfo' ? fstab has. /dev/cd0/cdrom cd9660 ro,noauto 0 0 - Do you have the permissions in devfs.conf ? only things set in there are.. perm xpt0 0666 perm pass0 0666 Example: if you can run cdrecord --scanbus as root, but you do not get the same result running it as a normal user, you do not have cdrecord installed as suid root. Then the scan for devices in k3b will probably fail. i get the same output if i use it from root or user. And i just burnt a DVD ISO find using the 1st cmnd line u gave. Since you successfully burnt from the command line, I would go through the checklist in showinfo. For example: 3b. - For every user who should be able to use k3b and for every CD or DVD device add a directory in the users home directory. These directories must be owned by the corresponding user. For each such directory add a line in /etc/fstab (see remark 2), like: /dev/cd0c /usr/home/XXX/cdrom cd9660 ro,noauto,nodev,nosuid 0 0 Furthermore allow user mounts as described in topic 9.22 of the FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPYMOUNT seems you missed this! Sorry I can't really help you further, I've done all this once and it worked ok, but I don't currently have k3b installed on any of my systems so I can't give you more specific pointers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell <[EMAIL PROTECTED]> escribió: I was asking you to try k3b because internally it uses these commands to write. I don't currently have it installed (I am not really a KDE user, and I write most stuff from the command line anyway) but I think you probably have a permission problem of some kind. - Do you have the suid flag on cdrecord and cdrdao? -rwsrwsrwt 1 root wheel 406368 Jun 28 21:53 cdrecord -rwsrwsrwt 1 root wheel 603920 Jun 24 23:21 cdrdao - Do you have the fstab line suggested by 'showinfo' ? fstab has. /dev/cd0/cdrom cd9660 ro,noauto 0 0 - Do you have the permissions in devfs.conf ? only things set in there are.. perm xpt0 0666 perm pass0 0666 Example: if you can run cdrecord --scanbus as root, but you do not get the same result running it as a normal user, you do not have cdrecord installed as suid root. Then the scan for devices in k3b will probably fail. i get the same output if i use it from root or user. And i just burnt a DVD ISO find using the 1st cmnd line u gave. I haven't been following this thread so I may repeat something or miss something but basically you need to check: Your running kernel is compiled with the "device atapicam" option because AFAIK k3b only works with scsi. I have the following lines in this computers /etc/devfs.conf link acd0 cdrom link acd0 dvd link acd0 rdvd link acd1 cdrom1 link acd1 dvd1 link acd1 rdvd1 link acd0 cd0 link acd1 cd1 perm acd0 0777 perm acd1 0777 perm cd0 0777 perm cd1 0777 Maybe over kill but works great and I, too, was a command line cd burner for years but k3b brought me the light. IMO, it is great. I am running /var/db/pkg/cdrtools-2.01_7 /var/db/pkg/k3b-1.0.4_3 although on my laptop amd64 I think I am using cdrtools-devel. I hope this helps a bit. I haven't found a machine, since I started burning dvd's a couple of years ago that k3b didn't work beautifully. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
> I was asking you to try k3b because internally it uses these commands to > write. I don't currently have it installed (I am not really a KDE user, > and I write most stuff from the command line anyway) but I think you > probably have a permission problem of some kind. > > - Do you have the suid flag on cdrecord and cdrdao? -rwsrwsrwt 1 root wheel 406368 Jun 28 21:53 cdrecord -rwsrwsrwt 1 root wheel 603920 Jun 24 23:21 cdrdao > - Do you have the fstab line suggested by 'showinfo' ? fstab has. /dev/cd0/cdrom cd9660 ro,noauto 0 0 > - Do you have the permissions in devfs.conf ? only things set in there are.. perm xpt0 0666 perm pass0 0666 > Example: > if you can run cdrecord --scanbus as root, but you do not get the same > result running it as a normal user, you do not have cdrecord installed > as suid root. Then the scan for devices in k3b will probably fail. i get the same output if i use it from root or user. And i just burnt a DVD ISO find using the 1st cmnd line u gave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell wrote: cdrecord writes DVDs as well, you just need a more recent version. Try sysutils/cdrtools-devel instead of sysutils/cdrtools. Fabian Being that it went to burn anyway, im assuming the burner is aok an is a matter of simply finding why k3b dosent detect it OR allow me to add it as a device when trying to configure k3b once the program is loaded. You can use growisofs to burn dvd isos from the command line, should be something like: growisofs -Z /dev/cd0=mytest.iso I was asking you to try k3b because internally it uses these commands to write. I don't currently have it installed (I am not really a KDE user, and I write most stuff from the command line anyway) but I think you probably have a permission problem of some kind. - Do you have the suid flag on cdrecord and cdrdao? - Do you have the fstab line suggested by 'showinfo' ? - Do you have the permissions in devfs.conf ? and so on. Sorry for repeating this, but assuming your recorder works from the command line (and I believe it does), there is nothing really more to stop k3b from using it. But k3b runs as normal user, and you run the commands as root. The problems usually start there. Example: if you can run cdrecord --scanbus as root, but you do not get the same result running it as a normal user, you do not have cdrecord installed as suid root. Then the scan for devices in k3b will probably fail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Manolis Kiagias <[EMAIL PROTECTED]> wrote: > Warren Liddell wrote: > >> Ok, it should be working. If you have an iso file and an empty CD at > >> hand try something like this: > >> > >> cdrecord -v -dao speed=24 driveropts=burnfree dev=3,0,0 mytest.iso > >> > >> and see if it actually records it. > >> > > > > > > Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.3) Copyright (C) 1995-2004 Jörg > > Schilling > > TOC Type: 1 = CD-ROM > > scsidev: '3,0,0' > > scsibus: 3 target: 0 lun: 0 [...] > > Profile: 0x0002 > > cdrecord: Found DVD media but DVD-R/DVD-RW support code is missing. > > cdrecord: If you need DVD-R/DVD-RW support, ask the Author for > > cdrecord-ProDVD. > Well, cdrecord writes CDs, not DVDs and it seems you have inserted a > DVD. Do you have an empty CDR to try? cdrecord writes DVDs as well, you just need a more recent version. Try sysutils/cdrtools-devel instead of sysutils/cdrtools. Fabian signature.asc Description: PGP signature
Re: Howto get k3b to detect my Burner
> cdrecord writes DVDs as well, you just need a more recent version. > Try sysutils/cdrtools-devel instead of sysutils/cdrtools. > > Fabian Being that it went to burn anyway, im assuming the burner is aok an is a matter of simply finding why k3b dosent detect it OR allow me to add it as a device when trying to configure k3b once the program is loaded. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
> Well, cdrecord writes CDs, not DVDs and it seems you have inserted a > DVD. Do you have an empty CDR to try? I only got DVD ISO files ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell wrote: Ok, it should be working. If you have an iso file and an empty CD at hand try something like this: cdrecord -v -dao speed=24 driveropts=burnfree dev=3,0,0 mytest.iso and see if it actually records it. Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.3) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Using libscg version 'schily-0.8'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'TSSTcorp' Identifikation : 'CDDVDW SH-S203D ' Revision : 'SB00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0010 Profile: 0x0015 Profile: 0x0016 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0014 Profile: 0x0013 Profile: 0x0012 Profile: 0x0011 Profile: 0x0010 (current) Profile: 0x000A Profile: 0x0009 Profile: 0x0008 Profile: 0x0002 cdrecord: Found DVD media but DVD-R/DVD-RW support code is missing. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. Well, cdrecord writes CDs, not DVDs and it seems you have inserted a DVD. Do you have an empty CDR to try? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
> Ok, it should be working. If you have an iso file and an empty CD at > hand try something like this: > > cdrecord -v -dao speed=24 driveropts=burnfree dev=3,0,0 mytest.iso > > and see if it actually records it. Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.3) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Using libscg version 'schily-0.8'. Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'TSSTcorp' Identifikation : 'CDDVDW SH-S203D ' Revision : 'SB00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0010 Profile: 0x0015 Profile: 0x0016 Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0014 Profile: 0x0013 Profile: 0x0012 Profile: 0x0011 Profile: 0x0010 (current) Profile: 0x000A Profile: 0x0009 Profile: 0x0008 Profile: 0x0002 cdrecord: Found DVD media but DVD-R/DVD-RW support code is missing. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Using generic SCSI-3/mmc CD/DVD driver (checks media) (mmc_cd_dvd). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1712128 = 1672 KB FIFO size : 4194304 = 4096 KB Track 01: data 0 MB padsize: 598 KB Total size:0 MB (00:04.00) = 300 sectors Lout start:1 MB (00:06/00) = 300 sectors Current Secsize: 2048 cdrecord: Unspecified command not implemented for this drive. Starting to write CD/DVD at speed 0 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Writing pregap for track 2 at -150 cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 FF FF FF 6A 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x30 Qual 0x06 (cannot format medium - incompatible medium) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.001s timeout 200s write track pad data: error after 0 bytes BFree: 0 K BSize: 1672 K Starting new track at sector: 0 Track 02:0 of0 MB written. WARNING: padding up to secsize. cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 01 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 30 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x30 Qual 0x06 (cannot format medium - incompatible medium) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.001s timeout 200s write track data: error after 0 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. Writing time:5.006s Average write speed 0.8x. Fixating... Fixating time:0.000s cdrecord: fifo had 1 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell wrote: Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.3) Copyright (C) 1995-2004 Jörg Schilling Using libscg version 'schily-0.8'. scsibus0: 0,0,0 0) 'LEXAR ' 'JUMPDRIVE SECURE' '3000' Removable Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus3: 3,0,0 300) 'TSSTcorp' 'CDDVDW SH-S203D ' 'SB00' Removable CD-ROM 3,1,0 301) * 3,2,0 302) * 3,3,0 303) * 3,4,0 304) * 3,5,0 305) * 3,6,0 306) * 3,7,0 307) * Ok, it should be working. If you have an iso file and an empty CD at hand try something like this: cdrecord -v -dao speed=24 driveropts=burnfree dev=3,0,0 mytest.iso and see if it actually records it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
On Saturday 28 June 2008 20:53:32 Manolis Kiagias wrote: > Warren Liddell wrote: > > Followed a few things, but it seems ot not initalise my burner even > > though its detected..below is the read out when running from console. > > --- > > > > kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject > > *paren > > > > Could you please check it with a command line tool? > Try as root: > > cdrecord --scanbus > > and post the output (I assume cdrecord is installed, it is a dependency > of k3b IIRC) Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.3) Copyright (C) 1995-2004 Jörg Schilling Using libscg version 'schily-0.8'. scsibus0: 0,0,0 0) 'LEXAR ' 'JUMPDRIVE SECURE' '3000' Removable Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus3: 3,0,0 300) 'TSSTcorp' 'CDDVDW SH-S203D ' 'SB00' Removable CD-ROM 3,1,0 301) * 3,2,0 302) * 3,3,0 303) * 3,4,0 304) * 3,5,0 305) * 3,6,0 306) * 3,7,0 307) * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Warren Liddell wrote: Followed a few things, but it seems ot not initalise my burner even though its detected..below is the read out when running from console. --- kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *paren Could you please check it with a command line tool? Try as root: cdrecord --scanbus and post the output (I assume cdrecord is installed, it is a dependency of k3b IIRC) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Howto get k3b to detect my Burner
Followed a few things, but it seems ot not initalise my burner even though its detected..below is the read out when running from console. --- kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *paren t, const char *name, KInstance *instance ) $ k3b: (K3bCdrecordProgram) could not start /opt/schily/bin k3b: (K3bMkisofsProgram) could not start /opt/schily/bin k3b: (K3bCdrecordProgram) could not start /home/shinjii/bin k3b: (K3bMkisofsProgram) could not start /home/shinjii/bin k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, suidroot, plain-atapi, hacked-atapi, audio-stdin, b urnfree k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version >= 1.11a02, us ing burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support fo r Just Link via burnfree driveroption (BSDDeviceScan) number of matches 22 (BSDDeviceScan) periph: da0 (BSDDeviceScan) periph: pass0 (BSDDeviceScan) periph: cd0 (BSDDeviceScan) periph: pass1 (BSDDeviceScan) add device /dev/cd0:3:0:0 (/dev/pass1) (K3bDevice::Device) /dev/cd0: init() (K3bDevice::openDevice) open device /dev/pass1 failed. Could not initialize device /dev/cd0 k3b: [void K3bMediaCache::clearDeviceList()] k3b: (K3bCdrecordProgram) could not start /opt/schily/bin k3b: (K3bMkisofsProgram) could not start /opt/schily/bin k3b: (K3bCdrecordProgram) could not start /home/shinjii/bin k3b: (K3bMkisofsProgram) could not start /home/shinjii/bin k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, suidroot, plain-atapi, hacked-atapi, audio-stdin, b urnfree k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version >= 1.11a02, us ing burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support fo r Just Link via burnfree driveroption Devices: -- kdecore (KAction): WARNING: KActionCollection::operator+=(): function is severel y deprecated. k3b: (K3bFileTreeView::addCdDeviceBranches) k3b: (K3bFileTreeView::addCdDeviceBranches) done k3b: (K3bFileTreeView::addCdDeviceBranches) k3b: (K3bFileTreeView::addCdDeviceBranches) done k3b: (K3bCore) System problems: k3b: NON_CRITICAL k3b: PROBLEM: No CD/DVD writer found. k3b: DETAILS: K3b did not find an optical writing device in your system. Thus, you will not be able to burn CDs or DVDs. However, you can still use other K3b features like audio track extraction or audio transcoding or ISO9660 image creat ion. k3b: SOLUTION: k3b: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Howto get k3b to detect my Burner
I have read verious manuals and the showinfo in k3b, but being relatively new to the freebsd world, im not quite sure what to do in order to get k3b to detect my burner. The burning device /dev/acd0 is a SATA burner Any help greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
