Almost Black Screen After Signing In

vw98008 · 11-27-2019, 12:39 AM

I get an almost black screen after signing into Deepin. The home screen is barely visible. If you don't take a close look, you would think you get a black screen. I have posted this question on the Deepin forum without any help so far.

How to solve this problem?

mrmazda · 11-27-2019, 09:38 AM

Is it visible enough to get into settings and disable compositing? If so, see if it helps. When did you install Deepin? Please post here using code tags output from the info collection script inxi:

Code:

inxi -GxxSMza

Try also:

Code:

pastebinit /var/log/Xorg.0.log

and provide here the resulting URL. If you get a file not found error, try ~/.local/share/xorg/Xorg.0.log instead. If the pastebin command itself is not found or otherwise fails, you can upload one of those files via web browser to a pastebin, e.g.:

uteck · 11-27-2019, 10:09 AM

Sounds like the LCD backlight is set to a minimal setting.
If you can open a terminal and read it, run xrandr and see what your display is called, for me it is eDP-1.
The try this command, replace eDP-1 with your display name:

Code:

xrandr --output eDP-1 --brightness .9

Then look in your window manager to set up a key combo to control the backlight.

vw98008 · 11-27-2019, 11:54 AM

Quote:

Originally Posted by mrmazda

Is it visible enough to get into settings and disable compositing? If so, see if it helps. When did you install Deepin? Please post here using code tags output from the info collection script inxi:

Code:

inxi -GxxSMza

Try also:

Code:

pastebinit /var/log/Xorg.0.log

and provide here the resulting URL. If you get a file not found error, try ~/.local/share/xorg/Xorg.0.log instead. If the pastebin command itself is not found or otherwise fails, you can upload one of those files via web browser to a pastebin, e.g.:

I have to use a USB live boot to get a terminal. None of the two commands are there. I can't get the inxi installed with the live boot due to various reasons.

vw98008 · 11-27-2019, 11:57 AM

Quote:

Originally Posted by uteck

Sounds like the LCD backlight is set to a minimal setting.
If you can open a terminal and read it, run xrandr and see what your display is called, for me it is eDP-1.
The try this command, replace eDP-1 with your display name:

Code:

xrandr --output eDP-1 --brightness .9

Then look in your window manager to set up a key combo to control the backlight.

I don't know my Dell laptop display name. The following is the output of xrandr.

Quote:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 61.00*
800x600 61.00

uteck · 11-27-2019, 02:10 PM

Looks like your display is named default.

mrmazda · 11-27-2019, 02:30 PM

Quote:

Originally Posted by uteck

Looks like your display is named default.

1024x768 plus the response OP got from xrandr probably spells use of VESA or FBDEV X driver. Neither AFAIK will provide proper names to xrandr. One of these two crude fallback drivers is apparently the cause of the subject problem. Please paste entire input and output here using code tags around the paste from:

Code:

sudo inxi -GxxSza

vw98008 · 11-27-2019, 02:36 PM

Quote:

Originally Posted by mrmazda

1024x768 plus the response OP got from xrandr probably spells use of VESA or FBDEV X driver. Neither AFAIK will provide proper names to xrandr. One of these two crude fallback drivers is apparently the cause of the subject problem. Please paste entire input and output here using code tags around the paste from:

Code:

sudo inxi -GxxSza

Again, Deepin live boot mood doesn't come with inxi. And I can't install it under the live boot. I don't know any other Linux distros come with the command or not.

mrmazda · 11-27-2019, 02:48 PM

It doesn't need to be installed, merely present.

Code:

wget https://github.com/smxi/inxi/archive/master.zip
unzip master.zip
sudo sh inxi-master/inxi -GxxSza

Should solve that problem. Output can be redirected to a file for transfer in order to copy and paste. Or, before running it, run the command named script, which will capture all screen activity to a file until script is aborted.

We will probably need to see /var/log/Xorg.0.log or /var/log/Xorg.0.log.old if they exist, or if not, ~/.local/share/xorg/Xorg.0.log or ~/.local/share/xorg/Xorg.0.log. Probably

Code:

pastebinit /mnt/var/log/Xorg.0.log

or one of the other possibles should do the job if you are able to live boot something and mount your installed systems root filesystem to /mnt/.

vw98008 · 11-27-2019, 03:25 PM

Quote:

Originally Posted by mrmazda

It doesn't need to be installed, merely present.

Code:

wget https://github.com/smxi/inxi/archive/master.zip
unzip master.zip
sudo sh inxi-master/inxi -GxxSza

Should solve that problem. Output can be redirected to a file for transfer in order to copy and paste. Or, before running it, run the command named script, which will capture all screen activity to a file until script is aborted.

...

Thanks very much for the info.

I run those commands without any problem for the first two. For the third one, I get the following error:

Quote:

deepin@Deepin:~/Desktop$ sudo sh inxi-master/inxi -GxxSza
inxi-master/inxi: 17: inxi-master/inxi: use: not found
inxi-master/inxi: 18: inxi-master/inxi: use: not found
inxi-master/inxi: 20: inxi-master/inxi: use: not found
inxi-master/inxi: 22: inxi-master/inxi: Syntax error: "(" unexpected

mrmazda · 11-27-2019, 04:46 PM

Instead of that last line, do these two instead:

Code:

cd inxi-master
./inxi -GxxSza

There must be something wrong with that script that doesn't like inxi-master/inxi.

vw98008 · 11-27-2019, 05:44 PM

Quote:

Originally Posted by mrmazda

Instead of that last line, do these two instead:

Code:

cd inxi-master
./inxi -GxxSza

There must be something wrong with that script that doesn't like inxi-master/inxi.

Here is the output:

Code:

deepin@Deepin:~/inxi-master$ ./inxi -GxxSza
System:
  Host: Deepin Kernel: 4.15.0-29deepin-generic x86_64 bits: 64 
  compiler: gcc v: 7.3.0 
  parameters: BOOT_IMAGE=/live/vmlinuz boot=live components 
  memtest noapic noapm nodma nomce nomodeset nosmp nosplash 
  vga=normal union=overlay initrd=/live/initrd.lz 
  Desktop: Deepin 15.8 wm: Deepin-Metacity dm: LightDM 
  Distro: Deepin 15.8 base: Debian unstable 
Graphics:
  Device-1: AMD RS690M [Radeon Xpress 1200/1250/1270] vendor: Dell 
  driver: N/A bus ID: 01:05.0 chip ID: 1002:791f 
  Display: x11 server: X.Org 1.20.0 driver: ati,vesa 
  unloaded: fbdev,modesetting,radeon resolution: 1024x768~61Hz 
  Message: Unable to show advanced data. Required tool glxinfo 
  missing.

The deepin version is for the live boot, but not for the installed one which is 5.11.

mrmazda · 11-27-2019, 10:05 PM

Quote:

Originally Posted by vw98008

Code:

deepin@Deepin:~/inxi-master$ ./inxi -GxxSza
System:    Host: Deepin Kernel: 4.15.0-29deepin-generic x86_64 bits: 64 compiler: gcc v: 7.3.0
           parameters: BOOT_IMAGE=/live/vmlinuz boot=live components memtest noapic noapm nodma nomce nomodeset nosmp nosplash vga=normal union=overlay initrd=/live/initrd.lz
           Desktop: Deepin 15.8 wm: Deepin-Metacity dm: LightDM Distro: Deepin 15.8 base: Debian unstable
Graphics:  Device-1: AMD RS690M [Radeon Xpress 1200/1250/1270] vendor: Dell driver: N/A 
           bus ID: 01:05.0 chip ID: 1002:791f
           Display: x11 server: X.Org 1.20.0 driver: ati,vesa unloaded: fbdev,modesetting,radeon resolution: 1024x768~61Hz
           Message: Unable to show advanced data. Required tool glxinfo missing.

The deepin version is for the live boot, but not for the installed one which is 5.11.

This is confusing. All those parameters make it clear the output is from a safe mode boot. The nomodeset parameter is for troubleshooting and enabling repairs to be made, but when utilized means the output doesn't represent adequately the state of things while the problem(s) described are present. Nomodeset here explains why the video mode is only 1024x768, due to use of the VESA driver fallen back to by blocking the radeon driver. When things are as they should be, output should resemble the following from Debian 10:

Code:

$ inxi -GxxSza
System:    Host: fi965 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
           parameters: ro BOOT_IMAGE=/vmlinuz root=LABEL=w71buster mitigations=auto
           Desktop: Trinity R14.0.7 tk: Qt 3.5.0 wm: Twin dm: startx Distro: Debian GNU/Linux 10 (buster)
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] RV620 PRO [Radeon HD 3470] vendor: Dell driver: radeon v: kernel
           bus ID: 01:00.0 chip ID: 1002:95c0
           Display: server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa alternate: ati resolution: 1920x1200~60Hz
           OpenGL: renderer: AMD RV620 (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) v: 3.3 Mesa 18.3.6 compat-v: 3.0
           direct render: Yes

Boot the installed system using the rescue or safe mode Grub menu choice, then login and do:

Code:

sudo apt update
sudo apt install firmware-amd-graphics mesa-utils

This seems like a situation caused by a firmware package not being installed. If apt does not report the firmware package was already installed, this attempt to install it should fix the problem, so go ahead and try to reboot normally.

If firmware-amd-graphics was already installed, do:

Code:

sudo pastebinit /var/log/Xorg.0.log

and report the provided URL here. If you get an error message trying this, then try:

Code:

sudo pastebinit .local/share/xorg/Xorg.0.log

If you are unable to boot the installed system in failsafe mode, we'll have to try to boot live and then create a chroot to perform the above apt actions:

Code:

# sudo mount /dev/sda2 /mnt
# sudo mount -o bind /proc /mnt/proc
# sudo mount -o bind /sys /mnt/sys
# sudo mount -o bind /dev /mnt/dev
# sudo chroot /mnt

This assumes /dev/sda2 is the root partition for your installed Deepin and will have to be changed to whatever is the correct location on sda.

BTW, when you paste command output, you should be enclosing in code tags, not quote tags, which lose the output formatting.

vw98008 · 11-28-2019, 11:44 AM

Quote:

Originally Posted by mrmazda

...
This assumes /dev/sda2 is the root partition for your installed Deepin and will have to be changed to whatever is the correct location on sda.
...

How can you find the root partition? The command

Code:

ls -l /dev/sd*

doesn't tell me much.

I have tried lsblk and its output is for the USB, but not the hard drive. I also tried

Code:

sudo fdisk /dev/sda

with command i and partition number 1 or 2.

I can't tell whether the output is for USB or hard drive.

mrmazda · 11-28-2019, 01:14 PM

Try parted -l. It should be fairly obvious which is the USB.