Ok, I found this. I dont understand the change from Fedora 33 to 34 really.
sudo nano /etc/default/grub => to edit and save Ok.
=> sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg => to refrain
=> sudo grub2-mkconfig -o /etc/grub2-efi.cfg => from Fedora 34 ?
or => sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Ok, the question is now: How can i update grub.
https://www.qubes-os.org/doc/how-to-install-software-in-dom0/#changing-default-kernel
The sudo grub2-mkconfig -o /boot/grub2/grub.cfg ignore the i915 parameter.
This is the ´sudo nano /etc/default/grub`
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed ‘s, release .*$,g’ /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true <= i added this, tried it also without this line
GRUB_DISABLE_SUBMENU=false <= this was before true, tried it also true
GRUB_TERMINAL_OUTPUT=“gfxterm”
GRUB_CMDLINE_LINUX=“rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet i915.enable_psr=0”
GRUB_DISABLE_RECOVERY=“true”
GRUB_THEME="/boot/grub2/themes/qubes/theme.txt"
GRUB_CMDLINE_XEN_DEFAULT=“console=none dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan smt=off gnttab_max_frames=2048 gnttab_max_maptrack_frames=4096”
GRUB_DISABLE_OS_PROBER=“true”
GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX rd.qubes.hide_all_usb"
And this the output of cat /proc/cmdline
placeholder root=/dev/mapper/qubes_dom0-root ro rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet rd.qubes.hide_all_usb
Hi @steff I moved your post into the respective thread for that machine. In this category we aim to have one thread per model so all of the relevant discussion is in one place. (/CC @fsflover … thanks!)
This topic is walked “All Around the Qubes”, hahahah
First try if the parameter is even available for your gpu:
$ modinfo i915 | grep ‘^parm:’
If yes, then try to put it after the word “consoles”.
Give us
$ sudo journalctl -g i915
After that, I’m out of ideas.
Maybe @51lieal could help.
The same model of on my laptop, I use 5.10.104-3.fc32.qubes.x86_64 qubes4.1. From time to time I get black screen, fan spins and nothing happens. I presume it can be like that forever so after a 10 min I turn it off. Sometimes next boot is correct sometimes not. It is completely random issue. I don’t have an idea how to investigate this issue. Such issue can derail any conference meeting.
I have added these manually (not sure if these are being used):
./grub2/grub.cfg: module2 /vmlinuz-5.10.104-3.fc32.qubes.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-fc2da74f-db16-45d2-8c2d-ccb01118e2c8 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet **i915.enable_psr=0**
./grub2/grub.cfg: module2 /vmlinuz-5.10.104-3.fc32.qubes.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-fc2da74f-db16-45d2-8c2d-ccb01118e2c8 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet **i915.enable_psr=0**
./grub2/grub.cfg: module /vmlinuz-5.10.104-3.fc32.qubes.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-fc2da74f-db16-45d2-8c2d-ccb01118e2c8 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb **quiet i915.enable_psr=0**
and for efi (I’m not sure how it works to me it looks like grub is launched from EFI):
/efi/EFI/qubes/grub.cfg: module2 /vmlinuz-5.10.104-3.fc32.qubes.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-fc2da74f-db16-45d2-8c2d-ccb01118e2c8 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet **i915.enable_psr=0**
./efi/EFI/qubes/grub.cfg: module2 /vmlinuz-5.10.104-3.fc32.qubes.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-fc2da74f-db16-45d2-8c2d-ccb01118e2c8 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet **i915.enable_psr=0**
./efi/EFI/qubes/grub.cfg: module /vmlinuz-5.10.104-3.fc32.qubes.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-fc2da74f-db16-45d2-8c2d-ccb01118e2c8 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb **quiet i915.enable_psr=0**
Do you have any update whether suspend is working now? I am considering buying the InfinityBook but I am a little reluctant if there are still compatibility issues.
Furthermore: Are 4 cores sufficient?
I also wanted to contribute to this report.
---
layout:
'hcl'
type:
'notebook'
hvm:
'yes'
iommu:
'yes'
slat:
'yes'
tpm:
'unknown'
remap:
'yes'
brand: |
TUXEDO
model: |
TUXEDO InfinityBook Pro 14 Gen6
bios: |
N.1.01A05
cpu: |
11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz
cpu-short: |
FIXME
chipset: |
Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01)
chipset-short: |
FIXME
gpu: |
Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
gpu-short: |
FIXME
network: |
Intel Corporation Wi-Fi 6 AX201 (rev 20)
memory: |
65277
scsi: |
usb: |
3
versions:
- works:
'FIXME:yes|no|partial'
qubes: |
R4.1
xen: |
4.14.6
kernel: |
5.15.94-1
remark: |
FIXME
credit: |
FIXAUTHOR
link: |
FIXLINK
---
I had the same issue as @slimy-crawdad and the solution @enmus posted worked for me (see above).
But a new issue I noticed is that the latest kernel that works is 5.15.x
Because when qubes updated to kernel 5.16.x or 6.1.x (these are the only two higher versions I tested, but I guess it can be applied to every kernel higher than 5.15.x) it broke my system. Booting worked as usual but as soon as I logged in the screen turned black and stayed this way. So I had to boot with a previous kernel and delete the latest version. After that everything worked normal again.
I fixed this issue with versionlock my kernel version to 5.15.x, so it won’t update to a higher version but still everything else will be updated, see How to stop Qubes form updating kernel?