SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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 184.108.40.206 bareacpi.i, and use it to compile a 2.6 kernel.
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 220.127.116.11 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.
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?
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?
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.