/proc/cmdline did not have hdd=ide-scsi in it so I updated /etc/grub.conf with that parameter and now cdrecord -scanbus finds and correctly identifies the burner. I'm about to make a copy of Fedora Core 2 for a local charity that refurbishes old computers.
Am Sa, den 18.09.2004 schrieb Jude DaShiell um 23:55:
/proc/cmdline did not have hdd=ide-scsi in it so I updated /etc/grub.conf with that parameter and now cdrecord -scanbus finds and correctly identifies the burner. I'm about to make a copy of Fedora Core 2 for a local charity that refurbishes old computers.
Please read the Fedora Core 2 release notes. ide-scsi emulation is obsolete. So many time explained here on the list how to use a CD burning device on FC2.
Alexander
On Sat, 2004-09-18 at 15:36, Alexander Dalloz wrote:
Am Sa, den 18.09.2004 schrieb Jude DaShiell um 23:55:
/proc/cmdline did not have hdd=ide-scsi in it so I updated /etc/grub.conf with that parameter and now cdrecord -scanbus finds and correctly identifies the burner. I'm about to make a copy of Fedora Core 2 for a local charity that refurbishes old computers.
Please read the Fedora Core 2 release notes. ide-scsi emulation is obsolete. So many time explained here on the list how to use a CD burning device on FC2.
I don't mean to be a pest, but can you send me a pointer to exactly where you have explained how to burn CDs under FC2. A modest search of the archives hasn't turned up anything. Ditto /usr/src/linux/README and the files under /usr/src/linux/Documentation.
The latest cdrecord upgrade has completely broken CD burning on my system; the last audio CD is **quite** amusing and not unpleasant to listen to, but nothing like the original sound.
Many thanks for all your good postings:
Jonathan Ryshpan jonrysh@pacbell.net
I don't mean to be a pest, but can you send me a pointer to exactly where you have explained how to burn CDs under FC2. A modest search of the archives hasn't turned up anything. Ditto /usr/src/linux/README and the files under /usr/src/linux/Documentation.
The latest cdrecord upgrade has completely broken CD burning on my system; the last audio CD is **quite** amusing and not unpleasant to listen to, but nothing like the original sound.
Many thanks for all your good postings:
Jonathan Ryshpan jonrysh@pacbell.net
I'm not clear on what you're needing help with: the specifics of how to use cdrecord (or the much easier to use k3b), or is your problem associated with the "can't burn as a non-root user in kernel 2.6.8.x"?
k3b is very intuitive and does a nice job burning cds with a minimum of fuss. However if you are using the 2.6.8.x kernel, you can't burn as a non-root user. Your choices are to either a) su to the root user and burn away, or b) boot into an earlier kernel.
This tutorial may be of some help: http://penguinsolutions.org/fedora/cdrw/
Here's a trick I've used to help teach myself the necessary cdrecord commands: burn in k3b, but make a note of the output log. It provides the specific cdrecord command that k3b created to get the job done.
Hope this helps, Clint
On Tue, 2004-09-28 at 02:20, Clint Harshaw wrote:
I don't mean to be a pest, but can you send me a pointer to exactly where you have explained how to burn CDs under FC2. A modest search of the archives hasn't turned up anything. Ditto /usr/src/linux/README and the files under /usr/src/linux/Documentation.
The latest cdrecord upgrade has completely broken CD burning on my system; the last audio CD is **quite** amusing and not unpleasant to listen to, but nothing like the original sound.
Many thanks for all your good postings:
Jonathan Ryshpan jonrysh@pacbell.net
I'm not clear on what you're needing help with: the specifics of how to use cdrecord (or the much easier to use k3b), or is your problem associated with the "can't burn as a non-root user in kernel 2.6.8.x"?
k3b is very intuitive and does a nice job burning cds with a minimum of fuss. However if you are using the 2.6.8.x kernel, you can't burn as a non-root user. Your choices are to either a) su to the root user and burn away, or b) boot into an earlier kernel.
This tutorial may be of some help: http://penguinsolutions.org/fedora/cdrw/
Here's a trick I've used to help teach myself the necessary cdrecord commands: burn in k3b, but make a note of the output log. It provides the specific cdrecord command that k3b created to get the job done.
I've been making CDs with a little script, from which I use the single line: cdrecord -v dev=/dev/cdrom -dao -useinfo *.wav This has always worked in the past. I've also used the front end gcombust, which has also generally worked OK
Lately, I've noticed the following things:
o "cdrecord -scanbus" produces the line 1,0,0 100) 'SONY ' 'DVD RW DRU-510A ' '1.0c' Removable CD-ROM but "cdrecord dev=1,1,0 -inq" produces the lines scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 cdrecord: No such file or directory. Cannot open '/dev/sg*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. "cdrecord dev=/dev/hdc -inq" produces info that looks correct.
o When I try to burn a CD-ROM using the line cdrecord -v dev=/dev/cdrom -dao -useinfo *.wav #or similar and with /usr/bin/cdrecord setuid to root I get messages, the gist of which are DAO mode, or SAO mode, or RAW mode are not available.
o When I tried to burn an audio CD-ROM as root, I crashed the X server and some other daemons. (I'm not sure which ones, they flashed past me while robooting the system.) The CD generated in this process got the correct entry from the cddb database, but sounded **very** strange.
I've just installed k3b, but haven't had a chance to use it yet.
It looks from your little web site: http://penguinsolutions.org/fedora/cdrw/cdrw.html that Linux-2.6.8 is well and truly broken, and that the best thing to do is to downgrade to 2.6.7. Other people say all kinds of things about installing, or **not** installing the ide-scsi module. It may also be that cdrdao, which can be invoked by k3b works better than cdrecord; I haven't had time to try this yet. Alex Dalloz claims to have posted solutions multiple times, but I can't find his postings anywhere in the archive.
The situation is complicated because cdrecord has recently been upgraded as well as the kernel. As near as I can figure out, the reason for the upgrade is to have cdrecord drop privilege when invoking child processes, which it can do in some cases, using the RSH environment variable.
Many Thanks - jon
Am Di, den 28.09.2004 schrieb akonstam@trinity.edu um 22:47:
Forget cdrecord and use k3b or xcdroast,
Aaron Konstam
Hm? At least k3b uses cdrecord for burning. So if cdrecord does not work, how should k3b then?
Alexander
akonstam@trinity.edu wrote:
On Tue, Sep 28, 2004 at 09:30:16AM -0700, Jonathan Ryshpan wrote:
On Tue, 2004-09-28 at 02:20, Clint Harshaw wrote:
I don't mean to be a pest, but can you send me a pointer to exactly where you have explained how to burn CDs under FC2. A modest search of the archives hasn't turned up anything. Ditto /usr/src/linux/README and the files under /usr/src/linux/Documentation.
Forget cdrecord and use k3b or xcdroast,
I second that motion. I always used cdrecord until I installed FC2 and found the new setup introduced some weirdness into the way cdrecord worked. Also, I found the k3b is an absolutely fantastic cd burning interface and lets me specify details without overwhelming me with them. The xcdroast interface is a monstrosity, spare yourself the pain, it's not worth figuring out if you have k3b.
Paul
Dear Clint Harshaw,
Once you wrote about "Re: latest cdrecord problem status":
k3b is very intuitive and does a nice job burning cds with a minimum of fuss.
Since you are at that, can you please point me to the option which will force k3b to recognize ISO9660 image and write it to CDs as filesystem, not as single file.
cdrecord does it out of the box, but k3b seems to be different in this regard.
TIA.
On Tue, Sep 28, 2004 at 09:30:16AM -0700, Jonathan Ryshpan wrote:
On Tue, 2004-09-28 at 02:20, Clint Harshaw wrote:
I don't mean to be a pest, but can you send me a pointer to exactly where you have explained how to burn CDs under FC2. A modest search of the archives hasn't turned up anything. Ditto /usr/src/linux/README and the files under /usr/src/linux/Documentation.
Forget cdrecord and use k3b or xcdroast,
On Tue, 28 Sep 2004 23:43:47 +0300, Leonid Mamchenkov wrote:
Dear Clint Harshaw,
Once you wrote about "Re: latest cdrecord problem status":
k3b is very intuitive and does a nice job burning cds with a minimum of fuss.
Since you are at that, can you please point me to the option which will force k3b to recognize ISO9660 image and write it to CDs as filesystem, not as single file.
cdrecord does it out of the box, but k3b seems to be different in this regard.
Use menu "Tools > CD > Burn CD Image..."
Leonid Mamchenkov wrote:
Dear Clint Harshaw,
Once you wrote about "Re: latest cdrecord problem status":
k3b is very intuitive and does a nice job burning cds with a minimum of fuss.
Since you are at that, can you please point me to the option which will force k3b to recognize ISO9660 image and write it to CDs as filesystem, not as single file.
cdrecord does it out of the box, but k3b seems to be different in this regard.
TIA.
Sure -- here are the instructions that will get k3b to burn an iso for you:
Suppose you have an iso named blah.iso in a directory.
1. Start k3b 2. Click on Tools -> CD -> Burn CD Image 3. In the Image to Burn section, browse to the directory containing blah.iso. 4. Select blah.iso 5. Click on burn
You're all set!
One thing I have noticed about k3b, is that when you select the Burn CD Image option, it will go to the location of the first .iso that you burned, and immediately start the md5 check. You have to manually browse to the next cd to burn each time, and interupt the check. There probably is a setting to change that will remedy this, but it's only a mild annoyance, and not a headache.
Hope this helps, Clint
On Tuesday 28 Sep 2004 16:30, Jonathan Ryshpan wrote:
The latest cdrecord upgrade has completely broken CD burning on my system; the last audio CD is **quite** amusing and not unpleasant to listen to, but nothing like the original sound.
rpm -q cdrecord? on my system I have cdrecord-2.01-0.a27.4.FC2.3 which as far as I can tell is the latest one.
cdrecord -v dev=/dev/cdrom -dao -useinfo *.wav
are you trying to burn an audio CD? have you considered cdrecord -v dev=... -audio -pad *.wav always worked here...
Lately, I've noticed the following things:
o "cdrecord -scanbus" produces the line 1,0,0 100) 'SONY ' 'DVD RW DRU-510A ' '1.0c' Removable CD-ROM but "cdrecord dev=1,1,0 -inq" produces the lines scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 cdrecord: No such file or directory. Cannot open '/dev/sg*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. "cdrecord dev=/dev/hdc -inq" produces info that looks correct.
try cdrecord dev=ATAPI:1,0,0 -inq although ide-scsi is no longer required you do need to tell cdrecord that it needs to use an ATAPI device.
Alternatively you could put this info into /etc/cdrecord.conf
the kernel-2.6.8 issue is well documented and does indeed stop you from burning CDs as a normal user. Downgrading is not too hard and is my current solution of choice...
Stuart
So, I've got a couple of FC2 machines on a network and what I want is to get a network storage device to plug into the network and use it for backup.
Looking at a couple of them yesterday, they all have a windows configuration CD. Not having any Windows machines I felt better to ask here for solutions rather than buying into the unknown.
So, what network storage devices work on a pure Fedora network? I'd like to get 200GB or more storage.
I note that for the same capacity network storage devices are rather cheaper than Snap servers - whats that about?
Thanks
Richard
On Mon, 2004-10-11 at 09:36, Richard Emberson wrote:
Looking at a couple of them yesterday, they all have a windows configuration CD. Not having any Windows machines I felt better to ask here for solutions rather than buying into the unknown.
So, what network storage devices work on a pure Fedora network? I'd like to get 200GB or more storage.
The NAS devices I have worked with in the past used a web front end to configure them. The windows configuration CD you mentioned might be drives for windows systems to use the NAS device but typically for windows machines NAS devices appear as windows shares (samba type shares). Good NAS devices however should support NFS as well as windows lan manager type file sharing.
Check the ones you are looking at to determine if they can be setup just using a browser. It they can and they support NFS then you can use them no problem. If they only support Lan Manager type shares you can still use them with Linux you will just need to configure samba on your systems so you will have the permissions to access the NAS device.
Another alternative is that you can purchase 200GB harddrives (or larger) for not to much money. A couple of months back Compusa had a sale going on for 250GB Maxtor drives for something like $150. Probably a lot cheaper than a NAS device. You can just pop one in one of your Linux boxes and use NFS to share it out.
This is what worked out best for me. I bought a MAXTOR 200GB external hard drive and a linksys NSLU2 and now I can access it from my windoze & fedora core 2 boxes (using webmin smbfs ) without a problem.
Raghu.
On Mon, 11 Oct 2004 10:07:36 -0400, Scot L. Harris webid@cfl.rr.com wrote:
On Mon, 2004-10-11 at 09:36, Richard Emberson wrote:
Looking at a couple of them yesterday, they all have a windows configuration CD. Not having any Windows machines I felt better to ask here for solutions rather than buying into the unknown.
So, what network storage devices work on a pure Fedora network? I'd like to get 200GB or more storage.
The NAS devices I have worked with in the past used a web front end to configure them. The windows configuration CD you mentioned might be drives for windows systems to use the NAS device but typically for windows machines NAS devices appear as windows shares (samba type shares). Good NAS devices however should support NFS as well as windows lan manager type file sharing.
Check the ones you are looking at to determine if they can be setup just using a browser. It they can and they support NFS then you can use them no problem. If they only support Lan Manager type shares you can still use them with Linux you will just need to configure samba on your systems so you will have the permissions to access the NAS device.
Another alternative is that you can purchase 200GB harddrives (or larger) for not to much money. A couple of months back Compusa had a sale going on for 250GB Maxtor drives for something like $150. Probably a lot cheaper than a NAS device. You can just pop one in one of your Linux boxes and use NFS to share it out.
-- Scot L. Harris webid@cfl.rr.com
The discerning person is always at a disadvantage.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
xcdroast is another front-end for cdrecord.
On Tue, 28 Sep 2004, Alexander Dalloz wrote:
Am Di, den 28.09.2004 schrieb akonstam@trinity.edu um 22:47:
Forget cdrecord and use k3b or xcdroast,
Aaron Konstam
Hm? At least k3b uses cdrecord for burning. So if cdrecord does not work, how should k3b then?
Alexander
-- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp Serendipity 22:40:42 up 8 days, 44 users, load average: 1.87, 1.74, 1.76
On Fri, 2004-10-15 at 16:28 -0400, Jude DaShiell wrote:
xcdroast is another front-end for cdrecord.
On Tue, 28 Sep 2004, Alexander Dalloz wrote:
Am Di, den 28.09.2004 schrieb akonstam@trinity.edu um 22:47:
Forget cdrecord and use k3b or xcdroast,
Aaron Konstam
Hm? At least k3b uses cdrecord for burning. So if cdrecord does not work, how should k3b then?
Alexander
I was actually using konqueror. As I said, it worked before and then it just stopped.
-
akonstam＠trinity.edu -
Alexander Dalloz -
Clint Harshaw -
Edward Croft -
Jonathan Ryshpan -
Jude DaShiell -
Leonid Mamchenkov -
Michael Schwendt -
Paul Kopacz -
Raghu Vadapalli -
Richard Emberson -
Scot L. Harris -
Stuart Sears