rancher
Drop "console=ttyS0" from default kernel cmdline parameters for x86_64
In this issue console=ttyS0 was removed from the kernel cmdline because of slow boot issues.
But in the install iso created by the elemental toolkit it still has that kernel parameter, and causes issues on some devices without serial consoles.
The default installers should probably match what the elemental parameters are.
Hi @artificial-aidan!
Yep, there are some issues with the serial console on certain systems. The build-iso command has the extra-cmdline flag which specifies extra kernel cmdline parameters for the ISO. This flag defaults to security=selinux enforcing=0 console=tty1 console=ttyS0 and is where you can drop console=ttyS0 if you run into this issue.
Let me know if it helps!
This works if building a custom ISO, but the default ones built for the elemental pipeline still contain it. Which is used by elemental operator
Maybe this is an elemental issue instead, and the docker file should be updated. But the decision was made to remove it for the installed OS, but it's still on the install ISO.
This works if building a custom ISO, but the default ones built for the elemental pipeline still contain it. Which is used by elemental operator
Maybe this is an elemental issue instead, and the docker file should be updated. But the decision was made to remove it for the installed OS, but it's still on the install ISO.
Yep, adding support for this in the seedimage building is the next step but we haven't had the time to implement it yet.
Is there a plan to make this configurable in the seed image? I spent some time looking at that but with how it is built, the build-iso command isn't called during seed image creation, just file system mapping. And you can't change the boot ISO without unpacking the efi file system.
Should this be an elemental operator issue then?
Is there a plan to make this configurable in the seed image? I spent some time looking at that but with how it is built, the build-iso command isn't called during seed image creation, just file system mapping. And you can't change the boot ISO without unpacking the efi file system.
Not right now, but if you add an issue in elemental-operator we will have a look! The solution would probably involve xorriso to add a grub-variables file to the ISO.
Should this be an elemental operator issue issue then?
Yes, please do that!