http://bugzilla.novell.com/show_bug.cgi?id=576681 http://bugzilla.novell.com/show_bug.cgi?id=576681#c36 --- Comment #36 from Paul Hands <jphands@eircom.net> 2010-03-20 17:15:47 UTC --- I did a bit more characterisation on these, as I think we may be mixing 2 different issues in the same bug ID. The original hang issue : Adding ipv6.disable to the installer boot options works just fine. I tried this with a couple of different installations, above and below 700MB RAM. With ipv6 disabled, all installations succeed. Subsequent reboots do NOT need the ipv6 boot option - they work anyway. I also tried with ipv6 support enabled and disabled in YaST2 - no difference. The system boots and runs X quite happily, so it seems that it only the installer that needs ipv6.disable. Perhaps someone else can confirm? The newer failing to start X issue : I see this in Virtualbox 3.1.4 only if I install the VBox Guest Additions. I think this is a separate issue, and should perhaps be pushed over to a different bug? I saw errors in the kernel module loads for the VBox additions - the vboxvfs module fails at modprobe with..... FATAL : Error inserting vboxvfs (/lib/modules/2.6.33-5-default/misc/vboxvfs.ko): Invalid module format Running startx after that produces the X hang described by others. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.