Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ok so today i compiled my first kernel (2.4 upgraded to 2.6.7). the good news is that linux was able to boot properly and start x. the bad news is that i dont think i added the right support for all my peripherals. when i was configuring the kernel as some points i would hold down enter because the shear amount of questions . this is most likely why i am having some trouble.
to solve this i am going to do a clean install of slack 10 and then try again until i get it right. alot of the questions asked were about what chipsets to support. i have no idea what my different chipsets are. what is the best way to find them? and also is there somewhere that explains the questions in more simplistic terms than the help included in the kernel?
To find out what sort of chipsets you have, type "lspci" (as root). This should give you a nearly incomprehensible list of chipsets in your computer. Write them down. Often it is enough to write down the manufacturer of the chipset, because many manufacturers only make one or two compatible chipsets of each type. Most people will only need to keep track of the IDE interface, sound card, USB, host bridge (for the agpgart driver) and video card chipsets. Depending on your setup you might also need SATA, firewire or a number of other things.
buffed317 -- next time you compile a kernel, use make menuconfig or make xconfig instead of make xconfig. They are much easier to get along with and you can browse through menus of configuration option rather than having them all given to you in a big long list.
what i propose is that u get urself a working configurstion of the 2.6 kenel whci is working for ur kernel. u can get to those after u have installed a precompiled kernel.
after that u can remove options from there
beacuse it happended at many time we do not what are the things required for our system
what about kernel arguements? how do i pass those? i just did a second kernel compile on a clean installation of slack 10. the only problems i am having now is that the cdrom is reconized but not mountable,i get this error when i try to mount it:
mount: special device /dev/cdrom does not exist
i think i need to use hdc = ide.......something. i forget exactly what it is. also i have a pcmcia card with 2 2.0 usb ports. upon boot the kernel sees that there is a card there but doesnt activate it. the two power lights for the ports dont light up. what are some common kernel arguements? is there a list somewhere? what file do i add the arguements to? i googled for stuff and nothing useful came up.
mesand: how do i go about tweaking a kernel like that?
For quick and easy kernel configuring, take your distro's working kernel+source's .config file and use something like KDE's kcmshell linuz app to work your way through the options and just disable/module things you know you dont need. Eg HAM radio or ISDN support. Then drop that .config file in as you're going through the compile process and you've got nothing to change via make *config.
hdc=ide-cdrom. 2.4 used to use hdX=ide-scsi for scsi emulation, but that is no longer necessary.
Not too sure about the usb thing. make sure the pcmcia modules are inserted (using modprobe). This is from the kernel option on pcmcia: To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package.
So you might need to do some extra configuring before they work.
if u r using 2.6 kernel in ur distro then u do not need this ,modutils but if ur distro is using 2.4 kernel then u need to upgrade ur modutils and others
i am using slack 10 with a 2.4.* kernel since the utils are out of date could this be causing me problems? i have been building everything into the kernel that i need. should i make more thing modules? if so what?
when i had the modutls problem, the kernel did not get even started and since u r having problem in the modules
section,u can try out the new modutils etc packages
Is the pcmcia module getting loaded? Check the output of "lsmod" after it's finished booting. You might also need the cardbus module. You can insert the with modprobe if they aren't already loaded.
ps: you don't need to reboot every time you change a setting (unless you want to change kernels). Just run /etc/rc.d/rc.pcmcia to see if it has been fixed.
pps: i believe slack 9 and 10 are "2.6 ready" even though they ship with 2.4 kernels. This means they already have the correct versions of modutils and all that stuff
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.