| View previous topic :: View next topic |
| Author |
Message |
Blademan
Developer
Joined: 05 Oct 2002
Posts: 116
|
 Posted: Sat Feb 01, 2003 10:32 pm Post subject: Stupid kernel question |
 |
|
| I just compiled a kernel withthe 2.4.19r10 sources, copied it ot /boot, but I still boot up with a r9 kernel. What am I NOT doing? TIA. |
|
| Back to top |
|
 |
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Sat Feb 01, 2003 10:35 pm Post subject: |
|
|
| Maybe mounting /boot before copying bzImage into it. I made this error the first time I updated my kernel in Gentoo. |
|
| Back to top |
|
|
garo
Bodhisattva
Joined: 15 Jul 2002
Posts: 860
Location: Edegem,BELGIUM
|
| Posted: Sat Feb 01, 2003 10:39 pm Post subject: |
|
|
| Quote: | | I just compiled a kernel withthe 2.4.19r10 sources, copied it ot /boot, but I still boot up with a r9 kernel. What am I NOT doing? TIA. |
Did you change the config of your bootloader (lilo,grub,..)?
_________________
My favorite links this month:
- Surf Random
- Web-based SSH
- Stop Spam |
|
| Back to top |
|
|
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Sat Feb 01, 2003 10:41 pm Post subject: wrong kernel |
|
|
Did you change/add to grub to point to the new kernel if you didn't use the same filename as your previous one. It is a good idea to name the new kernel differently (bzImage.date, kernel-2.4.19_r10.date, etc.) then add that new kernel to the grub menu. Test the new kernel, then if your satisfied it works, change the grub menu default to your new kernel. That way you will always have a good working kernel to use. 
Brian |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sun Feb 02, 2003 1:13 am Post subject: |
|
|
If you're using LILO, you need to rerun lilo every time you change kernels.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
kyptin
Tux's lil' helper
Joined: 29 Jun 2002
Posts: 95
Location: UNC (Chapel Hill, NC, USA)
|
| Posted: Sun Feb 02, 2003 5:39 am Post subject: /usr/src/linux |
|
|
| One other thing you might want to do once you're satisfied the new kernel works is change the /usr/src/linux symlink. That probably won't affect booting, but it's a good idea, and you might run into a problem if you don't change it: 'ln -sf /usr/src/newerlinuxpath /usr/src/linux' |
|
| Back to top |
|
|
Blademan
Developer
Joined: 05 Oct 2002
Posts: 116
|
| Posted: Sun Feb 02, 2003 6:11 am Post subject: |
|
|
Thanks for all the help. Let me elaborate. The system has been running fine since Nov. using 2.4.19r9. Emerge -u world brought in r10 sources, and broke my nvidia 3xxx r2 kernel emerge. So I fixed the /usr/src/linux symlink and pointed it to r10 sources. I compiled a new kernel (with MTRR this time) and threw it into /boot. I tried to move the old bzImage, but it's not there, so I just put the new kernel in /boot. An ls shows the following:
| Code: | omega root # ls -l /boot/
total 984
lrwxrwxrwx 1 root root 1 Oct 28 11:42 boot -> .
-rw-r--r-- 1 root root 1000837 Feb 1 02:17 bzImage
omega root # ls -l /boot/boot/
total 984
lrwxrwxrwx 1 root root 1 Oct 28 11:42 boot -> .
-rw-r--r-- 1 root root 1000837 Feb 1 02:17 bzImage
omega root # ls -l /boot/boot/boot/
total 984
lrwxrwxrwx 1 root root 1 Oct 28 11:42 boot -> .
-rw-r--r-- 1 root root 1000837 Feb 1 02:17 bzImage
omega boot # ls -l /usr/src/
total 8
lrwxrwxrwx 1 root root 23 Jan 13 18:01 linux -> linux-2.4.19-gentoo-r10
drwxr-xr-x 16 root root 4096 Feb 1 02:05 linux-2.4.19-gentoo-r10
drwxr-xr-x 15 root root 4096 Dec 3 13:06 linux-2.4.19-gentoo-r9
omega boot # uname -a
Linux omega.dummy.net 2.4.19-gentoo-r9 #1 Sun Oct 6 15:40:34 EDT 2002 i686 Pentium III (Katmai) GenuineIntel GNU/Linux
omega boot # |
What is going on here? |
|
| Back to top |
|
|
royko
n00b
Joined: 02 Feb 2003
Posts: 21
Location: Chicago, IL
|
| Posted: Sun Feb 02, 2003 8:39 am Post subject: |
|
|
did you make sure to mount your boot partition before copying bzImage there?
| Code: | | mount /dev/hdaX /boot |
where X is the number of your boot partition.
If you aren't mounted to that partition, then copying bzImage there doesn't do anything.
/boot has a link in it back to /boot, so /boot/boot is the same as /boot, and /boot/boot/boot is the same as boot. I have the same link. It happened at some point during the install. Not sure why it's there or what it does, but I wouldn't mess with it. It's not causing your problem.
If you DID mount the boot partition and copy bzImage over there, then I don't know what's up, unless you somehow got your bzImage files mixed up. If it is mounted, I'd try compiling kernel again and recopying bzImage.
Btw, it's a good idea to back up the old bzImage. Make sure to do this BEFORE you copy over the new one (obviously). If the current bzImage isn't in /boot, then you haven't mounted your boot partition.
Good luck. |
|
| Back to top |
|
|
Blademan
Developer
Joined: 05 Oct 2002
Posts: 116
|
| Posted: Sun Feb 02, 2003 3:16 pm Post subject: |
|
|
| Thanks. That was it, I hadn't mounted /boot. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sun Feb 02, 2003 7:50 pm Post subject: |
|
|
I recommend the following for people who have separate /boot partitions, unmounted by default: | Code: | # umount /boot
# touch /boot/I_AM_UNMOUNTED |
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
|
Installing Gentoo
