LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 04-18-2017, 04:41 AM   #1
RacerBG
LQ Newbie
 
Registered: Jun 2015
Location: Bulgaria
Distribution: Arch Linux, Debian Jessie
Posts: 26

Rep: Reputation: 6
Question 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!

Last edited by RacerBG; 04-20-2017 at 11:00 AM.
 
Old 04-18-2017, 12:49 PM   #2
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,507

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
Quote:
Originally Posted by RacerBG View Post
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!
I am not sure (I have only ever had ONE Lenovo Laptop to play with, and NONE at the current time) but that does not sound like a DE issue. That reads like an XWindows (X.org) issue to me.

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?
 
Old 04-18-2017, 03:53 PM   #3
RacerBG
LQ Newbie
 
Registered: Jun 2015
Location: Bulgaria
Distribution: Arch Linux, Debian Jessie
Posts: 26

Original Poster
Rep: Reputation: 6
Quote:
Originally Posted by wpeckham View Post
I am not sure (I have only ever had ONE Lenovo Laptop to play with, and NONE at the current time) but that does not sound like a DE issue. That reads like an XWindows (X.org) issue to me.

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?
I'm afraid I don't know, sir... Please, tell me what to do and maybe tomorrow I will be able to do that.
 
Old 04-18-2017, 08:07 PM   #4
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,507

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
Hmmm. Ok, well see if you can capture the output of these commands as a start:
Code:
dmesg | grep -i "consol
video
nvid"
this helps tell what it thought it should load, and what modules for video it decided to unload. This will most likely NOT show the problem, but may have useful information. Run without the grep lists a LOT of useful information that we may not want to read today.
Code:
lsmod
will show every loaded module.
Code:
grep "EE
WW" /var/log/Xorg.0.log
This will show every X.org ERROR and WARNING message from the most recent xwindows run. Dumped (using cat perhaps) without the grep, it can be a LOT of information, most of which will probably not apply to the problem.

If you have, or can install lshw you might try
Code:
lshw -class display
and we will see if that information helps.

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!

Last edited by wpeckham; 04-18-2017 at 08:08 PM.
 
Old 04-19-2017, 12:49 PM   #5
RacerBG
LQ Newbie
 
Registered: Jun 2015
Location: Bulgaria
Distribution: Arch Linux, Debian Jessie
Posts: 26

Original Poster
Rep: Reputation: 6
First command:
Code:
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.223720] pci 0000:00:02.0: Video device with shadowed ROM
[    1.544588] [drm] Replacing VGA console driver
[    1.545199] Console: switching to colour dummy device 80x25
[    2.188041] Console: switching to colour frame buffer device 128x48
[    2.212105] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[    2.213960] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[   10.035814] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[   10.039766] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
[   40.918875] Suspending console(s) (use no_console_suspend to debug)
[   43.211729] video LNXVIDEO:00: Restoring backlight state
Next:

Code:
Module                  Size  Used by
ctr                    12807  0 
ccm                    17361  0 
bnep                   17184  2 
bluetooth             335968  5 bnep
6lowpan_iphc           16548  1 bluetooth
nfsd                  236959  2 
auth_rpcgss            45765  1 nfsd
oid_registry           12387  1 auth_rpcgss
nfs_acl                12463  1 nfsd
nfs                   168022  0 
lockd                  73443  2 nfs,nfsd
fscache                44782  1 nfs
sunrpc                211341  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
arc4                   12480  2 
iwl4965                87852  0 
pcmcia                 44245  0 
iwlegacy               53921  1 iwl4965
mac80211              425546  2 iwl4965,iwlegacy
cfg80211              354137  3 iwl4965,iwlegacy,mac80211
snd_hda_codec_analog    13523  1 
yenta_socket           38561  0 
coretemp               12708  0 
pcmcia_rsrc            17292  1 yenta_socket
pcmcia_core            18024  3 pcmcia,pcmcia_rsrc,yenta_socket
snd_hda_codec_generic    58021  1 snd_hda_codec_analog
iTCO_wdt               12727  0 
kvm_intel             133523  0 
iTCO_vendor_support    12585  1 iTCO_wdt
kvm                   334491  1 kvm_intel
thinkpad_acpi          59487  0 
ppdev                  16686  0 
snd_hda_intel          26023  2 
parport_pc             26004  0 
shpchp                 30673  0 
parport                35213  2 ppdev,parport_pc
lpc_ich                16616  0 
pcspkr                 12531  0 
nvram                  12882  1 thinkpad_acpi
mfd_core               12537  1 lpc_ich
rfkill                 18387  5 cfg80211,thinkpad_acpi,bluetooth
serio_raw              12737  0 
i2c_i801               16845  0 
snd_hda_controller     26262  1 snd_hda_intel
snd_hda_codec          93797  4 snd_hda_codec_generic,snd_hda_intel,snd_hda_controller,snd_hda_codec_analog
snd_hwdep              12906  1 snd_hda_codec
tpm_tis                17063  0 
tpm                    26879  1 tpm_tis
battery                13164  0 
snd_pcm                78128  3 snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer              26149  1 snd_pcm
snd                    55101  12 snd_hwdep,snd_timer,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_hda_codec_analog
soundcore              12890  2 snd,snd_hda_codec
evdev                  17136  21 
ac                     12627  0 
acpi_cpufreq           17050  1 
processor              27590  3 acpi_cpufreq
fuse                   81592  1 
autofs4                34865  2 
ext4                  442557  1 
crc16                  12327  2 ext4,bluetooth
mbcache                17027  1 ext4
jbd2                   72964  1 ext4
sg                     25573  0 
sd_mod                 43684  3 
crc_t10dif             12399  1 sd_mod
crct10dif_generic      12517  1 
crct10dif_common       12340  2 crct10dif_generic,crc_t10dif
ata_generic            12450  0 
psmouse                93505  0 
ata_piix               29371  2 
libata                161908  2 ata_generic,ata_piix
scsi_mod              164132  3 sg,libata,sd_mod
firewire_ohci          34856  0 
sdhci_pci              17697  0 
sdhci                  34721  1 sdhci_pci
mmc_core               91803  2 sdhci,sdhci_pci
firewire_core          51113  1 firewire_ohci
crc_itu_t              12331  1 firewire_core
thermal                17343  0 
i915                  766751  3 
i2c_algo_bit           12647  1 i915
drm_kms_helper         44450  1 i915
video                  17763  1 i915
button                 12824  1 i915
drm                   207686  5 i915,drm_kms_helper
i2c_core               36838  5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
thermal_sys            27122  3 video,thermal,processor
ehci_pci               12464  0 
uhci_hcd               38948  0 
ehci_hcd               64933  1 ehci_pci
e1000e                192552  0 
ptp                    17462  1 e1000e
pps_core               17080  1 ptp
usbcore               171098  3 uhci_hcd,ehci_hcd,ehci_pci
usb_common             12408  1 usbcore
Next (and by the way here I see a problem):

Code:
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.                                                        
[    21.770] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.                                              
[    21.770] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.                                               
[    21.770] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    21.770] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    21.770] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    21.770] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    22.431] (WW) Falling back to old probe method for modesetting
[    22.431] (WW) Falling back to old probe method for fbdev
[    22.444] (WW) Falling back to old probe method for vesa
The last one:

Code:
  *-display:0             
       description: VGA compatible controller
       product: Mobile GM965/GL960 Integrated Graphics Controller (primary)
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 0c
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:43 memory:f8000000-f80fffff memory:e0000000-efffffff ioport:1800(size=8)
  *-display:1 UNCLAIMED
       description: Display controller
       product: Mobile GM965/GL960 Integrated Graphics Controller (secondary)
       vendor: Intel Corporation
       physical id: 2.1
       bus info: pci@0000:00:02.1
       version: 0c
       width: 64 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list
       configuration: latency=0
       resources: memory:f8100000-f81fffff
I hope that now we can try to find a solution for the problems above.
 
Old 04-19-2017, 08:44 PM   #6
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,507

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
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.
 
Old 04-20-2017, 03:11 AM   #7
RacerBG
LQ Newbie
 
Registered: Jun 2015
Location: Bulgaria
Distribution: Arch Linux, Debian Jessie
Posts: 26

Original Poster
Rep: Reputation: 6
Quote:
Originally Posted by wpeckham View Post
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.
EDIT: For the moment, it looks like updating the firmware video drivers works!

And also I would like to know how to fix the problem which appeared on the third log file.

Thanks in advance.

Last edited by RacerBG; 04-20-2017 at 04:17 AM.
 
Old 04-20-2017, 09:46 AM   #8
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,507

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
Quote:
Originally Posted by RacerBG View Post
EDIT: For the moment, it looks like updating the firmware video drivers works!

And also I would like to know how to fix the problem which appeared on the third log file.

Thanks in advance.
There was no problem in the third log file. There were (normal) warnings that suggest that the init process for Xwindows went through several autodetect steps before settling on a detected configuration. This is normal behavior for modern X.org.

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!
 
1 members found this post helpful.
Old 04-20-2017, 10:59 AM   #9
RacerBG
LQ Newbie
 
Registered: Jun 2015
Location: Bulgaria
Distribution: Arch Linux, Debian Jessie
Posts: 26

Original Poster
Rep: Reputation: 6
Quote:
Originally Posted by wpeckham View Post
There was no problem in the third log file. There were (normal) warnings that suggest that the init process for Xwindows went through several autodetect steps before settling on a detected configuration. This is normal behavior for modern X.org.

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!


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!
 
Old 04-20-2017, 06:54 PM   #10
wpeckham
LQ Guru
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS,Manjaro
Posts: 5,507

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
Thank you! Very glad that worked!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] After Loading Grub, Black Screen!!! NetRock Linux - Desktop 6 11-02-2010 07:47 PM
[SOLVED] Black Screen after Grub Loading .......3 ,2 ,1 NetRock Linux - Hardware 5 11-02-2010 07:29 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 08:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration