When was the last time that you ran
`dmesg|less` on your linux system?
You **NEVER** did?
You dont know what you are missing my POSIX dweller!
Look at the awsome input to your brains!!!
Of course you should first run
`man dmesg` since you should not trust a command which uses sudo from a stranger on the internet
https://www.man7.org/linux/man-pages/man1/dmesg.1.html
<< dmesg - print or control the kernel ring buffer
Yes on debian based machines, for some odd reason you are not allowed to run dmesg anymore as a regular user, so I run
`sudo dmesg|less`
Now you know what dmesg does, run it and learn to the bit, what happens on your linux machine when you cycle through the POST sequence
Now you will ask why I put up a screen cap of Naked.Gun.33.1.3.The.Final.Insult in this thread.
The logic is simple. Because I now have tsc=unstable in my permanent boot options in GRUB, I have achieved playing this 1080p stream on my machine without any hickups of mPlayer!
mPlayer has the gorgeous option of bailing out by itself if you have CPU/GPU/FPU or RAM issues, protecting an unstable machine as my Gigabyte miniPC. Since the switch mPlayer did not have to bail out!
Now the parameters are added permanently at boot
using this UI in my distro. I love editing config files directly. This convuloted manner of editing grub config is inefficient, also unusable in a proxmox or jail ENV where everything is done from *sh
The parameters were parsed successfully. Now the unsable tsc clock on this system is bypassed from boot
I've just added the parameters to the kernel according to the instructions on the web page; photographed them for our pleasure
Since the people who know about kernel parameter parsing via GRUB, did not see my post and because I forgot to use the AksFediverse hash, I hunted for an answer and am reading this one...
https://linuxconfig.org/how-to-set-kernel-boot-parameters-on-linux
This is the massive list of GRUB sub commands that I have to wade through
I have taken a Higher Grade Android to make this photograph and luckily this camera system knows how to capture the Light of the IPS LED panel in Total Darkness.
Compliments of Open Camera Android version
I'm going to include another photograph to give you an indication of how complex GRUB is in comparison to Legacy Lilo
When I press tab twice in Rapid Succession, the whole screen is filled with commands that I can execute within the GRUB sh {command environment}
I literally have to read all the man pages of those GRUB sub commands which give me an indication that they can do what I want, just so I can pass the parameters to the kernel
GRUB has made the distance between the command prompt and the kernel much bigger!
The camera of the Android is utterly failing to focus on the dimly lit IPS Led flat panel screen, but I have still captured a photograph of the command shell of GRUB
I have found the way to add parameters to the kernel at both time from GRUB
I'll make a photograph in a number of minutes
I dived into the disappearance of Lilo on all distro's. It turns out that Lilo was only usuable on BIOS, it did not evolve to UEFI systems.
I wanted to easily pass commands to the kernel pre-boot. Before I dive into the workings of grub, can anyone tell me where i Need to go to parse pre boot parameters through grub to the kernel?
Jumping in deep immediately
OS Linux
Kernel 6.x
found workaround for hardware errors on critical timer tsc
snippet from dmesg
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1796.607 MHz processor
snippet two
[ 0.068905] AMD-Vi: Using global IVHD EFR:0x206d73ef22254ade, EFR2:0x0
[ 0.069804] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.074120] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19e5a467a58, max_idle_ns: 440795257552 ns
[ 0.074127] Calibrating delay loop (skipped), value calculated using timer frequency.. 3593.21 BogoMIPS (lpj=1796607)
[ 0.074141] Zenbleed: please update your microcode for the most optimal fix
line [ 0.074141] clearly states that my microcode is not updated (not related to tsc)
[ 0.210124] TSC synchronization [CPU#0 -> CPU#8]:
[ 0.210124] Measured 2808 cycles TSC warp between CPUs, turning off TSC clock.
[ 0.210126] tsc: Marking TSC unstable due to check_tsc_sync_source failed
[ 0.210176] #1 #3 #5 #7 #9 #11 #13 #15
I added tsc=unstable to the boot options in grub, so from what I read here the parameter was passed to the kernel? Can someone please verify for me if this output states that?
The warning I get is that the BIOS of this machine is broken! and that the option tsc=unstable will work around that massive bug
Ich bin noch nach Korrelation am suchen, aber dem ersten EIndruck zufolge startet mein Laptop unter 50% Akkustand deutlich langsamer, als darüber.
Bei vollem Akku lande ich (inkl. Passworteingabe) nach ~14 Sekunden in Plasma.
Bei Akku 50% dauert das ca. 2 Minuten und das System ist super träge. #dmesg offenbart... nichts. Es dauert einfach nur alles lange.
Die Korrelation mit dem Akkustand ist bisher (nach zwei Vorkommnissen) die einzige Korrelation, die ich finden kann.