Hi Christian,
Both Keith Hei and I [Branden] have 440BX boards that still run
up-to-date/recent coreboot (though they do need a bit of work).
I also have an Intel 440LX board [Trigem Florida-TG (COGNAC)] that I
was intending on trying to get coreboot to run on yet, but I wanted to
get it reworked
Hi Keith
So far I've only tested the complete patch train (73888) like
previously mentioned and didn't have my serial console set up at the
time.
I dug out the cable from behind my desk and got it run to my work
bench again, so that should help out.
I'm assuming you would want logs with raminit
> Dear coreboot community,
> I just started coreboot and getting the hang of it. I am considering getting
> a M1 MacBook for my
> development work.
> May I will will coreboot work well on M1 MacBook? I am doing the coreboot
> work for x86
> platforms.
> I understand that coreboot is using i386 cr
With https://review.coreboot.org/c/coreboot/+/58387 merged, my p2b
board hangs at seabios.
I've attached serial logs from a rom of this commit and the previous one.
Branden
coreboot-4.15-1377-g7261b5ade5 Sat Feb 5 07:56:48 UTC 2022 bootblock starting (log level: 7)...
FMAP: Found "FLASH" versio
Hi
> I have to calmly tell it "laptop=this is not a laptop" and then it works as
> usual. I don't remember
> ever having to do this before. Why? If I have a clue I can code up and submit
> a patch.
If I recall correctly both my p2b and p2-99 boards do that while
running vendor firmware, though
uding microcode updates for now. I'm hoping the LTO and romstage
sources inside the bootblock will make in it yet, since they both
saved s[pace.
I only attached a specific portion of the log, since it got rather
long with spew set.
Branden Waldner
Initializing devices...
CPU_CLUSTER:
P2B. I'm working on recovering it
and I was planning on trying a build with log level spew on the P2-99
since it is easy for me to recover with the way I have it setup right
now.
Branden Waldner
___
coreboot mailing list -- coreboot@coreboot.org
m in the legacy ASEG (0xa -
> 0xb) region. A
> POC showed that it's not that hard to do with PARALLEL_MP
> https://review.coreboot.org/c/coreboot/+/58700
I didn't even know that was a problem until now. I doubt there is much
I can do about it myself at this point in time
> /bin/sh: 1: python: not found
> make[2]: *** [Makefile:168: out/romlayout16.lds] Error 127
I ran in to this error the other day in a clean build environment and
was going to mention it in the thread about python in the build
system, but Peter Surge already commented here on it.
If you are on Ub
A bit of a follow up, I verified it happens in a 32 bit (i686) Debian
sid chroot and not in 32 bit Debian Bullseye (actual install on
hardware).
Should I be properly reporting this on the issue tracker?
I don't have an account on the coreboot redmine tracker, though I
probably should make one.
I c
I've been working on testing current coreboot on my asus/p2b and
asus/p2-99 for the upcoming release, but ran in to problems trying to
build it on my p2b with Gentoo with gcc 11.2.0. It (ironically) did
build and work on the p2-99 with Debian Buster (oldstable) with gcc
8.3.0. It also built on my m
I was just checking the mailing list archive and noticed that it isn't
showing any new messages since September 9.
I wasn't able to determine if there was a mailing list admin address
to send this to, so I hope just sending it to the list is okay. (I did
see this "mail...@coreboot.org alias for ma
> Hi Branden,
>
>VultureProg was mentioned - even a DIY emulator would be fairly
>straightforward; that's a nice microcontroller project.
>
>
>That seems a bit overkill, but then again flash chips seem to be more
>expensive then microcontrollers these days. I don't think I'm
On 6/7/21, Rao G wrote:
> Please look into this document too about Disk On Chip
> https://www.coreboot.org/images/9/97/LinuxBIOS.pdf
>
I'll check it out yet.
>> Branden wrote...
>>
>> In the first place, I think my assumption of it exposing a large rom
>> was wrong, it looks like they only
Well, I'm finally getting around to writing this, though I'm still not
all that comfortable bringing it up.
I purchased a diskonchip 2000 266mb a while ago just to mess around
with. It took a long time in shipping though and then it took me a
while to actually try to test it out. I had thought I c
>> I haven't had much luck in finding options for recovery. Ideally I'd
>> like something like the dual switched bios in the old wiki but
>> toggle-able electronically ie. gpio pin from spare router w/ Openwrt.
>
>That's the product BIOS Savior RD1 from Taiwanese IOSS, switched by a
>jumper which c
On 6/1/21, Angel Pons wrote:
> Hi Branden, list,
>
> On Tue, Jun 1, 2021 at 2:10 AM Branden Waldner wrote:
>>
>> The LTO patches seem to both compile and work/boot for me on the p2b.
>>
>> I built it both on a debian sid x86_64 system and on the gentoo i686
>
The LTO patches seem to both compile and work/boot for me on the p2b.
I built it both on a debian sid x86_64 system and on the gentoo i686
setup I currently have for the p2b, both with the coreboot
crossgcc-i386 toolchain.
It looks like it uses the system linker though (or something similiar,
I d
On 5/25/21, Paul Menzel wrote:
> Dear Branden,
>
>
> Am 22.05.21 um 20:03 schrieb Branden Waldner:
>> On 5/21/21, Arthur Heymans wrote:
>
>>> Thanks for sharing your findings. The flash is 256K big, which is quite
>>> small these days.
>>> When bui
y 21, 2021 at 7:08 AM Paul Menzel wrote:
>
>> Dear Branden,
>>
>>
>> Am 21.05.21 um 05:36 schrieb Branden Waldner:
>> > When testing the latest coreboot code before the 4.14 release, I found
>> > I couldn't build a working image with the default (or
When testing the latest coreboot code before the 4.14 release, I found
I couldn't build a working image with the default (or what I usually
use) config for the asus/p2b. I figured out that it failed to build
with an error of not enough space in cbfs after the merge to enable
bootblock console for i
Well, this seems to be really going off topic. My only intention was
to ask what the required/recommended host(system) compiler was and
what documentation there was for that.
Branden Waldner wrote:
> Is there an expected minimal system gcc version and if so, is it
> documented? I couldn&
I recently looked in to why I couldn't build coreboot on one of my
systems any longer and I think I found the cause.
It looks like vboot uses features not available in gcc 6 on Debian Stretch.
I actually did manage to get it to build and work by commenting out
the offending gcc warning flags and
I tested Nico's method for you with a Debian bios install, but it
might be different for the Manjaro live usb.
To stall grub from booting, you can press the left arrow key
repeatedly, assuming that doesn't mess with tianocore loading first.
Then you press e to edit the boot parameters. For my debi
On 9/21/19, Nico Huber wrote:
>
> If nobody resurrects these changes, can you please squash the
> commits? If you remove the Change-Id from the commit message,
> a new should be generated and you could push it to Gerrit as
> a new change.
>
I managed to squash the commits and resubmit the change,
I have tested coreboot on both the asus/p2b and asus/p2-99 and it
seems to work fine. I had previously commented on the mailing list
instead of these patches and then never really followed up on it.
I meant to retest and comment on the change sets on gerrit (22977 and
22965) before they got abando
I believe the recommendation is to start with one of the boards
closest to what you have (ie. one of the boards with the same
northbridge, southbridge, and superio), try to figure out any
adjustments you can tell it needs and test and debug.
The northbridge is part of the cpu and depends on which
I got an actual p2b motherboard a few months ago so that I could
actually test it properly and not just claim the p2b build works on
the p2-99. It seems to work fine and flashrom works on the p2b (but
not the p2-99).
I believe there was some discussion and a patch to setup the p2-99 as
a variant o
>> git bundles available over resumable http(s) can help a lot with that,
>> but they are almost never provided.
>I think this is a fair enough request, and maybe quite straightforward
>to arrange. Do you already have some scripts to create a bundle every
>now and then, that you could contribute?
Not everyone has access to decent reliable internet and git is pretty
much useless if it gets interrupted. I would prefer to be able to
clone the source code[1] without the documentation without having to
resort to some weird git commands to get it done. Of course, having
git bundles available over
Hello,
If I'm understanding this correctly, you are unable to get
Coreboot/TianoCore to correctly load/boot efi grub2 (on disk). If this
isn't working your not even able to get to chainloading Clover.
(Unless grub2 is working, but booting Ubuntu isn't?).
You could either try to get your Coreboot/
Hi Paul,
My intention in uploading again to the board status repository was to
do to it with the patches Keith made merged. It's failed though as
make clean and make distclean didn't seem to clean up the old
(external?) acpi code like when I first tested the patch for Keith
(The kernel log shows a
While testing the 22687 change set, I ended up having the board fail
to boot after rebooting.
After getting the logs organized I figured I check it out with a clean
rom and sure enough, after rebooting from the grub prompt six times
with ctl+alt+del, it ended up failing to boot.
It looks to alway
Alright, I've finally got a follow up with the raminit logs and bx
configuration dumps. Hopefully you'll find something interesting or
useful in there. As expected, I had to use serial capture for the
raminit logs, since the default cbmem size isn't large enough.
I didn't get any logs from it comp
I tried the acpi patches again, and this time it worked properly. I
don't know if I had just missed running make clean, ended up flashing
the wrong rom with aflash, or messed something else up.
As for flashrom, I'd posted logs from my attempts at running it on its
mailing list
[32m[0.00]
I'm not sure that I'm setting up the acpi patches correctly then. I
had just ran:
git fetch https://review.coreboot.org/coreboot refs/changes/73/22473/1
&& git checkout FETCH_HEAD
originally. I think I had run make clean as well.
I tried doing:
git fetch https://review.coreboot.org/coreboot refs/c
Keith, I've attached the dmesg from running a build with the acpi
patch you had me listed as a reviewer on -
https://review.coreboot.org/#/c/22473/
It's still throwing acpi errors. Is having color codes in the log
okay? I can avoid them in the future if it's a bother.
Also, I wouldn't really cons
I managed to get the board status uploaded earlier today.
CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME was set to P2-99, other then
that, it shows up as just a P2B.
I guess I need to look in to figuring out how to get flashrom to work
properly. I could check that the floppy, second serial port, and
paral
I did manage to get a clean build that board_status wouldn't complain
about being dirty. The problem was I couldn't clone board_status
properly, have a crappy isp. I can probably clone it from some where
else tommorrow, or else I'll have to wait a week.
After using git clean I was able to actually
In reply to Keith.
Probably won't show up as a reply since I wasn't subscribed to the
list. I am now though, so it should work out now. I also had to
rewrite this, since gmail didn't like noscript refreshing the page
when I enabled javascript from google to register on gerrit.
My config was actual
Hi all,
I wasn't planning on posting unless I could actually contribute
something, but since Keith Hui posted last month about his work on
CBMEM for 440BX and ACPI, I figured I should do some proper testing
and at least post if it worked out.
I'm running coreboot on a ASUS P2-99 board with the co
41 matches
Mail list logo
