Issue #451 has been reported by Felix Singer.
----------------------------------------
Bug #451: Fix POST code handling
https://ticket.coreboot.org/issues/451
* Author: Felix Singer
* Status: New
* Priority: Normal
* Target version: none
* Start date: 2023-01-29
----------------------------------------
coreboot supports writing POST codes to I/O port 80. There are various Kconfigs that deal with POST codes, which don’t have effect on most platforms. The code to send POST codes is scattered in C and Assembly, some use functions, some use macros and others simply use the `outb` instruction. The POST codes are duplicated between stages and aren’t documented properly.
## Tasks
* Guard Kconfigs with a depends on to only show on supported platforms
* Remove duplicated Kconfigs
* Replace `outb(0x80, ...)` with calls to `post_code(...)`
* Update Documentation/POSTCODES
* Use defines from console/post_codes.h where possible
* Drop duplicated POST codes
* Make use of all possible 255 values
## Requirements
* Knowledge in the coreboot build system and the concept of stages
* Other knowledge: Little experience with C and x86 Assembly
* Hardware requirements: Nothing special
## Mentors
* Patrick Rudolph patrick.rudolph(a)9elements.com
* Christian Walter christian.walter(a)9elements.com
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: https://ticket.coreboot.org/my/account
Issue #449 has been reported by Crazy Fox.
----------------------------------------
Bug #449: ThinkPad T440p fail to start, continous beeping & LED blinking
https://ticket.coreboot.org/issues/449
* Author: Crazy Fox
* Status: New
* Priority: Normal
* Category: coreboot common code
* Target version: 4.18
* Start date: 2023-01-14
* Affected versions: 4.18
* Affected hardware: haswell
----------------------------------------
Hi, Team
Being corebooted before and works fine on 4.17.
After flashing 4.18 my t440p wont startup (black screen, constant beeping & LED blinking). I've tried and retried different nconfigs but result is the same. I know that it is lack of information, but I need to recover the laptop first to grab some logs from it.
Log from FT232H's debug is attached, the rest of info (defconfig, flashrom command etc. will upload soon)
---Files--------------------------------
coreboot_t440p_emerg.log (7.85 KB)
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: https://ticket.coreboot.org/my/account
Hi,
I've been experimenting with Linux's coreboot framebuffer driver on a
google/gru (kevin) chromebook with stock firmware. I get these kernel
messages:
platform simple-framebuffer.0: failed to claim resource 0: [mem
0x00000000-0x00ea5fff]
coreboot: could not register framebuffer
framebuffer: probe of coreboot7 failed with error -16
When I tried to print the coreboot table struct in kernel I saw the
framebuffer physical address is 0. Browsing coreboot sources led me to a
"rockchip/rk3399: display: Do not allocate framebuffer in coreboot" [1]
commit, which says it's "dynamically chosen by libpayload now". I think
the coreboot tables should be updated after this, but aren't.
[1] https://review.coreboot.org/c/coreboot/+/17109/
I suspect `set_vbe_mode_info_valid(&edid, (uintptr_t)0);` is the point
of interest there, which is now `fb_new_framebuffer_info_from_edid`,
which is in a few more files:
$ git grep "fb_new_framebuffer_info_from_edid(.*0);"
src/mainboard/google/asurada/mainboard.c: ...
src/mainboard/google/cherry/mainboard.c: ...
src/mainboard/google/corsola/display.c: ...
src/mainboard/google/geralt/display.c: ...
src/mainboard/google/herobrine/mainboard.c: ...
src/mainboard/google/kukui/mainboard.c: ...
src/mainboard/google/oak/mainboard.c: ...
src/mainboard/google/trogdor/mainboard.c: ...
src/soc/rockchip/rk3399/display.c: ...
I don't quite know how to solve this, but was told to report it to the
mailing list.
Hello,
I checked the vendor section of the coreboot website which states that System76 sells desktops and laptops with Coreboot. While system76 does sell laptops with coreboot, I couldn't find any clear statement regarding their desktops on system76's website. I contacted them previous week to verify that info and it turns out their desktops do not include Coreboot. Here is part of the answer that was given to me by the sales team on 10th of January 2023:"
We have not yet ported Coreboot to any of our desktop models, they are all currently using proprietary motherboard vendor firmware."
So I would recommend deleting the reference to their desktops on coreboot's website as it's a bit misleading.
By the way, I couldn't find any company selling desktops with Coreboot preinstalled. At all. Crap, things have to change :) !
Cheers.
Julien Danglard
professeur de français
--
Tutanota respects your privacy and it's for free, try it ! https://tutanota.com
Issue #440 has been reported by J Nky.
----------------------------------------
Bug #440: superiotool tells you to run it as root and stops even when ran as root
https://ticket.coreboot.org/issues/440
* Author: J Nky
* Status: New
* Priority: Normal
* Target version: none
* Start date: 2022-11-24
* Affected versions: 4.15
* Affected OS: ubuntu 22.10
----------------------------------------
On ubuntu 22.10:
**sudo superiotool**
iopl: Function not implemented
Superiotool must be run as root.
superiotool tells you to run it as root and stops even when ran as root
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: https://ticket.coreboot.org/my/account
Dear coreboot folks,
A colleague made me aware of the presentation *The OSF on Supermicro's
platform* [1] by the Supermicro employees Hancock Chang and Simon Chou¹
at the OCP Global Summit 2022 this October. This is great news. I would
have loved to also read about this on the coreboot mailing list.
In the talk, the board Supermicro X12SPW is mentioned, and that it’s
planned for the X13 series. One of our suppliers responded though, that
systems with coreboot are currently not generally available, but it’s
something Supermicro offers to ODMs or for projects with large volumes.
The slide *Call to Action* contains:
> Come and collaborate with Supermicro
Collaboration would be great. A first step would be, if Supermicro
(engineers) would get in touch with the coreboot project/community on
the mailing list, and also upstreamed their work and contributed their
improvements. Judging from the presented times, there is still a lot of
potential to unlocked, and where the coreboot community already has a
lot of experience in to share to make sure, the Supermicro boards work
even better.
Kind regards,
Paul
PS: OpenBMC patches are already being sent upstream [2].
¹ Hopefully correct addresses in Cc. At least my test message did not
bounce.
[1]: https://www.youtube.com/watch?v=U_WO-_np9wQ
[2]:
https://lore.kernel.org/openbmc/20221229100155.2954455-1-ryans@supermicro.c…
Issue #450 has been reported by Felix Singer.
----------------------------------------
Bug #450: Port over wiki pages to the new documentation
https://ticket.coreboot.org/issues/450
* Author: Felix Singer
* Status: New
* Priority: Normal
* Target version: none
* Start date: 2023-01-20
----------------------------------------
The [old coreboot wiki](https://www.coreboot.org/Welcome_to_coreboot) is being retired and it's replaced by https://doc.coreboot.org created with Sphinx. There are several wiki pages which are still not ported over.
This ticket is meant as a tracking ticket. Please create a separate ticket for each wiki page which needs a port.
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: https://ticket.coreboot.org/my/account
Hi,
As folks may have gathered from my other question about the GCC build
environment, I've been playing around with the old X2100 port (
https://github.com/mjg59/coreboot/tree/x2100_ng).
I got it to build and added the latest version of MrChromebox's Tianocore,
but there's still one issue that keep is from being very useable.
After flashing / plugging in the machine, the power button will turn it on,
but only once. If I shut down any OS, or even if it goes to sleep or
suspends, the power button no longer has any effect so the only "fix" is
currently to unplug power and re-plug it.
Where might I look for causes of this? Is it a shutdown state thing? ACPI?
Thanks,
Rafael