Conversation

Notices

1. Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 05:03:25 UTC Bernie

   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? 🤔

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 19:41:54 UTC Bernie

     in reply to

     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 🤬

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:02:38 UTC Bernie

     in reply to

     Looks like the MSI firmware is deleting the GRUB boot entries that I create with efibootmgr... 🤬

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:03:08 UTC Bernie

     in reply to

     I tried creating an entry from the built-in UEFI Shell, and it also got deleted.

     What's going on?!?

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:06:36 UTC Bernie

     in reply to

     • penguin42

     @penguin42 Well, first I gotta boot somehow...

   • penguin42 (penguin42@mastodon.org.uk)'s status on Saturday, 16-Apr-2022 21:06:39 UTC penguin42

     in reply to

     @codewiz latest firmware?

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:07:09 UTC Bernie

     in reply to

     Other MSI users are complaining about this same behavior:

     https://bbs.archlinux.org/viewtopic.php?pid=1874820#p1874820

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:14:51 UTC Bernie

     in reply to

     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

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:16:04 UTC Bernie

     in reply to

     lol, MSI... your UEFI firmware sucks even more than the others I've seen!

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 21:20:28 UTC Bernie

     in reply to

     • tokudan

     @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.

   • tokudan@chaos.social's status on Saturday, 16-Apr-2022 21:20:29 UTC tokudan

     in reply to

     @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

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 23:08:01 UTC Bernie

     in reply to

     • tokudan

     @tokudan I found a workaround:
     https://mstdn.io/@codewiz/108143814846249839

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 16-Apr-2022 23:17:31 UTC Bernie

     in reply to

     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.

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 17-Apr-2022 00:44:14 UTC Bernie

     in reply to

     • penguin42

     @penguin42 See other branch of this thread for the root cause (TL;DR: MSI built broken assumptions in their UEFI boot code)

   • penguin42 (penguin42@mastodon.org.uk)'s status on Sunday, 17-Apr-2022 00:44:17 UTC penguin42

     in reply to

     @codewiz Is it actually remembering anything between boots - even minor settings?

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 17-Apr-2022 00:58:56 UTC Bernie

     in reply to

     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...

   • christyotwisty 🇨🇦 (cosullivan@mstdn.io)'s status on Sunday, 17-Apr-2022 02:41:25 UTC christyotwisty 🇨🇦

     in reply to

     @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?

   • flutergork🇨🇦️ (flutergork@mstdn.io)'s status on Sunday, 17-Apr-2022 11:31:10 UTC flutergork🇨🇦️

     in reply to

     @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. 🙃

   • Tagomago (tagomago@mastodon.social)'s status on Sunday, 17-Apr-2022 11:41:02 UTC Tagomago

     in reply to

     @codewiz Spent my morning applying five non-cumulative BIOS updates thanks to you. Mini heart attacks whenever the bar stopped for a while...

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 17-Apr-2022 22:53:58 UTC Bernie

     in reply to

     • Tagomago

     @tagomago I hate those non-linear progress bars!

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 17-Apr-2022 23:00:29 UTC Bernie

     in reply to

     • flutergork🇨🇦️

     @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.EFI

     grub-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.

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 17-Apr-2022 23:18:14 UTC Bernie

     in reply to

     • flutergork🇨🇦️

     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

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 17-Apr-2022 23:20:16 UTC Bernie

     in reply to

     • flutergork🇨🇦️

     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

   • flutergork🇨🇦️ (flutergork@mstdn.io)'s status on Monday, 18-Apr-2022 09:47:13 UTC flutergork🇨🇦️

     in reply to

     @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.

   • Thom Zane :verified: (thomzane@daedal.io)'s status on Friday, 09-Sep-2022 13:51:09 UTC Thom Zane :verified:

     in reply to

     @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