-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
(WIP) Kgpe d16 current working #472
Conversation
/heads/config/coreboot-kgpe-d16_server CONFIG_PAYLOAD_FILE="../../build/kgpe-d16_server/bzImage" /heads/config/coreboot-kgpe-d16_workstation CONFIG_PAYLOAD_FILE="../../build/kgpe-d16_workstation/bzImage" |
Thanks @zifxify. There is now AST support in linux. I'm doing some tests and mods to whiptail (gui-init) so that the server/laptops with/without TPM/Nitrokeys work as intended (#493) I'm not sure there is really a need to seperate such boards if options are clearly defined in board config. If they are, i'll include your fixes! |
fb36b10
to
fb0a376
Compare
Separated the boards properly (untested) |
#712 followup.
|
@tlaurion need to enable onboard USB (doesn't work for previous versions). thanks for commit. |
Why not PS2? Having USB on by default for keyboards opens up a lot et attack vectors and is not recommended. On workstation? Server? |
df9969a
to
f22b26a
Compare
c5c98af
to
46b9c79
Compare
https://www.qubes-os.org/doc/usb-devices/#using-usb-keyboards-and-other-input-devices
@ 0rb677 I'm confused now. :P |
@0rb677 @Tonux599 @zifxify : Please let me know the current state of this PR at this point (and let me know if you know more people with boards in this issue. You can find flashable artifacts for 46b9c79 by clicking the green check mark on the commit which will bring you to those roms from the artifacts tab: |
@flammit : any objection on the server config? That was basically an upgrade of what was upstream with (plymouth fix for QubesOS) in board config and USB_COMPANION added. |
I actually do not use heads, but pure coreboot 4.11 with SeaBIOS. I would be happy to test heads, but will I be able to boot FreeBSD with it? This is my primary operating system. |
Since its kexec based from a linux payload, I do not think so in current situation but if things involved in that area.. I'll remove you from the list of kgpe-d16 testers under heads for the moment then. |
@tlaurion remove my comment. KGPE-D16 heads now works only with PS/2 keyboard. |
@0rb677 pike support added in both boards following #712 (comment) |
As said previously, once yellow dot will turn into green check, you can download build there (without USB keyboard support: PR welcome) |
@0rb677 : board addition for kgpe-d16_workstation-usb_keyboard with Pike support. |
@0rb677 b22d913 built successfully while save_cache for cache failed (got lost in commits it seems). Artifact is there and downloadable for new board config. Let me know how it goes. |
@0rb677 please test 2e4f046 build's artifacts above when build is finished and report in original ticket I tagged you in so that it can be merged in master. |
I will do it tomorrow. |
@0rb677 I would like you to launch said script from recovery shell. And screenshot what happened out of whiptail, from shell output. |
I dont understand it works with couple of bugs.
So it works? |
…, while kgpe-d16-> kgpe-d16_server
… build server and workstation)
…r gui-init to work in FB mode
… in whiptail (console mode, not FbWhiptail based
…nts (linux version defined under board config)
b4de802
to
e9895eb
Compare
Now par with master. Comments welcome, build happening on PR, as always (green arrow on latest commit: e9895eb) When build is ready, you can download roms per artifacts for all roms not requiring blobs outside of repos. |
…m out of ideas. Next step, ask CircleCI for support
Effort continues here: #867 |
Trying to get back QubesOS GUI installer to install QubesOS on a preflashed Heads system (Mitigation of "LUKS volume creation error from QubesOS text-based installer WON'T FIX error")