[SOLVED] Booting to black screen with kernel 5.6 RC2

Agent X · 02-19-2020, 02:44 PM

I'm running Manjaro 19.0 testing build 64 bit and received several system updates and the 5.6 rc2 kernel was part of them. After installing and doing a reboot and selecting to boot into Manjaro the system just sat there doing nothing. I restarted the system again, selected advanced options, and the 5.5 kernel and booted right into my desktop. Would like to know if anyone has any idea on what might be the issue. Thanks

Code:

System:    Host: Secret-Computer Kernel: 5.5.4-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.5-x86_64 
           root=UUID=e0246a06-8b86-404a-8d9d-2efe69098371 rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Desktop: KDE Plasma 5.18.1 tk: Qt 5.14.1 wm: kwin_x11 dm: SDDM 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: 970 PRO GAMING/AURA v: Rev 1.xx 
           serial: <filter> UEFI: American Megatrends v: 1001 date: 06/07/2017 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> 
           charge: 5% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Mouse serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
           family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 
           L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 42161 
           Speed: 1399 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 
           1: 1403 2: 1404 3: 1404 4: 1397 5: 1402 6: 1404 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           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: Full AMD retpoline, IBPB: conditional, STIBP: 
           disabled, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ASUSTeK driver: nvidia 
           v: 440.59 bus ID: 01:00.0 chip ID: 10de:1380 
           Display: x11 server: X.Org 1.20.7 driver: nvidia compositor: kwin_x11 
           resolution: 2560x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.59 
           direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1002:4383 
           Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:0fbc 
           Sound Server: ALSA v: k5.5.4-1-MANJARO 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k 
           port: d000 bus ID: 04:00.0 chip ID: 8086:1539 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 4.32 TiB used: 3.11 TiB (71.9%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 120GB size: 111.79 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: A-Data model: SU800 size: 119.24 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> scheme: GPT 
           ID-3: /dev/sdc vendor: Western Digital model: WD10EARS-00Y5B1 
           size: 931.51 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
           serial: <filter> rev: 0A80 scheme: GPT 
           ID-4: /dev/sdd vendor: Seagate model: ST31500541AS size: 1.36 TiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 5900 rpm 
           serial: <filter> rev: CC34 scheme: GPT 
           ID-5: /dev/sde type: USB vendor: Seagate model: ST2000LM007-1R8174 
           size: 1.82 TiB block size: physical: 512 B logical: 512 B rotation: 5400 rpm 
           serial: <filter> rev: 9300 scheme: GPT 
Partition: ID-1: / raw size: 90.98 GiB size: 89.05 GiB (97.88%) used: 47.29 GiB (53.1%) 
           fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 37.8 C mobo: N/A gpu: nvidia temp: 32 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 29% 
Info:      Processes: 302 Uptime: 3h 17m Memory: 15.54 GiB used: 4.87 GiB (31.3%) 
           Init: systemd v: 244 Compilers: gcc: 9.2.1 clang: 9.0.1 Shell: bash v: 5.0.16 
           running in: konsole inxi: 3.0.37

vtel57 · 02-19-2020, 04:39 PM

UPDATE your Nvidia drivers to the newest ones available from Nvidia, not the Manjaro repos. This should fix your X problem.

Agent X · 02-19-2020, 04:55 PM

Quote:

Originally Posted by vtel57

UPDATE your Nvidia drivers to the newest ones available from Nvidia, not the Manjaro repos. This should fix your X problem.

Pretty sure the nVidia headers for the latest kernel are missing but don't don't know how to check to be sure.

vtel57 · 02-19-2020, 05:40 PM

The reason I posted that was because I saw that you're using an Nvidia vid card in your system and there was a rash of this issue a few weeks back due to Nvidia dragging its feet about updating its drivers to be compatible with the 5.x kernels. They do have updated drivers in their downloads area of their website, but they probably have not made it to Manjaro's repos yet. You may have to install the Nvidia updated drivers manually to get this to work for you.

Agent X · 02-19-2020, 05:42 PM

OK fair enough, thanks

vtel57 · 02-19-2020, 06:40 PM

Well, it's just a suggestion, my friend. Stand by... others may have more suggestions for you. I'll keep an eye on this thread to see how you get it resolved.

Luck with it!

~Eric

Agent X · 03-02-2020, 08:39 AM

Quote:

Originally Posted by vtel57

Well, it's just a suggestion, my friend. Stand by... others may have more suggestions for you. I'll keep an eye on this thread to see how you get it resolved.

Luck with it!

~Eric

You do realize I was basically saying I appreciate the info, right? That said RC3 seems to have fixed the issue.

vtel57 · 03-02-2020, 09:34 AM

Quote:

Originally Posted by Agent X

You do realize I was basically saying I appreciate the info, right?

Sure. No worries.

Quote:

That said RC3 seems to have fixed the issue.

Excellent!

Please mark this one as SOLVED.

Have a great week!

~Eric