[Mageia-dev] Fwd: Re: M3 won't complete boot after update
annew at kde.org
Thu Sep 27 12:02:05 CEST 2012
-----BEGIN PGP SIGNED MESSAGE-----
On 27/09/12 10:15, Colin Guthrie wrote:
> Does it work when forcing a runlevel 3 boot instead. This is
> closer to a proper boot and likely a better testing environment. I
> presume the getty's are showing for you in level 3?
To my surprise, the same, text boot, to level 3 does complete perfectly.
There are a couple of gpg messages, though:
gpg-agent: enabled debug flags: assuan
can't connect to '/home/anne/.gnupg/log-socket': No such file or
I don't know whether this is to be expected, or whether it has any
relevance at this point.
"systemctl show prefdm.service | grep ActiveEnter.*Mono" returns 0
I presume this is to be expected at this stage.
"systemctl start prefdm.service"
Failed to issue method call: Access denied
In case that has to be root, I used "su -" then the same command, but
that just gives me a flashing cursor.
> The results of this test are only really valuable if you do a
> normal boot to runlevel 5 as this is when the service should be
Doesn't runlevel 5 attempt to launch the desktop, though? I don't see
how I can do that.
> What I'm trying to work out here is if the job relating to
> starting the prefdm.service had to be ejected due to some kind of
> If there is a conflict then the values will be 0 and this will
> explain why your graphical desktop does not start.
While the new reboot is completing, and while I remember - irqbalance
daemon always fails to start. I've assumed it's not relevant?
>>>>> If it still fails, then try starting prefdm.service
>>>>> manually (systemctl start prefdm.service) and see what
>>> Nothing at all happens. It returns to the prompt.
> This is curious. Does this also occur at runelevel 3? What does
> systemctl status prefdm.service tell you after it returns you to
> the prompt?
prefdm.service - Display Manager
Loaded: loaded (/usr/lib/systemd/system/prefdm.service: static)
Active: inactive (dead)
> Is there anything useful in the kdm log file about why kdm failed
> to launch X11?
Looks like an X11 problem. The netbook is Atom N550, Intel everything.
Fatal server error:
no screens found
(EE) Please also check the log file at "var/log/Xorg.0.log" for
Server terminated with error (1). Closing log file.
from Xorg.0.log file:
Warning, couldn't open module v4l
Failed to load module "v4l" (module does not exist, 0)
Module glx: vendor="X.Org Foundation"
compiled for 1.13.0 module version = 1.0.0
ABI class: X.Org Server Extension, version 7.0
Loading extension GLX
Warning: couldn't open module intel
Failed to load module "intel" (module does not exist, 0)
No drivers available
Fatal server error:
no screens found
Looks as though we've found it.
>>> We have all spent a lot of time on this. There are files on
>>> the netbook that I must recover, so now it's decision time.
>>> It would probably be easier and quicker to grab the latest
>>> image (in which case can you remind me where to go for that)
>>> but I am willing to continue if there is any possibility that
>>> what we discover could save grief for others.
>>> What do you think?
> Plenty more to debug if you want to continue.
Probably Intel graphics are less common than ATi and NVidia, but if
there is a real problem here (as opposed to user-caused one) we should
continue. I can hold on a bit longer. Just give me the next steps :-)
Need KDE help? Try
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Mageia-dev