I had this problem some time ago, which has a workaround, I think, and which is fixed in the latest code but not in the current installation ISO.
I do not understand why there are so few mentions of it here.
My GPU was Arc Pro B50, Marek saw it on Lunar Lake series.
I am curious to know:
Did anyone else have the same problem? and what GPU?
Do most other Arc gpus using Xe have enough on-board firmware to work?
Should I be looking at the timeline for 4.3.next, to see when the official installer will carry the fix - and how could I do that??
Multiple questions - all remarks welcome!
Details, workaround, etc.
I am about to reinstall, so it came to mind. Not a big issue for me, and maybe it is very rare⦠but maybe many folk just give up?
Yes, almost certainly (not 100% sure for the most recent install, and I did not keep careful records.)
There is a weird unsolved screen corruption problem which I make occasional attempts to resolve, and ālatestā has been my choice, hoping/assuming itās a kernel driver problem: Qubes issue 10661
It should be excellent hardware for Qubes, but I would not currently recommend Intel Arc Pro B50, especially after Intel pulled a big bait&switch, and downgraded the number of VFs to 2, for unknown reason.
There is a pretty useful guide somewhere⦠I will have a look to see if I can find it.
IIRC, it was quite nice, once I got it to load xe drivers on the PF, but to load stub drivers on the 2 x VF, so they could be passed through to a pair of qubes.
I did not do a lot of testing though⦠wish I had the time
Iāll soon be testing with a weekly build to check if that could help.
I have the āblocked cursorā at the launch of the installer. Setting inst.vnc at the grub and setting the IP lead to an error of the VNC service
If it is 4.3.1, and you have another GPU for installation, then:
the firmware copy problem is fixed, but
It is necessary to blacklist xe driver for the first reboot after main installation (add rd.driver.blacklist=xe xe.blacklist=1 on your kernel command line.
Then do full update, after the graphical installer is finished.
I also had a similar problem some days ago, though it was possile to run without gpu. like nomodeset=0.
Later just updating my BIOS by flash updating solved the issue.
It was a dell latitude 5500.
Iāve managed to have the VNC installer working with these kernel parameters: inst.text inst.xdriver=vesda nomodeset. But itās not failing to boot to finalize the configurationā¦