Msi dasharo upstream #1995

Tonux599 · 2025-08-27T00:04:08Z

Replaces #1962

This is based on Dasharo's coreboot instead of coreboot 25.03.

This is draft for the moment, I'll be testing MSI Pro Z790-P DDR5 on Thursday 28th. I'll un-draft post testing.

It should work, as I have been using my custom fork https://github.com/Tonux599/heads/tree/my-custom-msi_z790p_ddr5 for awhile now without issue. However, that fork is not suitable for most as I've customised it for my own uses (like forcing XMP, disabling hyperthreading, etc).

@mblanqui @Hexdigest123 can you test on your boards?

Need to do some commit cleanup pre-merge also.

TODO:

Maybe upgrade to Dasharo v1.1.5/v0.9.3

Signed-off-by: Michał Żygowski <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Signed-off-by: Michał Kopeć <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Signed-off-by: Matthew Drobnak <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Signed-off-by: Thomas Clarke <[email protected]>

Tonux599 · 2025-08-28T12:54:45Z

See table below for artefacts ready to be tested.

Board	Artefacts
UNTESTED_msi_z690a_ddr4	https://app.circleci.com/pipelines/github/Tonux599/heads/146/workflows/e5e32e13-c5f3-41e8-b965-49accd44880f/jobs/1666/artifacts
UNTESTED_msi_z690a_ddr5	https://app.circleci.com/pipelines/github/Tonux599/heads/146/workflows/e5e32e13-c5f3-41e8-b965-49accd44880f/jobs/1676/artifacts
UNTESTED_msi_z790p_ddr4	https://app.circleci.com/pipelines/github/Tonux599/heads/146/workflows/e5e32e13-c5f3-41e8-b965-49accd44880f/jobs/1667/artifacts
msi_z790p_ddr5	https://app.circleci.com/pipelines/github/Tonux599/heads/146/workflows/e5e32e13-c5f3-41e8-b965-49accd44880f/jobs/1679/artifacts

I have tested msi_z790p_ddr5 myself and it works without issue. A few things to note:

No USB keyboard support.
PS/2 keyboard work (this was unsupported in Dasharo's release).
No HOTP support.
There's no bootsplash right now as at one point it was causing hangs. This can be retested later if required.
This uses flashprog instead of flashrom. Dasharo's release used their own flashrom branch, but current heads flashprog works fine for my board.

In the future, we can create variants supporting USB keyboard and HOTP if the community requires.

Future issues that need addressing are:

Making sure bootsplash works.
Avoiding the workaround for >16MiB flash (4125177, bf9708f, and 9be0ce3). A fix to flashtools may help here. The current workaround adds time to boot.

@tlaurion this is good to merge IMO, msi_z790p_ddr5 works great. It's now over to others to test their variants.

tlaurion · 2025-08-28T15:45:10Z

initrd/bin/cbfs-init

+	/bin/flashprog -p internal --fmap -i COREBOOT -i FMAP -r /tmp/cbfs-init.rom \
+		&& CBFS_ARG=" -o /tmp/cbfs-init.rom" \
+		|| echo "Failed reading Heads configuration from flash! Some features may not be available."
+fi
+
 # Load individual files
-cbfsfiles=`cbfs -t 50 -l 2>/dev/null | grep "^heads/initrd/"`
+cbfsfiles=`cbfs -t 50 -l $CBFS_ARG 2>/dev/null | grep "^heads/initrd/"`


@Tonux599 what happens when calling cbfs on MSI platform? What is the issue that needs this workaround?

If my understanding is correct, the cbfs util reads the cbfs from a location in memory. If a flash is >16M then either:

Coreboot doesn't map CBFS's larger than 16M into memory. Or,

cbfs doesn't have the ability to read a region in memory larger than 16M.

Not sure what it is, but the above workaround is from dasharo's release. Effectively, it uses flashprog to read the flash chip (taking 10s of seconds), and then having the cbfs util read from the resulting file.

Edit: and calling cbfs as normal results in an invalid header magic error (presumably because it's reading garbage).

Edit: and calling cbfs as normal results in an invalid header magic error (presumably because it's reading garbage).

Yes that's why I ask because novacustom boards have spi chips of 32mb and don't need that workaround.

Edit: and calling cbfs as normal results in an invalid header magic error (presumably because it's reading garbage).

Yes that's why I ask because novacustom boards have spi chips of 32mb and don't need that workaround.

Ah yes, whilst the flash for those boards are 32M I presume the CBFS size is <=16M. These boards need a bigger CBFS so we can fit the ROMHOLE in at a specific location (which allows the rom to be flashed from a usb port on the back).

@miczyg1 am I correct?

Indeed. cbfs utility only works for cbfs size or flash size <=16MB. Otherwise you need to dump whole flash to make CBFS parsing work...

@tlaurion happy if I resolve this conversation?

@Tonux599 that deserves a new issue to be tracked/fixed/resolved under Heads and then osresearch/flashtools. After which this thread can be resolved yes, cross-linking those for traceability. Using flashrom/flashprog is a hack here.

@miczyg1 random thought, could we not have a 16MB CBFS on the 32MB flash and just write the ROMHOLE to where it belongs on the flash? Presuming the ROMHOLE is somewhere past the the first 16MB.

@Tonux599 you can't do that. heads paylaod is ~8MB in size, it will not fit neither above nor belwo ROMHOLE if CBFS/coreboot is just 16MB. The ROMHOLE fixed address i just that unfortunate, that it cannot be workarounded. By forcefully writing the ROMHOLE you will corrupt the CBFS and make the image unbootable most likely.

@miczyg1 Thanks. Trying to wrap my brain around this but think I'm getting there. Presumably it collides with the ROMHOLE is because the CBFS (and bootblock) needs to be placed at the end of the 32MB flash chip?

Also trying to look into a fix for the cbfs utility to read the whole CBFS mapped into memory. @miczyg1 is the whole 32MB mapped into memory or just the top 16MB? Having looked at some cbmem logs it looks like FLASH with size 0x2000000 is mapped @ 0xfe000000.

Just trying to work out if this is a limitation in the cbfs utility or coreboot.

BOARDS_AND_TESTERS.md

tlaurion

LGTM :)

aphick · 2025-09-17T23:52:25Z

Thanks so much for this PR! Testing it on my z790p pro DDR5 and it works great (I enabled USB keyboards)

Hexdigest123 · 2025-09-18T09:37:04Z

Thanks so much for this PR! Testing it on my z790p pro DDR5 and it works great (I enabled USB keyboards)

Did you have any issues setting the whole thing up or were there any hoops i would try it on my device but the last thing i wanna do is reflash my board with a programmer because the firmware ripped it apart

Tonux599 · 2025-09-18T16:45:40Z

How do I enable USB keyboard support, and if it's already somewhat stable, I'd move to Heads completely if you think this is feasible.

I set export CONFIG_USB_KEYBOARD=y in boards/msi_z790p_ddr5/msi_z790p_ddr5.config but this did NOT enable them. Once flashed I had to use a PS2 Keyboard to enable USB keyboards in the Heads settings

Looks like it should be CONFIG_REQUIRE_USB_KEYBOARD=y not CONFIG_USB_KEYBOARD=y. Thank you for raising this, looks like it changed since Dasharo's Heads release.

@Hexdigest123 please use CONFIG_REQUIRE_USB_KEYBOARD=y and report back your test results. Also, what board are you using?

Signed-off-by: Thomas Clarke <[email protected]>

Tonux599 · 2025-09-18T16:51:43Z

@tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

Hexdigest123 · 2025-09-18T16:51:56Z

How do I enable USB keyboard support, and if it's already somewhat stable, I'd move to Heads completely if you think this is feasible.

I set export CONFIG_USB_KEYBOARD=y in boards/msi_z790p_ddr5/msi_z790p_ddr5.config but this did NOT enable them. Once flashed I had to use a PS2 Keyboard to enable USB keyboards in the Heads settings

Looks like it should be CONFIG_REQUIRE_USB_KEYBOARD=y not CONFIG_USB_KEYBOARD=y. Thank you for raising this, looks like it changed since Dasharo's Heads release.

@Hexdigest123 please use CONFIG_REQUIRE_USB_KEYBOARD=y and report back your test results. Also, what board are you using?

Im using the msi_z790p_ddr5 and thanks for the clarification

tlaurion · 2025-09-18T16:57:09Z

@tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

I am not sure about this. People coming to Heads, having a board that permits ps2 keyboard but deciding to use USB? USB hid being a security risk, is there anything justifying usage of USB keyboard vs ps2?

If so, what about we enable it in config by default, and warn the user to deactivate it through config for additional security?

Otherwise I don't have anything against it per se, but we might at some point hit some limitations through CircleCI for free tier build time but we ar not there yet.

Tonux599 · 2025-09-18T17:01:26Z

@tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

I am not sure about this. People coming to Heads, having a board that permits ps2 keyboard but deciding to use USB? USB hid being a security risk, is there anything justifying usage of USB keyboard vs ps2?

If so, what about we enable it in config by default, and warn the user to deactivate it through config for additional security?

Otherwise I don't have anything against it per se, but we might at some point hit some limitations through CircleCI for free tier build time but we ar not there yet.

If CONFIG_USER_USB_KEYBOARD=y is set a build time can it be disabled by the user later? That might be the best of both worlds and yeah maybe sometime add a warning somewhere that it has been enabled.

Tonux599 · 2025-09-18T17:03:57Z

Looks like Dasharo literally just released new versions for the MSI boards, so will update sometime.

https://docs.dasharo.com/variants/msi_z690/releases/#v115-2025-09-18
https://docs.dasharo.com/variants/msi_z790/releases/#v093-2025-09-18

non-LTS so may not be as stable though.

tlaurion · 2025-09-18T17:10:49Z

@tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

I am not sure about this. People coming to Heads, having a board that permits ps2 keyboard but deciding to use USB? USB hid being a security risk, is there anything justifying usage of USB keyboard vs ps2?

If so, what about we enable it in config by default, and warn the user to deactivate it through config for additional security?

Otherwise I don't have anything against it per se, but we might at some point hit some limitations through CircleCI for free tier build time but we ar not there yet.

If CONFIG_USER_USB_KEYBOARD=y is set a build time can it be disabled by the user later? That might be the best of both worlds and yeah maybe sometime add a warning somewhere that it has been enabled.

All laptop boards now build and ship usb hid, but don't load it by default unless configured so. config-gui.sh documents this as code.

tlaurion · 2025-09-18T17:10:49Z

@tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

I am not sure about this. People coming to Heads, having a board that permits ps2 keyboard but deciding to use USB? USB hid being a security risk, is there anything justifying usage of USB keyboard vs ps2?

If so, what about we enable it in config by default, and warn the user to deactivate it through config for additional security?

Otherwise I don't have anything against it per se, but we might at some point hit some limitations through CircleCI for free tier build time but we ar not there yet.

If CONFIG_USER_USB_KEYBOARD=y is set a build time can it be disabled by the user later? That might be the best of both worlds and yeah maybe sometime add a warning somewhere that it has been enabled.

All laptop boards now build and ship usb hid, but don't load it by default unless configured so. config-gui.sh documents this as code.

tlaurion · 2025-09-19T19:11:56Z

Looks like Dasharo literally just released new versions for the MSI boards, so will update sometime.

https://docs.dasharo.com/variants/msi_z690/releases/#v115-2025-09-18
https://docs.dasharo.com/variants/msi_z790/releases/#v093-2025-09-18

non-LTS so may not be as stable though.

Both based on coreboot 24.12.

As general advice, use make coreboot helpers to save in defconfig format, remove config lines there that should not be overriden, and then use helper to save back in oldconfig format.

@Tonux599 do you plan on bumping coreboot version soon? Mostly all boards but NV4x seem to have been bumped, which heads share for buildstack for most boards.

tlaurion · 2025-09-19T19:18:55Z

@tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

I am not sure about this. People coming to Heads, having a board that permits ps2 keyboard but deciding to use USB? USB hid being a security risk, is there anything justifying usage of USB keyboard vs ps2?

If so, what about we enable it in config by default, and warn the user to deactivate it through config for additional security?

Otherwise I don't have anything against it per se, but we might at some point hit some limitations through CircleCI for free tier build time but we ar not there yet.

If CONFIG_USER_USB_KEYBOARD=y is set a build time can it be disabled by the user later? That might be the best of both worlds and yeah maybe sometime add a warning somewhere that it has been enabled.

As said in prior comment, the idea here was to have users use ps2 when supported (or on-board keyboards for laptops) to enable us keyboard once per options config override or at build time (board config), letting the default be safer (ps2 safer then us for keyboards in regard of rubber ducky).

I would like to read a good justification to change this first, from a real use case that would justify usb keyboard when ps2 is available from motherboard connector @Hexdigest123 ? Why do you prefer usb to ps2?

Hexdigest123 · 2025-09-19T20:29:35Z

E> > > @tlaurion re discussion above, would you like me to create usb keyboard variants? That would double the number of board configs though.

I am not sure about this. People coming to Heads, having a board that permits ps2 keyboard but deciding to use USB? USB hid being a security risk, is there anything justifying usage of USB keyboard vs ps2?
If so, what about we enable it in config by default, and warn the user to deactivate it through config for additional security?
Otherwise I don't have anything against it per se, but we might at some point hit some limitations through CircleCI for free tier build time but we ar not there yet.

If CONFIG_USER_USB_KEYBOARD=y is set a build time can it be disabled by the user later? That might be the best of both worlds and yeah maybe sometime add a warning somewhere that it has been enabled.

As said in prior comment, the idea here was to have users use ps2 when supported (or on-board keyboards for laptops) to enable us keyboard once per options config override or at build time (board config), letting the default be safer (ps2 safer then us for keyboards in regard of rubber ducky).

I would like to read a good justification to change this first, from a real use case that would justify usb keyboard when ps2 is available from motherboard connector @Hexdigest123 ? Why do you prefer usb to ps2?

I think USB support from the pre-built images isn't strictly necessary, but I prefer it because I'm not going to buy a PS/2 keyboard just to use my USB keyboard. Having the option to turn it on and build it myself is fine with me. I'm just glad someone did the heavy lifting of upgrading Heads to the newest version, and a big thanks again.

I'm in the process of flashing the ROM onto my board and will give you an update.

Hexdigest123 · 2025-09-19T20:59:56Z

Before i switch over to the firmware for more then just a few tests does it have the new microcode for 14th Gen Intel CPU's so its not getting fried?

Hexdigest123 · 2025-09-19T21:14:15Z

I switched my firmware, and from what I can tell, the startup works just fine. However, I'll need a PS/2 keyboard, which I'll buy tomorrow, since the "CONFIG_REQUIRE_USB_KEYBOARD=y" flag didn't work for some reason.

I'll be back for the full test.

tlaurion · 2025-09-19T22:39:56Z

I switched my firmware, and from what I can tell, the startup works just fine. However, I'll need a PS/2 keyboard, which I'll buy tomorrow, since the "CONFIG_REQUIRE_USB_KEYBOARD=y" flag didn't work for some reason.

I'll be back for the full test.

The PR that made things configurable, usb hid module included by default, while not loaded unless configured by user was #1838

Init:
https://github.com/linuxboot/heads/blob/master/initrd%2Finit#L189

Calling enable _usb from etc/functions :
https://github.com/linuxboot/heads/blob/master/initrd%2Fetc%2Ffunctions#L387

So either
export CONFIG_USB_KEYBOARD_REQUIRED=y

Or

export CONFIG_USER_USB_KEYBOARD=y

In board config should work @Hexdigest123. If exported variables in board config don't match what code expects, the driver won't be loaded by enable_usb and usb hid won't be there so usb keyboard won't work.

Edit: Export requirements missing under https://github.com/linuxboot/heads/blob/master/doc/config.md

Hexdigest123 · 2025-09-20T18:09:48Z

Hi, I just tried out your fork. It seems I'm doing something wrong because it's not working at all (basic setup, booting into an OS). Here is some output that might help.

I tried the following:

Reset TPM
OEM Ownership
Add PGP Key via the interface
Reflashed HEADS again
Reset HOTP, TOTP

Tonux599 · 2025-09-20T18:25:43Z

@Hexdigest123 what TPM module are you using?

Tonux599 · 2025-09-20T18:29:01Z

Looks like Dasharo literally just released new versions for the MSI boards, so will update sometime.
https://docs.dasharo.com/variants/msi_z690/releases/#v115-2025-09-18
https://docs.dasharo.com/variants/msi_z790/releases/#v093-2025-09-18
non-LTS so may not be as stable though.

Both based on coreboot 24.12.

As general advice, use make coreboot helpers to save in defconfig format, remove config lines there that should not be overriden, and then use helper to save back in oldconfig format.

@Tonux599 do you plan on bumping coreboot version soon? Mostly all boards but NV4x seem to have been bumped, which heads share for buildstack for most boards.

Maybe. Added it to a TODO on first post. Will do some testing on my custom branch first, but might leave it to the future as currently this PR has about 2 months of stability testing going for it.

Tonux599 · 2025-09-20T18:30:56Z

Before i switch over to the firmware for more then just a few tests does it have the new microcode for 14th Gen Intel CPU's so its not getting fried?

It uses whatever is here https://github.com/Dasharo/dasharo-blobs/tree/main/msi

Of-course, your OS may update it anyway on boot.

Hexdigest123 · 2025-09-20T18:34:54Z

@Hexdigest123 what TPM module are you using?

I bought this mainboard and I'm not sure, but I believe it should have a TPM 2.0 MSI MS-4462 (9672) module.
https://shop.3mdeb.com/product/msi-pro-z790-p-wifi-ddr5-motherboard-with-dasharo-pro-package/

Tonux599 · 2025-09-20T18:39:50Z

@Hexdigest123 what TPM module are you using?

I bought this mainboard and I'm not sure, but I believe it should have a TPM 2.0 MSI MS-4462 (9672) module. https://shop.3mdeb.com/product/msi-pro-z790-p-wifi-ddr5-motherboard-with-dasharo-pro-package/

I can't see on that product page that it ships with a TPM installed? Where you using Dasharo's Heads before and was it working? Can you check to see if the TPM is installed to the motherboard?

The errors in your screenshot show that the TPM can't be found by the kernel. So either it's not installed, or something else is wrong that is hiding it.

Hexdigest123 · 2025-09-20T18:48:11Z

@Hexdigest123 what TPM module are you using?

I bought this mainboard and I'm not sure, but I believe it should have a TPM 2.0 MSI MS-4462 (9672) module. https://shop.3mdeb.com/product/msi-pro-z790-p-wifi-ddr5-motherboard-with-dasharo-pro-package/

I can't see on that product page that it ships with a TPM installed? Where you using Dasharo's Heads before and was it working? Can you check to see if the TPM is installed to the motherboard?

The errors in your screenshot show that the TPM can't be found by the kernel. So either it's not installed, or something else is wrong that is hiding it.

I haven't used Heads before. I used Coreboot with UEFI before, and that might actually be the problem. To be honest, I didn't expect someone to figure out the newest version. Do I need to buy and install the new TPM onto the board?

Tonux599 · 2025-09-20T18:52:42Z

I can't see on that product page that it ships with a TPM installed? Where you using Dasharo's Heads before and was it working? Can you check to see if the TPM is installed to the motherboard?
The errors in your screenshot show that the TPM can't be found by the kernel. So either it's not installed, or something else is wrong that is hiding it.

I haven't used Heads before. I used Coreboot with UEFI before, and that might actually be the problem. To be honest, I didn't expect someone to figure out the newest version. Do I need to buy and solder the new TPM onto the board?

Ah right. You'll need the "MS-4462" TPM module for TOTP to work and for the boot to be measured. You don't need to solder it, there is a header on the board.

Maybe just double check to see if one is installed and there isn't something else going on here.

Hexdigest123 · 2025-09-20T18:56:52Z

I can't see on that product page that it ships with a TPM installed? Where you using Dasharo's Heads before and was it working? Can you check to see if the TPM is installed to the motherboard?
The errors in your screenshot show that the TPM can't be found by the kernel. So either it's not installed, or something else is wrong that is hiding it.

I haven't used Heads before. I used Coreboot with UEFI before, and that might actually be the problem. To be honest, I didn't expect someone to figure out the newest version. Do I need to buy and solder the new TPM onto the board?

Ah right. You'll need the "MS-4462" TPM module for TOTP to work and for the boot to be measured. You don't need to solder it, there is a header on the board.

Maybe just double check to see if one is installed and there isn't something else going on here.

I checked it and no there is non sry for wasting your time im gonna order it real quick but from my last experience it may take some time like a few days maximum a week though everything else you made seemed to work

Hexdigest123 · 2025-09-20T19:34:24Z

Before i switch over to the firmware for more then just a few tests does it have the new microcode for 14th Gen Intel CPU's so its not getting fried?

It uses whatever is here https://github.com/Dasharo/dasharo-blobs/tree/main/msi

Of-course, your OS may update it anyway on boot.

The problem I addressed was the degradation issue in the Raptor Lake (13th/14th gen) CPUs from Intel. Someone mentioned that Heads didn't include the necessary microcode, and from what I've seen in the blobs, there is a patch, "0x12" that contains some updates but not for my CPU, at least from what I've been able to find online.

Hexdigest123 · 2025-09-24T15:58:54Z

Hi, so i tried it with the TPM Module installed and everything works fine i resetted the tpm and chose what to boot my OS also works fine as far as i am aware.

Tonux599 · 2025-09-25T21:08:11Z

Looks like Dasharo literally just released new versions for the MSI boards, so will update sometime.
https://docs.dasharo.com/variants/msi_z690/releases/#v115-2025-09-18
https://docs.dasharo.com/variants/msi_z790/releases/#v093-2025-09-18
non-LTS so may not be as stable though.

Both based on coreboot 24.12.
As general advice, use make coreboot helpers to save in defconfig format, remove config lines there that should not be overriden, and then use helper to save back in oldconfig format.
@Tonux599 do you plan on bumping coreboot version soon? Mostly all boards but NV4x seem to have been bumped, which heads share for buildstack for most boards.

Maybe. Added it to a TODO on first post. Will do some testing on my custom branch first, but might leave it to the future as currently this PR has about 2 months of stability testing going for it.

Testing this now, v0.9.3 seems to be running well without issue. Will update this PR soon-ish.

Signed-off-by: Thomas Clarke <[email protected]>

Tonux599 · 2025-09-26T23:08:38Z

Artefacts for v1.1.5 / v0.9.3.

Board	Artefacts
UNTESTED_msi_z690a_ddr4	https://app.circleci.com/pipelines/github/Tonux599/heads/148/workflows/3a1a294b-3463-411e-9a66-80749393393c/jobs/1757/artifacts
UNTESTED_msi_z690a_ddr5	https://app.circleci.com/pipelines/github/Tonux599/heads/148/workflows/3a1a294b-3463-411e-9a66-80749393393c/jobs/1758/artifacts
UNTESTED_msi_z790p_ddr4	https://app.circleci.com/pipelines/github/Tonux599/heads/148/workflows/3a1a294b-3463-411e-9a66-80749393393c/jobs/1759/artifacts
msi_z790p_ddr5	https://app.circleci.com/pipelines/github/Tonux599/heads/148/workflows/3a1a294b-3463-411e-9a66-80749393393c/jobs/1774/artifacts

miczyg1 and others added 8 commits August 25, 2025 23:24

Add MSI PRO Z690-A DDR4 target

b88c453

Signed-off-by: Michał Żygowski <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Add MSI PRO Z690-A (DDR5) target

8499f8b

Signed-off-by: Michał Żygowski <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Add MSI PRO Z790-P DDR4 target

80b28f2

Signed-off-by: Michał Żygowski <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Add MSI PRO Z790-P (DDR5) target

4977d10

Signed-off-by: Michał Żygowski <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

initrd/bin/cbfs-init: workaround for >16MiB flash

4125177

Signed-off-by: Michał Kopeć <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

boards/msi*: use w/a for >16MiB flash

bf9708f

Signed-off-by: Michał Kopeć <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

initrd/bin/cbfs-init: add error check for flashrom command

9be0ce3

Signed-off-by: Michał Kopeć <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

MSI Z690 / Z790 - Enable PROC_SYSCTL support for Heads init script.

13e832a

Signed-off-by: Matthew Drobnak <[email protected]> Signed-off-by: Thomas Clarke <[email protected]>

Tonux599 mentioned this pull request Aug 27, 2025

3mdeb/Dasharo has discontinued Heads on MSI desktops, time to upstream? #1960

Open

Tonux599 added 13 commits August 27, 2025 23:43

msi: add dasharo MSI release fork in coreboot module

f83092e

Signed-off-by: Thomas Clarke <[email protected]>

msi: use dasharo_msi coreboot version

2d5cf61

Signed-off-by: Thomas Clarke <[email protected]>

msi: disable dropbear, hotp, and usb keyboard

a920cc8

Signed-off-by: Thomas Clarke <[email protected]>

msi: enable PS/2 keyboard in coreboot config

70bcddd

Signed-off-by: Thomas Clarke <[email protected]>

msi: add vm.panic_on_oom=1 to linux cmd line

3036467

Signed-off-by: Thomas Clarke <[email protected]>

msi: disable bootsplash

6643d96

Signed-off-by: Thomas Clarke <[email protected]>

msi: use flashprog not flashrom

3965485

Signed-off-by: Thomas Clarke <[email protected]>

msi: use flashprog on initrd/bin/cbfs-init

10be901

Signed-off-by: Thomas Clarke <[email protected]>

msi: make olddefconfig on coreboot configs

f3ad8c2

Signed-off-by: Thomas Clarke <[email protected]>

msi: make olddefconfig on linux config

0f93d67

Signed-off-by: Thomas Clarke <[email protected]>

CircleCI: add MSI boards

0bfbccb

Signed-off-by: Thomas Clarke <[email protected]>

msi: mark untested boards

94fa9c5

Signed-off-by: Thomas Clarke <[email protected]>

BOARDS_AND_TESTERS.md: add MSI boards

7546d7b

Signed-off-by: Thomas Clarke <[email protected]>

Tonux599 force-pushed the msi-dasharo-upstream branch from 9cdd697 to 7546d7b Compare August 27, 2025 23:03

Tonux599 marked this pull request as ready for review August 28, 2025 12:54

tlaurion reviewed Aug 28, 2025

View reviewed changes

BOARDS_AND_TESTERS.md Show resolved Hide resolved

tlaurion requested changes Aug 28, 2025

View reviewed changes

msi: CONFIG_REQUIRE_USB_KEYBOARD=n not CONFIG_USB_KEYBOARD=n

1a0b584

Signed-off-by: Thomas Clarke <[email protected]>

Tonux599 added 2 commits September 26, 2025 22:34

msi: bump to v1.1.5 / v0.9.3

7493d8d

Signed-off-by: Thomas Clarke <[email protected]>

msi: update coreboot configs for v1.1.5 / v0.9.3

0c2656d

Signed-off-by: Thomas Clarke <[email protected]>

Uh oh!

Msi dasharo upstream #1995

Are you sure you want to change the base?

Msi dasharo upstream #1995

Uh oh!

Conversation

Tonux599 commented Aug 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Tonux599 commented Aug 28, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Tonux599 Aug 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tlaurion Sep 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

tlaurion left a comment

Choose a reason for hiding this comment

Uh oh!

aphick commented Sep 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Hexdigest123 commented Sep 18, 2025

Uh oh!

Tonux599 commented Sep 18, 2025

Uh oh!

Tonux599 commented Sep 18, 2025

Uh oh!

Hexdigest123 commented Sep 18, 2025

Uh oh!

tlaurion commented Sep 18, 2025

Uh oh!

Tonux599 commented Sep 18, 2025

Uh oh!

Tonux599 commented Sep 18, 2025

Uh oh!

tlaurion commented Sep 18, 2025

Uh oh!

tlaurion commented Sep 18, 2025

Uh oh!

tlaurion commented Sep 19, 2025

Uh oh!

tlaurion commented Sep 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Hexdigest123 commented Sep 19, 2025

Uh oh!

Hexdigest123 commented Sep 19, 2025

Uh oh!

Hexdigest123 commented Sep 19, 2025

Uh oh!

tlaurion commented Sep 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Hexdigest123 commented Sep 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Tonux599 commented Sep 20, 2025

Uh oh!

Tonux599 commented Sep 20, 2025

Tonux599 commented Aug 27, 2025 •

edited

Loading

Tonux599 Aug 28, 2025 •

edited

Loading

tlaurion Sep 4, 2025 •

edited

Loading

aphick commented Sep 17, 2025 •

edited

Loading

tlaurion commented Sep 19, 2025 •

edited

Loading

tlaurion commented Sep 19, 2025 •

edited

Loading

Hexdigest123 commented Sep 20, 2025 •

edited

Loading

Hexdigest123 commented Sep 20, 2025 •

edited

Loading