![](https://seccdn.libravatar.org/avatar/a1fdfdca1b14fb0e9cdc0ec8aed3e057.jpg?s=120&d=mm&r=g)
If your lilo was run, and you did make modules, and
make modules_install, and it still doesn't work, you
need to look at your compile.
When you compiled your kernel, did you compile the
eide e.g. support INTO the Kernel (not as a module)?
If you loaded as a module, it will never work. Also,
you need gzip support compiled into the kernel.
My suggestion, as I agree with you that the smallest
kernel required is best, is to do the following:
run the make config, and leave block devices alone,
except for scsi support, which you can either 'n' or
'm'. Then say 'n' to all the other stuff you don't
need, such as ham, sound, joystick, etc..
make clean;make dep;make bZimage;make bZlilo
Check that the new kernel and System.map have
successfully copied themselves to the /boot. IF you
move the kernel, or rename, or whatever, rerun lilo!
mk_initrd
reboot!
This should give you about a 600k kernel.
--- Ken Hughes
Kastus wrote:
Hi Ken,
The problem is that the kernel is way too big and the computer is a bit outdated. I've had a similar problem with SuSE 6.3 and kernel 2.2.13 on a Iwill motherboard. I stripped down the kernel to the very basics but had to have scsi disk support. With resident scsi kernel never get booted. The only way out was to make scsi module and use initrd. Then it worked.
HTH, -Kastus
The newly compiled kernel is around 440k, while the SuSE default is over 800k! I don't have any fat stuff like scsi compiled, mainly networking stuff. Does anyone know if SuSE writes lilo to the mbr by default? Maybe it's not my kernel, but lilo that's hosing me up.
<rant> As a side note, I understand SuSE's stance on supporting non-SuSE-default kernel compiles, but it's still the SuSE kernel, with _their_ kernel mods and such. Rather than force you to use an 800k kernel with a bunch of modules you don't want like usb, parallel port, etc., it seems as though they could offer some stripped down modules without alot of the fluff to choose from. </rant>
Thanks for all the help! Cheers!
Ken
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
__________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
![](https://seccdn.libravatar.org/avatar/cfe9cebf1e9368b80628b16bb6eb2623.jpg?s=120&d=mm&r=g)
Well, problem is sorta solved. I made sure to compile ramdisk support into the kernel (using bzImage rather than zImage), left the initrd stuff in lilo.conf, rebooted and viola! Bootable kernel! This was on my test SuSE 7.0 machine. Odd thing is that if I duplicate the _same_exact_thing_ on the production firewall, I get: Loading Linux... and then the machine resets. I'm 'bout ready to bag this and use my test machine as the new firewall anyway. Thanks again for all the help everyone! Cheers! Ken -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (2)
-
heroron@yahoo.com
-
kenh@ast-inc.com