Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I have been using slackware since 10.2 and kept on compiling the linux kernel ever since.
I usually take the current /boot/config file and do an oldconfig and then make install.
If ever I tried from scratch with a noconfig to all options for an optimized kernel .
All kinds of bad things happen but after some reconfiguration , the kernel boots properly but I have never managed to get a proper vesa screen, ie it boots into 1024x768 directly but no fonts are found and neither the logo. If I tried a vga=0 on lilo boot , there are some screens full of kernel messages but afterwards it changes over to vesa mode and a dark screen.
I do not even know what are the dependencies, to have a minimal configuration with a working vesa.
I tried to start from /boot/config and remove all other unimportant options but it is taking too much time. (its been six years but still not enough it seems).
Even weird , I found that you can only turn off networking options only if you turn off an option in the scsi parts of the xconfig. ( I will post this option later when I find where I put it on my backup)
Originally Posted by http://kernel-seeds.org/working.html
Getting started:
Having worked with numerous kernel seed users as time has gone on, I realize that I need to be clear about a few things at the outset.
1. Kernel seeds are not bootable, "out of the box". They have to be configured by yourself in order to do anything. You have to add your list of hardware devices to the seed and compile it. To get the information, execute the following commands: lspci -n, and cat /proc/cpuinfo. Keep that information handy. You'll be using it soon.
2. A properly configured seed is only the beginning. There are numerous programs that require other settings to be turned on. For instance, iptables requires that most of the settings under Networking options --> Network packet filtering framework have to be turned on or made into modules before it can function. Clearly, setting up iptables is beyond the scope of just getting the machine up and running. In some cases, such as with my laptop, I haven't added anything beyond the basics. In others, I've had to do some retuning after things get running the right way.
Working with kernel seeds is like working with any other kernel with one exception: with kernel seeds, you are provided a stable base upon which you build a functional computer. There is no guesswork as far as the basics are concerned. Kernel seeds are my sane make defconfig for the real world.
If you can read the page at the link provided then give my your results of the following commands,
Code:
lspci -n
and
Code:
cat /proc/cpuinfo
then I will help you get started with a proper configuration.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.