On Friday, June 2, 2017 at 3:59:09 PM UTC-4, Stephan Marwedel wrote: > On 6/2/17 7:11 AM, cooloutac wrote: > > On Thursday, June 1, 2017 at 2:31:10 PM UTC-4, Stephan Marwedel wrote: > >> I have trouble booting the installer. Using the standard UEFI setup of > >> the T470p does not work at all. Switching to legacy boot settings boots > >> into the GRUB menu. However, when I tried to actually boot into the > >> Qubes installer it immediately performs a reboot. This means that I > >> never get to the point to actually install Qubes on the machine. > >> > >> I tried to boot the vanilla Fedora 23 live system. It boots without any > >> problem using both the standard UEFI setup and legacy boot. What is the > >> difference between Qubes and Fedora 23 that prevents Qubes from being > >> booted on that machine? May it be related to Secure Boot or TPM settings? > >> > >> On 05/20/2017 03:28 AM, cooloutac wrote: > >>> On Friday, May 19, 2017 at 5:23:58 PM UTC-4, Stephan Marwedel wrote: > >>>> I recently got a new Kaby Lake Thinkpad. It runs fine with Archlinux. > >>>> > >>>> However, I wanted to install Qubes on it and installed a second SSD for > >>>> that purpose. Even following the hints from the official Qubes > >>>> documentation I was unable to install Qubes 3.2 from the original > >>>> installer. It seems that this machine is simply too new for Qubes 3.2. > >>>> How can I try it out with newer kernels? May alpha or beta versions of > >>>> upcoming release be worth a try?? > >>>> > >>>> Any hints appreciated. > >>> what about baremetal fedora23?, if it work with that should be able to > >>> get it working in qubes maybe you need later kernel version from testing > >>> repo. > >>> > > secure boot has to be off. > I turned secure boot off and tried various combinations of boot > settings, like UEFI with CSM and pure legacy boot to no avail. Using > legacy boot, the GRUB menu appears. When I select the menu item "Install > Qubes" I see a message in text mode about the kernel being loaded. > Shortly after, I the screen goes blank and the system performs a reboot. > Nop error message is displayed. Something seems to be fundamentally > wrong with either my setup or the combination of Qubes 3.2 with this > particular machine. Does anybody else have similar experience with a > machine of this type?
try legacy boot again, and and test with vt-d off maybe. only difference I can think of. disable secondary gpu and network card too. make sure gpu has enough memory. double check bios options maybe usb settings too. -- 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/aba11235-9b46-4ad3-9024-90cb6018449e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
