Le jeu. 4 juin 2020 à 21:36, HacKurx <[email protected]> a écrit : > > Le 2020-06-04 12:49, Paul Menzel a écrit : > > Thank you for the report. > > Thank you for your answer. > > > Am 04.06.20 um 11:26 schrieb HacKurx: > >> Good morning, everyone, > >> > >> I hadn't updated my coreboot version for a long time on my Asrock > >> E350M1 card because of lack of time and because this one was on a very > > > > I guess you mean *board* and not *card*? > > Motherboard. Sorry for English ;) > > >> stable version. While trying to test the current 4.12 version, I > >> encountered problems in Debian 10. > > > > What coreboot version did you use before? > > Before, coreboot-4.2-20160128 with SeaBIOS-1.9.0 > > But because of the problem, I've been testing coreboot-4.5-20170204 > (commit 8a06cc7ec8 util/ifdtool: Fix ICH Gbe unlock) with > SeaBIOS-1.13.0-20200603 which works well (it's the commit before the > one I had to reverse). > > >> Indeed, there is a bad graphical detection, the resolution of my hdmi > >> output went from 1360x768 to 720x400 pixels. > >> Xorg indicates that the drm device cannot be opened : > >> (EE) open /dev/dri/card0: No such file or directory > >> > >> I once had a Oops kernel message: > >> https://pastebin.com/uZLZyYrq > > > > For the future, please attach the logs to the message, so people can > > read it offline. > > All right. > > >> I manage to restore normal working in coreboot 4.12-git by removing the commits: > >> a5c2ac6256d0dae112b24c422d1270919acb6321 "x86/acpi: Add VFCT table" > >> 6f978cfd1ab6a57e5729e19bed3df7702c4f09cb "x86/acpi: Use initialized > >> VBIOS in VFCT table" > > > > I cannot remember seeing this on my board [1], but I am only using the > > VGA adapter (shouldn’t matter). > > > > [ 1.552912] [drm] Found smc ucode version: 0x00010601 > > In linux : > drivers/gpu/drm/radeon/sumo_dpm.c: DRM_INFO("Found smc ucode > version: 0x%08x\n", pi->fw_version); > > > These commits have been present since coreboot 4.6, and I have not > > seen this. It just provides the VGA Optiom ROM/Video BIOS to the > > graphics driver via ACPI. > > I just change the coreboot version without changing my OS. As soon as > I overrun a version with this commit, I get a display problem. > > > Do you have the AMD graphics firmware files installed under > > `/lib/firmware/radeon`? > > Yes. We can even see the loading the dmesg: > [ 4.816786] [drm] Loading PALM Microcode > [ 4.816872] radeon 0000:00:01.0: firmware: direct-loading firmware > radeon/PALM_pfp.bin > [ 4.816909] radeon 0000:00:01.0: firmware: direct-loading firmware > radeon/PALM_me.bin > [ 4.816941] radeon 0000:00:01.0: firmware: direct-loading firmware > radeon/SUMO_rlc.bin > [ 4.816957] [drm] Found smc ucode version: 0x00010601 > [ 4.817038] BUG: unable to handle kernel NULL pointer dereference > at 0000000000000000 > > md5sum /lib/firmware/radeon/* > ... > > > Please attach your coreboot configuration (`defconfig` generated by > > `make savedefconfig`), and the output of `build/cbfstool > > build/coreboot.rom print`. > > $ cat defconfig > CONFIG_VENDOR_ASROCK=y > CONFIG_VGA_BIOS=y > CONFIG_BOARD_ASROCK_E350M1=y > CONFIG_DRIVERS_PS2_KEYBOARD=y > CONFIG_SEABIOS_MASTER=y > CONFIG_COREINFO_SECONDARY_PAYLOAD=y > > $ build/cbfstool build/coreboot.rom > FMAP REGION: COREBOOT > Name Offset Type Size Comp > cbfs master header 0x0 cbfs header 32 none > fallback/romstage 0x80 stage 185300 none > fallback/ramstage 0x2d4c0 stage 117630 none > config 0x4a080 raw 219 none > revision 0x4a1c0 raw 674 none > fallback/dsdt.aml 0x4a4c0 raw 9607 none > cmos_layout.bin 0x4cac0 cmos_layout 1228 none > pci1002,9802.rom 0x4d000 optionrom 57856 none > fallback/postcar 0x5b280 stage 16372 none > img/coreinfo 0x5f2c0 simple elf 52655 none > fallback/payload 0x6c0c0 simple elf 69955 none > payload_config 0x7d240 raw 1621 none > payload_revision 0x7d900 raw 238 none > (empty) 0x7da40 null 3613528 none > s3nv 0x3efdc0 raw 8192 none > (empty) 0x3f1e00 null 24472 none > bootblock 0x3f7dc0 bootblock 32768 none > > > Anyway, I guess it could be a problem in Linux 4.19.118. Could you > > please try a recent Linux kernel from the Debian backports repository, > > or another way? If that problem is fixed in newer versions, the Linux > > stable folks and Debian Linux kernel folks should backport that > > commit. > > I'm willing to redo a test with a newer kernel, but I had the same > problem with Ubuntu 20.04 LTS (Linux 5.4.0-29-generic). > > Thanks. > > Best regards, > > Loic
Nothing to do, debian can't boot properly with kernels 5.4 and 5.7 [1]. I can only reach lightdm using nomodeset (but i have a bad graphic resolution). I tried with your kernel parameters and VGA but it doesn't change anything. I compared with the original bios, there was no VFCT table: --- /home/loic/Bureau/ASROCK +++ /home/loic/Bureau/coreboot @@ -1,18 +1,17 @@ -DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./E350M1, BIOS P2.10 03/06/2014 +DMI: ASROCK E350M1/E350M1, BIOS 4.12-503-gdedbf63522 06/04/2020 ... ACPI: Early table checksum verification disabled -ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA) -ACPI: XSDT 0x00000000AF467078 00006C (v01 ALASKA A M I 01072009 AMI 00010013) -ACPI: FACP 0x00000000AF46C878 0000F4 (v04 ALASKA A M I 01072009 AMI 00010013) -ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180810/tbfadt-624) -ACPI: DSDT 0x00000000AF467178 0056FE (v02 ALASKA A M I 00000000 INTL 20051117) -ACPI: FACS 0x00000000AF474F80 000040 -ACPI: APIC 0x00000000AF46C970 000062 (v03 ALASKA A M I 01072009 AMI 00010013) -ACPI: FPDT 0x00000000AF46C9D8 000044 (v01 ALASKA A M I 01072009 AMI 00010013) -ACPI: MCFG 0x00000000AF46CA20 00003C (v01 ALASKA A M I 01072009 MSFT 00010013) -ACPI: AAFT 0x00000000AF46CA60 000042 (v01 ALASKA OEMAAFT 01072009 MSFT 00000097) -ACPI: HPET 0x00000000AF46CAA8 000038 (v01 ALASKA A M I 01072009 AMI 00000005) -ACPI: SSDT 0x00000000AF46CAE0 0003DE (v01 AMD POWERNOW 00000001 AMD 00000001) -ACPI: SSDT 0x00000000AF46CEC0 00168E (v02 AMD ALIB 00000001 MSFT 04000000) -ACPI: BGRT 0x00000000AF46E550 000038 (v00 ALASKA A M I 01072009 AMI 00010013) +ACPI: RSDP 0x00000000000F6250 000024 (v02 COREv4) +ACPI: XSDT 0x0000000067E560E0 000064 (v01 COREv4 COREBOOT 00000000 CORE 20200110) +ACPI: FACP 0x0000000067E58810 000114 (v06 COREv4 COREBOOT 00000000 CORE 20200110) +ACPI: DSDT 0x0000000067E56280 002587 (v02 COREv4 COREBOOT 00010001 INTL 20200110) +ACPI: FACS 0x0000000067E56240 000040 +ACPI: FACS 0x0000000067E56240 000040 +ACPI: SSDT 0x0000000067E58930 00008A (v02 COREv4 COREBOOT 0000002A CORE 20200110) +ACPI: APIC 0x0000000067E589C0 00005C (v03 COREv4 COREBOOT 00000000 CORE 20200110) +ACPI: HEST 0x0000000067E58A20 000028 (v01 COREv4 COREBOOT 00000000 CORE 20200110) +ACPI: SSDT 0x0000000067E58A50 00168E (v02 AMD ALIB 00000001 MSFT 04000000) +ACPI: SSDT 0x0000000067E5A0E0 0003DE (v01 AMD POWERNOW 00000001 AMD 00000001) +ACPI: VFCT 0x0000000067E5A4C0 00E269 (v01 COREv4 COREBOOT 00000000 CORE 20200110) +ACPI: HPET 0x0000000067E68730 000038 (v01 COREv4 COREBOOT 00000000 CORE 20200110) ACPI: Local APIC address 0xfee00000 There must therefore be an incompatibility. 1] https://framapic.org/gallery#ML9XNF3UG1oW/w55DEPZ9MtMi.JPG,fArYZK0PuHU0/JjYNdnBUXhYj.JPG,3xmtCbhLNeh4/Pe5qLNx5tM7U.JPG,mhdg5qel3gIY/PQxggJgwh6lN.JPG,OHdEgK3jDzqn/7jftoAoHuTQo.JPG -- Best regards, HacKurx (Loic)
_______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
