You are not logged in.
Thanks for the replies, mrunion and WonderWoofy.
@WonderWoofy: I did as you suggested and compiled 3.12.9-1 using ABS, then installed it. I get precisely the same weird results as I do with the 3.12.9-1 kernel release from the Arch package repos.
@mrunion: Thanks again for posting about the USB thumb drive trick. It keeps me from having to revert to an older kernel.
There was a time when I would have tried to hound this down until I got it fixed. I'll just accept this for now, though, and expect for a fix to magically appear in the future. There's still enough non-compliance in the whole UEFI scheme that I'm not too surprised when this kind of thing happens. The USB thumb drive workaround isn't a hassle for me at all. In fact, I'm sort of intrigued by the weirdness of it.
Last edited by dhave (2014-02-01 18:20:42)
Offline
@dhave,
That is interesting that it didn't work for you. I guess it was worth a try though. I haven't been bit by this bug since something like 3.7 or 3.8, but I established that (for me) it had something to do with the efistub code/functionality. So as a backup solution, I keep grub-efi installed on my machine. Since it loads the kernel in the traditional bootloader way, it doesn't at all rely on the internal efistub functionality.
Honestly, I would rather not have grub on my machine, but it also provides the ability to boot an iso via loopback, so I have it set up with the archiso as well. Hopefully the syslinux project's memdisk functionality will eventually be ported over to UEFI, at which point I will be able to load the archiso like a giganto initramfs. That'll be nice if it ever happens.
Offline
Honestly, I would rather not have grub on my machine, but it also provides the ability to boot an iso via loopback, so I have it set up with the archiso as well. Hopefully the syslinux project's memdisk functionality will eventually be ported over to UEFI, at which point I will be able to load the archiso like a giganto initramfs. That'll be nice if it ever happens.
@WonderWoofy: Yeah, I keep grub around for similar reasons. It amazes me how long it's taking UEFI to take hold as the norm; maybe it has to do with the large number of non-UEFI-capable machines that Linux is still used on, and the fact that many people go with Linux for the good reason that a lot of distros run fine on older machines.
Offline
FWIW, I'm having success with linux-ck-3.12.9 booting via rEFInd (UEFI, of course). I had to install the latest nvidia-ck (331.38-3) to get to a graphical display, but otherwise, all went fine. After I copied the latest linux-ck kernel and initramfs to my EFI partition, rEFInd found it and presented it to me in the boot menu. All is humming along fine, so far.
Last edited by dhave (2014-02-09 00:08:19)
Offline