diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-September/018985.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-September/018985.html | 233 |
1 files changed, 233 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-September/018985.html b/zarb-ml/mageia-dev/2012-September/018985.html new file mode 100644 index 000000000..854da7bd3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-September/018985.html @@ -0,0 +1,233 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Fwd: Re: M3 won't complete boot after update + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Fwd%3A%20Re%3A%20%20M3%20won%27t%20complete%20boot%20after%20update&In-Reply-To=%3C50644713.501%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="018981.html"> + <LINK REL="Next" HREF="018986.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Fwd: Re: M3 won't complete boot after update</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Fwd%3A%20Re%3A%20%20M3%20won%27t%20complete%20boot%20after%20update&In-Reply-To=%3C50644713.501%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] Fwd: Re: M3 won't complete boot after update">mageia at colin.guthr.ie + </A><BR> + <I>Thu Sep 27 14:31:15 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="018981.html">[Mageia-dev] Fwd: Re: M3 won't complete boot after update +</A></li> + <LI>Next message: <A HREF="018986.html">[Mageia-dev] Fwd: Re: M3 won't complete boot after update +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#18985">[ date ]</a> + <a href="thread.html#18985">[ thread ]</a> + <a href="subject.html#18985">[ subject ]</a> + <a href="author.html#18985">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Anne Wilson at 27/09/12 11:02 did gyre and gimble: +><i> On 27/09/12 10:15, Colin Guthrie wrote: +</I>>><i> Does it work when forcing a runlevel 3 boot instead. This is +</I>>><i> closer to a proper boot and likely a better testing environment. I +</I>>><i> presume the getty's are showing for you in level 3? +</I>><i> +</I>><i> To my surprise, the same, text boot, to level 3 does complete perfectly. +</I>><i> There are a couple of gpg messages, though: +</I>><i> +</I>><i> gpg-agent: enabled debug flags: assuan +</I>><i> can't connect to '/home/anne/.gnupg/log-socket': No such file or +</I>><i> directory. +</I> +Curious but almost certainly unrelated. + +><i> I don't know whether this is to be expected, or whether it has any +</I>><i> relevance at this point. +</I>><i> +</I>><i> "systemctl show prefdm.service | grep ActiveEnter.*Mono" returns 0 +</I>><i> +</I>><i> I presume this is to be expected at this stage. +</I> +Yes, this is expected on runlevel 3. + +><i> "systemctl start prefdm.service" +</I>><i> Failed to issue method call: Access denied +</I> +Yes, this is because you are not root. + +><i> In case that has to be root, I used "su -" then the same command, but +</I>><i> that just gives me a flashing cursor. +</I> +So it was just hanging there? It would be interesting to run systemctl +--no-block start prefdm.service and then run "systemctl status +prefdm.service" and see what kind of state it was in. i.e. is it +starting, or failed etc. + +It should eventually fail after a couple minutes and perhaps give you +some interesting log message about it. + +>><i> The results of this test are only really valuable if you do a +</I>>><i> normal boot to runlevel 5 as this is when the service should be +</I>>><i> started. +</I>><i> +</I>><i> Doesn't runlevel 5 attempt to launch the desktop, though? I don't see +</I>><i> how I can do that. +</I> +Indeed, the test there would be weather or not the system is even trying +to start the graphical desktop or something has prevent it getting that far. + +I presume it does try and start a graphical desktop then? If so, can you +not switch to vt2 at this stage and get a login getty prompt to do some +debugging? (e.g. systemctl status prefdm.service and see what state it's +in etc.) + +>><i> What I'm trying to work out here is if the job relating to +</I>>><i> starting the prefdm.service had to be ejected due to some kind of +</I>>><i> conflict. +</I>><i> +</I>>><i> If there is a conflict then the values will be 0 and this will +</I>>><i> explain why your graphical desktop does not start. +</I>><i> +</I>><i> While the new reboot is completing, and while I remember - irqbalance +</I>><i> daemon always fails to start. I've assumed it's not relevant? +</I> +I noticed this yesterday too. It has a very incomplete systemd unit for +some reason. Will have to investigate who added that without checking it. + + +>>>>>><i> If it still fails, then try starting prefdm.service +</I>>>>>>><i> manually (systemctl start prefdm.service) and see what +</I>>>>>>><i> happens. +</I>>>>><i> +</I>>>>><i> Nothing at all happens. It returns to the prompt. +</I>>><i> This is curious. Does this also occur at runelevel 3? What does +</I>>><i> systemctl status prefdm.service tell you after it returns you to +</I>>><i> the prompt? +</I>><i> +</I>><i> prefdm.service - Display Manager +</I>><i> Loaded: loaded (/usr/lib/systemd/system/prefdm.service: static) +</I>><i> Active: inactive (dead) +</I>><i> CGroup: name=systemd:/system/prefdm.service +</I>><i> +</I>>><i> Is there anything useful in the kdm log file about why kdm failed +</I>>><i> to launch X11? +</I>><i> +</I>><i> Looks like an X11 problem. The netbook is Atom N550, Intel everything. +</I>><i> +</I>><i> tail kdm.log +</I>><i> +</I>><i> Fatal server error: +</I>><i> no screens found +</I>><i> (EE) +</I>><i> Please consult...... +</I>><i> (EE) Please also check the log file at "var/log/Xorg.0.log" for +</I>><i> additional information +</I>><i> (EE) +</I>><i> Server terminated with error (1). Closing log file. +</I> +Yup, it's an X problem plain and simple, ignore all the rest of the +systemd debugging options above. + +><i> from Xorg.0.log file: +</I>><i> +</I>><i> LoadModule "v4l" +</I>><i> Warning, couldn't open module v4l +</I>><i> UnloadModule "v4l" +</I>><i> Unloading v4l +</I>><i> Failed to load module "v4l" (module does not exist, 0) +</I>><i> LoadModule "glx" +</I>><i> Loading /usr/lib/xorg/modules/extensions/libglx.so +</I>><i> Module glx: vendor="X.Org Foundation" +</I>><i> compiled for 1.13.0 module version = 1.0.0 +</I>><i> ABI class: X.Org Server Extension, version 7.0 +</I>><i> AIGLX enabled +</I>><i> Loading extension GLX +</I>><i> LoadModule "intel" +</I>><i> Warning: couldn't open module intel +</I>><i> UnloadModule: "intel" +</I>><i> Unloading intel +</I>><i> Failed to load module "intel" (module does not exist, 0) +</I>><i> No drivers available +</I>><i> Fatal server error: +</I>><i> no screens found +</I>><i> Please consult..... +</I>><i> +</I>><i> Looks as though we've found it. +</I>><i> +</I>>>>><i> We have all spent a lot of time on this. There are files on +</I>>>>><i> the netbook that I must recover, so now it's decision time. +</I>>>>><i> It would probably be easier and quicker to grab the latest +</I>>>>><i> image (in which case can you remind me where to go for that) +</I>>>>><i> but I am willing to continue if there is any possibility that +</I>>>>><i> what we discover could save grief for others. +</I>>>>><i> +</I>>>>><i> What do you think? +</I>>><i> Plenty more to debug if you want to continue. +</I>><i> +</I>><i> Probably Intel graphics are less common than ATi and NVidia, but if +</I>><i> there is a real problem here (as opposed to user-caused one) we should +</I>><i> continue. I can hold on a bit longer. Just give me the next steps :-) +</I> +Oh I would disagree. I think intel is more common (but I base this on +very little evidence!) Certainly I *always* ensure I have an intel card +in anything I purchase. Their Open Source commitment is just much better +than the others IMO. + +Are you sure the packages are all up-to-date? I guess this relates to +the recently(ish) updated X11 stack. + +I presume you have the x11-driver-video-intel package installed? + +Col + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="018981.html">[Mageia-dev] Fwd: Re: M3 won't complete boot after update +</A></li> + <LI>Next message: <A HREF="018986.html">[Mageia-dev] Fwd: Re: M3 won't complete boot after update +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#18985">[ date ]</a> + <a href="thread.html#18985">[ thread ]</a> + <a href="subject.html#18985">[ subject ]</a> + <a href="author.html#18985">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |