My guess is that maybe you've configured this repo incorrectly. After
logging in to review coreboot org , go to
https://review.coreboot.org/admin/repos/board-status and copy a HTTP
command for cloning, like " git clone
"https://mikebdp@review.coreboot.org/a/board-status" && (cd
"board-status" && mkdir -p .git/hooks && curl -Lo `git rev-parse
--git-dir`/hooks/commit-msg
https://mikebdp@review.coreboot.org/tools/hooks/commit-msg; chmod +x
`git rev-parse --git-dir`/hooks/commit-msg) " , with mikebdp replaced
by your username there (but better to copy it from HTTP tab to avoid
accidental mistakes). Then copy the files you would like to commit to
this repository, commit and push, and it should only ask your
password, without a username.
On Sun, Dec 8, 2019 at 11:37 AM Mike Banon <mikebdp2(a)gmail.com> wrote:
>
> My guess is that maybe you've configured this repo incorrectly. After
> logging in to review coreboot org , go to
> https://review.coreboot.org/admin/repos/board-status and copy a HTTP
> command for cloning, like " git clone
> "https://mikebdp@review.coreboot.org/a/board-status" && (cd
> "board-status" && mkdir -p .git/hooks && curl -Lo `git rev-parse
> --git-dir`/hooks/commit-msg
> https://mikebdp@review.coreboot.org/tools/hooks/commit-msg; chmod +x
> `git rev-parse --git-dir`/hooks/commit-msg) " , with mikebdp replaced
> by your username there (but better to copy it from HTTP tab to avoid
> accidental mistakes). Then copy the files you would like to commit to
> this repository, commit and push, and it should only ask your
> password, without a username.
>
> On Wed, Dec 4, 2019 at 5:17 PM Jorge Fernandez Monteagudo
> <jorgefm(a)cirsa.com> wrote:
> >
> > Hi all,
> >
> > I've generated a new entry in util/board_status/board-status/amd/bettong/4.10-6-g12ec481/2019-12-04T13_27_01Z/
> > but I'm not able to push the changes.
> >
> > I'm able to entry in to https://review.coreboot.org/settings/ and I can see my HTTP credentials with my github user name
> > and I've generated a new password pushing the button but then I try to do a push and always get:
> >
> > $ cd util/board_status/board-status
> > $ git push
> > Username for 'https://review.coreboot.org': jorgefm1900
> > Password for 'https://jorgefm1900@review.coreboot.org':
> > fatal: Authentication failed for 'https://review.coreboot.org/board-status.git/'
> >
> > Any resource to configure a review.coreboot.org repo user? I've tried to change the password through Github creating a
> > personal access token without luck...
> >
> > Thanks!
> > _______________________________________________
> > coreboot mailing list -- coreboot(a)coreboot.org
> > To unsubscribe send an email to coreboot-leave(a)coreboot.org
Hi,
In the spirit of board report coverage, I pulled out the (used, but new to
me) AM1I-A I have and spent a day or two trying to install the latest
coreboot on it.
The board boots fine under the stock bios, and returns to working order if
flashed with my backup, but shows little signs of life with coreboot.
Along the way I extracted and included the vgabios rom, as well as tried
with a nivida card, so I'm pretty sure that's not it.
I tried having it save the console output to flash, but that made the build
fail. [1]
Yesterday evening I noticed it was configured by default to use open-source
init (and for some reason the build finishes without error), but as far as
I know that doesn't exist for family 16h. Switching to BinaryPI causes the
build to fail. [2] 3rd party blobs are cloned and enabled.
I'm running an Athlon 5250, or something of that nature, with a couple of
gigs of ram on one dimm. My current .config is [3].
Sincerely,
-Matt
[1] https://pastebin.com/FZEiCq8P
[2] https://pastebin.com/Q30u7Lgs
[3] https://pastebin.com/ufuq22i8
Hi,
I know a couple folks here are active on Thinkpads.com / familiar with the
X210 port by Matthew.
The stock BIOS doesn't appear to support non-NVME devices in the M.2 slot;
I'm attempting to get a Sunix UPD2018 card working to add USB-C.
With stock BIOS, the card works just fine in the WiFi slot, and an NVME
drive works just fine in the M.2 slot so nothing appears physically broken.
However, so far nothing I've done lets me detect the Sunix card if I try to
put it in the NVME slot using this adapter
<https://www.adt.link/product/R42.html>. I would think it should just show
up under "lspci" like it does in the WiFi slot, but it does not.
I have not tried the latest Coreboot / port yet, but I figured I might as
well get some opinions on the subject.
What do you guys think, can this be done with Coreboot?
Cheers,
Rafael
Hi
Regarding the deprecation of AGESA platforms due to ROMCC_BOOTBLOCK.
As of 3rd December there is active development, while not much testing
yet, only for the following AGESA platform boards:
* asrock/imb-a180
* lenovo/g505s
* pcengines/apu1
Developers will help people who have these platforms to bring their
board sources to current standards. The process begins by uploading a
fresh board-status result for the board you volunteer to work on and
announce this by replying to this thread.
Using one of the above boards as a sample, it might not take more than
30 minutes and two boots to make the required transition. But first we
need to have the above boards working of course.
Our board-status repository has some previous results for the boards
listed below, and we need your assistance to keep these boards in:
* amd/olivehill
* amd/persimmon
* amd/thatcher
* asrock/e350m1
* asus/am1i-a
* asus/f2a85-m
* biostar/am1ml
* gizmosphere/gizmo
* hp/pavilion_m6_1035dx
* jetway/nf81-t56n-lf
* lippert/frontrunner-af
* msi/ms7721
Same offer and request of help as above applies to the following
boards, for which we have no previous board-status records:
* amd/inagua
* amd/parmer
* amd/south_station
* amd/union_station
* bap/ode_e20XX
* biostar/a68n_5200
* elmex/pcm205400
* gizmosphere/gizmo2
* hp/abm
* lippert/toucan-af
Any board with ROMCC_BOOTBLOCK will be disabled from automatic
build-testing by 14th December at latest, such that ROMCC_BOOTBLOCK
removal in common code can proceed. Boards that see no activity will
be removed from the tree 31st December 2019.
Once a board has its source removed, it will face the standard review
process should someone want to bring it back. Reincarnations until
next (4.12) release might not be accepted.
Kind regards,
Kyösti Mälkki
Hello folks
i sadly had to replace KGPE-d16 board for my fileserver to a Supermicro
A1SRi-C2558 because of electric pill ....
investigating a bit with intelmetool and mecleaner non of them could
found any sign for an ME-region in this board.. so i asking myself if
there is no ME/SPS on the intel C2000 socs, what would make them a DAMN
SEXY platform to port coreboot too.
Here my investigations:
root@lain:~# /speedy/foo/Downloads/coreboot/util/intelmetool/intelmetool
-m -d
ME PCI device is hidden
RCBA addr: 0xfed1c000
MEI was hidden on PCI, now unlocked
Re-hiding MEI device...done
Can't find ME PCI device
./me_cleaner/me_cleaner.py -c Supermicro_Firmware/A1SAi18_118/A1SAi18.118
Full image detected
The ME region in this image has already been disabled
The HAP bit is NOT SET
Checking the FTPR RSA signature... Traceback (most recent call last):
 File "./me_cleaner/me_cleaner.py", line 955, in <module>
   print_check_partition_signature(mef, ftpr_offset + ftpr_mn2_offset)
NameError: name 'mef' is not defined
 binwalk Supermicro_Firmware/A1SAi18_118/A1SAi18.118
DECIMALÂ Â Â Â Â Â HEXADECIMALÂ Â Â Â DESCRIPTION
--------------------------------------------------------------------------------
2097152Â Â Â Â Â Â 0x200000Â Â Â Â Â Â Â UEFI PI Firmware Volume, volume size:
131072, header size: 0, revision: 0, EFI Firmware File System v2, GUID:
8C8CE578-8A3D-4F1C-3599-896185C32DD3
2555904Â Â Â Â Â Â 0x270000Â Â Â Â Â Â Â UEFI PI Firmware Volume, volume size:
3932160, header size: 96, revision: 0, EFI Firmware File System v2,
GUID: 8C8CE578-8A3D-4F1C-3599-896185C32DD3
2629664Â Â Â Â Â Â 0x282020Â Â Â Â Â Â Â Microsoft executable, portable (PE)
4325602Â Â Â Â Â Â 0x4200E2Â Â Â Â Â Â Â Copyright string: "Copyright (C) %04x
American Megatrends, Inc. "
6488064Â Â Â Â Â Â 0x630000Â Â Â Â Â Â Â UEFI PI Firmware Volume, volume size:
262144, header size: 0, revision: 0, EFI Firmware File System v2, GUID:
8C8CE578-8A3D-4F1C-3599-896185C32DD3
6946816Â Â Â Â Â Â 0x6A0000Â Â Â Â Â Â Â UEFI PI Firmware Volume, volume size:
1441792, header size: 96, revision: 0, EFI Firmware File System v2,
GUID: 8C8CE578-8A3D-4F1C-3599-896185C32DD3
6947360Â Â Â Â Â Â 0x6A0220Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6971232Â Â Â Â Â Â 0x6A5F60Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6981408Â Â Â Â Â Â 0x6A8720Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6983616Â Â Â Â Â Â 0x6A8FC0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6985504Â Â Â Â Â Â 0x6A9720Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6986144Â Â Â Â Â Â 0x6A99A0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6988896Â Â Â Â Â Â 0x6AA460Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6991360Â Â Â Â Â Â 0x6AAE00Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6995264Â Â Â Â Â Â 0x6ABD40Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6997056Â Â Â Â Â Â 0x6AC440Â Â Â Â Â Â Â Microsoft executable, portable (PE)
6998816Â Â Â Â Â Â 0x6ACB20Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7000553Â Â Â Â Â Â 0x6AD1E9Â Â Â Â Â Â Â gzip compressed data, ASCII, has header
CRC, has original file name: "", last modified: 2104-12-22 18:41:23
(bogus date)
7001792Â Â Â Â Â Â 0x6AD6C0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7004576Â Â Â Â Â Â 0x6AE1A0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7152192Â Â Â Â Â Â 0x6D2240Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7156928Â Â Â Â Â Â 0x6D34C0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7164096Â Â Â Â Â Â 0x6D50C0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7171040Â Â Â Â Â Â 0x6D6BE0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7175872Â Â Â Â Â Â 0x6D7EC0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7177536Â Â Â Â Â Â 0x6D8540Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7178688Â Â Â Â Â Â 0x6D89C0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7182144Â Â Â Â Â Â 0x6D9740Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7188576Â Â Â Â Â Â 0x6DB060Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7203776Â Â Â Â Â Â 0x6DEBC0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7253696Â Â Â Â Â Â 0x6EAEC0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7263136Â Â Â Â Â Â 0x6ED3A0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7263871Â Â Â Â Â Â 0x6ED67FÂ Â Â Â Â Â Â mcrypt 2.2 encrypted data, algorithm:
blowfish-448, mode: CBC, keymode: 8bit
7270688Â Â Â Â Â Â 0x6EF120Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7272480Â Â Â Â Â Â 0x6EF820Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7279008Â Â Â Â Â Â 0x6F11A0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7304768Â Â Â Â Â Â 0x6F7640Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7307968Â Â Â Â Â Â 0x6F82C0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7313952Â Â Â Â Â Â 0x6F9A20Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7317152Â Â Â Â Â Â 0x6FA6A0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7318048Â Â Â Â Â Â 0x6FAA20Â Â Â Â Â Â Â Microsoft executable, portable (PE)
7322016Â Â Â Â Â Â 0x6FB9A0Â Â Â Â Â Â Â Microsoft executable, portable (PE)
8384152Â Â Â Â Â Â 0x7FEE98Â Â Â Â Â Â Â Microsoft executable, portable (PE)
Hi, I'm researching an article about funding drivers & firmware for linux on mainstream hardware. I'm a huge fan of coreboot/seabios & feel both excited for life after binary blobs and frustrated at how difficult it is to ship OSS firmware.
Looking for any and all feedback but tag in especially if you know about:
* what skill-sets the community needs to develop these without industry support
* $$ figures for driver development in-house at major shops
* are OSS firmware projects trying to support mainstream laptops on launch? are manufacturers interested?
Have had a series of linux laptops as my daily drivers for ~ 4 years -- am grateful for the work the community is doing.
Hi guys,
I finally have a chance to sit down and update my local coreboot repo.
To make sure it works I tried to build for asus/p2b-ls,p2b-d,p2b-ds...
my usual i440bx boards.
But my build is now failing. I'd get:
CREATE build/mainboard/asus/p2b-ls/cbfs-file.kMfK0Y.out (from
/usr/src/coreboot/.config)
make: *** [src/cpu/Makefile.inc:44: build/cpu_microcode_blob.bin] Error 1
That makefile line seems to indicate that some CPU microcode file is not there.
Just want ask somebody else to also try building for these boards and
confirm if it is just me, as some people have been able to boot test
some recent i440bx changes and one has to be able to build to be able
to test.
Thanks
Keith
Hi everyone,
I'm trying to port my P67 pro (as others but due to lack of time this
one at least) on coreboot.
Here is the repo I use for my tests:
https://github.com/skollrc/Asrock-P67-Pro-port .
I'm also trying to port GA-G33M-DS2R and H81M-ITX boards but the P67 Pro
is my priority. The DS2R board will require more time to be fully
functional and I don't have a heavy use of the ITX board.
Is there anyone interested in helping me to test or work on the port? I
have a newborn child and a time consumer job so I have not as much time
as I would like to finish the job...
best regard
Robin
Hello All:
I am using the default Tianocore stable (Mr. Chromebox Matt version?) but is taking:
2minutes 30seconds from the appearance of the logo to the Tiano menu / grub bootloader.
After entering the payload there is no more serial debug output.
Anyone had this issue and knows the fix.
Anyone of you know how to enable the serial debug output to Tiano.
Any help will be very much appreciated.
Thank you,
Jose Trujillo.
