Re: [coreboot] Schematics and PCB design for ASMB4 (Was: There are ASMB5's on fleabay right now for $30/ea (firmware storage module required for OpenBMC on the KGPE-D16/KCMA-D8))

[Andrew Luke Nesbit]

Dear Daniel,

Please see my comments inline...

On 03/11/2018 04:32, Daniel Gröber wrote:
> On Sat, Nov 03, 2018 at 12:10:25AM +0100, Angel Pons wrote:
>> Is it me, or is that thing a SPI flash chip on a PCB plus a few
>> transistors? It seems like copying the PCB design is rather doable, or am I
>> missing something?
> 
> Indeed, very doable, but tedious work ;)
> 
> Here you go:
> 
> https://github.com/DanielG/asmb4
> https://oshpark.com/shared_projects/jZLoDQ3Y

This is fantastic, thank you!!

I've been intending to do something very similar to this.  So far I have
spent most of 2018 on my career change -- thankfully this is now done,
and should be more benefectial in the long run.

Cloning these modules would be very liberating, based on my experiences
so far.  Thank you for your work.  Please keep me in the loop for future
developments.  Nevertheless, I'll continue to follow your work, and I
will be available to contribute financially if appropriate.

I have some ASMB4- and ASMB5-iKVM modules, on which I have been doing
OpenBMC experiments for the D16 and D8.  This is now music to my ears :-)

> I had the schematics lying around on paper for a while now but I was
> too lazy to digitize them until now. The design is completely
> untested, I just ordered some boards though so we'll see.

If there's any possibility that you might have one or two spare
prototypes or clones to send me for evaluation, please let me know :-)

I'm happy to cover costs, plus some extra money to contribute to further
development or your time and labor.  This is an important project and I
am prepared to put money on the table to help move it forward.

> FWIW if anyone is interrested in gettingd some assembled boards I might
> do a small production run.

Yes.  As I already mentioned, I can contribute financially to support
libre-friendly designs.  I am also keen to help to verify designs and
actual prototypes, conduct formal(?) methods for testing, and to help to
load these modules in UAT, STAGING, or PROD environments.

Kind regards,

Andrew
-- 
OpenPGP key: EB28 0338 28B7 19DA DAB0  B193 D21D 996E 883B E5B9

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] Schematics and PCB design for ASMB4 (Was: There are ASMB5's on fleabay right now for $30/ea (firmware storage module required for OpenBMC on the KGPE-D16/KCMA-D8))

[Daniel Gröber]

Hi,

On Sat, Nov 03, 2018 at 12:10:25AM +0100, Angel Pons wrote:
> Is it me, or is that thing a SPI flash chip on a PCB plus a few
> transistors? It seems like copying the PCB design is rather doable, or am I
> missing something?

Indeed, very doable, but tedious work ;)

Here you go:

https://github.com/DanielG/asmb4
https://oshpark.com/shared_projects/jZLoDQ3Y

I had the schematics lying around on paper for a while now but I was
too lazy to digitize them until now. The design is completely
untested, I just ordered some boards though so we'll see.

FWIW if anyone is interrested in getting some assembled boards I might
do a small production run.

--Daniel


signature.asc
Description: PGP signature
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Status Update of F2A85M

[Kinky Nekoboi]

i have tried it, microcode is now updated, but this does not help with
linux not wants to boot with iommu enabled


Am 02.11.2018 um 21:29 schrieb Mike Banon:
> For our Richland 15h family AMD CPUs (and for 16h also) , this
> microcode update procedure - accessible from coreboot's configuration
> "menuconfig" menu - is broken, I've observed this 0K problem too. You
> should leave this "Include CPU microcode in CBFS" option as "Do not
> include microcode updates" and just run a script from this wiki -
> http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
> - it will patch the AMD microcodes hardcoded inside .c source code
> files as the arrays of hex values. After you'll patch your coreboot,
> rebuild it and install to your motherboard, your microcode's patch
> level should change from 0x0600110f to 0x0600111f (0f->1f)
>
> Best regards,
> Mike Banon
> On Fri, Nov 2, 2018 at 10:51 PM kinky_nekoboi
>  wrote:
>> I tried only the one included in current master tree.
>>
>> But CBFS reports me an 0KB blob as an output ... so that its mostlikele
>> the reason it halts after boot (maybe updating an not working microcode
>> to the cpu than ?)
>>
>> i have microcodes enabled per linux kernel update
>> dmesg | grep microcode:
>> [3.794585] microcode: CPU0: patch_level=0x0600110f
>> [3.794588] microcode: CPU1: patch_level=0x0600110f
>> [3.794595] microcode: CPU2: patch_level=0x0600110f
>> [3.794602] microcode: CPU3: patch_level=0x0600110f
>> [3.794653] microcode: Microcode Update Driver: v2.2.
>>
>> Am 02.11.2018 um 17:12 schrieb Mike Banon:
>>> Which microcode gives you a brick? Have you tried those new 2018
>>> microcodes (not merged yet to coreboot) for 15h generation -
>>> https://review.coreboot.org/c/coreboot/+/28273 ? If not, here is a
>>> quick & secure way to get them -
>>> http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
>>> (although this script is at "Lenovo G505S hacking" page, the same
>>> microcodes should work for desktop Richland CPUs as well) . By the
>>> way, it could help you to get your hardware virtualization (IOMMU)
>>> working
>>> On Fri, Nov 2, 2018 at 7:06 PM kinky_nekoboi
>>>  wrote:
 Hi Mike, i hope i can help u i am just a User of coreboot and noo skilled 
 coreboot hacker yet lol.
 The A10-6800K should work as its the same CPU core/ gen.
 do not include microcode it makes the rom a brick mode.
 U have to add a VGA bios if u are using the Internal GPU.
 i am using a F2A85M rev 1.1 (not pro and not LE, they are quite rare)

 Am 2. November 2018 17:01:24 MEZ schrieb Mike Banon :
> Nice report. Do you think A10-6800K CPU would have worked at this
> motherboard? Or only A8-6600K is supported? Also, what hardware
> revision of this motherboard do you have? (there were F2A85M / --//--
> PRO and some other revisions, so I'm a bit confused) . I am seriously
> considering doing a similar build, but would like to get the fastest
> available CPU you could install there
> On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi
>  wrote:
>>  something like that happens if u connect anything to a USB2 Port
>>
>>  [ 2600.001601] usb 7-1: new full-speed USB device number 3 using 
>> ohci-pci
>>  [ 2600.001612] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2600.001619] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2600.001624] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2600.185864] usb 7-1: device descriptor read/64, error -11
>>  [ 2600.293659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2600.293669] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2600.293674] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2600.477668] usb 7-1: device descriptor read/64, error -11
>>  [ 2600.585647] usb usb7-port1: attempt power cycle
>>  [ 2601.090486] usb 7-1: new full-speed USB device number 4 using 
>> ohci-pci
>>  [ 2601.090494] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2601.301659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2601.509672] usb 7-1: device not accepting address 4, error -11
>>  [ 2601.693678] usb 7-1: new full-speed USB device number 5 using 
>> ohci-pci
>>  [ 2601.693693] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x0001c52c2ea8+8 of device mask 
>>  [ 2601.901677] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>> 0x00

Re: [coreboot] There are ASMB5's on fleabay right now for $30/ea (firmware storage module required for OpenBMC on the KGPE-D16/KCMA-D8)

[Angel Pons]

Hello,

Is it me, or is that thing a SPI flash chip on a PCB plus a few
transistors? It seems like copying the PCB design is rather doable, or am I
missing something?

Regards,

Angel Pons
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [LinuxBoot] FOSDEM 2019 deadline today

[Carl-Daniel Hailfinger]

In that case, I'd also like to point you to the deadline for submitting
main track talks which is tomorrow(!).
https://fosdem.org/2019/news/2018-08-10-call-for-participation/
Having a coreboot/LinuxBoot talk there would be awesome. Ron/David,
could you submit something or do you have someone in mind who can do that?

There's also lightning talks, deadline is a bit later.

OK, I'm submitting a request for a stand. I need a backup contact for
the stand. Who is willing to do that? AFAICS we can still change the
backup contact later if life happens.

Regards,
Carl-Daniel

On 02.11.2018 20:48, David Hendricks wrote:
>
>
> On Fri, Nov 2, 2018 at 9:15 AM 'Ron Minnich' via linuxboot
> mailto:linuxb...@googlegroups.com>> wrote:
>
> I"m leaning to yes, by which I mean if you do it, I'll show up.
>
> I can't believe I said that.
> On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger
>  > wrote:
> >
> > Hi!
> >
> > FOSDEM next year will be on 2 & 3 February 2019.
> > The deadline for applying for a stand is today.
> > Do we want a coreboot/flashrom/LinuxBoot stand/booth?
>
>
> Same as what Ron said. I think someone from FB can be there to talk
> about coreboot/LinuxBoot stuff and perhaps bring some hardware to demo.
>
>


-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] There are ASMB5's on fleabay right now for $30/ea (firmware storage module required for OpenBMC on the KGPE-D16/KCMA-D8)

[taii...@gmx.com]

(This is the firmware storage module required to use OpenBMC on the
KGPE-D16/KCMA-D8 boards - with it at last one can have feature
equivalency with a proprietary system)

Great opportunity if you need but don't have one - they appear to be
brand new.

Raptor says either the ASMB4 or the ASMB5 will work.

While the facebook version of OpenBMC is stripped down (they used that
one for smaller firmware size afaik) and not as nice as the IBM OpenBMC
found on the various OpenPOWER machines it is still secure and much
nicer than the exploit filled default BMC firmware from ASUS.

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [LinuxBoot] FOSDEM 2019 deadline today

[Ron Minnich via coreboot]

I"m leaning to yes, by which I mean if you do it, I'll show up.

I can't believe I said that.
On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger
 wrote:
>
> Hi!
>
> FOSDEM next year will be on 2 & 3 February 2019.
> The deadline for applying for a stand is today.
> Do we want a coreboot/flashrom/LinuxBoot stand/booth?
>
> There will be a hardware enablement devroom as well, and we might be
> able to participate there, but that's not necessarily giving us a chance
> to talk to people all day.
>
> Regards,
> Carl-Daniel
>
> --
> You received this message because you are subscribed to the Google Groups 
> "linuxboot" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to linuxboot+unsubscr...@googlegroups.com.
> To post to this group, send email to linuxb...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/linuxboot/c813b1b3-6f36-5e43-5f46-0bfd5afbd50b%40gmx.net.
> For more options, visit https://groups.google.com/d/optout.

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Status Update of F2A85M

[Mike Banon]

For our Richland 15h family AMD CPUs (and for 16h also) , this
microcode update procedure - accessible from coreboot's configuration
"menuconfig" menu - is broken, I've observed this 0K problem too. You
should leave this "Include CPU microcode in CBFS" option as "Do not
include microcode updates" and just run a script from this wiki -
http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
- it will patch the AMD microcodes hardcoded inside .c source code
files as the arrays of hex values. After you'll patch your coreboot,
rebuild it and install to your motherboard, your microcode's patch
level should change from 0x0600110f to 0x0600111f (0f->1f)

Best regards,
Mike Banon
On Fri, Nov 2, 2018 at 10:51 PM kinky_nekoboi
 wrote:
>
> I tried only the one included in current master tree.
>
> But CBFS reports me an 0KB blob as an output ... so that its mostlikele
> the reason it halts after boot (maybe updating an not working microcode
> to the cpu than ?)
>
> i have microcodes enabled per linux kernel update
> dmesg | grep microcode:
> [3.794585] microcode: CPU0: patch_level=0x0600110f
> [3.794588] microcode: CPU1: patch_level=0x0600110f
> [3.794595] microcode: CPU2: patch_level=0x0600110f
> [3.794602] microcode: CPU3: patch_level=0x0600110f
> [3.794653] microcode: Microcode Update Driver: v2.2.
>
> Am 02.11.2018 um 17:12 schrieb Mike Banon:
> > Which microcode gives you a brick? Have you tried those new 2018
> > microcodes (not merged yet to coreboot) for 15h generation -
> > https://review.coreboot.org/c/coreboot/+/28273 ? If not, here is a
> > quick & secure way to get them -
> > http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
> > (although this script is at "Lenovo G505S hacking" page, the same
> > microcodes should work for desktop Richland CPUs as well) . By the
> > way, it could help you to get your hardware virtualization (IOMMU)
> > working
> > On Fri, Nov 2, 2018 at 7:06 PM kinky_nekoboi
> >  wrote:
> >> Hi Mike, i hope i can help u i am just a User of coreboot and noo skilled 
> >> coreboot hacker yet lol.
> >> The A10-6800K should work as its the same CPU core/ gen.
> >> do not include microcode it makes the rom a brick mode.
> >> U have to add a VGA bios if u are using the Internal GPU.
> >> i am using a F2A85M rev 1.1 (not pro and not LE, they are quite rare)
> >>
> >> Am 2. November 2018 17:01:24 MEZ schrieb Mike Banon :
> >>> Nice report. Do you think A10-6800K CPU would have worked at this
> >>> motherboard? Or only A8-6600K is supported? Also, what hardware
> >>> revision of this motherboard do you have? (there were F2A85M / --//--
> >>> PRO and some other revisions, so I'm a bit confused) . I am seriously
> >>> considering doing a similar build, but would like to get the fastest
> >>> available CPU you could install there
> >>> On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi
> >>>  wrote:
> 
>   something like that happens if u connect anything to a USB2 Port
> 
>   [ 2600.001601] usb 7-1: new full-speed USB device number 3 using 
>  ohci-pci
>   [ 2600.001612] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2600.001619] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2600.001624] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2600.185864] usb 7-1: device descriptor read/64, error -11
>   [ 2600.293659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2600.293669] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2600.293674] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2600.477668] usb 7-1: device descriptor read/64, error -11
>   [ 2600.585647] usb usb7-port1: attempt power cycle
>   [ 2601.090486] usb 7-1: new full-speed USB device number 4 using 
>  ohci-pci
>   [ 2601.090494] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2601.301659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2601.509672] usb 7-1: device not accepting address 4, error -11
>   [ 2601.693678] usb 7-1: new full-speed USB device number 5 using 
>  ohci-pci
>   [ 2601.693693] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2601.901677] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>  0x0001c52c2ea8+8 of device mask 
>   [ 2602.109672] usb 7-1: device not accepting address 5, error -11
>   [ 2602.109723] usb usb7-port1: unable to enumerate USB device
> 
> 

Re: [coreboot] Status Update of F2A85M

[kinky_nekoboi]

I tried only the one included in current master tree.

But CBFS reports me an 0KB blob as an output ... so that its mostlikele
the reason it halts after boot (maybe updating an not working microcode
to the cpu than ?)

i have microcodes enabled per linux kernel update
dmesg | grep microcode:
[    3.794585] microcode: CPU0: patch_level=0x0600110f
[    3.794588] microcode: CPU1: patch_level=0x0600110f
[    3.794595] microcode: CPU2: patch_level=0x0600110f
[    3.794602] microcode: CPU3: patch_level=0x0600110f
[    3.794653] microcode: Microcode Update Driver: v2.2.

Am 02.11.2018 um 17:12 schrieb Mike Banon:
> Which microcode gives you a brick? Have you tried those new 2018
> microcodes (not merged yet to coreboot) for 15h generation -
> https://review.coreboot.org/c/coreboot/+/28273 ? If not, here is a
> quick & secure way to get them -
> http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
> (although this script is at "Lenovo G505S hacking" page, the same
> microcodes should work for desktop Richland CPUs as well) . By the
> way, it could help you to get your hardware virtualization (IOMMU)
> working
> On Fri, Nov 2, 2018 at 7:06 PM kinky_nekoboi
>  wrote:
>> Hi Mike, i hope i can help u i am just a User of coreboot and noo skilled 
>> coreboot hacker yet lol.
>> The A10-6800K should work as its the same CPU core/ gen.
>> do not include microcode it makes the rom a brick mode.
>> U have to add a VGA bios if u are using the Internal GPU.
>> i am using a F2A85M rev 1.1 (not pro and not LE, they are quite rare)
>>
>> Am 2. November 2018 17:01:24 MEZ schrieb Mike Banon :
>>> Nice report. Do you think A10-6800K CPU would have worked at this
>>> motherboard? Or only A8-6600K is supported? Also, what hardware
>>> revision of this motherboard do you have? (there were F2A85M / --//--
>>> PRO and some other revisions, so I'm a bit confused) . I am seriously
>>> considering doing a similar build, but would like to get the fastest
>>> available CPU you could install there
>>> On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi
>>>  wrote:

  something like that happens if u connect anything to a USB2 Port

  [ 2600.001601] usb 7-1: new full-speed USB device number 3 using ohci-pci
  [ 2600.001612] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2600.001619] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2600.001624] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2600.185864] usb 7-1: device descriptor read/64, error -11
  [ 2600.293659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2600.293669] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2600.293674] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2600.477668] usb 7-1: device descriptor read/64, error -11
  [ 2600.585647] usb usb7-port1: attempt power cycle
  [ 2601.090486] usb 7-1: new full-speed USB device number 4 using ohci-pci
  [ 2601.090494] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2601.301659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2601.509672] usb 7-1: device not accepting address 4, error -11
  [ 2601.693678] usb 7-1: new full-speed USB device number 5 using ohci-pci
  [ 2601.693693] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2601.901677] ohci-pci :00:12.0: dma_direct_map_page: overflow 
 0x0001c52c2ea8+8 of device mask 
  [ 2602.109672] usb 7-1: device not accepting address 5, error -11
  [ 2602.109723] usb usb7-port1: unable to enumerate USB device


  Am 02.11.2018 um 02:01 schrieb kinky_nekoboi:

  heeey

  i am very happy that i have coreboot running now on my desktop machine...

  ADDON-GPU card works now

  Nvramcui works

  Optionrom execution works.

  IOMMU does not work .. debian has to boot with iommu=off.

  but KVM virtualsation works somehow.

  Suspend does not work.

  USB is still extremely buggy ... only the USB3 Ports are useable.


  here some output

  Architektur:   x86_64
  CPU Operationsmodus:   32-bit, 64-bit
  Byte-Reihenfolge:  Little Endian
  CPU(s):4
  Liste der Online-CPU(s):   0-3
  Thread(s) pro Kern:2
  Kern(e) pro Socket:2
  Sockel:1
  NUMA-Knoten:   1
  Anbieterkennung:   

Re: [coreboot] [LinuxBoot] FOSDEM 2019 deadline today

[David Hendricks]

On Fri, Nov 2, 2018 at 9:15 AM 'Ron Minnich' via linuxboot <
linuxb...@googlegroups.com> wrote:

> I"m leaning to yes, by which I mean if you do it, I'll show up.
>
> I can't believe I said that.
> On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger
>  wrote:
> >
> > Hi!
> >
> > FOSDEM next year will be on 2 & 3 February 2019.
> > The deadline for applying for a stand is today.
> > Do we want a coreboot/flashrom/LinuxBoot stand/booth?
>

Same as what Ron said. I think someone from FB can be there to talk about
coreboot/LinuxBoot stuff and perhaps bring some hardware to demo.
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Status Update of F2A85M

[Mike Banon]

Which microcode gives you a brick? Have you tried those new 2018
microcodes (not merged yet to coreboot) for 15h generation -
https://review.coreboot.org/c/coreboot/+/28273 ? If not, here is a
quick & secure way to get them -
http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
(although this script is at "Lenovo G505S hacking" page, the same
microcodes should work for desktop Richland CPUs as well) . By the
way, it could help you to get your hardware virtualization (IOMMU)
working
On Fri, Nov 2, 2018 at 7:06 PM kinky_nekoboi
 wrote:
>
> Hi Mike, i hope i can help u i am just a User of coreboot and noo skilled 
> coreboot hacker yet lol.
> The A10-6800K should work as its the same CPU core/ gen.
> do not include microcode it makes the rom a brick mode.
> U have to add a VGA bios if u are using the Internal GPU.
> i am using a F2A85M rev 1.1 (not pro and not LE, they are quite rare)
>
> Am 2. November 2018 17:01:24 MEZ schrieb Mike Banon :
>>
>> Nice report. Do you think A10-6800K CPU would have worked at this
>> motherboard? Or only A8-6600K is supported? Also, what hardware
>> revision of this motherboard do you have? (there were F2A85M / --//--
>> PRO and some other revisions, so I'm a bit confused) . I am seriously
>> considering doing a similar build, but would like to get the fastest
>> available CPU you could install there
>> On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi
>>  wrote:
>>>
>>>
>>>  something like that happens if u connect anything to a USB2 Port
>>>
>>>  [ 2600.001601] usb 7-1: new full-speed USB device number 3 using ohci-pci
>>>  [ 2600.001612] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2600.001619] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2600.001624] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2600.185864] usb 7-1: device descriptor read/64, error -11
>>>  [ 2600.293659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2600.293669] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2600.293674] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2600.477668] usb 7-1: device descriptor read/64, error -11
>>>  [ 2600.585647] usb usb7-port1: attempt power cycle
>>>  [ 2601.090486] usb 7-1: new full-speed USB device number 4 using ohci-pci
>>>  [ 2601.090494] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2601.301659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2601.509672] usb 7-1: device not accepting address 4, error -11
>>>  [ 2601.693678] usb 7-1: new full-speed USB device number 5 using ohci-pci
>>>  [ 2601.693693] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2601.901677] ohci-pci :00:12.0: dma_direct_map_page: overflow 
>>> 0x0001c52c2ea8+8 of device mask 
>>>  [ 2602.109672] usb 7-1: device not accepting address 5, error -11
>>>  [ 2602.109723] usb usb7-port1: unable to enumerate USB device
>>>
>>>
>>>  Am 02.11.2018 um 02:01 schrieb kinky_nekoboi:
>>>
>>>  heeey
>>>
>>>  i am very happy that i have coreboot running now on my desktop machine...
>>>
>>>  ADDON-GPU card works now
>>>
>>>  Nvramcui works
>>>
>>>  Optionrom execution works.
>>>
>>>  IOMMU does not work .. debian has to boot with iommu=off.
>>>
>>>  but KVM virtualsation works somehow.
>>>
>>>  Suspend does not work.
>>>
>>>  USB is still extremely buggy ... only the USB3 Ports are useable.
>>>
>>>
>>>  here some output
>>>
>>>  Architektur:   x86_64
>>>  CPU Operationsmodus:   32-bit, 64-bit
>>>  Byte-Reihenfolge:  Little Endian
>>>  CPU(s):4
>>>  Liste der Online-CPU(s):   0-3
>>>  Thread(s) pro Kern:2
>>>  Kern(e) pro Socket:2
>>>  Sockel:1
>>>  NUMA-Knoten:   1
>>>  Anbieterkennung:   AuthenticAMD
>>>  Prozessorfamilie:  21
>>>  Modell:19
>>>  Modellname:AMD A8-6600K APU with Radeon(tm) HD Graphics
>>>  Stepping:  1
>>>  CPU MHz:   2068.754
>>>  Maximale Taktfrequenz der CPU: 3900,
>>>  Minimale Taktfrequenz der CPU: 1900,
>>>  BogoMIPS:  7786.16
>>>  Virtualisierung:   AMD-V
>>>  L1d Cache: 16K
>>>  L1i Cache: 64K
>>>  L2 Cache:  2048K
>>>  NUMA-Knoten0 CPU(s):   0-3
>>>  Markierungen:  fpu vme de pse tsc msr pae mce cx8 apic
>>>  sep mtrr pge mca cmov pat 

Re: [coreboot] Status Update of F2A85M

[kinky_nekoboi]

Hi Mike, i hope i can help u i am just a User of coreboot and noo skilled 
coreboot hacker yet lol.
The A10-6800K should work as its the same CPU core/ gen.
do not include microcode it makes the rom a brick mode.
U have to add a VGA bios if u are using the Internal GPU.
i am using a F2A85M rev 1.1 (not pro and not LE, they are quite rare)

Am 2. November 2018 17:01:24 MEZ schrieb Mike Banon :
>Nice report. Do you think A10-6800K CPU would have worked at this
>motherboard? Or only A8-6600K is supported? Also, what hardware
>revision of this motherboard do you have? (there were F2A85M / --//--
>PRO and some other revisions, so I'm a bit confused) . I am seriously
>considering doing a similar build, but would like to get the fastest
>available CPU you could install there
>On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi
> wrote:
>>
>> something like that happens if u connect anything to a USB2 Port
>>
>> [ 2600.001601] usb 7-1: new full-speed USB device number 3 using
>ohci-pci
>> [ 2600.001612] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2600.001619] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2600.001624] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2600.185864] usb 7-1: device descriptor read/64, error -11
>> [ 2600.293659] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2600.293669] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2600.293674] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2600.477668] usb 7-1: device descriptor read/64, error -11
>> [ 2600.585647] usb usb7-port1: attempt power cycle
>> [ 2601.090486] usb 7-1: new full-speed USB device number 4 using
>ohci-pci
>> [ 2601.090494] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2601.301659] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2601.509672] usb 7-1: device not accepting address 4, error -11
>> [ 2601.693678] usb 7-1: new full-speed USB device number 5 using
>ohci-pci
>> [ 2601.693693] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2601.901677] ohci-pci :00:12.0: dma_direct_map_page: overflow
>0x0001c52c2ea8+8 of device mask 
>> [ 2602.109672] usb 7-1: device not accepting address 5, error -11
>> [ 2602.109723] usb usb7-port1: unable to enumerate USB device
>>
>>
>> Am 02.11.2018 um 02:01 schrieb kinky_nekoboi:
>>
>> heeey
>>
>> i am very happy that i have coreboot running now on my desktop
>machine...
>>
>> ADDON-GPU card works now
>>
>> Nvramcui works
>>
>> Optionrom execution works.
>>
>> IOMMU does not work .. debian has to boot with iommu=off.
>>
>> but KVM virtualsation works somehow.
>>
>> Suspend does not work.
>>
>> USB is still extremely buggy ... only the USB3 Ports are useable.
>>
>>
>> here some output
>>
>> Architektur:   x86_64
>> CPU Operationsmodus:   32-bit, 64-bit
>> Byte-Reihenfolge:  Little Endian
>> CPU(s):4
>> Liste der Online-CPU(s):   0-3
>> Thread(s) pro Kern:2
>> Kern(e) pro Socket:2
>> Sockel:1
>> NUMA-Knoten:   1
>> Anbieterkennung:   AuthenticAMD
>> Prozessorfamilie:  21
>> Modell:19
>> Modellname:AMD A8-6600K APU with Radeon(tm) HD
>Graphics
>> Stepping:  1
>> CPU MHz:   2068.754
>> Maximale Taktfrequenz der CPU: 3900,
>> Minimale Taktfrequenz der CPU: 1900,
>> BogoMIPS:  7786.16
>> Virtualisierung:   AMD-V
>> L1d Cache: 16K
>> L1i Cache: 64K
>> L2 Cache:  2048K
>> NUMA-Knoten0 CPU(s):   0-3
>> Markierungen:  fpu vme de pse tsc msr pae mce cx8
>apic
>> sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall
>nx
>> mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl
>nonstop_tsc
>> cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16
>sse4_1
>> sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic
>> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit
>wdt
>> lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb
>> hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save
>tsc_scale
>> vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
>>
>>
>> 23 entries total:
>>
>>0:1st timestamp 13,116
>>1:start of romstage 13,477 (361)
>>2:before ram initialization

Re: [coreboot] Status Update of F2A85M

[Mike Banon]

Nice report. Do you think A10-6800K CPU would have worked at this
motherboard? Or only A8-6600K is supported? Also, what hardware
revision of this motherboard do you have? (there were F2A85M / --//--
PRO and some other revisions, so I'm a bit confused) . I am seriously
considering doing a similar build, but would like to get the fastest
available CPU you could install there
On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi
 wrote:
>
> something like that happens if u connect anything to a USB2 Port
>
> [ 2600.001601] usb 7-1: new full-speed USB device number 3 using ohci-pci
> [ 2600.001612] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2600.001619] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2600.001624] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2600.185864] usb 7-1: device descriptor read/64, error -11
> [ 2600.293659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2600.293669] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2600.293674] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2600.477668] usb 7-1: device descriptor read/64, error -11
> [ 2600.585647] usb usb7-port1: attempt power cycle
> [ 2601.090486] usb 7-1: new full-speed USB device number 4 using ohci-pci
> [ 2601.090494] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2601.301659] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2601.509672] usb 7-1: device not accepting address 4, error -11
> [ 2601.693678] usb 7-1: new full-speed USB device number 5 using ohci-pci
> [ 2601.693693] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2601.901677] ohci-pci :00:12.0: dma_direct_map_page: overflow 
> 0x0001c52c2ea8+8 of device mask 
> [ 2602.109672] usb 7-1: device not accepting address 5, error -11
> [ 2602.109723] usb usb7-port1: unable to enumerate USB device
>
>
> Am 02.11.2018 um 02:01 schrieb kinky_nekoboi:
>
> heeey
>
> i am very happy that i have coreboot running now on my desktop machine...
>
> ADDON-GPU card works now
>
> Nvramcui works
>
> Optionrom execution works.
>
> IOMMU does not work .. debian has to boot with iommu=off.
>
> but KVM virtualsation works somehow.
>
> Suspend does not work.
>
> USB is still extremely buggy ... only the USB3 Ports are useable.
>
>
> here some output
>
> Architektur:   x86_64
> CPU Operationsmodus:   32-bit, 64-bit
> Byte-Reihenfolge:  Little Endian
> CPU(s):4
> Liste der Online-CPU(s):   0-3
> Thread(s) pro Kern:2
> Kern(e) pro Socket:2
> Sockel:1
> NUMA-Knoten:   1
> Anbieterkennung:   AuthenticAMD
> Prozessorfamilie:  21
> Modell:19
> Modellname:AMD A8-6600K APU with Radeon(tm) HD Graphics
> Stepping:  1
> CPU MHz:   2068.754
> Maximale Taktfrequenz der CPU: 3900,
> Minimale Taktfrequenz der CPU: 1900,
> BogoMIPS:  7786.16
> Virtualisierung:   AMD-V
> L1d Cache: 16K
> L1i Cache: 64K
> L2 Cache:  2048K
> NUMA-Knoten0 CPU(s):   0-3
> Markierungen:  fpu vme de pse tsc msr pae mce cx8 apic
> sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx
> mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc
> cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1
> sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic
> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt
> lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb
> hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale
> vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
>
>
> 23 entries total:
>
>0:1st timestamp 13,116
>1:start of romstage 13,477 (361)
>2:before ram initialization 75,515 (62,038)
>3:after ram initialization  1,308,025 (1,232,510)
>4:end of romstage   1,319,893 (11,867)
>8:starting to load ramstage 1,319,966 (73)
>   15:starting LZMA decompress (ignore for x86) 1,319,984 (18)
>   16:finished LZMA decompress (ignore for x86) 1,370,088 (50,103)
>9:finished loading ramstage 1,370,357 (269)
>   10:start

[coreboot] New Defects reported by Coverity Scan for coreboot

[scan-admin]

Hi,

Please find the latest report on new defect(s) introduced to coreboot found 
with Coverity Scan.

1 new defect(s) introduced to coreboot found with Coverity Scan.
1 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent 
build analyzed by Coverity Scan.

New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)


** CID 1396558:  Control flow issues  (MISSING_BREAK)
/src/mainboard/google/poppy/variants/nami/mainboard.c: 238 in 
variant_devtree_update()



*** CID 1396558:  Control flow issues  (MISSING_BREAK)
/src/mainboard/google/poppy/variants/nami/mainboard.c: 238 in 
variant_devtree_update()
232 switch (sku_id) {
233 case SKU_0_SONA:
234 case SKU_1_SONA:
235 case SKU_0_SYNDRA:
236 case SKU_1_SYNDRA:
237 case SKU_2_SYNDRA:
>>> CID 1396558:  Control flow issues  (MISSING_BREAK)
>>> The case for value "179296U" is not terminated by a 'break' statement.
238 case SKU_3_SYNDRA:
239 pl2_id = PL2_ID_SONA_SYNDRA;
240 case SKU_0_VAYNE:
241 case SKU_1_VAYNE:
242 case SKU_2_VAYNE:
243 case SKU_0_PANTHEON:



To view the defects in Coverity Scan visit, 
https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRbLuoVetFLSjdonCi1EjfHRqWGQvojmmkYaBE-2BPJiTQvQ-3D-3D_q4bX76XMySz3BXBlWr5fXXJ4cvAsgEXEqC7dBPM7O5Y3GF4hLF1-2Fhmf3a8scGXsMbL59oQeIcfo713ImKVkdfZctKNZGZwF-2Fuv3UJIwyz4IY-2FblCtz-2Bu3Prw458XqMzCPgvF6DUWOY84mHzG63zylHGuN8H8Yow0PfA6agmE2xIPGMxVcSN2yhCqMWF23WWtQfNnaEGcaKtXtT6g9Xwd472l5dPJ8XF6Uqch2zmWUbs-3D


-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] FOSDEM 2019 deadline today

[Carl-Daniel Hailfinger]

Hi!

FOSDEM next year will be on 2 & 3 February 2019.
The deadline for applying for a stand is today.
Do we want a coreboot/flashrom/LinuxBoot stand/booth?

There will be a hardware enablement devroom as well, and we might be
able to participate there, but that's not necessarily giving us a chance
to talk to people all day.

Regards,
Carl-Daniel

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] CoffeeLake RVP master: Code changed... How to enable SATA and LAN?

[Jose Trujillo via coreboot]

Hello coreboot developers:

Looks that coreboot development has been  very active lately integrating FSP, 
adding new platforms and getting ready  for the 4.9 release.
And  also I can see new payloads "WOW" (like LinuxBoot, Yabits)... what a 
revolution of features and code.

I am using coreboot "master" from yesterday and using CoffeeLake RVP tree on my 
CoffeeLake H (non RVP) system and reconfiguring .
I am in the process of testing the functionality of coreboot on my devices and 
I know I need to wait for the release.

I am trying to figure out how is going to be the way of enabling SATA and LAN 
(and other devices) on the platforms with renewed code.
1.- In "device pci" list of devicetree.cb file (that previously had issues).
2.- As register in devicetree.cb (EnableLan and EnableSata no longer works).
3.- Kconfig or somewere else.

I am trying several ways to enable LAN and SATA in the "user domain" code but 
failed.
Unless I still have something not configured correctly I would like to know the 
right way of enable those devices.

Thank you all,
Jose.-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot