LinuxQuestions.org - [SOLVED] After upgrading 64-current to 2.6.33, still boots 2.6.32.7 and loads no modules

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - After upgrading 64-current to 2.6.33, still boots 2.6.32.7 and loads no modules (https://www.linuxquestions.org/questions/slackware-14/after-upgrading-64-current-to-2-6-33-still-boots-2-6-32-7-and-loads-no-modules-797802/)

After upgrading 64-current to 2.6.33, still boots 2.6.32.7 and loads no modules

Hi, I've been trying 64-current for a little while, and I just tried using slackpkg to install-new/upgrade-all, which included the kernel upgrade to 2.6.33. Long story short, I'm somehow booting the wrong kernel, and that causes modprobe not to be able to load any modules.

After a fresh boot:

Code:

# uname -r

2.6.32.7

# lsmod

Module                    Size  Used by

#

There aren't any modules (I think) because /lib/modules/2.6.32.7/ doesn't exist, and everything is in /lib/modules/2.6.33/

In /etc/lilo.conf, I have it pointing to the right image:

Code:

image = /boot/vmlinuz

  root = /dev/sda2

  label = Linux

  read-only

/boot/vmlinuz is a symlink to /boot/vmlinuz-huge-2.6.33, which apparently automatically replaced the 2.6.32.7 image with the upgrade-all.
I have run lilo to reinstall the configuration, but it didn't change anything.

So, I'm somehow booting the wrong kernel, and I have no idea why. Is there something obvious I'm missing, or am I looking at the wrong problem? I really don't have much experience with messing with the kernel (a main reason I switched to slackware was to learn all sorts of things), so I'm not sure where to look.

Thanks!

You run lilo after this upgrade?

Quote:

Originally Posted by LuckyCyborg (Post 3911796)

You run lilo after this upgrade?

I did. The output was simply:

Code:

# lilo

Added Linux *

#

And it still boots 2.6.32.7

Edit: I added lba32 to lilo.conf, which suppressed a warning from lilo, but didn't affect anything else.

to help you more effectively, can you post the output of "fdisk -l", "ls -la /boot", "lilo -v" (the -v option gives you other hints) and the full lilo.conf? I think, just a guess from the info you gave us, that you are installing the bootloader in a place and booting from another.
you should have a look also in the bios boot sequence.

@Abraxel: Your /boot/vmlinuz symlink point where? Wich file?

it seems he wrote it in his post, to /boot/vmlinuz-huge-2.6.33 :)

did you run

make modules_install

after you you made your kernel?

Quote:

Originally Posted by ponce (Post 3911814)

Sure, no problem.

fdisk -l
(for reference, /dev/sda2 is /, /dev/sda3 is /home, and /dev/sdb is just a spare hard disk that shouldn't have anything to do with this)

Code:

Disk /dev/sda: 640.1 GB, 640135028736 bytes

255 heads, 63 sectors/track, 77825 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x000ee0e4



  Device Boot      Start        End      Blocks  Id  System

/dev/sda1              1        1045    8393931  82  Linux swap

/dev/sda2  *        1046      14100  104864287+  83  Linux

/dev/sda3          14101      77825  511871062+  83  Linux



Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes

255 heads, 63 sectors/track, 121601 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x76f0ab2b



  Device Boot      Start        End      Blocks  Id  System

/dev/sdb1              1      121601  976760001  83  Linux

ls -la /boot

Code:

total 11799

drwxr-xr-x  2 root root    624 2010-03-25 07:34 ./

drwxr-xr-x 23 root root    536 2010-03-24 21:57 ../

lrwxrwxrwx  1 root root      37 2010-03-24 21:35 README.initrd -> /usr/doc/mkinitrd-1.4.3/README.initrd

lrwxrwxrwx  1 root root      22 2010-03-24 21:22 System.map -> System.map-huge-2.6.33

-rw-r--r--  1 root root 1512231 2010-02-27 17:45 System.map-generic-2.6.33

-rw-r--r--  1 root root 2508251 2010-03-07 12:36 System.map-huge-2.6.33

-rw-r--r--  1 root root    512 2010-02-26 11:54 boot.0800

-rw-r--r--  1 root root    512 2010-02-25 06:12 boot.0802

-rw-r--r--  1 root root    168 2010-02-25 06:12 boot_message.txt

lrwxrwxrwx  1 root root      18 2010-03-24 21:22 config -> config-huge-2.6.33

-rw-r--r--  1 root root  101662 2010-02-27 17:45 config-generic-2.6.33

-rw-r--r--  1 root root  101615 2010-03-07 12:36 config-huge-2.6.33

-rw-r--r--  1 root root    5040 2010-02-14 21:09 diag1.img

-rw-r--r--  1 root root  17932 2010-02-14 21:09 diag2.img

-rw-------  1 root root  83968 2010-03-25 07:34 map

-rw-r--r--  1 root root  17318 2008-12-08 19:56 slack.bmp

lrwxrwxrwx  1 root root      19 2010-03-24 21:22 vmlinuz -> vmlinuz-huge-2.6.33

-rw-r--r--  1 root root 2511152 2010-02-27 17:45 vmlinuz-generic-2.6.33

-rw-r--r--  1 root root 5173888 2010-03-07 12:36 vmlinuz-huge-2.6.33

lilo -v

Code:

LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger

Development beyond version 21 Copyright (C) 1999-2006 John Coffman

Released 19-Feb-2007 and compiled at 20:09:28 on Feb 14 2010



Reading boot sector from /dev/sda2

Using BITMAP secondary loader

Calling map_insert_data

Mapping bitmap file /boot/slack.bmp

Calling map_insert_file



Boot image: /boot/vmlinuz -> vmlinuz-huge-2.6.33

Added Linux *



Writing boot sector.

/boot/boot.0802 exists - no boot sector backup copy made.

And /etc/lilo.conf

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

# Append any additional kernel parameters:

append=" vt.default_utf8=0"

boot = /dev/sda2

#boot = /dev/sda



# Get rid of warning "LBA32 addressing assumed"

lba32



# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

  bitmap = /boot/slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

  bmp-colors = 255,0,255,0,255,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

  bmp-table = 60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

  bmp-timer = 65,27,0,255



# Standard menu.

# Or, you can comment out the bitmap menu above and 

# use a boot message with the standard menu:

#message = /boot/boot_message.txt



# Wait until the timeout to boot (if commented out, boot the

# first entry immediately):

prompt

# Timeout before the first entry boots.

# This is given in tenths of a second, so 600 for every minute:

#timeout = 1200

timeout = 60

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# VESA framebuffer console @ 1024x768x64k

vga = 791

# Normal VGA console

# vga = normal

# VESA framebuffer console @ 1024x768x64k

# vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

# vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/sda2

  label = Linux

  read-only

# Linux bootable partition config ends

I hope that helps! I'm still pretty lost.

Quote:

Originally Posted by Daedra (Post 3911959)

did you run

make modules_install

after you you made your kernel?

I did not... but I didn't actually make my kernel, I just upgraded the slackware packages. Do I still need to run "make modules_install", or was that done automatically? Looking in /lib/modules/2.6.33, which was apparently created by the upgrade, it looks like all the aliases and dependencies and modules and such are there, which makes me suspect that it's already been done. Am I assuming too much or just confused?

I think mystery is solved: you are booting from the MBR of /dev/sda, where the kernel has installed in the past.
after, you probably changed

Code:

boot=/dev/sda

Code:

boot=/dev/sda2

in /etc/lilo/conf (you also commented the original one) so the next execution of lilo installed it to /dev/sda2, in the partition instead of the MBR of the disk.
solution should be to change it back to the original, execute lilo and reboot.

hoping that wasn't something you left trying to install it also in the partition. ;)

as last resort trying to disconnect the spare hard disk can be an option: if your system won't boot anymore, lilo it's installed there :D

Quote:

Originally Posted by ponce (Post 3912113)

I think mystery is solved: you are booting from the MBR of /dev/sda, where the kernel has installed in the past.
after, you probably changed

Code:

boot=/dev/sda

Code:

boot=/dev/sda2

That worked! Thank you! I'm trying to remember why I changed that in the first place (I'm fairly certain I was trying to fix something during the initial installation, but I can't for the life of me remember what).