<html><head></head><body>i am using Debian Testing with Kernel 4.18. sooo this should not be the problem i guess..<br>The 2 Mainproblem atm are<br>make the USB2 ports work.<br>fix iommu<br><br>also it would be nice if there would be nice if they add a working microcode update mechanism<br><br><div class="gmail_quote">Am 3. November 2018 20:02:23 MEZ schrieb Mike Banon <mikebdp2@gmail.com>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Have you tried any Linux distributions other than Debian? Because<br>Debian's packages and Linux kernel - are relatively ancient, and maybe<br>the problems you're having - have been fixed in the recent kernel<br>versions (although they could have broken something else there ;) .<br>Please try a very modern Linux distribution, like Antergos<br>(newbie-friendly Arch Linux with GUI), Artix Linux (friendly Arch<br>without systemd), or maybe a fully updated Void Linux (really clean<br>and ultra fast Linux, also no systemd). Maybe some of your current<br>problems wouldn't exist there, it might be a good idea to try ;)<br>On Sat, Nov 3, 2018 at 2:37 AM Kinky Nekoboi<br><kinky_nekoboi@bluetardis.de> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><br> i have tried it, microcode is now updated, but this does not help with<br> linux not wants to boot with iommu enabled<br><br><br> Am 02.11.2018 um 21:29 schrieb Mike Banon:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> For our Richland 15h family AMD CPUs (and for 16h also) , this<br> microcode update procedure - accessible from coreboot's configuration<br> "menuconfig" menu - is broken, I've observed this 0K problem too. You<br> should leave this "Include CPU microcode in CBFS" option as "Do not<br> include microcode updates" and just run a script from this wiki -<br> <a href="http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates">http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates</a><br> - it will patch the AMD microcodes hardcoded inside .c source code<br> files as the arrays of hex values. After you'll patch your coreboot,<br> rebuild it and install to your motherboard, your microcode's patch<br> level should change from 0x0600110f to 0x0600111f (0f->1f)<br><br> Best regards,<br> Mike Banon<br> On Fri, Nov 2, 2018 at 10:51 PM kinky_nekoboi<br> <kinky_nekoboi@bluetardis.de> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> I tried only the one included in current master tree.<br><br> But CBFS reports me an 0KB blob as an output ... so that its mostlikele<br> the reason it halts after boot (maybe updating an not working microcode<br> to the cpu than ?)<br><br> i have microcodes enabled per linux kernel update<br> dmesg | grep microcode:<br> [ 3.794585] microcode: CPU0: patch_level=0x0600110f<br> [ 3.794588] microcode: CPU1: patch_level=0x0600110f<br> [ 3.794595] microcode: CPU2: patch_level=0x0600110f<br> [ 3.794602] microcode: CPU3: patch_level=0x0600110f<br> [ 3.794653] microcode: Microcode Update Driver: v2.2.<br><br> Am 02.11.2018 um 17:12 schrieb Mike Banon:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;">Which microcode gives you a brick? Have you tried those new 2018<br>microcodes (not merged yet to coreboot) for 15h generation -<br><a href="https://review.coreboot.org/c/coreboot/+/28273">https://review.coreboot.org/c/coreboot/+/28273</a> ? If not, here is a<br>quick & secure way to get them -<br><a href="http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates">http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates</a><br>(although this script is at "Lenovo G505S hacking" page, the same<br>microcodes should work for desktop Richland CPUs as well) . By the<br>way, it could help you to get your hardware virtualization (IOMMU)<br>working<br>On Fri, Nov 2, 2018 at 7:06 PM kinky_nekoboi<br><kinky_nekoboi@bluetardis.de> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"> Hi Mike, i hope i can help u i am just a User of coreboot and noo skilled coreboot hacker yet lol.<br> The A10-6800K should work as its the same CPU core/ gen.<br> do not include microcode it makes the rom a brick mode.<br> U have to add a VGA bios if u are using the Internal GPU.<br> i am using a F2A85M rev 1.1 (not pro and not LE, they are quite rare)<br><br> Am 2. November 2018 17:01:24 MEZ schrieb Mike Banon <mikebdp2@gmail.com>:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">Nice report. Do you think A10-6800K CPU would have worked at this<br>motherboard? Or only A8-6600K is supported? Also, what hardware<br>revision of this motherboard do you have? (there were F2A85M / --//--<br>PRO and some other revisions, so I'm a bit confused) . I am seriously<br>considering doing a similar build, but would like to get the fastest<br>available CPU you could install there<br>On Fri, Nov 2, 2018 at 4:29 AM kinky_nekoboi<br><kinky_nekoboi@bluetardis.de> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"> something like that happens if u connect anything to a USB2 Port<br><br> [ 2600.001601] usb 7-1: new full-speed USB device number 3 using ohci-pci<br> [ 2600.001612] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2600.001619] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2600.001624] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2600.185864] usb 7-1: device descriptor read/64, error -11<br> [ 2600.293659] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2600.293669] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2600.293674] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2600.477668] usb 7-1: device descriptor read/64, error -11<br> [ 2600.585647] usb usb7-port1: attempt power cycle<br> [ 2601.090486] usb 7-1: new full-speed USB device number 4 using ohci-pci<br> [ 2601.090494] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2601.301659] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2601.509672] usb 7-1: device not accepting address 4, error -11<br> [ 2601.693678] usb 7-1: new full-speed USB device number 5 using ohci-pci<br> [ 2601.693693] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2601.901677] ohci-pci 0000:00:12.0: dma_direct_map_page: overflow 0x00000001c52c2ea8+8 of device mask ffffffff<br> [ 2602.109672] usb 7-1: device not accepting address 5, error -11<br> [ 2602.109723] usb usb7-port1: unable to enumerate USB device<br><br><br> Am 02.11.2018 um 02:01 schrieb kinky_nekoboi:<br><br> heeey<br><br> i am very happy that i have coreboot running now on my desktop machine...<br><br> ADDON-GPU card works now<br><br> Nvramcui works<br><br> Optionrom execution works.<br><br> IOMMU does not work .. debian has to boot with iommu=off.<br><br> but KVM virtualsation works somehow.<br><br> Suspend does not work.<br><br> USB is still extremely buggy ... only the USB3 Ports are useable.<br><br><br> here some output<br><br> Architektur: x86_64<br> CPU Operationsmodus: 32-bit, 64-bit<br> Byte-Reihenfolge: Little Endian<br> CPU(s): 4<br> Liste der Online-CPU(s): 0-3<br> Thread(s) pro Kern: 2<br> Kern(e) pro Socket: 2<br> Sockel: 1<br> NUMA-Knoten: 1<br> Anbieterkennung: AuthenticAMD<br> Prozessorfamilie: 21<br> Modell: 19<br> Modellname: AMD A8-6600K APU with Radeon(tm) HD Graphics<br> Stepping: 1<br> CPU MHz: 2068.754<br> Maximale Taktfrequenz der CPU: 3900,0000<br> Minimale Taktfrequenz der CPU: 1900,0000<br> BogoMIPS: 7786.16<br> Virtualisierung: AMD-V<br> L1d Cache: 16K<br> L1i Cache: 64K<br> L2 Cache: 2048K<br> NUMA-Knoten0 CPU(s): 0-3<br> Markierungen: fpu vme de pse tsc msr pae mce cx8 apic<br> sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx<br> mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc<br> cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1<br> sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic<br> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt<br> lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb<br> hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale<br> vmcb_clean flushbyasid decodeassists pausefilter pfthreshold<br><br><br> 23 entries total:<br><br> 0:1st timestamp 13,116<br> 1:start of romstage 13,477 (361)<br> 2:before ram initialization 75,515 (62,038)<br> 3:after ram initialization 1,308,025 (1,232,510)<br> 4:end of romstage 1,319,893 (11,867)<br> 8:starting to load ramstage 1,319,966 (73)<br> 15:starting LZMA decompress (ignore for x86) 1,319,984 (18)<br> 16:finished LZMA decompress (ignore for x86) 1,370,088 (50,103)<br> 9:finished loading ramstage 1,370,357 (269)<br> 10:start of ramstage 1,371,078 (720)<br> 30:device enumeration 1,461,571 (90,493)<br> 40:device configuration 1,470,758 (9,186)<br> 50:device enable 1,501,692 (30,933)<br> 60:device initialization 1,569,453 (67,761)<br> 65:Option ROM initialization 1,769,162 (199,708)<br> 65:Option ROM initialization 1,936,860 (167,697)<br> 70:device setup done 2,011,094 (74,234)<br> 75:cbmem post 2,366,967 (355,873)<br> 80:write tables 2,371,915 (4,947)<br> 85:finalize chips 2,750,289 (378,374)<br> 90:load payload 2,755,411 (5,122)<br> 15:starting LZMA decompress (ignore for x86) 2,797,472 (42,060)<br> 16:finished LZMA decompress (ignore for x86) 2,823,100 (25,628)<br> 99:selfboot jump 2,838,148 (15,048)<br><br> Total Time: 2,825,023<br><br><br><br><br> --<br> coreboot mailing list: coreboot@coreboot.org<br> <a href="https://mail.coreboot.org/mailman/listinfo/coreboot">https://mail.coreboot.org/mailman/listinfo/coreboot</a><br></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote><br><br> --<br> coreboot mailing list: coreboot@coreboot.org<br> <a href="https://mail.coreboot.org/mailman/listinfo/coreboot">https://mail.coreboot.org/mailman/listinfo/coreboot</a><br></blockquote></pre></blockquote></div></body></html>