Quote:
Code:
# rpm -qa 'kernel*' As to how I got it, I did this command: Code:
yum install kernel Code:
# yum install kernel |
First the command does work if the kernel(s) was installed by using rpm and/or yum;
$ rpm -qa 'kernel*' kernel-2.6.18-8.1.15.el5 kernel-headers-2.6.18-8.1.15.el5 kernel-devel-2.6.18-8.1.15.el5 I'm running a custom kernel that was built from the kernel.org source so it does not show up using the command, but does show using the uname -a command; $ uname -a Linux Aspire5100 2.6.23.1 #1 Sun Nov 4 14:30:33 EST 2007 x86_64 x86_64 x86_64 GNU/Linux Second you are running F7 so please allow yum to work and install the kernel, it would be a real good idea. |
Quote:
here we go with the yum install kernel: Code:
Is this ok [y/N]: y yum update kernel does this: Code:
# yum update kernel |
So manually down load and install the kernel;
http://download.fedora.redhat.com/pu...1.fc7.i686.rpm After downloading install as root by typing: rpm -ivh kernel-2.6.23.1-21.fc7.i686.rpm You can also look in the /var/cache directory area, the file may be there already. |
Somewhere along the line that kernel was installed by a non standard method. It does not matter at this point if it was an operator error of some sort or something was randomly corrupted. The problem is that you do not know what else may have been goofed. My best advice at this point would be to do a clean install. There is no other way to know for sure that something (or a whole lot of somethings) else is goofed. My first run at linux I ended up doing three clean installs in two months due to operator errors. We learn as we go.
Good Luck Lazlow |
Quote:
Thanks, to everyone, for your help. so far.... :) |
just fyi all, i reinstalled the vm, and oh, look:
Code:
# uname -r i'm going to try the FC6 install to see what i can come up with. or just give up on my VM based webhost and install a machine in the datacentre i work in.... at huge cost :( |
The install disks you got are not standard then.
|
All times are GMT -5. The time now is 11:33 AM. |