Mailinglist Archive: opensuse-factory (396 mails)

< Previous Next >
Re: [opensuse-factory] 2011-01-16 factory-tested status
  • From: "Bernhard M. Wiedemann" <bernhardout@xxxxxxxx>
  • Date: Mon, 17 Jan 2011 07:52:31 +0100
  • Message-id: <4D33E72F.7020302@lsmod.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 17.01.2011 05:11, schrieb Larry Finger:
On 01/16/2011 04:07 PM, Bernhard M. Wiedemann wrote:

There is still
https://bugzilla.novell.com/show_bug.cgi?id=660464
randomly affecting many 32bit testruns on KVM (and probably still
VirtualBox). However, the very same 2.6.37-kernel works on my two
Laptops (except for a panic on suspend-to-RAM).
VMs are an important platform for testers/users, so this should not be
taken lightly.

For the record, I unloaded Build 1016 of the i586 NET install CD and installed
it on a VirtualBox VM. The only problem I had was that it did not get an IP
via
DHCP when the network was configured the NAT option. After I switched to
BRIDGE
mode, all was OK.

I was surprised to see that the kernel is 2.6.37-rc5, not the 2.6.37 that I
expected.

Larry

The explanation is very simple. All NET install CDs use the 11.4 repo by
default, which redirects to MS5 atm, which did not yet have this bug.
You explicitly have to change the source in isolinux bootloader via F4
to /factory/repo/oss
I know two other people who did the same yesterday, when they wanted to
install Factory. This indicates that this workflow should be better
documented or otherwise be aided.

You could also just try booting up any i586 Build10xx.iso 10 times - it
does contain the new kernel+udev
and see if it works every time.

Ciao
Bernhard M.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk0z5y8ACgkQSTYLOx37oWT3TACgrE7kqGjfztGmt9X+a+DUSiX5
zukAoP6fpH1Od7ap4weAj4rRPtaQW9yP
=Tzr9
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups