2.6.0 Question
 

I've just compiled the kernel, no errors. Here's what I did:

make gconfig
make bzImage
make modules
su
make modules_install
make install

After that I rebooted...no kernel panic or anything, but it still says I'm using 2.4.22 (actually it said 2.4.23 before I compiled the kernel). So basically all i want to know is which kernel I'm using at this point. Anyway to check?

~Protex

Did you check your symlinks or filenames in /boot and compare them to your lilo.conf. Then you would need to rerun lilo.

Re: 2.6.0 Question
 

make install updates and runs lilo for you. Keep in mind that you MUST edit the Makefile and uncomment line 450 (export.....) for make install to work. And before you do anything, you need to edit the Makefile and you may also want to edit lilo.conf to add the proper entries so your old kernel is still available in case this kernel doesn't work.

All you need to do is...

make gconfig
make
su -c "make modules_install"
make install

That's it...reboot.

DaOne,

That did th trick, however it didn't boot. I prolly forgot to include something..

Can you post your lilo.conf? Also, explain didn't boot...I am assuming that you at least got to the Lilo boot menu???

I'm pretty sure it isn't a problem with lilo, but just incase here is the lilo.conf:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 200
default=Windows
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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 @ 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/hdb5
label = Linux
append = "hdd=ide-scsi"
read-only
# Linux bootable partition config ends
image = /boot/vmlinuz-ide-2.4.23
root = /dev/hdb5
label = Linux_2_4_23
append = "hdd=ide-scsi"
read-only
other=/dev/hda1
label=Windows
boot-as=0x80

Anyway, a little more detail of won't boot would be, I select linux (which should be 2.6.0) and then i see a quick flash of text followed by green and blue bars vertically on the screen ontop of my bios information. Then I can't do anything, so I power off and reboot to 2.4.23.

~Protex

Do the caps/numlock lighst flash on your keyboard? If so, there's a kernel panic.

After the screen blanks, do you see harddisk activity via the led ?

If so, looks like you compiled in the wrong (or non-functional) framebuffer device for the display. Try booting with

<2.6.0 name> vga=normal

from lilo.

And that'll give you no framebuffer. That may get you to the loginprompt for 2.6.0.

Good luck :)

-Shade

I got this exact same problem and I set "vga = normal" in my /etc/lilo.conf file and that didn't help at all. I was able to login and switch to runlevel 4 "blindly" and now I'm running Mozilla 1.6b on XFree86 4.3.0 on my new 2.6.0 kernel.

I'm not sure if it's psychological or not, but my system seems to be running a bit faster now. :)

I'm off to investigate my framebuffer problems now. :)

Peace...

Congrats.

I'd say it's definitely a framebuffer problem, then ;)

I've had bad results with all two of the kernel videocard-specific framebuffer drivers on my laptop and desktop (trident and radeon respectively). I just use the standard VESA VGA framebuffer driver without problems.
I suggest you do the same ;)

-Shade

I will try the vga = normal and the standard vesa fb device. I am using a Radeon video card so that could be the stem of the whole problem.

As far as kernel panic goes, it does not flash the number or caplock leds on the keyboard, but at the same time it does not seem like there is any HD activity either.

Hopefully, after I get the frame buffer worked out, I will be able to tell you guys (or gals) what is going on.

I'll Let you all know, thanks in advance!!! :)

~Protex

after make modules_install, you have to copy bzimage in /boot:

...
$ make modules_install
$ cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz
$ cp /usr/src/linux/System.map /boot/System.map
$ lilo
$ reboot

M.

Ok, vga=normal didn't do anything. I went back and reconfigured my kernel from scratch incase i missed something. I was able to log in blind and startx. I'm going to leave the radeon frame buffer device driver out of the kernel and just use the vesa. I'll let you know how it goes.

~Protex

Edit: That seemed to work, however I did get some warnings regarding OSS and agpgart. I'm pretty sure most of them are concerning modules that I choose to compile into the kernel instead of making them modules. Everything seems to work.

Thanks again.

~Protex

Protex- that's exactly what I was referring to. The radeon kernel module has never worked for framebuffer with my ATI Radeon 9000 Pro.
I've always just used the VESA without problems.

However, to get the ATI drivers working correctly, I've also always had to have agpgart as a module...

Your milage may vary of course, but you might find that once you try to get 3d working with your radeon, you'll need to recompile again, with agpgart as a module.

-Shade

I haven't had problems with 3d as it is currently (using dri drivers not ati's). Unreal Tournament runs just fine. However, error messages anger me so I'm just going to make those things, like agpgart, modules just to make the errors go away.

Honestly, I didn't notice the speed increase that everyone was talking about either. A while back I tried out test 2 or 3 on a mandrake 9.1 install, and I was blown away by the speed 2.6 had. With slack, everything felt fast to begin with so I didn't notice any major boost. Maybe if Pat releases a slack 2.6 kernel, then i would notice the speed boost.

Oh, and on another note, I was not able to remove scsi support from the kernel. Does it have to be compiled into it now?

~Protex