olib
30 August 2020 00:23
1
Hi!
I’m running the Manjaro Gnome edition (on a Lenovo E590 notebook) and faced the issue that after the update the Login screen/GDM has not been shown anymore after starting up the notebook. It just displays the “Lenovo” logo, switches to a black screen and nothing seems to happen anymore.
But: If I switch to TTY2 via “ALT+F2” and then back again to TTY1 via “ALT+F1” then it shows the Login screen/GDM and I can login as usual.
Do I need somehow to restore the UEFI boot loader configuration or anything else?
Also my Manjaro Gnome installation did not install Grub or I haven’t seen it in action at least. It directly starts the Manjaro system without showing up the Grub boot list. This was already since the beginning of my installation. Not sure if this is as it should be, or if I can configure this somehow by myself.
Thanks for help!
Welcome to the forum!
Please see:
When asking questions in the forum it is most helpful to everyone for you to provide some basic information.
When sharing information to either give or receive assistance, please be aware of the following:
1 ) In almost every situation not explicitly involving appearance, Text is preferred over Images.
2 ) When providing code or text output, please format it so the content is easy to read.
How to Format “Code” in the Forum
Its easy to make your text and code easy on the eyes
Firs…
Please post your system information as outlined in the above post.
Please also post the output of the following to a pastebin service and link it here:
sudo journalctl -p 3 -xb
2 Likes
olib
31 August 2020 16:25
3
My sys info:
System:
Kernel: 5.8.3-2-MANJARO x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64
root=UUID=4b2c1e01-eca3-4ce7-9485-ff01456fd732 rw quiet
resume=UUID=c6e182a6-c74f-4ddf-82d9-1d8544766458 udev.log_priority=3
Desktop: GNOME 3.36.5 tk: GTK 3.24.22 wm: gnome-shell dm: GDM 3.36.3
Distro: Manjaro Linux
Machine:
Type: Laptop System: LENOVO product: 20NB000YMZ v: ThinkPad E590
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20NB000YMZ v: SDK0J40697 WIN serial: <filter>
UEFI: LENOVO v: R0YET45W (1.28 ) date: 08/10/2020
Battery:
ID-1: BAT0 charge: 39.0 Wh condition: 39.0/45.0 Wh (87%) volts: 12.3/11.1
model: LGC 01AV445 type: Li-poly serial: <filter> status: Full cycles: 38
CPU:
Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP
arch: Kaby Lake family: 6 model-id: 8E (142) stepping: C (12) microcode: D6
L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 32012
Speed: 1071 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 2009 2: 2267
3: 2289 4: 2155 5: 2332 6: 1454 7: 2373 8: 2301
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:3ea0
Device-2: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]
vendor: Lenovo driver: amdgpu v: kernel bus ID: 03:00.0 chip ID: 1002:699f
Device-3: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo
bus ID: 1-6:7 chip ID: 5986:2113
Display: x11 server: X.org 1.20.8 compositor: gnome-shell
driver: amdgpu,ati,intel unloaded: modesetting alternate: fbdev,vesa
resolution: <xdpyinfo missing>
OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.6
direct render: Yes
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci
bus ID: 00:1f.3 chip ID: 8086:9dc8
Device-2: DisplayLink USB3.1 Hub type: USB driver: snd-usb-audio
bus ID: 2-2.2:9 chip ID: 17e9:6015 serial: <filter>
Device-3: GN Netcom Jabra UC VOICE 550a type: USB
driver: jabra,snd-usb-audio,usbhid bus ID: 1-4:18 chip ID: 0b0e:0349
serial: <filter>
Sound Server: ALSA v: k5.8.3-2-MANJARO
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel port: 2000 bus ID: 04:00.0
chip ID: 10ec:8168
IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: 2000
bus ID: 05:00.0 chip ID: 8086:2526
IF: wlp5s0 state: up mac: <filter>
Device-3: Lenovo type: USB driver: cdc_ether bus ID: 2-2.3:7
chip ID: 17ef:a359 serial: <filter>
IF: enp0s20f0u2u3c2 state: down mac: <filter>
Drives:
Local Storage: total: 476.94 GiB used: 33.28 GiB (7.0%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM512GDHTNG-8710B
size: 476.94 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 serial: <filter> rev: 80010C00 scheme: GPT
Partition:
ID-1: / raw size: 467.84 GiB size: 459.50 GiB (98.22%)
used: 33.28 GiB (7.2%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3
Sensors:
System Temperatures: cpu: 51.0 C mobo: 0.0 C gpu: amdgpu temp: 44 C
Fan Speeds (RPM): cpu: 3700
Info:
Processes: 291 Uptime: 9h 55m Memory: 31.09 GiB used: 5.86 GiB (18.9%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: apt: 0 pacman: 1173
lib: 328 Shell: Zsh v: 5.8 running in: gnome-terminal inxi: 3.1.05
The output of the “journalctl” command will be posted soon too.
olib:
Also my Manjaro Gnome installation did not install Grub or I haven’t seen it in action at least. It directly starts the Manjaro system without showing up the Grub boot list. This was already since the beginning of my installation. Not sure if this is as it should be, or if I can configure this somehow by myself.
You can be sure it has been installed. This behavior is standard but can be changed, easily:
sudo nano /etc/default/grub
Change the line starting GRUB_TIMEOUT_STYLE= into
GRUB_TIMEOUT_STYLE=menu
Change the line starting GRUB_TIMEOUT= (create it if it not exists) into
GRUB_TIMEOUT=10
Save the file and exit. Then run
sudo update-grub
and reboot.
1 Like
olib
1 September 2020 19:56
5
Thank you @Wollie for your Grup tipp. I was able to activate the Grub menu during startup.
The black/blank screen now appears after I try to start the default “Manjaro Linux”. This means the notebook starts, the Lenovo logo appears, after 1-2 seconds the Grub menu appears, I select Manjaro to start and then the black/blank screen appears. As it looks like the GDM does not start automatically or I don’t know yet…
Here my journalctl output: PROTOCOL://ix.io/2vU9 (could not add a link, received the message “Cannot include links…” maybe I don’t have enough permissions?)
Wollie
2 September 2020 06:04
6
In the old forum you can find a nice thread with some suggestions, just have a look if one of them helps you:
While there are many potential reasons why your Manjaro installation doesn't boot to a desktop, the primary reason is that the graphics drivers haven't loaded correctly so your login/display manager (DM) doesn't start. This is why you get a "black...
Reading time: 1 mins 🕑
Likes: 28 ❤
Here is another, newer thread of the current forum with more or less the same content:
Original author in old forum was @jonathon
While there are many potential reasons why your Manjaro installation doesn’t boot to a desktop, the primary reason is that the graphics drivers haven’t loaded correctly so your login/display manager (DM) doesn’t start. This is why you get a “black screen” or stuck at an
[ OK ] Started some service
message.
The normal reason for this is that you have the incorrect driver version for the kernel. This happens when the mirror you are updating from i…
olib
10 September 2020 05:46
7
Thanks a lot @Wollie for your linked threads. Unfortunately I could not solve it yet with the mentioned tricks/steps in your provided links.
But your provided links gave me the idea to switch the kernel, because I have used Kernel 5.8.x and now I have switched back to Kernel 5.4.x and it worked!
Thank you for your support!
1 Like
system
Closed
13 September 2020 05:46
8
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.