Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Find the answer to your Linux question:
New to Linux Forums? Register here for free!
    Linux Forums > GNU Linux Zone > Installation > Boot directly from bzImage kernel image

Forgot Password?
 Installation   Need help or have questions about installing Linux, including dual booting with other distros or Windows? put them here!

Site Navigation
Linux Articles
Linux Forums
Linux Downloads
Linux Hosting
Free Magazines
Job Board
IRC Chat
RSS Feeds


Linux Forum Topics
Linux Forums
Your Distro
Linux Resources
GNU Linux Zone
The Community
Reply
 
Thread Tools Display Modes
Old 10-05-2009   #1 (permalink)
Just Joined!
 
probe's Avatar
 
Join Date: Oct 2009
Location: Belgrade, Serbia
Posts: 21
Boot directly from bzImage kernel image

Hi,

Before few months I succeed to do this, but I didn't write down
how I did it [won't happen again ].

So the problem is how to boot directly from kernel image file bzImage, without
initrd and vmlinuz file.

I know that one part of the problem is to enable drivers for hard disk drive
directly into kernel. But another part of the problem is text in menu.lst file,
which should direct you straight to bzImage file, which is copied into /boot
folder.

Any help ??

thanks
probe is offline  


Reply With Quote
Old 10-06-2009   #2 (permalink)
Linux User
 
hazel's Avatar
 
Join Date: May 2004
Location: Harrow, UK
Posts: 493
You need to have a "stanza" in menu.lst specifying your new kernel.title. For example, here is one that I use:
Code:
	
title         Experimental Debian kernel
root		(hd0,3)
kernel		/boot/bzImage root=/dev/hda4 quiet
savedefault
boot
The "root" line gives GRUB's root, i.e. the partition where menu.lst and the other grub files are. The "kernel" line gives the location of your bzImage and the linux root partition corresponding to it.
__________________
"I'm just a little old lady; don't try to dazzle me with jargon!"
hazel is offline   Reply With Quote
Old 10-07-2009   #3 (permalink)
Just Joined!
 
probe's Avatar
 
Join Date: Oct 2009
Location: Belgrade, Serbia
Posts: 21
Thanks,

this looks exactly like the code in menu.lst I used before few months.
I will just include drivers for HD in block devices and rebuild
kernel and it should work,

thanks again !
probe is offline   Reply With Quote
Old 10-08-2009   #4 (permalink)
Just Joined!
 
Join Date: Oct 2009
Posts: 1
Quote:
Originally Posted by probe View Post
Thanks,

this looks exactly like the code in menu.lst I used before few months.
I will just include drivers for HD in block devices and rebuild
kernel and it should work,

thanks again !
Now I understood the problem that you discussed here. It is helpful for me and everybody. I look forward to contributing your idea.
cincridul is offline   Reply With Quote
Old 10-08-2009   #5 (permalink)
Just Joined!
 
probe's Avatar
 
Join Date: Oct 2009
Location: Belgrade, Serbia
Posts: 21
Hey cincridul,

No problem, thanks. And it is not idea, it works. After you do 'make'
on new kernel, just copy arch/i386/boot/bzImage to /boot/ directory,
and that's it.

And set menu.lst like hazel posted. I think you need to build in your
kernel [directly not as module] hard drive drivers for your
HD (under block devices) and filesystem drivers, and that is all kernel
needs to boot straight just from image,



------------------------------------------------------------------

www.tech-vibe.com
probe is offline   Reply With Quote
Old 10-08-2009   #6 (permalink)
Linux User
 
hazel's Avatar
 
Join Date: May 2004
Location: Harrow, UK
Posts: 493
Yes, you need to build in the driver for your hard drive (IDE or SATA), for the filesystem on it (e.g. ext3) and for the chipset of your drive controller (as reported by the kernel at boot time). For example, I have an Intel motherboard and the kernel reports piix as my disk driver chipset, so I need to have the PIIX_IDE option enabled. Actually most stock kernels have all possible chipsets enabled by default.

You also need to run "make modules_install" before rebooting because some of your initialisation scripts will need to load modules corresponding to your new kernel.
__________________
"I'm just a little old lady; don't try to dazzle me with jargon!"
hazel is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Free Magazines
Run Your Own Web Server Using Linux & Apache - Free 191 Page Preview
Learn about everything you'll need to build and maintain your Linux servers, and to deploy Web applications to them.
subscribe
Open Source Security Myths Dispelled
Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization
subscribe
InformationWeek
InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology.
subscribe



All times are GMT. The time now is 08:15 AM.






© 2000 - 2009 - All Rights Reserved - Property of  MAS Media

Content Relevant URLs by vBSEO 3.3.0 RC2