This is becoming a real friggen royal pain in the @$$.




I'm nowhere near the stage where I can either "compile" or "re-compile" anything never mind getting the damned cdrw to work.

Well, I've never used SuSE, so I wouldn't know.
I use slackware, just because I _want_ to compile everything myself etc
Great for learning stuff

But anyway, as long as you don't have scsi-emulation (either compiled in your kernel or as a module) OR a 2.6 kernel, you can forget about burning with an IDE device...

ok .... if this isn't weird...



This is just the weirdest thing. I removed all the entries I made in "modules.conf", "/etc/fstab", symlinks, everything - even the line "hdc=ide-scsi" in the bootloader and rebooted my comp to get back to the way it was.

Once I reboot, and started K3b just for the heck of it, BOTH my DVD and CDRW show up as SCSI devices!


Is Linux running contrary to what I want it to do??

Haha
Let me guess: after a reboot everything is back to your old config
Anyway, let's hope it keeps working

Yup, everything's back to original config (I had made backup copies of /etc/fstab and /etc/modules.conf) and now that I've rebooted the CDRW and DVD are "/dev/sr0" and "/dev/sr1" respectively. Really bizarre. LOL watch me reboot and that will change back to /dev/cdrom and /dev/dvd again! noooooooooo. (don't even want to think about it.)

This is really perplexing though. I'm wondering why this would happen. Not that I want to re-create this whole affair - seems I grew a few grey hairs and lost a few pounds during all this.

Anycase, when I run "cdrecord -scanbus" as "root" this is now the result:

• linux:/ # cdrecord -scanbus
  Cdrecord 2.0 (i686-suse-linux) Copyright (C) 1995-2002 Jörg Schilling
  Linux sg driver version: 3.1.24
  Using libscg version 'schily-0.7'
  cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.75-resmgr-patch '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright 1997 J. Schilling').
  scsibus1:
  1,0,0 100) 'LITE-ON ' 'LTR-52327S ' 'QS04' Removable CD-ROM
  1,1,0 101) 'HL-DT-ST' 'DVD-ROM GDR8161B' '0100' Removable CD-ROM
  1,2,0 102) *
  1,3,0 103) *
  1,4,0 104) *
  1,5,0 105) *
  1,6,0 106) *
  1,7,0 107) *
  linux:/ #

I dunno how all this happened, but I'd give y'all a beer for the help.
Thanks

Ok, just a quick update - for anyone reading this in the future. (hope this helps you as it did me).

In SuSE 8.2 it seems the SCSI module has to be called to be loaded properly and then there are a few things that need "tweaking" in order for the system to "see" the CDRW:

1) add "hdX=ide-scsi" to the GRUB bootloader (where X is the cdrw drive)
2) logged in as "root" edit (use pico) the file /etc/init.d/boot.local
add this line at the end of the file:
/sbin/modprobe ide-scsi
3) in a console, logged in as "root" make a symbolic link like so:
ln -sf /dev/scd0 /dev/cdrecorder
4) edit /etc/fstab (using pico) and add this line:
/dev/cdrecorder /media/cdrecorder auto ro,user,exec 0 0
5) reboot
6) login as root in login manager (GUI), go to CD-ROM Drives in YaST2 Control Centre (YaST2-YaST2 modules-Hardware-CD-ROM Drives) and add your drive.

If you're thinking of using K3b as your burning software, then log in as root (login manager) and then run K3b Setup and your drive will be visible and properly configured already.

BTW, if you want to use K3b you'd best uninstall the version distributed with SuSE (it's crippled), download and install the full version here: http://packman.links2linux.de/index....ction=219&vn=1

To uninstall K3b: console (root), type: rpm -e k3b
To install new version: console (root), type: rpm -ihv k3b_filename.rpm


Hope this will help someone that was in my shoes.