Tried this with the Gnome LiveCD of 13.2. The Live CD boots just fine and runs. After installing to the .vdi and rebooting I just get a black screen. Any thoughts? running VirtualBox 4.3.8 on OSX 10.9.2 Host. The very first message I see while booting is Failed to load kernel module.
I’m also having this problem, the error occurs when loading kernel but the error states “Failed to mount root filesystem”
On 03/20/2014 09:36 AM, charliestheman wrote:
>
> LKJ;2631554 Wrote:
>> Tried this with the Gnome LiveCD of 13.2. The Live CD boots just fine
>> and runs. After installing to the .vdi and rebooting I just get a black
>> screen. Any thoughts? running VirtualBox 4.3.8 on OSX 10.9.2 Host. The
>> very first message I see while booting is Failed to load kernel module.
>
> I’m also having this problem, the error occurs when loading kernel but
> the error states “Failed to mount root filesystem”
I have seen that problem with the Factory ISOs. According to Coolo (the release
Manager), it works on openQA using KVM. He also says that he will be releasing
13.2-MS0 soon. If that still has the problem, then it needs to be reported. The
openSUSE-Factory mailing list is where I would note the problem.
I thought this was the 13.2 Milestone 0 release. I’m not sure I want to subscribe to yet another mailing list. I might just wait until Milestone 1 or 2 etc.
I installed 13.2 M0 within VBox 4.3.8 from the KDE Live version and I got a working system with some hiccups along the way. At the second/configuration stage of the install, I got a big orange error notice about YaST not being able to configure something but it allowed me to click past and then took me to a page to set up a new user. I did that and then got the same orange YaST error again. Then I got another new user page and I left it blank.
I was warned that leaving this blank was not a good idea, but then KDE booted with the second user name I created. A reboot used the same second user name. I haven’t played with it much since the install but maybe there’s more problems with Gnome live than with the KDE one.
I actually tried the KDE version first and got the same YaST error but I wasn’t a diligent. It’s why I decided to try the Gnome version. Perhaps I’ll try the full version and see how that goes. Third time’s a charm right? 
apparently there are problems with the installers on the live CDs. I downloaded the full DVD and installed 13.2 with XFCE without a problem.
On Thu, 20 Mar 2014 22:56:01 GMT
LKJ <LKJ@no-mx.forums.opensuse.org> wrote:
>
> apparently there are problems with the installers on the live CDs. I
> downloaded the full DVD and installed 13.2 with XFCE without a
> problem.
>
I also used full DVD and installed KDE with no problem although I
forgot to untick “automatic configuration” and got shocked by how quick
it installed. Main problem so far is that YaST2 crashes when trying to
install software. No problem using YaST running in console. I’ve
mentioned this in the mailing list
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.12.2; AMD Phenom II X2 550 Processor;
Kernel: 3.14-rc5; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
the only thing I’ve installed so far is VLC and I had no crash in YaST. As soon as I remember how to add shared folders I will see if VLC works. It does boot.
On Fri, 21 Mar 2014 13:26:01 GMT
LKJ <LKJ@no-mx.forums.opensuse.org> wrote:
>
> the only thing I’ve installed so far is VLC and I had no crash in
> YaST.
I guess you don’t have nVidia graphics? The messages I got by
running YaST from console whilst logged on as “root” - got none as
default user - pointed to a problem with nouveau; the file
“/usr/lib64/dri/updates/nouveau_dri.so” was not found.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.12.3; AMD Phenom II X2 550 Processor;
Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA)
well, my host does but since it’s a VirtualBox guest it’s using the VirtualBox video driver.
Uninstall libproxy1-config-kde4.
https://bugzilla.novell.com/show_bug.cgi?id=866692
And make sure that libqdialogsolver1 is not installed.
https://bugzilla.novell.com/show_bug.cgi?id=866622
On Fri, 21 Mar 2014 18:16:01 GMT
wolfi323 <wolfi323@no-mx.forums.opensuse.org> wrote:
>
> Cloddy;2631871 Wrote:
> > Main problem so far is that YaST2 crashes when trying to
> > install software. No problem using YaST running in console. I’ve
> > mentioned this in the mailing list
> >
> Uninstall libproxy1-config-kde4.
> https://bugzilla.novell.com/show_bug.cgi?id=866692
>
> And make sure that libqdialogsolver1 is not installed.
> https://bugzilla.novell.com/show_bug.cgi?id=866622
>
>
Done that but the next time I use YaST GUI to install software it tries
to re-install all the stuff I’ve deleted. So, YaST GUI is still
unusable for software installs. I’ll tack something on to the bug
report.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.12.3; AMD Phenom II X2 550 Processor;
Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA)
LKJ wrote:
>
> the only thing I’ve installed so far is VLC and I had no crash in YaST.
> As soon as I remember how to add shared folders I will see if VLC works.
> It does boot.
>
You’re way past where I got - trying to update a 13.1 vm failed all sorts of
things. First try got the file system wrong and refused to mount the
partition on the first try then got it right and proceeded until it failed
to initialize the vm’s ethernet. I wiped the vm’s disk and the clean
install completed but I still had no ethernet connection.
I think I’ll let this puppy bake a bit longer before investing any more
time.
–
Will Honea
Do I understand you correctly? You uninstall packages and they get re-installed when you enter YaST again?
In that case, that’s actually because of a change in libzypp. Upto 13.1 packages you uninstalled got added to the SoftLocks file and never installed again automatically. This “feature” was removed recently because it caused all sorts of unexpected behaviour, f.e. making the nvidia driver 1-click install the wrong kernel module when you uninstalled it before.
So when you enter YaST again, it wants to install all recommended packages. To prevent that you could deselect the option “Install recommended packages for already installed packages” in YaST’s menu.
If you mean that libproxy1-config-kde4 gets re-installed, well: Just taboo it and it will not get installed again (right.click on the package and select “Taboo - Never install”).
In any way, this has absolutely nothing to do with the bug report where you added the comment btw., which is about YaST crashing.
Sorry, that was not quite correct. It should read:
To prevent that you could try to enable the option “Ignore recommended packages for already installed packages” in YaST’s menu (“Options”).
Or set “solver.onlyRequires = true” in /etc/zypp/zypp.conf.