Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have needed to upgrade my kernel from 2.4.2 to 2.4.18 to support my nic. I have followed the kernel rebuild instructions
make clean
make xconfig
make bzImage
vi lilo.conf
cp /arch/i386/boot/bzImage /boot/vmlinuz-2.4.18
and my system was working great with the new kernel. It even booted first time and the nic was found and working ( i like this linux thing).
However my floppy was unable to read dos fs. The error is
'mount: unable to determine file type and none specified'
The floppy was reading DOS under 2.4.2 kernel. So i figured it was due to the kernel configuration params that relates to DOS fs. So i set
CONFIG_FAT_FS='y'
CONFIG_MSDOS='y'
And then did the build procedure above.
Now when i boot i get the following error
Loading linux-2.4.18 ...................
uncompressigng linux....ok, booting the kernel.
ran out of input data
-- System halted.
Not a good start. If i set the
CONFIG_FAT_FS='n'
CONFIG_MSDOS='n'
and recompile the kernel boots fine. Why?:-/
I have only found one other thread about the above error but there was no response :-(
So my question is
'how do i get my floppy reading dos fs and my kernel to load?'
also normally you should do make modules and make modules_install when you build your kernel, and copy the System.map file to /boot/System.map-2.4.18 and link to it with /boot/System.map
did you build an initrd.img for the kernel, or are you not using one
Last edited by DavidPhillips; 06-15-2002 at 09:22 PM.
I build the msdos fs as modules and then did the modules_install and guess what.... the kernel boots and the floppy is mountable. I guess the msdos support can't be compiled into the kernel.
Never mind i am happy.
make mrproper
make menuconfig
make dep
make clean
make bzImage
make modules
make modules_Install
copy the image to /boot
add entry to lilo.conf
rerun lilo
I have been attempting to rebuild my 2.4.18 kernel. I am having lots of very strange errors depending on what i select on the make xconfig. The latest error is the following.
'invalid compressed format (err=1)' -- system halted."
I guess the error itself explanatory. But what is causing this?
I am doing the following steps. recommended by jayakrishnan.
make mrproper
make menuconfig
make dep
make clean
make bzImage
make modules
make modules_install
copy the image to /boot
add entry to lilo.conf
rerun lilo
Someone has mentioned copying the System.map file to boot but i don't understand why.
I am really confused about this kernel building. Depending on which option are set to 'y' or 'm' i get kernek loading errors from
'run out of input data' ( very common ).
or
The make modules_install generates symbolic link failures on elf.o. What have i done incorrectly?
When i build a kernel myself i normally don't use modules at all but put all the thing i needs directly in the kernel - minus one source of possible trouble.
There are some things that are only available as modules but i don't need them.
I have found that modules_install may not be a bad idea if you have no modules, the mkinitrd will need to see something there, there may be other reasons as well.
Sometimes building a kernel takes one or both of two things.
use the old config as a starting point. Or trial and error to determine what works.
Last edited by DavidPhillips; 06-19-2002 at 04:54 PM.
usually, when I re-compile a kernel, I do the following:
make menuconfig
make dep
make modules
make modules_install
make bzImage
make install
it's much quicker...and I let the Makefile handle the dealing with lilo. much better than what I used to do (try construction a .config file by hand...ouch)
your problem sounds like it's a dependancy. I'd install the msdos support as a module from within menuconfig. it's easier
I believe the problem to have been the way i was saving the config from make xconfig. I was saving the config to an external file, since i didn't know what i was doing i thought it was a good idea at the time. Once i tried saving the file to the default location ( i have no idea where ) it worked OK.
I think i'lll put this down to 'follow the kernel building instructions EXACTLY'
<plug>I usually use buildkernel to compile a kernel<endplug> Since i never get it right the first time and can still do all the configurations it helps a lot. Don't have to mess with make this and that.
I got the 'ran out of input data' for the first time today, grabbed a boot disk, restored the previous config file (which I keep a backup of) and recompiled to as it was before. My problem is tho, that I still get the error
All my numerous problems disappeared when i followed the steps below. My problem was that i wasn't running lilo on the new image. I don't unsderstand what lilo does on the new image but it worked for me. Maybe a guru can shed some light on this?
make mrproper
make menuconfig
make dep
make clean
make bzImage
make modules
make modules_install
copy the image to /boot
add entry to lilo.conf
lilo
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.