[qubes-users] nvme0n1 may not have enough space for grub2 to embed core.img when using the ext4 file system on lvm
Hello, I got this problem when trying to install R4.0.1 on my Lenovo Thinkpad P7. It has 2 HDs of which the second contains an original Windows 10 install for which I can choose the boot loader if I want to run it. On the first HD I have the following partitioning scheme in Anaconda: Qubes Linux 4.0.1 for x86_64 System 920 GiB, device type: LVM encrypt, vol group: qubes_dom0, /file system: Ext4, Name: root qubes_dom)-root /boot/efi 100 MiB, device type: Standard partition, nvme0n1p3 file system: EFI System Partition, Name: nvme0n1p3 swap 30 GiB, device type: LVM encrypt, vol group: qubes_dom0 file system: swap, Name: 00 Unknown Unknown 128 MiB, nvme0n1p1 EFI Sys part200 MiB nvme0n1p2 I guess these Unknown and EFI Sys Partition are there to have some boot loader for Windows. Now when I accept these settings, I get the warning: "nvme0n1 may not have enough space for grub2 to embed core.img when using the ext4 file system on lvmlv" Does anyone know how to solve this problem? BIOS is set to 'Legacy'. -- 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/bfc80628-3030-4e78-bc86-43d80e7e1cca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] 4.0.1
I see you guys (or is it folks?) replaced the 4.0.1pre1 with the 4.0.1, thank you for that! :) -- 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/8392be55-1d6e-4815-bc16-9cd4d93800bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Boot failure after update / boot loop
What I don't understand, is that the update script doesn't check whether actually there is enough space for the new kernel, or its keys if that's the issue. Feels like a bug to 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 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/b6e1bb39-d4eb-4aaa-b92d-c75c464e5041%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Boot failure after update / boot loop
On Wednesday, October 31, 2018 at 8:54:03 PM UTC, Alchemist wrote: > Just grew the partition. easy enough to do in Gparted. And how about the suggestion of using an older kernel in xen.cfg? Did you do that? Did you grow the /boot partition after that and just returned xen.cfg to the new kernel? Thanks. -- 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/04b70219-47ab-4231-9f1b-1e840e474139%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Boot failure after update / boot loop
On Tuesday, October 30, 2018 at 5:39:21 AM UTC, Alchemist wrote: > Do you dual boot with Windows? > > If you do, the reason is that by default the Windows 10 installer will set > the /boot/efi partition to 100mb which... is really not enough space. > > > So keep that in mind. I made the changes and now it's happy. So, after changing the kernel to boot in /boot/efi/EFI/qubes/xen.cfg, what exactly did you do to solve the problem? Did you change the size of /boot/efi without reformatting your HD and re-installing qubes? If so, how? Please tell me. :) By the way, I remember that when I installed Qubes 4 (after having used an older one) I also increased the size of the separate EFI boot partition. I'll have to check that out. -- 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/722a7851-62de-486e-bf12-4d434d65b945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Boot failure after update / boot loop
On Sunday, October 21, 2018 at 3:15:37 PM UTC, Alchemist wrote: > So i just installed 4.0 and updated it, after I ran the update I rebooted. > > I'm no longer able to boot into qubes, even using refid, I can see the EFI > boot string but it just shuts down the machine. I've got the same problem, see my 'miss-post' https://groups.google.com/forum/#!topic/qubes-users/eW3N434-tlo and will try the same solution as offered by @awokd. -- 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/46ea3f0e-88ac-4583-9b92-748e1d1ce3be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: system doesn't boot after update
On Monday, October 29, 2018 at 4:39:03 AM UTC, joeh...@gmail.com wrote: > Me too, I did qvm-dom0-update yesterday and when it tried to re-boot it got > in a boot loop, and I'll re-type the messages here: > - > Xen 4.8.4 (c/s) EFI loader > Using configuration file 'xen.cfg' > vmlinux-4.14.74-1.pvops.qubes.x86_64: 0x495ae000-0x49b8db20 > initramfs-4.14.74-1.pvops.qubes.x86_64.img: > 0x49002000-0x495ae000 > 0x:0x01:0x00.0x0: ROM: 0x19400 bytes at 0x5302e018 > 0x:0x00:0x02.0x0: ROM: 0x1 bytes at 0x5300c018 > - > [0.179397] ACPI Error: [\_SB_.PCIO.XHC_.?HUB.HS11] Namespace lookup > failure > AE-NOT_FOUND (20170720/dswload-210) > [0.179406] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog > (20170720/psobject-252) > [0.179500] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSalt) while loading > table (20170728/tbxfload-220) > [0.188039] ACPI Error: 1 table load failures, 11 successful > (20170728/tbxflad-246) > [0.508657] Initramfs unpacking failed: read error > [2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on > unknown-block(0.0) > [2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted > 4.1474-1.pvops.qubes.x86_64 #1 > [2.762790] Hardware name: LENOVO, BIOS N1TET41W (1.15) 10/20/2017 > [2.762813] Call Trace: > [2.762826] dump_stack+0x5c/0x85 > [2.762839] panic+0xc4/0x252 > [2.762851] mount_block_root+0x35b/0x52c > [2.762865] ? do_early_param+0x16e/0x16e > [2.762879] prepare_namespace+0x278/0x245 > [2.762892] ? do_early_param+0x16e/0x16e > [2.762905] kernel_init_freeable+0x2c8/0x324 > [2.762920] ? rest_init+0xb0/0xb0 > [2.762932] kernel_init+0xa/0x101 > [2.762945] ret_from_fork+0x35/0x40 > [2.762964] Kernel Offset: disabled > > > I anyone could help me get my qubes running again I'd be much obliged. I just see there was another one with the same problem: https://groups.google.com/forum/#!topic/qubes-users/ftXn36ipklQ I'm going to try the solution proposed there and will continue in that thread, as it is more related than this one. Sorry for the wrong posting here. -- 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/058a7857-a840-4516-922c-6fc42c66a56c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: system doesn't boot after update
Me too, I did qvm-dom0-update yesterday and when it tried to re-boot it got in a boot loop, and I'll re-type the messages here: - Xen 4.8.4 (c/s) EFI loader Using configuration file 'xen.cfg' vmlinux-4.14.74-1.pvops.qubes.x86_64: 0x495ae000-0x49b8db20 initramfs-4.14.74-1.pvops.qubes.x86_64.img: 0x49002000-0x495ae000 0x:0x01:0x00.0x0: ROM: 0x19400 bytes at 0x5302e018 0x:0x00:0x02.0x0: ROM: 0x1 bytes at 0x5300c018 - [0.179397] ACPI Error: [\_SB_.PCIO.XHC_.?HUB.HS11] Namespace lookup failure AE-NOT_FOUND (20170720/dswload-210) [0.179406] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170720/psobject-252) [0.179500] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSalt) while loading table (20170728/tbxfload-220) [0.188039] ACPI Error: 1 table load failures, 11 successful (20170728/tbxflad-246) [0.508657] Initramfs unpacking failed: read error [2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on unknown-block(0.0) [2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted 4.1474-1.pvops.qubes.x86_64 #1 [2.762790] Hardware name: LENOVO, BIOS N1TET41W (1.15) 10/20/2017 [2.762813] Call Trace: [2.762826] dump_stack+0x5c/0x85 [2.762839] panic+0xc4/0x252 [2.762851] mount_block_root+0x35b/0x52c [2.762865] ? do_early_param+0x16e/0x16e [2.762879] prepare_namespace+0x278/0x245 [2.762892] ? do_early_param+0x16e/0x16e [2.762905] kernel_init_freeable+0x2c8/0x324 [2.762920] ? rest_init+0xb0/0xb0 [2.762932] kernel_init+0xa/0x101 [2.762945] ret_from_fork+0x35/0x40 [2.762964] Kernel Offset: disabled I anyone could help me get my qubes running again I'd be much obliged. -- 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/17aa1c5d-b5b8-42fe-8144-f79fcf1f895f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes4.0 rc3 install error
On Monday, December 4, 2017 at 9:59:33 PM UTC+8, awokd wrote: > On Mon, December 4, 2017 3:57 am, Shashank wrote: > > > At least 3MB more required for /boot/efi > > If there is nothing on the drive you need to keep, choose the "I need to > recover space" option in the installer. Mark the top level of the tree so > EVERYTHING on the drive will be deleted. Let the Qubes/Xen installer > Auto-partition your space. A bit late maybe, but then I just installed Qubes R4.0 on my laptop (Lenovo P70) with Windows 10 pre-installed. Previously I had Qubes R3.2 installed and now the 200 MB EFI partition that was to be mounted on /boot/efi was too small. I followed ahint of somebody (maybe even in this thread?). In Anaconda, for the Qubes R4.0 install, there were two entries for one 200 MB partition mounted to /boot/efi. One under 'unknown', one under 'SYSTEM' in the new to install Linux. I removed that one and created a new one, 300 MB big, probably unnecessarily big because I guess it will only contain the UEFI keys for this one instance of Qubes, but anyway, it worked. Qubes installed, with a freeze however while configuring Qubes, but the second time configuration completed, Qubes works, and Windows still works. -- 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/3f42f4c7-e2a7-42e3-8cf6-21b4c49f8230%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Feedback Qubes-R4.0-rc4 on a Lenovo Thinkpad P71
Before installing Qubes-R4.0-rc4-x86_64 on my laptop in UEFI mode but not secure boot, I first had to follow the instructions on https://www.qubes-os.org/doc/thinkpad-troubleshooting/ summarized below: In a nutshell, you need to use the Fedora livecd-tools to make a Qubes Installation USB Stick from the Qubes ISO image, then update the label on the partition of that USB stick to “BOOT”, and then update the BOOT/EFI/xen.cfg file on the USB stick so that all labels point to BOOT. Then it installed properly. However, there still seems to be some issues as reported by dmesg output below. -- ~]$ sudo dmesg --notime --show-delta --level=err,warn [<0.00>] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload-210) [<0.11>] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252) [<0.000229>] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSsdt) while loading table (20170728/tbxfload-228) [<0.012538>] ACPI Error: 1 table load failures, 11 successful (20170728/tbxfload-246) [<0.003614>] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [<0.01>] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [<0.001585>] cpu 0 spinlock event irq 121 [<0.001459>] cpu 1 spinlock event irq 133 [<0.000567>] cpu 2 spinlock event irq 140 [<0.000315>] cpu 3 spinlock event irq 147 [<0.000803>] cpu 4 spinlock event irq 154 [<0.000200>] cpu 5 spinlock event irq 161 [<0.000787>] cpu 6 spinlock event irq 168 [<0.000184>] cpu 7 spinlock event irq 175 [<0.001973>] Grant table initialized [<1.030409>] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [<0.026886>] hpet_acpi_add: no address or irqs in _CRS [<1.260721>] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [<0.67>] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [<0.021726>] i915: unknown parameter 'preliminary_hw_support' ignored [<0.008035>] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170728/nsarguments-100) [<0.000105>] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170728/nsarguments-100) [<0.373511>] nouveau :01:00.0: bus: MMIO read of FAULT at 022554 [ IBUS ] [<0.001572>] nouveau :01:00.0: bus: MMIO read of FAULT at 10ac08 [ IBUS ] [<0.874699>] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [< 69.549364>] device-mapper: thin: Data device (dm-2) discard unsupported: Disabling discard passdown. [<0.466515>] systemd: 26 output lines suppressed due to ratelimiting [<0.708450>] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [<5.237246>] kauditd_printk_skb: 81 callbacks suppressed [< 88.634764>] kauditd_printk_skb: 1 callbacks suppressed [< 10.806499>] kauditd_printk_skb: 7 callbacks suppressed [< 72.680640>] kauditd_printk_skb: 1 callbacks suppressed [< 11.120214>] kauditd_printk_skb: 7 callbacks suppressed [< 78.707516>] kauditd_printk_skb: 1 callbacks suppressed [< 10.752228>] kauditd_printk_skb: 7 callbacks suppressed [< 75.713107>] kauditd_printk_skb: 1 callbacks suppressed [< 11.964648>] kauditd_printk_skb: 7 callbacks suppressed [< 66.095443>] kauditd_printk_skb: 147 callbacks suppressed [<6.035025>] kauditd_printk_skb: 82 callbacks suppressed [<5.029873>] kauditd_printk_skb: 102 callbacks suppressed [<5.544555>] kauditd_printk_skb: 90 callbacks suppressed [<5.002831>] kauditd_printk_skb: 88 callbacks suppressed [< 41.219150>] kauditd_printk_skb: 34 callbacks suppressed [< 36.255902>] xen_pciback: :00:14.0: cannot enable memory-write-invalidate (-22) [< 142.443039>] kauditd_printk_skb: 4 callbacks suppressed [< 198.824432>] kauditd_printk_skb: 5 callbacks suppressed -- -- 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/167ebaa8-4633-49d5-aa6a-23c550cfb5d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0-rc3 not installing on Lenovo P71
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: 0x800e [ 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
[qubes-users] Re: Lenovo ThinkPad, won't boot
On Tuesday, January 30, 2018 at 7:24:23 AM UTC+8, Tim W wrote: > Here is a thread with steps to get uefi install of 3.2 working on the p51 > from a few weeks ago > > https://groups.google.com/forum/m/#!topic/qubes-users/4VsKdxnKHBk > > Cbeers, > > Tim Here is a page from the qubes documentation: https://www.qubes-os.org/doc/thinkpad-troubleshooting/ -- 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/9fb34b05-8135-47e4-af37-2c33e7883b51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0-rc3 not installing on Lenovo P71
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: 0x800e [ 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. > > Thanks for the suggestion. I pressed after putting the cursor on 'test image then start qubes' and got a line: /ubnkern
Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71
On Sunday, January 28, 2018 at 10:30:47 AM UTC+8, awokd wrote: > On Sun, January 28, 2018 2:13 am, xxx 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: 0x800e [ 137.216201] dracut-initqueue[566]: > > Looks like a buggy firmware. See if your manufacturer has a bios update. > Could maybe try turning off power saving since some messages sort of sound > related. If you don't care about EFI, you could disable it and boot and > install in legacy mode. If you want EFI, could try booting Refind, then > the installer from there. I just updated the BIOS yesterday through the Lenovo Avantage program. Starting Windows doesn't present any problems. I'll check out your other suggestions, thanks. -- 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/df3606ee-3eb1-4c6b-8f9d-a715622ac32b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71
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: 0x800e [ 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 -- 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/a41da9e6-8ef4-43e6-ae62-babf1b1f2507%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
