[coreboot] Re: Debugging Windows 10 BSOD
Highly possible you don't need to connect live sessions using windbg, you
can analysis the generated dump file to simply open with windbg.
Raul Rangel 于2021年1月14日周四 上午6:21写道：
> I'm trying to boot the Windows 10 Installer on a picasso based device
> using coreboot + tianocore. I keep getting a BSOD after the windows logo
> shows with the very descriptive stop code `ACPI BIOS ERROR`.
>
> I've enabled bootdebug on the USB stick using the following:
>
> bcdedit /store H:\boot\bcd /bootdebug {bootmgr} on
> bcdedit /store H:\boot\bcd /bootdebug {default} on
> bcdedit /store H:\boot\bcd /debug {debug} on
>
> Here is the BCD:
>
> C:\Windows\system32>bcdedit /store h:\boot\bcd
> Windows Boot Manager
>
> identifier {bootmgr}
> description Windows Boot Manager
> locale en-US
> inherit {globalsettings}
> bootdebug Yes
> default {default}
> displayorder{default}
> toolsdisplayorder {memdiag}
> timeout 30
>
> Windows Boot Loader
> ---
> identifier {default}
> device
> ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
> path\windows\system32\boot\winload.exe
> description Windows Setup
> locale en-US
> inherit {bootloadersettings}
> bootdebug Yes
> osdevice
> ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
> systemroot \windows
> bootmenupolicy Standard
> detecthal Yes
> winpe Yes
> debug Yes
> ems No
>
> C:\Windows\system32>bcdedit /store h:\boot\bcd /dbgsettings
> debugtype Serial
> debugport 1
> baudrate115200
>
>
> I have also added the SPCR table:
>
> [000h 4]Signature : "SPCR"[Serial Port
> Console Redirection table]
> [004h 0004 4] Table Length : 0050
> [008h 0008 1] Revision : 02
> [009h 0009 1] Checksum : F1
> [00Ah 0010 6] Oem ID : "COREv4"
> [010h 0016 8] Oem Table ID : "COREBOOT"
> [018h 0024 4] Oem Revision : 002A
> [01Ch 0028 4] Asl Compiler ID : "CORE"
> [020h 0032 4]Asl Compiler Revision : 20200925
>
> [024h 0036 1] Interface Type : 00
> [025h 0037 3] Reserved : 00
>
> [028h 0040 12] Serial Port Register : [Generic Address
> Structure]
> [028h 0040 1] Space ID : 00 [SystemMemory]
> [029h 0041 1]Bit Width : 20
> [02Ah 0042 1] Bit Offset : 00
> [02Bh 0043 1] Encoded Access Width : 03 [DWord Access:32]
> [02Ch 0044 8] Address : FEDC9000
>
> [034h 0052 1] Interrupt Type : 03
> [035h 0053 1] PCAT-compatible IRQ : 04
> [036h 0054 4]Interrupt : 0004
> [03Ah 0058 1]Baud Rate : 00
> [03Bh 0059 1] Parity : 00
> [03Ch 0060 1]Stop Bits : 00
> [03Dh 0061 1] Flow Control : 00
> [03Eh 0062 1]Terminal Type : 00
> [04Ch 0076 1] Reserved : 00
> [040h 0064 2]PCI Device ID :
> [042h 0066 2]PCI Vendor ID :
> [044h 0068 1] PCI Bus : 00
> [045h 0069 1] PCI Device : 00
> [046h 0070 1] PCI Function : 00
> [047h 0071 4]PCI Flags :
> [04Bh 0075 1] PCI Segment : 00
> [04Ch 0076 4] Reserved :
>
> And the DBG2 table:
>
> [000h 4]Signature : "DBG2"[Debug Port
> table type 2]
> [004h 0004 4] Table Length : 005C
> [008h 0008 1] Revision : 00
> [009h 0009 1] Checksum : 78
> [00Ah 0010 6] Oem ID : "COREv4"
> [010h 0016 8] Oem Table ID : "COREBOOT"
> [018h 0024 4] Oem Revision :
> [01Ch 0028 4] Asl Compiler ID : "CORE"
> [020h 0032 4]Asl Compiler Revision : 20200925
>
> [024h 0036 4] Info Offset : 002C
> [028h 0040 4] Info Count : 0001
>
> [02Ch 0044 1] Revision : 00
> [02Dh 0045 2] Length : 0030
> [02Fh 0047
[coreboot] Questions about ASRock H110M-DVS
Hi all, I read on Coreboot webpage that this board is in almost full working state https://doc.coreboot.org/mainboard/asrock/h110m-dvs.html . The CPU supported by this board is Kaby Lake which is quite fast for applications. I have a question about the flash chip. The documentation says the flash chip is Macronix MX25L6473E, but is putting in w25q64fvaig flash chip will work too? What about other similar chips, such as GD25B64BPIG? Also, for this board, there are a few variants Asrock Intel H110M-DGS, -DVS, and -HDV. Can I use -DGS for this board? In the documentation, integrated graphics init with libgfxinit (see Known issues) , and VGA is not working. In summary integrated graphics not working, but if I put on a PCIe graphic card, coreboot will work? Also, for this line: I should fill in the actual macaddress ./util/scripts/config --set-str REALTEK_8168_MACADDRESS "xx:xx:xx:xx:xx:xx" For this line, what does this line do? make olddefconfig Thank you so much, ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Questions about Asus A88XM-E
All, I have an Asus A88XM-E, and I am trying to install Coreboot on it. 1 ) The chip that came with the board says "GD25Q64(B)" (8192 kB, SPI). I think the chip definitely broken somehow. Everytime I tried to flashrom, it says Erasing and writing flash chip... FAILED at 0x! Expected=0xff, Found=0x00, failed byte count from 0x-0x0fff: 0xd0c ERASE FAILED! when I tried sudo flashrom -w build/coreboot.rom --programmer ch341a_spi, it says Verifying flash... FAILED at 0x! Expected=0x5f, Found=0xff, failed byte count from 0x-0x007f: 0xb5 Your flash chip is in an unknown state. I am having a hard time flashing back to original bios as well. Can I buy W25Q64FVAIG to replace? The chip says GD25B64BP1G . Is that caused by using 5 V to be broken? I only performed flashrom -w and flashrom -r . 2) For configuration, I copied this configuration: https://review.coreboot.org/cgit/board-status.git/tree/asus/a88xm-e/4.12-3285-ga2118c7b54/2020-10-15T00_01_02Z/config.short.txt? to .config and added the board. I have exported the vga bios from Linux using: cp /sys/devices/pci:00/:00:01.0/rom vgabios.bin . The above config does not work with make, it tries to go to a webpage for secondary payload, and that webpage is changed. Removing those two lines CONFIG_COREINFO_SECONDARY_PAYLOAD=y && CONFIG_TINT_SECONDARY_PAYLOAD=y will let me build the rom. When I do sudo flashrom -w build/coreboot.rom --programmer ch341a_spi, it sometimes says write done: Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x! Expected=0x5f, Found=0xff, failed byte count from 0x-0x007f: 0xb5 Your flash chip is in an unknown state. When I boot with Coreboot, I see a black screen. I renamed vgabios.bin to pci1002,990c.rom, and I put that file in the ~/Coreboot/ folder. Thanks for helping out, ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Debugging Windows 10 BSOD
Stoney has the same issue, pretty sure it's related to a memory
address range being incorrectly marked or something similar (based on
the DWORD output of the BSOD), but never bothered to troubleshoot
On Wed, Jan 13, 2021 at 4:21 PM Raul Rangel wrote:
>
> I'm trying to boot the Windows 10 Installer on a picasso based device using
> coreboot + tianocore. I keep getting a BSOD after the windows logo shows with
> the very descriptive stop code `ACPI BIOS ERROR`.
>
> I've enabled bootdebug on the USB stick using the following:
>
> bcdedit /store H:\boot\bcd /bootdebug {bootmgr} on
> bcdedit /store H:\boot\bcd /bootdebug {default} on
> bcdedit /store H:\boot\bcd /debug {debug} on
>
> Here is the BCD:
>
> C:\Windows\system32>bcdedit /store h:\boot\bcd
> Windows Boot Manager
>
> identifier {bootmgr}
> description Windows Boot Manager
> locale en-US
> inherit {globalsettings}
> bootdebug Yes
> default {default}
> displayorder{default}
> toolsdisplayorder {memdiag}
> timeout 30
>
> Windows Boot Loader
> ---
> identifier {default}
> device
> ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
> path\windows\system32\boot\winload.exe
> description Windows Setup
> locale en-US
> inherit {bootloadersettings}
> bootdebug Yes
> osdevice
> ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
> systemroot \windows
> bootmenupolicy Standard
> detecthal Yes
> winpe Yes
> debug Yes
> ems No
>
> C:\Windows\system32>bcdedit /store h:\boot\bcd /dbgsettings
> debugtype Serial
> debugport 1
> baudrate115200
>
>
> I have also added the SPCR table:
>
> [000h 4]Signature : "SPCR"[Serial Port
> Console Redirection table]
> [004h 0004 4] Table Length : 0050
> [008h 0008 1] Revision : 02
> [009h 0009 1] Checksum : F1
> [00Ah 0010 6] Oem ID : "COREv4"
> [010h 0016 8] Oem Table ID : "COREBOOT"
> [018h 0024 4] Oem Revision : 002A
> [01Ch 0028 4] Asl Compiler ID : "CORE"
> [020h 0032 4]Asl Compiler Revision : 20200925
>
> [024h 0036 1] Interface Type : 00
> [025h 0037 3] Reserved : 00
>
> [028h 0040 12] Serial Port Register : [Generic Address Structure]
> [028h 0040 1] Space ID : 00 [SystemMemory]
> [029h 0041 1]Bit Width : 20
> [02Ah 0042 1] Bit Offset : 00
> [02Bh 0043 1] Encoded Access Width : 03 [DWord Access:32]
> [02Ch 0044 8] Address : FEDC9000
>
> [034h 0052 1] Interrupt Type : 03
> [035h 0053 1] PCAT-compatible IRQ : 04
> [036h 0054 4]Interrupt : 0004
> [03Ah 0058 1]Baud Rate : 00
> [03Bh 0059 1] Parity : 00
> [03Ch 0060 1]Stop Bits : 00
> [03Dh 0061 1] Flow Control : 00
> [03Eh 0062 1]Terminal Type : 00
> [04Ch 0076 1] Reserved : 00
> [040h 0064 2]PCI Device ID :
> [042h 0066 2]PCI Vendor ID :
> [044h 0068 1] PCI Bus : 00
> [045h 0069 1] PCI Device : 00
> [046h 0070 1] PCI Function : 00
> [047h 0071 4]PCI Flags :
> [04Bh 0075 1] PCI Segment : 00
> [04Ch 0076 4] Reserved :
>
> And the DBG2 table:
>
> [000h 4]Signature : "DBG2"[Debug Port
> table type 2]
> [004h 0004 4] Table Length : 005C
> [008h 0008 1] Revision : 00
> [009h 0009 1] Checksum : 78
> [00Ah 0010 6] Oem ID : "COREv4"
> [010h 0016 8] Oem Table ID : "COREBOOT"
> [018h 0024 4] Oem Revision :
> [01Ch 0028 4] Asl Compiler ID : "CORE"
> [020h 0032 4]Asl Compiler Revision : 20200925
>
> [024h 0036 4] Info Offset : 002C
> [028h 0040 4] Info Count : 0001
>
> [02Ch 0044 1]
[coreboot] Debugging Windows 10 BSOD
I'm trying to boot the Windows 10 Installer on a picasso based device using
coreboot + tianocore. I keep getting a BSOD after the windows logo shows
with the very descriptive stop code `ACPI BIOS ERROR`.
I've enabled bootdebug on the USB stick using the following:
bcdedit /store H:\boot\bcd /bootdebug {bootmgr} on
bcdedit /store H:\boot\bcd /bootdebug {default} on
bcdedit /store H:\boot\bcd /debug {debug} on
Here is the BCD:
C:\Windows\system32>bcdedit /store h:\boot\bcd
Windows Boot Manager
identifier {bootmgr}
description Windows Boot Manager
locale en-US
inherit {globalsettings}
bootdebug Yes
default {default}
displayorder{default}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
---
identifier {default}
device
ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path\windows\system32\boot\winload.exe
description Windows Setup
locale en-US
inherit {bootloadersettings}
bootdebug Yes
osdevice
ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot \windows
bootmenupolicy Standard
detecthal Yes
winpe Yes
debug Yes
ems No
C:\Windows\system32>bcdedit /store h:\boot\bcd /dbgsettings
debugtype Serial
debugport 1
baudrate115200
I have also added the SPCR table:
[000h 4]Signature : "SPCR"[Serial Port
Console Redirection table]
[004h 0004 4] Table Length : 0050
[008h 0008 1] Revision : 02
[009h 0009 1] Checksum : F1
[00Ah 0010 6] Oem ID : "COREv4"
[010h 0016 8] Oem Table ID : "COREBOOT"
[018h 0024 4] Oem Revision : 002A
[01Ch 0028 4] Asl Compiler ID : "CORE"
[020h 0032 4]Asl Compiler Revision : 20200925
[024h 0036 1] Interface Type : 00
[025h 0037 3] Reserved : 00
[028h 0040 12] Serial Port Register : [Generic Address
Structure]
[028h 0040 1] Space ID : 00 [SystemMemory]
[029h 0041 1]Bit Width : 20
[02Ah 0042 1] Bit Offset : 00
[02Bh 0043 1] Encoded Access Width : 03 [DWord Access:32]
[02Ch 0044 8] Address : FEDC9000
[034h 0052 1] Interrupt Type : 03
[035h 0053 1] PCAT-compatible IRQ : 04
[036h 0054 4]Interrupt : 0004
[03Ah 0058 1]Baud Rate : 00
[03Bh 0059 1] Parity : 00
[03Ch 0060 1]Stop Bits : 00
[03Dh 0061 1] Flow Control : 00
[03Eh 0062 1]Terminal Type : 00
[04Ch 0076 1] Reserved : 00
[040h 0064 2]PCI Device ID :
[042h 0066 2]PCI Vendor ID :
[044h 0068 1] PCI Bus : 00
[045h 0069 1] PCI Device : 00
[046h 0070 1] PCI Function : 00
[047h 0071 4]PCI Flags :
[04Bh 0075 1] PCI Segment : 00
[04Ch 0076 4] Reserved :
And the DBG2 table:
[000h 4]Signature : "DBG2"[Debug Port
table type 2]
[004h 0004 4] Table Length : 005C
[008h 0008 1] Revision : 00
[009h 0009 1] Checksum : 78
[00Ah 0010 6] Oem ID : "COREv4"
[010h 0016 8] Oem Table ID : "COREBOOT"
[018h 0024 4] Oem Revision :
[01Ch 0028 4] Asl Compiler ID : "CORE"
[020h 0032 4]Asl Compiler Revision : 20200925
[024h 0036 4] Info Offset : 002C
[028h 0040 4] Info Count : 0001
[02Ch 0044 1] Revision : 00
[02Dh 0045 2] Length : 0030
[02Fh 0047 1] Register Count : 01
[030h 0048 2] Namepath Length : 000A
[032h 0050 2] Namepath Offset : 0026
[034h 0052 2] OEM Data Length : [Optional field not
present]
[036h 0054 2] OEM Data Offset : [Optional field not
present]
[038h 0056 2]Port Type : 8000
[03Ah
[coreboot] Tooling of choice for coordinating and running the coreboot leadership meeting
Hi everybody, when announcing today's leadership meeting on IRC I got some replies to the tune of "oh no, Google!" as the meeting minutes are recorded on Google Docs and the meeting itself is held using Google Meet. Note that both are set up to be usable without a Google account, so the impact on users should be limited. That said, if that's a real concern that prevents people from participating who otherwise would like to chime in, we need a solution. To avoid spending too much time on something that may not actually be a problem, I'm asking you: 1. To consider if you care about the leadership meeting (otherwise, please don't create extra work to prove a point about "big tech", software licenses or whatever) 2. If using these two tools for this specific purpose is a problem for you 3. What your ideal alternative solution would look like 4. How your solution would be implemented 5. Present the result of 4 to the list :-) Note that this project, its developers, contributors and maintainers aren't in the business of managing servers or communication suites (although we spend a fair amount of time and money on running coreboot.org to ensure people can contribute with little restrictions: apart from that meeting, everything we do is self-hosted!) so a proposal should be low maintenance for us. This means: running the meeting must not be a hassle (we tried a fair amount of open tools for running the calls: jitsi, mumble and several others, and they fell flat, for example because they sent video streams from everybody to everybody. n^2 traffic growth isn't great), available for the long term (if you offer to run the necessary services for us that's nice, but we'd prefer not to have to change routines again 3 months down the road because your priorities shifted, so any such offer should give us the impression that it's available for the foreseeable future) and not just exchanging one "troublesome" vendor for another (I guess we'll see what "troublesome" means to people in the community.) As for capacity: The meetings take one hour every 14 days. Today's meeting had 17 participants and I think some meetings had a few more folks joining. Those are discussions not presentations, so high-latency streaming options (such as PeerTube's new live stream feature) won't work. Thanks, Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] question about Coreboot
Hello, I search on the internet about coreboot and Qubes os. I use a Lenovo ThinkPadT460P i7 16 gb and i have install Qubes OS. Is there a compatible version of Coreboor for a Lenovo ThinkPadT460P i7. I found the X220 and X230. Ramon ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
