See inlines. On Friday, January 4, 2019 at 5:16:16 PM UTC-5, Achim Patzner wrote: > > The good old I219-LM problem... Before assigning (or after 8-) it to > sys-net (I do not really see any reason it should be assigned to sys- > firewall... are you sure?) it needs to get set to no-strict-reset=true > and permissive=true; take a look at qubes-os.org.
I think you mis-understand. I am not assigning/attaching anything. This is doing installation only that generates the error. > Use the dGPU or take care of turning off the nouveau driver completely > (nouveau.modesetting=0). > > Why don't you use the nVidia GPU instead? It is definitely faster than > the iGPU anyway, booting faster, using (at least on my machine) less > energy and you do not meed to modify the kernel command line. And on > kernel-latest my system is working with all cores. > That is not ideal. The main reasons to disable the dGPU is for battery life. Under Arch, I can do this (not efficiently have you) with bbswitch. However, I am not making it that far with Qubes as I cannot boot into the system after installation. > > WARNING (to anyone else installing on a P1/X1 Extreme/P52, etc): To > > install, you must switch to discrete graphics in BIOS (no hybrid). But, DO > > NOT DO THIS unless you have BIOS 1.17 or later or you will BRICK YOUR > > THINKPAD! > > That didn't break mine. Turning on Thunderbolt BIOS support and turning > off secure boot did that for me. Switching to dGPU is only causing > problems if you do not wait on the next reboot for the system to > reinitialize the device tree in ME (and thus starting with empty ACPI > tables) by resetting it at just the right time during the 30 seconds > this would take. > First of all, what laptop do you have? "That didn't break mine" indicates you also have a P1? Please share your experience installing Qubes to a fully functional state (including suspend - not even us Arch guys have figured out suspend yet with the ACPI tables on the P1). It is an extremely well known bricking problem with all modern (early to late 2018) Lenovo Thinkpad models: https://www.reddit.com/r/thinkpad/comments/a2g0k4/warning_do_not_change_from_hybrid_graphics_to/ (and dozens of threads on the Lenovo forums) If you have an early 2018 Thinkpad, you're pretty much ok. My warning applies to all current models. It got so bad Lenovo actually pulled the last 2 or 3 BIOS from just about every Thinkpad and Yoga series from the downloads site. The 1.15 my P1 came with is long gone, as well as the 1.13 version that was there. Only 1.10 and 1.17 are available now - and 1.17 I can confirm does not brick it. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6dfd1f09-1434-4639-9afc-15959fc8eeb5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
