[coreboot] Status Update of F2A85M
kinky_nekoboi
kinky_nekoboi at bluetardis.de
Sun Nov 4 13:38:23 CET 2018
i am using Debian Testing with Kernel 4.18. sooo this should not be the problem i guess..
The 2 Mainproblem atm are
make the USB2 ports work.
fix iommu
also it would be nice if there would be nice if they add a working microcode update mechanism
Am 3. November 2018 20:02:23 MEZ schrieb Mike Banon <mikebdp2 at gmail.com>:
>Have you tried any Linux distributions other than Debian? Because
>Debian's packages and Linux kernel - are relatively ancient, and maybe
>the problems you're having - have been fixed in the recent kernel
>versions (although they could have broken something else there ;) .
>Please try a very modern Linux distribution, like Antergos
>(newbie-friendly Arch Linux with GUI), Artix Linux (friendly Arch
>without systemd), or maybe a fully updated Void Linux (really clean
>and ultra fast Linux, also no systemd). Maybe some of your current
>problems wouldn't exist there, it might be a good idea to try ;)
>On Sat, Nov 3, 2018 at 2:37 AM Kinky Nekoboi
><kinky_nekoboi at bluetardis.de> wrote:
>>
>> 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
>> > <kinky_nekoboi at bluetardis.de> 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
>> >>> <kinky_nekoboi at bluetardis.de> 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
><mikebdp2 at gmail.com>:
>> >>>>> 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
>> >>>>> <kinky_nekoboi at bluetardis.de> 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 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2600.001619] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2600.001624] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2600.185864] usb 7-1: device descriptor read/64, error -11
>> >>>>>> [ 2600.293659] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2600.293669] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2600.293674] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 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 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2601.301659] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 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 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 2601.901677] ohci-pci 0000:00:12.0: dma_direct_map_page:
>overflow 0x00000001c52c2ea8+8 of device mask ffffffff
>> >>>>>> [ 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,0000
>> >>>>>> Minimale Taktfrequenz der CPU: 1900,0000
>> >>>>>> 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 of ramstage
>1,371,078 (720)
>> >>>>>> 30:device enumeration
>1,461,571 (90,493)
>> >>>>>> 40:device configuration
>1,470,758 (9,186)
>> >>>>>> 50:device enable
>1,501,692 (30,933)
>> >>>>>> 60:device initialization
>1,569,453 (67,761)
>> >>>>>> 65:Option ROM initialization
>1,769,162 (199,708)
>> >>>>>> 65:Option ROM initialization
>1,936,860 (167,697)
>> >>>>>> 70:device setup done
>2,011,094 (74,234)
>> >>>>>> 75:cbmem post
>2,366,967 (355,873)
>> >>>>>> 80:write tables
>2,371,915 (4,947)
>> >>>>>> 85:finalize chips
>2,750,289 (378,374)
>> >>>>>> 90:load payload
>2,755,411 (5,122)
>> >>>>>> 15:starting LZMA decompress (ignore for x86)
>2,797,472 (42,060)
>> >>>>>> 16:finished LZMA decompress (ignore for x86)
>2,823,100 (25,628)
>> >>>>>> 99:selfboot jump
>2,838,148 (15,048)
>> >>>>>>
>> >>>>>> Total Time: 2,825,023
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> coreboot mailing list: coreboot at coreboot.org
>> >>>>>> https://mail.coreboot.org/mailman/listinfo/coreboot
>>
>>
>> --
>> coreboot mailing list: coreboot at coreboot.org
>> https://mail.coreboot.org/mailman/listinfo/coreboot
>
>--
>coreboot mailing list: coreboot at coreboot.org
>https://mail.coreboot.org/mailman/listinfo/coreboot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20181104/9a1931d8/attachment.html>
More information about the coreboot
mailing list