Trying to sort my driver problems:
Added: The steps proposed bby Dave H to get round a previous problem (recreate /home/user did not work
drakx11 tells me the proprietary driver wasn't installed correctly
I can find no combination of driver module/monitor parameter values that doesn't end in EE error
startx as root give me a poor definition GUI - nowhere near the 1920 x
1080 the monitor is capable of.
So I thought :enough (or words to that effect) reinstall Mageia 8
So now I can't complete the partition step because apparently I must
have a BIOS boot partition. How did the previous installation complete? Confused of Dorset
On Mon, 27 Dec 2021 11:23:58 -0500, Grimble <grimble@nomail.afraid.org> wrote:
The partition table layout has been changed from dos mbr format to gpt format.OK, created an empty partition (/dev/sda7 on my disk, parted calls it
With dos mbr format, grub stores it's boot loader starting in sector 2
of track
0 (sector 1 contains the master boot record).
With gpt, there is no room in the first track, so a empty partition (not formatted,
called the bios boot partition) is required for grub to store it's loader.
Either switch back to using the dos mbr partition table layout or create
the empty
bios boot partition.
Regards, Dave Hodgins
On 27/12/2021 18:00, David W. Hodgins wrote:
On Mon, 27 Dec 2021 11:23:58 -0500, GrimbleSNIP
<grimble@nomail.afraid.org> wrote:
=20
=20
The partition table layout has been changed from dos mbr format to
gpt format.
=20
With dos mbr format, grub stores it's boot loader starting in
sector 2 of track 0 (sector 1 contains the master boot record).
=20
With gpt, there is no room in the first track, so a empty partition
(not formatted, called the bios boot partition) is required for
grub to store it's loader.
=20
Either switch back to using the dos mbr partition table layout or
create the empty bios boot partition.
OK, created an empty partition (/dev/sda7 on my disk, parted calls it=20 grub2 core.img)
Installation completed but reboot landed me in grub rescue mode. A
file /boot/grub2/x86_64-efi/normal.mod
doesn't exist: very true, the directory x86_64-efi hasn't been
created. I notice on another Mageia8 installation normal.mod is
located in the sub-directory grub2/i386-pc.
Thought I could place normal.mod where grub could find it, but no:=20 "invalid arch-dependent ELF magic"
So why has boot loader installation created a different architecture=20
from precvious installation. Can I use Mageia rescue function to=20 re-install boot loader?
While GRUB visually looks the same across both boot methods, the
versions of the boot loader installed are very different. The legacy
BIOS version is 16-bit and runs in the boot processor's real mode — on
one core only, without hyperthreading — while the UEFI-aware version of GRUB is a 64-bit UEFI executable running in the processor's long mode.
On 27/12/2021 18:00, David W. Hodgins wrote:Thanks Aragorn, David. Reinstalled from the correct partition of my USB
On Mon, 27 Dec 2021 11:23:58 -0500, GrimbleSNIP
<grimble@nomail.afraid.org> wrote:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 52:03:10 |
Calls: | 9,566 |
Files: | 13,660 |
Messages: | 6,142,498 |