Last night I compiled 2.6.3 and it seemed to go swimmingly well, my box booted first time and everything seemed to be ok. I then ran into my first error

Error 1:
I typed, startx and after editing my XF86Config (I have nvidia drivers in 2.4.x, not yet in 2.6.3) I sucessfully loaded into kde. I then got an error message "Artscd CPU overload sound server exiting" (or words to that effect), I tested my sound and found that it seems to work fine, so what gives?

Error 2:
Tried to install nvidia drivers and found I hadn't compiled loadable module support into the kernel, recompiled after adding this. I now got errors booting up saying things like "modprobe keybdev module not found", 2.6.3 shouldn't be trying to load any modules as I didn't build any!!! How do I stop this? my modules.conf is empty. I'm pretty sure that it is looking in a file meant for my old kernel that had modules and then reading this and trying to load the modules for the old kernel. I did make modules and make modules_install as per the instructions, what else do I have to do?

Error 3:
Ok, so my box still boots even if those error messages are a bit annoying. I then tried to install the nvidia drivers, driver uncompresses ok and then it builds an interface for my kernel, I then get an error saying modules.ko can't be found. What is this, and is it related to error2?

Error 4:
This morning I booted again into 2.6.3 and got the following
I assume this means Cyclic Redundancy Check error? What the heck has happened?

1. How did you test your snd? Do command-line players work?

2. 2.6 kernels require mod-init-tools instead of modutils. The new config file for modules is modprobe.conf, not modules.conf. And since you did not build any modules, the config file might need to be manually tweaked to pass driver options using the bootloader rather than through the modules config file.

3. Yes. mod-init-tools problem.

4. The kernel image got corrupted somehow. Recompile.

1. I went for the "ignore message approach" I opened up KSCD and put a CD in the drive, everything worked fine.

2&3. No idea what you just said , I'm with you until "...and since you did not build any modules, the config file might need to be manually tweaked to...." pass driver options using the bootloader eh??

I had a look in modprobe.conf and this is a blank file, surely this is correct since I shouldn't be loading any modules

Could it be something to do with initrd? I've never really heard of this file and have never changed it between kernels, do I need to change it?

4. Will recompile and hope for the best

thanks for the help, i really appreciate it

some of the startup scripts might explicitly request module loading. maybe that's why? If your system is running fine, I wouldn't worry about it.

yeah, but that's the point - my system isn't running fine, I really need to get the nvidia module working for 2.6.3 and I can't do this until I get the module problem sorted.

What startup scripts are there?

Surely I must have done something wrong in installing my kernel? I mean I have a bog-standard slackware install, nothing special, or is everyone else encountering the same problems and just not saying anything about it?

the startup scripts are in /etc/rc.d.

the scripts might expect certain things to be compiled as modules which you might have compiled into the kernel. If so, there shouldn't be a problem as far as the working of the machine goes. Also, it might expect certain modules that you just did not compile. And some names of the modules have changed (I know that a number usb related moduels have changed their names).

I actually get that keybdev myself. Somehow, it can't be compiled as module in 2.6.3 but you shouldn't worry about it. If the keyb is working, the thing is compiled into the kernel.

thanks, I'll look into the rc.d files (I'm guessing rc.modules is the only one I should be concerned with?)

Any idea how to solve my modules.ko not found problem? This is the one that is the most important to me as I'd really like to get my nvidia driver installed

I'd look at all the rc scripts. you never know.

I have no idea about the modules.ko thing. sorry. have you checked if the nvidia drivers work with 2.6.3?

I sorted out the nvidia thing!!!

The original nvidia driver doesn't work but I was trying with a 2.6.x specific version of it, so it wasn't that - I've still no idea what I changed, I rebuilt the kernel (with pretty much identical options) and re-ran lilo, hey presto fixed!!

As for the loading modules I think it goes much deeper than the rc.d files, there seems to be stuff litered all over the place but I will carry on trying!

Any ideas on my sound problems (I have the dialogue box up this time) it says:-

*Title Bar* Error - artsmessage

*In Dialogue box* Sound server fatal error: cpu overload, aborting

I also got some fatal OSS errors during boot, do you think its related? my sound is still working fine though (aumix, kscd etc) but aRts Control Tool refuses to start (not that I'm actually bothered) but it would be nice to get ride of the error message every time I startx

you could go into kde control center and make it NOT start the arts sound server at startup. Should ge trid of the message. It might also help to change sound I/O method thing from auto to the what you're using (either oss or alsa).

you can start arts manually with
artsshell start

and kill it with
artsshell terminate

You can check the status with
artsshell status

every time I start alsa it dies within about five seconds, I've disabled it in the control centre. that's fine with me, I always thought arts was a bit lame anyhow

If you are using KDE 3.2 go into the Control Center -> Sound & Multimedia -> Sound Server -> Hardware and change it to Threaded Open Sound System. Then test the sound. It should work.

Or edit the following file. /home/$user/.kde/share/config/kcmartsrc with the changes below

The '-a toss' is the threaded open sound system selection.

[Arts]
AddOptions=
Arguments=\s-F 10 -S 4096 -a toss -d -s 60 -m artsmessage -c drkonqi -l 3 -f
AudioIO=toss
AutoSuspend=true
Bits=0
DeviceName=
FullDuplex=true
Latency=250
NetworkTransparent=false
ResponseTime=1
SamplingRate=0
StartRealtime=true
StartServer=true
SuspendTime=60
X11GlobalComm=false

The above error goes away if you use the -mm 2.6 kernel updates.