Other than console.. how to pass grub parameter? pcie_aspm=off

General questions
,
1

I also have a mini pc… and trying to resolve the boot error…

This forum has a brief description… mine is the same…

dmesg | grep pcieport | wc -l
2432

[  408.373224] pcieport 0000:00:1c.2: AER: Multiple Corrected error message received from 0000:00:1c.2
[  408.373269] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[  408.373275] pcieport 0000:00:1c.2:   device [8086:4dba] error status/mask=00000001/00002000
[  408.373283] pcieport 0000:00:1c.2:    [ 0] RxErr

Active state power management seems to be the complaint…

I see there is a $boot_opts but that seems to be sourced from the top of the script…

Is there a way work with grub without direct console access?

Thank you in advance.

2

The Grub settings can be found in /boot/grub/grub.cfg.d/

There’s a series of scripts that inherit different values. The /boot/grub/grub.cfg.d/vyos-versions folder is the portion that presents the specific options for a boot image.

3

If your mini PC has multiple M.2 slots, try moving the M.2 drive to a different slot and see if the error persists.

4

Thank you for the suggestion… when I get back there again I will check…

5

I have a feature request over ⚓ T5432 Add grub-settings to system section in VyOS config-mode to add this to the vyos-config so the bootstring can be altered when vyos-config commit the config.

Until the above is reality you have to manually alter the grub.cfg from the bash mode of CLI (and redo that each and every time you add a new release to your box).

1 Like
6

While this did provide a solution, it appears to only work once…

the /boot/grub/grub.cfg.d/vyos-versions/

the 1.4 rolling and 1.5 rolling are what I have in there…

the 1.5 changes exist until I boot the 1.5 after 1.5 boots the cfg file is reset to its defaults…

Was I not supposed to manually edit the file?

7

Thank you for the " what am I missing " confirmation…

Keeping a copy of the 1.5-rolling and 1.4-rolling in /config/scripts/ is persistent…

so possibly an @reboot crontab entry cp’ing the cfg back… etc

Seems to be a valid option today until that feature request …

Thank you again

8

Note that /boot is common between installs while what you got in /config is copied from current version when you update so after next reboot (when you boot to newer version) it got its own /config.

Which means whatever you do in (for example) /config of 1.5.1 when you boot back to 1.5.0 the old /config is what you will see then.

In my case I manually alter /boot/grub/grub.cfg but I know that some work have been done lately to add boot options such as CPU vuln mitigations on/off which will probably rewrite the /boot/grub/grub.cfg every time the config is commited (I havent tested the latest nightlies).

1 Like
9

That was my original problem…

vyos@vyos:~$ cat -n /boot/grub/grub.cfg
     1  load_env
     2  insmod regexp
     3
     4  for cfgfile in ${prefix}/grub.cfg.d/*-autoload.cfg
     5  do
     6      source ${cfgfile}
     7  done

What to do here…

vyos@vyos:/boot/grub/grub.cfg.d$ grep -ri vmlinuz *
vyos-versions/1.5-rolling-202404040019.cfg:    linux "/boot/1.5-rolling-202404040019/vmlinuz" ${boot_opts}

vyos@vyos:/boot/grub/grub.cfg.d$ grep -ri boot_opts *
vyos-versions/1.5-rolling-202404040019.cfg:    set boot_opts="boot=live rootdelay=5 noautologin net.ifnames=0 biosdevname=0 vyos-union=/boot/1.5-rolling-202404040019 pcie_aspm=off mitigations=off
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.