Re: [qubes-users] Ghost in the machine?
Thank you very much Awokd, below the answers in bold Sent with ProtonMail Secure Email.‐‐‐ Original Message ‐‐‐ On Friday, December 27, 2019 8:30 AM, 'awokd' via qubes-users qubes-users@googlegroups.com wrote: > 'Chökie Gyaltsen' via qubes-users: > > > Thank you very much for your answers, my replies in bold below. > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > > On Thursday, December 26, 2019 2:03 PM, 'awokd' via qubes-users > > qubes-users@googlegroups.com wrote: > > > > > 'Chökie Gyaltsen' via qubes-users: > > > I included the -b option on journalctl and the same message with 'uinput' > > module not being loaded and zenstored not found and being rebuiild showed > > up on today's boot. > > The 'uinput' one is the only odd message, since I'm not seeing it on > mine. I'll try a fresh install of 4.0.2rc3 sometime and see. Maybe it > gets loaded later in the boot sequence than in 4.0.1, since you've > determined it shows up anyways. Ignore xenstored, that always happens. OK perfect, thank you for your help. > > > > All the errors are still happening since install. I am sorry to insist, > > > > but the 'uinput' error is the one that worries me more, pardon my > > > > ignorance and thus the question: > > > > How can i check the signature of the module loaded? Is it possible? > > You should be able to find SHA256 sums somewhere of that module (make > sure the version exactly matches yours). This is fine for a quick check. Great! > 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/74a2cb28-57f0-8a2f-1e0f-5a74e8879e87%40danwin1210.me. -- 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/zZunP1rN9JEzgJjPGnxoX0bgteLwN1kfABMUCy4REEhJ7VopW6waAJXnet0LAZY2YUZCEuKwuVu5ic4H9uFeZ4c3MezhgYTtfGZZXPKgOYk%3D%40pm.me. publickey - bodhisattvayana@pm.me - 0xEC5E8A90.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Ghost in the machine?
'Chökie Gyaltsen' via qubes-users: > Thank you very much for your answers, my replies in bold below. > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Thursday, December 26, 2019 2:03 PM, 'awokd' via qubes-users > qubes-users@googlegroups.com wrote: > >> 'Chökie Gyaltsen' via qubes-users: > > I included the -b option on journalctl and the same message with 'uinput' > module not being loaded and zenstored not found and being rebuiild showed up > on today's boot. The 'uinput' one is the only odd message, since I'm not seeing it on mine. I'll try a fresh install of 4.0.2rc3 sometime and see. Maybe it gets loaded later in the boot sequence than in 4.0.1, since you've determined it shows up anyways. Ignore xenstored, that always happens. >>> All the errors are still happening since install. I am sorry to insist, but >>> the 'uinput' error is the one that worries me more, pardon my ignorance and >>> thus the question: >>> How can i check the signature of the module loaded? Is it possible? You should be able to find SHA256 sums somewhere of that module (make sure the version exactly matches yours). This is fine for a quick check. -- 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/74a2cb28-57f0-8a2f-1e0f-5a74e8879e87%40danwin1210.me.
Re: [qubes-users] Ghost in the machine?
Thank you very much for your answers, my replies in bold below. Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, December 26, 2019 2:03 PM, 'awokd' via qubes-users qubes-users@googlegroups.com wrote: > 'Chökie Gyaltsen' via qubes-users: > > > On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users > > qubes-users@googlegroups.com wrote: > > > > In which log > > > are you seeing the above error? > > > > This message is from journalctl -ax and persisted after installation at > > everyboot until today for 3 weeks. > > Try including the -b option. I included the -b option on journalctl and the same message with 'uinput' module not being loaded and zenstored not found and being rebuiild showed up on today's boot. Thank you > > All the errors are still happening since install. I am sorry to insist, but > > the 'uinput' error is the one that worries me more, pardon my ignorance and > > thus the question: > > How can i check the signature of the module loaded? Is it possible? > > See if they persist with the above option. > > - don't top post > Mailing list etiquette: > > - trim quoted reply to only relevant portions > > - when possible, copy and paste text instead of screenshots > -- > 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/e8651f1e-cc01-502e-16e6-bc2d5709b763%40danwin1210.me. > -- 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/6Q9E7Ou6gM26SA_wQCVKsWPs98oF475sKLEY8hrcgmqkHu7SvYbZROgcNwrWygc_Wncc9XvmB2gQf6TlNPeiuks9ZnpGy8sHsCJ8s5PSAm0%3D%40pm.me. publickey - bodhisattvayana@pm.me - 0xEC5E8A90.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Ghost in the machine?
'Chökie Gyaltsen' via qubes-users: > On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users > qubes-users@googlegroups.com wrote: >> In which log >> are you seeing the above error? > > This message is from journalctl -ax and persisted after installation at > everyboot until today for 3 weeks. Try including the -b option. > All the errors are still happening since install. I am sorry to insist, but > the 'uinput' error is the one that worries me more, pardon my ignorance and > thus the question: > How can i check the signature of the module loaded? Is it possible? See if they persist with the above option. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/e8651f1e-cc01-502e-16e6-bc2d5709b763%40danwin1210.me.
Re: [qubes-users] Ghost in the machine?
Thank you for the answers,Below i reply in bold. Happy new year everyone! ‐‐‐ Original Message ‐‐‐ On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users qubes-users@googlegroups.com wrote: > > > > Dec 15 20:52:30 dom0 systemd-modules-load[195]: 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 > > Didn't realize you were running rc3. Have you tried 4.0.1? I installed 4.0.1 in the beginning of the month, rc3 was not available yet, and i had an even worse message on journalctl: Kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun After rc3 was made available, i installed it and the message this CPU pipe FIFO underrun was not in the logs anymore. But all the other messages are there still. > In which log > are you seeing the above error? This message is from journalctl -ax and persisted after installation at everyboot until today for 3 weeks. > > Dec 22 16:29:16 dom0 systemd-modules-load[540]: Inserted module 'uinput' > > OK, so it's working on yours too. > > > Dec 22 16:29:12 dom0 systemd[1]: 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. > > > 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? > > Ignore this error. It does not impact Qubes functionality. Qubes is working fine, but due to the problems i had already with this machine before, after several reinstalls, including the worrying journalctl message "CPU pipe A FIFO Underrun" mentioned above; since 'uinput' is related to keyboard and mouse and it is failing, how can i be sure the version that is being loaded is not somehow tainted? Because it fails on first try, right? 'uinput' deals with keyboard and mouse and although they work fine, they seem to be perfect for logging user activity ( keyboard and mouse ). > > > > Dec 15 20:52:37 dom0 xenstored[1267]: Checking store complete. > > > > > > Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name > > > > org.freedesktop.UDisks2 on the system message bus > > > > Dec 15 20:52:38 dom0 udisksd[1497]: 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? > > Ignore the install logs unless you're troubleshooting an installation > issue. Instead, reference the log from a recent boot, and see if those > errors you mentioned are still present (apart from the > "systemd-modules-load.service has failed".) All the errors are still happening since install. I am sorry to insist, but the 'uinput' error is the one that worries me more, pardon my ignorance and thus the question: How can i check the signature of the module loaded? Is it possible? Thank you very much for your help. > - don't top post > Mailing list etiquette: > > - trim quoted reply to only relevant portions > > - when possible, copy and paste text instead of screenshots > > -- > > 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/72d5969d-f052-e2d4-b9bd-36cd5c962291%40danwin1210.me. > -- 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/LOHuS92AhR-_EMwHw2gpBrxSizysb3oTGiLEkP6FtE8k-t4yayuyRXmDhTLSgHnN2C-X25Bd35hqrgQ-eqOso7gPVcQ_Y0eKnCMNtTTXzKI%3D%40pm.me. publickey - bodhisattvayana@pm.me - 0xEC5E8A90.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital
Re: [qubes-users] Ghost in the machine?
'Chökie Gyaltsen' via qubes-users: > 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 Does make some sense if the Linux kernel used now has better support for Intel integrated graphics. Appears it must! >>> Dec 15 20:52:30 dom0 systemd-modules-load[195]: 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 Didn't realize you were running rc3. Have you tried 4.0.1? In which log are you seeing the above error? > Dec 22 16:29:16 dom0 systemd-modules-load[540]: Inserted module 'uinput' OK, so it's working on yours too. > Dec 22 16:29:12 dom0 systemd[1]: 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. > 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? Ignore this error. It does not impact Qubes functionality. >>> Dec 15 20:52:37 dom0 xenstored[1267]: Checking store complete. > >>> Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name >>> org.freedesktop.UDisks2 on the system message bus >>> Dec 15 20:52:38 dom0 udisksd[1497]: 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? Ignore the install logs unless you're troubleshooting an installation issue. Instead, reference the log from a recent boot, and see if those errors you mentioned are still present (apart from the "systemd-modules-load.service has failed".) -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/72d5969d-f052-e2d4-b9bd-36cd5c962291%40danwin1210.me.
Re: [qubes-users] Ghost in the machine?
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[195]: 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[540]: Inserted module 'uinput' Dec 22 16:29:16 dom0 systemd[1]: Started Load Kernel Modules. More info from journalctl journalctl -aex --unit systemd-modules-load.service Dec 22 16:29:12 dom0 systemd-modules-load[199]: Inserted module 'xen_gntalloc' Dec 22 16:29:12 dom0 systemd-modules-load[199]: Inserted module 'xen_blkback' Dec 22 16:29:12 dom0 systemd-modules-load[199]: Inserted module 'xen_pciback' Dec 22 16:29:12 dom0 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Dec 22 16:29:12 dom0 systemd[1]: 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[1]: systemd-modules-load.service: Unit entered failed state. Dec 22 16:29:12 dom0 systemd[1]: systemd-modules-load.service: Failed with resul 'exit-code'.Dec 22 16:29:16 dom0 systemd-modules-load[540]: Inserted module 'uinput' Dec 22 16:29:16 dom0 systemd[1]: 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[1267]: Checking store complete. > > Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name > > org.freedesktop.UDisks2 on the system message bus > > Dec 15 20:52:38 dom0 udisksd[1497]: 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
Re: [qubes-users] Ghost in the machine?
'Chökie Gyaltsen' via qubes-users: > Hello all, > > > I've just installed Qubes latest preview 3. Installed it offline, so all the > logs you will see are from a disconnected system. There are some services > disabled related to security that worry me ( listed below ). Also some > entries that i have some doubts on sys logs ( written below also ). I had a > critical warning just after the install, related to gtk before the login > screen. Attached are all the logs found, complete. If you need some other > info please just let me know. > > output of systemctl -al showing inactive services only ( full list of > services attached ) > > - > UNIT > LOAD ACTIVE SUB > DESCRIPTION > boot.automount >loadedinactive dead boot.automount > The question here is if it is normal that these services are disabled on > first login just after a disconnected install? Yes; most of those only fire once on boot and are no longer needed afterwards. > > > > output of journalctl -ax --merge ( full journalctl output attached ) below > the messages i have some comments on my doubts > - > 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.> > Dec 15 20:52:30 dom0 systemd-modules-load[195]: 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. > Dec 15 20:52:31 dom0 kernel: nvme nvme0: missing or invalid SUBNQN field. > Dec 15 20:52:31 dom0 kernel: nvme nvme0: Shutdown timeout set to 8 seconds > Dec 15 20:52:31 dom0 kernel: nvme0n1: p1 p2 > ( after some searching i found that this message is related to the boot disk > Samsung V-NAND SSD 970 PRO NVMe M.2, just installed. The hardware is pretty > new but Samsung has made available the source code for 'magician' ( if i > remember correctly, ( i am still offline ), software under request. The linux > version is old and does not recognize any of the disks present on the > machine. Do you know of any opensource project ongoing to port the tool to > linux? ) No, but I am not aware of any functionality the software provides that can't be accomplished some other way. Not really Qubes related, though. > Dec 15 20:52:34 dom0 kernel: platform regulatory.0: Direct firmware load for > regulatory.db failed with error -2 > ( is it normal this error? ) Yes, Xen/Qubes blocks some direct hardware access. > Dec 15 20:52:35 dom0 systemd[1]: tmp.mount: Directory /tmp to mount over is > not empty, mounting anyway. > ( this always happened in previous installations, strange no? ) Typical on a remount. > Dec 15 20:52:36 dom0 systemd-tmpfiles[1180]: Cannot set file attribute for > '/var/log/journal', value=0x0080, mask=0x0080: Operation not supported > Dec 15 20:52:36 dom0 systemd-tmpfiles[1180]: Cannot set file attribute for > '/var/log/journal/2f474aa11eba4b1394708823e685bcd8', value=0x0080, > mask=0x0080: Operation not supported > ( is this normal? ) My logs show it too. > Dec 15 20:52:36 dom0 xenstored[1267]: TDB: tdb_open_ex: could not open file > /var/lib/xenstored/tdb: No such file or directory > Dec 15 20:52:36 dom0 xenstored[1267]: Checking store ... > ( this message happens at every boot ) Same. > Dec 15 20:52:37 dom0 xenstored[1267]: Checking store complete. > > Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name org.freedesktop.UDisks2 > on the system message bus > Dec 15 20:52:38 dom0 udisksd[1497]: 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. > Dec 15 22:29:02
