I had recently installed the kernel sources so that I could compile the VirtualBox kernel module to use… well…VirtualBox… but I had not restarted afterwards. I had been using my system problem free until tonight when I decided to restart. I had no internet connection and through ifconfig showing only lo and ifup eth0 returning “device eth0 is not accessible”, I discovered I had a bigger problem than at first thought. Then I discovered that no PCI devices other than video were working, and so I referred to /var/log/messages and discoverd a line stating that "/lib/modules/2.6.37.6-0.5-desktop/modules.dep : no such file or directory.
All other entries in that directory were some version of 2.6.37.1-1.2.
Unfortunately I had to end up reinstalling because without internet access I was not able to find a solution to the problem, and I also did not thing to save copies of some of the relevent configuration files and logs… But if anyone might have some information on what might of caused this, how to prevent it in the future, and how I could have gone about fixing it it would be greatly appreciated! I have never had something like this happen before.
Hm, you are free to think this is a worthless answer (and in the end it maybe so), but I should realy try to find out what you did beside installing the kernel source.
My idea is also that it might help others to help you giving some factual information like replacing “I had recently installed the kernel sources …” with something like: “I have openSUSSE 11.? with kernel 2… and I installed the packages kernel-…”. I hope you get the message.
On 2011-05-29 10:36, hito kiri wrote:
>
> But if anyone might have some information on what might of
> caused this, how to prevent it in the future, and how I could have gone
> about fixing it it would be greatly appreciated! I have never had
> something like this happen before.
I’m unsure of what you did, but I suspect you installed the wrong version.
I assume you installed the suse provided RPM?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
But if anyone might have some information on what might of caused this, how to prevent it in the future, and how I could have gone about fixing it it would be greatly appreciated! I have never had something like this happen before.
It,s unclear what has occurred, but you could edit /etc/zypp/zypp.conf. to enable multiversion for the kernel, you don’t tell us which version of openSUSE you are using, so we can’t say how to go about that.
This would allow you to choose between kernels, but again It’s unclear as to weather or not this would be useful.
Sorry, I am using 11.4. I installed the kernel-source package through YaST, and from what I could tell by the looks of things I was running 2.6.37.1-1.2 at the time and it apparently installed 2.6.37.6-0.5. Grub showed it was booting /boot/vmlinuz-2.6.37.1-1.2-desktop, and there was no 2.6.37.6-0.5 entry in /boot at all. Other than installing the sources I just recompiled the VBox kernel driver. I have done this several times before in the past on older versions of openSUSE and I have never had this happen.