On Sunday, March 24, 2019 at 3:36:10 PM UTC-4, awokd wrote: > Mike Keehan wrote on 3/24/19 3:36 PM: > > On Sun, 24 Mar 2019 02:07:10 -0400 > > Yushatak <[email protected]> wrote: > > > >> Machine has no legacy mode. > >> > >> On Sat, Mar 23, 2019, 11:32 PM Gaijin <[email protected]> wrote: > >> > >>> On 2019-03-24 02:41, Yushatak wrote: > >>>> On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote: > >>>>> When I boot the Qubes installation media (I dd'd it to a USB > >>>>> stick per > >>> the instructions on the site) it initializes Xen, then the kernel > >>> starts booting (Linux penguins, etc.), and then it goes to a black > >>> screen and there's no activity. F1 does nothing. My hardware is a > >>> laptop with an i7 8700K and an Nvidia 1060, so it smelled like > >>> nouveau driver problems to me. However, normally one works around > >>> that by editing the kernel line in grub with nouveau.modeset=0 and > >>> I have no grub! I decided to try editing the grub.conf in the > >>> isolinux directory of the ISO by extracting the iso, editing, then > >>> regenerating the ISO. Someone on IRC was nice enough to provide me > >>> a log from the official build of the ISO so I used the proper > >>> switches/etc.. I booted that in a VM to make sure it was OK as a > >>> sanity check, then wrote that to the USB stick (which takes like 26 > >>> minutes, it's USB 2.. not fun) and it stopped booting after > >>> attaching the USB stick as a SCSI device, not even quite getting to > >>> the black screen. AFAIK my hardware requires a 4.18 kernel and from > >>> what they said on IRC there's nothing newer than 4.14 in Qubes > >>> anyway, but since it tries to boot I don't know. I throw myself > >>> upon your mercy, Qubes community/developers. > >>>> > >>>> Nobody has a single thought? > >>> > >>> Might the solution be putting your BIOS into Legacy mode? > >>> https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU > >>> > >>> In my case switching the HDD from AHCI mode to IDE mode seemed to > >>> get past this blank screen and got me to the install screen. > >>> > >> > > > > I had exactly this problem when I installed Qubes. Searching this mail > > list found the answer. (You have to edit the installation image, or > > mount the image, edit it and build a new image for installation.) > > > I think the issue is he edited grub.cfg but has no legacy mode, which > means grub won't be used. Yushatak, try using that same procedure to > edit xen.cfg instead. It will be somewhere under boot/efi/EFI/qubes.
There is no such path, the closest I'm aware of is EFI/BOOT, which contains BOOTX64.cfg, which I already modified with nouveau.modeset=0 on each option to no avail. To my understanding this is the conf that should apply since this is the EFI boot folder, so I don't think that setting is the culprit. That said, it's not Xen.cfg, but I did 'ls -R | grep Xen.cfg' which resulted in nothing, then did 'ls -R | grep xen' which returned packages as well as xen.gz, then 'ls -R | grep Xen' which returned nothing, so I'm not sure there is such a config. -- 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/57022df6-359b-4318-940c-cc8e57aa67ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
