shermanm | I wanted to ask the purpose of having `nofb nomodeset "gfxpayload=text"` as the defaults for `DIB_BOOTLOADER_DEFAULT_CMDLINE` | 16:28 |
---|---|---|
shermanm | https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/bootloader/environment.d/10-bootloader-default-cmdline#L1 | 16:28 |
shermanm | We've noticed that having `nomodeset` can cause instances to become unbootable when AMD's ROCM drivers are installed | 16:28 |
shermanm | and I can't seem to find `nofb` documented for recent kernels | 16:35 |
clarkb | shermanm: have you checked the git log? | 16:42 |
shermanm | they sort of appear there 8 years ago, and 5 years ago only gfxpayload was touched | 16:42 |
clarkb | vga=normal is depreciated, use gfxpayload=text instead | 16:43 |
clarkb | "defaulting to the existing 'nofb nomodeset vga=normal', that will allow to modify these boot params." | 16:43 |
clarkb | so config was added to make it configurable and that config defaulted to the defaults at the time | 16:44 |
clarkb | from 11275c212b3f2b8c936f07e7938dd81b2908faac | 16:44 |
clarkb | and then those were updated to drop a deprecated option | 16:44 |
clarkb | its interesting that nomodeset causes problems since that is basically "use generic mode". Ubuntu sets nomodeset when booting safe mode | 16:45 |
clarkb | I would've expected it to not matter outside of graphical environments | 16:45 |
clarkb | looking at ubuntu, debian, centos, etc defaults for modern grub configuration for linux command line may be a good idea | 16:46 |
clarkb | then determine from there if we should make any edits | 16:46 |
shermanm | I know that ironic has removed nomodeset as a default due to other issues it was causing | 16:46 |
shermanm | https://github.com/openstack/ironic/commit/f2605e928136f88032ef9b4977a076d5c535987b | 16:46 |
shermanm | good pointer on the distro defaults | 16:47 |
clarkb | in general though the list chosen by dib is one that I would expect to use as basic as possible a "graphical" setup | 16:47 |
clarkb | no framebuffer, no gpu driver specific configuration (nomodeset) and text output | 16:48 |
clarkb | which seems like a good idea for a server focused tool | 16:48 |
shermanm | I did want to note that `nofb` isn't listed here https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt, but i'm still hunting down when it was last documented | 16:53 |
TheJulia | shermanm: My "gut" feeling is this perception on use of serial consoles for machines, but in reality if your booting it on physical hardware you *want* a framebuffer to reduce the overall interrupt count call to the GPU for anything which goes to the console | 16:56 |
TheJulia | same is also semi-true for VMs, it entirely depends on how much gets written to the console | 16:57 |
TheJulia | nofb... I *think* is a grub parameter actually | 16:57 |
TheJulia | or it was in like linux 2.2 | 16:57 |
shermanm | thats kind of what I was seeing, no real mentions in past 20 years | 16:57 |
TheJulia | yeah, nomodeset is also amongst the things which sorts of helps with some graphics cases, but not entirely | 16:58 |
TheJulia | At RH, we've had a ton of issues over the past two years with hardware that starts to burn interrupt for graphics or serial console mesages | 16:58 |
TheJulia | which is bad if your trying to run real time or near real time packet handling payloads | 16:58 |
TheJulia | s/payloads/workloads/ | 16:59 |
TheJulia | like, stupidly bad | 16:59 |
TheJulia | Anyhow, I wanted to highlight some diskimage-builder changes could use reviews | 16:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!