Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chromebook kernels and arm64 support #28

Open
sarnold opened this issue Nov 18, 2019 · 1 comment
Open

Chromebook kernels and arm64 support #28

sarnold opened this issue Nov 18, 2019 · 1 comment
Labels

Comments

@sarnold
Copy link

sarnold commented Nov 18, 2019

Hi again: This involves the chromebook signed FIT kernel images (and a few chromebook bootloader unknowns and possible tie-ins with dm-verity) as well as non-chromebook arm64 using UEFI blobs (as arm64 devices can have multiple bootloader options).

BUT, for now I'm mainly looking for an obvious way to short-circuit the luks/EFI settings/checks in buildkernel (which I couldn't really find). I did see the two DISABLE options but there isn't any explicit ARCH support yet. so I was wondering what you might suggest as an approach for now?

At this point I'd just like to test your kernel/initramfs approach as a signed FIT image on arm64 in a semi-automated fashion (note there are also plenty of x86_64 chromebooks this could work on, but I only have arm/arm64 chromebook hardware). I have a (forked) set of chromebook builder scripts but they're stand-alone and not distro-specific and have nothing to do with genkernel/anything, but at least in this context they can be used to make a bootable sdcard/usb-stick for starting the gnome install...

If i didn't mention it yet, the gnome install parts worked great on arm64 chromeobook, so the thinkpad now has a little brother named kevin ;)

@sakaki- sakaki- added the EOL label Oct 31, 2020
@sakaki-
Copy link
Owner

sakaki- commented Oct 31, 2020

31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and it may be of use to others); however, I plan no further updates, nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.

For further details, please see my post here.

With sincere apologies, sakaki ><

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants