Kernel too large?
I've got Slack 10 on my Proliant Dual PPRO 200mhz running without issues.
When I go to enable SMP, I run make menuconfig and change only 2 things, the processor type (it shows 486, changed to Pentium Pro) and then enabled SMP with a max of 2 CPU's. I got the error right after I ran make bzImage. It says the kernel is too large and lilo will not add the image to the MBR after i've changed lilo.conf. Wtf am I missing here? Thanks. |
Just run /sbin/lilo -v to take change in account, ignore kernel size message as it just advertising you that it is too big to copy it in a floppy boot disk
|
doesn't /sbin/lilo -v just show the version?
I did run lilo after and it gave the same error .. kernel too large. I thought the error could be just as you said, only for a floppy is it too large. However when I ran lilo after changing lilo.conf to append the new kernel .. it gives that error. I'm just a little hesititant doing it again because it's running so nice now. =) Thanks for the quick reply. |
Just a quick question, did you copy the right file ? (arch/i386/boot/bzImage)
Also could you post your lilo.conf part where you add new kernel entry ? |
When you get a chance, can you post the size in kilobytes your new kernel?
|
Cedrik - I checked out the /usr/src/linux/arch/i386/boot/ and there was a bzImage which was just a bit smaller than my current kernel .. which would make sense.
I then copied it to /boot as vmlinuz.old and then ran lilo .. no problem. (my lilo.conf still has an entry for another kernel) Rebooted and I get a good ole Kernel Panic, VFS Unable to mount root fs on 08:05. I'll post my lilo.conf root@cerveza:/etc# cat lilo.conf # LILO configuration file # generated by 'liloconfig' # # Start LILO global section append="nousb mem=exactmap mem=640K@0 mem=511M@1M" boot = /dev/sda message = /boot/boot_message.txt prompt timeout = 1200 # Override dangerous defaults that rewrite the partition table: change-rules reset # Normal VGA console vga = normal # VESA framebuffer console @ 1024x768x64k # vga=791 # VESA framebuffer console @ 1024x768x32k # vga=790 # VESA framebuffer console @ 1024x768x256 # vga=773 # VESA framebuffer console @ 800x600x64k # vga=788 # VESA framebuffer console @ 800x600x32k # vga=787 # VESA framebuffer console @ 800x600x256 # vga=771 # VESA framebuffer console @ 640x480x64k # vga=785 # VESA framebuffer console @ 640x480x32k # vga=784 # VESA framebuffer console @ 640x480x256 # vga=769 # End LILO global section # Linux bootable partition config begins image = /boot/vmlinuz root = /dev/sda5 label = Linux read-only image = /boot/vmlinuz.old root = /dev/sda5 label = Linux-SMP read-only # Linux bootable partition config ends I only made one change in make menuconfig so I know I didnt disable any built in support. Here's the /boot dir root@cerveza:~# cd /boot/ root@cerveza:/boot# ls -l total 4682 lrwxrwxrwx 1 root root 37 2004-09-28 01:50 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd lrwxrwxrwx 1 root root 21 2004-09-28 01:49 System.map -> System.map-ide-2.4.26 -rw-r--r-- 1 root root 620999 2004-06-14 20:29 System.map-ide-2.4.26 -rw-r--r-- 1 root root 512 2004-09-28 02:58 boot.0800 -rw-r--r-- 1 root root 168 2004-09-28 02:58 boot_message.txt lrwxrwxrwx 1 root root 17 2004-09-28 01:49 config -> config-ide-2.4.26 -rw-r--r-- 1 root root 41017 2004-06-14 20:29 config-ide-2.4.26 -rw-r--r-- 1 root root 5032 2004-05-21 01:19 diag1.img drwx------ 2 root root 12288 2004-09-28 01:44 lost+found/ -rw------- 1 root root 44032 2004-10-01 07:39 map -r-------- 1 root root 1424782 2004-09-29 03:05 vmlinuz -rw-r--r-- 1 root root 1248111 2004-06-14 20:29 vmlinuz-ide-2.4.26 -r-------- 1 root root 1366029 2004-10-01 07:30 vmlinuz.old Maybe I should retry recompiling the kernel? Thanks again. |
assuming your top post means
CONFIG_SMP=y if you have 4 G of ram CONFIG_NOHIGHMEM=n CONFIG_HIGHMEM4G=y 2) The reason I asked the size of your new kernel is that grub can boot kernels up to 1440Kb in size 3) you may also consider the following to assist (=yes) CONFIG_PREEMPT=y for speed CONFIG_MODULE_FORCE_UNLOAD=y under loaded mod support so you can compile more drivers than you think you need but won't be forced to reboot (according to LinuxUser & Developer magazine) 4) you can of course make most things modules but then you are forced to have a bigger initrd image to get your hardware recognised. try on your booted system lspci cat /proc/cpuinfo to confirm some of your stuff |
Remove math emulation, that's 66k right there.
|
root@cerveza:~# lspci
00:00.0 Host bridge: Intel Corp. 440FX - 82441FX PMC [Natoma] (rev 02) 00:0d.0 PCI bridge: IBM IBM27-82351 (rev 01) 00:0f.0 PCI bridge: IBM IBM27-82351 (rev 07) 00:10.0 Network controller: Compaq Computer Corporation Netelligent 10/100 TX PCI UTP (rev 10) 00:12.0 Network controller: Compaq Computer Corporation Netelligent 10/100 TX PCI UTP (rev 10) 00:14.0 EISA bridge: Compaq Computer Corporation PCI to EISA Bridge (rev 07) 01:06.0 VGA compatible controller: Cirrus Logic GD 5430/40 [Alpine] (rev 22) 01:07.0 Network controller: Compaq Computer Corporation Netelligent Integrated 10/100 TX UTP (rev 10) 01:09.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 03) 02:00.0 Unknown mass storage controller: Compaq Computer Corporation Smart-2/P RAID Controller (rev 03) I have a Proliant 2500 Dual Pentium Pro 200MHZ with 512 megs of ram. my lilo.conf shows what I have to do to get 512 megs avail when 16 is only shown (mem=exactmap mem=640K@0 mem=511M@1M) root@cerveza:~# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 1 model name : Pentium Pro stepping : 9 cpu MHz : 199.466 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov bogomips : 397.31 There's the cpuinfo ... only shows one CPU which is of course PPRO. CONFIG_PREEMPT=y for speed CONFIG_MODULE_FORCE_UNLOAD=y I'll try these to see what changes it makes but currently my SMP kernal boots with a Kernel Panic. Not sure why as I only changed the SMP to YES and the max CPUs to 2. |
The reason I asked the size of your new kernel is that grub can boot kernels up to 1440Kb in size
Where did you see that ? |
it probably sounds like boasting but heres my updated tutorial look for the emergency boot of large kernels on how to use 2 or 3 floppies .
as one floppy is devoted to the kernel its theoretical size is 1440 Kb http://www.linuxquestions.org/questi...86#post1208786 |
All times are GMT -5. The time now is 02:42 AM. |