I have just finished compiling a 2.6.8 kernel but on boot-up I get the following messages:

FATAL Module ide_cd not found

FATAL Module ide_detect not found

FATAL Module ide_disk not found

Module psmouse not found

The system then continues booting.

I used my existing 2.4 kernel config as a guide to this compile. I have compiled in scsi support for my ide drives and my mouse is USB.

I would be grateful if anyone could shed some light on these error messages?

Does the install work or crash?

I would venture a guess that a config file/boot script is looking for those things as modules. If the boot fails, you probably forgot to compile them as modules. If the boot succeeds, you probably compiled them in as "Y", but some script is looking for it.

What I would personally do is to aptitude install kernel-image-2.6.8-3-686 (or whatever architecture kernel you need). This will give you a stock 2.6.8 kernel from the debian repositories that will hopefully work without any errors. Then if you want to recompile it after that, copy the config-2.6.8-3-686 file from /boot to /usr/src/linux/.config and then rebuild your kernel from that.

The install doesn't crash in so far as I am posting this reply from it now although I have no sound and haven't tried the DVDrom yet. I think you are right in that I have compiled some things in as "Y" that should have been modules. I like your suggestion about the stock kernel. As it's late here now I will give that a whirl tomorrow.

Thanks

Mikie

You have no need to use the ide-scsi for cdrom drives anymore access and burning work fine using just a plain ide device with a 2.6 kernel. Make sure you have the alsa-base, alsa-utils and alsa-oss packages installed for the sound those are all that are needed besides the included in kernel module for your sound card that is assuming you enabled it during compile. BTW you should consider consider a newer kernel than 2.6.8 that is rather dated with security problems with it you can try www.backports.org to get IIRC a 2.6.16 kernel built for sarge you may also want some of the other newer packages that are included there.

Thanks, I didn't install alsa-oss which might explain the lack of sound. I still have a couple of questions though.

Originally posted by HappyTux:
.

Just to get this clear in my head, I have said "Y" to scsi support and have hdc=ide-scsi as a boot option in Grub. Are you saying that I don't need either of these for my DVD-RW to work?

When I did my compile I did "aptitude install kernel-source-2.6.8" then did cd into /usr/src, created the symlink and used make menuconfig and kpkg etc. If I use "aptitude install kernel-image-2.6.xx-x-686" what happens after that? I haven't upgraded my kernel that way before.

Correct. 2.6 kernels don't use scsi emulation for CD/DVD drives anymore. I bet that those grub options are what is causing you to get the module errors since 2.6 kernels don't use those modules for that purpose anymore.It basically does the dpkg -i kernel-image-blahblah that you do after you use make-kpkg. So it will install the kernel and update grub.

I had another stab at this yesterday evening.
Firstly I installed alsa-oss and removed the hdc=ide-scsi from my kernel boot line in Grub.
When I rebooted into the 2.6.8 kernel I still got the "Fatal" messages as above but this time as KDE started I had sound. Unfortunately the sound was that of breaking glass accompanying an error message saying that "/dev/cdrom could not be accessed, check that you have permission and that there is a CD in the drive". I checked permissions and restarted X with a cd in the drive but got the same message which, I thought, has to be related to those boot errors. Still, at least I had sound.
Secondly, rather than recompile I decided to take the advice of installing a stock kernel and since I didn't want to complicate things further with a backport I did "aptitude install kernel-image-2.6.8-3-K7". This kernel booted first time without any obvious errors (I haven't studied dmesg) and sound still worked but again the broken glass etc.
As this couldn't have anything to do with the boot errors I suddenly remembered that for scsi emulation I had changed /dev/cdrom to /dev/sr0 in /etc/fstab and symlinked it to /dev/scd0.
It was getting late, but I think I now have to figure out how to put my /etc/fstab right without breaking my system.

Sorry about the length of this post.

Change the /etc/fstab from /dev/sr0 to /dev/hdc, hdd, hdb depending on where on the ide bus the drive is, using dmesg | grep hd should show it in the output.

I'm trying to think of a way of doing this that won't stop my DVD-RW working with my 2.4 kernel so I can always go back to that if things go wrong. Instead of changing /dev/sr0 to /dev/hdc can I add a new line in /etc/fstab for /dev/hdc and how would I do that without confusing /etc/fstab?

Put a # at the front of the /dev/sr0 line then when you reboot to 2.4 remove it and put the same # in fornt of the /dev/hdc.