On Tuesday, 7 August 2018 14:49:33 UTC+1, Jim Snider  wrote:
> On Monday, May 7, 2018 at 12:03:17 AM UTC-5, Yassine wrote:
> > On Sunday, 6 May 2018 14:46:32 UTC+1, Yassine  wrote:
> > > Updating previous report as reinstalling from 4.0-rc3 to 4.0
> > > 
> > > Needed to edit xen EFI config to remove mapbs/noexitboot keys and disable 
> > > nouveau modesetting (nouveau.modeset=0)
> > 
> > After install I tested different configuration and was able to get discrete 
> > gpu hardware support:
> > - Removed nouveau.modeset=0
> > - Added kernel param: acpi_osi=!
> > - Changed iommu support from iommu=no-igfx to iommu=on
> 
> Yassine
> 
> I have a Dell Precision 5520 like yours except mine has the Xeon E3-1505M v6 
> processor, so I think your solution should work on my Dell. I have not been 
> able to get it to work.
> 
> Problem : Qubes 4.0 Installer hangs at anaconda screen.
> 
> I made the install USB using Rufus 3.1 in dd mode. I have tried and tried to 
> edit the BOOTX64.cfg on the USB install drive but it is write protected and I 
> have not been able to writew changes using several different approaches.
> I booted UEFI,  The results of the install:
> 
> message :  "Not asking for VNC because we don't have a network"
> message :  "44.288997 watchdog: BUG: soft lockup - CPU#5 stuck fot 23s! 
> [Xorg:1383]
> 
> I then made a ISO mode install USB using Rufus and edited the BOOTX64.cfg as 
> follows:
> 
> [global]
> default=qubes-verbose
> 
> [qubes-check]
> options=console=none
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 
> quiet rhgb rd.live.check
> ramdisk=initrd.img
> 
> [qubes]
> options=console=none
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 
> quiet rhgb
> ramdisk=initrd.img
> 
> [qubes-verbose]
> options=console=vga efi=attr=uc 
> # noexitboot=1
> # mapbs=1
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1
> ramdisk=initrd.img
> 
> [qubes-rescue]
> options=loglvl=all
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 rescue
> ramdisk=initrd.img
> 
> I booted the ISO USB Legacy, At Blue Qubes screen, Trouble Shooting, TAB, 
> added nouveau.modeset=0
> The results of the install:
> 
> message :  "Not asking for VNC because we don't have a network"
> message :  "X starting failed, aborting installation"
> message :  "The installation cannot continue the system will be rebooted   
> Press ENTER to continue"
> 
> Yassine,
> 
> I have searched high and low on the internet and your 5520 / Qubes sucess is 
> rare. There is very little discussion of this specific combination.
> 
> If you could Please give me some guidance and edit my BOOTX64 above to match 
> yours verbatim, I can try that.
> 
> Anyone else reading this post that may have suggestions, please add to the 
> discussion
> 
> Thank you so much

Hi Jim,

Try changing the default boot entry to the following:

[qubes-verbose]
options=console=vga efi=attr=uc
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 
nouveau.modeset=1
ramdisk=initrd.img

Once you've installed Qubes successfully, try tuning your xen.cfg file from 
dom0 with the following configuration:

[global]
default=4.14.57-1.pvops.qubes.x86_64

[4.14.57-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=on ucode=scan
kernel=vmlinuz-4.14.57-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root 
rd.luks.uuid=luks-some-uuid rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap 
i915.alpha_support=1 acpi_osi=! rhgb rd.qubes.hide_all_usb
ramdisk=initramfs-4.14.57-1.pvops.qubes.x86_64.img

Hope this help

Yassine

-- 
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/75ac78ff-42ef-422f-a3ed-8d9efafa1f26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to