RE: kernel too big + histoire drole
En réponse à Ludovic Desfontaines [EMAIL PROTECTED]: C'est une bonne question. Comment forcer lilo à l'utiliser, je ne sais pas. Maitenant, il faut voir ou tu a récupérer ce noyau... Lu sur www.debian.org : Package: kernel-image-2.4.16-686 2.4.16-1 Linux kernel image for version 2.4.16 on PPro/Celeron/PII/PIII. This package contains the Linux kernel image for version 2.4.16 on Pentium Pro/Celeron/Pentium II/Pentium III, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. Pour forcer lilo à utiliser ce nouveau noyau, il faut être sur que les vmlinuz et System.map définis dans /etc/lilo.conf sont bien ceux installés par le package (soit à la racine /, soit dans /boot). Et comme je parlais d'histoire drôle, je vous fait part d'une expérience personnelle intéressante : quand j'ai installé ma première debian, c'était après une longue expérience de RedHat, et lors de la définition des partitions j'ai involontairement monté le répertoire /usr/local/ sur la partition où se trouvait l'ancienne install de RedHat, et je n'ai pas pensé à la formater. Conséquence : ma Debian utilisait les bin et les lib de l'ancienne RedHat ! En particulier j'étais incapable de compiler correctement le moindre noyau (kernel too big) jusqu'à ce que j'ai eu l'idée salvatrice de lancer un which lilo ... Bref une expérience un peu conne, mais qu'il est bon de connaitre parfois :o) A+ ! Olivier
Re: Kernel too big.
Kent West wrote: I checked the archives, but didn't find much on this. I've recompiled my kernel (using bzImage) to provide sound support, and now I'm getting a vmlinuz is too big message when I try to run lilo. My old kernel was 715260, and my new one is 749612. I've gone through make config and recompiled at least four times tonight, removing everything I thought I could live without, and I've changed everything to modules that could be changed to modules. Am I doing something wrong? Or have I really run into a size limitation? If the latter, does this not spell trouble for Linux, in that an average person with an average machine on an average LAN doing average things can't get all his average stuff into a kernel? Any suggestions would be welcome. sounds like your trying to use the vmlinuz file from /usr/src/linuxXXX/vmlinuz, you should be using the file /usr/src/linuxXXX/arch/i386/boot/bzImage ;assuming an Intel machine. -- John Foster AdVance-Computing Systems [EMAIL PROTECTED] ICQ# 19460173
Re: Kernel too big.
John Foster wrote: Kent West wrote: I've recompiled my kernel (using bzImage) to provide sound support, and now I'm getting a vmlinuz is too big message when I try to run lilo. John Foster answered: sounds like your trying to use the vmlinuz file from /usr/src/linuxXXX/vmlinuz, you should be using the file /usr/src/linuxXXX/arch/i386/boot/bzImage ;assuming an Intel machine. -- John Foster AdVance-Computing Systems [EMAIL PROTECTED] ICQ# 19460173 That was it! Thank you!
Kernel Panic (RE: kernel too big)
Thanks to every one for the help with my first problem. Finaly I could compile the new kernel, but I could not start the system with the new kernel. I get this message: 'kernel panic: no init found. Try passing init = option to kernel' What is the value of 'option'? How I pass this value to the kernel? I am using the kernel 2.2.1 in the Debian C.D. Thanks, Camilo Alejandro Arboleda
Re: Kernel Panic (RE: kernel too big)
Camilo Alejandro Arboleda wrote: Thanks to every one for the help with my first problem. Finaly I could compile the new kernel, but I could not start the system with the new kernel. I get this message: 'kernel panic: no init found. Try passing init = option to kernel' What is the value of 'option'? How I pass this value to the kernel? You should never need to do so. By default, /sbin/init is run. If this is suddenly not available to your kernel, it suggests that you have not included support for your hard disk in the kernel. (Your root disk support cannot be a module; it must be in the kernel itself.) My guess is that the BIOS is loading your kernel, but the kernel doesn't know how to read the disk. Do your boot messages from the kernel suggest that it is finding the hard disk? Look for references to /dev/hda, or /dev/sda if it's SCSI. -- Vote against SPAM: http://www.politik-digital.de/spam/ Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 Fear not, for I am with thee; be not dismayed, for I am thy God. I will strengthen thee and I will help thee; yea, I will uphold thee with the right hand of my righteousness. Isaiah 41:10
Re: Kernel too big
[This message has also been posted.] On 4 Jun 99 14:31:06 GMT Camilo Alejandro Arboleda [EMAIL PROTECTED] wrote: My name is Camilo. I am trying to compile the Linux kernel 2.1. . . . why? 2.2 is the current stable version. 2.1 is the previous development version, but all the features of 2.1 should be in 2.2, only more stable. When I compile the kernel with the command 'make bzImage' the image generated has a size of about 800.000 bytes, and when I try to install the image using 'liloconfig' I get the error 'kernel too big', but I cannot remove more drivers from the kernel without lose features that I really need. What is the maximum size of the kernel? Is possible to increase this size? The max size on Intel boxes is supposed to be 512MB or slightly more. This still goes back to the ancient 640K barrier in real mode. Don't remove any drivers, but compile them as modules instead of static parts of the kernel. For instance, if you need vfat support for Windows disks, or ISO9660 for CDs, or sound support, or PPP for a modem, you can compile all of those as modules and they won't increase the size of the kernel at all. See the Kernel-HOWTO. -- Carl Fink [EMAIL PROTECTED] Manager, Dueling Modems Computer Forum http://dm.net
Re: Kernel too big
Camilo Alejandro Arboleda wrote: When I compile the kernel with the command 'make bzImage' the image generated has a size of about 800.000 bytes, and when I try to install the image using 'liloconfig' I get the error 'kernel too big', but I cannot remove more drivers from the kernel without lose features that I really need. You could try to put some drivers in modules instead of compiling everything straight into the kernel itself? The usage of modules could reduce the kernel size quite a lot, I think. -Remco
Re: Kernel too big
On Fri, Jun 04, 1999 at 09:31:06AM -0500, Camilo Alejandro Arboleda wrote: When I compile the kernel with the command 'make bzImage' the image generated has a size of about 800.000 bytes, and when I try to install the image using 'liloconfig' I get the error 'kernel too big', but I cannot remove more drivers from the kernel without lose features that I really need. Use modules. If you're using `make menuconfig', type M at the more esoteric drivers. Make sure you have enough features to get booted up and reading your root partition - don't make things like your default HD interface (IDE, SCSI) into modules - but do so for most other things, like PPP and parallel port interfaces and so on. What is the maximum size of the kernel? Is possible to increase this size? No idea, and I doubt it. Isn't it a LILO problem? -- alisdair mcdiarmid [everything is plastic and we're all going to die]
Re: Kernel too big
No idea, and I doubt it. Isn't it a LILO problem? No, it is because the BIOS has to load the kernel, and because the kenrel starts in real mode, not protected mode. There is a thorough description in the archives sometime this earlier this year. Carl
