Followed the Plasma/Wayland/Nvidia instructions on the Arch Linux wiki after a fresh install of Manjaro (using the hardware settings in system settings to change my driver to video-nvidia). After doing this and restarting, the computer blackscreens after boot. Going into TTY2 and attempting to start X11 causes the system to immediately hang.
The intent is to boot into Wayland if possible; I’ve been able to do it before with some success on Nouveau drivers on a previous install on the same computer, but have been unable to since attempting to configure the proprietary drivers for the same purpose. I did a fresh install worrying that my previous install was too far gone to fix, having followed a number of other guides that seemed to only make the situation worse. Any assistance is appreciated.
I’ll send my inxi in a moment; I’m typing this from a different computer.
My inxi:
System:
Kernel: 6.5.3-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.5-x86_64
root=UUID=563ccf27-2759-4f1a-85a4-cca05d4f85da rw 3 splash
udev.log_priority=3
Console: tty 1 DM: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 20TLS01300 v: ThinkPad X1 Extreme Gen 3
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20TLS01300 v: SDK0R32862 WIN
serial: <superuser required> UEFI: LENOVO v: N2VET33W (1.18 )
date: 08/11/2021
Battery:
ID-1: BAT0 charge: 41.5 Wh (60.8%) condition: 68.3/80.0 Wh (85.4%)
power: 30.8 W volts: 15.4 min: 15.4 model: Celxpert 5B10X19050 type: Li-poly
serial: <filter> status: discharging cycles: 261
Memory:
System RAM: total: 32 GiB available: 31.1 GiB used: 809.3 MiB (2.5%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i7-10850H bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 2 microcode: 0xF8
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 837 high: 900 min/max: 800/5100 scaling:
driver: intel_pstate governor: powersave cores: 1: 900 2: 900 3: 848 4: 800
5: 900 6: 800 7: 800 8: 800 9: 800 10: 900 11: 800 12: 800 bogomips: 64821
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca mce
md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx ospke pae pat
pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts
rdrand rdseed rdtscp rep_good sdbg sep smap smep smx ss ssbd sse sse2
sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional,
RSB filling, PBRSB-eIBRS: SW sequence
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Lenovo driver: i915
v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:9bc4 class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Lenovo
driver: nvidia v: 535.104.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-08) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s ports: active: none
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1f95 class-ID: 0300
Device-3: IMC Networks Integrated Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 13d3:5405
class-ID: fe01 serial: <filter>
Display: server: X.org v: 1.21.1.8 driver: X: loaded: nvidia gpu: i915
tty: 240x67
Monitor-1: eDP-1 model: Samsung 0x4141 built: 2019 res: 3840x2160 dpi: 284
gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
modes: 3840x2160
API: OpenGL Message: GL data unavailable in console. Try -G --display
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Lenovo
driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl,
snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0401
Device-2: NVIDIA vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
API: ALSA v: k6.5.3-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 0.3.80 status: off with: pipewire-media-session
status: off tools: pw-cli
Server-3: PulseAudio v: 16.1 status: off with: pulseaudio-alsa type: plugin
tools: pacat,pactl
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
WAN IP: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:6 chip-ID: 8087:0026
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 491.85 GiB used: 10.38 GiB (2.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLB512HBJQ-000L7
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5M2QEXF7 temp: 41.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: Ultra size: 14.91 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 2.01 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 212.11 GiB size: 207.73 GiB (97.93%) used: 10.35 GiB (5.0%)
fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5 label: N/A
uuid: 563ccf27-2759-4f1a-85a4-cca05d4f85da
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 29.4 MiB (11.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
label: SYSTEM uuid: 6432-47C5
Swap:
Alert: No swap data was found.
Unmounted:
ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 263.58 GiB fs: ntfs
label: Windows uuid: 2490349590346F82
ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 1000 MiB fs: ntfs
label: WinRE_DRV uuid: 0EBC34A2BC34866D
ID-4: /dev/sda1 maj-min: 8:1 size: 3.63 GiB fs: iso9660
ID-5: /dev/sda2 maj-min: 8:2 size: 4 MiB fs: vfat label: MISO_EFI
uuid: 09D0-669F
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-1:2 info: SanDisk Ultra type: mass storage driver: usb-storage
interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
power: 200mA chip-ID: 0781:556c class-ID: 0806 serial: <filter>
Device-2: 1-8:3 info: IMC Networks Integrated Camera type: video
driver: uvcvideo interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
mode: 2.0 power: 500mA chip-ID: 13d3:5405 class-ID: fe01 serial: <filter>
Device-3: 1-9:4 info: Synaptics Prometheus MIS Touch Fingerprint Reader
type: <vendor specific> driver: N/A interfaces: 1 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 06cb:00bd class-ID: ff00 serial: <filter>
Device-4: 1-10:5 info: Wacom Pen and multitouch sensor type: HID
driver: usbhid,wacom interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 400mA chip-ID: 056a:51a0 class-ID: 0300
Device-5: 1-14:6 info: Intel AX201 Bluetooth type: bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 100mA chip-ID: 8087:0026 class-ID: e001
Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 42.0 C pch: 53.0 C mobo: N/A gpu: nvidia temp: 41 C
Fan Speeds (rpm): fan-1: 2757 fan-2: 2544
Info:
Processes: 234 Uptime: 1m wakeups: 178 Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1134 libs: 332 tools: pamac pm: flatpak pkgs: 0
Shell: Bash (login) v: 5.1.16 running-in: tty 1 inxi: 3.3.29
Some things I probably should add, now that I think about it: On previous installs I was able to access TTY2 normally via Ctrl-Alt-F2. After reinstalling and doing the same steps, I cannot do that; I have to boot into TTY2 instead. My install had hybrid NVIDIA Intel drivers before; I switched them to standard NVIDIA drivers using the Manjaro driver config GUI.
Olli
22 September 2023 16:11
6
WISHETH:
normally via Ctrl-Alt-F2
is it possible that the graphical session is linked to TTY2 ? can you check Ctrl-Alt-F3 instead and report.
1 Like
Indeed. Ever since about two months ago, it is no longer guaranteed whether sddm will start on tty1 or tty2. If one needs a free tty with Plasma, then one should use tty3.
Nothing on TTY1-7. Not a real hang, because I’m able to access them, but when I boot up X11 on TTY1, it just black screens. startplasma-x11 returns “$DISPLAY is not set or cannot connect to the X server.” ($DISPLAY does not seem to be set.)
I’ve done a few things since the last install, but from the looks of it, Manjaro should be working off the Nvidia drivers. I worry that’s the core issue.
In theory, yes. But Nvidia has already been a pain in the behind for a very long time now, and it doesn’t look like they plan on changing their attitude.
*My Manjaro install(, apologies. Though, this is far more of a hassle than I thought it’d be; such is unfortunate.)
Olli
22 September 2023 17:22
11
okay so let’S try some magic (hopefully). please boot into console. install envycontrol (it’s in the aur)
pamac install envycontrol
then you’ll need to edit the grub and mkinitcpio with sudo rights.
edit /etc/default/grub and add
nvidia_drm.modeset=1
to the existing
GRUB_CMDLINE_LINUX_DEFAULT="
edit /ect/mkinitcpio.conf
MODULES=(nvidia_modeset nvidia_uvm nvidia_drm)
run
sudo mkinitcpio -P
sudo update-grub
Got error: target not found: envycontrol
Olli
22 September 2023 17:31
14
as @Aragorn suggested try the build option, if this isn’t succesful try
yay -S envycontrol
1 Like
Got the build option. Making the edits now.
After making the edits, should I just reboot?
Olli
22 September 2023 17:35
17
yes, but you’re not finished yet but try if you can boot into a graphical session now and report.
Same deal; grub booted fine, but I black screen. tty1 and tty2 seem occupied, but tty3 is fine.
Olli
22 September 2023 17:39
19
can you explain what things you did before ?
I fresh installed, then updated to latest official drivers from the site; on previous installs, I tried steps similar to what you described, but wasn’t sure what was doing what. Haven’t done much this time around.
Olli
22 September 2023 17:40
21
okay, please go to TTY3 and run
sudo envycontrol -s nvidia
reboot and report
I seem to boot into X11 just fine. envycontrol seemed to do the trick; thank you very much. Would I be able to try booting into Wayland from here if my drivers are up to date?
