Hello everybody, i have a problem, problem which appeared from nowhere, and if anyone can offer me resolution i’ll be very happy…
Here we go: i had a openSUSE 12.2 x64 installation and today i upgraded to 12.3 x64 using tutorial from SDB:Offline upgrade - openSUSE as a model. The upgrade was succesfully and the system was booting in full kde desktop mode. Then i downloaded the opensuse 13.1 RC1 x64 dvd from software.opensuse.org: Download openSUSE 13.1 RC1 and i repeated the upgrade process to 13.1. Again the process seems to be completed successfully but now i don’t have the option to boot in desktop mode any more. The only options in boot menu are “openSUSE GNU/Linux, with Xen” and “advanced options for openSUSE” with default to first option. When i try to use the advanced options menu i get “xen supervisor, version xen” menu which it take me to another menu with “openSUSE GNU/Linux, with Xen”…and when i try to boot this xen stuff i get a error “error: file ‘/boot/xen.gz’ not found”
So my question are: where is my default desktop kernel? was lost on upgrade process? is not there (on dvd) anymore and now everybody should use virtualisation? should i revert/reinstall the 12.3 version and forget for now this weird version?
The install was done on a athlon x64 6000 with 4GB of ram and a common hdd partitioning - no fancy scheme just the defaults. The system is used as a media center (with xbmc) and for my children’s games so the data is not too valuable - a clean reinstall will not be too troublesome but i wonder if i’ll reinstall this 13.1 RC1 version i’ll get the same xen boot menu, which is not desirable by any means.
Sorry for my english, but is not my mother language.
Why on earth are you using Xen? A media center + kids games doesn’t need virtualization. Plus, 13.1 is RC, Release Candidate, and as such meant for testing/bugfinding.
I never intended to use Xen - it just popped up on boot menu, without me, doing anything intentional for this. Also i used in other ocassions RC versions without any kind of problems so it seems, for me, the normal course of action.
On 2013-10-14 06:16, pixecs wrote:
>
> Knurpht;2591176 Wrote:
>> Why on earth are you using Xen? A media center + kids games doesn’t need
>> virtualization. Plus, 13.1 is RC, Release Candidate, and as such meant
>> for testing/bugfinding.
> I never intended to use Xen - it just popped up on boot menu, without
> me, doing anything intentional for this. Also i used in other ocassions
> RC versions without any kind of problems so it seems, for me, the normal
> course of action.
Well, you should report this in Bugzilla ASAP so that it gets corrected
before 13.1 is released. That’s what the Beta and RC versions are, for YOU to find and report issues to the devs in Bugzillas
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
using a live usb stick (kde in my case) i booted the system and then:
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /sys /mnt/sys
mount --bind /proc /mnt/proc
chroot /mnt
yast2
Using yast2 i removed the xen kernel and i installed the desktop kernel - after this step i had a bootable system but without a desktop so it was necessary to remove the nvidia proprietary driver (i have a GF 8600GT card) and to force reinstall of the nouveau driver.
Another step was to add, in yast2, by hand the 13.1 repositories:
> Using yast2 i removed the xen kernel and i installed the desktop kernel
> - after this step i had a bootable system but without a desktop so it
> was necessary to remove the nvidia proprietary driver (i have a GF
> 8600GT card) and to force reinstall of the nouveau driver.
> Another step was to add, in yast2, by hand the 13.1 repositories:
>
Any idea on what log files i will need to use on this bug report? I have a backup for folder “/var/log/YAST2” done before attempting to fix the problem.
Spell out the problem and how you think you got there also the hardware and any logs you have that you think maybe relevant. More info is better then less but it should be related to the problem.
On 2013-10-15 06:16, pixecs wrote:
>
> Any idea on what log files i will need to use on this bug report? I have
> a backup for folder “/var/log/YAST2” done before attempting to fix the
> problem.
Just run “/sbin/save_y2logs”, it creates a targz of all needed files for
the report.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
