Qubes User:
> Hi everyone,
> Thank you for all your help and discussion. I posted the HCL for the device
> I'm troubleshooting -- the latest Lenovo Flex 14 with the i5-10210U. You
> can find it here:
>
https://groups.google.com/forum/#!topic/qubes-users/kamMImlGMNQ
>
> I'm guessing the plan is to set up networking, update the templates and
> dom0, then troubleshoot the trackpad and external monitor. I plugged in the
> monitor with HDMI and it didn't show up under System Tools > Display, and
> my touchpad doesn't show up under System Tools > Mouse and Touchpad.
Looking at your lspci, I'm guessing the machine doesn't have any wired
networking? (I was going to suggest using a wired connection temporarily
to install updates)
Just to be clear, are you trying to use a USB wireless card, or the
internal wireless card?
I meant for you to run `iw list`, not `iwlist`, which is a different
command. Sorry for the confusion. However from the iwconfig & ifconfig,
I'm fairly certain it won't show up in `iw list` anyways.
Not sure what this is. Googling Adomax, I get a bunch of keyboards, so
I'm guessing your device's internal keyboard is USB (as opposed to LPC
or the like). Weird that it's showing up in sys-net and not sys-usb.
Also weird that's the only USB device listed besides the hub. I'm not
seeing any USB network cards.
So it looks like your network card is detected but not recognized. If it
is recognized it should show the full name of the device, instead of the
raw product code. In this case, "Intel Wireless-AC 9462". And as you
noted, no kernel drivers are loaded. This card uses 'iwlwifi'.
If this is a relatively new model card, it could be that the kernel is
just too old, and doesn't have the drivers. You could try installing a
newer kernel, but that's going to be difficult without networking.
https://www.qubes-os.org/doc/newer-hardware-troubleshooting/
https://www.qubes-os.org/doc/software-update-dom0/#kernel-upgrade
Looking at the Linux Kernel Driver Database, I see your device (02f0)
appears to be present in kernel 5.0 at the earliest (if I'm reading it
correctly).
https://cateee.net/lkddb/web-lkddb/WLAN_VENDOR_INTEL.html
Here's a thread about your same card on 5.0.0, with info about manually
installing the firmware. I'm not sure if it helps.
https://askubuntu.com/questions/1180765/intel-wifi-card-not-working-on-ubuntu
I sort of don't think it's a firmware issue at this point, though,
because even if the firmware were missing, I think lspci would still
show the full name of the card. Do you see anything in the kernel logs
about the firmware, or about the card at all?
Personally I would first try a newer (>=5.0) kernel, and then tackle the
firmware issue next if it's still not working.
> There's no Kernel driver in use or Kernel modules as we would expect under
> the output for lspci -k (as seen on the wireless troubleshooting page
> <
https://www.qubes-os.org/doc/wireless-troubleshooting/>). This happens
> also when I run lspci -k in dom0. Could this be related to the
>
>> [FAILED] Failed to start Load Kernel Modules.
I'm pretty sure I've seen that on every machine I've ever install Qubes
on, even when everything works fine. I probably wouldn't worry too much
about it, but here's a guide on how to troubleshoot that message:
https://superuser.com/questions/997938/how-do-i-figure-out-why-systemctl-service-systemd-modules-load-fails
Is the network card assigned to sys-net, according to Qubes Manager ->
VM settings -> Devices?
>>
> that I'm getting on each start-up and shut-down?
>
> When I run lspci |grep -i wireless, I don't receive any output. When I run journalctl
> -k -b |grep -i input in dom0, I see: Lid Switch, Power Button, Power
> Button, AT Translated Set 2 keyboard, Ideapad extra buttons, PC Speaker,
> Integrated Camera: Integrated C, and my logitech receiver and mouses, but I
> don't see anything about my touchpad.
Hmm, I can't think of anything at the moment about the touchpad. I'll
have to look into it and get back to you. For now all I can say is try a
newer kernel, as that can fix (or cause) all sorts of different hardware
problems.
> Any suggestions on what to do next given these outputs?
> How can I check whether my firmware is installed correctly in my Fedora 29
> template?
>
> I went back to the boot menu to look at my usb installer that I used to
> install 4.0.1 on my Flex. On the boot menu, I see two options for my usb
> installer. EFI USB Device (my USB) and USB HDD : my USB. When I go to the
> EFI option, I don't see the boot menu as shown on the installation guide
> <
https://www.qubes-os.org/doc/installation-guide/>, but when go to the HDD
> option, I do. When enter the HDD option and run the test this media, the
> test fails, and the installation fails. When I run the EFI option, the
> installer boots and I can install Qubes. What does test media do and what
> does it mean when it fails? Could having a failed test media result in some
> of the problems I'm experiencing with my current installation? I used the
> Rufus tool on Windows and dd mode to create my installation USB. Should I
> first install something else (e.g., Fedora) then recreate my installation
> medium using dd from the command line? I'm pretty sure I properly verified
> my download of the iso (I'm not sure if it's related):
It sounds like "USB HDD" is the legacy mode option for the same device.
UEFI is strongly recommended if it's working okay. UEFI bypasses grub,
that's why you don't see the boot menu in UEFI but you do in legacy.
I don't know why it's failing the media test. In theory it should test
and run fine in legacy mode, but that's often not the case. You can try
re-writing the ISO, perhaps on a different USB drive. But I think if the
image were corrupt you'd run into major problems with the installer even
in UEFI mode.
>
>> gpg -v --verify Qubes-R4.0.1-x86_64.iso.asc Qubes-R4.0.1-x86_64.iso
>> gpg: Signature made 01/05/19 19:05:39 Pacific Standard Time
>> gpg: using RSA key 5817A43B283DE5A9181A522E1848792F9E2795E9
>> gpg: using pgp trust model
>> gpg: Good signature from "Qubes OS Release 4 Signing Key" [full]
>> gpg: binary signature, digest algorithm SHA256, key algorithm rsa4096
>>
>
> Once again, thank you everyone for the questions, discussion, and
> suggestions.
I looked at your HCL report, and given the number of issues you're
facing, it might be worth trying a R4.1 pre-release build, which is
based on F29 and Xen 4.12. These builds are considered unstable, but you
very well might end up with fewer headaches than the older stable releases.
Here is the latest build (click assets tab for ISO):
https://openqa.qubes-os.org/tests/4428
By the end of the month, the developers plan on releasing an official
testing ISO for R4.1 based on Fedora 31.
https://www.mail-archive.com/qubes...@googlegroups.com/msg31288.html