linuxboot / heads

A minimal Linux that runs as a coreboot or LinuxBoot ROM payload to provide a secure, flexible boot environment for laptops, workstations and servers.
https://osresearch.net/
GNU General Public License v2.0
1.42k stars 185 forks source link

Feature request : KGPE-D16 in workstation mode with Aspeed supported in FbWhiptail (second GPU HVM passthrough desired under QubesOS) and Pike support #712

Closed ghost closed 4 years ago

ghost commented 4 years ago

Do i need replace W25Q16BVAIG to W25Q128FVSG for heads flash?

I have built 16MB rom heads firmware using make BOARD=kgpe-d16

user@builder-heads:~/heads/build/kgpe-d16$ ls -lh kgpe-d16.rom 
16M

but W25Q16BVAIGDIP8 detected by ch341a show only 2M

DSC_0114

PS. i got help on #coreboot irc

< hell__> suxx_: the KGPE-D16 has a socketed DIP-8 flash chip
< hell__> you can use a flat screwdriver to *carefully* lift the chip out 

This is spi chip where located it. maybe someone else will come in handy, will be helpful

Windond 25Q16BVAIG datasheet

KGPE-D16

There is no problems with CH341a programmer

winbond111

suxx@lab:~/roms$ sudo flashrom -p ch341a_spi -r bios2.bin
flashrom v1.2 on Linux 5.4.0-28-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q16.V" (2048 kB, SPI) on ch341a_spi.
Reading flash... done.

Libreboot ,for example, works bad. Sometime boot, sometimes not. 9/10 powerups - it shows me black screen. I hope Heads will work better...

Tonux599 commented 4 years ago

Hi @0rb677

Do you mean W25Q128FVIQ as opposed to W25Q128FVSG? The W25Q128FVIQ is what I use and is a DIP8 chip as opposed to W25Q128FVSG which is a surface mounted chip.

Also check here for good RAM modules to use which may be affecting your successful boots. Also you will be required to use more than a single memory modules if you intend on using more than one CPU (I notice two heat sinks but one stick of RAM). Each processor is allocated memory from RAM located above/below it.

ghost commented 4 years ago

@Tonux599 hi and thanks :) W25Q128FVIQ dip-8 (W25Q128FV: 128M-bit / 16M-byte family) just it ordered on ebay and aliexpress. wait until the chip arrives How is performance? Do i need to tweak config for acpid onboard graphics? Does the motherboard work well with heads? Can you recommend a memory that is 100% wound up? I bought 4x16GB used ram but works only two modules (A2 and C2 slots)

So, for other people, this is BAD ram modules (2x6276 opteron 32 cores) bad-ram

This is GOOD ram modules (2x6276 opteron 32 cores) good-ram

mikebdp2 commented 4 years ago

@0rb677 1) Please consider adding this info to coreboot's wiki HCL - for other people to see. Otherwise, nobody - except the readers of this thread - could know about you experiences: the images you've uploaded (without retyping the text from them) aren't searchable in the Internet by a RAM model number. Also, have you ever discussed this RAM issue on coreboot's mailing lists or r/coreboot?

2) It could be that RAM has worked in the past and got broken in later coreboot versions. Have you checked the experiences of the other people with this RAM? There could've been a code regression.

3) RAM init code is a bit complicated, but it's the opensource - and you could read some of the RAM debug advices at the comments here https://www.reddit.com/r/coreboot/comments/gf9b1m/coreboot_on_an_amd_gseries_kabini_based_hp_thin/ . I've used this approach successfully to add the XMP / custom timings support for the coreboot AMD boards with opensource AGESA. These patches could be found on https://review.coreboot.org/ by searching for "AMD_XMP" or just applying the https://review.coreboot.org/c/coreboot/+/40495 . With this patch, you could enforce the custom timings on your RAM by substituting the SPD readings, and maybe that will help to get your RAM working.

tlaurion commented 4 years ago

@0rb677 1) Please consider adding this info to coreboot's wiki HCL - for other people to see. Otherwise, nobody - except the readers of this thread - could know about you experiences: the images you've uploaded (without retyping the text from them) aren't searchable in the Internet by a RAM model number. Also, have you ever discussed this RAM issue on coreboot's mailing lists or r/coreboot?

2) It could be that RAM has worked in the past and got broken in later coreboot versions. Have you checked the experiences of the other people with this RAM? There could've been a code regression.

3) RAM init code is a bit complicated, but it's the opensource - and you could read some of the RAM debug advices at the comments here https://www.reddit.com/r/coreboot/comments/gf9b1m/coreboot_on_an_amd_gseries_kabini_based_hp_thin/ . I've used this approach successfully to add the XMP / custom timings support for the coreboot AMD boards with opensource AGESA. These patches could be found on https://review.coreboot.org/ by searching for "AMD_XMP" or just applying the https://review.coreboot.org/c/coreboot/+/40495 . With this patch, you could enforce the custom timings on your RAM by substituting the SPD readings, and maybe that will help to get your RAM working.

Some trace of scattered doc: https://www.raptorengineering.com/coreboot/kgpe-d16-status.php https://libreboot.org/docs/hardware/kgpe-d16.html https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

Memory chips known to work: https://www.coreboot.org/Board:asus/kgpe-d16

tlaurion commented 4 years ago

@mikebdp2 @0rb677 make BOARD=kgpe-d16 will produce headless board as it is now, other pull requests under heads have been made to split server and workstation configurations. Current situation takes for granted that you reprogrammed the BMC internally with provided Heads script. Let me know how it goes.

It is also possible to deactivate ASPEED onboard graphic card (shitty for workstation, really low resolution. Good for headless IMHO but guys out there preferred headless over hybrid so it is how it is now), while board's associated linux kernel config will need to be tweaked to support your chosen card. I owuld advise doing a PR when you are successful, in the form: kgpe-d16-wks-graphic_card

Ping me in your progress, I can definitely give a hand and help you document things out in another https://github.com/osresearch/heads-wiki page

This project's documentation needs a lot of love, I know.

ghost commented 4 years ago

I dont understand.

Current situation takes for granted that you reprogrammed the BMC internally with provided Heads script.

@tlaurion @mikebdp2 What does it mean? I need to use Open On-Chip Debugger, also buy ARM-USB-TINY and FT2232HL spi programmator for BMC module?

The system boots without outputting console to the vga graphic card until the system setups it's own console (both coreboot, heads and password output are sent to serial console and KVM).

What passwords do you mean? I have clean HDD and replaced bios by heads (16mb spi chip). There is no video signal. I cant boot any system from usb flash. Also there is no ASMB4 or ASMB5 KVM firmware module on this motherboard by default. Do i need to buy it? Do i need to buy this https://www.asus.com/com/Commercial-Servers-Workstations/ASMB4iKVM/ Or it can be flashed by serial console inside heads? Any chance to get GUI whiptail like on x220/x230 ? My progress is here https://github.com/0rb677/KGPE-D16-HEADS I have built bmc port and flashed new chip use master branch. When i start PC, there is nothing on the screen. Can you help me more detail?

alexmaloteaux commented 4 years ago

I dont understand.

Current situation takes for granted that you reprogrammed the BMC internally with provided Heads script.

check "Transfer Flash image to destination host" here : https://raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

@tlaurion @mikebdp2 What does it mean? I need to use Open On-Chip Debugger, also buy ARM-USB-TINY and FT2232HL spi programmator for BMC module?

No, OpenOcd and a 20 pin jtag debugger is if you want to debug/improve OpenBmc Booting process

There is no video signal. I cant boot any system from usb flash.

By default heads does not input anything until you input /configure through the uart port from within OpenBMC. Actually in my case there is a HEAD logo... Your system is not booting because i thing you have flashed OpenBMC that is 16Mb too on the Bios Chip and not the IPMI module

Also there is no ASMB4 or ASMB5 KVM firmware module on this motherboard by default. Do i need to buy it?

Yes

Do i need to buy this https://www.asus.com/com/Commercial-Servers-Workstations/ASMB4iKVM/

I have ASMB5 and it works perfectly

Or it can be flashed by serial console inside heads?

no you have to flash the module from a linux system running on the board with the raptor flashrom fork

Any chance to get GUI whiptail like on x220/x230 ?

dont know

My progress is here https://github.com/0rb677/KGPE-D16-HEADS I have built bmc port and flashed new chip use master branch. When i start PC, there is nothing on the screen. Can you help me more detail?

I think because you flashed OpenBmc on the Bios chip and not on the ipmi module, reflash head in that case on the Bios

ghost commented 4 years ago

@alexmaloteaux big thanks for help. i will try again. How do you build heads? make BOARD=kgpe-d16 without any blobs added? thats all?

I think because you flashed OpenBmc on the Bios chip

No. I flashed https://github.com/0rb677/KGPE-D16-HEADS/blob/master/kgpe-d16.rom on the 16 mb spi Winbond chip. Like it usually do (use ch341a programmator)

DSC_0147

alexmaloteaux commented 4 years ago

@alexmaloteaux big thanks for help. i will try again. How do you build heads? make BOARD=kgpe-d16 without any blobs added? thats all?

Yes but i have myself an issue with the TPM being recognized by coreboot but not by tpm-tools (tag issue ...) :( so I use coreboot without screen purely over OpenBmc console until i have more time to debug

alexmaloteaux commented 4 years ago

Ram, : 2x Micron 16GB server memory Dimm 2Rx4 Ram DDR3 MT36KSF2G72PZ-1G6E1FE PC3L-12800R CPU : 2x Opteron 6378 Asus Pike is coming , im using IBM m1015 atm un hba it Mode.

I dont reset CMOS

Im using coreboot/seabios atm over OpenBmc, and trying to fix an issue with head TPM

ghost commented 4 years ago

@alexmaloteaux thanks a lot!!!

tlaurion commented 4 years ago

I have seen your message but I'm away of computer . You should at least be seeing ASPEED message on screen at boot.

Maybe the video jumper on motherboard is set to external video card? It should be set to internal video card.

There is a PR that splits workstation board from server board.

Ill try to get back to you in the next days. You can also see the maintainer issue and tag other kgpe-d16 users.

On May 31, 2020 5:58:33 PM UTC, 0rb notifications@github.com wrote:

I dont understand.

Current situation takes for granted that you reprogrammed the BMC internally with provided Heads script.

@tlaurion What does it mean? I need to use Open On-Chip Debugger, also buy ARM-USB-TINY and FT2232HL spi programmator for BMC module?

The system boots without outputting console to the vga graphic card until the system setups it's own console (both coreboot, heads and password output are sent to serial console and KVM). What passwords? I have clean HDD and replaced bios by heads. There is no video signal. I cant boot any system from usb flash. Also there is no ASMB4 or ASMB5 KVM firmware module on this motherboard by default. Do i need to buy it? Or it can be flashed by UART from console use?

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/osresearch/heads/issues/712#issuecomment-636505640 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

ghost commented 4 years ago

@tlaurion Without ASMB5 KVM and BMC reflashed? I don’t know for sure, but I remember that Libreboot started with this motherboard one of out ten times (1/10). Image from here https://www.mirrorservice.org/sites/libreboot.org/release/stable/20160907/rom/grub/libreboot_r20160907_grub_kgpe-d16.tar.xz Stock bios works good.

You should at least be seeing ASPEED message on screen at boot.

I’ll try to test it again this week

tlaurion commented 4 years ago

@0rb677 @alexmaloteaux I've updated https://github.com/osresearch/heads/pull/472 so that it is rebased on master. It makes two boards: a server (which is the equivalent of master, and takes into account that the OpenBMC KVM chip was reflashed and outputs serial output to it, and a workstation board, which outputs everything to tty0 (instead of server board over ttyS1)

Let me know if you have any question. As far as I know, coreboot 4.8.1 was not able to deal correctly with TPM and was left behind with a noTPM option using the libremKey as a less advantageous root of trust. VBOOT+measured boot was never tested by me and the KGPE-D16 board stayed at the stage of PoC.

Which is why #719

tlaurion commented 4 years ago

@0rb677 @alexmaloteaux

Note that the workstation board could use gui-init instead of generic-init if ASPEED (AST) support was added on workstation kernel config (to not depend on shared linux-kgpe-d16.config as those two boards are doing currently).

If you need more help in that direction, let me know.

A discussion is happening under #721 on how we could still support the kgpe-d16 and duplicate coreboot config to 4.11 and make it supported into Heads with proper TPM support.

Your involvement would be important, since supporting the kgpe-d16 in its current state without #719 is unfortunately not a priority on me and should be a community sideproject for someone that wants it more supported in its 4.11 status.

tlaurion commented 4 years ago

I dont understand.

Current situation takes for granted that you reprogrammed the BMC internally with provided Heads script.

@tlaurion @mikebdp2 What does it mean? I need to use Open On-Chip Debugger, also buy ARM-USB-TINY and FT2232HL spi programmator for BMC module?

The system boots without outputting console to the vga graphic card until the system setups it's own console (both coreboot, heads and password output are sent to serial console and KVM).

What passwords do you mean? I have clean HDD and replaced bios by heads (16mb spi chip). There is no video signal. I cant boot any system from usb flash. Also there is no ASMB4 or ASMB5 KVM firmware module on this motherboard by default. Do i need to buy it? Do i need to buy this https://www.asus.com/com/Commercial-Servers-Workstations/ASMB4iKVM/ Or it can be flashed by serial console inside heads? Any chance to get GUI whiptail like on x220/x230 ? My progress is here https://github.com/0rb677/KGPE-D16-HEADS I have built bmc port and flashed new chip use master branch. When i start PC, there is nothing on the screen. Can you help me more detail?

Missed that. You can reprogram from Heads the ASMB4iKVM with that script https://github.com/osresearch/heads/blob/master/initrd/bin/flashrom-kgpe-d16-openbmc.sh

You have to follow https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

Tonux599 commented 4 years ago

As I mentioned in #719 but will reiterate here, Asus 90-C1B0AU-00XBN0VZ is a TPM1.2 module that is compatible with this board and heads. In concerns to usability of this board, with that TPM module and a YubiKey this branch provides almost identical functionality that heads does on my thinkpads. I'll be maintaining it until more concert decisions are made on the future of this board.

alexmaloteaux commented 4 years ago

Missed that. You can reprogram from Heads the ASMB4iKVM with that script https://github.com/osresearch/heads/blob/master/initrd/bin/flashrom-kgpe-d16-openbmc.sh

Thats nice :)

Any idea where i can buy a Asus 90-C1B0AU-00XBN0VZ, all major suppliers are out of stock

Tonux599 commented 4 years ago

Any idea where i can buy a Asus 90-C1B0AU-00XBN0VZ, all major suppliers are out of stock

@alexmaloteaux that's the problem, I took a gamble on a ebay listing titled "Asus TPM" which picture was 20pin but looked slightly different than my Asus TPM2 module. For future reference to anyone looking for this module note that the TPM1.2 module has a capacitor to the left of the chip whereas the TPM2 module does not.

tlaurion commented 4 years ago

Will buy too

ghost commented 4 years ago

@tlaurion are you here? trying your branch and another spi chip. (i have two) I still can’t understand what the problem is and why I didn’t have a video signal without any KVM and BMC. Also I still need to pick up the console from work and buy ASMB5 Can you help me to build correctly branch for a workstation with whiptal like in x220? Is it possible? External video cards will be GTX 1060. still look RAM settings in the config , what if it starts up all? I have all hope for you guys. I’ll check the jumpers now.

suxx@lab:~/Build$ git clone https://github.com/tlaurion/heads
Cloning into 'heads'...
remote: Enumerating objects: 170, done.
remote: Counting objects: 100% (170/170), done.
remote: Compressing objects: 100% (101/101), done.
remote: Total 9895 (delta 95), reused 121 (delta 58), pack-reused 9725
Receiving objects: 100% (9895/9895), 4.39 MiB | 6.78 MiB/s, done.
Resolving deltas: 100% (6745/6745), done.
suxx@lab:~/Build$ cd heads/ && git checkout -b kgpe-d16_current_working
Switched to a new branch 'kgpe-d16_current_working'
suxx@lab:~/Build/heads$ make BOARD=kgpe-d16

(which is the equivalent of master, and takes into account that the OpenBMC KVM chip was reflashed and outputs serial output to it, and a workstation board, which outputs everything to tty0 (instead of server board over ttyS1)

Is it possible to start heads normally? With shitty resolution and use ASPEED default VGA output?

tlaurion commented 4 years ago
rm -rf heads
git clone https://github.com/tlaurion/heads
cd heads
git checkout kgpe-d16_current_working
make BOARD=kgpe-d16_workstation

but then you will hit #733

tlaurion commented 4 years ago

@tlaurion are you here? trying your branch and another spi chip. (i have two) I still can’t understand what the problem is and why I didn’t have a video signal without any KVM and BMC.

Simply because the master branch takes into account that all output goes to BMC and was subject to debates on past tickets. Main branch didnt seperate boards into workstation (without BMC) and server (headless) and my PoC stayed there without receiving much love since I do use it headless and since #719, I have lost a bit of interest and do not have much time to invest into this board support anymore.

Also I still need to pick up the console from work and buy ASMB5 Can you help me to build correctly branch for a workstation with whiptal like in x220? Is it possible? External video cards will be GTX 1060. still look RAM settings in the config , what if it starts up all? I have all hope for you guys.

It would, but AST support should be activated in linux config. You can try that path for the workstation linux config, and modify the workstation board configuration to use gui-init instead of generic-init.

For linux config change:

cp config/linux-kgpe-d16_workstation build/linux-4XXXX/.config
cd  build/linux-4XXXX/
make menuconfig

Activate AST graphic for server board. Review jumper on motherboard. then

make savedefconfig
cp defconfig ../../config/linux-kgpe-d16_workstation.config
make BOARD=kgpe-d16_workstation

If I recall well, it worked before. If you do, please do a PR.

I’ll check the jumpers now.

suxx@lab:~/Build$ git clone https://github.com/tlaurion/heads
Cloning into 'heads'...
remote: Enumerating objects: 170, done.
remote: Counting objects: 100% (170/170), done.
remote: Compressing objects: 100% (101/101), done.
remote: Total 9895 (delta 95), reused 121 (delta 58), pack-reused 9725
Receiving objects: 100% (9895/9895), 4.39 MiB | 6.78 MiB/s, done.
Resolving deltas: 100% (6745/6745), done.
suxx@lab:~/Build$ cd heads/ && git checkout -b kgpe-d16_current_working
Switched to a new branch 'kgpe-d16_current_working'
suxx@lab:~/Build/heads$ make BOARD=kgpe-d16

(which is the equivalent of master, and takes into account that the OpenBMC KVM chip was reflashed and outputs serial output to it, and a workstation board, which outputs everything to tty0 (instead of server board over ttyS1)

Is it possible to start heads normally? With shitty resolution and use ASPEED default VGA output?

If terminal output goes to /dev/tty0 and not serial terminal (/dev/ttyS*) your should have output if ASPEED shows to your screen (which has to be caused by jumper setting, or as someone else stated before, if you flashed wrong image to the 16Mb flash chip.)

@0rb677 Let me know how it goes.

ghost commented 4 years ago

@tlaurion thank you very much for detailed answer and spending your free time :) I haven’t received so much information about this board anywhere else.

tlaurion commented 4 years ago

733 is fixed. Retrying CIs builds.

ghost commented 4 years ago

i am too and i see your new issue #735

make[1]: Leaving directory '/home/suxx/Build/heads/build/linux-4.14.62'
2020-06-03 23:22:49+03:00 MAKE musl-cross
ghost commented 4 years ago

this is a VGA jumper vga-jumper

tlaurion commented 4 years ago

735 fixed with https://github.com/tlaurion/heads/commit/18f8265e880f4d199466ab282c9261a0fa9925df merged in master.... continuing...

ghost commented 4 years ago

@tlaurion @Tonux599 @alexmaloteaux @mikebdp2

(5/5 success) with 3 x16GB memory sticks (DIMM_A2 + DIMM_C2 + DIMM_E2) and another 16mb spi windond chip flashed with kgpe-d16_workstation branch.

It wont boot for me :

  1. if memory stick in wrong slot (same situation with stock rom)
  2. if no external GPU Video Card installed in PCI-E slot

This configuration is boot stable. tomorrow i will try to install something and check if ram works correctly. add hdd. second vga card and pike controller.

Thank you guys. Im happy :)

DSC_0163

tlaurion commented 4 years ago

You added ast support in Linux config.as explained above?

On June 3, 2020 9:49:23 PM UTC, 0rb notifications@github.com wrote:

Done.

2020-06-04 00:47:45+03:00 MAKE coreboot
2020-06-04 00:48:22+03:00 DONE coreboot
"/home/suxx/Build/heads/build/coreboot-4.8.1/kgpe-d16_workstation/cbfstool" "/home/suxx/Build/heads/build/coreboot-4.8.1/kgpe-d16_workstation/coreboot.rom" print
Name                           Offset     Type           Size   Comp
cbfs master header             0x0        cbfs header        32 none
fallback/romstage              0x80       stage          174468 none
config                         0x2aa80    raw               572 none
revision                       0x2ad00    raw               561 none
cmos.default                   0x2af80    cmos_default      256 none
cmos_layout.bin                0x2b0c0    cmos_layout      3524 none
fallback/dsdt.aml              0x2bec0    raw             10010 none
(empty)                        0x2e640    null             5976 none
s3nv                           0x2fdc0    raw             65536 none
fallback/ramstage              0x3fe00    stage           88041 none
fallback/payload               0x55640    simple elf    5441458 none
microcode_amd.bin              0x585e40   microcode       12684 none
microcode_amd_fam15h.bin       0x589040   microcode        7876 none
(empty)                        0x58af80   null         10962392 none
bootblock                      0xfff580   bootblock        2120 none
2020-06-04 00:48:22+03:00 INSTALL   build/coreboot-4.8.1/kgpe-d16_workstation/coreboot.rom => build/kgpe-d16_workstation/coreboot.rom
9087d0a185745bd913fcd61da0400011f5d14e526a26a6fd5cb7406b9d81689c  build/kgpe-d16_workstation/coreboot.rom
9087d0a185745bd913fcd61da0400011f5d14e526a26a6fd5cb7406b9d81689c  /home/suxx/Build/heads/build/kgpe-d16_workstation/coreboot.rom

Start to flash.

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/osresearch/heads/issues/712#issuecomment-638479771 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

ghost commented 4 years ago

@tlaurion forgot. rebuilding.

paulmenzel commented 4 years ago

Guys, it’s really hard to follow these issues, and in my opinion also rude to expect users to read through the thread. (Unfortunately GitHub comments do not support threading.)

I’d really appreciated it, if you opened one issue with a descriptive title/summary for each problem, so issue discussions are hopefully shorter, and users can more easily search the issue list to find solutions for their problems.

ghost commented 4 years ago

@paulmenzel @tlaurion can you add build process for kgde-d16 on website http://osresearch.net/ from here? And then we can remove this thread. Also what about prebuilt roms on heads ftp like libreboot did? we have not tried to watch ram timings in the config..one ram stick wont boot. i have 4x16

Tonux599 commented 4 years ago

@0rb677 modifications to the site can be made by PR here. The build process for the board will eventually be the same as any other board building with make BOARD=$BOARD. This needs to be satisfied before prebuilt roms are provided.

@tlaurion is there any consideration on making perhaps a IRC channel for first line support or general discussion?

tlaurion commented 4 years ago

@tlaurion is there any consideration on making perhaps a IRC channel for first line support or general discussion?

Heads channel lives here

ghost commented 4 years ago

@tlaurion it works with AST enabled. But it cant initialize gui-init

DSC_0167

stt3

ghost commented 4 years ago

@tlaurion do you need dmesg/lsusb/lspci/dmidecode?

Memory works. 47,1GB found (but dmesg show some ECC error detected on the NB) ASPEED works. Pike works.

alexmaloteaux commented 4 years ago

@0rb677 i know it is not related but did you flash the pike with the optrom ? i flashed without as i do for all lsi cards and the card is detected but not the disk connected to the pike sata ports :( Also with a pike the server shutdown after a while by himself , i guess because it becomes extremly hot ?

ghost commented 4 years ago

@alexmaloteaux im not try run it 365/24/7. But 3-4 days without shutdown it works good. No im not flash it. Did you try to enter on controller ctrl +s ? Change sata cables? Change sata ports? I use cheapest Pike 2008 and default 3.5 sata WD 3TB. But not tryed to build raid or attach SAS disk. pike

tlaurion commented 4 years ago

@tlaurion it works with AST enabled. But it cant initialize gui-init

DSC_0167

stt3

https://github.com/osresearch/heads/issues/477#issuecomment-461938492

Attempts continuing over https://github.com/tlaurion/heads/tree/kgpe-d16_current_working

tlaurion commented 4 years ago

https://github.com/osresearch/heads/issues/560#issue-441766401

tlaurion commented 4 years ago

https://github.com/osresearch/heads/compare/master...tlaurion:kgpe-d16_staging

alexmaloteaux commented 4 years ago

enter on controller ctrl +s ? Change sata cables? C

Hi i found issue;

There is an incompatibility between Freebsd - mps driver (lsi) and some hard disk.. Also without proper ventilation the chipset get past 80 Degre and OpenBmc shut down the board .

All fixed now thanks

ghost commented 4 years ago

@tlaurion

  1. re-merge https://github.com/tlaurion/heads/tree/kgpe-d16_current_working
  2. trying to add this changes and enable FBWhiptail
    #Whiptail
    #CONFIG_SLANG=y
    #CONFIG_NEWT=y
    #Board supports TPMv2. Heads support TPMv1 
    CONFIG_TPM=n
    #FBWhiptail
    CONFIG_CAIRO=y
    CONFIG_FBWHIPTAIL=y
    CONFIG_GPG2=y
    export CONFIG_WARNING_BG_COLOR="--background-gradient 0 0 0 150 125 0"
    export CONFIG_ERROR_BG_COLOR="--background-gradient 0 0 0 150 0 0"

    from here https://github.com/osresearch/heads/commit/5c4f415e0927cbe15c847ec57059474b6123a8ab to heads/boards/kgpe-d16_workstation/kgpe-d16_workstation.config and re-flashing

tlaurion commented 4 years ago

Let me know how it goes.

#Whiptail
CONFIG_SLANG=y
CONFIG_NEWT=y

Will permit you to launch gui-init in text mode instead of FbWhiptail.

For the changes linked to using libremkey without a TPM, I wouldn't advise merging them. Discussion happened here

Best PoC for server/workstation would be to have 1.2 TPM board and add export add CONFIG_TPM=y to board config.

If LIBREM_KEY is added in board config, the board becomes dependent on a HOTP compliant USB Security dongle to enforce remote attestation USB Security dongle, which requires a TPM 1.2 compliant chip for measurements (which may require to activate additional TPM chips in coreboot config.)

For QubesOS GUI issue, i'm not sure ASpeed is supported in QubesOS initrd. I remember I was able to install QubesOS 4.x but had VNC hack didnt went totally well for me and gave up a while ago.

tlaurion commented 4 years ago

Because AST doesnt work with fbwhiptail ?

@0rb677 : I don't remember. My use case was server. If you want to go the workstation way and use an external graphic card then the onboard Aspeed, you will have to duplicate the board config and specialize it. (eg: kgpe-d16_workstation_nvidia-gpu)

I may have been able to boot with Aspeed and local tty configuration with a newer kernel in 2018-2019, on which I depended on my privacybeast branch. If I remember correctly, the AST support in kernel 4.14.62 was new at that time, and the number of patches that were applied to that support since that version are quite important. I do not know the QubesOS dom0 (Fedora-25 now) support for AST. The thing that needs to be known is that the FB needs to be prepared by Heads' linux kernel since it passes vga=current when kexec'ing into new kernel. So if the FB is not ready, there will be screen corruption, and in the screenshot above, it seems that QubesOS installer doesn't detect the FB properly and stays in console mode.

QubesOS doesn't play well with console installer.

Having AST supported in Heads might require the kernel to be upgraded, which requires a lot of work linked to #590 . Upgrading module/kernel cannot just be made by applying the same kernel configuration because of #732 and #590, and breaks x230-flash and t430-flash because of really limited space in CBFS (4mb). So to upgrade the kernel (for all boards), the *-flash boards will need to be reduced in functionalities (and kernel features removed, eg networking, crypto etc), else upgrading the kernel would break some other boards.

This is why this is PoC, unfortunately. Keep up :)

ghost commented 4 years ago

@tlaurion workstation way is hard with nvidia cards. because its hard to get working in Qubes (attach to HVM). i want to try fbwhip again, because i think i merged your modifications without whip package and modified config. And then i go your text mode way with SLANG.

If you want to go the workstation way and use an external graphic card then the onboard Aspeed

No reason. Heads works good. Qubes works on onboard VGA card. Only if dom0 will be laggy with AST. I want to use two External cards for attaching to HVM. Is it good idea?

tlaurion commented 4 years ago

@tlaurion workstation way is hard with nvidia cards. because its hard to get working in Qubes (attach to HVM). i want to try fbwhip again, because i think i merged your modifications without whip package and modified config. And then i go your text mode way with SLANG.

That would be having it at install, not in HVM but for dom0. ASpeed not being seen by the whole system because of jumper setting. I would have expected workstation board to be used as a workstation. QubesOS on 800x600 is not really useable as a workstation. So the kgpe-d16 workstation board doesn't seem really useful to me, unless coupled with a different kernel configuration supporting external GPU.

tlaurion commented 4 years ago

@0rb677 : this would change pretty soon with https://www.qubes-os.org/news/2020/03/18/gui-domain/ for AST, VNC setup permitting to control QubesOS remotely. Also note https://github.com/Rudd-O/qubes-network-server/

Let me know how it goes!

ghost commented 4 years ago

@tlaurion this is sad :( Maybe set jumper to external card. One Nvidia be for dom0 and Heads. Second for GPU passthrouth to HVM ? Is it possible?