coreboot December 2017

coreboot@coreboot.org

68 participants
177 discussions

Support for a 2004 HP Workstation
by Giancarlo A Jones 06 Dec '17

06 Dec '17

Hi corebooters Just joined the list. I have a Pentium 4 HP workstation (xw6200) with which the urge to tinker is strong. https://support.hp.com/us-en/document/c00215315. There is no webpage for the motherboard but there is a service manual. http://jp.ext.hp.com/lib/doc/manual/workstation/hp_workstation/c00213035.pdf I want to swap out the vendor bios for SeaBIOS purely out of the need to tinker. Here's the quick and dirty list of chips: *Motherboard: HP 08B8h *512kb SST49LF004A/B EEPROM *Intel ICH5/ICH5R I/O Controller *Intel E7525 Memory Controller *SMSC LPC47B397 Super I/O The dump of the commands suggested is below. I notice that everything but the memory controller seems to be supported by coreboot. Is there any plan to support this board? If not any guidance on slapping something together that might work? Thanks for your help! --Giancarlo *DMI* Base Board Information Manufacturer: Hewlett-Packard Product Name: 08B8h Version: Not Specified Serial Number: CZC634058M *PCI* -[0000:00]-+-00.0 Intel Corporation E7525 Memory Controller Hub [8086:359e] +-02.0-[20]-- +-03.0-[01]----00.0 Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express [14e4:1677] +-04.0-[40]--+-00.0 Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300] [1002:5b60] | \-00.1 Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300 SE] [1002:5b70] +-1d.0 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 [8086:24d2] +-1d.1 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 [8086:24d4] +-1d.2 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 [8086:24d7] +-1d.3 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 [8086:24de] +-1d.7 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller [8086:24dd] +-1e.0-[02]-- +-1f.0 Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge [8086:24d0] +-1f.1 Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller [8086:24db] +-1f.2 Intel Corporation 82801EB (ICH5) SATA Controller [8086:24d1] \-1f.5 Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller [8086:24d5] *SUPER I/O SUMMARY* superiotool r6637 Found SMSC LPC47B397 (id=0x6f, rev=0x01) at 0x2e No dump available for this Super I/O *SUPER I/O VERBOSE* superiotool r6637 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0x0000, rev=0x00 Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0x0400, id=0x016f Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=standard) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x2e... Failed. Returned data: id=0x6f01, rev=0x9 Probing for ITE Super I/O (init=it8502e) at 0x2e... Failed. Returned data: id=0x6f01, rev=0x9 Probing for ITE Super I/O (init=it8761e) at 0x2e... Failed. Returned data: id=0x6f01, rev=0x9 Probing for ITE Super I/O (init=it8228e) at 0x2e... Failed. Returned data: id=0x6f01, rev=0x9 Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0x6f01, rev=0x9 Probing for ITE Super I/O (init=standard) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8661f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8671f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x15c... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x164e... Failed. Returned data: port=0xff, port+1=0xff Probing for Nuvoton Super I/O at 0x164e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x164e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x2e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x2e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x4e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x4e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Found SMSC LPC47B397 (id=0x6f, rev=0x01) at 0x2e No dump available for this Super I/O Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0x00/0x00, rev=0x00 Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for VIA Super I/O at 0x3f0... PCI device 1106:0686 not found. Probing for Server Engines Super I/O at 0x2e... Failed. Returned data: id=0xffff, rev=0xff *FLASHROM SUMMARY* flashrom v0.9.7-r1782 on Linux 3.16.0-4-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH5/ICH5R". Enabling flash write... Warning: Setting Bios Control at 0x4e from 0x02 to 0x01 failed. New value is 0x03. OK. Found SST flash chip "SST49LF004A/B" (512 kB, FWH) at physical address 0xfff80000. No operations were specified. *FLASHROM VERBOSE* flashrom v0.9.7-r1782 on Linux 3.16.0-4-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (3 args): flashrom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 2123M loops per second, 10 myus = 10 us, 100 myus = 99 us, 1000 myus = 1003 us, 10000 myus = 9961 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Mini Tower" DMI string system-manufacturer: "Hewlett-Packard" DMI string system-product-name: "hp workstation xw6200" DMI string system-version: " " DMI string baseboard-manufacturer: "Hewlett-Packard" DMI string baseboard-product-name: "08B8h" DMI string baseboard-version: "Not Specified" Found chipset "Intel ICH5/ICH5R" with PCI ID 8086:24d0. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes BIOS_CNTL = 0x03: BIOS Lock Enable: enabled, BIOS Write Enable: enabled Warning: Setting Bios Control at 0x4e from 0x02 to 0x01 failed. New value is 0x03. OK. The following protocols are supported: FWH. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x50, id2 0x07, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Found SST flash chip "SST49LF004A/B" (512 kB, FWH) at physical address 0xfff80000. Lock status for 0x000000 (size 0x010000) is 01, write locked Lock status for 0x010000 (size 0x010000) is 01, write locked Lock status for 0x020000 (size 0x010000) is 01, write locked Lock status for 0x030000 (size 0x010000) is 01, write locked Lock status for 0x040000 (size 0x010000) is 01, write locked Lock status for 0x050000 (size 0x010000) is 01, write locked Lock status for 0x060000 (size 0x010000) is 01, write locked Lock status for 0x070000 (size 0x010000) is 01, write locked Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x50, id2 0x07, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x20, id2 0x20, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Found SST flash chip "SST49LF004A/B" (512 kB, FWH). No operations were specified.

1 0

Do you support PCI devices onboard the mobo: MSI/NEC MS-7168 for FreeBSD OS?
by Zoran Stojsavljevic 06 Dec '17

06 Dec '17

Hello Martin and Michal (since your support/expertise is required/crucial here), This mobo (owned by Vincenzo) is too old. I took the freedom to attach imported picture, so people can see better. [image: Inline image 1] BIOS is legacy, from 06/2009. It has PCI devices, and it seems that few of them share IRQ5 (no idea how many interrupts this board supports, seems only 8)?! In order to understand if PCI devices on MSI/NEC MS-7168 mobo are supported, I was able to google interesting site: http://code.metager.de/source/xref/freebsd/share/misc/pci_vendors So, let us ask the question to the maintainers of this site, if the mobo: MSI/NEC MS-7168 is FreeBSD supported for PCI devices onboard, shown here? Martin and Michal, Could you, please, answer us: do you support PCI devices on-board the mobo: MSI/NEC MS-7168 for FreeBSD OS? Thank you, Zoran _______ On Wed, Dec 6, 2017 at 11:27 AM, Vincenzo Di Salvo < ingegneriaforense(a)alice.it> wrote: > Ok Zoran, > > > > thanks very much. > > > > It seems to me that tha BIOS (legacy 32 bit) recognize the USB controller > (PCI Onboard USB Controller, IRQ5), as you can see from the attached photo > (please, can you confirm this ?) > > > > So, I think taht the problem is due to the FreeBSD, that has not the > drivers for that hardware. The motherboard is not of the last generation > (MSI/NEC MS-7168) and I think that FreeBSD has not a big database for any > specific hardware. > > So I should have the USB unix device driver for that machine,declare it in > the kernel and re-make the kernel. > > Difficult, because I've not find unix driver on-line for that motherboard. > It seems an OEM motherboard. > > > > About coreboot: probably it is better if buy a motherboard for which the > coreboot team has developed a stable version; after that I can use FreeBSD. > > > > Regards. > > > > Vincenzo. > > *Da:* coreboot [mailto:coreboot-bounces@coreboot.org] *Per conto di *Zoran > Stojsavljevic > *Inviato:* mercoledì 6 dicembre 2017 09:20 > *A:* Vincenzo Di Salvo > *Cc:* coreboot > *Oggetto:* Re: [coreboot] usbd_req_re_enumerate > > > > I can try to help here. But what you wrote here is not enough. > > > > What info is required here, is (significantly) more, then you wrote here. > I'll try to make some ad-hoc systematic approach. :-) > > > > Phase 1: > > [1] What PC/CPU you are using for this purpose (as much detailed info as > possible: make. year, mobo, configuration, etc.)? > > [2] What BIOS (UEFI/Legacy, there are only 4 possible cases): > > [A] 64bit (implies automatically UEFI); > > [B] Legacy 16bit; > > [C] Legacy 32bit; > > [D] UEFI 32bit! > > [3] BIOS make, year, vendor, any documentation, etc. > > > > From here, the phase 1 accomplishments is to make USB root hub and > external USB ports to work with BIOS + FreeBSD. > > > > Coreboot + FreeBSD will be the phase 2. > > > > Zoran > > > > On Wed, Dec 6, 2017 at 2:47 AM, Vincenzo Di Salvo < > ingegneriaforense(a)alice.it> wrote: > > Hello guys, > > during the freebsd installation I receive these messages: > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_IOERROR > ugen0.2: <Unknown> at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > > These message disappear if in the BIOS I disable the parameter: > USB 1.1 OHCI Controllers, > but so doing I cannot use any USB PORT on my workstation. > > QUESTIONS: > 1. Please, can you tell me what this means ? > > 2. Do you know if using Coreboot is it possible avoid this problem ? > > Thanks very much in advance. > > Vincenzo. > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot > > >

1 0

chip identifier in ifd
by Christoph Pomaska 06 Dec '17

06 Dec '17

Hi, did anyone ever try to modify the ifd regarding the chip identifiers? I recently had to replace a chip on a sandybridge device because the old one lost a leg, so it's not usable anymore. Problem is that I wasn't able yet to revive the device that is in an error state. Also changing the identifier in binary didn't help. Is there a checksum to these values or something similar? Best regards Christoph Pomaska

1 0

Your me_cleaner experiences/anomalies
by Hal Martin 06 Dec '17

06 Dec '17

Hi all, I know me_cleaner is not directly related to coreboot, but I think that coreboot users are among the most common people to use me_cleaner. I have run me_cleaner on an Ivy Bridge platform firmware. In both the original vendor firmware and coreboot, cleaning the ME causes all chipset SATA ports to stop functioning. After me_cleaner, SATA ports are inoperable not only within the pre-boot environment but also in Linux. Connecting a SATA device results in continuous link errors/resets and all SATA devices are not usable. If anyone has experienced hardware of Sandy/Ivy Bridge generation not functioning correctly after running me_cleaner, I'd appreciate hearing your experiences! *** coreboot output: PCH type: HM76, device id: 1e59, rev id 4 Intel ME early init Intel ME firmware is ready ME: Requested 32MB UMA Starting native Platform init ...(snip) Done MRS commands t123: 1767, 6000, 7620 ME: FW Partition Table : OK ME: Bringup Loader Failure : NO ME: Firmware Init Complete : NO ME: Manufacturing Mode : YES ME: Boot Options Present : NO ME: Update In Progress : NO ME: Current Working State : Recovery ME: Current Operation State : Bring up ME: Current Operation Mode : Normal ME: Error Code : Debug Failure ME: Progress Phase : BUP Phase ME: Power Management Event : Pseudo-global reset ME: Progress Phase State : 0x42 ME: HFS error : 4 ME: FWS2: 0x1642017a ME: Bist in progress: 0x0 ME: ICC Status : 0x1 ME: Invoke MEBx : 0x1 ME: CPU replaced : 0x1 ME: MBP ready : 0x1 ME: MFS failure : 0x1 ME: Warm reset req : 0x0 ME: CPU repl valid : 0x1 ME: (Reserved) : 0x0 ME: FW update req : 0x0 ME: (Reserved) : 0x0 ME: Current state : 0x42 ME: Current PM event: 0x6 ME: Progress code : 0x1 Full training required PASSED! Tell ME that DRAM is ready ME: FWS2: 0x1642017a ME: Bist in progress: 0x0 ME: ICC Status : 0x1 ME: Invoke MEBx : 0x1 ME: CPU replaced : 0x1 ME: MBP ready : 0x1 ME: MFS failure : 0x1 ME: Warm reset req : 0x0 ME: CPU repl valid : 0x1 ME: (Reserved) : 0x0 ME: FW update req : 0x0 ME: (Reserved) : 0x0 ME: Current state : 0x42 ME: Current PM event: 0x6 ME: Progress code : 0x1 ME: Requested BIOS Action: No DID Ack received ME: FW Partition Table : OK ME: Bringup Loader Failure : NO ME: Firmware Init Complete : NO ME: Manufacturing Mode : YES ME: Boot Options Present : NO ME: Update In Progress : NO ME: Current Working State : Recovery ME: Current Operation State : Bring up ME: Current Operation Mode : Normal ME: Error Code : Debug Failure ME: Progress Phase : BUP Phase ME: Power Management Event : Pseudo-global reset ME: Progress Phase State : 0x42 ...(snip) TOUUD 0x27b600000 TOLUD 0x82a00000 TOM 0x200000000 MEBASE 0x1fe000000 IGD decoded, subtracting 32M UMA and 2M GTT *** intelmetool: ./intelmetool -s Bad news, you have a `HM76 Express Chipset LPC Controller` so you have ME hardware on board and you can't control or disable it, continuing... MEI found: [8086:1e3a] 7 Series/C216 Chipset Family MEI Controller #1 ME Status : 0x4192 ME Status 2 : 0x1642017a ME: FW Partition Table : OK ME: Bringup Loader Failure : NO ME: Firmware Init Complete : NO ME: Manufacturing Mode : YES ME: Boot Options Present : NO ME: Update In Progress : NO ME: Current Working State : Recovery ME: Current Operation State : Bring up ME: Current Operation Mode : Normal ME: Error Code : Debug Failure ME: Progress Phase : BUP Phase ME: Power Management Event : Pseudo-global reset ME: Progress Phase State : 0x42 ME: Extend SHA-256: 6b831b4a9c0dd9630b2578792d3929d7b5560a4cb9b886b559572d1f2446c3d8 ME: has a broken implementation on your board withthis firmware ME: failed to become ready ME: failed to become ready ME: GET FW VERSION message failed ME: failed to become ready ME: failed to become ready ME: GET FWCAPS message failed *** me_cleaner output looks totally normal: Full image detected The ME/TXE region goes from 0x3000 to 0xd00000 Found FPT header at 0x3010 Found 23 partition(s) Found FTPR header: FTPR partition spans from 0x183000 to 0x24d000 ME/TXE firmware version 8.1.51.1471 Removing extra partitions... Removing extra partition entries in FPT... Removing EFFS presence flag... Correcting checksum (0xed)... Reading FTPR modules list... UPDATE (LZMA , 0x1cf4e9 - 0x1cf6a7): removed ROMP (Huffman, fragmented data ): NOT removed, essential BUP (Huffman, fragmented data ): NOT removed, essential KERNEL (Huffman, fragmented data ): removed POLICY (Huffman, fragmented data ): removed HOSTCOMM (LZMA , 0x1cf6a7 - 0x1d642f): removed RSA (LZMA , 0x1d642f - 0x1db715): removed CLS (LZMA , 0x1db715 - 0x1e0eaa): removed TDT (LZMA , 0x1e0eaa - 0x1e75a0): removed FTCS (Huffman, fragmented data ): removed ClsPriv (LZMA , 0x1e75a0 - 0x1e7981): removed SESSMGR (LZMA , 0x1e7981 - 0x1f62ab): removed The ME minimum size should be 1667072 bytes (0x197000 bytes) The ME region can be reduced up to: 00003000:00199fff me Checking the FTPR RSA signature... VALID Done! Good luck! I've documented this issue on the me_cleaner project. If you would like to also comment on GitHub, here is the issue: https://github.com/corna/me_cleaner/issues/119 Thanks, Hal

1 0

R: freebsd
by Vincenzo Di Salvo 06 Dec '17

06 Dec '17

Hello guys, It is a pleasure for me to see that you also appreciate the architecture of the freebsd operating system. Yes Enrico, Tribunale di Lecce is the Italian Court of the City of Lecce. Zoran asks me what my goal is. Really difficult to explain in two words. I try. I apologize with coreboot community if the question is not stricly pertinent to coreboot. It will be in a future email. BACKGROUND. My goal is to make raw images of memory devices like USB sticks and SATA hard drives. The images must be connected avoiding to modify the content of the original devices, in particular the timestamps of the files contained in them, which, as it's known, are filesystem dependent. If I'm not mistaken, when I connect a USB stick or a SATA hard disk to a computer with a Freebsd operating system, the Freebsd recognizes the device at physical level, it creates a node in the / dev directory, but does not bother to understand what it is, that is, for him it is a raw device, so it does not perform dangerous operations like autorun and automount. It seems to me that in Unix this is the meaning of a character device. If this is true, the original device is protected and you can proceed to cloning using the dd command. QUESTIONS AND YOUR TIPS AND CORRECTIONS: 1- What actually happens when you plug in to USB device (you can suggest me a bibliograph to read) 2 - Is there a Unix command that logs in real-time the whole flux, from the physical plugging action of the device to the /dev node creation ? 3 - Verify that the creation of the /dev node only implies that the device is recognized as raw and the O.S. will not be able to access its memory (condition of device write blocked). See you !! Best Regards. Vincenzo. Da: coreboot [mailto:coreboot-bounces@coreboot.org] Per conto di ron minnich Inviato: lunedì 4 dicembre 2017 16:52 A: Zoran Stojsavljevic Cc: Ivan Ivanov; ingegneriaforense(a)alice.it; coreboot Oggetto: Re: [coreboot] freebsd if you watch netflix, you're using freebsd. It's a very solid piece of software. --- Questa email è stata esaminata alla ricerca di virus da AVG. http://www.avg.com

2 2

Re: [coreboot] Blank screen during boot and max CPU fan speed for ASUS KGPE-D16
by Daniel K 06 Dec '17

06 Dec '17

Thanks for the suggestion about the RAM Zoran. Tried it out in the following configurations for 2x CPU setup as per the ASUS documentation but with no luck: - 8x 4 GB = 32 GB @ A2, B2, C2, D2, E2, F2, G2, H2 - 6x 4 GB = 24 GB @ A2, B2, C2, E2, F2, G2 - 4x 4 GB = 16 GB @ A2, C2, E2, G2 - 2x 4 GB = 8 GB @ A2, E2 Additionally, I find that my keyboard does not work in my SSD instance of GRUB (I have the default SeaBIOS on the coreboot BIOS chip) however after GRUB launches Debian, everything works fine. Since coreboot is able to boot to my SSD, could it even be a RAM issue? I'd assume if there was an issue with the RAM the BIOS just wouldn't be able to proceed. ________________________________ From: Zoran Stojsavljevic <zoran.stojsavljevic(a)gmail.com> Sent: 05 December 2017 02:46 To: Daniel K Cc: coreboot(a)coreboot.org Subject: Re: [coreboot] Blank screen during boot and max CPU fan speed for ASUS KGPE-D16 > - Memory: 16x 4 GB = 64 GB Corsair DDR3-1600 SDRAM (CMZ32GX3M8X1600C9) I will try shot in the dark, since I have no idea about AMD architecture. Seems that you have 8-memory channels architecture, And being you I will start reducing amount of memory to see if anything changes. Would first do 8x 4GB and see what will happen with Coreboot? Have no idea and original MRC algorithm (number of them) in BIOS is/are the same as in Coreboot... And I am trying to target the differences! https://www.anandtech.com/show/6068/lrdimms-rdimms-supermicros-latest-twin/2 LRDIMMs, RDIMMs, and Supermicro’s Latest Twi - AnandTech<https://www.anandtech.com/show/6068/lrdimms-rdimms-supermicros-latest-twin/2> www.anandtech.com Typically, desktop and mobile systems use Unbuffered DIMMs (UDIMMs). The memory controller inside your CPU addresses each memory chip of your UDIMM individually and ... Zoran On Tue, Dec 5, 2017 at 8:05 AM, Daniel K <shambles_09(a)hotmail.com<mailto:shambles_09@hotmail.com>> wrote: Hello, I'm trying out coreboot for the first time. This is great work you are all doing. Having a few issues with my ASUS KGPE-D16 and wonder if anyone could help. The issue is that my CPU fans appear to spin at maximum speed at all times, and the whole boot process is black until my Debian login screen. Flash method: Flashing a couple of 25Q16BVAIG DIP8 chips with a CH341A external USB programmer I bought online and the flashrom linux tool. Using a chip extraction tool for the swap, and making sure to clear my CMOS memory between each swap. Image creation: Followed the steps from: https://www.coreboot.org/Build_HOWTO I checked out the commit reported at the latest successful run: https://review.coreboot.org/gitweb/cgit/coreboot.git/commit/?id=3f09b0ffef9… For the .config file, I tried both creating my own with 'make nconfig' and also copied the .config from the latest successful run at: https://review.coreboot.org/gitweb/cgit/board-status.git/tree/asus/kgpe-d16… I don't bother getting the AMD IMC, AMD XHCI, and AMD PSP because I don't believe my motherboard needs it according to the board page: https://www.coreboot.org/Board:asus/kgpe-d16 I also don't bother getting the vgabios.rom because according to https://www.phoronix.com/scan.php?page=news_item&px=NzQwMQ, coreboot has native vga text-mode? And this page states only text-mode works for my CPU: https://www.raptorengineering.com/coreboot/kgpe-d16-status.php Detailed issue description: In all instances, my PC boots up and shows a black screen for about 10-20 seconds. About 5-10 seconds in, my CPU fans start blowing at what appears to be maximum speed. After another 5-15 seconds, I see my Debian login screen and am able to use my computer normally. However the loud fans put me on edge and I end up turning the PC off after a while. At subsequent boots, the fans start up at maximum speed right away. Swapping back to my vendor BIOS brings the fans back to normal. Could this be microcode related? Same happens for both my onboard graphics as well as my PCIe GPU. System specifications: - Motherboard: ASUS KGPE-D16 - CPU: 2x AMD Opteron 6272 (2.1 GHz) - Memory: 16x 4 GB = 64 GB Corsair DDR3-1600 SDRAM (CMZ32GX3M8X1600C9) - Video: EVGA GeForce GTX 570 (128MB) - Storage: Don't know if this matters, but I have 1x SSD and 1x HDD SATA 3 drives, and one PCIe M.2 NVMe adapter with an M.2 SSD. Additional notes: - Also tried the latest KGPE-D16 Libreboot image but I only get a permanent black screen with that. - Disconnected the ASMB4/KVM module. - Don't think I have LRDIMM RAM because I'm able to boot into Debian. Regards, - Daniel K. -- coreboot mailing list: coreboot(a)coreboot.org<mailto:coreboot@coreboot.org> https://mail.coreboot.org/mailman/listinfo/coreboot

1 0

Re: [coreboot] Blank screen during boot and max CPU fan speed for ASUS KGPE-D16
by Daniel K 06 Dec '17

06 Dec '17

Thanks for the info about the fans Tim, Zoran, and Taiidan. I haven't tried to use fancontrol yet, so I'm confident that will be the solution to my fan issue. https://www.coreboot.org/Build_HOWTO ________________________________ From: Zoran Stojsavljevic <zoran.stojsavljevic(a)gmail.com> Sent: 05 December 2017 23:31 To: Taiidan(a)gmx.com Cc: Timothy Pearson; coreboot(a)coreboot.org; Daniel K Subject: Re: [coreboot] Blank screen during boot and max CPU fan speed for ASUS KGPE-D16 > Naah as tim said you just have to run fancontrol or use Raptor's OpenBMC port for the KGPE-D16/KCMA-D8 boards. I got it. Raptor's OpenBMC port for the KGPE-D16/KCMA-D8 boards module should/must be included in Debian distro as driver addendum. In this case it is not. Thank you, Zotran On Wed, Dec 6, 2017 at 6:56 AM, Taiidan(a)gmx.com<mailto:Taiidan@gmx.com> <Taiidan(a)gmx.com<mailto:Taiidan@gmx.com>> wrote: On 12/06/2017 12:35 AM, Zoran Stojsavljevic wrote: The full speed fan is normal. These are server boards and coreboot *purposefully sets the fans to full speed until the OS boots* and can take over fan control duties via 'fancontrol' [1] or a similar application. Note that the 'w83795' kernel module is required for this to work. Correct me if I am wrong, but how I understood the topic/problem, the fans continue to blow full speed indefinitely even after OS boots, don't they? Naah as tim said you just have to run fancontrol or use Raptor's OpenBMC port for the KGPE-D16/KCMA-D8 boards. Additionally I added this info to the wiki many months ago, as I too was bothered by the fan speed when I first installed coreboot years ago and assumed something was broken to which tim explained it for me too :D

1 0

Re: [coreboot] Blank screen during boot and max CPU fan speed for ASUS KGPE-D16
by Taiidan＠gmx.com 06 Dec '17

06 Dec '17

On 12/06/2017 12:35 AM, Zoran Stojsavljevic wrote: >> The full speed fan is normal. These are server boards and coreboot >> *purposefully sets the fans to full speed until the OS boots* and can take >> over fan control duties via 'fancontrol' [1] or a similar application. >> Note that the 'w83795' kernel module is required for this to work. > Correct me if I am wrong, but how I understood the topic/problem, the fans > continue to blow full speed indefinitely even after OS boots, don't they? Naah as tim said you just have to run fancontrol or use Raptor's OpenBMC port for the KGPE-D16/KCMA-D8 boards. Additionally I added this info to the wiki many months ago, as I too was bothered by the fan speed when I first installed coreboot years ago and assumed something was broken to which tim explained it for me too :D

2 1

Re: [coreboot] Blank screen during boot and max CPU fan speed for ASUS KGPE-D16
by Timothy Pearson 06 Dec '17

06 Dec '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/05/2017 01:05 AM, Daniel K wrote: > > > Hello, > > > I'm trying out coreboot for the first time. This is great work you are > all doing. > > Having a few issues with my ASUS KGPE-D16 and wonder if anyone could help. > > > The issue is that my CPU fans appear to spin at maximum speed at all > times, and the whole boot process is black until my Debian login screen. The full speed fan is normal. These are server boards and coreboot purposefully sets the fans to full speed until the OS boots and can take over fan control duties via 'fancontrol' [1] or a similar application. Note that the 'w83795' kernel module is required for this to work. Alternatively, you can install a reflashed iKVM module with the beta version of the OpenBMC port for this board [2]. This is somewhat more complex, but if you have all of the fan connectors plugged in the BMC can handle fan control independently from the host CPU. If you have only a handful of fans, or very slow fans, connected, then you would need to modify the OpenBMC source and rebuild, since OpenBMC has no way of determining whether uninstalled / slow fans are disconnected or failed. Hope this helps! [1] https://linux.die.net/man/8/fancontrol [2] https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php - -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJaJvL0AAoJEK+E3vEXDOFbx7EIAL2oF7HRCkuyeKLg6Y1jynR5 nNtgqh2SRooAnMpor/G5z/pA4Lo/iq76CNYh6Z9gXlUaB2LP1Gz6IMprt6+VGrDQ wEZbQS1O0MBQriNhD8k/IllljZm4uo0JCe08BgZZW3UXui9z5sxKf3diOsdYn4oA X1S6sbGtT0qiqykuVPZyTlHti1+LIFeQRWXcihAs6UFOIpV4h3lXdCZE0iSNJbka ZCID3e56BoPXA6HE9Df8vm90NVkhCYXCssE4U1LuOgKz4JA3PkXI0F9yPyYpNc9v ZnNFsgS8fpu9FvEdCTy6wT7kSxcJEWCPgLu8msMts04RkP9bok3yuODm6mpL/LM= =Pq6E -----END PGP SIGNATURE-----

2 1

need help with RS780L HT3 init
by Vladislav Tsendrovskii 06 Dec '17

06 Dec '17

Hello! I'm trying to port coreboot to my ga-780t-d3l-rev4.0 mainboard It has AM3+ socket, fam15h cpu, 760G (RS780L) and SB710 And I have 2 problems, running coreboot: 1) "AMD_CB_EventNotify: ERROR: HT_EVENT_NCOH_DEVICE_FAILED: node 0 link 0 depth: 0 attemptedBUID: 1" i've added some trivial printk debug and get cpuSetAMDMSR done Enter amd_ht_init Fam15 northbridge interface secBus = 0 currentPtr = 0x0 Found device 0x96001022 Total links = 0 Searching of next capabilities at 0x0 currentPtr = 0xC4 Writing BUID=0x1 to [20:16] of 0xC4 Read 0x0 from 0x000080C4, bits [20:16] AMD_CB_EventNotify: ERROR: HT_EVENT_NCOH_DEVICE_FAILED: node 0 link 0 depth: 0 attemptedBUID: 1 AMD_CB_EventNotify: INFO: HT_EVENT_NCOH_AUTO_DEPTH: node 0 link 0 depth: 255 Exit amd_ht_init cpuSetAMDPCI 00 done 2) second problem, that coreboot finish booting at "Waiting for predriver calibration to be applied..." when memory initialization After this system writes, that BIOS checksum is incorrect and restores original bios from backup -- Best regards, Vladislav Tsendrovskii

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot December 2017