Ask Your Question
1

FedUp Fedora 17 to 19 i386 Virtualbox guest gdm issue [closed]

asked 2013-09-11 11:48:08 -0600

nippur gravatar image

updated 2013-09-11 22:16:14 -0600

FranciscoD_ gravatar image

I have upgraded an F17 VB guest, F17 all updated, F17 gnome in fall-back mode (of course), fedup-cli and its log no error messages, to F19.

All went well, boots with no errors, only GDM wont start. Going to login at console (Hostkey+F2,3,4,5 or 6) and log as root, telinit 3 and back to telinit 5 (which would cure GDM issues 99%) doesn't work.

Stuck at full fedora logo.

any suggestions?

Virtualbox 4.2.18 r 88780 on host (Fedora 14) ext-pack installed on guest

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by nippur
close date 2014-04-15 11:30:26.744235

Comments

Can't close this one myself, but considering this one as such

nippur gravatar imagenippur ( 2013-10-14 02:45:33 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2013-10-14 02:28:54 -0600

nippur gravatar image

updated 2013-10-14 02:30:27 -0600

Apparently the VB-Guest kernel modules were not created after upgrade.

My solution was editing xorg.conf by setting driver to 'vesa', restarting gdm (systemctl restart gdm.service), logging in and reinstalling the guest additions.

Worked like a charm.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-09-11 11:48:08 -0600

Seen: 263 times

Last updated: Oct 14 '13