Kernel Upgrade Problem

[flebber]

Hi am having problem with the kernel upgrade,I am using slackware 10.1 and upgrading from Kernel 2.4.29 to 2.6.11.7 these are the instructions I am following. I have taken them from vaariuos places as different issues have arised, just wondering what could be going wrong after I reboot from the upgrade I am ending up with the Bios data check going ok but then a black screen and nothing works any clues?

First, need to edit lilo.conf.

pico /etc/lilo.conf

Add this to your config...you can just copy what is there and add the .old stuff.

image = /boot/vmlinuz.new

root = /dev/hda1

label = slack.new

read-only


Note: Replace /dev/hda1 with the correct location of your root partition.

Now we need to edit the Makefile to make sure your new kernel is copied to the appropriate directory.

If you are using 8.1 or later, open /usr/src/linux/Makefile in a text editor, scroll to line 74 and
uncomment the the line #export INSTALL_PATH=/boot.
For 8.0 you must leave this line commented.

So...cd /usr/src/linux

pico Makefile

scroll to line 74 and
uncomment the the line #export INSTALL_PATH=/boot.
For 8.0 you must leave this line commented.

From /usr/src

rm -f linux
ln -s linux-2.6.0 linux
cd /linux

make mrproper

Then copy your existing .config to your new kernel source tree...

cp /usr/src/linux-2.4.?/.config /usr/src/linux

I have used all these options in different installs largely I am using Make menuconfig,
just used the others to see if i got a better result.

make oldconfig (to use your old config and choose to add/not add the new options)
or...
make menuconfig (to use your old config and tweak further)
or...
make whatever other type you like (xconfig,gconfig,etc.)

Just exit and save the configuration, then...

make

At this point I am having to update Vmlinuz.new in lilo with the following which I can'do prior
as Bzimage and System.map aren,t in the boot directory before the make command

here you will be in /usr/src/linux-2.6.11

cp /usr/src/linux/arch/i386/boot/bzimage /boot/vmlinuz.new
cp System.map /boot/Syatem.map-2.6.11
cp .config /boot/config-2.6.11

cd
Here you should be in system@home:#

cd /boot
cp System.map System.old
ln -sf System.map-2.6.11 System.map

Then I have finished off a few different ways

su -c "make modules_install"
make install

or

Make bzImage
Make Install

or

Make && Make Modules_install
Make Install

In all cases I have finished with the "lilo" command to make sure it updates without error, but
it does not seem to work on reboot i am coming to "data bios check successful" and then the screen
is going blank and thats where it all ends.

Can you see where I have gone wrong?

 

[jstreich]

Lilo is a three stage loader... The first this it prints is:
lilo (in various parts) -- if your not seeing this at all, then lilo is not installed properly (stage 1 was not able to run). If you see "li" but are missing the "lo", it was unable to load stage 2... This means lilo is installed but it's not set up right. If you get the whole thing "lilo" and or you get to the menu (or Linux STARTS to boot), and then panics, the Kernel isn't setup correctly.

1.) My advice, install GRUB.
2.) If you HAVE to use lilo, makesure it's installed to the MBR and not just the "front of the disk"
3.) Always keep Knoppix arround -- it is VERY useful.

[plug=shameless]

http://game-master.us/phpx-3.4.0/

[/plug]

 

[stefanwagner]

And lilo didn't tell you of errors?

I would never remove an old kernel, before successfully booting the new one, but that's perhaps too late, and wouldn't had helped, if you don't get to the 'kernel-panic' message.

Did you have a

boot=/dev/hda

entry in lilo.conf?

seeking a job as java-programmer in Berlin:

http://home.arcor.de/hirnstrom/bewerbung

 

[flebber]

This is my Lilo.conf

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdc=ide-scsi"
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga = 773
# 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 @ 1280x1024x64k
# vga=775
# 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
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda5
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz-2.6.11
root = /dev/hda5
label = Slackware.vec
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz-2.6
root = /dev/hda5
label = Slackware-2.6
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends

 

[stefanwagner]

did the vga=773 entry work before?

Select an entry and add manually vga=ask, then start with default (80x25)

lilo: Slackware.vec vga=ask

seeking a job as java-programmer in Berlin:

http://home.arcor.de/hirnstrom/bewerbung

 

[AP81]

flebber,

You have complicated things for yourself a little.

I have slackware 10.1 working perfectly with 2.6.11.3. Don't copy a config file from 2.4.xx to a 2.6.xx.xx (if you are). You are better of starting fresh. A couple of things that might catch you out with your kernel compilation: Make sure you have DMA enabled, make sure you enable support for your root filesystem (not as a module- otherwise your system will be unbootable), also compile ALSA as a module (as well as your soundcards - trust me on this one). I am guessing you have a wrong VGA setting (or have compiled something out of your kernel that you need)

This is what it do:

1. Untar kernel source to /usr/src
2. Remove /usr/src/linux: rm -fr linux
3. create symlink: ln -s /usr/src/linux-2.6.11.3 linux
4. go into linux directory: cd linux
5. make menuconfig
6. make bzImage
7. make modules
8. make modules install
9. copy kernel: cp arch/i386/boot/bzImage /boot/vmlinuz-new
10. copy config: cp .config /boot/config-new
11. copy System.map cp System.map /boot/System.map-new
12. create symlinks:
- cd /boot
- rm vmlinuz
- rm System.map
- rm config
- ln -s vmlinuz-new vmlinuz
- ln -s config-new config
- ln -s System.map-new System.map-new
13. Update your entries:
- point kernel to vmlinuz
- point root to /dev/hdx
14. Install lastest nVidia drivers








------------------------------------
There's no place like 127.0.0.1
------------------------------------

 

[stefanwagner]

Don't remove /usr/src/linux, because you will often need the asm-section (step 2).

seeking a job as java-programmer in Berlin:

http://home.arcor.de/hirnstrom/bewerbung

 

[AP81]

stefanwagner (Programmer)
10 May 05 19:46
Don't remove /usr/src/linux, because you will often need the asm-section (step 2).

obviously, that's why you create it again :

2.  Remove /usr/src/linux: rm -fr linux
3.  create symlink: ln -s /usr/src/linux-2.6.11.3 linux

------------------------------------
There's no place like 127.0.0.1
------------------------------------

 

[stefanwagner]

I once deleted it myself, and got an error on 'make menuconfig'.

And - not being sure about that:
Often you compile applications/ libraries, which look at
/usr/src/linux, and that code needn't be mixed with actual kernel headers.
While the kernel is updated frequently, applications stay for longer times.

seeking a job as java-programmer in Berlin:

http://home.arcor.de/hirnstrom/bewerbung

 

[AP81]

I don't know how you compile kernels, but I usually do it from within the /usr/src/linux directory. Now if you already have another kernel source symlinked to the /usr/src/linux directroy, how are you supposed to compile another kernel?




------------------------------------
There's no place like 127.0.0.1
------------------------------------

 

[jrjuiliano]

More often than not, if you can use make menuconfig from within the symlinked directory you didn't point to the right directory. I've done this a few times typing too fast.

 

[jrjuiliano]

Uh, typo. That should read "can't use make menuconfig...

 

[stefanwagner]

/usr/src/linux-2.6.11.7

seeking a job as java-programmer in Berlin:

http://home.arcor.de/hirnstrom/bewerbung