LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 04-30-2006, 12:25 AM   #1
ViROID
LQ Newbie
 
Registered: Apr 2006
Posts: 10

Rep: Reputation: 0
No grub or lilo, what file contains boot menu?


I finally managed to get a kernel compiled under FC5 (they don't make it easy do they..) and I copied over the bzImage to /boot/vmlinuz-2.6.16-1.2096 and the System.map file to /boot/system.map. My delima now is that I'm not using Lilo or Grub and I dont know where the bootmenu configuration file is to add the new kernel option. If someone could point me in the right direction, that would be great. =)

/etc/grub.conf exists, its flashing red, which means is a symbolic link right? If I read this correctly it pointed to /etc/grub/grub.conf, which doesnt exist because grub isnt installed. (That I'm aware of)

...V
 
Old 04-30-2006, 12:31 AM   #2
IBall
Senior Member
 
Registered: Nov 2003
Location: Perth, Western Australia
Distribution: Ubuntu, Debian, Various using VMWare
Posts: 2,088

Rep: Reputation: 62
Flashing red means a broken symbolic link, which is consistent with /etc/grub/grub.conf not existing (ie GRUB not installed).

If you are not using GRUB or LILO, then you need to add an entry to that boot loaders config file to point to the newly installed kernel. Unfortunatly, we can not help unless we know what boot loader you are using. The default with Fedora Core 5 is GRUB.

--Ian
 
Old 04-30-2006, 12:36 AM   #3
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
Some observations:

1. how do you know grub is not installed (anaconda installs grub by default and lilo is the only other option. To have neither, you would have had to remove them and add something else.

2. my grub.conf is in /boot/grub/grub.conf - some folk have it as /boot/grub/menue.lst

3. symbolic links are light blue on my system (FC4). However, this is configurable: dir_colors(5)... flashing means an orphan - a link to a file that dosn't exist. Which is fair enough, because it is pointing to the wrong directory. (see point 2)

Last edited by Simon Bridge; 04-30-2006 at 01:26 AM. Reason: clarification
 
Old 04-30-2006, 12:45 AM   #4
ViROID
LQ Newbie
 
Registered: Apr 2006
Posts: 10

Original Poster
Rep: Reputation: 0
Okay... So, I'm a moron? according to yum, grub is installed. but there is no /etc/grub/grub.conf

whereis grub

returns grub: /sbin/grub /etc/grub.conf /usr/share/grub /usr/share/man/man8/grub.8.gz
 
Old 04-30-2006, 01:18 AM   #5
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
have you looked in /boot/grub?

$ whereis grub
grub: /sbin/grub /etc/grub.conf /usr/share/grub /usr/share/man/man8/grub.8.gz

... see, I get the same, and grub is installed on my system.
(note /sbin/grub is the grub executable - it is installed)
See the whereis man file for why this dosn't find what you are looking for.

However:

$ locate grub.conf
$ su
Password:
# locate grub.conf
/boot/grub/grub.conf



See?

Last edited by Simon Bridge; 04-30-2006 at 01:25 AM.
 
Old 04-30-2006, 01:34 AM   #6
ViROID
LQ Newbie
 
Registered: Apr 2006
Posts: 10

Original Poster
Rep: Reputation: 0
I'm so confused here... I've been trying to find this grub.conf file for the last ten minutes, there was a flashing red /etc/grub.conf and now its light blue, linking to /boot/grub/grub.conf. Right after I copied my bzImage and System.map files to the /boot folder, I went into /boot and those were the only two files in there, now I see the grub folder, lost+found, the config/system.map/vmlinuz/initrd files for 2.6.16-1.2054_FC5smp and 2.6.16-1.2096_FC5smp kernels.

I booted into the 2096 kernel, some of my devices didnt work, so I assume thats the kernel I compiled, how the heck did it get into the menu if I didnt add it? and I named the one I copied vmlinux-2.6.16-1.2096, I dont recall adding _FC4smp to it. Blah.

.V
 
Old 04-30-2006, 01:54 AM   #7
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
Quote:
I've been trying to find this grub.conf file for the last ten minutes
Did you find it?

Quote:
I copied my bzImage and System.map files to the /boot
I think you are supposed to do "make install" (or something like that) at the end of compiling everything. This target will copy the required files and edit the boot.conf for you. I think it even makes the initrd for you.[edit: hmmm... I don't see that target in my makefile here...]

This is for 2.6 kernels. With the 2.4 kernels, yes, you had to go right to the very top of the source tree to find the image and then manually copy it to /boot, and manually edit grub.conf ... are you, perhaps, using an old howto?

Quote:
I named the one I copied vmlinux-2.6.16-1.2096
How did you "name" it?
The kernel "name" in the grub menue is read from the grub.conf file. If you have not edited the grub.conf file, you have not "named" the entry.

Last edited by Simon Bridge; 04-30-2006 at 02:10 AM.
 
Old 04-30-2006, 02:12 AM   #8
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
For more on compiling the kernel:
http://www.kernelnewbies.org/
http://www.linuxchix.org/content/cou...ernel_hacking/

It seems I stand corrected ... interestingly, neither of these howtos suggest creating a new initrd ... perhaps because 2.6.x has initramfs support. Still, I see initrd's in /boot still.

Last edited by Simon Bridge; 04-30-2006 at 02:16 AM.
 
Old 04-30-2006, 10:29 AM   #9
ViROID
LQ Newbie
 
Registered: Apr 2006
Posts: 10

Original Poster
Rep: Reputation: 0
I thought of something after I got some sleep.. I was compiling in my user account, later when I was searching for grub and stuff, I believe I was su'd to root.. I assume most of the files and directories in /boot are owned by root correct, therefore I might not have seen files owned by root? I can't test that at the moment, I've got another computer hooked up too the monitor and keyboard because I couldnt find my KVM switch last night.

Quote:
Originally Posted by Simon Bridge
Did you find it?

I think you are supposed to do "make install" (or something like that) at the end of compiling everything. This target will copy the required files and edit the boot.conf for you. I think it even makes the initrd for you.[edit: hmmm... I don't see that target in my makefile here...]

How did you "name" it?
The kernel "name" in the grub menue is read from the grub.conf file. If you have not edited the grub.conf file, you have not "named" the entry.
Let's see... If I recall I did a make oldconfig, make menuconfig, make bzImage, make modules, cp /arch/boot/noarch/bzImage /boot/vmlinuz-2.6.16-1.2096, cp System.map /boot,make modules_install. It was at this point that I started looking for the grub.conf file and couldnt find it. I then rebooted the computer to figure out which bootloader I was using and it was infact grub, I noticed there were two entries in the menu, one being a 2054 kernel, and the other being the 2096 kernel.

I'm thinking that I may have had yum download the 2096 kernel update, which means the second entry in the grub boot menu is the one yum installed?? If its a FC5 build, why wouldn't my sound card be supported by default? It was with the 2054_FC5 kernel. Who knows.. Thats what lead me to believe that the 2096 entry was the one I compiled. But anyhow..

V
 
Old 04-30-2006, 09:55 PM   #10
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
I'm sorry - can I be clear about this: did you find your grub.conf file?

How could you have done "yum upgrade kernel" and not know about it?

This kernel you were compiling... was it supposed to be a vanilla kernel?

Possibly, if you had hand-compiled a kernel, and missed a crucial driver, then yum-upgrade would simply copy the mistake to a newer version.

If you were compiling a vanilla kernel, not a distro one, then the oldconfig file won't be present... so make oldconfig will just load the defaults. This won't be obvious from the menuconfig ... you should run "make gconfig" instead.

Some of your hardware dosn't go, therefore, because you failed to compile for their support. This usually takes several goes: I remember I kept missing out either usb or lp support on my first tries. Crucial settings can be in unexpected places. I found if I went through every single branch of the gconfig tree, and read all the notes on everything, while carefully holding everything I needed in mind, I could get it right.

Once you've got it right once, you save the configuration file, and make oldconfig will work.

OR: you down;oad the distro kernel source, which includes the oldconfig settings as well. This is what you do if you want to add extra functionality into the kernel (like ntfs support).

On the whole, I'm not sure anyone can figure out what has been going on. You seem to only have a vague idea about what you may have done (evidence, you don't know if you use grub or not, you don't realise the existance of the grub executable means grub is installed, then you don't know if you did a yum upgrade or not...)

Quote:
Originally Posted by ViROID
Okay... So, I'm a moron?
I wouldn't go that far ... but if I were you, I'd start keeping a log (longhand) of everything you do when you fiddle with your system like this. This is an established scientific approach which can fish you out of even tougher places than this.
 
Old 04-30-2006, 10:00 PM   #11
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
hmmm ... thinking about it: you want to know if your kernel compile attempt and the entry in the grub menue are one and the same thing.

This should be easy - the standard kernels go under /usr/src/kernels (show me the content of this directory)

Now: where did you put the kernel source that you were compiling? (Assuming you know, of course...)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
need to access /boot/grub/menu.lst and /boot/grub/device.map neouto Linux - Newbie 8 09-04-2005 12:45 PM
Setting password on grub, wha to do after changing default values in /boot/grub/menu. sarajevo Linux - Security 1 08-17-2005 09:01 PM
Lilo and Grub menu list merger.... Rubedogg Linux - Newbie 2 03-24-2005 07:47 PM
lilo and openmosix was just installed and was added to lilo boot menu but.. kublador Linux - Software 0 06-18-2003 02:59 AM
LILO Boot Menu Everest63 Linux - General 1 02-26-2001 08:06 AM


All times are GMT -5. The time now is 01:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration