Hi, i’m very newbie using Manjaro bur i’m Feel in love.
Even if i experiencing a ton of problems.
At this point, the most important is that i’m not able to make my GPU works ok and with the VA-API enable on i3 and Sway. In Manjaro Gnome, i’ve managed to make It work with the propietary drivers, not with nouveau, which i rhink It Will not work with Wayland.
I have try a lot of options and i have search a lot of info, even i have try to figure out with the help of Chatgpt with no success.
The thing is that the screen can be see, bur if i test the GPU, there js no VA-API and, in the other hand, if i try to install the Nvidia drivers everithing crashs.
I have a 1050ti.
Anyone knows how to fix this problwm?
Sorry for the delay, but i have to reinstall sway first, and a lot of things. If vdpau is what i need, vdpau xD
I said VA-API because is what xbox xcloud tell me is what i need, but i don’t know what is the correct option. anyways, thx for the tip. so, yes, vdpau.
i have made the commands you tell me, i post everything:
The new installation of sway continue to work just like the others attempts and the accelaration does not work, even if there is signal out and i can see the screen (i’m witing this in my computer)
This is the journalctl, i post it because i think it say something about nvidia and maybe it could be useful:
journalctl -xe 127 ✘
░░ Subject: A stop job for unit user-967.slice has finished
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A stop job for unit user-967.slice has finished.
░░
░░ The job identifier is 1053 and the job result is done.
ago 15 16:31:30 ManjarOS systemd[570]: Started PipeWire PulseAudio.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 295.
ago 15 16:31:30 ManjarOS rtkit-daemon[864]: Successfully made thread 1108 of process 1108 owned by '1000' high priority at nice level -11.
ago 15 16:31:30 ManjarOS rtkit-daemon[864]: Supervising 4 threads of 3 processes of 1 users.
ago 15 16:31:30 ManjarOS rtkit-daemon[864]: Successfully made thread 1148 of process 1108 owned by '1000' RT at priority 20.
ago 15 16:31:30 ManjarOS rtkit-daemon[864]: Supervising 5 threads of 3 processes of 1 users.
ago 15 16:31:32 ManjarOS dbus-daemon[618]: [session uid=1000 pid=618] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.50' (uid=1000 pid=1140 comm="pamac checkupdates -q")
ago 15 16:31:32 ManjarOS systemd[570]: Starting Virtual filesystem metadata service...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit UNIT has begun execution.
░░
░░ The job identifier is 319.
ago 15 16:31:32 ManjarOS dbus-daemon[618]: [session uid=1000 pid=618] Successfully activated service 'org.gtk.vfs.Metadata'
ago 15 16:31:32 ManjarOS systemd[570]: Started Virtual filesystem metadata service.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 319.
ago 15 16:31:33 ManjarOS systemd-timesyncd[464]: Contacted time server 208.85.20.220:123 (2.manjaro.pool.ntp.org).
ago 15 16:31:33 ManjarOS systemd-timesyncd[464]: Initial clock synchronization to Tue 2023-08-15 16:31:33.847452 CEST.
░░ Subject: Initial clock synchronization
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ For the first time during the current boot an NTP synchronization has been
░░ acquired and the local system clock adjustment has been initiated.
ago 15 16:31:34 ManjarOS systemd[1]: systemd-hostnamed.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit systemd-hostnamed.service has successfully entered the 'dead' state.
ago 15 16:32:00 ManjarOS systemd[1]: systemd-localed.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit systemd-localed.service has successfully entered the 'dead' state.
ago 15 16:32:37 ManjarOS sudo[1424]: PAM unable to dlopen(/usr/lib/security/pam_fprintd.so): /usr/lib/security/pam_fprintd.so: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio
ago 15 16:32:37 ManjarOS sudo[1424]: PAM adding faulty module: /usr/lib/security/pam_fprintd.so
ago 15 16:32:39 ManjarOS dbus-daemon[471]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.47' (uid=0 pid=1424 comm="sudo modprobe nvidia")
ago 15 16:32:39 ManjarOS dbus-daemon[471]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
ago 15 16:32:39 ManjarOS sudo[1424]: eduardo : TTY=pts/0 ; PWD=/home/eduardo ; USER=root ; COMMAND=/usr/bin/modprobe nvidia
ago 15 16:32:39 ManjarOS sudo[1424]: pam_unix(sudo:session): session opened for user root(uid=0) by eduardo(uid=1000)
ago 15 16:32:39 ManjarOS sudo[1424]: pam_unix(sudo:session): session closed for user root
lines 2456-2519/2519 (END)
The lsmod nvidia command does not show any result and modprobe, this one:
modprobe nvidia
modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.1.44-1-MANJARO
Hi, and thank you for the answer.
first, the outputs:
mhwd --list
> 0000:01:00.0 (0300:10de:1c82) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-nvidia 2023.03.23 false PCI
video-nvidia-470xx 2023.03.23 false PCI
video-nvidia-390xx 2023.03.23 false PCI
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:04:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
network-r8168 2016.04.20 true PCI
and
mhwd --listinstalled
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Second, i have an issue whith the propietary drivers that consist in make all my installation crash. Everytime I install the nvidia propietary drivers, the screen falls to black while installing, and then after a forces restart it is impossible to login again (even if i uninstall nvidia drivers and reinstall nouveau)
This second part is related with wayland, and no wanting to start with propiertary drivers (normally sway has a log option, nos supported, which is destined to that but not in my case)
thx you!
I have arrive, for myself, to the same point. That’s why i asked in the first time.
I know wayland, and nvidia, and everything but, you know, it works on Garuda and EndeavourOS so this is beyond need, it’s about to know why it is not working when it could.
in the other hand, Nouveau supports the Pascal family and, of course, my GPU so it can be crap, but it must work.
this is the reason why i asked.
I’m pretty sure the issue is that my drivers (nouveau) are setting for another kernel and that’s why the modprobe fails but i don’t know how to fix it. It can’t be so dificult.
Even if i dont really understand what can i do with all that info, i think some of my problems could be fixed with this.
But I’m a bit scared because i prefer not to crash my installation again with some try.
The history with Nvidia and Wayland is in a second spot, i prefer install the drivers correctly, before i made tries to make Wayland support propietary drivers.