You are not logged in.
Pages: 1
I have been using Linux for a while, but I am not very familiar with the booting process of Linux.
First, I have managed to get Arch booting using grub2-efi, however I would like to use the Linux Kernel EFISTUB.
I have placed the initramfs-linux.img and vmlinuz-linux.efi in the /EFI/Arch/ (which happens to be mounted on /boot) and a linux.conf in the same place containing
initrd=\EFI\Arch\initramfs-linux.img root=/dev/sda5 ro quiet
When I try to boot Arch using rEFInd (not rEFInd to Grub2 to Arch) I see that rEFInd attempts to use the settings found in the linux.conf then I get the following:
[ 0.592308] i8042: No controller found
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents....
[ 0.673673] uhci_hcd 0000:00:1a.0: Found HC with no IRQ. Check PIOS/PCI 0000:00:1a.0 setup!
[ 0.673739] uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -19
[ 0.673793] uhci_hcd 0000:00:1d.0: Found HC with no IRQ. Check PIOS/PCI 0000:00:1a.0 setup!
[ 0.673849] uhci_hcd 0000:00:1d.0: init 0000:00:1a.0 fail, -19
ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
You are being dropped to a recovery shell
Type /exit/ to try and continue booting
sh: can't access tty; job control turned off
I am not sure what most of it means, however my research tells me that the uhci_hcd is some device that the kernel cannot use correctly and the two that start with ERROR: are related to the EFI booting. Since I specified the device in the linux.conf should it be looking there and not in ''?
Can someone guide me along the correct path?
Comment reguarding the "uhci_hcd" and "No controller found" messages are welcome as well.
Last edited by raisdead (2012-09-15 19:32:29)
Offline
Hello raisdead.
I'm using an iMac (mid 2010, with i3 processor and AMD 4670 graphics).
I also have been trying to get EFISTUB boot to work and I've got it running now. I prefer it to grub.
Your log reports are OK (like mine) until the ERROR comes up.
I think you may not have got the correct UUID for your disk in the refind_linux.conf file.
If you can boot with another linux, maybe a live install disk, and run
sudo blkid /dev/sda7 (or whatever the number is for your arch disk partition)
you will get the UUID to put in your refind_linux.conf file.
In the refind_linux.conf file, the menu line I use to boot with is
"Boot default" "root=UUID=e5ead341-2bea-4933-969c-09ba528e9729 ro nosplash nomodeset init=/bin/systemd"
You might use the same but with your own UUID value, and maybe no init= value, if you are not using systemd yet (despite initial problems I recommend it).
The nomodeset is to avoid a black screen problem with the radeon video module.
My boot files are under EFI/arch353/ on the first partition on my mac. The files there are
refind_linux.conf
vmlinuz-linux
initramfs-linux.img
initramfs-linux-fallback.img
To keep this up to date when the kernel changes I mount the EFI partition (do this before the new kernel is installed, otherwise you might lose the ability to mount)
mount /dev/sda1 /mnt/uefi
make a new folder arch354 (say)
and copy over the new vmlinuz, initramfs files, together with a copy of the original refind_linux.conf
When one version isn't needed just delete its folder.
refind seems to find anything that might be bootable.
Good luck.
Offline
Thanks for the best practice and suggestions. For everyone else who lands here this will help.
Also for those who have done other reading, using a linux.conf is not required. I am not sure what purpose it would serve, perhaps someone will discover and post here.
Offline
Pages: 1