On Monday, January 29, 2018 at 10:11:12 AM UTC+8, Qubed One wrote: > Yuraeitha: > > On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com > > wrote: > >> I burned the ISO to USB stick then started to install Qubes but got > >> the following: > >> > >> [ 0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace > >> lookup failure, AE_NOT_FOUND (20170531/dswload-210) [ 0.093383] > >> ACPI Exception: AE_NOT_FOUND, During name lookup/catalog > >> (20170531/psobject-252) [ 0.093539] ACPI Exception: > >> AE_NOT_FOUND, (SSDT:ProjSsdt) while loading table > >> (20170531/tbxfload-220) [ 0.098243] ACPI Error: 1 table load > >> failures, 12 successful (20170531/tbxfload-246) [ 2.376031] > >> Couldn't get size: 0x800000000000000e [ 137.216201] > >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting > >> timeout scripts [ 137.779207] dracut-initqueue[566]: Warning: > >> Dracut-initqueue timeout - starting timeout scripts [ 138.324711] > >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting > >> timeout scripts [ 138.852226] dracut-initqueue[566]: Warning: > >> Dracut-initqueue timeout - starting timeout scripts [ 139.395971] > >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting > >> timeout scripts . . . > >> > >> This went on for some time, so I switched off and wrote this > >> message. I hope there are no serious typos coz I typed this off of > >> a picture taken of the screen. > >> > >> Any hints? Thanks > > > > I'm by no means an expert on the kernel, but dracut "looks" like > > kernel errors, and "ACPI" (Advanced Configuration and Power > > Interface) looks like a firmware/kernel support mismatch, either by a > > lack of features, lack of development, firmware-bug, kernel-bug, or > > possibly an un-updated firmware. The firmware should be the > > motherboard (BIOS/UEFI). > > > > You could start looking in your BIOS/UEFI after settings that may be > > wrong and require adjustments. Is VT-d enabled? Is there a second > > "Virtualization" that needs enabling, for exaple under "Advanced --> > > CPU" UEFI settings? There can be other settings too, it's hard to > > mention them all, but those two are the most important ones, which is > > sometimes only 1 merged setting. > > > > Does your hardware support VT-d and other Qubes hardware > > requirements? Does Qubes 3.2. run on this hardware? Qubes 4 is known > > to be more strict to hardware requirements and may not work smoothly > > or may not even install if the hardware requirements or security is > > not correct. Qubes 3.2. is less an issue when missing VT-d and > > similar. This might also be a place to look and confirm. If you got > > Qubes 3.2. running on the machine, then try run in dom0 > > "qubes-hcl-report" to see if you meet the requirements. > > > > However, dracut/ACPI errors doesn't strike me as errors that appear > > if there are issues with the Qubes 4 specific requirements. > > > > You may want to try install with LegacyBIOS/Grub if you tried > > UEFI/EFI, or vice versa, whichever you did not try yet. You can also > > update your BIOS/UEFI to the newest version, however be sure you > > don't brick your machine. Make sure you know any pitfalls as it may > > make your motherboard break and become useless. > > > > The kernel contains drivers too, the most essential ones, while the > > modules contain extra drivers for the kernel. These errors could also > > be driver issues, for example you may have to edit the EFI or the > > Grub to pick a different driver before starting. Unfortunately I > > believe you need to edit the /boot/efi/EFI.cfg file on the install > > media, but you can more easily change it live on Grub by hovering > > over the install menu, and thne press "E" key to edit the install > > menu in grub. Here you can change ACPI settings, drivers, > > virtulization states, hide/unhide hardware, and so on. > > > Maybe try this: hit e at this point as directed, then add: > acpi=off > to the end of the long line that begins with: > module /vmlinuz-4... > > then boot in to the installer from there. > > > > I'm not sure if it even is a driver issue, I can't see that from the > > logs, whether it can be found there or not. But it's some clues to go > > with, and maybe you can google some up to trial and error. Just be > > careful, for example few of the ACPI settings can be dangerous to > > your hardwaree, so double-check any recommendations you find on the > > internet. > > > > Also it may be worth if you can find any ACPI settings in your > > UEFI/BIOS too. > > > > At any rate, I usually solve these kind of problems with trial and > > errors through experiments. Someone more knowledgeable might drop by > > with a better advice. For now though, some clues you can try start > > with if you did not do them already. > >
Ok, I found this web page: https://www.qubes-os.org/doc/thinkpad-troubleshooting/ and got qubes working. However, WiFi and the mouse (sys-usb), even though it worked at the first boot after installation of qubes don't work anymore. Will try again. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a1ce1b02-172b-418e-a930-0d8be5d4f487%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
