Re: [qubes-users] Ethernet socket device not available in Network Connections
[quote] my sys-net is also sys-usb because I used the USB ethernet adapter so I think this is the problem but I don't know how to fix. [/quote] I doubt that this is the problem. Have you assigned the device to sys-net in the "devices" tab of sys-net settings. When sys-net boots up, can you run `sudo journalctl -b ` in sys-net and look for any entries relating to networking devices. It may be that you need specific drivers for the NIC, so knowing what it is would be a help. -- I never presume to speak for the Qubes team. When I comment in the mailing lists I speak for myself. -- 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/ZeO5oqfRsyO49pVY%40thirdeyesecurity.org.
[qubes-users] Ethernet socket device not available in Network Connections
I was using USB ethernet adapter before, but now I have enabled my laptop's own Gb socket and I would like to use this. The device is listed in lspci: > Ethernet controller: Intel Corporation Ethernet Connection blabla The device is not listed in Network Connections application. The only device there is `vif`. I know this device is working in Ubuntu which I am using before. my sys-net is also sys-usb because I used the USB ethernet adapter so I think this is the problem but I don't know how to fix. -- 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/d50f5b93-e244-4423-900d-34469b414478%40magenta.de.
[qubes-users] Where to run undervolt script?
What is the safest way to use undervolt script in Qubes? https://github.com/georgewhewell/undervolt.git This is running on Python. Is it better to use new service qube for this or can I run it in dom0/sys-net/sys-firewall? -- 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/85e151b0-3709-441a-9f13-f17abf07ed1a%40magenta.de.
Re: [qubes-users] Screen sleep doesn't disable backlight
Neil du Preez: On 2024-02-24 16:19, ales...@magenta.de wrote: On Qubes 4,2, when the screen goes to sleep after idle time or when I lock the screen, the screen is black but the backlight is still on. Only when the system goes to Suspend is the backlight turned off. How can I fix this? Hi, I have attached screenshots of xscreensaver and power manager settings that work for me. I discovered them long ago through trial and error, but I don't remember what other combinations worked and didn't. Hope it helps. Yes this helps. Now Lock Screen backlight is off but I didn't try idle sleep yet. -- 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/bea24b39-9098-442e-a66c-65286d093038%40magenta.de.
Re: [qubes-users] Qubes 4.2 error: Failed to remove old efi boot entry.
Neil du Preez: On 2024-02-24 16:02, ales...@magenta.de wrote: In my fresh install of 4.2 this error appeared. The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation? Failed to remove old efi boot entry. This is most likely a kernel or firmware bug. But it would be nice to understand why this happens and how to fix it. You might have a setting in your BIOS that prevents boot entries from being removed. I think you are right, there is the option "boot order lock" enabled in the BIOS. I will try to use efibootmanager to fix this after I have disabled this setting. Thank you for the suggestion! -- 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/8640d9b9-8b29-484d-90bd-e1f163193749%40magenta.de.
