GRUB is loading but the DM shows black screen
Hello guys, in short my problem is as follows:
I. I tried 2 scenarios - one with Gnome and one with KDE (respectively with GDM and KDM). 1. In both cases everything works BUT after GRUB2 menu and successful OS loading both KDM and GDM shows black screen. 2. I pass through it by entering the laptop in sleep mode and then resuming it - then it shows the login screen or lock screen I'm not sure and everything works. 3. In some cases both GDM and KDM were loading successfully. II. So my question is how to stop this black screen before GDM or KDM from appearing? The used laptop is Lenovo ThinkPad X61. I'm almost sure that all drivers are already installed. Thanks in advance! :) |
Quote:
I would like to see the video related lines from your dmesg report, and perhaps any relevant log entries for x.org, system (system messages log), and perhaps kdm/gdm log lines. Even if I can make nothing of that, providing such information may help someone else here recognize the issue. Do you know how to record and present this information? |
Quote:
|
Hmmm. Ok, well see if you can capture the output of these commands as a start:
Code:
dmesg | grep -i "consol Code:
lsmod Code:
grep "EE If you have, or can install lshw you might try Code:
lshw -class display I did research some old complaints, but they seem BACKWARDS to yours. Some users booted and all worked, then after sleep/suspend mode had to jump through hoops to get normal display on wakeup. I have not found one that was bad on boot but fixed itself on wakeup from suspend. Interesting! |
First command:
Code:
[ 0.000000] Console: colour VGA+ 80x25 Code:
Module Size Used by Code:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. Code:
*-display:0 |
OK, first I see nothing there that should be fatal. That makes sense, as something fatal would have stopped the display from working and we see it working after a wakeup from suspend. We need someone smarter, or more information as there is no clearly smoking gun here (to my eyes).
The one thing I have found that related to that i915 module on Lenovo hardware was that the firmware needed to be updated. While this may not be the same issue, it would not hurt to apply all available updates to include the linux-firmware packages to see if that has any impact on the symptoms. The firmware level cannot be far back or we would be seeing more messages in the logs, but any improvement in the firmware code might be just what we need to nail this. |
Quote:
And also I would like to know how to fix the problem which appeared on the third log file. Thanks in advance. :) |
Quote:
Old versions did this ONCE and wrote out a config file, then used that and never did detection again until forced. Today the hardware environment is assumed to be a lot more mobile, and it does autodetect on every start and caches a LOT fewer settings for the next start. I would wait for several normal boots to verify that the firmware upgrade does resolve the issue. If it appears stable, please mark this thread "SOLVED" at that point. Driver and firmware updates and resulting resolution of issues is a part of the technical environment. Everything from Firewalls to Smart Watches (and certainly including computers and all components) are subject to fixes. Even your car, if it is less than ten years old, gets a software and firmware upgrade when the vendor determines that is needful. I am jsut glad that we appear to have made progress! Luck! |
Quote:
I can confirm that this problem is solved. Already 3 times the laptop is booting as it should. Thank you very much! :) Regards and rep+ from me! |
Thank you! Very glad that worked!
|
All times are GMT -5. The time now is 03:49 PM. |