I read the article ^^ but what is mentioned there to create a new file: /boot/grub2/user.cfg canot work for me:
root@mostro:/boot/grub2# touch user.cfg
touch: cannot touch âuser.cfgâ: Read-only file system
So back to square 0:
my whish is to enable grub menu on the serial console
this is achieved by configuring this grub parameters:
serial --unit=0 --speed=115200
terminal --timeout=5 serial console
rpm-ostree will create a new deployment with the specified kernel arguments added and reboot into the new configuration. The GRUB bootloader will continue to use its previous default.
Yes that works perfectly, but doesnt cover GRUB as the document also says.
GRUB needs this two lines of config ^^ which I dont know in which file should go
If your data is stored under a persistent /var, it will not be affected by system upgrades or re-provisioning unless you have explicitly configured it.
FWIW, there are people who run Fedora CoreOS entirely from RAM, so with each update (release), which is every two weeks, they effectively re-provision their systems.
Ok, I did change /boot filesystem to rw and created the file; but now it fails the grub2-mkconfig:
root@mostro:~# grub2-mkconfig -o /boot/grub2/grub.cfg
/usr/sbin/grub2-probe: error: failed to get canonical path of `composefs'.
root@mostro:~# cat /boot/grub2/user.cfg
serial --unit=0 --speed=115200
terminal --timeout=10 serial console
As far as I know, the GRUB config is now a static config in Fedora CoreOS, so you probably donât need the grub2-mkconfig step. Since you have already created/modified /boot/grub2/user.cfg just reboot to check if it will work.
tried different combination of user.cfg and also adding the same directly in grub.cfg but no avail. Out of options now.
Shall I open a bugzilla?
What is the procedure to open a bug for fedora coreOs
root@mostro:/boot/grub2# cat user.cfg
set timeout=10
insmod serial
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal serial
Not sure if this is Fedora CoreOS related, as setting set timeout=10 works. Unfortunately I donât have the necessary equipment to test the serial console settings.
As I mentioned in my previous post, unfortunately I donât have the necessary equipment to test the serial console settings on a bare metal machine. However, it seems to work on a virtual machine.
These are the steps I followed to test it:
hricky@silverblue >_ ssh core@fcos-22.local
Fedora CoreOS 41.20241215.1.0
Tracker: https://github.com/coreos/fedora-coreos-tracker
Discuss: https://discussion.fedoraproject.org/tag/coreos
Last login: Sun Dec 22 17:26:27 2024
Hristo, tty access works for me as well.
What doesnât work for me is getting the GRUB menu on the serial console.
Would you mind checking if you can get the GRUB menu via serial in your setupâŠ
can you tell me what sudo bootupctl status shows on your system? I wonder if this might be a case where the grub.cfg on your system is older and wonât pick up changes to user.cfg.
Another way to tell is, are you able to reproduce the issue on a freshly installed system?
In fact, if I completely screw up one of my VM deployments, I can always get into the GRUB menu (without making any configuration modifications) with the following commands: