- This topic has 20 replies, 6 voices, and was last updated Dec 4-7:08 am by Brian Masinick.
-
Posts
-
boombaby
Hello, Bitjam, Anticapitalista (et al)…
HOLD THE PHONE!!!
I again tried the User that I added (at install) but this time using ALT+password (ie the OTHER password: ie the PROPER password – ie NOT some other password).
So it booted to a User desktop. I haven’t looked over it yet.
Bitjam, yes, that is the screen that I get. That’s the one that comes up after some resolution shifts at DVD boot – and where I can only use “safemode” install. I didn’t change anything on the “live” system – just pressed “install”.
I will let you know the outcome, but I expect it will work properly, because this all was an error by me. I will let you know.
Regards and regrets,
boombabyFirst of all apologies. If I had remembered my password you would not have heard from me. Sorry.
Yes; desktop is all there. Very nice too.
When Mandriva first started the central control thing, and Mageia perfected it, I became a linux enthusiast. Indeed I gave up MS-Windows by using Mageia 5/6. In my move to a modern 64-bit laptop I put my trust in Mint. Now Antix has a control centre thingy too. Excellente! Needs extra development. In the next release can I suggest “slick” is a good word to keep in mind?
So I look forward to digging into it and making good use of Antix.
Now, WHY did Antix install BUT the EFI/Grub setup did not complete it? Is it my (EFI) multiboot setup? Why didn’t Antix “insert itself” somehow? (Remember, I tried it 3 different ways, yet the old 16.2 setup remained.)
- This reply was modified 5 years, 6 months ago by boombaby.
Brian Masinick
We don’t seem to be alone in having these kinds of problems. To me, these kinds of problems began when distributions started using the GUID Partition Table (GPT) along with UEFI and the GRUB EFI implementation.
This technology has been “around” since at least 2009 – read the Roderick Smith article available on IBM’s site @ IBM Developer Works – GUID, GPT, and UEFI.
Here’s an excerpt from that article that highlights some of the “problems”:
Boot loader support
Boot loader support for GPT is variable and depends on your computer’s firmware type. Under BIOS, only the Grand Unified Bootloader (GRUB) 2 officially supports GPT. Most Linux distributions today use GRUB 2 as the default boot loader, but some continue to use the older GRUB Legacy. GRUB Legacy doesn’t officially support GPT, but patched versions with GPT support are readily available. The still-older Linux Loader (LILO) doesn’t explicitly support GPT, but its disk-addressing methods are based on sector locations, so it often does work (in practice).
If you use GRUB 2 on a BIOS-based computer, be sure to create a BIOS Boot Partition, which holds GRUB’s second-stage code. (This partition is identified as having its bios_grub flag set under GNU Parted or as being of type EF02 under gdisk.) The BIOS Boot Partition can be as small as 32KiB in some configurations, although it must sometimes be a bit larger. Given modern partition alignment policies, a size of 1MiB is common.
If your computer uses EFI, any EFI-capable boot loader will work with GPT; but EFI boot loader selection for Linux is tricky. As of mid-2012, some boot loaders remain unreliable or have system-specific quirks. In my experience, the Linux kernel’s EFI stub loader (introduced with the 3.3.0 kernel) is the most reliable, followed by the EFI LILO (ELILO), a heavily patched version of GRUB Legacy used by Fedora, and finally GRUB 2. In addition to the boot loader, you might need a separate boot manager to enable operating system selection, particularly if you dual-boot and use the kernel’s EFI stub loader or ELILO to boot Linux. Two common choices for this task are rEFIt and rEFInd, the latter being a more up-to-date fork of the former. (Note that I maintain rEFInd.) See Related topics for links to all of these programs.
EFI requires the presence of an EFI System Partition (ESP) to boot. (Macs are a partial exception to this rule, although they ship with ESPs defined.) The ESP should contain a FAT32 file system. The EFI standard doesn’t specify a size, but something between 100MiB and 500MiB usually works well. If you use the Linux kernel’s EFI stub loader or ELILO, you may need to store your kernel on the ESP, so creating an ESP on the large end of the scale is advisable.
--
Brian MasinickBrian Masinick
When I initialize my system and enable UEFI in the boot sequence, (using my 64-bit Dell Inspiron 5558, the only boot option that works is Failsafe; the others hang before run-level 5 completes to display the GUI.
If I boot to the hard drive or the USB, I have fewer issues, but I still am running into scenarios where the GUI is locking up unless I first boot with S (Single) added, then use telinit 5 (Five) and provide the root password – then the GUI displays as expected.
I’ve recently experienced issues when attempting to perform any installations with UEFI (secure or insecure) enabled, so I may have messed something up on the Dell Inspiron 5558 that is affecting not only antiX, so it’s quite likely that the issues are NOT directly related to any antiX defects. I recently reinstalled both antiX 16.2 and openSUSE 42.3 and encountered the same issue, and I had previously installed both of them at an earlier date without any issues whatsoever. Moreover, when I examine the contents of the resultant grub.cfg that gets generated in /boot/grub with GRUB EFI, it isn’t capturing all of the partitions containing distributions, so something else is wrong, again not pointing directly to antiX, but more likely in my firmware configuration.
When I boot without EFI enabled, I have somewhat better results, which again points to my configuration. When I figure out what I’ve done wrong and correct it, if there’s anything worthwhile to share, I’ll do so, and if I learn something valuable, I may document my findings (but only if my research leads to solid, reusable and repeatable results that are consistent with existing documentation).
--
Brian Masinick
jdmeaux1952
Thanks, Brian. The article cleared a lot of confusion that I had concerning GRUB.
The Kernel has my back covered.
AMD desktop FX-8320 ASUS M5A97 LE R2.0 nVidia GeForce 730 GT 8 Gb memory
MSI laptop S6000 i5-460M 4 Gb ramA great mind is something to get terribly wasted.
LRU# 563815Brian Masinick
By the way, I cleaned up the entries in the boot loader and then I was able to use a couple different instances of UEFI enabled boot loader entries.
Following the procedures mentioned in the IBM Developer Works series ( @ IBM Developer Works – GUID, GPT, and UEFI ) did help me resolve my issues.--
Brian Masinick
- You must be logged in to reply to this topic.
