Specific Hardware questions and help needed

[Sarissi]

To preamble a bit, I want to get away from Windows native boot entirely. In order to do this, I need to get my Cyberdrive CW038D CD-R/RW working as a burner, which is listed in the mandrake hardware database as supported.

 

When I did the K3B setup, it listed the drive, but, some things are missing:

 

eMovix

tccat

tcdecode

tcextract

tcprobe

tcscan

transcode

vcdxbuild

vcdxgen

 

Do I need these installed to burn CD-ROMs? If so, I will install them and this brings me to what next? I tried to burn a test CD, but it would not do so with a fresh CDR in the drive.

 

Does the burner HAVE to be in the master position? That might be a bit tough with my setup.

 

Other hardware I would like to get and have work:

 

USB Hard disk

USB pendrive

USB Compact Flash card reader/writer

EIDE DVD/CD writer Combo drive (a good one)

 

The most important thing at the moment, is my cd burner. Thank you in advance!

[Ixthusdan]

Please post your /etc/fstab and your /etc/lilo.conf.

 

Burners do not have to be masters, but I recommend putting cd devices on seperate channels.

[Sarissi]

IF I knew how to even look at lilo.conf and fstab I would do so.

 

MY current drive setup, excluding floppy is:

 

hda = 60 gig WD, all Windows

 

hdb = 60 gig WD, 1/2 windows and 1/2 linux

 

hdc = 61 gig Maxtor, all linux

 

hdd = cd burner

 

In temporary exile are a maxtor 61 gig hd, and a cdrom drive. I used to have a Promise Ultra100 PCI EIDE controller, until I got his ASRock K7VT2 and found that mandrake install (8.2) swapped the mobo and promise controllers: hda became hde (etc) for install, then linux boot swapped them back, totally screwing the linux boot.

 

If I remember the enterprise kernel error message correctly, the chipset was not recognized. IF that explains the eide controller swapping, then I could get another controller.

 

Unfortunately, I have heard horror stories about mobos made by Asus and Asus Group, which makes this mobo, and their mobos not liking to have both mobo eide and pci eide controllers active (mobo's must be turned off). I like both. Giga-Byte mobos don't have this problem.

[Sarissi]

Okay, here is lilo.conf:

 

boot=/dev/hdb1

map=/boot/map

default="linux-enterpris"

keytable=/boot/us.klt

nowarn

message=/boot/message

menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz

label="linux"

root=/dev/hdb1

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off quiet"

vga=788

read-only

image=/boot/vmlinuz

label="linux-nonfb"

root=/dev/hdb1

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off"

read-only

image=/boot/vmlinuz-enterprise

label="linux-enterpris"

root=/dev/hdb1

initrd=/boot/initrd-enterprise.img

append="devfs=mount hdd=ide-scsi acpi=off"

read-only

image=/boot/vmlinuz

label="failsafe"

root=/dev/hdb1

initrd=/boot/initrd.img

append="devfs=nomount hdd=ide-scsi acpi=off failsafe"

read-only

other=/dev/hda1

label="windows"

table=/dev/hda

other=/dev/fd0

label="floppy"

unsafe

 

Here is fstab:

 

/dev/hdb1 / ext2 noatime 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hdc1 /home ext2 noatime 1 2

none /mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0

/dev/hda1 /mnt/win_c vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hdb5 /mnt/win_c2 vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hda5 /mnt/win_d vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hdb6 /mnt/win_d2 vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hda6 /mnt/win_e vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hdb7 /mnt/win_e2 vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hda7 /mnt/win_f vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

/dev/hda8 /mnt/win_g vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

none /proc proc defaults 0 0

/dev/hdb3 /usr ext2 noatime 1 2

/dev/hdb2 swap swap defaults 0 0

/dev/scsi/host0/bus0/target0/lun0/cd	/mnt/cdrecorder	auto	ro,noauto,user,exec	0 0

 

Now what? Once I figured out, that since I am not changing anything at this point, I could open in kedit (open with option on right click). Duh! :roll:

[Ixthusdan]

The only problem I see is the double entry in your fstab for the cd device. For your current configuration, you should place a "hash" mark (#) in front of the two cd related lines:

#none /dev/cdrom supermount

#dev=dev/scd0, fs=auto, blahblahblah

 

That should do it. Remeber, you need to be root in order to edit this file. If you like gui, simply launch File Manager- Super User Mode, navigate to the file, and click on it. An editor will auto launch and you can edit and save. Then, reboot.

[Sarissi]

Thanks! Now, I presume that while I am editing fstab, I can change the 'win_c' etcetera, entries to something useful, like the actual drive names????

 

I am going to do this later today, as I am going back to bed. I will check back later before I do it.

[Ixthusdan]

You can make it read anyway you wish, but remember that if you change mount point names you will have to also change the folder names in /mnt. As a hint, drives must be unmounted in order to make these sorts of changes. :wink:

 

"umount win_c" is a command that would unmount that particular drive.

[Sarissi]

Ixthusdan;

 

I got it working, thanks to your help! This was the final, critical thing needed in order to see my way clear to a linux native boot (only) box.

[bvc]

[Sarissi]

bvc: Thanks! :D

 

It is very nice to find a site that has a bunch of helpful people. I have no use for those holier than thou geeks, that love to trash newbies that are migrating away from windows. Editing things like fstab is totally foriegn to windows users, as is compiling a kernel. This is actually the first time I have done anything like this, so the satisfaction of getting something working, is very great indeed!!