Re: Adding my CDRW device to k3b
On Friday 22 April 2005 04:21, Michael Nottebrock wrote: I recently discovered another problem with k3b: Try to burn a 5.4-RC3 iso with it. Booting off it wouldn't work, and after pulling out a modest amount of hair I mounted the CD, and yes, there was one single file called blah.iso on the CD :) And you're sure you used the Tools/CD/Burn CD Image menu to do that? (as Frank also hinted) Erm, oops, sorry said the crashing pilot :) Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding my CDRW device to k3b
On Apr 20 06:54PM, Michael Collette wrote: Before getting into the CDRW stuff, why K3B wouldn't run. I would bet that you're using an X Display Manager, like kdm, gdm, or even xdm. You can't just su into root and run stuff like that. You need to fully log out, then log into whatever wm you use as root. When you do that, k3b should come up just fine. I log into my system as root then launch kdm then log in as myself. What do you recommend I do, log into kdm as root? Is there any way to get k3b running under a normal user account? But it still probably won't pick up the devices :( Oh, if life were simpler in FreeBSD land. First off, check that the following lines exist in your kernel config... device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atapicam Especially important is that last one, as it ain't in the GENERIC kernel last I checked. That's the magical beast that'll get it all playing. Get that in there and recompile your kernel. You might get away with kldload cam, but I honestly don't know if that's the same thing. I was missing a few of the above items: sa, ses, and ch. My new kernel is compiling now. Then you'll want to get permissions and links all setup proper every time you boot in. Here you'll need to get /etc/devfs.conf all tweaked up proper for normal users. # /etc/devfs.conf permacd00666 linkacd0cdrom linkacd0dvd permpass0 0666 permcd0 0666 permxpt00666 You may want to instead link cd0 to cdrom and dvd, but these settings seem to work for me here. Took care of this as well. I don't recall seeing anything about editing devfs.conf in the handbook. Perhaps I overlooked it. Make sure your /etc/rc.conf has the line... devd_enable=YES This is default in newer versions of FreeBSD. Doesn't hurt to toss it in there thought. All set now with this as well. The k3b port will have installed cdrdao, but it wouldn't have tweaked on it's permissions. This one you'll most likely want to make it suid root. Definitely not something you'd want to do on a production server box just out of paranoia, but reasonably safe on a desktop. # As root cd /usr/local/bin chmod u+s cdrdao I stumbled upon these while researching my problem. Double checked the above and it looks good. After jumping through all those fun loving hoops, it should work shweet. In fact, k3b will automatically add your CD into the device list. If k3b didn't put it in there for you, that's a clue that something isn't right. I'm waiting for my new shiny kernel and we will see what happens! Thanks so much for your help Michael! I look forward to making some illegitimate music CDs and driving around dodging the law! :D Good luck! On 4/14/05, Justin R. Pessa [EMAIL PROTECTED] wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. Here is the output of dmesg. The system sees the device fine, I folloed the handbook instructions for CDRW setup. acd0: CDRW TDK CDRW241040X/6.34 at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: TDK CDRW241040X 6.34 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [1 x 2048 byte records] $ ls -al /dev/acd0 crw-rw-rw- 1 root jstn4, 13 Apr 7 22:14 /dev/acd0 I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Any ideas? Thanks! ._ | Justin R. Pessa | http://jstn.sdf1.org -- When you come to a fork in the roadTake it - Yogi Berra Warm Regards, - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' pgpQeP5oC7gks.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
Justin R. Pessa wrote: On Apr 20 06:54PM, Michael Collette wrote: Before getting into the CDRW stuff, why K3B wouldn't run. I would bet that you're using an X Display Manager, like kdm, gdm, or even xdm. You can't just su into root and run stuff like that. You need to fully log out, then log into whatever wm you use as root. When you do that, k3b should come up just fine. I log into my system as root then launch kdm then log in as myself. What do you recommend I do, log into kdm as root? Is there any way to get k3b running under a normal user account? Try making the dvd+rw-tools port install setuid-root. I don't believe that K3B needs to be root, just the underlying software it calls to actually burn the image -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding my CDRW device to k3b
Seems like the suggestions below worked like a charm! I'm burning a CD as we speak, thanks a lot! On Apr 20 05 06:54PM, Michael Collette wrote: Before getting into the CDRW stuff, why K3B wouldn't run. I would bet that you're using an X Display Manager, like kdm, gdm, or even xdm. You can't just su into root and run stuff like that. You need to fully log out, then log into whatever wm you use as root. When you do that, k3b should come up just fine. But it still probably won't pick up the devices :( Oh, if life were simpler in FreeBSD land. First off, check that the following lines exist in your kernel config... device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atapicam Especially important is that last one, as it ain't in the GENERIC kernel last I checked. That's the magical beast that'll get it all playing. Get that in there and recompile your kernel. You might get away with kldload cam, but I honestly don't know if that's the same thing. Then you'll want to get permissions and links all setup proper every time you boot in. Here you'll need to get /etc/devfs.conf all tweaked up proper for normal users. # /etc/devfs.conf permacd00666 linkacd0cdrom linkacd0dvd permpass0 0666 permcd0 0666 permxpt00666 You may want to instead link cd0 to cdrom and dvd, but these settings seem to work for me here. Make sure your /etc/rc.conf has the line... devd_enable=YES This is default in newer versions of FreeBSD. Doesn't hurt to toss it in there thought. The k3b port will have installed cdrdao, but it wouldn't have tweaked on it's permissions. This one you'll most likely want to make it suid root. Definitely not something you'd want to do on a production server box just out of paranoia, but reasonably safe on a desktop. # As root cd /usr/local/bin chmod u+s cdrdao After jumping through all those fun loving hoops, it should work shweet. In fact, k3b will automatically add your CD into the device list. If k3b didn't put it in there for you, that's a clue that something isn't right. Good luck! On 4/14/05, Justin R. Pessa [EMAIL PROTECTED] wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. Here is the output of dmesg. The system sees the device fine, I folloed the handbook instructions for CDRW setup. acd0: CDRW TDK CDRW241040X/6.34 at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: TDK CDRW241040X 6.34 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [1 x 2048 byte records] $ ls -al /dev/acd0 crw-rw-rw- 1 root jstn4, 13 Apr 7 22:14 /dev/acd0 I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Any ideas? Thanks! ._ | Justin R. Pessa | http://jstn.sdf1.org -- When you come to a fork in the roadTake it - Yogi Berra - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' pgpLiqaWKZqiw.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
OK, let it be clear that the cdrdao thing is a problem of the software itself (as in: not needed to be root if done right), but certainly for us with devfs and proper permissions and group membership this can be solved without any problems or upstream changes. I can burn CDs alright but the GUI throws the warning nonetheless (simply because of cdrdao not being suid root? -- suid root shouldn't be needed at all). I recently discovered another problem with k3b: Try to burn a 5.4-RC3 iso with it. Booting off it wouldn't work, and after pulling out a modest amount of hair I mounted the CD, and yes, there was one single file called blah.iso on the CD :) [CC'd to ports@ as a FYI so that maintainer will see this as will others who might be interested. There really are a few problems with this port IMHO] Dan On Friday 22 April 2005 00:25, Justin R. Pessa wrote: Seems like the suggestions below worked like a charm! I'm burning a CD as we speak, thanks a lot! On Apr 20 05 06:54PM, Michael Collette wrote: Before getting into the CDRW stuff, why K3B wouldn't run. I would bet that you're using an X Display Manager, like kdm, gdm, or even xdm. You can't just su into root and run stuff like that. You need to fully log out, then log into whatever wm you use as root. When you do that, k3b should come up just fine. But it still probably won't pick up the devices :( Oh, if life were simpler in FreeBSD land. First off, check that the following lines exist in your kernel config... device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atapicam Especially important is that last one, as it ain't in the GENERIC kernel last I checked. That's the magical beast that'll get it all playing. Get that in there and recompile your kernel. You might get away with kldload cam, but I honestly don't know if that's the same thing. Then you'll want to get permissions and links all setup proper every time you boot in. Here you'll need to get /etc/devfs.conf all tweaked up proper for normal users. # /etc/devfs.conf permacd00666 linkacd0cdrom linkacd0dvd permpass0 0666 permcd0 0666 permxpt00666 You may want to instead link cd0 to cdrom and dvd, but these settings seem to work for me here. Make sure your /etc/rc.conf has the line... devd_enable=YES This is default in newer versions of FreeBSD. Doesn't hurt to toss it in there thought. The k3b port will have installed cdrdao, but it wouldn't have tweaked on it's permissions. This one you'll most likely want to make it suid root. Definitely not something you'd want to do on a production server box just out of paranoia, but reasonably safe on a desktop. # As root cd /usr/local/bin chmod u+s cdrdao After jumping through all those fun loving hoops, it should work shweet. In fact, k3b will automatically add your CD into the device list. If k3b didn't put it in there for you, that's a clue that something isn't right. Good luck! On 4/14/05, Justin R. Pessa [EMAIL PROTECTED] wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. Here is the output of dmesg. The system sees the device fine, I folloed the handbook instructions for CDRW setup. acd0: CDRW TDK CDRW241040X/6.34 at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: TDK CDRW241040X 6.34 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [1 x 2048 byte records] $ ls -al /dev/acd0 crw-rw-rw- 1 root jstn4, 13 Apr 7 22:14 /dev/acd0 I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Any ideas? Thanks! ._ | Justin R. Pessa | http://jstn.sdf1.org -- When you come to a fork in the roadTake it - Yogi Berra - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding my CDRW device to k3b
On Friday, 22. April 2005 03:35, Danny Pansters wrote: OK, let it be clear that the cdrdao thing is a problem of the software itself (as in: not needed to be root if done right), but certainly for us with devfs and proper permissions and group membership this can be solved without any problems or upstream changes. I can burn CDs alright but the GUI throws the warning nonetheless (simply because of cdrdao not being suid root? -- suid root shouldn't be needed at all). Only if cdrdao is suid root, it can set itself to realtime priority during burning, which is a feature. This used to be more important back when the machines were slower and buffer underruns meant burning coasters. You can turn off the permissions check (and all other similar checks) with k3b's options, Misc tab, Check system configuration checkbox. I recently discovered another problem with k3b: Try to burn a 5.4-RC3 iso with it. Booting off it wouldn't work, and after pulling out a modest amount of hair I mounted the CD, and yes, there was one single file called blah.iso on the CD :) And you're sure you used the Tools/CD/Burn CD Image menu to do that? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgptAmnDwPWqd.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
On Friday 15 April 2005 00:00, Justin R. Pessa wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. snip I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Have you tried running k3b as root, if it sees your device as root. Then you can change the permissions for the devices or just run it as root hope this helps .nbco ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding my CDRW device to k3b
On Apr 15 12:06AM, nbco wrote: On Friday 15 April 2005 00:00, Justin R. Pessa wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. snip I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Have you tried running k3b as root, if it sees your device as root. When I run an X app as root I get: Password: [EMAIL PROTECTED] /home/jstn $ k3b Xlib: connection to :0.0 refused by server Xlib: No protocol specified k3b: cannot connect to X server :0.0 I'm not sure how to give root permission to the X session on this display. Any thoughts here? Then you can change the permissions for the devices or just run it as root hope this helps .nbco Thanks! - j ._ | Justin R. Pessa | http://jstn.sdf1.org pgpdqGb6bhggH.pgp Description: PGP signature
Re: Adding my CDRW device to k3b
On Friday 15 April 2005 00:08, Justin R. Pessa wrote: On Apr 15 12:06AM, nbco wrote: On Friday 15 April 2005 00:00, Justin R. Pessa wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. snip I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Have you tried running k3b as root, if it sees your device as root. When I run an X app as root I get: Password: [EMAIL PROTECTED] /home/jstn $ k3b Xlib: connection to :0.0 refused by server Xlib: No protocol specified k3b: cannot connect to X server :0.0 I'm not sure how to give root permission to the X session on this display. Any thoughts here? Well, it seems, you should check your .xserverrc for your X -nolisten tcp r :0 settings or chown the raw devices from root to yourself. .nbco ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding my CDRW device to k3b
On Friday 15 April 2005 01:06, nbco wrote: On Friday 15 April 2005 00:00, Justin R. Pessa wrote: Allo! I'm having problems trying to get k3b to recognize my CDRW drive. I went to Settings COnfigure k3b Devices. When I add /dev/acd0 it says Could not find an additional device at /dev/acd0. snip I realize this is probably more a k3b problem than a FreeBSD problem, but I feel as though there is something specific to FreeBSD I have either missed or am over looking. Have you tried running k3b as root, if it sees your device as root. Then you can change the permissions for the devices or just run it as root hope this helps .nbco When I run an X app as root I get: Password: [EMAIL PROTECTED] /home/jstn $ k3b Xlib: connection to :0.0 refused by server Xlib: No protocol specified k3b: cannot connect to X server :0.0 I'm not sure how to give root permission to the X session on this display. Any thoughts here? You shouldn't run as root. If running an X app as root without the X session being run by root to begin with, you'd connect to a second X server, e.g. :1. But you shouldn't do this at all. Instead you should enable atapicam (and basic scsi support) in your kernel and use /dev/cd0, the emulated scsi CDRW, instead. K3b uses cdrecord which uses scsi devices only. As far as root goes: per default the CD devices are owned root:operator, so just add your username to the operator group in /etc/groups and you should be done. HTH, Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
