Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
On Tuesday, 18 December 2018 08:18:15 UTC, smvi...@invisson.com wrote: > El martes, 18 de diciembre de 2018, 6:05:18 (UTC+1), Yassine escribió: > > > > Regarding issues with when unplugging thunderbolt after boot, this is due > > to PCI hotplugging being disabled (for obvious security reasons) - more > > details here https://github.com/QubesOS/qubes-issues/issues/1673 > > > > @Jim: following awokd's procedure you should be able to get UEFI working, > > also the configuration that I described for installation and > > post-installation were tested with UEFI only > > > > Now if you reboot and the PCI devices served by the thunderbolt/usb-c are > > not present anymore, you'll have to manually remove them from the list of > > pci devices that are passed through to your NetVM or UsbVM. > > Same for when you boot with the thunderbolt attached, you'll have to > > reattach the pci devices to the VM for passthrough. > > Thank you Yassine! now I fully understand why this happens. > > I don't really care if I have to reboot to make it work, but the problem is > even after reboot, it is not detected, so I have to turn off sys-firewall + > sys-net, unplug the adapter and plug it again and finally start the VMs again > for it to work, what is a bit of a PITA. I'd be happy if it was recognized > directly when booting, even if a later disconnects make it stop working... > Have any of you been able to achieve something like this at least? > > Thank you!! Ok then, you might want to test different thunderbolt BIOS configurations. TB Security and TB Device enumeration mode for example. I also know from experience that some docking stations firmware have bugs that might require a reboot and the boot process of the docking station can itself take a bit of time (~20s). -- 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/823d21d8-985c-4d30-a6da-6810b54039ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
On Monday, 17 December 2018 20:05:53 UTC, smvi...@invisson.com wrote: > > I have a Precision 5520 and the USB-C Ethernet adapter that came with > > it. I'm running Qubes R4.0. > > > > I've been able to use the adapter once per boot before I unplug it. If I > > unplug it and plug it back in, then it doesn't show up as an Ethernet > > device in the NetVM, and I have to reboot to use it again. > > > > If I boot the laptop with the adapter plugged in, dom0 sees four PCI > > bridge devices and one USB 3.1 controller associated with the adapter: > > > > [user@dom0 ~]$ lspci > > ... > > 05:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge > > [Alpine Ridge 2C 2015] > > 06:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge > > [Alpine Ridge 2C 2015] > > 06:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge > > [Alpine Ridge 2C 2015] > > 06:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge > > [Alpine Ridge 2C 2015] > > 3d:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller > > [Alpine Ridge] > > > > I can create a NetVM and assign the last PCI device listed here to it. > > NetworkManager recognizes the USB device as an Ethernet device in the > > NetVM. > > > > However, if I plug the adapter in after I boot, then I have to rescan > > the PCI bus to see those devices: > > > > [root@dom0 ~]# echo 1 > /sys/bus/pci/rescan > > > > Then, lspci will show the USB 3.1 controller. This works the first time > > I plug the adapter in after boot. But the NetVM still won't see an > > Ethernet adapter if I've already unplugged it. > > > > Adding and removing a PCI device creates other issues. If I unplug the > > adapter, the NetVM that I attached the device to will hang on shutdown. > > And the same VM will fail to boot if the adapter isn't plugged in: > > > > [user@dom0 ~]$ qvm-start sys-dongle > > Logical Volume "vm-sys-dongle-root-snap" already exists in volume > > group "qubes_dom0" > > > > I haven't investigated further since I use WiFi almost exclusively on > > that laptop. But maybe you'll have better luck with plugging and > > unplugging the adapter on the 5530. > > > > Brian > > > > -- > > Brian C. Duggan > > he/him/his > > This is great Brian! thanks for your help! > > I have already figure it out how to make it work thanks to your description, > and something similar is happening now with the plug/unplugging... I'll try > to dig deeper but at least now I can use it! > > Best regards. Regarding issues with when unplugging thunderbolt after boot, this is due to PCI hotplugging being disabled (for obvious security reasons) - more details here https://github.com/QubesOS/qubes-issues/issues/1673 @Jim: following awokd's procedure you should be able to get UEFI working, also the configuration that I described for installation and post-installation were tested with UEFI only Now if you reboot and the PCI devices served by the thunderbolt/usb-c are not present anymore, you'll have to manually remove them from the list of pci devices that are passed through to your NetVM or UsbVM. Same for when you boot with the thunderbolt attached, you'll have to reattach the pci devices to the VM for passthrough. -- 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/7ada9d85-95f8-4780-a090-8221270c7eba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
There was a mistake in the install kernel parameter I shared, instead of "nouveau.modeset=1" it should be "nouveau.modeset=0" On Wed, 8 Aug 2018 at 08:20, Yassine wrote: > 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 a topic in the > Google Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/WMc88pfT-hM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > qubes-users+unsubscr.
[qubes-users] Re: Updated HCL report - Dell Precision 5520
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 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/75ac78ff-42ef-422f-a3ed-8d9efafa1f26%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Updated HCL report - Dell Precision 5520
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 -- 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/29be1281-b4eb-42bc-a0c5-9f7860048a36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Drop-down menus don't show properly in IntelliJ IDEA (R4.0 / i3)
On Sunday, 6 May 2018 10:43:28 UTC+1, Dimitri wrote: > Hi, > I want to use IntelliJ IDEA under Qubes R4.0 (with i3 wm). On a right-click > the IDE shows a drop down menu. However, this disappears immediately. I did't > have this issue in R3.2. Also all the drop down menus in IDEA have window > title. In other apps the drop-down menus just have a thin colored border. > Maybe this because IDEA uses some Java UI (?) > Any ideas how to fix that? > > Thanks! Hi Dmitri, I've been using IntelliJ on 3.2 and 4.0 but never had the kind of issue you describe, however I had a similar issue with another java application. In my case I worked around the issue by downgrading the software version and never had time to investigate. I would check the jre used by IntelliJ and eventually try to upgrade intellij/jre -- 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/db8df0fb-a844-4323-b784-1bc33917539c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Updated HCL report - Dell Precision 5520
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) -- 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/e6166477-b811-4de0-aecc-91e935ee429c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Precision_5520-20180506-142129.yml Description: Binary data
Re: [qubes-users] Installing in UEFI (Ryzen 1800X, ASRock Fatal1ty X370 Professional Gaming)
On Thursday, 1 February 2018 13:18:28 UTC, Willem D wrote: > On Thursday, 1 February 2018 13:40:24 UTC+2, awokd wrote: > > On Thu, February 1, 2018 10:21 am, Willem D wrote: > > > > To workaround the problem, try using Refind. To actually debug it, I think > > Qubes is using a modified version of Fedora 25's installer. Does that one > > work on your system? Not aware of any log files that get generated that > > early (especially if it can't find a file system interface). > > I just tried Fedora 25 Live x86_64 (workstation), to my surprise it worked. I > had to add "nomodeset" to boot parameter. It turns out the GeForce GT 1030 > does not have modesetting support yet. I will remove that card in future > Qubes tests. > > Going to read up on Refind and leaving this here for reference: > https://www.qubes-os.org/doc/uefi-troubleshooting/ Hi Willem, If you successfully installed in legacy mode by changing some kernel parameters you might want to check the following procedure: https://github.com/QubesOS/qubes-doc/pull/512 Basically, you mound the EFI partition on your USB device and edit the Xen configuration. It worked for 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/750a52d4-a241-4150-bdd4-48853dd91dcb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL report - Dell Precision 5520
At first couldn't install 4.0-rc3 because of some hardware issues (dual GPU and multicore features). Upgraded the BIOS and modified xen configuration to blacklist nouveau and bochs_drm in order have a successful install -- 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/4d452c25-598c-4130-84e0-edece6028077%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Precision_5520-20180131-230512.yml Description: Binary data
