>kernel headers ( post #102)
>
>Regarding the /usr/src/linux symlink...
>
>In Slackware linux, there is no problem with updating the /usr/src/linux symlink. Here's >why...
>
>Slackware includes a packages called 'Kernel-Headers'. This includes parts of the kernel source >for the default distro kernel. For slackware current, this is 2.4.24. The files reside in >/usr/include/linux and /usr/include/asm, and are needed to compile software because of (i >think..) glibc.
>
>Anyway, as long as you have the 'Kernel Headers' package installed (and if you can compile >stuff, and haven't messed with this stuff already, you do) it doesn't matter which kernel >sources /usr/src/linux points to, since the includes are not linked to /usr/src/linux. Now - don't >worry that the kernel headers package is not the same version as your kernel (ie 2.6.1), >because it only needs to match glibc, which is compiled against the kernel that slackware was >designed around.
>
>In summary: If you have glibc and kernel headers packages from the same slackware version >there is no problem with pointing /usr/src/linux to the 2.6.0 sources.

Hi,

yeah, I found out that Slackware wasn't affected by it. However I got some problems there, without tinkering the Kernel-headers package. Don't know what's been going on there...

Obviously Slack is the best distro, since PW solved the problem in a efficient way. But from this point, it's of no use, except nostalgia maybe, to make a link on /usr/src/linux... is it ?

And AFAIK, it is still relevant on other distros. I found a Debian user-list thread with confused users, ... and confused developers. Guess it would be more appropriate to skip that step in every 'Compile your kernel esaily' guide, because everyone is not running Slackware... They should, but they don't.

Regards,
jdif

I am using slackware 9.1, linux 2.4.22, and am using kernel 2.6.1 for the upgrade. I have checked to make sure i have met all the utilities/mods/etc requirements listed @ http://kerneltrap.org/node/view/799 ..i followed everything DaOne has written exactly , and i used 'make oldconfig'

After about 20 minutes of "make" i get the following errors and the make exits:

CC [M] drivers/char/rio/rioroute.o
{standard input}: Assembler messages:
{standard input}:637: Error: value of ffffffffffffff75 too large for field of 1 bytes at 0000000000000636
make[3]: *** [drivers/char/rio/rioroute.o] Error 1
make[2]: *** [drivers/char/rio] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2


any help is greatly appreciated!


thanks

Perhaps an idiot's guide needs to be made. I followed the instructions on the original posting, and even some from one of the following one editing my lilio.conf to include the new boot image. However my boot loader doesn't have a new label added to the boot list, and slack just boots my custom 2.4.22 kernel. The original boot options from when I installed slack 9.1 appear, and none of the new ones.

Molly, did you make sure you ran 'make mrproper' first?

Joe_Bogarde, after you edited your lilo.conf file, did you run lilo? The way i do it is:
lilo -t
that tests for errors...if no errors, then:
lilo

Hope this helps.

Jeff

Joe_Bogarde,
did you run lilo as root after editing your lilo.conf file?
# /sbin/lilo (not including the "#", of course)
That should update your lilo file.

is the 2.6.1 kernel on kernel.org NOT the new kernel? I think it just be a patch, which is kewl, but I'd like the kernel.

Where can one get it?

<- obvious?

I'm not liking this 2.6.1 kernel one bit. While using the 2.4.22 .config file, half of the settings aren't even loaded because of the changes between the 2 versions. So far, my USB and SB Live are broken up in Linux....Booting into Slackware.old is fine.

Also no AGP support for my Radeon 9600 is avaliable....I tried every guide on this forum

yes i ran make mrproper first .. ive found its just going to be slightly difficult getting the kernel config'd properly .. im making progress though, no longer get the errors i listed!

Hi everyone,

I'm not sure what version of module-init-tools to download. There's 0.9.13, 0.9.14, 0.9.15-pre1, 0.9.15-pre2, 3.0, and testsuite versions. Which one?

The last time I compiled module-init-tools, it stopped my old kernel from being able to call modprobe properly. I would get the message "Kernel requires old modprobe". What do I do to avoid this problem? Yes, I did do "make moveold".

@jdifool

I agree. There is no reason I am aware of to update the /usr/src/linux symlink as long as you haven't messed with the aforementioned stuff. One reason I think it's important to know that this doesn't affect slackware as installed, however, is that one might (as I did) read up on these symlinks elsewhere, uninstall the clearly obsolete kernel headers package , modify the links in /usr/include to point to /usr/src/linux, play with the kernel for a while, and eventually be really confused when nothing compiles anymore . But yes - the best way is just not to mess with this. As usual.

I have a question about the new 2.6.x structure.
When I boot 2.6.1, there are two fatal errors :
unable to modprobe keybdev
unable to modprobe mousedev
I've read that in 2.6.1 keybdev is named usbkbd and mousedev is named usbmouse, witch is obviously the cause of my problem. Now my question is where do I rename keybdev to usbkbd and mousedev to usbmouse, because the only place I could think of is rc.modules, where the two modprobes are commented...So where are they modprobed ?

After I compiled and booted I got an "L" follwed by "99" about 200 times, then I got disk failure message. I can boot into the old kernel with a boot disk.

Thanks DaOne! Compiled kernel 2.6.1 in 1 try thansk to this FAQ ...lol unlike 2.4.22 this kernel works with you recompile it ...lol My old 2.4.22 kernel I could not recompile ...I kelpt on getting errors so I waited and now it works..lol anyways I know that I'm boring you with this crap but thanks anyways!

Hello,

I am also having a problem with a blank screen after uncompressing the kernel at boot, however my situation is a little different from the others.

When I select my 2.6.1 entry at the LILO entry I see "Uncompressing Linux.....done" and about 40 lines of text (they flash by too fast to read), then the screen goes blank with the exception of the cursor, which I see flashing at the bottom left corner of the screen.

I do not hear any hard drive activity, and it does not seem to do anything. Waiting and logging in blindly does not work. It seems to be frozen at this point.

Any ideas or suggestions?

XStorm, check /etc/modules.conf. Also, in /etc/rc.d do:

grep keybdev *

and you should find it.