Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
tools/build bootsect setup compressed /vmlinux.out CURRENT > zImage
Root Device is (22,1)
Boot Sector is 512 bytes
Setup is 4380 bytes
System is 285 bytes
sync
Leaving .....arch/i386/boot
I used to be able to build bootable floppies without issue but something must have changed.....
Any help/pointer appreciated. I am guessing the issue is nothing to do with the kernel as such but something to do with the bootloader not being happy?
ye it is an old 486. I needed to rebuild the kernel because of a change of network card.
Its 2.0.40 running on 486 building kernels and booting of floppies used to work fine on this machine - last build was done about 18 months ago.
I don't know all the caused of getting a reboot after "Loading.........." but before "Uncompressing Linux" that suggests that the bootloader has some problem?
My latest attempt is that I have grabbed an archive of the 2.0.20 kernel and created a bare minimum kernel and built a zImage and copied to a floppy. That still has the issue of the computer rebooting right before the "Uncompressing Linux" message. I blank the floppy first to made sure the image that I create is the image that is the one on the floppy.
I have now had the idea to copy vmlinux straight to the floppy....That will get round the need to uncompress the kernel.... I haven't had a chance to try that yet.
Here is an update: The vmlinux idea didn't work as the machine started reading the disk and then just got stuck at a blank screen.
The last time I built a successful floppy was November 2015 which was kernel 2.0.40
I am guessing the issue must be some environmental wherby something goes wrong creating the zImage/vmlinux. If any old hands have any ideas that would be really helpful.
What I am going to try now is to build a zImage on a different system (build a kernel targeted at 486). That should be a way to create a successful bootable image.
Thanks for spending the time looking at this question.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.