I finally was able to compile everything on 2.6.3 (thanks to the instructions on this forum).
Pushed my luck on preempive kernel and high performance timers too and i got casual hang up of pc...
I found that artsd was eating up sometime about 50% of my athlon 2600 CPU so i disabled it in control center of KDE and everything works perfectly...

hope this may help...

hey DaOne, just wanted to say thanks for the quick reference although the last part, I did it "the old way" with the System.map file and copying bzImage under /boot.

It worked so thats what counts

installed on mbr. Two different labels and no other bootloaders.

Can you post your lilo.conf? Also, after running lilo or make install, can you post the output as well?

Anyone else having mouse troubles with the 2.6 kernel? I've been looking aimlessly for a way to get my mx700 to behave properly. It works fine nuder gpm is I set it to exps2, but once X starts the mouse moves all over when you try and control it, and sends button clicks on its own. I now have gpm disabled and the problem still persists. I have tried every protocol in XF86Config and none work. Under 2.4.22 ExplorerPS/2 works just fine. I am desperatly in need of some help.

What release of 2.6.x ? If it is 2.6.2 there was a known problem with the mouse? Try 2.6.3 or later.

It occurs in 2.6.0, 2.6.1, 2.6.2, and 2.6.3 in Slackware and FC1.

However, I tried FC2 test 1 and it worked great. However. FC2 gives me other problems. So there _has_ to be some typoe of a solution out there.

when doing 'cp System.map /boot/System.map' are we not deleting the original System.map? what i generally do is 'cp System.map /boot/System.map-version' and make a link for System.map.

so how is the association between the image file and map file maintained if they're both renamed?

and what happens if we don't do ln -s linux-2.6.3 linux?

I think the original System.map is just a symlink to your old System.map-version
so i dont think deleting it will cost any problem.... I never had any problems doing that..

and about the "ln -s linux-2.6.3 linux" you probably still using the old linux which is symlink to linux-2.6.another-version

so maybe thats why you still boot the old kernel... coz you actually copied bzImage from 2.6.2 and not from 2.6.3.. but thats just something i forgot to do so i mentioned it.. maybe you forgot it too.. who knows? you dont really have to bother about what i said something you forgot, what I was realy trying to say was to really follow the steps daone and jymbo gave...

yeaaaah, got my first 2.6 booted first time around!

no errors during boot but after doing startx I got an error box that popped up. It said
"CPU overload - audio device exiting"
(not the exact message but words to that effect), I have just tested my sound and it is working perfectly - any idea what caused the message?

I also have another question, I have an nvidia video card and am currently waiting for the driver for 2.6 to download , I didn't compile module support into my kernel - am I gonna have to recompile the kernel to get the nvidia driver working?

mercuryx013 - My mx700 is working fine in 2.6.3, without any problems on Slack9.1 can post my XF86Config if you want?

i always use the full path name when copying or moving files during kernl stuff. does the symlink make a diff otherwise?

also, i'm not booting the old kernel, i WANT to know HOW to.

what i meant about the system map was how the association is maintained? is it only through System.map and bzImage? (which may or may not be symlinks)

Please do, althought I think my XF86Config is right - because it works under 2.4.22 right now. Did you change anything when you compiled your kernel?

I've been thinking that it's maybe because I didn't update modutils?

i always use the full path name when copying or moving files during kernl stuff. does the symlink make a diff otherwise?

also, i'm not booting the old kernel, i WANT to know HOW to.

what i meant about the system map was how the association is maintained? is it only through System.map and bzImage? (which may or may not be symlinks)

*********

i dont think symlink makes a difference, its just a link. but i use it anyway so im not really sure.

to boot your old kernel, you should make a copy of your original kernel 2.4.22
under boot directory cp vmlinuz to something like vmlinuz-2.4.22 then add an entry to your lilo
#new kernel 2.6
image = /boot/vmlinuz
label = linux-2.6
#old kernel 2.4
image = /boot/vmlinuz-2.4.22
label = linux-2.4

check my lilo config under page11 or 12.

if you wanna learn about System.maps check page 1.

no, i didn't change anything in my XF86Config (well I had to change the video driver at first as I haven't gotten round to installing the nvidia video drivers yet) and I didn't do anything with modutils either (in fact i've no idea what to change in modutils or what it really does if I'm honest). all I did was compile the kernel following the same procedure as always (I didn't use my old config from 2.4.x as I thought it'd be better with a clean config). The only thing I can think of is that you've got some funny options in your kernel config. I went for a minimalist approach with no modules and only what I needed for my system but you're welcome to have a look at my config if you want? (I've got an Athlon 2000XP, motherboard AsRock K7S8X and the usual cdwriter, pci, usb, modem stuff)

the relevant bits from my XF86Config are
I never changed the button number from 2 as I quite like the behaviour when X thinks the mouse has only 2 buttons

Please send it, I would like to take a look.