[Mageia-dev] Important and urgent: people with ati cards needed on beta3 pre release qa

Wed Apr 18 12:10:21 CEST 2012

'Twas brillig, and Oliver Burger at 18/04/12 07:41 did gyre and gimble:
+> Am 18.04.2012 01:24, schrieb Anssi Hannula:
+>> 18.04.2012 01:27, Colin Guthrie kirjoitti:
+>>> 'Twas brillig, and Oliver Burger at 17/04/12 22:15 did gyre and gimble:
+>>>> Hi there,
+>>>>
+>>>> we have some kind of an ugly problem with ati cards on beta3 pre
+>>>> relase.
+>>>> After installing the dvd it just won't boot.
+>>>
+>>> Don't you mean "X does not start" rather than "it just won't boot"? Or
+>>> have I missed something fundamental here?
+>>>
+>>> I already somewhat wasted your time earlier because I got you to get all
+>>> sorts of interesting debug for me because I thought it was a boot/init
+>>> problem, but it turns out X is just failing to initialise the vesa
+>>> driver.... have I missed some details on this problem?
+>>
+>> I indeed thought that Oliver had said he had no /var/log/Xorg.0.log
+>> after first boot and thus it didn't even try to start X... But
+>> apparently that wasn't the case after all, so maybe I misunderstood (or
+>> misread).
+>>
+>> I've added a comment in the bugreport.
+>>
+> At first boot, X doesn't start at all, the system hangs before that.
+
+OK, so this would be interesting to me. I guess I'll need the logs from
+that first boot to debug things.
+
+Some questions:
+ 1. Ideally, if you can reproduce this, can you add the following to the
+kernel command line before first boot: "systemd.log_level=debug
+systemd.log_target=kmsg" (it will obviously require a reinstall. I
+suspect this could be related to
+https://bugs.mageia.org/show_bug.cgi?id=4772 but as I've not been able
+to reproduce this on any of my VMs, I suspect it may need some real
+laptop h/w to reproduce which I don't have easy access to - I can switch
+disks in my laptop but it's not exactly easy :s)
+
+ 2. Does the boot properly hang? What is the resolution? Does it just
+sit there forever and never timeout in a kind of deadlock? Can you get
+to tty2 to login?
+
+ 3. Assuming you cannot login, do the reboot and grab the
+/var/log/dmesg.old file (as this will have the debug from the first
+boot). If you can login, then just grab the /var/log/dmesg file.
+
+Sorry I can't offer any more helpful advice until I can debug. But this
+could be two separate and maybe (possibly related) issues that are being
+debugged here: first boot hang and X config. It could be that the first
+boot hang cause harddrake to be unable to do what it was supposed to on
+first boot and thus left things in a less than ideal state for X setup?
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+