I received a kernel update a few days ago. When I try to boot with kernel 2.6.37, I get a few errors saying that a volume couldn’t be mounted and that /lib/modules/2.6.37-desktop/modules.dep couldn’t be found. I’m then left with a minimal terminal prompt.
Is this a common problem? If not, I’ll try to take a picture of the error so that you can see exactly what happened. I can still boot with kernel 2.6.34 like I could before the update.
Woah… how did that happen? You brought up an interesting point: I don’t subscribe to unstable repositories. But my current kernel-desktop-base package seems to originate from the Tumbleweed repository at obs://build.opensuse.org/openSUSE:Tumbleweed, even though I don’t recall subscribing to the rolling release repository. Other kernel-related packages still have 2.6.34.
I’ll just downgrade kernel-desktop-base to the most recent available version (2.6.34) to fix this issue.
Disable the tumbleweed repo unless you wish to use it (BTW I use it on a test partition, but I updated four kernel related packages). Highlight the package(s) that updated and downgrade it to 2.6.34-0.7.1 with YaST (as shown in your picture) using the radio button under versions.
I do not know anything about virtual box or visualization in general - but could you not use something (a kernel module) that begins with
and is not in the Rolling-Release-Repository (and is not made to work on the '.37 kernel as host-system)?
See: software.opensuse.org: Search Results
But maybe you want to prevent something like this in the future, too?
Are you sure that you do not use anything else form Tumbleweed? (-> Item-by-item downgrade or all-in-one repository switch?)
Did you deactivate the Tumbleweed repository?
I will never do a one-click install from the Tumbleweed repo ever again. (Unless I feel safe using unstable software, of course.)
The Tumbleweed repo was never in my repository list. It was used exclusively when I did a one-click install of a bad VirtualBox version. I’m think that there are no more oddities in my package manager, but I don’t know the appropriate zypper command to verify that.
BTW, for next time, the zypper command to display in a terminal is “zypper lr -d”. Always post that output wrapped in code tags (Go advanced, select text, then click on “#”)
You could disable the original 11.3 cd device entry. I don’t enable debug. Oss and Non-Oss are static, so no need to auto refresh. I usually disable the libdvdcss repo as it hardly ever changes, and any other repos I don’t often use.
Good tip… I almost forgot about the existence of the rpm command. I remember using it long ago back when openSUSE and Fedora couldn’t detect my WiFi card out of the box, but since then I’ve been using zypper (openSUSE) and apt-get (Ubuntu) for all my package managing needs. Thanks man!