LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   New Kernel Error (http://www.linuxquestions.org/questions/slackware-14/new-kernel-error-43021/)

BittaBrotha 01-27-2003 09:55 PM

New Kernel Error
 
I've just reinstalled Slackware 8.0 with kernel 2.2.19 and once installed, it will boot fine. When I try to compile kernel 2.4.19, everything goes fine until time to reboot the system.

When it reboots, the info that displays while booting, I see something about {Disk Seek Errors} or something similar. I see a few of them and then I get the Kernel Panic errors.

I've checked and doubled check the new kernel and everything seems to look okay. Why would I get this error on the 2.4.19 kernel but not with the 2.2.19 kernel? I guess I will try downloading the 2.4.20 kernel and try that.

Also I've recompiled kernels for Slack 8.0 numerous times without this happening. But this is a different kernel then the other one's I used. Maybe it's a bad kernel, I dunno!

Any ideas/suggestions?

Thnx.

trotfox 01-27-2003 10:01 PM

Hi Bitta Brother,
There could be numerous reason why the new Kernel is not working, It may help if you send through the error messages that you get on boot.

I don't think that the 2.4.20 kernel will give much of a change from the 2.4.19.

Possibly there are some "additional" options that need to be specified in your Kernel configuration for your hard disks to work properly.

RG
Aaron

Excalibur 01-27-2003 10:16 PM

My first thought would be a disk error. You might try to recopy the kernel and rerun lilo. However, it could also be a DMA issue if the high speed IDE controller drivers were enabled. So you might try a kernel parameter ide=nodma to disable DMA operations. It can be done in your lilo.conf file by adding the "append = ide=nodma" statement to the new kernel section. Then run lilo to write the new boot record. Also, if the prior kernel install of lilo used the MBR to boot and the new kernel is using the partition (i.e. hda1 instead of hda for example) then the old boot loader could be trying to load from the MBR. Simply change it back to the MBR of the disk (hda) and rerun lilo to write the new MBR record.

Just a few thoughts to perhaps help isolate where the problem is. I am running 2.4.19 with Slack 8.1 and very stable other than VM issues under high memory demands. But I have those problems with 18, 19 and 20.

BittaBrotha 01-27-2003 10:22 PM

Thnx for the replies...well I've done it before without any problems but then I may have left something out of the new kernel. I'm at work now but will try your suggestions when I get home in the morning.

I didn't give my hardware specs so here goes:

An AMD XP 1700 cpu, Shuttle AK31A with VIA 266 chipset, 256mb ram, 40gb Maxtor IDE HD, ATI Radeon 7200 agp video card and a DVD/CD drive.

This same setup worked once before without any problems using the 2.4.19 kernel but I did reformat my hard drive and this is when the problems began!


All times are GMT -5. The time now is 10:01 PM.