burned by XCDroast

[dishawjp]

Hi All,

I tried to get RH 8 XCDRoast up last night.  I checked out the FAQ, went to xcdroast.org, downloaded and installed the new files and no luck.  So did some Google searching and found that SCSI emulation was the way to go.  I edited grub and got that happening... but still can't burn a CD.  

I wasn't too concerned... I was getting low on beer and was considering calling it a night, but did do a reboot for some reason that escapes me this morning.  Anyway, during the reboot, fstab failed to load /dev/cdrom1. I edited fstab to comment out that line and the computer will boot now without whining, but I have a problem here I need to fix.

Should I re-edit grub and forget SCSI emulation for the CD drives or modify my fstab?  Why would fstab bitch about /dev/cdrom1 but be cool with /dev/cdrom which is set up the same way?  Or, should I blame the whole thing on Molson... I had a case of their Goldens to help me with this last night

Seriously though, if anyone can think of what I most likely hosed and the best way to correct it I'd appreciate it.

Jim

[voidmain]

That's weird. When I did a fresh install of Red Hat 8.0 it automatically configured my burner with ide-scsi on /dev/scd0. X11 is right, can you paste in a copy of your /etc/fstab and also the output from "ls -l /dev/cdrom*"?

[ December 21, 2002: Message edited by: void main ]

[Master of Reality]

why was fstab complaining about the cdrom at bootup? Was there a cdrom in the drive?

I know when i had trouble with my cd burner i added hd*=ide-scsi (*=drive) and xcdroast the nworked fine without anything else. That was in RH 8.

[dishawjp]

Thanks!

My /etc/fstab file is:[dishawjp@eunix etc]$ cat fstab

LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
/dev/hdc2               swap                    swap    defaults        0 0
#/dev/cdrom1             /mnt/cdrom1             iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,kudzu,ro 0
0
/dev/cdrom1             /mnt/cdrom1             iso9660 noauto,owner,kudzu,ro 0
0

The outupt from ls -l /dev/cdrom is:

[dishawjp@eunix etc]$ ls -l /dev/cdrom
lrwxrwxrwx    1 root     root            9 Dec 20 19:57 /dev/cdrom -> /dev/scd0

There was no CDROM in the drive when this happened.

Any assistance greatly appreciated!

Jim

[dishawjp]

Doh!!!!

I just saw it!

I have the /dev/cdrom1 in there twice.  Maybe I should have had a few Molsons less last night. I don't know how that happened though.  I don't think I was drunk enough to have put it in there again.

Jim

[voidmain]

quote:Originally posted by DOSman:
Doh!!!!

I just saw it!

I have the /dev/cdrom1 in there twice.

Yeah, but one is commented out. It looks good to me other than the last zeros are wrapped to the next line, it's not *really* that way in your real fstab file is it? What exactly does the error say?

[ December 21, 2002: Message edited by: void main ]

[dishawjp]

Hi void main,

When I commented it out, the error "failed" error message went away.  I had concerns about commenting out a line in my fstab. The line is not wrapped in the actual fstab, my Xterm window should have been made wider to prevent that.  If I remember correctly the error was a "failed" and "mount point not found"   and it mentioned /dev/cdrom1.  This happened last night and I was not thinking too clearly... I just commented that line out, the error went away and then I posted this question to the list.

I still don't have XCDroast working, but that's less of a concern for now. I was afraid that I'd managed to hose something seriously and *that* had me quite concerned.

Thanks again for all your help.

Jim

[voidmain]

Wow, XCDroast is pretty easy to set up. The first time you run it you need to do it as root and create users that you want to allow to use it. Maybe you didn't run it as root the first time?

[creedon]

Jim, it might be wise for you to do some research on CD burning in Linux; all the GUI apps are just front-ends for the CLI application whose name escapes me at the moment.  (It's early; I'm old, OK?)  You've often said to me that you're more comfortable at the CLI than using a graphical app, maybe you would have more success that way.

[Master of Reality]

that would be cdrecord it is a frontend for. But some like Gcombust are also frontends for mkisofs, cdlabelgen, diff, cdda2wav, cdparanoia, lpr.

DAMMIT, i just spilled hot chocolate on myself.

[creedon]

quote:Originally posted by The Master of Reality / B0b:
that would be cdrecord it is a frontend for. But some like Gcombust are also frontends for mkisofs, cdlabelgen, diff, cdda2wav, cdparanoia, lpr.

DAMMIT, i just spilled hot chocolate on myself.

OOWWWWWWWWWWW!!!!  
Yeah, you're right, but cdrecord is the best, and easiest , of the bunch.  (HMMMM....cdrecord, I must remember that.....what were we talking about again?)

[voidmain]

But the thing is, if he installed the RPM it should not have let him install it without the cdrtools prereqs. Unless he forced it with a "--nodeps" which would not have been a good idea. When I installed Red Hat 8 I recall everything being installed from the beginning. I didn't have to do anything other than click on it on the menu at which point it told me I had to run it as root because it was the first run. So I did and it just worked. I have upgraded it from the xcdroast website since that time and used the new cdrtools packages also from xcdroast web site.

[ December 22, 2002: Message edited by: void main ]

[dishawjp]

Hi All,

I've been looking at your comments and hammering away at this computer for a good part of the afternoon.  I think that I have XCDroast about ready to run.  I haven't actually burned a CD yet, but it finally recognizes both the source and target drives and can read the tracks on the source drive.

I did download all the cdtools .rpm files the other day, I had logged in as root to start things, had edited my /boot/grub/menu.lst file for SCSI emulation, created the necessary symbolic links and all that. It just wouldn't run :-(

Now I've been screwing with other things, dunno what I actually did to make it work... but it looks like it's gonna run.  Maybe the difference is that today I'm drinking some good Dutch beer (Christoffel Blond) that my daughter brought me back from Holland and not Canadian beer

I doubt that this could have done it, but among other things, I did download and install the updated kernel from Red Hat (vmlinuz-2.4.18-19.8.0) .  That caused much unhappiness and I had to go back to the earlier one (vmlinuz-2.4.18-14).  I'm starting to feel like I can hose just about anything

MoR/Bob... stick to cold beverages... they're a LOT safer

Creedon... I looked at the man page for cdrecord and it really does look to be a lot more my style.  I'll be giving that a much closer look soon.  I think I'll just take it a bit easy on this thing for the rest of the night and see if I can avoid doing any serious damage to it.

Quick question... All I did to avoid booting to the new kernel was remove references to it in the  grub menu.lst file.  Should I uninstall it?  If so would the best way be to use rpm or should I just leave well enough alone?  Everything seems to be working pretty well now.

Thanks again to all!

Jim

[voidmain]

You can leave the new kernel in there, it won't hurt anything, it just won't get used. I have a feeling you upgraded the new kernel and then X didn't work because you have it set to the nVidia drivers and were lost because you didn't have X. Am I correct?  When you install a new kernel you either have to revert your XF86Config to use "nv" as the driver or install the nVidia drivers for that exact kernel before booting the new kernel. I always upgrade the kernel, reboot and then install the nVidia drivers from a virtual terminal. Then start X.

And here's my script I use for burning ISOs using cdrecord:

Code: [Select]

This will run cdrecord in the background. To watch its progress just do a "tail -f /tmp/mkcd.log". Note you will have to add your logon ID to the "cdrecording" group in order to run it under your userid. Or you can run it as root or do a "# chmod +s /usr/bin/cdrecord" but I don't suggest doing that.

To create an ISO from a CD you can just do:

$ cat /dev/cdrom1 > cdimage.iso

or

$ dd if=/dev/cdrom1 of=cdimage.iso

But for ripping audio CDs and creating a new audio CD from a mix of the resulting wav files Xcdroast is the way to go. It will not automatically convert ripped files to MP3 or OGG (yet) like other ripping utilities.

[ December 22, 2002: Message edited by: void main ]

[dishawjp]

void main,

As usual you are right.  When I started Xwindows bad things happened and I got nervous and bailed on the new kernel.  It must have been the NVidia drivers.

It may be a while before I get to do any serious playing around with it (holidays and all) but when I have some time, I'll download the NVidia drivers for the new kernel and then give it another go.  Sort of the same with the CD burner.  I'll paly with the command line interface and the GUI and decide which works better for me.

Thanks to all for your advice and assistance!

Jim