I'm not defending anything, nor anyone.
when the install goes as planned, q40s creates a root.disk (swap as well) image that gets loop mounted at boot that has its own shim64.efi file in the efi system partition. unless i am missing something, this appears to be a full linux (debian 11 based) system running on its own. the disk image is stored in windows 10's ntfs partition, but shows as ext4 in lsblk.
i hope i didn't overstate or oversell my familiarity with q4os. when i first started with linux a few years ago, like you, i was in search of lightweight linux distributions to use on (for me) an older system with not much ram or a particularly powerful cpu. i tested q4os at the time, but eventually settled with something different.
gnome-boxes. that program is also available (without installing Synaptic) in Plasma Discover listed as GNOME Boxes: https://help.gnome.org/users/gnome-boxes/stable/Are you not a native English speaker? Would explain why we totally speak past each other repeatedly?
Good point. I was under the impression Q4OS would take over the hardware and security competely. But I can imagine that a virus could indeed do changes, for example to .exe files on the drive though Q4OS. What is easy and efficient against such exploits in linux?
With what you settled and for what reason in the end?
Showed that amount of RAM usage in my case too.
I couldn't accomplish yet. Because no WLAN was recognized, along with Sound. Anyway my nightshift work is in an emergency sleeping shelter, and one guest with a little linux experience could add the sound already. Alledgedly by changing it to something virtual. Later he remembered that in linux one command line is needed only, to turn ethernet on. He will try that tonight.
i settled on bodhi linux and used it for a few years in part because of the fact that it was lightweight, but also because it was suggested that it might be a little harder to use for beginners since i was looking to learn a bit more about the internal workings: https://www.bodhilinux.com/
before you mentioned a different distribution (slitaz maybe?) had a windows installer, i hadn't thought about Q4OS and that option in some time. as you said, since it isn't is normally suggested it just didn't cross my mind until then.
if that works to get your ethernet running, there is a package called
hardinfo and listed as System Profiler and Benchmark in the Plasma Discover Software Center. that program has a graphical user interface may be able to provide the guest and you with some added info about the WLAN adapter if it still isn't working.lspci -knn | grep -iA3 netThe guest was unable to. But I did find this info in the graphic interface:
Network
Device-1: Realtec RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID, 10ec:c8168 class ID: 0200
IF: enp2s0 state: down mac: 28:1d:ef:2d:6e:ee
Device-2 Realtec RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: N/A modules: rtw88_8821ce port: d000 bus ID: 03:00.0 chip ID: 10ec:c821 class ID: 0280Brings:
02:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/
8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Exp
ress Gigabit Ethernet Controller [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE
802.11ac PCIe Wireless NEtwork Adapter [10ec:c821]
Subsystem: Realtek Semiconductor Co., Ltd. RtL8821CE 802.11ac PCIe W
ireless Network Adapter [10ec:c821]
Kernel modules rtw88_8821cei'll add this link real quick about usb tethering a smartphone (in case you have one) to see if that may get you started then look at the other info you posted: https://www.makeuseof.com/tag/how-to-tether-your-smartphone-in-linux/
when an adapter is working the state should be "up". can you try clicking on the network icon in the bottom right of the screen to see if it will allow you to connect from there? if not, you may be able to right-click on the connection name (often "Wired connection 1") to check the configuration settings.
sudo ip link set enp2s0 upone of the functional differences between the two is the lack of a "Kernel driver in use" line for the wireless adapter. that is most likely why this output looks different as well:
you'll notice there is no interface name (IF) and no state listed for the wireless adapter so you wouldn't be able to use the previous command to try and bring it UP.
journalctl -b | grep -iE '03:00.0|8821ce'Showed only 'no connection available' (I'm translating from the German interface).
Shows exactly the same.
Strange. When I come to the first vertical line in this code, it automaticlly changes it to:
lspi -knn | grep -iA3 netmy apologies. that's because i left out the part where it would have to be installed. i was able to do so though Discover and meant to add that part.
you are quite welcome.
i've not seen that before. you could try
journalctl -b -g '03:00.0|8821ce'journalctl -b -g '02:00.0|r8169|enp2s0'Actually might be just a less failed installation of Q4OS again.
failed to load open \EFI\DEBIAN\***S* - Invalid parameter
Failed to load image**: Invalid parameter
start_image() returned Invalid parameter, falling back to defauld loaderhelped me realize that i see what seems like very similar text when booting. on my system (i know it may be limited since they are both virtual machines), i don't get a menu before that text. the text flashes briefly like you said and then i get the menu with q4os, windows and bios.
that certainly isn't something i have seen before. or if it happens with other distros, it has been too quick for me to take notice of. however, even with what seems like similar text and quirky boot behavior to yours, the virtual machine's networking works as expected.
changed to:
lspi -knn | grep -iA3 net8821cs'Again changing to something else with the first |
journalctl -b -g 03:00.0journalctl -b -g 8821cejournalctl -b -g 02:00.0journalctl -b -g r8169journalctl -b -g enp2s0
