As soon as the other person gets back to me with his opinions and additions or detractions,. removals. I will be getting it ready to send out. One correction in these instructions, the VmLinuz.new should be VmLinuz-2.6.11 as this will better reference the versionaing.

Well have done everything as listed changed # comment out of line 450 in makefile created entries in lilo and done the make && make modules_install and make install, lilo finds it all well but when i boot it does the bios data check successfully and then to a blank screen and thats where it stops....little confused, doesn't give me an idead of where an error would be.

And I created a whole new install when doing this from Kernel-2.6.11.7.

sounds like you made an possible error in one of three places. The Kernel needs to have some pointers to it, .config /boot/System.map-2.6.11.7 VmLinuz-2.6.11.7 config-2.6.11.7 these all reside in the /boot direcoty. Lilo may have not set the settings correctly as it may have had too many lines of information, I have had this happen, it's why I say this. the second is from setting the display incorrectly, depending on your Video card, it can cause a blank screen if it is set wrong. The 3rd is you have made a serious error in the compile and you got what is known as a "Halt" command and it just is not going to respond at all. Take out your Second Slackware CD and boot to it, it is an emergency CD that will boot to your old kernel and allow you to make corrections. Hope that this gives you an idea of wht your problem is.

Hi still having problem with the kernel upgrade, these are the instructions I am following after
I reboot from the upgrade I am ending up with the a black screen and nothing works any clues?

First, we need to edit lilo.conf. Pick your favorite editor...one that is easy for newbies (and I still use this from time to time) is pico.

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?

Suggests if you are using Slackware to boot to the Second CD and let it boot to your hard drive. The second CD is a Emergency/Live CD.

Now from what I have read there is a problem. Conflicting Instructions.

the newly 2.6.11.7 VmLinuz and System.map are in the / directory. They are not in /boot unless you changed the install.sh to reflect where they go.

it will be VmLinuz and System.map

They need to be moved to the /boot as VmLinuz-2.6.11.7 and System.map-2.6.11.7, then open lilo.conf and make your changes. If this still does not work, then I think you have made a serious error in your setup on the build, not in how it is compiled. Did you change all the needed areas to match your hardware profiles??? If this is somehting you missed, then you may have to redo the entire mess. The Defaults are not going to be what everybody has.

I've compiled 2.6.10, and I've got a kernel panic that I don't know what to do about.

Here is some stuff from the boot i wrote down:


nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed


I wrote that down because it looks pretty weird to me, here comes the actual kernel panic:


VFS: Cannot open root device "803" or unknown-block(8,3)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)


I've got two S-ATA disks and a K8N Neo Platinum motherboard ( nForce 3 250Gb). It works perfeclty with the 2.4.29 kernel.

My lilo conf looks like this:

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = 2.4.29
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz-2.6.10
root = /dev/sda3
label = 2.6.10
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

I've just copied the old one and changed it a little, as you can see.

** edit **
I'm using reiserfs and i have compiled reiserfs in the kernel.
I've compiled "SCSI device support -> SCSI low level drivers -> Serial ATA support -> NVIDIA sata support" as well

** /edit **


Seen this before? Kow some way in which I can get more info out of my computer? I don't know where to start looking, really.

I got this from a Failed IDE controller and installed a new one, it caused this, due to a different way the controllers handle the devices.




Should appear as this and have #global settings to minimize the file size.




Ok did you Moduler it, or built in? I don't see how that could make too much difference. I use Reiserfs and bare.i, did you use the jfs.s??

If you cna boot with the Second CD as it is an Emergency Disk, will it boot the drive and get you up and running? Did you try or know this?

what do you mean?

I built it in the kernel, and i use the sata.i 2.4.29 kernel right now.

#Begin global Lilo configuration

information here regarding the files and boot loaders and names. for two there should be label and the rest, 4 lines each

#end global

boot=VmLinuz-2.6.1
name=slack

boot=VmLinuz-2.4.29
name=Main

and so on. I will have to read the Linux bible to get you the correct information, but this is a general idea.

Hmmm...as long as Makefile is edited to uncomment the export path, vmlinuz and System.map will be copied to the /boot directory during "make install".

Yes and also the newer Linux 2.6.11.9 is out.

Ok...I haven't had a chance to toy with 2.6.11.9 yet. I guess I'll have to get moving on that

Lol, yes, I willbe testing it in the next week. I have a new system, so it should work better now, ACPI and all on and should actually get better responses.

I had this problem recently with a clean install of Mandrake v10.0. I did not modify the kernel and got the same 'bios data checking' as above. I am using lilo btw.

The machine was an old fujitsu-siemens scenic machine with i815 chipset. I upgraded the Phoenix bios from:
release 4.06 rev1.06.1214 to release 4.06 rev 1.13.1214.

I rebooted the machine and it booted fine. Hope this helps.

Holy Cow!! this thread is getting outdated very quickly. Since this last post I have a new AMD Sempron 2500+ and 512MB of system RAM so now I can do some more testing, still needs to find if there will be some compability issues with the new VIA chipset I have, I think that I may have fixed an IRQ issue, as the AGPART was crashing, because it could not find the AGP IRQ, and last night, I did a few things and fixed that, so now maybe I can actually get on with updating the kernels, and since this last writing, the new Linux 2.6.11.10 has come out. I recently updated to Linux 2.4.30, so it's getting better.