pkg search k3b returns nothing
I've just changed to pkg and thought that I would try out how it works. After copying the pkg.conf.sample to pkg.conf and doing pkg update Updating repository catalogue repo.txz100% 1836 1.8KB/s 1.8KB/s 00:00 I tried the command pkg search k3b and it returned with nothing. Is it so that not all ports are available as packages and that's why I don't get anything? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg search k3b returns nothing
On 04/02/2013 11:35, Leslie Jensen wrote: I've just changed to pkg and thought that I would try out how it works. After copying the pkg.conf.sample to pkg.conf and doing pkg update Updating repository catalogue repo.txz100% 1836 1.8KB/s 1.8KB/s 00:00 I tried the command pkg search k3b and it returned with nothing. Is it so that not all ports are available as packages and that's why I don't get anything? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org What repo are you using? According to the latest release announcement (http://www.freebsd.org/releases/9.1R/announce.html), no official repos hold pkgng, it's just a test environment with one package or so. The bad news is that pkg2ng conversion is irreversible:) I just googled and found an unofficial repo announced here: http://lists.freebsd.org/pipermail/freebsd-stable/2013-February/072037.html Or you can try to set up one yourself as explained here: http://www.sysadmin-fr.org/fr/node/667 But I haven't tested how this works. Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg search k3b returns nothing
2013-04-02 11:22, Jeff Tipton skrev:
On 04/02/2013 11:35, Leslie Jensen wrote:
I've just changed to pkg and thought that I would try out how it works.
After copying the pkg.conf.sample to pkg.conf and doing
pkg update
Updating repository catalogue
repo.txz100% 1836 1.8KB/s 1.8KB/s 00:00
I tried the command pkg search k3b and it returned with nothing.
Is it so that not all ports are available as packages and that's why I
don't get anything?
Thanks
/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
What repo are you using? According to the latest release announcement
(http://www.freebsd.org/releases/9.1R/announce.html), no official repos
hold pkgng, it's just a test environment with one package or so. The bad
news is that pkg2ng conversion is irreversible:) I just googled and
found an unofficial repo announced here:
http://lists.freebsd.org/pipermail/freebsd-stable/2013-February/072037.html
Or you can try to set up one yourself as explained here:
http://www.sysadmin-fr.org/fr/node/667
But I haven't tested how this works.
Jeff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
My /usr/local/etc/pkg.conf lists
PACKAGESITE : http://pkg.freebsd.org/${ABI}/latest
But thank you anyway.
I suspected something like this so I'll just carry on installing as I
use to.
Hopefully there will be packages available eventually.
/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg search k3b returns nothing
On 2013-04-02 10:35, Leslie Jensen wrote: I've just changed to pkg and thought that I would try out how it works. After copying the pkg.conf.sample to pkg.conf and doing pkg update Updating repository catalogue repo.txz100% 1836 1.8KB/s 1.8KB/s 00:00 I tried the command pkg search k3b and it returned with nothing. Is it so that not all ports are available as packages and that's why I don't get anything? http://www.freebsd.org/news/2012-compromise.html signature.asc Description: OpenPGP digital signature
SV: Re: pkg search k3b returns nothing
Thank you! I had not read the last announcements. That explains it all. Sent from my Samsung Mobile Originalmeddelande Från: Tijl Coosemans t...@coosemans.org Datum: Till: Leslie Jensen les...@eskk.nu Kopia: FreeBSD Questions Mailing List freebsd-questions@freebsd.org Rubrik: Re: pkg search k3b returns nothing On 2013-04-02 10:35, Leslie Jensen wrote: I've just changed to pkg and thought that I would try out how it works. After copying the pkg.conf.sample to pkg.conf and doing pkg update Updating repository catalogue repo.txz 100% 1836 1.8KB/s 1.8KB/s 00:00 I tried the command pkg search k3b and it returned with nothing. Is it so that not all ports are available as packages and that's why I don't get anything? http://www.freebsd.org/news/2012-compromise.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Which k3b is recommended?
On Thu, 2013-01-03 at 09:50 +0100, Leslie Jensen wrote: I need k3b on a newly installed 9.1-RELEASE system. I wonder if I miss out on some functionality if I go with version without KDE? I use XFCE4 as my Desktop. I don't think so. On Linux I'm running K3b on Xfce. I never noticed that there's a difference, if KDE isn't installed. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Which k3b is recommended?
On Thu, 03 Jan 2013 09:50:46 +0100, Leslie Jensen wrote: I need k3b on a newly installed 9.1-RELEASE system. I wonder if I miss out on some functionality if I go with version without KDE? I use XFCE4 as my Desktop. Maybe not directly related, but I'm using k9copy without a full KDE installation, with WindowMaker as my window manager (no desktop at all). I'm not missing any essential functionality for this program. So probably using k3b should work just fine. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Which k3b is recommended?
I need k3b on a newly installed 9.1-RELEASE system. I wonder if I miss out on some functionality if I go with version without KDE? I use XFCE4 as my Desktop. Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Which k3b is recommended?
Le Thu, 03 Jan 2013 09:50:46 +0100, Leslie Jensen les...@eskk.nu a écrit : I need k3b on a newly installed 9.1-RELEASE system. I wonder if I miss out on some functionality if I go with version without KDE? Don't know. I use XFCE4 as my Desktop. Did you tried sysutils/xfburn? It is ligth but does the job. (nowadays I use cdrecord directly, but xfburn worked in the past...) Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Which k3b is recommended?
Hello. 2013/01/03 09:50:46 +0100 Leslie Jensen les...@eskk.nu = To FreeBSD Questions : LJ I need k3b on a newly installed 9.1-RELEASE system. LJ I wonder if I miss out on some functionality if I go with version LJ without KDE? LJ I use XFCE4 as my Desktop. I use the 'sysutils/tkdvd' and the only thing I time to time use to find missing there is the '-joliet-long' checkbox. -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: 1754B9C1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0) SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1) LITE-ON DVDRW SHW-160P6S PS08at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
On 04/07/2012 09:13, Jeff Tipton wrote: Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0) SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1) LITE-ON DVDRW SHW-160P6S PS08at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Some news. I found out that xfburn depends on libburn, so I recompiled libburn, too. Now xfburn seems to work (could blank a disk, write an ISO image, write files to a disk). As for k3b (which I would prefer), nothing changed. Only I found that when I insert a disk before launching k3b, it finds the drive as read-only. Now the popup window says: No CD/DVD/BD writer found. 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 such as audio track extraction, audio transcoding or ISO9660 image creation. In Settings Devices dialog, Writers are shown as none, and /dev/cd0 is under Read-only Drives. There are blank squares against Vendor and Firmware, and Error against Write Capabilities:. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
On Sat, 07 Apr 2012 18:57:09 +0300 Jeff Tipton jef...@mail.com wrote: On 04/07/2012 09:13, Jeff Tipton wrote: Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0) SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1) LITE-ON DVDRW SHW-160P6S PS08at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Some news. I found out that xfburn depends on libburn, so I recompiled libburn, too. Now xfburn seems to work (could blank a disk, write an ISO image, write files to a disk). As for k3b (which I would prefer), nothing changed. Only I found that when I insert a disk before launching k3b, it finds the drive as read-only. Now the popup window says: No CD/DVD/BD writer found. 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 such as audio track extraction, audio transcoding or ISO9660 image creation. In Settings Devices dialog, Writers are shown as none, and /dev/cd0 is under Read-only Drives. There are blank squares against Vendor and Firmware, and Error against Write Capabilities:. For what it is worth, I had a similar problem with FreeBSD 9 back in the Beta days. IIRC I had to rebuild cdparanoia and then K3B and all was working again. YMMV Good Luck Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
On 04/08/2012 03:33, Robert wrote: On Sat, 07 Apr 2012 18:57:09 +0300 Jeff Tiptonjef...@mail.com wrote: On 04/07/2012 09:13, Jeff Tipton wrote: Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0)SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1)LITE-ON DVDRW SHW-160P6S PS08 at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Some news. I found out that xfburn depends on libburn, so I recompiled libburn, too. Now xfburn seems to work (could blank a disk, write an ISO image, write files to a disk). As for k3b (which I would prefer), nothing changed. Only I found that when I insert a disk before launching k3b, it finds the drive as read-only. Now the popup window says: No CD/DVD/BD writer found. 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 such as audio track extraction, audio transcoding or ISO9660 image creation. In Settings Devices dialog, Writers are shown as none, and /dev/cd0 is under Read-only Drives. There are blank squares against Vendor and Firmware, and Error against Write Capabilities:. For what it is worth, I had a similar problem with FreeBSD 9 back in the Beta days. IIRC I had to rebuild cdparanoia and then K3B and all was working again. YMMV Good Luck Robert Thank you, it works now! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems With K3b
On Sat, 20 Feb 2010 22:00:10 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: I've already added the necessary line to /boot/default/loader.conf for enabling dma) The file /boot/loader.conf is the file you should edit. The defaults file is read prior to the normal config file, it is overriden by different settings. Using pkg_add for k3b isn't working because I'm using a newer version of some of it's dependencies and that apparently is causing problems (I should have never installed Xv, I had to upgrade jpeg from jpeg-7 to jpeg-8 and that upgrade has caused nothing but problems). I've experienced that fun, too. :-) What error message is issued if you fake install K3B? See pkg_add -rvn (remote, verbose, no-install)? Maybe it will work with the newer version of libjpeg. I realize now that I'm going to have to learn to use the port management tools to help prevent problems like this in the future and that's ok. I've often been told that portmaster would be a good choice. I've used portinstall / portupgrade in the past, but have to say that I honestly prefer pkg_add -r for simplicity. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems With K3b
On Sunday 21 February 2010, Programmer In Training wrote: so I deinstalled qt33 and began recompiling it with the intention of enabling thread support. The compile of Qt than proceeded to fail (I've long since closed the window but could retry it to get the specific messages if needed). I need Qt back because I have quite a few apps that require Qt installed I know that this won't help your immediate problem of getting Qt back but it might help with future problems. You don't really need to deinstall any package before attempting to rebuild it, e.g. First create a log file for the task. script rebuild.log Now create a backup copy of your current working package, adjust the version number below to match your system pkg_create -b qt-3.3.8_11 /tmp/qt-3.3.8_11 Go ahead and build the new binary but don't attempt to install it yet cd /usr/ports/x11-toolkits/qt33 make clean make If you get this far then you've successfully created the binary so go ahead and install it. make deinstall reinstall make clean If everything goes pear shaped in the install stage and the new version fails to install then just cd to /tmp and use pkg_add qt-3.3.8_11.tbz to reinstall the previous version. When everything is finished hit control-D or type exit to stop logging your output. You have a full record of all output in your rebuild.log file so if things went wrong during the build you can peruse it at leisure even after you've closed the window. I realize now that I'm going to have to learn to use the port management tools to help prevent problems like this in the future It's certainly worth spending some time to familiarise yourself with portupgrade or portmaster - among other things these do all the necessary steps of creating temporary backups and reinstalling them if things go wrong. Portmaster should be adequate for most of your needs, portupgrade offers more features but at the expense of a bit more complexity -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems With K3b
On 02/21/10 03:58, Polytropon wrote: snip I've often been told that portmaster would be a good choice. I've used portinstall / portupgrade in the past, but have to say that I honestly prefer pkg_add -r for simplicity. :-) I'm running portmaster right now to check for new packages and (recursively) dependencies and to upgrade anything that needs upgrading (if I'm reading the man page right I believe I issued the right command). I'm hoping this will take care of my k3b issue as well. Either way, I've decided to not worry about k3b, though I do want to resolve this if for no other reason than for if someone else runs into this problem, the archive will have the solution. I'd give you the output of pkg_add -rvn k3b but it'd be pointless because at some point I think I might have forced its install. pkgdb -f (to handle the stale dependency for mDNSResponder-108) flakes out on mDNSResponder, I think. I have more important issues right now than k3b (such as searching out docs for accessing my internal IOmega ZIP100 drive, seeing as the handbook only deals with USB, Optical (CD and DVD) and Floppy drives). I'll keep the list updated with my progress in getting k3b working (right now I get the following: [us...@hostname]k3b /libexec/ld-elf.so.1: Shared object libkparts.so.3 not found, required by k3b which I'm hoping portmaster will fix). -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Problems With K3b
I'm trying to install k3b from ports so I might use my DVD super multi format drive (an HP 1040i; I've already added the necessary line to /boot/default/loader.conf for enabling dma) with either the gui or cli but during the install of libthai (which is a dependency of kimproxy which is a dependency of k3b) the configure script infinitely loops. Is anyone else having this issue? I was able to add it via pkg_add -r but encountered other problems. Apparently I hadn't compiled Qt with thread support and another required part of kdelibs failed on that part, so I deinstalled qt33 and began recompiling it with the intention of enabling thread support. The compile of Qt than proceeded to fail (I've long since closed the window but could retry it to get the specific messages if needed). I need Qt back because I have quite a few apps that require Qt installed (though I'm wanting to get rid of qwit, if anyone can recommend a /good/ Twitter client for FreeBSD, I'd appreciate a private mail with the recommendation). Using pkg_add for k3b isn't working because I'm using a newer version of some of it's dependencies and that apparently is causing problems (I should have never installed Xv, I had to upgrade jpeg from jpeg-7 to jpeg-8 and that upgrade has caused nothing but problems). I can really do without k3b since I do have the cli tools, but I'd like to resolve these issues (when I asked for help with flash, I was able to update my ports collection so I have the latest available as of yesterday) so that they aren't problems further on down the road. I realize now that I'm going to have to learn to use the port management tools to help prevent problems like this in the future and that's ok. This install is supposed to be a learning experience (even if this box has become my primary machine, unlike I had intended) and I am trying to learn. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: K3b-DVD
On July 20, 2009, ajtiM wrote: My system: FreeBSD 7.2, KDE 3.5.10 Same here. I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported When I run cdrecord with an invalid option, I get the following output. I draw attention to the line stating that there is no support for DVD-R/DVD-RW. I speculate that this may be related to the problem you are seeing. I have not explored cdrecord-ProDVD. # cdrecord xxx cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01 (amd64-unknown-freebsd7.1) Copyright (C) 1995-2004 J�rg Schilling scsidev: '5,0,0' scsibus: 5 target: 0 lun: 0 Using libscg version 'schily-0.8'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identifikation : 'DVD-RAM GH22NS30' Revision : '1.01' Device seems to be: Generic mmc2 DVD-R/DVD-RW. 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-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R cdrecord: No such file or directory. Cannot open 'xxx'. Cheers, -- Norbert Papke. npa...@acm.org http://saveournet.ca Protecting your Internet's level playing field ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Monday 20 July 2009 16:39:45 ajtiM wrote: Hi! My system: FreeBSD 7.2, KDE 3.5.10 I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported I had this writer at one point. Check the NEC site for supported media. It doesn't support all writeable DVD layers, especially the low cost ones, however there are some firmware upgrades that add new media support. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Thursday 23 July 2009 13:51:51 Mel Flynn wrote: On Monday 20 July 2009 16:39:45 ajtiM wrote: Hi! My system: FreeBSD 7.2, KDE 3.5.10 I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported I had this writer at one point. Check the NEC site for supported media. It doesn't support all writeable DVD layers, especially the low cost ones, however there are some firmware upgrades that add new media support. It hasfirmware upgrade but I need Windows. On my computer is just FreeBSD. -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Thursday 23 July 2009 12:57:42 ajtiM wrote: On Thursday 23 July 2009 13:51:51 Mel Flynn wrote: On Monday 20 July 2009 16:39:45 ajtiM wrote: Hi! My system: FreeBSD 7.2, KDE 3.5.10 I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported I had this writer at one point. Check the NEC site for supported media. It doesn't support all writeable DVD layers, especially the low cost ones, however there are some firmware upgrades that add new media support. It hasfirmware upgrade but I need Windows. On my computer is just FreeBSD. Put the drive on a windows computer or buy new media that is compatible. There's no other way, unfortunately. There is however a PDF on the site with compatible media. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Monday 20 July 2009 08:39:45 pm ajtiM wrote: Hi! My system: FreeBSD 7.2, KDE 3.5.10 I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported Write error Debugging output: System --- K3b Version: 1.0.5 KDE Version: 3.5.10 QT Version: 3.3.8 Kernel: 7.2-RELEASE-p2 Devices --- _NEC DVD_RW ND-1300A 1.06 (/dev/cd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW] [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite] Burned media --- DVD-R Sequential K3bIsoImager --- mkisofs print size result: 1930464 (3953590272 bytes) Pipe throughput: 33570816 bytes read, 33562624 bytes written. Used versions --- mkisofs: 2.1 growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/pass4 obs=32k seek=0' /dev/pass4: Current Write Speed is 1.0x1352KBps. :-[ wr...@lba=0h failed with SK=5h/CANNOT WRITE MEDIUM - INCOMPATIBLE : FORMAT]: Invalid argument :-( media is not formatted or unsupported. :-( write failed: Invalid argument --- diagnostics removed --- Some thoughts. Every time I set up k3b to run under FreeBSD I had to run it as root or it would not recognize the drive properly. The first thing I can think of is to make sure that under set - devices your drive is displayed properly. If not, try running k3b as root. Not an ideal solution but ti should at least get you going, if that is the problem. The other problem I have had is that I had to change from Writing Mode : Auto to Writing Mode: DAO I don't know why but I would have read / write errors, change the Write Mode to DAO and then it would work. I hope this helps, I understand your frustration... Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Tuesday 21 July 2009 08:47:35 Mark Moellering wrote: On Monday 20 July 2009 08:39:45 pm ajtiM wrote: Hi! My system: FreeBSD 7.2, KDE 3.5.10 I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported Write error Debugging output: System --- K3b Version: 1.0.5 KDE Version: 3.5.10 QT Version: 3.3.8 Kernel: 7.2-RELEASE-p2 Devices --- _NEC DVD_RW ND-1300A 1.06 (/dev/cd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW] [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite] Burned media --- DVD-R Sequential K3bIsoImager --- mkisofs print size result: 1930464 (3953590272 bytes) Pipe throughput: 33570816 bytes read, 33562624 bytes written. Used versions --- mkisofs: 2.1 growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/pass4 obs=32k seek=0' /dev/pass4: Current Write Speed is 1.0x1352KBps. :-[ wr...@lba=0h failed with SK=5h/CANNOT WRITE MEDIUM - INCOMPATIBLE : FORMAT]: Invalid argument :-( media is not formatted or unsupported. :-( write failed: Invalid argument --- diagnostics removed --- Some thoughts. Every time I set up k3b to run under FreeBSD I had to run it as root or it would not recognize the drive properly. The first thing I can think of is to make sure that under set - devices your drive is displayed properly. If not, try running k3b as root. Not an ideal solution but ti should at least get you going, if that is the problem. The other problem I have had is that I had to change from Writing Mode : Auto toWriting Mode: DAO I don't know why but I would have read / write errors, change the Write Mode to DAO and then it would work. I hope this helps, I understand your frustration... Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I did try but it didn't work (burning of CD works). In /var/log/messages I have: ... ul 21 16:34:49 athena kernel: acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x06 Jul 21 16:34:49 athena last message repeated 2 times Jul 21 16:34:49 athena kernel: (cd0:ata1:0:0:0): READ TOC/PMA/ATIP. CDB: 43 0 0 0 0 0 0 0 4 0 Jul 21 16:34:49 athena kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Jul 21 16:34:49 athena kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Jul 21 16:34:49 athena kernel: (cd0:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 Jul 21 16:34:49 athena kernel: (cd0:ata1:0:0:0): Invalid field in CDB: Command byte 6 is invalid Jul 21 16:34:49 athena kernel: (cd0:ata1:0:0:0): Unretryable error Jul 21 16:35:39 athena kernel: acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x06 Jul 21 16:36:12 athena kernel: acd0: FAILURE - RESERVE_TRACK ILLEGAL REQUEST asc=0x30 ascq=0x05 Jul 21 16:36:12 athena kernel: acd0: FAILURE - WRITE_BIG ILLEGAL REQUEST asc=0x30 ascq=0x05 in /etc/devfs.conf: Commonly used by many ports linkacd0cdrom linkacd0dvd linkcd0 cdrom linkcd0 dvd # K3b perm/dev/acd0 0666 perm/dev/cd00666 permcdrom 0666 permdvd 0666 permxpt00666 permpass4 0666 and in /etc/fstab: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd0/cdrom cd9660 ro,noauto 0 0 Thanks. -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Tue, 21 Jul 2009 17:18:14 -0500, ajtiM lum...@gmail.com wrote: in /etc/devfs.conf: Commonly used by many ports linkacd0cdrom linkacd0dvd linkcd0 cdrom linkcd0 dvd All four lines? Where do /dev/dvd and /dev/cdrom actually point to? The devices should be cd0, not acd0. The growisofs program utilizes /dev/cd0 for burning via the atapicam facility - I'm sure you have loaded it. # K3b perm/dev/acd0 0666 perm/dev/cd00666 I'm not sure the /dev/ prefix is needed... permcdrom 0666 permdvd 0666 permxpt00666 permpass4 0666 For comparison: I have linkacd0cdrom linkcd0 dvd only, and permissions own cd0 root:operator permcd0 0664 own xpt0root:operator permxpt00660 own pass0 root:operator permpass0 0660 I added my username to the operator group (and wheel), so I can have power on the devices needed for burning. Have you done this, too? and in /etc/fstab: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd0/cdrom cd9660 ro,noauto 0 0 I don't know why you are employing cd0 and acd0 in parallel. You can use cd0 for everything. I'm using the acd driver only for reading CDs and DVDs, but for recording them, cd0 is used. So the corresponding entries in my /etc/fstab is this: /dev/acd0/media/cdrom cd9660 ro,noauto 0 0 Allthough it looks like a medium error, it's still possible that it is a permission problem, and growisofs is showing this problem. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
K3b-DVD
Hi! My system: FreeBSD 7.2, KDE 3.5.10 I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported Write error Debugging output: System --- K3b Version: 1.0.5 KDE Version: 3.5.10 QT Version: 3.3.8 Kernel: 7.2-RELEASE-p2 Devices --- _NEC DVD_RW ND-1300A 1.06 (/dev/cd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW] [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite] Burned media --- DVD-R Sequential K3bIsoImager --- mkisofs print size result: 1930464 (3953590272 bytes) Pipe throughput: 33570816 bytes read, 33562624 bytes written. Used versions --- mkisofs: 2.1 growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/pass4 obs=32k seek=0' /dev/pass4: Current Write Speed is 1.0x1352KBps. :-[ wr...@lba=0h failed with SK=5h/CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT]: Invalid argument :-( media is not formatted or unsupported. :-( write failed: Invalid argument growisofs command: --- /usr/local/bin/growisofs -Z /dev/cd0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=tracksize:1930464 -use-the-force-luke=bufsize:32m mkisofs --- 1930464 0.03% done, estimate finish Mon Jul 20 19:33:13 2009 0.05% done, estimate finish Mon Jul 20 19:33:13 2009 0.08% done, estimate finish Mon Jul 20 19:33:13 2009 0.10% done, estimate finish Mon Jul 20 19:33:13 2009 0.13% done, estimate finish Mon Jul 20 19:33:13 2009 0.16% done, estimate finish Mon Jul 20 19:33:13 2009 0.18% done, estimate finish Mon Jul 20 19:33:13 2009 0.21% done, estimate finish Mon Jul 20 19:33:13 2009 0.23% done, estimate finish Mon Jul 20 19:33:13 2009 0.26% done, estimate finish Mon Jul 20 19:33:13 2009 0.29% done, estimate finish Mon Jul 20 19:33:13 2009 0.31% done, estimate finish Mon Jul 20 19:33:13 2009 0.34% done, estimate finish Mon Jul 20 19:33:13 2009 0.36% done, estimate finish Mon Jul 20 19:33:13 2009 0.39% done, estimate finish Mon Jul 20 19:33:13 2009 0.42% done, estimate finish Mon Jul 20 19:33:13 2009 0.44% done, estimate finish Mon Jul 20 19:37:00 2009 0.47% done, estimate finish Mon Jul 20 19:36:47 2009 0.49% done, estimate finish Mon Jul 20 19:36:35 2009 0.52% done, estimate finish Mon Jul 20 19:36:25 2009 0.54% done, estimate finish Mon Jul 20 19:36:16 2009 0.57% done, estimate finish Mon Jul 20 19:36:08 2009 0.60% done, estimate finish Mon Jul 20 19:36:00 2009 0.62% done, estimate finish Mon Jul 20 19:35:53 2009 0.65% done, estimate finish Mon Jul 20 19:35:47 2009 0.67% done, estimate finish Mon Jul 20 19:35:41 2009 0.70% done, estimate finish Mon Jul 20 19:35:35 2009 0.73% done, estimate finish Mon Jul 20 19:35:30 2009 0.75% done, estimate finish Mon Jul 20 19:35:26 2009 0.78% done, estimate finish Mon Jul 20 19:35:21 2009 0.80% done, estimate finish Mon Jul 20 19:35:17 2009 0.83% done, estimate finish Mon Jul 20 19:35:13 2009 mkisofs calculate size command: --- /usr/local/bin/mkisofs -gui -graft-points -print-size -quiet -volid OREGON -volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer -sysid FREEBSD -volset-size 1 -volset-seqno 1 -sort /tmp/kde-ajtim/k3baYZzED.tmp -rational-rock -hide-list /tmp/kde-ajtim/k3byN8Xqs.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-ajtim/k3bnTMadX.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-ajtim/k3brPzoL3.tmp mkisofs command: --- /usr/local/bin/mkisofs -gui -graft-points -volid OREGON -volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer -sysid FREEBSD -volset-size 1 -volset-seqno 1 -sort /tmp/kde-ajtim/k3bopj3Zk.tmp -rational-rock -hide-list /tmp/kde-ajtim/k3bWY712E.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-ajtim/k3bxTrNNL.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-ajtim/k3byB6RnA.tmp -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Mon, 20 Jul 2009 19:39:45 -0500, ajtiM lum...@gmail.com wrote: I did try to burn data DVD with my NEC DVD ND-1300A but I got an error: :-( Media is not formatted or unsupported Write error Check if your drive really supports DVD-R (allthoug it obviously should) by running this command: # cdrecord -scanbus # cdrecord dev=1,0,0 -inq # cdrecord dev=1,0,0 -prcap The cdrecord program is part of the cdrtools port / package. growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/pass4 obs=32k seek=0' /dev/pass4: Current Write Speed is 1.0x1352KBps. :-[ wr...@lba=0h failed with SK=5h/CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT]: Invalid argument :-( media is not formatted or unsupported. :-( write failed: Invalid argument growisofs command: --- /usr/local/bin/growisofs -Z /dev/cd0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=tracksize:1930464 -use-the-force-luke=bufsize:32m Check if the growisofs command alone produces the same error messages (just to make sure it's not a K3B problem): # growisofs -Z /dev/cd0 -r -J some files here Check permissions for the cd and pass devices. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Monday 20 July 2009 20:11:03 Polytropon wrote: Check if your drive really supports DVD-R (allthoug it obviously should) by running this command: # cdrecord -scanbus # cdrecord dev=1,0,0 -inq # cdrecord dev=1,0,0 -prcap The cdrecord program is part of the cdrtools port / package. Thank you for the help. I don't know what is wrong still. I did burn DVD on FreeBSD 7.2 and before that on Linux. Now I have FreeBSD 7.2 (no ther OS) but it doesn't work. cdrecord -scanbus Cdrecord-Clone 2.01 (i386-unknown-freebsd7.2) Copyright (C) 1995-2004 Jörg Schilling Using libscg version 'schily-0.8'. scsibus0: 0,0,0 0) 'IN-WIN ' 'iAPP HS-CF' '0.96' 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) * scsibus2: 2,0,0 200) '_NEC' 'DVD_RW ND-1300A ' '1.06' Removable CD-ROM 2,1,0 201) * 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) * 2,7,0 207) * cdrecord dev=2,0,0 -inq Cdrecord-Clone 2.01 (i386-unknown-freebsd7.2) Copyright (C) 1995-2004 Jörg Schilling scsidev: '2,0,0' scsibus: 2 target: 0 lun: 0 Using libscg version 'schily-0.8'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-1300A ' Revision : '1.06' Device seems to be: Generic mmc2 DVD-R/DVD-RW. cdrecord dev=2,0,0 -prcap Cdrecord-Clone 2.01 (i386-unknown-freebsd7.2) Copyright (C) 1995-2004 Jörg Schilling scsidev: '2,0,0' scsibus: 2 target: 0 lun: 0 Using libscg version 'schily-0.8'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: '_NEC' Identifikation : 'DVD_RW ND-1300A ' Revision : '1.06' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Drive capabilities, per MMC-3 page 2A: Does read CD-R media Does write CD-R media Does read CD-RW media Does write CD-RW media Does read DVD-ROM media Does read DVD-R media Does write DVD-R media Does not read DVD-RAM media Does not write DVD-RAM media Does support test writing Does read Mode 2 Form 1 blocks Does read Mode 2 Form 2 blocks Does read digital audio blocks Does restart non-streamed digital audio reads accurately Does support Buffer-Underrun-Free recording Does read multi-session CDs Does read fixed-packet CD media using Method 2 Does not read CD bar code Does read R-W subcode information Does not return R-W subcode de-interleaved and error-corrected Does read raw P-W subcode data from lead in Does return CD media catalog number Does return CD ISRC information Does support C2 error pointers Does not deliver composite A/V data Does play audio CDs Number of volume control levels: 256 Does support individual volume control setting for each channel Does support independent mute setting for each channel Does not support digital output on port 1 Does not support digital output on port 2 Loading mechanism type: tray Does support ejection of CD via START/STOP command Does not lock media on power up via prevent jumper Does allow media to be locked in the drive via PREVENT/ALLOW command Is not currently in a media-locked state Does not support changing side of disk Does not have load-empty-slot-in-changer feature Does not support Individual Disk Present feature Maximum read speed: 7056 kB/s (CD 40x, DVD 5x) Current read speed: 7056 kB/s (CD 40x, DVD 5x) Maximum write speed: 2822 kB/s (CD 16x, DVD 2x) Current write speed: 2822 kB/s (CD 16x, DVD 2x) Rotational control selected: CLV/PCAV Buffer size in KB: 2048 Copy management revision supported: 1 Number of supported write speeds: 3 Write speed # 0: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) Write speed # 1: 1411 kB/s CLV/PCAV (CD 8x, DVD 1x) Write speed # 2: 706 kB/s CLV/PCAV (CD 4x, DVD 0x) -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Mon, 20 Jul 2009 20:29:20 -0500, ajtiM lum...@gmail.com wrote: Thank you for the help. I don't know what is wrong still. I did burn DVD on FreeBSD 7.2 and before that on Linux. Now I have FreeBSD 7.2 (no ther OS) but it doesn't work. Did you always use K3B? Have you changed permissions on the device files? And finally: Are you sure that you are really using a blank DVD-R that is not defective? I'm asking because I was that clever myself to try to write to a defective media. :-) cdrecord -scanbus 2,0,0 200) '_NEC' 'DVD_RW ND-1300A ' '1.06' Removable CD-ROM [...] cdrecord dev=2,0,0 -prcap Drive capabilities, per MMC-3 page 2A: Does write CD-R media Does write CD-RW media Does write DVD-R media Okay, this indicates it writed DVD-R. Additionally, it doesn't seem to be able to write DVD+R. Again, check for the appropriate media. Everything else looks completely valid. Have you tried to use plain growisofs in order to check that it's not a K3B problem? -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b-DVD
On Monday 20 July 2009 20:39:01 Polytropon wrote: On Mon, 20 Jul 2009 20:29:20 -0500, ajtiM lum...@gmail.com wrote: Thank you for the help. I don't know what is wrong still. I did burn DVD on FreeBSD 7.2 and before that on Linux. Now I have FreeBSD 7.2 (no ther OS) but it doesn't work. Did you always use K3B? Have you changed permissions on the device files? And finally: Are you sure that you are really using a blank DVD-R that is not defective? I'm asking because I was that clever myself to try to write to a defective media. :-) Yes, I use K3b always. I bought 10 DVD-R on Sunday. I did try to different from the box. cdrecord -scanbus 2,0,0 200) '_NEC' 'DVD_RW ND-1300A ' '1.06' Removable CD-ROM [...] cdrecord dev=2,0,0 -prcap Drive capabilities, per MMC-3 page 2A: Does write CD-R media Does write CD-RW media Does write DVD-R media Okay, this indicates it writed DVD-R. Additionally, it doesn't seem to be able to write DVD+R. Again, check for the appropriate media. DVD's which I bought are DVD-R Everything else looks completely valid. Have you tried to use plain growisofs in order to check that it's not a K3B problem? growisofs -dvd-compat -Z /dev/cd0 -J -R /home/ME/MyFiles/Pictures/Ore Executing 'mkisofs -J -R /home/ME/MyFiles/Pictures/Ore | builtin_dd of=/de v/pass4 obs=32k seek=0' 0.26% done, estimate finish Mon Jul 20 20:50:52 2009 0.52% done, estimate finish Mon Jul 20 20:50:52 2009 0.78% done, estimate finish Mon Jul 20 20:50:52 2009 /dev/pass4: Current Write Speed is 1.0x1352KBps. :-[ wr...@lba=0h failed with SK=5h/CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT]: I nvalid argument :-( media is not formatted or unsupported. :-( write failed: Invalid argument -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: K3b dosent detect either of my burners
Warren Liddell wrote: When the atapicam module is loaded, it treats ATAPI CDs like SCSI ones, so you should get names like cd0 and cd1. Can you perform an ls /dev/cd* and see if these devices exist? I haven't used a SATA recorder in my machine yet, but since the ata driver attaches to them, I see no reason they should not work with atapicam. Have you tried burning from the command line? And have you followed all the post-install instructions in k3b? (try make showinfo in the port's directory). I got /dev/cd0 /dev/cd1 I went through most instructions in the showinfo, although 1 part had me confused .. /etc/devfs.rules under '[system=10]' --- devfs.rules dose'nt exist Just create the file / section then. burning from command line works fine but is a tiresome nuisance AFAIR, k3b and most other GUI burning programs use the command line tools as backends. Since these are working, it is only a matter of settings to making k3b work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b dosent detect either of my burners
can't you simply use growisofs in command line. it's so simple. On Fri, 29 Aug 2008, Warren Liddell wrote: I have gone through the info from various sites, handbooks, email archives and yet still k3b doesnt detect neither 1 of my 2 SATA Burners .. i use FreeBSD 7.0-STABLE KDE4 AMD64. below r the 2 burners as they appear in dmesg. acd0: DVDR TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 acd1: DVDR ATAPI DVD A DH20A3S/9P56 at ata3-master SATA150 ___ 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]
K3b dosent detect either of my burners
I have gone through the info from various sites, handbooks, email archives and yet still k3b doesnt detect neither 1 of my 2 SATA Burners .. i use FreeBSD 7.0-STABLE KDE4 AMD64. below r the 2 burners as they appear in dmesg. acd0: DVDR TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 acd1: DVDR ATAPI DVD A DH20A3S/9P56 at ata3-master SATA150 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b dosent detect either of my burners
On Fri, Aug 29, 2008 at 09:58:39PM +1000, Warren Liddell wrote: I have gone through the info from various sites, handbooks, email archives and yet still k3b doesnt detect neither 1 of my 2 SATA Burners .. i use FreeBSD 7.0-STABLE KDE4 AMD64. below r the 2 burners as they appear in dmesg. acd0: DVDR TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 acd1: DVDR ATAPI DVD A DH20A3S/9P56 at ata3-master SATA150 Can you try to load the 'atapicam' module? -- Oliver PETER, email: [EMAIL PROTECTED], ICQ# 113969174 I like to con people. And I like to insult people. If you combine con insult, you get consult! -- Dogbert pgpLXvntW4PdT.pgp Description: PGP signature
Re: K3b dosent detect either of my burners
On Saturday 30 August 2008 01:46:04 Oliver Peter wrote: On Fri, Aug 29, 2008 at 09:58:39PM +1000, Warren Liddell wrote: I have gone through the info from various sites, handbooks, email archives and yet still k3b doesnt detect neither 1 of my 2 SATA Burners .. i use FreeBSD 7.0-STABLE KDE4 AMD64. below r the 2 burners as they appear in dmesg. acd0: DVDR TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 acd1: DVDR ATAPI DVD A DH20A3S/9P56 at ata3-master SATA150 Can you try to load the 'atapicam' module? Yeah i have it loaded :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b dosent detect either of my burners
Warren Liddell wrote: On Saturday 30 August 2008 01:46:04 Oliver Peter wrote: On Fri, Aug 29, 2008 at 09:58:39PM +1000, Warren Liddell wrote: I have gone through the info from various sites, handbooks, email archives and yet still k3b doesnt detect neither 1 of my 2 SATA Burners .. i use FreeBSD 7.0-STABLE KDE4 AMD64. below r the 2 burners as they appear in dmesg. acd0: DVDR TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 acd1: DVDR ATAPI DVD A DH20A3S/9P56 at ata3-master SATA150 Can you try to load the 'atapicam' module? Yeah i have it loaded :) ___ When the atapicam module is loaded, it treats ATAPI CDs like SCSI ones, so you should get names like cd0 and cd1. Can you perform an ls /dev/cd* and see if these devices exist? I haven't used a SATA recorder in my machine yet, but since the ata driver attaches to them, I see no reason they should not work with atapicam. Have you tried burning from the command line? And have you followed all the post-install instructions in k3b? (try make showinfo in the port's directory). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b dosent detect either of my burners
When the atapicam module is loaded, it treats ATAPI CDs like SCSI ones, so you should get names like cd0 and cd1. Can you perform an ls /dev/cd* and see if these devices exist? I haven't used a SATA recorder in my machine yet, but since the ata driver attaches to them, I see no reason they should not work with atapicam. Have you tried burning from the command line? And have you followed all the post-install instructions in k3b? (try make showinfo in the port's directory). I got /dev/cd0 /dev/cd1 I went through most instructions in the showinfo, although 1 part had me confused .. /etc/devfs.rules under '[system=10]' --- devfs.rules dose'nt exist burning from command line works fine but is a tiresome nuisance ___ 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]
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]
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 SNIP 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
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 SNIP 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: 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
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: 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
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
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
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
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
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 [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
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
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/user/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 TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 pcm0: HDA Codec: Realtek ALC883 pcm0: HDA Driver Revision: 20071129_0050 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: LEXAR JUMPDRIVE SECURE 3000 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: TSSTcorp CDDVDW SH-S203D SB00 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 [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/user/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 TSSTcorp CDDVDW SH-S203D/SB00 at ata2-master SATA150 pcm0: HDA Codec: Realtek ALC883 pcm0: HDA Driver Revision: 20071129_0050 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: LEXAR JUMPDRIVE SECURE 3000 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: TSSTcorp CDDVDW SH-S203D SB00 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
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 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
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]
k3b not detecting my burner
I not long got k3b compiled and running, but it comes up saying ti dosent detect i have a burner, when i got a SATA burner sitting there that has been working fine with Winblows. Whats happening an how do i fix this issue ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: k3b not detecting my burner
On Behalf Of Warren Liddell I not long got k3b compiled and running, but it comes up saying ti dosent detect i have a burner, when i got a SATA burner sitting there that has been working fine with Winblows. Whats happening an how do i fix this issue ? AFAIK, the Unix/Linux disk burner software packages only work with SCSI devices. They require a SCSI translator for ATA/IDE drives. Is there a SCSI emulation option available for your SATA drives. Bob McConnell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b not detecting my burner
Warren Liddell wrote: I not long got k3b compiled and running, but it comes up saying ti dosent detect i have a burner, when i got a SATA burner sitting there that has been working fine with Winblows. Whats happening an how do i fix this issue ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Start by reading the detailed instructions of the port: cd /usr/ports/sysutils/k3b make showinfo You are probably missing the atapicam driver: kldload atapicam Edit /boot/loader.conf and add: atapicam_load=YES so that the above setting persists. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b not detecting my burner
Start by reading the detailed instructions of the port: cd /usr/ports/sysutils/k3b make showinfo You are probably missing the atapicam driver: kldload atapicam Edit /boot/loader.conf and add: atapicam_load=YES so that the above setting persists. Yeah i got atapicam loaded, obviously missing something else .. i'll see what the port sais. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b not detecting my burner
Start by reading the detailed instructions of the port: cd /usr/ports/sysutils/k3b make showinfo You are probably missing the atapicam driver: kldload atapicam Edit /boot/loader.conf and add: atapicam_load=YES so that the above setting persists. Yeah i got atapicam loaded, obviously missing something else .. i'll see what the port sais. Also, see if you can see it from k3b running as root or not. If you can as root but not on a normal user, you'll have to give your normal user permission to access the burner's device. Dave // bridd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b not detecting my burner
Also, see if you can see it from k3b running as root or not. If you can as root but not on a normal user, you'll have to give your normal user permission to access the burner's device. Dave // bridd k3b wont run as root # 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: 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: k3b not detecting my burner
Written by Warren Liddell on 06/25/08 08:02 Also, see if you can see it from k3b running as root or not. If you can as root but not on a normal user, you'll have to give your normal user permission to access the burner's device. Dave // bridd k3b wont run as root # 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: 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] That's because root doesn't have the magic cookie to authenticate to the display initiated by your user. Try sudo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b not detecting my burner
Warren Liddell wrote: Also, see if you can see it from k3b running as root or not. If you can as root but not on a normal user, you'll have to give your normal user permission to access the burner's device. Dave // bridd k3b wont run as root # 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: 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] k3b will issue a warning about being run as root, but it will certainly run as root. As the non-root user, in an xterm window, type: xhost localhost Then su to root and run k3b. Running as root isn't your problem, but if you want to eliminate permission problems on the burning device(s), you can try it that way. Tim Kellers CPE/NJIT ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b not detecting my burner
Warren Liddell wrote: Also, see if you can see it from k3b running as root or not. If you can as root but not on a normal user, you'll have to give your normal user permission to access the burner's device. Dave // bridd k3b wont run as root # k3b As a user a GUI app like k3b can be run as root by doing kdesu k3b. It will pop up a box asking for root's credentials. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Non aligned DMA transfer errors with k3b
Suddenly today all my attempts to burn DVDs with k3b result in a continuous stream of the following error messages. May 25 18:04:40 kestrel kernel: ata1: FAILURE - non aligned DMA transfer attempted May 25 18:04:40 kestrel kernel: acd0: setting up DMA failed Quiting k3b doesn't stop the flood of errors, reboots hang and the only solution is to hit the reset switch. I'm running 7.0 RELEASE and if I reboot into my 6.3 partition k3b works just fine, confirming that it's not a media or hardware fault. I've also replaced the DVD writer but I still get the problem with 7.0. I can burn the same data to the same DVD with growisofs with no problem which suggests that the problem lies with k3b so this got me wondering if it was related to the massive portupgrade I did yesterday (affecting 156 ports) but that seems unlikely because when portupgrade finished last night I rebooted and burnt that day's backup to DVD+RW without problem. This morning I burnt 3 DVD+Rs without problem, then about an hour later the problem suddenly appeared when I started to burn another DVD+RW, and there'd been absolutely no software or hardware changes since the previous successful run. Although I don't think upgrading the ports is responsible I've tried downgrading k3b from 1.0.4_1 to 1.0.4 but that had no effect, nor did downgrading dvd+rw-tools-7.1 to 7.0. I don't think any of the other upgraded ports would have been significant. Turning off DMA by setting hw.ata.ata_dma and hw.ata.atapi_dma to zero stops the errors but with a big performance hit so that's not an option for a permanent fix. I've now run out of ideas for what to try next so any suggestions would be welcome. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
k3b problem with DVD
Hello, For long I use k3b with great satisfaction. On a recent new system however it has serious problem with handling DVD-s. While it works with CD-s, as soon as DVD disc is placed into the drive it starts to emit error messages[1]. From this on (and even after stopping/killing it ) the system displays an extreme high interrupt activity (~50%) while CPU usage remains low. Ejecting the disc has no effect on k3b it no longer works even with CD-s. If the DVD is put before k3b start, k3b does not start for a long time (~ 15 minutes), then reports no proble with system configuration, show dvd device info on console, but can't handle the DVD disc. Mounting of DVDs by hal/thunar-volman/dbus/policykit works. I can play the dvd with mplayer, too. My system is: FreeBSD 7.0-RELEASE #5 k3b-1.0.4_1 The PIO device's firmware was upgraded to he latest with no effect. Excerpt from dmesg: acd0: DVDR PIONEER DVD-RW DVR-215D/1.18 at ata4-master SATA150 pcm0: HDA Codec: Realtek ALC883 pcm0: HDA Driver Revision: 20071129_0050 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 SMP: AP CPU #1 Launched! cd0 at ata3 bus 0 target 0 lun 0 cd0: PIONEER DVD-RW DVR-215D 1.18 Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Any suggestion to solve this is highly appreciated! Thanks! Zsolt P.s: Please CC to me, as I am not on the list. Thanks! [1] ... k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi, audio-stdin, burnfree k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version = 1.11a02, using burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version = 1.11a31, support for Just Link via burnfree driveroption (BSDDeviceScan) number of matches 18 (BSDDeviceScan) periph: pass0 (BSDDeviceScan) periph: cd0 (BSDDeviceScan) add device /dev/cd0:4:0:0 (/dev/pass0) (K3bDevice::Device) /dev/cd0: init() (K3bDevice::openDevice) open device /dev/pass0 succeeded. (K3bDevice::openDevice) open device /dev/pass0 succeeded. (K3bDevice::ScsiCommand) transport command 12, length: 6 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: CD Mastering (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: CD Track At Once (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: CD-RW Media Write Support (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: DVD Read (MMC5) (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: DVD+R (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: DVD+RW (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: DVD+R Double Layer (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: DVD-R/-RW Write (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: Rigid Restricted Overwrite (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::Device) /dev/cd0 feature: Layer Jump Recording (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::ScsiCommand) transport command 46, length: 10 (K3bDevice::openDevice) open device /dev/pass0 succeeded. (K3bDevice::openDevice) open device /dev/pass0 succeeded. (K3bDevice::ScsiCommand) transport command 5a, length: 10 (K3bDevice::ScsiCommand) transport command 5a, length: 10 (K3bDevice::Device) /dev/cd0: dataLen: 60 (K3bDevice::Device) /dev/cd0: checking for TAO (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::Device) /dev/cd0: checking for SAO (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::Device) /dev/cd0: checking for SAO_R96P (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::Device) /dev/cd0: checking for SAO_R96R (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::Device) /dev/cd0: checking for RAW_R16 (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::Device) /dev/cd0: checking for RAW_R96P (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::Device) /dev/cd0: checking for RAW_R96R (K3bDevice::ScsiCommand) transport command 55, length: 10 (K3bDevice::ScsiCommand) transport command 5a, length: 10 (K3bDevice::ScsiCommand) transport command 5a, length: 10 (K3bDevice::ScsiCommand) transport command 0, length: 6 (K3bDevice::ScsiCommand) transport command 46
k3b not recognizing ATAPI DVD A DH20A1S UX11 write capability
Hi I installed k3b-1.0.4/cdrtools-2.01_6/dvd+rw-tools-7.0 on an amd64 6.3machine running GENERIC but k3b gives the following error: 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 creation. k3b: SOLUTION: Any hints on how I can fix this? It worked fine under Linux and OpenBSD (which I used to burn the 6.3 CDs) Thanks a lot Bob Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.3-RELEASE #0: Wed Jan 16 01:43:02 UTC 2008 root at palmer.cse.buffalo.edu http://lists.freebsd.org/mailman/listinfo/freebsd-acpi:/usr/obj/usr/src/sys/SMP ACPI APIC Table: RS485 AWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2299.75-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb1 Stepping = 1 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch Cores per package: 2 real memory = 1039007744 (990 MB) avail memory = 989507584 (943 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 01:41:13) acpi0: RS485 AWRDACPI on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21 ACPI-0438: *** Error: Looking up [LNKC] in namespace, AE_NOT_FOUND SearchNode 0xffc8ebc0 StartNode 0xffc8ebc0 ReturnNode 0 ACPI-0438: *** Error: Looking up [LNKD] in namespace, AE_NOT_FOUND SearchNode 0xffc8ea40 StartNode 0xffc8ea40 ReturnNode 0 ACPI-0438: *** Error: Looking up [LNKA] in namespace, AE_NOT_FOUND SearchNode 0xffc8e8c0 StartNode 0xffc8e8c0 ReturnNode 0 ACPI-0438: *** Error: Looking up [LNKB] in namespace, AE_NOT_FOUND SearchNode 0xffc8e740 StartNode 0xffc8e740 ReturnNode 0 ACPI-0438: *** Error: Looking up [LNKC] in namespace, AE_NOT_FOUND SearchNode 0xffcd29c0 StartNode 0xffcd29c0 ReturnNode 0 ACPI-0438: *** Error: Looking up [LNKD] in namespace, AE_NOT_FOUND SearchNode 0xffcd2840 StartNode 0xffcd2840 ReturnNode 0 ACPI-0438: *** Error: Looking up [LNKA] in namespace, AE_NOT_FOUND SearchNode 0xffcd26c0 StartNode 0xffcd26c0 ReturnNode 0 acpi0: Power Button (fixed) ACPI-0381: *** Error: Looking up [_PCT] in namespace, AE_ALREADY_EXISTS ACPI-1304: *** Error: Method execution failed [\\_SB_.MEM_._CRS] (Node 0xffc95a00), AE_ALREADY_EXISTS ACPI-0239: *** Error: Method execution failed [\\_SB_.MEM_._CRS] (Node 0xffc95a00), AE_ALREADY_EXISTS can't fetch resources for \\_SB_.MEM_ - AE_ALREADY_EXISTS Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 32-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 5.0 (no driver attached) atapci0: ATI IXP400 SATA150 controller port 0xfe00-0xfe07,0xfd00-0xfd03,0xfc00-0xfc07,0xfb00-0xfb03,0xfa00-0xfa0f mem 0xfe02f000-0xfe02f1ff irq 23 at device 17.0 on pci0 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 atapci1: ATI IXP400 SATA150 controller port 0xf900-0xf907,0xf800-0xf803,0xf700-0xf707,0xf600-0xf603,0xf500-0xf50f mem 0xfe02e000-0xfe02e1ff irq 22 at device 18.0 on pci0 ata4: ATA channel 0 on atapci1 ata5: ATA channel 1 on atapci1 ohci0: ATI SB400 USB Controller mem 0xfe02d000-0xfe02dfff irq 19 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: ATI SB400 USB Controller on ohci0 usb0: USB revision 1.0 uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: ATI SB400 USB Controller mem 0xfe02c000-0xfe02cfff irq 19 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: ATI SB400 USB Controller on ohci1 usb1: USB revision 1.0 uhub1: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered
Re: k3b not recognizing ATAPI DVD A DH20A1S UX11 write capability
On Saturday 26 January 2008 16:41:55 Bob Bing wrote: I installed k3b-1.0.4/cdrtools-2.01_6/dvd+rw-tools-7.0 on an amd64 6.3machine running GENERIC but k3b gives the following error: 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 creation. k3b: SOLUTION: Any hints on how I can fix this? It worked fine under Linux and OpenBSD (which I used to burn the 6.3 CDs) You need to emulate it as a SCSI device: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html#ATAPICAM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
ajtiM wrote: On Sunday 25 November 2007 21:58:03 you wrote: ajtiM wrote: Hi! I am new with FreeBSD. I installed one day ago 7.0 beta3 and I try to learn and setup the system. When I start K3b (KDE) I got a message: No CD/DVD writer found. 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 creation. I tired as user and as root but resul is the same. BTW: under Linux I didn't have a problem Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You have not done your homework. Probably the following would be enough [pedja@ /usr/home/Pedja]$ more /boot/loader.conf atapicam_load=YES hw.ata.ata_dma=1 hw.ata.atapi_dma=1 You also need to add the following into your /etc/devfs.conf file # Allow members of the group operator to mount CD-ROMs. perm /dev/acd0 0666 perm /dev/cd00666 # Commonly used by many ports link cd0 cdrom link cd0 dvd link cd0 rdvd link acd0 cdrom link acd0 dvd link acd0 rdvd # Misc other devices permcdrom 0666 permdvd 0666 permrdvd0666 permxpt00666 permpass0 0666 I am not sure if you need HAL as mine is ON on this computer on which K3b works flawlessly. You will have to read handbook and the following is useful http://www.freebsd.org/gnome/. BTW: I really gets annoyed when people say by the way it works in Linux, Windows, Solaris or whatever. What is that suppose to mean? That is nothing wrong with hardware :) I realized that. I hope you saw my apology. I do know however why you can not use it as a user. You have to mount the disk on the file system that belongs to you not the root. So edit your /etc/fstab file as this #These are my options /dev/cd0 /usr/home/Pedja/mnt/cdrom cd9660 rw, noauto 0 0 /dev/acd0/usr/home/Pedja/mnt/cdrom cd9660 rw, noauto 0 0 and you should be good too go. That was exactly what I meant by saying that I do not know if you need HAL. You do not need HAL but you need to edit your /etc/fstab. Cheers, Predrag Thank you...I did but as user I couldn't use K3b but as root works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
K3b
Hi! I am new with FreeBSD. I installed one day ago 7.0 beta3 and I try to learn and setup the system. When I start K3b (KDE) I got a message: No CD/DVD writer found. 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 creation. I tired as user and as root but resul is the same. BTW: under Linux I didn't have a problem Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
On 26-Nov-07, at 5:07 AM, ajtiM wrote: Hi! I am new with FreeBSD. I installed one day ago 7.0 beta3 and I try to learn and setup the system. When I start K3b (KDE) I got a message: No CD/DVD writer found. 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 creation. I tired as user and as root but resul is the same. BTW: under Linux I didn't have a problem Check section '18.6.9 Using the ATAPI/CAM Driver' on http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating- cds.html regards, shantanoo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
Hi! I am new with FreeBSD. I installed one day ago 7.0 beta3 and I try to learn and setup the system. When I start K3b (KDE) I got a message: No CD/DVD writer found. 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 creation. I tired as user and as root but resul is the same. BTW: under Linux I didn't have a problem Thanks in advance. Response: Assuming some things still work as they did with the 6.X releases (probably a dangerous assumption) you need to enable the ATAPI driver. See here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html#ATAPICAM David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
ajtiM wrote: Hi! I am new with FreeBSD. I installed one day ago 7.0 beta3 and I try to learn and setup the system. When I start K3b (KDE) I got a message: No CD/DVD writer found. 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 creation. I tired as user and as root but resul is the same. BTW: under Linux I didn't have a problem Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You have not done your homework. Probably the following would be enough [pedja@ /usr/home/Pedja]$ more /boot/loader.conf atapicam_load=YES hw.ata.ata_dma=1 hw.ata.atapi_dma=1 You also need to add the following into your /etc/devfs.conf file # Allow members of the group operator to mount CD-ROMs. perm /dev/acd0 0666 perm /dev/cd00666 # Commonly used by many ports link cd0 cdrom link cd0 dvd link cd0 rdvd link acd0 cdrom link acd0 dvd link acd0 rdvd # Misc other devices permcdrom 0666 permdvd 0666 permrdvd0666 permxpt00666 permpass0 0666 I am not sure if you need HAL as mine is ON on this computer on which K3b works flawlessly. You will have to read handbook and the following is useful http://www.freebsd.org/gnome/. BTW: I really gets annoyed when people say by the way it works in Linux, Windows, Solaris or whatever. What is that suppose to mean? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
On Sunday 25 November 2007 05:37:46 pm ajtiM wrote: Hi! I am new with FreeBSD. I installed one day ago 7.0 beta3 and I try to learn and setup the system. When I start K3b (KDE) I got a message: No CD/DVD writer found. 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 creation. cd /usr/ports/sysutils/k3b make showinfo David -- This message is larva-tested, pupa-approved. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
[EMAIL PROTECTED] wrote: BTW: I really gets annoyed when people say by the way it works in Linux, Windows, Solaris or whatever. What is that suppose to mean? When someone describes a problem getting a certain hardware setup to work as desired in FreeBSD, and reports that it works in some other OS, I would take it to mean that one need not suggest testing the hardware, since it is already known to work properly in the other environment. For someone who happens to be familiar with whatever other OS was mentioned, it may also serve as an example of the sort of operation that the poster was attempting to achieve in FreeBSD. I realized after replaying to the mail! I apologize to the sender of the original message for the tone of my post. Cheers, Predrag ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: K3b
BTW: I really gets annoyed when people say by the way it works in Linux, Windows, Solaris or whatever. What is that suppose to mean? When someone describes a problem getting a certain hardware setup to work as desired in FreeBSD, and reports that it works in some other OS, I would take it to mean that one need not suggest testing the hardware, since it is already known to work properly in the other environment. For someone who happens to be familiar with whatever other OS was mentioned, it may also serve as an example of the sort of operation that the poster was attempting to achieve in FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
.rar files on K3b
Dear Sirs I've downloaded a .rar audio file other day but I don't get to fix it on K3b. My machine is amd64 and runs FreeBSD-6.1-Release amd64 Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: .rar files on K3b
On Aug 21, 2007, at 9:23 AMAug 21, 2007, [EMAIL PROTECTED] wrote: Dear Sirs I've downloaded a .rar audio file other day but I don't get to fix it on K3b. My machine is amd64 and runs FreeBSD-6.1-Release amd64 RAR is a method of compression, not an audio format. Try installing the rar archive utility from /usr/ports/archivers/rar and using unrar to decompress the file in question. HTH - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
k3b installation problem - make fails
Hi all, I installed all the libraries mentioned on k3b.org, including mandatory and optional (actually, excluding two of the optional libraries - libmusicbrainz and hal). I used the latest versions of all the libraries, and k3b as well. FreeBSD version 6.1. ./configure runs without error messages. But when I run make, it fails with the error message as follows: make all-recursive Making all in doc Making all in libk3bdevice /usr/local/bin/bash ../libtool --silent --mode=link --tag=CXX g++ -Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2 -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -fpermissive-o libk3bdevice.la -rpath /usr/local/lib -L/usr/local/lib -L/usr/X11R6/lib -version-info 2:1:0 -no-undefined k3bdevice.lo k3bdevice_mmc.lo k3bscsicommand.lo k3btrack.lo k3btoc.lo k3bdevicemanager.lo k3bmsf.lo k3bdiskinfo.lo k3bdeviceglobals.lo k3bcrc.lo k3bcdtext.lo -lkio -lcam -lm -L/usr/local/lib -L/usr/X11R6/lib libtool: link: cannot find the library `' *** Error code 1 Stop in... The name of the library, which cannot be found, appears empty in the message. Maybe, I should try some configuration options? If someone here faced a similar problem and solved it, or just know how to approach the problem, their advice would be highly appreciated. I can provide all the results shown on the screen during configure and make, if it is useful for targeting the problem. Many thanks to all in advance. Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b installation problem - make fails
On Thu, 20 Jul 2006 00:52:16 -0700 Andriy Babiy [EMAIL PROTECTED] wrote: Hi all, I installed all the libraries mentioned on k3b.org, including mandatory and optional (actually, excluding two of the optional libraries - libmusicbrainz and hal). I used the latest versions of all the libraries, and k3b as well. FreeBSD version 6.1. ./configure runs without error messages. But when I run make, it fails with the error message as follows: make all-recursive Making all in doc Making all in libk3bdevice /usr/local/bin/bash ../libtool --silent --mode=link --tag=CXX g++ -Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2 -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -fpermissive-o libk3bdevice.la -rpath /usr/local/lib -L/usr/local/lib -L/usr/X11R6/lib -version-info 2:1:0 -no-undefined k3bdevice.lo k3bdevice_mmc.lo k3bscsicommand.lo k3btrack.lo k3btoc.lo k3bdevicemanager.lo k3bmsf.lo k3bdiskinfo.lo k3bdeviceglobals.lo k3bcrc.lo k3bcdtext.lo -lkio -lcam -lm -L/usr/local/lib -L/usr/X11R6/lib libtool: link: cannot find the library `' *** Error code 1 Stop in... The name of the library, which cannot be found, appears empty in the message. Maybe, I should try some configuration options? If someone here faced a similar problem and solved it, Methinks someone did, since it's in the ports collection (at /usr/ports/sysutils/k3b). or just know how to approach the problem, their advice would be highly appreciated. Is there a reason you're compiling it manually? If so, it may be worth your while examining how it's done in ports and applying a similar approach. I can provide all the results shown on the screen during configure and make, if it is useful for targeting the problem. Many thanks to all in advance. Andriy -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b package
The port works just fine. I already installed it. I was only going to use packages because I was in a hurry. I did notice that it depends on libdvdcss, as does kaffeine. I couldn't find either of them in any of the subdirectories under pub/FreeBSD/ports/i386 on any of the mirrors that I checked, including several non-US ones. I used an ftp client to double-check, so I'm not just relying on the output of 'pkg_add -r'. Given that they rely on libdvdcss, maybe they aren't on the server for legal reasons. (DMCA, etc.) - Karl -Original Message- From: Lowell Gilbert [EMAIL PROTECTED] Sent: Jul 10, 2006 1:41 PM To: Karl Hammerschmidt [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: k3b package Karl Hammerschmidt [EMAIL PROTECTED] writes: I was planning to install k3b from a package, but I wasn't able to find it in packages-6-stable or packages-6.0-release on any of the ftp mirrors. Am I missing something? Well, I just built it successfully, and the port itself isn't marked for avoiding packaging, so I don't see offhand why you can't find a package. I guess you'll need to use the port for now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b package
Karl Hammerschmidt [EMAIL PROTECTED] writes: I was planning to install k3b from a package, but I wasn't able to find it in packages-6-stable or packages-6.0-release on any of the ftp mirrors. Am I missing something? Well, I just built it successfully, and the port itself isn't marked for avoiding packaging, so I don't see offhand why you can't find a package. I guess you'll need to use the port for now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b package
On 7/8/06, Karl Hammerschmidt [EMAIL PROTECTED] wrote: Hi, I was planning to install k3b from a package, but I wasn't able to find it in packages-6-stable or packages-6.0-release on any of the ftp mirrors. Am I missing something? - Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Are you/can you CVSUP the ports tree, and then try to install it from there? Is it not showing up in the ports tree when you do that? Is it showing up but the package not downloading? I recently installed this also without any mishaps. -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
k3b package
Hi, I was planning to install k3b from a package, but I wasn't able to find it in packages-6-stable or packages-6.0-release on any of the ftp mirrors. Am I missing something? - Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
k3b
Hi Does anyone know of an app similar to k3b for gnome. I know i can run it from gnome but it keeps crashing on me so id like some for gnome. Had a look around gnomefiles but couldnt find anything like it. Thanks Eoghan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b
On Wed, 19 Apr 2006 19:09:45 +0100 eoghan [EMAIL PROTECTED] wrote: Does anyone know of an app similar to k3b for gnome. I know i can run it from gnome but it keeps crashing on me so id like some for gnome. Had a look around gnomefiles but couldnt find anything like it. /usr/ports/sysutils/gnomebaker -- grtjs, albi gpg-key: lynx -dump http://scii.nl/~albi/gpg.asc | gpg --import ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b
None that can do as much as k3b. But gnomebaker can do the basic job or nautilus cd burner. On Wed, 2006-04-19 at 19:09 +0100, eoghan wrote: Hi Does anyone know of an app similar to k3b for gnome. I know i can run it from gnome but it keeps crashing on me so id like some for gnome. Had a look around gnomefiles but couldnt find anything like it. Thanks Eoghan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dev Tugnait [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: k3b
Dev Tugnait wrote: None that can do as much as k3b. But gnomebaker can do the basic job or nautilus cd burner. Ok thanks will give that a go. Eoghan On Wed, 2006-04-19 at 19:09 +0100, eoghan wrote: Hi Does anyone know of an app similar to k3b for gnome. I know i can run it from gnome but it keeps crashing on me so id like some for gnome. Had a look around gnomefiles but couldnt find anything like it. Thanks Eoghan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b
This : /usr/ports/sysutils/graveman/ is nice too. On 4/20/06, eoghan [EMAIL PROTECTED] wrote: Hi Does anyone know of an app similar to k3b for gnome. I know i can run it from gnome but it keeps crashing on me so id like some for gnome. Had a look around gnomefiles but couldnt find anything like it. Thanks Eoghan ___ 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: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Sorry, I neglected to remove your name. That was written by Andrea Venturoli, whose name appears after yours. On Saturday 25 March 2006 15:50, Duane Whitty wrote: Oliver Iberien wrote: On Saturday 25 March 2006 11:46, Andrea Venturoli wrote: Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. My Yamaha burner is still detected as a read-only device. bye Thanks av. Hmm, I don't remember writing this at all... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Oliver Iberien wrote: There is a thread here: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021958.html of someone with a scsi cd-r/w that was giving the same errors. The thread goes on to post some kind of fix to a flac decoder: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021969.html ...but I don't understand how this is related or how it is to be implemented. I don't know whether this is related either. However it mentions a build problem, which I haven't met. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. I believe you may also need in defs.conf perm xpt0 0666 Did that, same situation. My Yamaha burner is still detected as a read-only device. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
On Saturday 25 March 2006 11:46, Andrea Venturoli wrote: Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. My Yamaha burner is still detected as a read-only device. bye Thanks av. There is a thread here: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021958.html of someone with a scsi cd-r/w that was giving the same errors. The thread goes on to post some kind of fix to a flac decoder: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021969.html ...but I don't understand how this is related or how it is to be implemented. I have found a number of postings of similar problems with k3b and scsi drives dating from after mid-2004, which is when it started happening to me, but none gives a fix. http://linux.derkeiler.com/Mailing-Lists/SuSE/2005-03/1489.html http://72.14.203.104/search?q=cache:wOJpu0m4BcwJ:k3b.plainblack.com/feedback%3Ffunc%3Dview%26wid%3D29%26forumId%3D1000%26forumOp%3DviewThread%26forumPostId%3D100898+k3b+%22mode+sense%22hl=engl=usct=clnkcd=1ie=UTF-8 http://www.linuxhardware.de/deutsch/dcoulh/news_38206.html http://linuxfromscratch.org/pipermail/blfs-support/2004-June/050551.html http://72.14.203.104/search?q=cache:Dh1vQLiRy40J:bbs.cse.yzu.edu.tw/show.php%3Ftype%3Dpost%26board%3Dbsd-ports%26pageno%3D15+k3b+%22mode+sense%22hl=engl=usct=clnkcd=6ie=UTF-8 http://lurker.oltrelinux.com/message/20040211.213612.0308c619.en.html Oliver k3b on FreeBSD 6.0 incorrectly identifies my SCSI CD-R/W as read-only. It reports mode sense failure, which, Plextor tells me, can be a sign of a problem with the drive or the media. I've appended this part of the output at the bottom. However, cdrecord is able correctly to query the drive. Here is that output: Cdrecord-Clone 2.01 (i386-unknown-freebsd6.0) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 0 = CD-DA scsidev: '0,0' scsibus: 0 target: 0 lun: 0 Using libscg version 'schily-0.8'. SCSI buffer size: 64512 atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC Vendor_info : 'PLEXTOR ' Identifikation : 'CD-R PX-W4012S' Revision : '1.01' Device seems to be: Generic mmc CD-RW. Current: 0x0009 Profile: 0x0008 Profile: 0x0009 (current) Profile: 0x000A Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE VARIREC FORCESPEED SINGLESESSION HIDECDR Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 2394336 = 2338 KB Drive DMA Speed: 13933 kB/s 79x CD 10x DVD FIFO size : 4194304 = 4096 KB This looks as if the information is there for the asking, but I am no SCSI expert. It went on to burn without a hitch. k3b worked with this drive when I used SuSE 9.1, and when I experimentally put in the old drive that had SuSE on it with its old version of k3b, it identified the drive without problems. Any clues leading towards getting k3b working would be much appreciated it. Thanks, Oliver k3b output (extract): k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: modeSense 0x05 failed! k3b: (K3bDevice::Device) /dev/cd0: Cannot check write modes. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: read mode page 2A failed! k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Oliver Iberien wrote: On Saturday 25 March 2006 11:46, Andrea Venturoli wrote: Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. My Yamaha burner is still detected as a read-only device. bye Thanks av. Hmm, I don't remember writing this at all... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
k3b incorrectly identifies scsi r/w drive as read-only -- how to change?
I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. In Setup Devices there is no way to remove a device from the readonly heading and place it under writer drives, and none of the options except for the cdrao editor are editable. Attempting to change the driver crashes the program. k3b must be reading this from somewhere, but where? The drive is r,w is fstab. Thanks, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- how to change?
On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. In Setup Devices there is no way to remove a device from the readonly heading and place it under writer drives, and none of the options except for the cdrao editor are editable. Attempting to change the driver crashes the program. k3b must be reading this from somewhere, but where? The drive is r,w is fstab. Thanks, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I don't have access to my laptop (where I recently dealt with this), but /etc/devfs.conf (i think) has places where you can set the permission to devices. I believe I did 0666 (read/write to all) for acd0, cdrom0, pass0, and perhaps 1 other. After that (and manually setting perms to /dev/list) I was able to use k3b without being root. Hope this helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- how to change?
On Friday 24 March 2006 12:12, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. In Setup Devices there is no way to remove a device from the readonly heading and place it under writer drives, and none of the options except for the cdrao editor are editable. Attempting to change the driver crashes the program. k3b must be reading this from somewhere, but where? The drive is r,w is fstab. I don't have access to my laptop (where I recently dealt with this), but /etc/devfs.conf (i think) has places where you can set the permission to devices. I believe I did 0666 (read/write to all) for acd0, cdrom0, pass0, and perhaps 1 other. After that (and manually setting perms to /dev/list) I was able to use k3b without being root. I had done that. I can access the drive, but it is still not being correctly recognized as a writer. Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- how to change?
On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: On Friday 24 March 2006 12:12, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. In Setup Devices there is no way to remove a device from the readonly heading and place it under writer drives, and none of the options except for the cdrao editor are editable. Attempting to change the driver crashes the program. k3b must be reading this from somewhere, but where? The drive is r,w is fstab. I don't have access to my laptop (where I recently dealt with this), but /etc/devfs.conf (i think) has places where you can set the permission to devices. I believe I did 0666 (read/write to all) for acd0, cdrom0, pass0, and perhaps 1 other. After that (and manually setting perms to /dev/list) I was able to use k3b without being root. I had done that. I can access the drive, but it is still not being correctly recognized as a writer. Oliver What happens when you run k3b as root (just to test) Also, what are the permissions on (assuming the writer is the first cd device) /dev/cd0 /dev/acd0 /dev/pass0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
On Friday 24 March 2006 12:29, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: On Friday 24 March 2006 12:12, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. [snip] [snip] but /etc/devfs.conf (i think) has places where you can set the permission to devices. I believe I did 0666 (read/write to all) for acd0, cdrom0,... pass0, [snip] I had done that. I can access the drive, but it is still not being correctly recognized as a writer. [snip] What happens when you run k3b as root (just to test) Also, what are the permissions on (assuming the writer is the first cd device) /dev/cd0 /dev/acd0 /dev/pass0 From /etc/devfs.conf: own acd0root:wheel own cd0 root:wheel own pass0 root:wheel permpass0 0666 permacd 0666 permcd0 0666 perm/cdrom 0666 perm/cdrom1 0666 own /cdrom 0666 own /cdrom1 0666 k3b run as root fails though not being about to connect to X. Starting up k3b with sudo gives a bouquet of k3b errors, one of which is MODE SENSE FAILS: k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: modeSense 0x05 failed! k3b: (K3bDevice::Device) /dev/cd0: Cannot check write modes. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: read mode page 2A failed! k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: modeSense 0x05 failed! k3b: (K3bDevice::Device) /dev/cd0: Cannot check write modes. Would anyone have an idea how to fix this? Oliver Whole k3b startup follows: $ sudo k3b Password: ERROR: Communication problem with k3b, it probably crashed. $ k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version = 1.11a02, using burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version = 1.11a31, support for Just Link via burnfree driveroption k3b: (BSDDeviceScan) number of matches 8 k3b: (BSDDeviceScan) add device /dev/cd0:0:0:0 k3b: (K3bDevice::Device) /dev/cd0: init() k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::ScsiCommand) transport command 12, length: 6 k3b: (K3bDevice::ScsiCommand) transport command 46, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:GET CONFIGURATION (46) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b
