You are not logged in.
Pages: 1
arch linux usb install using Arch Linux beginners' guid
gdisk printout /dev/sda
MBR: Protective
BSD APM not present
GPT present
/boot EF00 EF system fat32 fs
/home 8300 linux system
/swap 8200
/ linux system
no journalctl -xn entries regardless of repeated reboots.
nothing on screen during power on. not even a cursor.
UEFI Motherboard, gummiboot installed. No errors during install. Though the only one config file in the /boot partition, loader.conf. Which contains one entry
"default 8e223669197c48d08b1d3c367d4c-*"
I can't think of anything else to add.
Any help given is greatly appreciated.
Paul
Offline
https://wiki.archlinux.org/index.php/Gu … ot_entries
And please use code tags when pasting to the boards https://wiki.archlinux.org/index.php/Fo … s_and_Code
Offline
The common mistake is to use UUID, rather than labeling the partitions, which leads to relevant confusion. Labels are easier to remember.
Developers defaulting on UUID because they don't know about everybody's conventions.
do it good first, it will be faster than do it twice the saint
Offline
Maybe try rEFInd? It's pretty good at finding kernels automatically regardless of how your system is set up.
Offline
I used rEFInd but there is a "gotcha" that I found out isn't in the Beginner's Guide (nor am I certain my advice should be added to it as it may confuse some people): When I installed the system I had to mount my boot partition as:
/boot/efi
Without that change rEFInd refused to boot properly. In the end, with this method, you'll end up with a boot partition that looks like this:
/boot/efi/EFI/...
It looks funny but it does work and it was the only way I found to get my install up and running. There are other ways to do things but you may want to try this one.
Offline
Jasonwryan
Will use the code tags in future.
silverhammermba, MoonSwan
I've started using gummiboot and I think that I should just use one and stick with it.
So with that I have a few questions, When I setup the partitions, I use gdisk. With the boot partition do I just leave it to gummiboot to set up the efi folder or create it myself after I have created the file systems.
I'm using a none UEFI install, does that matter? And when I do try to use UEFI bios I get a blue screen with an error 14. I can't remember the full text of the error.
Offline
paulk, sticking with gummiboot is fine of course. I was suggesting rEFInd more as a debugging tool: since rEFInd is usually easy to install and often can boot your kernel with no configuration whatsoever, it could be a good indication of where the problem lies. If rEFInd works, you probably have gummiboot misconfigured. If rEFInd doesn't work, perhaps your problem is more fundamental and gummiboot isn't to blame.
Offline
I'm using a none UEFI install, does that matter?
It might matter:
Offline
Pages: 1