| Summary: | starting X give black screen, from which I cannot exit | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Alberto Girlando <girlando> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | x11-server-1.10.1-1.1.mga | CVE: | |
| Status comment: | |||
|
Description
Alberto Girlando
2012-01-09 16:50:56 CET
And it was working before the update of xserver ? you can try https://wiki.mageia.org/en/Mageia_1_Errata#Radeon_HD_Issues What's the output of the following command: lspcidrake -v | grep Card What's needed is a GDB trace: Please download both https://bugs.mageia.org/attachment.cgi?id=121 and https://bugs.mageia.org/attachment.cgi?id=122 Then enable the core/debug_release media/repository and install x11-server-debug, x11-driver-video-ati-debug, glibc-debug Then just run "sh ./Xgdb2.sh" on a text terminal (not from a terminal within X11!!! use Ctrl+Alt+F1), then switch back to X11 until it segfaults (Ctrl+Alt+F7). (take from https://bugs.mageia.org/show_bug.cgi?id=87#c25) Yes, everything was working perfectly, also with the 3D desktop. I had always some problems when there was an upgrade of the kernel, just because the compilation of the proprietary drive gave problems unless I did it manually afterwards. But I could work around, since I had some answer from the system. But now the problem is certainly due to the upgrade of the X-server. The problem was dramatic to me, as in starting X with any procedure, I was lost in nowhere, with the only possibility to access the computer from another one, via ssh. Yesterday, before going home (the computer is the one I use at work, and actually I needed it desperately !) I googled around - with the other computer, of course, and found that the proprietary ATI drive had problems with acpi/udev. So, as suggested there, I inserted acpi=off at startup (I also used xdriver=vesa, but as I discovered in subsequent trial, that's irrelevant: this command seems to be ignored). Then the system DID NOT start with X, but this time gave me a message of error, and offer the opportunity to change the setting of the X-server. I first tried to switch to VESA, but it did not work: when tried to restart X the system hang (this time loosing control of the video, something did not happened previously). Then I started again, with acpi=off, and used the Xorg ati driver (without 3D acceleration). This time things worked, and now I have at least an X working, although without all the functionalities. I wanted to performed further tests, when I received Manuel's message. So maybe it is useful if I follow the suggested bug-tracking procedure: I posted the message at this stage, so people in my situation may have X working at once. Incidentally, I am using GNOME, not KDE, so the first errata indicated by Manuel probably does not apply (and the problem was different). One question to Manuel, as I am not an expert: what I have to do with the scripts: https://bugs.mageia.org/attachment.cgi?id=121 and https://bugs.mageia.org/attachment.cgi?id=122 In other words, with which name I have to save them, and where I have to puth them once I have made them executable ? In /usr/bin ? (In reply to comment #2) > One question to Manuel, as I am not an expert: what I have to do with the > scripts: > https://bugs.mageia.org/attachment.cgi?id=121 and > https://bugs.mageia.org/attachment.cgi?id=122 > > In other words, with which name I have to save them, and where I have to puth > them once I have made them executable ? In /usr/bin ? save the 121 as Xgdb2.sh in a folder (can be your home), then chmod +x Xgdb2.sh and the 122 as gcmds2 in the same folder. Then _attach_ (not paste) your backtrace here. OK, I could not do the test, since as soon as I logout OR made Ctrl/Alt F1, the computer loosed control of the terminal (green light turned to yellow), so I could not do the test (since you wanted me to debug a running X, I think a test made by logging on from another computer was invalid). So I did a further trial (re-installing the proprietary driver), and everything was OK again. So I put the status as SOLVED, although the reason of the behavior remain obscure to me. I repeat her the problem and how I got around it, just in case someone else incur in the issue. CPU: AMD Phenom(tm) II X4 920 Processor (64 bit) Card:ATI Radeon HD 2000 and later (radeon/fglrx): ATI Technologies Inc|Radeon 3100 Graphics [DISPLAY_VGA] (vendor:1002 device:9611 subv:1043 subd:82ee) Using the proprietary ATI driver ---------------------------------------- Upgraded to: kernel 2.6.38.8-desktop-9.mga AND x11-server-1.10.1-1.1.mga Tried to reboot. The new kernel recompiled fglrx. The system hanged when tried to start X: blank screen (but green light on the monitor: the card was controlling it somehow). I could not issue any command to exit X. Crtl/Alt Backspace or Crtl/Alt F1 (or any other) did not work. Only way to get out was to shutdown the computer. Tried to start with xdriver=vesa: did not work. Tried to make a safe boot and reconfigure X through aticonfig: did not work Tried to start with acpi=off In this case X did not start, but it gave me an error message, offering the possibility to reconfigure X (which was still configured for the proprietary drive) a) Tried to use VESA: did not work (why ?) b) Tried to use Xorg open ati driver: this time the system finally worked, once I decide myself to reboot (WITHOUT acpi=off) rather than simply logging out. However, I could not have 3D acceleration (no 3D desktop). In addition, when I was logging out OR when I was making Ctrl/Alt F1, the card loosed control of the monitor (yellow light), and again I had to reboot. Finally, once in X, I reconfigured X through drakconf, USING THE PROPRIETARY DRIVER when I was asked for. Since then, everything worked again as it was supposed to. Status:
NEW =>
RESOLVED |