Bug 1214645

(In reply to simon becherer from comment #0)
> tumbleweed 20230823
> in yast2 bootloader kernel parameter / command-line:
> if i append something to the command-line,
> and press OK,
> its disappeared after opening again yast2 bootloader kernel parameter

Strange. It works for me. Talking about "Kernel Parameters" / "Optional Kernel Commandline Parameters" input field
> 
> its not inside /boot/grub2/grub.cfg

well, it is ... in my case, so it  failed to save what you entered for whatever reason. So, could you attach logs collected by save_y2logs as described here: https://en.opensuse.org/openSUSE:Report_a_YaST_bug Thanks

I just checked with the latest yast2-bootloader from from YaST:Head, and it works for me: I see a new parameter that I added in /etc/default/grub at the

  GRUB_CMDLINE_LINUX_DEFAULT="..."

line.

Hi,
will check (again) later this week
with logs you suggested.

 - off topic -
sorry, running completely
out of time because of 25 year old
harddrive saturday ok, monday morning dead.
(in a production environment)
spend today 10 hours to organize and fix.
hopefully we are able to start production
tomorrow morning.
simoN

Created attachment 869224 [details]
yast2-log-boortloader-kernel-parameters-not-recogniced

So,
have done the following:
updated to tumbleweed 20230901
yast2 / boot loader / kernel parameters / optional kernel command line parameters
inside it is: video=1920x1080 showopts pcie_aspm=off
i changed to: video=1920x1080 showopts pcie_aspm=off mitigations=off
press [ok]
in main menue of yast2 now i pressed shift f8
and send as commend 4 the file.
going again inside the [kernel parameters]
it is still: video=1920x1080 showopts pcie_aspm=off
and the "mitigations=off" is missing.

checking the files:
/etc/default/grub the timestamp is updated, but the file content has not changed.
same for file:
/boot/grub2/grub.cfg

Created attachment 869271 [details]
Screenshot: YaST bootloader kernel parameters page

See screenshot in attachment #869271 [details]

Well, if you add the one kernel parameter that has its own dedicated widget on that page, the CPU mitigations, of course that dedicated widget takes precedence over any additional kernel parameters on that page. That is totally expected.

Please simply use that combo box for the CPU mitigations.

(In reply to simon becherer from comment #3)
> out of time because of 25 year old
> harddrive saturday ok, monday morning dead.
> (in a production environment)

Using the 'smartmontools' is strongly advised. They come as command line tools, but there is also a really nice GUI on top of them, 'gsmartcontrol'.

The smartmontools use hardware health data that all reasonably modern hard drives collect internally, such as the accumulated number of disk errors etc.; you might need to enable collecting those data in your PC's BIOS.

See also

  https://www.fosslinux.com/111631/using-smartmontools-in-linux-to-check-the-health-of-your-hdds-or-ssds.htm

gsmartcontrol screenshots:

https://gsmartcontrol.shaduri.dev/screenshots

Thanks,
for both infos.

well in english this is easy to see.

but in german its: "CPU-Herabsetzung".
and i (and i think some other non perfect english
speeking people too)
will fall in this trap, i have no idea what
"mitigations=off" the use for is.

because of my bug: 
https://bugzilla.opensuse.org/show_bug.cgi?id=1214628
i was told to use "mitigations=off"

and so i inserted it there. (copy paste)

would maybe a good idea to make a warning about
this "not allowed manual insertion of this
parameter" when pressing OK
or accept the manual insertion.

simoN

(In reply to Stefan Hundhammer from comment #9)
> gsmartcontrol screenshots:
> 
> https://gsmartcontrol.shaduri.dev/screenshots

well its an production machine with windows98 on it :-((
(and the drive was suddenly completely dead
bios: no drive attached)
simoN

i googled the "cpu herabsetzung"

first hit is something where is it explained,
but written its a "adventure"-translation
(a very uncommon maybe not clearly understandable
translation)

second hit is something like "give the cpu
less voltages".

and my thinking of this "cpu herabsetzung" was
it has something to do with clock speed.

so in my opinion it should be translated more like:

wthis widget should be with the text:
english:
"cpu-security-fix (midigation)"

german:
"cpu-sicherheits-fix (midigation)"

and i would of course the english word "midigation" also
have in german, because the its clear that it has
someting to do with this parameter.
- translating a parameter makes not much sense except
it could be also inside the kernel commandline be interted
translated.

simoN

Yes, some of those translations are really unfortunate; sometimes it would be better to leave things untranslated.