I am running slackware 10.0, kernel 2.4 and I keep getting these errors during bootup.

hdi: no response (status = 0xfe)
hdk: no response (status = 0xfe)

How do I fix these?


Also, when I use CDRECORD it says that no responses from /dev/dg*


Thanks for helping ^^

do you know what SHOULD be on /dev/hdi and /dev/hdk respectively? Or are they being used for anything? Usually, your primary IDE hard disk will be on /dev/hda, your slave hard drive might be /dev/hdb, your cdrom drive might be /dev/hdc, etc. I can't imagine how you'd get a /dev/hdi though.

What's in the file /etc/fstab and /etc/mtab (you'll need to be root for this)


With regard to the cdrecord problem, I imagine its very related. It's looking for the cdrw drive and it thnks it's on /dev/dg - why I'm unsure.

can the new linux kernel 2.6 fix it?

i don't think its really a kernel problem, unless your using very obscure hardware. But since it is just hard disks and cd rom drives we're talking about here, i don't think it's a kernel issue. I would only reinstall as a lat case option. if you check out the hardware compatability lists for your distribution, you can see if your hardware is supported or not. if not, there is a chance that the device drivers loaded are generic and point to the wrong interfaces. what does /etc/fstab say. it should be something like this:

/dev/hda2 / reiserfs acl,user_xattr 1 1
/dev/hda3 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid

etc.

i am guessing yours might not be like this, in which case, you just might be better off trying to reinstall. what kind of hardware setup are you using, btw? to answer your question, the 2.6.series and the 2.4 series kernels support about the same amount of hardware (hard disks and cdrom (ide devices)) anyway, so recompiling a 2.6.x kernel is pointless. have a go if you want. the current version is 2.6.13 as far as i know. get a 2.6.12 series which is very stable at this point.

I agree; it's probably a configuration problem, not a kernel problem.