[irneo@manjaro boot]$ ls
amd-ucode.img efi grub initramfs-5.3-x86_64-fallback.img initramfs-5.3-x86_64.img linux53-x86_64.kver memtest86+ vmlinuz-5.3-x86_64
I don't recall the specific initramfs from the Arch attempt but other than the linux53-x86_64.kver and the memtest86+ it looks similar to what I had.
If I look under the efi directory there are:
[manjaro efi]# ls
EFI grub
Under that EFI directory I see
[manjaro efi]# ls
Boot Manjaro Microsoft
I had created a folder for Arch there and in my attempt I had copied the files from /boot into it as I thought maybe I had done something wrong with my mounting since I saw the vmlinuz file in the /boot directory rather than it's own Arch direcory under the efi directory.
This is something that I have found very confusing with the directory structure and how I should be mounting that partition. The partition 2 has a folder EFI so it seems like maybe I should only be mounting that partition to /boot rather than mounting it to /boot/efi. However in the Manjaro install the directory structure is /boot/efi/EFI/ which didn't work for me in Arch the first time I tried it like that.
]]>In my nvme drive it ended up partioned as follows:
nvme1n1 259:2 0 465.8G 0 disk
├─nvme1n1p1 259:3 0 529M 0 part
├─nvme1n1p2 259:4 0 100M 0 part /boot/efi
├─nvme1n1p3 259:5 0 16M 0 part
├─nvme1n1p4 259:6 0 149G 0 part
├─nvme1n1p5 259:7 0 29.8G 0 part [SWAP]
├─nvme1n1p6 259:8 0 93.1G 0 part /
└─nvme1n1p7 259:9 0 193.2G 0 part /home
So I tried mounting the 2nd partition both as /boot/efi and as /boot but it didn't seem to make much difference.
The command I ran to install grub was:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
after that I would run:
grub-mkconfig -o /boot/grug/grub.cfg
I did notice a difference if I ran mkinitcpio -P prior to installing grub and it seemed like it produced more after that but it still wouldn't boot.
So I tried installing Ubuntu 19.10 again and although it seemed to install it wouldn't boot although I could see the UBUNTU efi boot option.
I then tried (this time successfully) to install the latest version of Manjaro 18.1.1.
This worked and I am writing this from within that installation. So I guess...problem solved....
I would really still like to know what I was doing wrong or perhaps what Manjaro did differently to do it right.
]]>There is still a problem however that I'm trying to figure out. I am able to go through all of the steps in the installer getting a swap partition, root partition and home partition set up and get to the point of installing the bootloader. I am trying to install GRUB 2 using the existing EFI partition created by Windows. However when I run the grub-mkconfig it just seems to find the Windows image and doesn't make a bootable entry for Arch.
I think I may have put an extra "efi" in the path for the efi directory so I'm going to try a reinstall mounting the EFI partition just to /boot to see if it makes a difference.
]]>mobo: mpg x570 gaming edge wifi
cpu: ryzen 5 3600x
memory: ballistix elite 16gb (2x 8gb)
Cannot boot into debian, arch, ubuntu 18 or 19, all saying the same thing "ahci controller unavailable!" among other errors,
has anyone found any solutions to this so far?
[ 142.257714] xhci_hcd 0000:2a:00.1: xHCI host controller not responding, assume dead
The xHCI controller is the USB3 controller. Linux can't access USB3 and thus can't access the installation media (that I assume you boot from USB3). There was also a problem with AHCI (the hard disk controller), but maybe it first needs to load its image- from the installation media.
Check the firmware setup and disable anything that relates to "fast boot". Also check if there are options relative to USB3 / xHCI. If you have a USB2 port in your laptop try to boot with the installation media in the USB2 slot. If you have windows installed check that the USB port work at all (it seems yes, otherwise you won't even be at the point you are).
Also make a Google check with the exact version of your laptop. It seems to be a firmware problem. Is there a firmware update for it? (But generally vendors assume that the firmware is fine as long as it works under Windows, however buggy it might be....)
]]>nomodeset + changing the tty after boot is done works for me.
To get X running, follow the instructions here: https://wiki.archlinux.org/index.php/Navi_10. Additionally, you will need the latest linux-firmware package from [Testing].
]]>I tried booting with both nomodeset and modprobe.blacklist=amdgpu (separately). But had similar errors. The primary being the error of AHCI unavailable.
]]>