Sabayon 7, gdm doesnt boot after update [Solved]

[liam.lah]

Hey,

I just last night install Sabayon 7 Gnome on my Acer Aspire one D260 Netbook.

The install went fine, I booted into Gnome 3, started messing around, and installed a bunch of updates (about 200 or so), I restarted the computer after the update, and it no longer booted into Gnome. Having not gone far i decided to re-install Sabayon again and try again.

So again this morning i installed, updated and upon reboot, i am stuck at the terminal login.

I havent got a log. but in verbose mode, a bunch of errors come up relating to:

Code: Select all

modprobe: FATAL: Could not read '/lib/modules/3.0.0-sabayon/kernel/net/ipv4/netfilter/ipt_SET.ko': No such file or directory.

That was the only one I could still see, there were about 20 more.


What can I do?

[micia]

Hi,

Did you update the kernel too during that system upgrade?
If you update your kernel, be sure to update the modules too.

[liam.lah]

I checked my version number, i had kernel 3.0.0-sabayon.

I decided to try upgrading to 3.1.0 and installin the new drivers.

The .ko module errors during start up no longer come up. But it still doesnt boot.

Im not sure if its changed since gnome 3, but typing gdm into the command brings up the following error:

** (gdm:8410): WARNING **: Failed to acquire org.gnome.Displaymanager: Connection ":1.35" is not allowed to own the service "org.gnome.Displaymanager" due to security policies in the configuration file

** (gdm:8410) WARNING **: Could not acquire name; bailing out

Running as root:

** (gdm:8481): WARNING **: Failed to acquire org.gnome.Displaymanager:

** (gdm:8481) WARNING **: Could not acquire name; bailing out

I even recorded the start up. Its not very informative, but you can see the screen flashing between the terminal and almost a gui before it stops at leaves me there.

http://www.youtube.com/watch?v=poBmuT9gh7Y

[lxnay]

How about posting some logs instead of making videos?
If you don't know how to do it, install cookbug (if it's not already installed) and launch it.

Don't expect us to be able to help you without proper logs.
In particular:

/var/log/Xorg.*
/var/log/messages
/var/log/entropy/*
dmesg -s 99999 (output)

generated from the broken system (of course, but some people really don't get it...).

[liam.lah]

How about posting some logs instead of making videos?
If you don't know how to do it, install cookbug (if it's not already installed) and launch it.

You are totally correct, logs are important, but to be fair. I had no indication of which logs to posts until i was told. Anyhow, here they are



/var/log/Xorg.*


/var/log/messages


/var/log/entropy/*


dmesg -s 99999 (output)


These logs above were taken from the .tar.bz file generated by cookbug. To double check though, i tried pulling from the exact spot you mentioned in each of these. as in "cp /var/log/messages /mnt/"

Some are too big for pastebin. so here are the .txts

http://dl.dropbox.com/u/6100708/logs/dmesg
http://dl.dropbox.com/u/6100708/logs/entropy.log.txt
http://dl.dropbox.com/u/6100708/logs/messages
http://dl.dropbox.com/u/6100708/logs/Xorg.0.log


Thanks in advance

[liam.lah]

I got it working again.

I re installed every package on my system with

Code: Select all

equo install $(equo query installed --quiet) --ask

Thanks micia from IRC for your help.