Re: [gentoo-user] Grub: for the love of almighty Zardoz the magniicent....
Got the motherboard running, the motherboard was IGNORING the "UEFI only" BIOS setting, it was attempting to boot my system in BIOS mode, I found that I had to efibootmgr and tell the stupid BIOS what is what... why the BIOS doesn't scan the first two directories under /EFI for *.efi and list them, then allow the user to select the default is byond me... I mean it would be much much too easy to do it that way. =\ The magic smoke had left my previous motherboard, literally a component was burned off the board, so couldn't put it back in service even if it could have been booted. The temporary build actually looks pretty nice. It has an absolutely absurd amount of RGB on it... hmm, I wonder how many of you good ppl have a similarly burned component that you haven't detected for some reason... If your build is more than ~2 years old, I suggest a close visual inspection of all components... The RGB on the ram does cause a serious heat issue when I have 4 sticks stacked up on the threadripper, but on this temporary build I'm only using two sticks and it looks very nice. -- The vaccine is a LIE. #TheHonklerIsReal Powers are not rights.
Re: [gentoo-user] Grub: for the love of almighty Zardoz the magniicent....
On Wednesday, 1 July 2020 09:15:10 BST Neil Bothwick wrote: > On Wed, 1 Jul 2020 01:40:54 + (UTC), Alan Grimes wrote: > > I RMA'd my normal mobo as previously discussed. > > I went to grab my previous motherboard and it turns out that it had > > actually released a goodly chunk of it's Magic Smoke (tm) while I > > hadn't been looking. So I went down to the Quickie Mart and grabbed a > > motherboard that was still compatible with the rusty old 1800x... The > > error was Unable to load "/grub/i386-pc/normal.mod" Some short explanation of what Live image you're trying to boot with and at least your partitioning scheme might help. The GRUB error is indicative of GRUB not finding the partition in which the normal.mod module is stored. > > I had to buy some > > more USB sticks (my optical drive seems functional but will not boot > > the machine...) Why not? There should be no difference between a LiveCD and a LiveUSB. If anything booting off a USB on some MoBos could be more troublesome. Have you looked into this problem to find out if there was some MoBo setting you had to change (physical jumper/switch/cable, or firmware)? > > and used gparted to get into the partition, . > > =((( All my .mod files were in x86_64-efi > > > > >>> AND IT WAS WORKING ON THE OTHER MOTHERBOARD!!! <<< > > > > =~ > > Dear beloved Zardoz, what have I done to deserve your wrath??? > > Is the replacement motherboard UEFI and is t set that way in the firmware > menus? > > I think Zardoz would ask why you are subjecting yourself to GRUB when you > have much simpler options with UEFI hardware. Assuming this is a UEFI MoBo you can boot any kernel images on disk directly, as long as you can point the UEFI firmware to them. Have a look here: https://wiki.gentoo.org/wiki/EFI_stub_kernel and perhaps here: https://wiki.gentoo.org/wiki/Efibootmgr signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Grub: for the love of almighty Zardoz the magniicent....
On Wed, 1 Jul 2020 01:40:54 + (UTC), Alan Grimes wrote: > I RMA'd my normal mobo as previously discussed. > I went to grab my previous motherboard and it turns out that it had > actually released a goodly chunk of it's Magic Smoke (tm) while I > hadn't been looking. So I went down to the Quickie Mart and grabbed a > motherboard that was still compatible with the rusty old 1800x... The > error was Unable to load "/grub/i386-pc/normal.mod" I had to buy some > more USB sticks (my optical drive seems functional but will not boot > the machine...) and used gparted to get into the partition, . > =((( All my .mod files were in x86_64-efi > >>> AND IT WAS WORKING ON THE OTHER MOTHERBOARD!!! <<< > =~ > Dear beloved Zardoz, what have I done to deserve your wrath??? Is the replacement motherboard UEFI and is t set that way in the firmware menus? I think Zardoz would ask why you are subjecting yourself to GRUB when you have much simpler options with UEFI hardware. -- Neil Bothwick I backed up my hard drive and ran into a bus. pgpNG2Rel4K3M.pgp Description: OpenPGP digital signature
[gentoo-user] Grub: for the love of almighty Zardoz the magniicent....
https://omsi.edu/calendar/zardoz I RMA'd my normal mobo as previously discussed. I went to grab my previous motherboard and it turns out that it had actually released a goodly chunk of it's Magic Smoke (tm) while I hadn't been looking. So I went down to the Quickie Mart and grabbed a motherboard that was still compatible with the rusty old 1800x... The error was Unable to load "/grub/i386-pc/normal.mod" I had to buy some more USB sticks (my optical drive seems functional but will not boot the machine...) and used gparted to get into the partition, . =((( All my .mod files were in x86_64-efi >>> AND IT WAS WORKING ON THE OTHER MOTHERBOARD!!! <<< =~ Dear beloved Zardoz, what have I done to deserve your wrath??? I need to have a run of brass plaques fabricated with the inscription "If it can fail then the design is wrong" and mail them to each of the penguins that cause me this much heartburn. I have no idea where even to begin fixing this mess...
