Quote:

---

i'm using grub, i'm not sure how to edit menu.lst

---

$ head -3 /boot/grub/menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub

Quote:

---

i tried adding

hdb=scsi hdc=scsi

and

hdc=ide-scsi

at the the end of the kernel line

---

Quote:

---

either way, #cdrecord -scanbus
says
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

---

$ more /usr/share/doc/cdrecord/README.ATAPI.setup

Quote:

---

yep,
the kernel is vmlinuz-2.4.27-1-386
debian version 3.1

---

Quote:

---

any ideas?

---

Quote:

---

21:33 <delta9> any ideas
21:33 <dpkg> Yeah, I have an idea! But I'll need a drawer full of rutabagas, a little WD-40, and 42 rabid hamsters.
And keep the CIA off my back for the next few hours!

---

Quote:

---

thanks.

---

Quote:

---

21:49 <delta9> ide cdr scsi
21:49 <dpkg> You need to disable (or compile as a module) ide-cdrom support and enable idescsi (block devices), scsi, scsi cdrom, scsi generic support in a 2.2.x onwards kernel. Check for similar options on a 2.0.x kernel

---

Quote:

---

sherm said:
READ THE FUCKING MANUAL .............

---

At least YOU said it...  This is the first thing any debian user will tell you.  The way to counter it is make sure you actually read the manual and prove so when asking your questions by referencing it ...  Why people get all bitchy that we force people to do this, I don't know as it just makes them better in the end . Lazy sods is what I think.

Quote:

---

haha, sorry
yea, i should have looked at the answer it put if front of my face.

at least i googled it.

---

Yes, you should always do several things on a linux system.  Generally I do them in this order: I check the manpage (`man programname'), check the info page (`info programname'), google.  On debian systems you also have the (awesome, one reason why I *love* debian) option to check in /usr/share/doc/packagename.  This is guaranteed to exist for most every package, as it is a violation of policy for a package to NOT have entries there.  Of course, how helpful it is depends on the maintainer, but that's why there's man, info, and google as well.  Generally, unless I'm in a fix for time, I *only* ask (and believe me, I ask plenty of questions, too!) after doing all of that.  It usually helps you better articulate your problem and it shows the people helping you that you did some research, which makes them feel more like they are helping you than GIVING you the answer...[/rant]

On to things

Quote:

---

hdc: SAMSUNG CD-R/RW SW-248F, ATAPI CD/DVD-ROM drive
hdc: attached ide-cdrom driver.
hdc: ATAPI 48X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA

---

These are all we're concerned about, and the lack of error messages is a Good Thing

Quote:

---

3. Find a line where you can append additional kernel parameters, eg.
  "append=" in lilo.conf or the loadlin-line in the batch file.
4. Append sth. like this: "hdb=ide-scsi hdc=ide-scsi max_scsi_luns=1"
  The hdX-parameters defines devices that should be mapped to SCSI
  latter. You may do it with non-writers too, since the emulation layer
  is almost complete. Or omit some so the devices will use their
  native drivers (eg. ide-cd).

What does it mean "Append sth." what does it mean "sth."

---

Ok, a couple things to note about the nature of debian.  Every package has a maintainer who is personally responsible for that package.  Often, they make mistakes in language, especially if english is their second language.  "Joerg Jaspert" maintains the cdrtools package, in which cdrecord is included.  Joerg also has been using debian for some time, as his information only contains information for LILO and not GRUB (which is now the default debian bootloader).  So what does he mean?  I think he meant "append it", which in GRUB is accomplished as passing commandline paramaters to the kernel image (that is, the way you have been doing it is fine).   Report a bug (lowest priority) or contact a maintainer if you are interested in helping (but I would think this could have been reported by now, as it has been quite a while).  Also, check bugs from time to time.

Quote:

---

Do i change my  grub entry like this?

kernel          /boot/vmlinuz-2.4.27-1-386 root=/dev/hda1 ro hdb=ide-scsi hdc=ide-scsi max_scsi_luns=1


or should i just add this because the drive is hdc

kernel          /boot/vmlinuz-2.4.27-1-386 root=/dev/hda1 ro hdc=ide-scsi max_scsi_luns=1

i'll try both, no better way to learn than to break somthing.

what do you think? Do i have the right idea?

---

You should only need to map hdc to scsi, as this is the drive in question.  And yes! I think you certainly have the right idea and were on the right track to begin with, just needed a little push or point (as we all do) in the right direction

Also, while I'm ranting about debian, if you haven't already, I highly recommend the package "apt-listbugs" be installed.  It will alert you about current bugs in a program when you install with apt, which can be useful as sometimes you may encounter the same issue but you already knew about it so you don't freak out .