Thank you for your answers awokd, Some of the issues were solved, below in bold the errors still happening.
Dec 15 20:52:30 dom0 kernel: Linux version 4.19.86-1.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Sun Dec 1 07:16:00 UTC 2019 > > Dec 15 20:52:30 dom0 kernel: Command line: placeholder > > root=/dev/mapper/qubes_dom0-root ro rd.lvm.lv=qubes_dom0/root > > rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 plymouth.ignore-serial-con > > ( is it possible to disable alpha support? i Have a skylake 9th gen ) - > > later there is an entry stating that it taints the kernel > > Possibly. Keep in mind dom0 runs Fedora 25, so does not have newer > drivers. In most cases, it does not matter. You could try to remove it > and see what happens. On this and your other hardware related questions, > you could also try booting a newer version of Qubes (i.e. 4.0.2rc3) or > another distribution like Debian 10 on the same hardware and > cross-referencing logs.> Thank you, i removed the alpha_support and with that the gtk errors i was having vanished along with the tainted kernel messages. Also noticed improvement of the speed of the graphics. Things appear to move smoother and faster screen. Does that make sense? The machine is a librem 13v3 > > Dec 15 20:52:30 dom0 systemd-modules-load: Failed to find module > > 'uinput' > > ( found info on kernel.org stating this module is for user input, is it > > normal that the module is not present? ) > > No, it is present on mine. i do not know how to solve this, i have seen some answers on github related to permissions, are these permissions correct? This is the second reinstal of Qubes 4.0.2-preview3 cd /dev ls -ltra uinput crw-rw---- 1 root qubes 10, 223 Dec 22 16:29 uinput The module seems to be running lsmod | grep uinput uinput 20480 0 The status of the module load service is this: ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled) Active: active (exited) since Sun 2019-12-22 16:29:16 WET; 6min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 540 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Main PID: 540 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/systemd-modules-load.service Dec 22 16:29:16 dom0 systemd-modules-load: Inserted module 'uinput' Dec 22 16:29:16 dom0 systemd: Started Load Kernel Modules. More info from journalctl journalctl -aex --unit systemd-modules-load.service Dec 22 16:29:12 dom0 systemd-modules-load: Inserted module 'xen_gntalloc' Dec 22 16:29:12 dom0 systemd-modules-load: Inserted module 'xen_blkback' Dec 22 16:29:12 dom0 systemd-modules-load: Inserted module 'xen_pciback' Dec 22 16:29:12 dom0 systemd: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Dec 22 16:29:12 dom0 systemd: Failed to start Load Kernel Modules. -- Subject: Unit systemd-modules-load.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-modules-load.service has failed. -- -- The result is failed. Dec 22 16:29:12 dom0 systemd: systemd-modules-load.service: Unit entered failed state. Dec 22 16:29:12 dom0 systemd: systemd-modules-load.service: Failed with resul 'exit-code'.Dec 22 16:29:16 dom0 systemd-modules-load: Inserted module 'uinput' Dec 22 16:29:16 dom0 systemd: Started Load Kernel Modules. -- Subject: Unit systemd-modules-load.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-modules-load.service has finished starting up. -- -- The start-up result is done. These messages are not so detailed on the causes on which the error ocurred. Is there a way to get more info, like turning on a debug mode on boot or something? Is there a way on qubes to check the signature of uinput module? > > Dec 15 20:52:37 dom0 xenstored: Checking store complete. > > Dec 15 20:52:38 dom0 udisksd: Acquired the name > > org.freedesktop.UDisks2 on the system message bus > > Dec 15 20:52:38 dom0 udisksd: Error loading modules: Error opening > > directory '/usr/lib64/udisks2/modules': No such file or directory > > Did you install something in dom0? Generally, you should not. Uninstall > it or reinstall Qubes and the error should go away. I did not install anything on dom0 ( how do i find what was supposedly installed, is there a way? ) This are the logs from installing the latest preview3 of 4.0.2. I installed it twice, the logs are the same, do you think reinstalling it will solve? Thank you for your patience. Sorry for so many questions. Merry Christmas everyone. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aBMUZaAMDO36arWKOtFXaie2BnFfs1N7FsyA8kQMFuiWs7tXNo9N5EVClSc6qEtASTkE4VOsUMfD02NY2wOfBBJ9IY4kWxdj8Ftiym5UYS8%3D%40pm.me.
publickey - firstname.lastname@example.org - 0xEC5E8A90.asc
Description: OpenPGP digital signature