Post-installation Issue With Dell Pro 14

User Support
,
1

Hi Everyone,

I was able to successfully install Qubes on my Dell Pro 14, and I able to see GRUB menu during the boot process. After I select “Qubes, with Xen hypervisor” I receive the following error code “Qubes Error- USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or usbcore.authorized_default=0”. Has anyone else experienced the same issue?

Thank you,

2

It it’s just after the installation, before the final step, it’s normal.

It’s not really an error, it’s more a warning, telling you that you don’t have a sys-usb VM. So either you create a sys-usb, either you accept to have USB devices connected to dom0 with the associated risk.

Bertrand

1 Like
3

Thanks for the reply Bertrand. So how do I proceed to the next step? My screen gets frozen after the message. Is there something I am missing maybe a keyboard command? Isn’t the final process to create the sys-usb? I never get to that post installation configuration screen. I have tried to edit the GRUB, but it hasn’t worked either.

4

If your screen get frozen, you have another problem. This message does not lead to a frozen installation.

If you are using the normal kernel, try to use kernel-latest for your installation.

What laptop do you have, which CPU, which other pain components?

Bertrand

1 Like
5

Hi Bertrand, I have a Dell Pro 14 Plus with a Intel Core i7 Ultra 268V x 8, 32 GB of ram, and a 512 GB Drive. When I try to install using kernel-latest the text becomes unreadable and has errors. I am starting to think that this laptop has compatibility issues with Qubes.

6

My laptop has a Intel Core Ultra 275HX and has some issues.
Qubes has an issue with how my laptop is organizing the PCI busses: there are two PCI Root Complex which seems to be very rare for destops and laptops of the previous generations. And this is due to how the Intel Core Ultra Series 2 processors and the associated Intel WM880 PCH chip are built up.

I would love to see a lspci -nn of your laptop.

The good side of this is that now, my laptop is usable. So there is hope!

A very recent laptop seems not to be a good thing for Qubes. But with time, Qubes support improves.

Bertrand

1 Like
7

So it looks like I finally got it installed via kernel-latest, however now it passes the “Qubes Error- USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or usbcore.authorized_default=0” message and then the screen just goes black. So some progress haha.

8

Hi Zulama - and welcome to the forum! :slight_smile:

Have you tried to edit the GRUB menu and:

  • remove quiet from the kernel parameters

?

Another thing you can try, is to:

  • replace quiet with module_blacklist=amdgpu

and finally, you can go all in and:

  • remove quiet from the kernel parameters
  • replace console=none with console=vga vga=,keep loglvl=all guest_loglvl=all noreboot=1 earlyprintk=xen as options to Xen

This final option should make the machine boot in a very verbose/slow mode - and print all messages, so you can see them.

Does your machine have an Intel or an AMD CPU?

:slight_smile:

9

Hi @Zulama

Does your laptop use only the Intel Arc graphics ? I see “Intel Core i7 Ultra 268V” has it included.

I just had a problem with Intel Arc and the 4.3.0 installer:

  • The installer uses Xe driver for the graphics during the first part of installation, until the first reboot.
  • …but it does not copy the firmware to the new installation on the disk, so I was getting black screen.

I found a work-around for the 4.3.0 installer, I think. (TLDR - copy the xe firmware to the target just after the installation begins) :

  1. Boot the installation media, and select the Install kernel latest.

  2. Prepare the keyboard layout, disk destination, user name.

  3. After pressing the button to begin installation, watch the screen for the creation of the luks partition and the lvm partitions (it is only a minute or two).

  4. Press Ctrl-Alt-F2 to find a text terminal (maybe it is Ctrl-Alt-F3?). There is a prompt that looks like this:
    [anaconda root@localhost /]

  5. Change to the root directory cd /

  6. Verify that the “xe” firmware is present: ls usr/lib/firmware/xe - you should see several files inside the directory. (bmg_guc_70… and some more)

  7. Wait until the initial directory structure is created on the target. Type :
    ls /mnt/sysroot/
    You should see some directories inside. (Use the UP arrow, and press Enter to try again, until you see the directories created.

  8. copy the directory to the target disk:

    cp --parents -r /usr/lib/firmware/xe /mnt/sysroot/

  9. Go back to the graphical installation Ctrl-Alt-F6, and wait for it to finish.

  10. Reboot, and hope to see some GUI.

At least on my current computer, this was enough to integrate some initial Xe firmware, to avoid the black screen. I am still testing, but I am very hopeful…

Let us know if you succeed, or if you don’t!

I think that the problem has already been addressed for the future: issue #10523

I guess it will also be fixed in the next installer version.

10

I think this is exactly the issue I am having! Yes my GPU is a Intel Ark, I am going to follow your directions and see if it works! Thanks Phceac!

11

So a update, for some reason I am unable to enter to the terminal to make the necessary changes. I tried holding Crtl+Alt+F2 and Crtl+Alt+F3, but the installation process goes ahead. Am I suppose to hold these keys as soon as it starts to install?

12

It is possible that F1 - F12 keys are working as “multimedia control keys” . They change volume, switch screen, and other things.

Some possibilities:

  • Fn+Esc can switch to Function key mode?
  • Fn+F3 gives the F3 press, so you must press Ctrl-Alt-Fn-F3 ?
  • or the BIOS should allow to change “Function key behaviour” so that default is function key and Fn-F3 is the multimedia control.

Let us know. You can test immediately after your install media starts. Remember that the installer is on number 6…