Post AIWEqIAaW6BomyWae0 by tokudan@chaos.social
(DIR) More posts by tokudan@chaos.social
(DIR) Post #AIUptb7ruWMKj5CsK0 by codewiz@mstdn.io
2022-04-16T05:03:23Z
0 likes, 0 repeats
Powering up my new mobo!Ok, blinky lights on the memory bus are back in fashion... but where are the switches to load a word into core memory? 🤔
(DIR) Post #AIW6GGZCCUAZl6LTOa by codewiz@mstdn.io
2022-04-16T19:41:03Z
0 likes, 0 repeats
Testing the new motherboard and swapping it into my old chassis: 2 hours.Fixing the damn UEFI boot manager so I can boot #ArchLinux again: 3 hours and counting 🤬
(DIR) Post #AIW6IPHOmDxZMQ2dcW by codewiz@mstdn.io
2022-04-16T19:41:52Z
0 likes, 0 repeats
Testing the new motherboard and swapping it into my old chassis: 2 hours.Fixing the damn UEFI vars to get #ArchLinux to boot again: 3 hours and counting 🤬
(DIR) Post #AIWDV7XejhRVn8eh84 by codewiz@mstdn.io
2022-04-16T21:02:35Z
0 likes, 0 repeats
Looks like the MSI firmware is deleting the GRUB boot entries that I create with efibootmgr... 🤬
(DIR) Post #AIWDXyzQzLpi8Y0sV6 by codewiz@mstdn.io
2022-04-16T21:03:07Z
0 likes, 0 repeats
I tried creating an entry from the built-in UEFI Shell, and it also got deleted.What's going on?!?
(DIR) Post #AIWDk4aXzzYwyY8aps by penguin42@mastodon.org.uk
2022-04-16T21:05:18Z
0 likes, 0 repeats
@codewiz latest firmware?
(DIR) Post #AIWDr9HwvGX3ZzoRIO by codewiz@mstdn.io
2022-04-16T21:06:35Z
0 likes, 0 repeats
@penguin42 Well, first I gotta boot somehow...
(DIR) Post #AIWDuDgJ2wuU4YfZdg by codewiz@mstdn.io
2022-04-16T21:07:08Z
0 likes, 0 repeats
Other MSI users are complaining about this same behavior:https://bbs.archlinux.org/viewtopic.php?pid=1874820#p1874820
(DIR) Post #AIWDxVQlVlgxzQy2jo by penguin42@mastodon.org.uk
2022-04-16T21:07:43Z
0 likes, 0 repeats
@codewiz Is it actually remembering anything between boots - even minor settings?
(DIR) Post #AIWEXwRaYPboC9j69I by codewiz@mstdn.io
2022-04-16T21:14:19Z
0 likes, 0 repeats
Ok, simply renaming grub to EFI/BOOT/BOOTX64.EFI made it appear as a boot menu option without even creating an EFI boot entry for it!I found a tip in the awesome Arch Wki:https://wiki.archlinux.org/title/GRUB#Default/fallback_boot_path#ArchLinux
(DIR) Post #AIWEhUxdaf07qzH3IG by codewiz@mstdn.io
2022-04-16T21:16:03Z
0 likes, 0 repeats
lol, MSI... your UEFI firmware sucks even more than the others I've seen!
(DIR) Post #AIWEqIAaW6BomyWae0 by tokudan@chaos.social
2022-04-16T21:17:31Z
0 likes, 0 repeats
@codewiz not sure if it's relevant, in my setup I have an option about uefi being protected or not (not just secure boot) and that accepts changes, but throws away all changes on reboot
(DIR) Post #AIWF7EQVgeok6Q38Eq by codewiz@mstdn.io
2022-04-16T21:20:06Z
0 likes, 0 repeats
@tokudan Thanks, that was my first guess, but I looked everywhere in the setup interface and couldn't find a way to disable this "smart" feature.
(DIR) Post #AIWOgjNdUdeTpIhuxk by codewiz@mstdn.io
2022-04-16T23:07:57Z
0 likes, 0 repeats
@tokudan I found a workaround:https://mstdn.io/@codewiz/108143814846249839
(DIR) Post #AIWPXOgf9zsSzniiPo by codewiz@mstdn.io
2022-04-16T23:17:28Z
0 likes, 0 repeats
On the upside, this new machine (i7-12700F 4.9GHz DDR5 5600) builds wezterm from sources in 2m05s.For comparison, my Thinkpad X1 (i7-10710U @ 4.7 GHz) takes 8m56s.
(DIR) Post #AIWXHJRvfIzZkefaym by codewiz@mstdn.io
2022-04-17T00:44:11Z
0 likes, 0 repeats
@penguin42 See other branch of this thread for the root cause (TL;DR: MSI built broken assumptions in their UEFI boot code)
(DIR) Post #AIWXZj3dC472O05Jei by penguin42@mastodon.org.uk
2022-04-17T00:47:30Z
0 likes, 0 repeats
@codewiz Broken UEFI? Shocking, just shocking, whod have thought!
(DIR) Post #AIWYafrWeuWWihRG9w by codewiz@mstdn.io
2022-04-17T00:58:54Z
0 likes, 0 repeats
Updating the BIOS...Wait, wasn't it supposed to be called "firmware" nowadays? More confusion due to fucking UEFI 💢Anyway, I like that you can just put the new image on a usb stick nowadays. No DOS floppy, no Windows utility...
(DIR) Post #AIWhjPHIaTvjTijU4O by cosullivan@mstdn.io
2022-04-17T02:41:16Z
0 likes, 0 repeats
@codewiz I am 97% of the way to ditching my Dell Latitude e6420 because I see no encouragement from Dell for updating my 2012 machine with a BIOS update: I am running Linux Mint.My battery is down to 17% post-upgrads and I see no online tutorials. Did you see any useful tutorial?
(DIR) Post #AIXSyorGSWuL0FPGDo by flutergork@mstdn.io
2022-04-17T11:30:45Z
0 likes, 0 repeats
@codewiz Maybe that's what was happening on my machine. It was acting strange. I moved from Arch-based to Fedora, via openSUSE. Now the only strange thing around here is me. 🙃
(DIR) Post #AIXTtkggdbuWZfbeoy by tagomago@mastodon.social
2022-04-17T11:41:00Z
0 likes, 0 repeats
@codewiz Spent my morning applying five non-cumulative BIOS updates thanks to you. Mini heart attacks whenever the bar stopped for a while...
(DIR) Post #AIYRx88tspunRBFKAi by codewiz@mstdn.io
2022-04-17T22:53:57Z
0 likes, 0 repeats
@tagomago I hate those non-linear progress bars!
(DIR) Post #AIYSWp5uBLRemjrgFE by codewiz@mstdn.io
2022-04-17T23:00:24Z
0 likes, 0 repeats
@flutergork 😂 It's likely that Fedora installs grub in the same path used by Windows so the bios doesn't try to "help".That's also how i fixed mine: moved grub to EFI\BOOT\BOOTX86.EFIgrub-install has a confusingly named option for this: --removable. I think it's called this way because removable drives can't take the EFI nvram vars with them, and thus the bootloader must use a path that firmware will discover automatically.
(DIR) Post #AIYU4dSI3snMUI1Qoa by codewiz@mstdn.io
2022-04-17T23:17:41Z
0 likes, 0 repeats
PC motherboard vendors feel compelled to add their kludgy fixes because the entire UEFI boot process is so brittle.The blame for this whole mess falls primarily on Intel for defining the original, half-assed EFI, and later on the UEFI Forum, who took it to its present state.https://en.wikipedia.org/wiki/Unified_EFI_Forum@flutergork
(DIR) Post #AIYUIYqvyEHsGdBnXc by codewiz@mstdn.io
2022-04-17T23:20:15Z
0 likes, 0 repeats
The entire UEFI boot process is so brittle that PC motherboard vendors feel compelled to add their kludgy fixes to help their customers.The blame for this big mess falls primarily on Intel for defining the original, half-assed EFI, and later on the UEFI Forum, who took it to its present state.https://en.wikipedia.org/wiki/Unified_EFI_Forum@flutergork
(DIR) Post #AIZOFQxGTOBKKwEgbo by flutergork@mstdn.io
2022-04-18T09:47:08Z
0 likes, 0 repeats
@codewiz There's no Windows installed on this machine, so I'm guessing it's other things. On the rare occasion that I might need Windows, I have another machine for that. I've read that others are having problems on occasion, including the Calamares installer.
(DIR) Post #AIbtqCLfECese4Zx5s by thomzane@daedal.io
2022-04-19T14:50:32Z
0 likes, 0 repeats
@codewiz Can you post some benchmarks on openbenchmarks with your new system?I wrote some quick reference doc for Phoronix Test Suite here: https://github.com/TechnologyClassroom/HardwareTest/issues/6#issuecomment-1066188987
(DIR) Post #AIv8BdGLjQBLohA5T6 by stephan@ruhr.social
2022-04-28T21:30:48Z
0 likes, 0 repeats
@codewiz Had the same problem, updating the BIOS erased all UEFI vars...
(DIR) Post #ANODwshSUI98S6KYue by codewiz@mstdn.io
2022-09-09T13:50:26Z
0 likes, 0 repeats
@thomzane It took a while, but here are some benchmarks on this board:https://openbenchmarking.org/result/2208148-CODE-GOREBOO85