How would I go about getting the configs that the slack kernels are compiled with? I find that bareacpi works great with my laptop, but the 2.6 kernels are missing some drivers and I can't use them. I tried to compile my own, but the first pass resulted in a blank screen, and the second pass caused the system to hard reset when I tried to boot. What I would like to do is get the config for the 2.4.33.3 bareacpi.i, and use it to compile a 2.6 kernel.

They are located on any of the Slacware mirrors. Just look in the kernels directory

Is what the config file is, the settings used to compile the kernel? I didn't know that....

you can get the config from a running kernel, have a read through this http://www.kroah.com/lkn/
it tells you pretty much everything you need to know about kernel compilation.

I don't think that this will work though. There are big differences between the 2.4 series and the 2.6, you can always try. If it works please report back im interested to see if it can

You really can't use 2.4.x configs for 2.6.x kernels. You can try, but it won't work. Just read that guide, it will help.

I'm not going to use the config to build it, I was going to see if I could use it as a guide when setting up the config for the 2.6 kernel. The 2.4.33.3 kernel works great on this box, but none of the 2.6 kernels I've found (or compiled myself) work.

Continuing: I have built a couple of working kernels, but no matter what I do, I can't get the sound to work, I can't get my wireless cards to work, and the mouse pad does not work. This is a problem that all pre-compiled kernels exhibit, as well as the ones I've compiled myself. Does anyone have an older Toshiba laptop running a 2.6.x kernel? My machine is a Satellite 1415 s173.

You unmuted the sound right ... alsamixer.

Actually, alsamixer gives an error about device not found. I'll post the error along with lspci output tonight. I'm guessing I need to find the drivers for the sound chipset in this box and get them installed. It should be that simple. Likewise for my network cards. One is an Intel 10/100 pro something that is rather common, the other is an Atheros wireless card. Neither of those should be that hard to get working. All of them work in 2.4.x kernels, I'm wondering if the drivers were just not included in the 2.6.x kernels?

If you compiled your own, you probably left it out. If you want to compile your own, may want to start with one of the default slackware 2.6.x configs, and take out whatever you don't need.

I would read Chapter 7 of this guide:
http://www.kroah.com/lkn/

That way you don't have to do trial and error.

Most things you'll be changing are in the device drivers section. And, of course, processor stuff and I/O scheduler.

did you do alsaconf before running alsamixer?

That is a very usefull chapter! However, I'm not able to mount sysfs, have not yet figured out how to get that to work in Slackware 11. I did, however get a new build with network support working. Sound is still dead, and the kernel comes with the second to the most recent version of Alsa. I'm going to update Alsa to most current and see if sound works.

When I boot, I get a blank screen. I suspect that it's going to the secondary display instead of the primary display. The nVidia drivers caused the same thing to happen, I had to modify xorg.conf to force it to use the primary display. I can login blindly and startx, and then KDE goes to the primary monitor. But all console output (Ctrl-F1-6) gives me a blank screen. It's a Toshiba s173 1415. nVidia GeForce 420 Go. Any ideas how to force the console to the primary output instead of the secondary outpout?

Did you compile in framebuffer support ? (vesafb)

I did it both ways. With framebuffer support, the nVidia drivers will not install. You get a message saying that the drivers are not compatible with framebuffer enabled. I think it's when I compiled without fb support that I started getting the blank screen, but I can try it again tonight to see if that is it or not.

I got that error too, but that's only if you include rivafb and nvidiafb. Do NOT include these and it will work. Only include vesafb for framebuffer, that should not interfere with the nvidia drivers.

So, in other words, the ONLY thing you should have checked under Graphics support is:

Nothing having to do with nivida should be checked including nvdia framebuffer support and nvidia riva support ... again these two should NOT be checked.