I can't login through display manager after fresh installation

silverwind63 · 29 August 2023 23:27

My spec:
CPU:R5 5600X
GPU:RTX3060TI
Driver:Open source Nvidia driver
RAM:8GB*2
SWAP:16GB
OS:wayfire edition

Hey guys,I couldn't login after the installation.I have tried to login through display manager,when I input the right password,it just login and bring me back to the login page.So I change to TTY2 and I login through TTY successfully and I can enter wayfire.

Also,when I try to bot from a bootable USB to install the system,there are two options: open source driver and proprietary driver,when I choose proprietary driver it won't boot,so I need to switch to open source driver.Is there anyway to use proprietary driver?

BluishHumility · 29 August 2023 23:38

Welcome @silverwind63, please post the output of garuda-inxi so we can take a look. Please also post the output of:

systemctl status display-manager

SGS · 30 August 2023 03:26

After installation with free driver, you can install the nvidia driver.

silverwind63 · 30 August 2023 09:26

System:
  Kernel: 6.4.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=ebc17044-ef14-4f0a-bdf5-b94090ac4139 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: wayfire v: 0.7.5 info: waybar vt: 2 dm: greetd
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME B550-PLUS v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2006
    date: 03/19/2021
CPU:
  Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA201009
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 2303 high: 3447 min/max: 2200/4650 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2199 2: 2200
    3: 2200 4: 2200 5: 2200 6: 2200 7: 3447 8: 2200 9: 2200 10: 2200 11: 2200
    12: 2199 bogomips: 88803
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] driver: nouveau
    v: kernel non-free: 535.xx+ status: current (as of 2023-08) arch: Ampere
    code: GAxxx process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3
    bus-ID: 08:00.0 chip-ID: 10de:2489 class-ID: 0300
  Display: wayland server: Xwayland v: 23.2.0 compositor: wayfire v: 0.7.5
    driver: gpu: nouveau display-ID: 1
  Monitor-1: HDMI-A-1 model: MSI G241 serial: <filter> built: 2021
    res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Message: No known Wayland EGL/GBM data sources. API: EGL/GBM
Audio:
  Device-1: NVIDIA GA104 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:228b
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.4.12-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.78 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.84 TiB used: 410.5 GiB (21.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Crucial model: CT1000P3PSSD8
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40A temp: 42.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 42B9T6TB temp: 38.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.5 GiB (44.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.5 GiB (44.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.5 GiB (44.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.5 GiB (44.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.52 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 64.1 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 469 Uptime: 10m wakeups: 0 Memory: total: 16 GiB
  available: 15.52 GiB used: 2.24 GiB (14.5%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1279 libs: 403 tools: pamac,paru Shell: fish v: 3.6.1
  default: Bash v: 5.1.16 running-in: alacritty inxi: 3.3.29
Garuda (2.6.16-1):
  System install date:     2023-08-29
  Last full system update: 2023-08-30 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            systemd-vconsole-setup.service

> systemctl status display-manager
● greetd.service - Greeter daemon
     Loaded: loaded (/usr/lib/systemd/system/greetd.service; enabled; preset: disabled)
     Active: active (running) since Wed 2023-08-30 17:15:08 CST; 11min ago
   Main PID: 747 (greetd)
      Tasks: 1 (limit: 19040)
     Memory: 4.4M
        CPU: 36ms
     CGroup: /system.slice/greetd.service
             └─747 greetd

 8月 30 17:15:08 chen-systemproductname systemd[1]: Started Greeter daemon.
 8月 30 17:15:08 chen-systemproductname greetd[747]: config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: Specific(1), switch: true }, general: ConfigGeneral { source_profile: true, runfile: "/run/g>
 8月 30 17:15:08 chen-systemproductname greetd[751]: config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: None, switch: false }, general: ConfigGeneral { source_profile: true, runfile: "/run/greetd.>
 8月 30 17:15:08 chen-systemproductname greetd[751]: pam_unix(greetd:session): session opened for user greeter(uid=966) by greeter(uid=0)
 8月 30 17:15:18 chen-systemproductname greetd[885]: config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: None, switch: false }, general: ConfigGeneral { source_profile: true, runfile: "/run/greetd.>
 8月 30 17:15:18 chen-systemproductname greetd[885]: pam_unix(greetd:session): session opened for user chen(uid=1000) by chen(uid=0)
 8月 30 17:15:24 chen-systemproductname greetd[1844]: config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: None, switch: false }, general: ConfigGeneral { source_profile: true, runfile: "/run/greetd>
 8月 30 17:15:24 chen-systemproductname greetd[1844]: pam_unix(greetd:session): session opened for user greeter(uid=966) by greeter(uid=0)
lines 1-18/18 (END)

silverwind63 · 31 August 2023 04:45

I have reply it below,please check it.

BluishHumility · 31 August 2023 17:45

Most likely the display manager is using the wrong keyboard layout.

QtGreet needs the keyboard layout specified explicitly for Wayfire in /etc/qtgreet/wayfire.ini, see here: GitHub - marcusbritanicus/QtGreet: Qt based greeter for greetd, to be run under wayfire or similar wlr-based compositors.

Configuring the keyboard layout for wayfire

Sometimes, it would be easier if the keyboard layout was not the default us. For wayfire, simply add the following line at the end of /etc/qtgreet/wayfire.ini file:
[input] xkb_layout = us

Put the keyboard layout you wish to use in place of us.

For this GPU you may use the nvidia-dkms package.

sudo pacman -S nvidia-dkms

silverwind63 · 1 September 2023 09:55

Setting my keyboard layout to us doesn't work.

BluishHumility · 1 September 2023 10:45

Please post the output of:

localectl status

silverwind63 · 1 September 2023 11:52

I have executed "cat /etc/default/keyboard" and the output said that my keyboard layout is us.Should I run localectl status to check more detail?

BluishHumility · 1 September 2023 12:12

Go ahead and paste the output of localectl status into the thread if you get a chance.

Just to clear something up: is the us keyboard layout what you want? Or do you use a different keyboard layout?

silverwind63 · 1 September 2023 14:29

The output:

System Locale: LANG=en_US.UTF-8
               LC_NUMERIC=zh_TW.UTF-8
               LC_TIME=zh_TW.UTF-8
               LC_MONETARY=zh_TW.UTF-8
               LC_PAPER=zh_TW.UTF-8
               LC_NAME=zh_TW.UTF-8
               LC_ADDRESS=zh_TW.UTF-8
               LC_TELEPHONE=zh_TW.UTF-8
               LC_MEASUREMENT=zh_TW.UTF-8
               LC_IDENTIFICATION=zh_TW.UTF-8
    VC Keymap: us
   X11 Layout: us

Also,after I install nvidia-dkms, when I reboot, I can’t even enter the login page (display manager?) and wayfire,so I reinstall the system and now booting with nouveau.So if I want to use wayland,I can’t use proprietary driver?

BluishHumility · 1 September 2023 15:34

What keyboard layout does your password depend on?

Are you still having trouble logging in to the display manager? I’m just trying to determine if the password you are trying to enter is compatible with the keyboard layout you are using.

At this point, Nvidia is pretty well supported on Wayland. Probably your issue is with Wayfire, not Wayland.

Try setting up early KMS like this:

https://wiki.archlinux.org/title/Dracut#Early_kernel_module_loading

sudo micro /etc/dracut.conf.d/nvidia_kms.conf

Paste into the file:

force_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "

Save and exit. Then rebuild the initramfs:

sudo dracut-rebuild

ALso, add this kernel parameter:

nvidia_drm.modeset=1

You can add it to the end of the kernel parameter line in Garuda Boot Options, then click Apply.

Next time, you can just restore a snapshot from the boot menu instead of completely reinstalling the system.

silverwind63 · 1 September 2023 22:55

Thank for your reply,now it work(both login and Wayland).However my cursor disappeared in wayfire,could you help me?

BluishHumility · 1 September 2023 23:34

You must set the WLR_NO_HARDWARE_CURSORS=1 environmental variable, see here: FAQ · WayfireWM/wayfire Wiki · GitHub

You can try setting it in ~/.profile as suggested in this post:

Edit the file:

micro ~/.profile

Add this line:

export WLR_NO_HARDWARE_CURSORS=1

Save and exit, reboot.

If that doesn’t work, you’ll have to set up a wrapper script for launching Wayfire as described in the Greetd wiki: index - man.sr.ht

system · 15 September 2023 23:35

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.