Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Then use the menu to load the config fcp -v .config /boot/config-2.6.32.8ile I want. Save it to .config
Just to make sure, what is the result of running the command "uname -r"? I just want to be very sure that 2.6.32.8ile is actually your kernel and thus config-2.6.32.8ile is a valid config. It's not that I mistrust you, I just can't see over your shoulder.
Added:
And, can you explain what this "config fcp -v .config" thing is when you say "Then use the menu to load the config fcp -v .config". I don't know what "fcp -v" means.
Last edited by Quakeboy02; 03-20-2010 at 07:40 PM.
Just to make sure, what is the result of running the command "uname -r"? I just want to be very sure that 2.6.32.8ile is actually your kernel and thus config-2.6.32.8ile is a valid config. It's not that I mistrust you, I just can't see over your shoulder.
Added:
And, can you explain what this "config fcp -v .config" thing is when you say "Then use the menu to load the config fcp -v .config". I don't know what "fcp -v" means.
The line :
Then use the menu to load the config fcp -v .config /boot/config-2.6.32.8ile I want. Save it to .config
Should read:
Then use the menu to load the config file I want.
I'm sorry if this is being obtuse, but I don't get why you would do this. That simply replaces the copy in /boot with the .config file from your current directory. Didn't you would want to run this, instead?
I'm sorry if this is being obtuse, but I don't get why you would do this. That simply replaces the copy in /boot with the .config file from your current directory. Didn't you would want to run this, instead?
Code:
cp -v /boot/config-2.6.32.7 .config
That copy is one of the last steps. these are the last three steps prior to a reboot:
I'm sorry if this is being obtuse, but I don't get why you would do this. That simply replaces the copy in /boot with the .config file from your current directory. Didn't you would want to run this, instead?
Code:
cp -v /boot/config-2.6.32.7 .config
Actually not only do I not have USB input, I can use an old keyboard and mouse. Xt is enabled in the kernel, but my XT keyboad doesn't work either. So I have not input.
What I am trying to verify is that you originally got the config from /boot/config-`uname -r` (theconfig file for the running kernel). I'd also like to verify that you ran "make oldconfig".
Actually not only do I not have USB input, I can use an old keyboard and mouse. Xt is enabled in the kernel, but my XT keyboad doesn't work either. So I have not input.
I'm sorry, I don't understand your point, here. Either there is a kernel that runs, or there isn't. The kernel that runs, by definition, has a config file that will result in a running kernel for that kernel version.
I'm sorry, I don't understand your point, here. Either there is a kernel that runs, or there isn't. The kernel that runs, by definition, has a config file that will result in a running kernel for that kernel version.
I have a working kernel. I just have no means of direct input via keyboard or mouse. That's what this thread has been aal about.
What I am trying to verify is that you originally got the config from /boot/config-`uname -r` (theconfig file for the running kernel). I'd also like to verify that you ran "make oldconfig".
No, I'm not getting the configuration file from /boot.config. I have several configuration files I have tried including the one I received from Drakeo. I execute the make menuconfig and load the file I want to try, like the one Drakeo posted.
After I exit 'make menuconfig", it is written to the same name I loaded. At that point I just rename it to .config and type 'make'.
OK, then one final question: why haven't you started with the config file that you know works on your machine?
I tried that early on, that Centos configuration uses initrd. When I tried that one, it didn't even boot up. I guess I could try removing the two entries that refer to initrd. That's one thing I haven't tried. As far as I know, there are only two entries:
CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_INTRO
The CentOS that works uses the old Grub, I am now trying to use Grub2.
Note that it has instrunctions and comments about initrd.
No, the only reason I brought up CentOS is that I know the inputs, but USB and otherwise work on this machine. I am work on another OS now, on the same machine that had CentOS on it.
So all I am saying is, I know there is a configurtion that works, I just haven't found it.
No, the only reason I brought up CentOS is that I know the inputs, but USB and otherwise work on this machine. I am work on another OS now, on the same machine that had CentOS on it.
Can you tell us which distro?
Quote:
So all I am saying is, I know there is a configurtion that works, I just haven't found it.
As I have already stated, it's at /boot/config-`uname -r`, by definition.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.