> That is somehow strange. That code should only do anything if the "enable_dual_graphics" NVRAM option is set to true. The default for that option is false. Since removing the code makes a difference for you I guess that somehow your system has this NVRAM option set to true, maybe the defaults were not written successfully? Could you check this?
I just did a check of sudo nvramtool -a and it shows enable_dual_graphics = Disable.
> You could perhaps compare the ACPI tables between vendor BIOS and coreboot. It's possible that the speaker node was simply forgotten in coreboot. Maybe it just needs to be added to the coreboot ACPI tables.
A redditer found a workaround for the speaker issue. By setting the multiple output in the Realtek's control panel, the speaker works. But it's still good if this can be fixed like normally. I have attached my autoport logs and generated source files both using vendor bios and coreboot. Also, the alsa-info.sh logs are included.
> This might be easy to fix. What are the required IDs and what are the current ones with coreboot?
The normal id on vendor bios is: PCI\VEN_10EC&DEV_5227&SUBSYS_220E17AA but on coreboot it becomes PCI\VEN_10EC&DEV_5227&SUBSYS_522710EC . It seems wired because the coreboot's devicetree.cb file did have a line subsystemid 0x17aa 0x220e inherit.
>> PCI Data Acquisition and Signal Processing Controller
>> PCI\VEN_8086&DEV_0C03&SUBSYS_00000000&REV_06\3&B1BFB68...
> No idea what this is.
I searched online on this VEN and DEV it seems it's the Intel DPTF stuff, but I don't know is it doing anything useful? I found some overclock fourm suggest to disable it. How to disable it in coreboot?
I also found another issue when i use a engineering sample cpu. When I use libgfxinit, the es cpu can boot in Windows but not in Manjaro. When I use extracted VGA BIOS, the es cpu can boot in Manjaro but not Windows... I know es cpu is known to have bugs, but it can boot in both using vendor bios. I have attached the journalctl logs if someone could help me.
-
Mar 30, 2020, 02:03 by peter@stuge.se:
Hi Dalao,
Dalao via coreboot wrote:
With the help from reddit, it works now!
First of all, congratulations on getting it to work! Very well done.
The reason is I need to remove the code added by this patch.
https://review.coreboot.org/c/coreboot/+/38723/6/src/mainboard/lenovo/t440p/romstage.c
> This patch is for dGPU, my model does not have dGPU.
I didn't thought it would affect my model, but removed it Win10 works
both using SeaBIOS or Tianocore.
That is somehow strange. That code should only do anything if the
"enable_dual_graphics" NVRAM option is set to true. The default for that
option is false. Since removing the code makes a difference for you I
guess that somehow your system has this NVRAM option set to true,
maybe the defaults were not written successfully? Could you check this?
There are some issues with Win10:
1, The first thing I notice is there is no sound output. The system
speaker device present in vendor BIOS is missing in coreboot:
ACPI\PNP0800\4&D8657FD&0
You could perhaps compare the ACPI tables between vendor BIOS and
coreboot. It's possible that the speaker node was simply forgotten in
coreboot. Maybe it just needs to be added to the coreboot ACPI tables.
2, Some FN-keys (FN-F4, Fn-F7 to F12) does not work.
This is also ACPI related, but I'm afraid I don't know more details.
3, Card reader's subsystemid is wrong and driver can't be installed.
This might be easy to fix. What are the required IDs and what are the
current ones with coreboot?
4, Two more devices which were not present in vendor BIOS but are present in coreboot, and these driver can't not be installed:
High Definition Audio Controller PCI\VEN_8086&DEV_8C20&SUBSYS_220E17AA&REV_05\3&B1BFB68...
This is the built-in sound card, so probably this is the reason you
get no sound. I wonder why this PCI device is different with coreboot.
Could you compare with vendor BIOS? Maybe subsystem IDs again?
PCI Data Acquisition and Signal Processing Controller PCI\VEN_8086&DEV_0C03&SUBSYS_00000000&REV_06\3&B1BFB68...
No idea what this is.
5, There is a Diagnostic Policy Service kept running.
Sorry, also no idea about that one.
//Peter
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org