Re: [coreboot] T400 screen issue / EDID handling
Dear Kroms, Am Montag, den 13.07.2015, 09:43 +0200 schrieb kr...@posteo.be: […] There are two more things two do. 1. Contact the Linux i915 folks and ask them, if the module is able to detect the configuration itself and does not rely on the firmware or if there is a way to override that setting from the Linux command line. Who is going to do this? Is this [1] the right community? I am not sure, if I am able to explain it right. If you want me to do this, what do you mean exactly with the module, is it i915? Yes i915 and it’d be great if you could do it. At least the second question should be answered. Looking at `/sbin/modinfo i915` it shows that there is such an option already. parm: lvds_channel_mode:Specify LVDS channel mode (0=probe BIOS [default], 1=single-channel, 2=dual-channel) (int) So you could add `i915.lvds_channel_mode=2`, I think, to the Linux command line and see if Linux is able to initialize your system. On [2], is written: Linux (kernel) has its own init code (including EDID parsing). The current suspicion is that coreboot's own initialization code has buggy EDID parsing in some way, such that the proper settings for the panel are not used, leading to the failure. Please tell me, if I understand it right: The kernel module should not rely on coreboot concerning the settings for the display and you want to know, if the kernel module is able to get the needed information direct from the display (EDID)? If this is possible, you want to know, if this is configurable with the Linux command line? Means Linux command line the same as kernel command line? Yes. But I am not sure if it’s related to EDID parsing at all. coreboot just hard codes it. 2. Improve coreboot so that the LVDS link configuration is detected during runtime as the vendor firmware (VGA Option ROM/Video BIOS(?)) does. While I am learning a lot of things working on this issue, this is far above my skills. No problem. Maybe somebody else will do it. Thanks, Paul [1] https://01.org/linuxgraphics/community/kernel [2] http://libreboot.org/docs/hcl/gm45_lcd.html signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear coreboot community, tty0_ in #coreboot/#libreboot found a partial fix. See: http://libreboot.org/docs/hcl/gm45_lcd.html Setting gfx.lvds_dual_channel = 1 is a workaround so that the kernel driver (i915) pickups the right value that coreboot had set. But there are few things to be fixed: 1) No video (fb) during payload(grub) for gm45 (T500) with lcd with dual channel lvds, up to the point where the kernel installs the i915 driver at which point i get working screen. (For single channel lvds controllers all works ok - there is video during payload). 2) There are devices with same model that come both variants (i.e T500) with a single or dual channel lvds . I dont know if there is (currently) way in coreboot (without using the vbios blob) to detect this dynamically (in runtime) instead of setting it in the devicetree. I am willing to work on this problems, but my knowledge is limited in this area. So, any hints on how to proceed, links to specs/docs, etc are welcome. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear Kroms, Am Sonntag, den 12.07.2015, 22:17 +0200 schrieb kr...@posteo.be: Thank you! Unfortunately, it also does not contain the Git revision. #define COREBOOT_ORIGIN_GIT_REVISION Unknown I dont´t know if you noticed that Francis wrote in this thread on Sun Jul 5 16:57:30 CEST 2015: Libreboot builds coreboot without the .git directory, so it's not possible to get the coreboot revision. You can find out what version of coreboot it is by looking at resources/scripts/helpers/download/coreboot He is using libreboot 20150518, so the coreboot revision that he's using is e19c8b0091022ae3f490601aed0c290cd5171b79 Thank you for looking this up! commit e19c8b0091022ae3f490601aed0c290cd5171b79 Author: Alexander Couzens lyn...@fe80.eu AuthorDate: Thu Apr 2 23:20:45 2015 +0200 Commit: Peter Stuge pe...@stuge.se CommitDate: Sun Apr 5 04:07:25 2015 +0200 acpi: protect acpi generators from PRE_RAM SMM 1. Try to use a newer Linux kernel. I updated the Kernel to 4.1.2 from Debian experimental. 2. Turn on debugging of the Linux i915 module [1]. 3. Please also post a log with debugging enabled when using the vendor firmware. Please find attached the two outputs (libreboot and lenovo_bios) from dmesg with debugging enabled. Awesome! Thank you very much. $ grep 'drm:' dmesg_debug_libreboot.txt [ 11.647383] [drm:i915_dump_device_info] i915 device info: gen=4, pciid=0x2a42 rev=0x07 flags=is_mobile,need_gfx_hws,is_g4x,has_fbc,has_pipe_cxsr,has_hotplug,supports_tv, [ 11.647410] [drm:intel_detect_pch] No PCH found. [ 11.647416] [drm:i915_gem_gtt_init] GMADR size = 256M [ 11.647418] [drm:i915_gem_gtt_init] GTT stolen size = 32M [ 11.647419] [drm:i915_gem_gtt_init] ppgtt mode: 0 [ 11.648615] [drm:intel_opregion_setup] graphic opregion physical addr: 0x0 [ 11.648618] [drm:intel_opregion_setup] ACPI OpRegion not supported! [ 11.648665] [drm:intel_device_info_runtime_init] slice total: 0 [ 11.648666] [drm:intel_device_info_runtime_init] subslice total: 0 [ 11.648668] [drm:intel_device_info_runtime_init] subslice per slice: 0 [ 11.648670] [drm:intel_device_info_runtime_init] EU total: 0 [ 11.648671] [drm:intel_device_info_runtime_init] EU per subslice: 0 [ 11.648672] [drm:intel_device_info_runtime_init] has slice power gating: n [ 11.648674] [drm:intel_device_info_runtime_init] has subslice power gating: n [ 11.648676] [drm:intel_device_info_runtime_init] has EU power gating: n [ 11.648680] [drm:init_vbt_defaults] Set default to SSC at 10 kHz [ 11.648684] [drm:validate_vbt] Using VBT from PCI ROM: $VBT IRONLAKE-MOBILEd [ 11.648687] [drm:parse_general_features] BDB_GENERAL_FEATURES int_tv_support 0 int_crt_support 1 lvds_use_ssc 1 lvds_ssc_freq 96000 display_clock_mode 0 fdi_rx_polarity_inverted 0 [ 11.648689] [drm:parse_sdvo_device_mapping] No general definition block is found, unable to construct sdvo mapping. [ 11.648691] [drm:parse_device_mapping] No general definition block is found, no devices defined. [ 11.648693] [drm:parse_psr] No PSR BDB found. [ 11.648700] [drm:intel_dsm_pci_probe] no _DSM method for intel device [ 11.648707] [drm:i915_gem_init_stolen] found 33554432 bytes of stolen memory at be00 [ 11.648710] [drm:intel_display_power_get] enabling always-on [ 11.648744] [drm:intel_modeset_init] 2 display pipes available. [ 11.648753] [drm:intel_modeset_init] pipe A sprite A init failed: -19 [ 11.648760] [drm:intel_modeset_init] pipe B sprite B init failed: -19 [ 11.718062] [drm:intel_lvds_init] using preferred mode from EDID: [ 11.718069] [drm:drm_mode_debug_printmodeline] Modeline 27:1440x900 60 101600 1440 1488 1520 1792 900 903 909 945 0x48 0xa [ 11.718075] [drm:intel_lvds_init] detected single-link lvds configuration [ 11.718147] [drm:intel_panel_setup_backlight] Connector LVDS-1 backlight initialized, enabled, brightness 98/98 [ 11.718205] [drm:intel_setup_outputs] probing SDVOB [ 11.718209] [drm:intel_gmbus_force_bit] enabling bit-banging on i915 gmbus dpb. force bit now 1 [ 11.727609] [drm:intel_sdvo_read_byte] i2c transfer returned -6 [ 11.727611] [drm:intel_sdvo_init] No SDVO device found on SDVOB [ 11.727642] [drm:intel_gmbus_force_bit] disabling bit-banging on i915 gmbus dpb. force bit now 0 [ 11.727644] [drm:intel_setup_outputs] probing HDMI on SDVOB [ 11.727701] [drm:intel_dp_init_connector] Adding DP connector on port B [ 11.727743] [drm:intel_dp_aux_init] registering DPDDC-B bus for card0-DP-1 [ 11.727781] [drm:intel_setup_outputs] probing SDVOC [ 11.727783] [drm:intel_gmbus_force_bit] enabling bit-banging on i915 gmbus dpb. force bit now 1 [ 11.737209] [drm:intel_sdvo_read_byte] i2c transfer returned -6 [
Re: [coreboot] T400 screen issue / EDID handling
Dear Paul, As you can see, the vendor firmware detects a dual-link LVDS configuration. [drm:intel_lvds_init] detected dual-link lvds configuration With coreboot a single-link LVDS configuration is detected. [drm:intel_lvds_init] detected single-link lvds configuration Thank you for checking the logs! Francis Rowe wrote to the list, that this is configured during compile time in coreboot [1][2]. You'd need to rebuild your image. Then you should have at least graphics when Linux started. Yes, I am very happy that they found a workaround. This is the next thing I am going to do. Because I re-flashed the Lenovo Bios I have to disassemble the T400 again to reach the flash chip. I wanted to provide you with the logs first. There are two more things two do. 1. Contact the Linux i915 folks and ask them, if the module is able to detect the configuration itself and does not rely on the firmware or if there is a way to override that setting from the Linux command line. Who is going to do this? Is this [1 [1]] the right community? I am not sure, if I am able to explain it right. If you want me to do this, what do you mean exactly with the module, is it i915? On [2 [2]], is written: Linux (kernel) has its own init code (including EDID parsing). The current suspicion is that coreboot's own initialization code has buggy EDID parsing in some way, such that the proper settings for the panel are not used, leading to the failure. Please tell me, if I understand it right: The kernel module should not rely on coreboot concerning the settings for the display and you want to know, if the kernel module is able to get the needed information direct from the display (EDID)? If this is possible, you want to know, if this is cofigurable with the Linux command line? Means Linux command line the same as kernel command line? 2. Improve coreboot so that the LVDS link configuration is detected during runtime as the vendor firmware (VGA Option ROM/Video BIOS(?)) does. While I am learning a lot of things working on this issue, this is far above my skills. Best regards, Kroms [1] https://01.org/linuxgraphics/community/kernel [1][2] http://libreboot.org/docs/hcl/gm45_lcd.html [2] [1] Links: -- [1] https://01.org/linuxgraphics/community/kernel [2] http://libreboot.org/docs/hcl/gm45_lcd.html -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear Kroms, I am sorry for the long delay. Am Sonntag, den 05.07.2015, 17:05 +0200 schrieb kr...@posteo.be: It might be in the revision file in CBFS. build/cbfstool build/coreboot.rom extract -n revision -f revision.txt Please find attached the revision.txt. Thank you! Unfortunately, it also does not contain the Git revision. #define COREBOOT_ORIGIN_GIT_REVISION Unknown and Linux - Do you mean the output of dmesg? Indeed, that’s one way of getting them. Please provide the output. It is also attached. I hope the information will help you to get closer to the solution. Thank you! Unfortunately, no useful i915 message are in there. Three things to try and do. 1. Try to use a newer Linux kernel. Trying to fix the Linux kernel is much easier and more likely, if the reports are against the latest version. Do you have a spare disk with a newer Linux kernel installed?Debian Sid/unstable currently ships Linux 4.0.8. Linux 4.1 could be installed from the Debian experimental archives. 2. Turn on debugging of the Linux i915 module [1]. To obtain a dmesg with debug information, add drm.debug=0xe to your kernel command line or, if you have display issues with kernel 4.1 or newer, use drm.debug=0x1e log_buf_len=1M instead. Then, reboot and reproduce the issue again. Make sure to attach the full dmesg all the way from boot. 3. Please also post a log with debugging enabled when using the vendor firmware. Thanks, Paul [1] https://01.org/linuxgraphics/documentation/how-report-bugs signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/07/15 15:27, kr...@posteo.be wrote: Hello, I allready contacted Francis from libreboot and he forwared me to this list, because it seems to be an issue regarding coreboot. I have flashed a Lenovo T400 with libreboot. The T400 has an Intel GPU and I am able to use it with an external display connected to the onboard vga-port. The issue is, that I can't use the internal display, which is an 1440x900 Samusung LTN141WD-L05, EDID dump: https://paste.debian.net/plainh/b3699c60 It seems like the internal screen is powered on while booting but it stays black. Francis assumes that this is due to bugs in how coreboot handles the EDID. Here is an EDID dump of a working display: http://paste.debian.net/plainh/776705d5 Anyone is able to help? Thanks in advance! Dear coreboot community, tty0_ in #coreboot/#libreboot found a partial fix. See: http://libreboot.org/docs/hcl/gm45_lcd.html -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVobEOAAoJEP9Ft0z50c+UJSgH/3tj9DiBbitS1eCgJ98743Ij sARuL4cFbUNMeT6nZmnhMEmv+O8Na9SO2yuvVb/iqcYLzbQc6gGmD8wzIln77c+c jXZ+Tje7RSwwCJvt3gDtXG1UTvnDGthJy+qUh5JqQxyNljSNFUQNCpkZw/vhAgJa aXcxO8w1W7eFRO5ueTR0HqF57JQXjyNBTicfCKqRpRJ/ac93ipbuKQBAIUywjjdD +LD3a31RfEjmd8YpAzEXbvUhl3b4NWTuy0nqQj9amaQGeJKycNSAYisLKqriPZXe r0WW9mfSUWWPTYpTtRREK8uBkKmRF0qMLKZES2B9SiDsZ3RcF0+CRAP+6UTwP+Y= =gxaG -END PGP SIGNATURE- -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear Kroms, Am Samstag, den 04.07.2015, 11:11 +0200 schrieb kr...@posteo.be: I used a pre-compiled libreboot ROM image for flashing my T400: t400_8mb_ukqwerty_vesafb.rom (source: http://mirrors.mit.edu/libreboot/20150518/rom/) I attached most of the requested information, I hope I found the right information: requested information - attached file or remark .config of coreboot - config_t400_8mb_libreboot and the payload - the 4 files beginning with grub_ log files from coreboot (cbmem -c) - cbmem_-c Thank you. Unfortunately, I was unable to see anything suspicious in there. Libreboot seems to strip of the coreboot revision it uses from the banner, which is not good. It might be in the revision file in CBFS. build/cbfstool build/coreboot.rom extract -n revision -f revision.txt the payload - I dont know to get or find it. It is GRUB. Unfortunately, I do not see GRUB’s debug messages in CBMEM. and Linux - Do you mean the output of dmesg? Indeed, that’s one way of getting them. Please provide the output. […] Thanks, Paul PS: It’s quite common to use interleaved posting style [1] on mailing lists. [1] https://en.wikipedia.org/wiki/Posting_style signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thank you. Unfortunately, I was unable to see anything suspicious in there. Libreboot seems to strip of the coreboot revision it uses from the banner, which is not good. It might be in the revision file in CBFS. Libreboot builds coreboot without the .git directory, so it's not possible to get the coreboot revision. You can find out what version of coreboot it is by looking at resources/scripts/helpers/download/coreboot He is using libreboot 20150518, so the coreboot revision that he's using is e19c8b0091022ae3f490601aed0c290cd5171b79 See http://git.savannah.gnu.org/cgit/libreboot.git/tree/resources/scripts/helpers/download/coreboot?id=r20150518fix -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVmUXaAAoJEP9Ft0z50c+UzDwIAIvUK5lpPHveEKdoGeHRIvZ/ wrfTuzqtM2snIT2baypZTpcirxCfcLonr4dntKG4VkL5edxzWTjWpPF855vLyCeQ gLBdGjHlZ+NTyZZDvkPoHJNGaPhoYUaUk/2L6GafUgYBRgxWcOjJs5xyfHk1VU/L BcXFztVKfPM2BDWW0nue8ycdxzo3fTfAwNdCCCFBaypi22eEQXqEt4WNjAxlKbwE Y1VxUn7klMDqP0HYCtWDr2Gmgw58LirZ2ZCq+Q00oae8ZXYIJzpp/qM6si8n25HI lzuU9AHIzDiMQ/hGAuU0J6VOK9uHw+DTgFjWyCgu69DgInA9mfihoQbLd+ro/Lo= =1+ZG -END PGP SIGNATURE- -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear Paul, thank you for looking into the files! It might be in the revision file in CBFS. build/cbfstool build/coreboot.rom extract -n revision -f revision.txt Please find attached the revision.txt. and Linux - Do you mean the output of dmesg? Indeed, that’s one way of getting them. Please provide the output. It is also attached. I hope the information will help you to get closer to the solution. PS: It’s quite common to use interleaved posting style [1] on mailing lists. [1] https://en.wikipedia.org/wiki/Posting_style Thank you for the hint. I will do so, the next time I am posting a link to a mailing-list. Best Regards, Kroms[0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) [0.00] Command line: BOOT_IMAGE=/vmlinuz root=/dev/sda1 rw [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0fff] type 16 [0.00] BIOS-e820: [mem 0x1000-0x0009] usable [0.00] BIOS-e820: [mem 0x000c-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbdaabfff] usable [0.00] BIOS-e820: [mem 0xbdaac000-0xbdbf] type 16 [0.00] BIOS-e820: [mem 0xbdc0-0xbfff] reserved [0.00] BIOS-e820: [mem 0xf000-0xf3ff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00023fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: LENOVO 6475ZQQ/6475ZQQ, BIOS CBET4000 4.0 05/18/2015 [0.00] e820: update [mem 0x-0x0fff] usable == reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] AGP: No AGP bridge found [0.00] e820: last_pfn = 0x24 max_arch_pfn = 0x4 [0.00] MTRR default type: write-back [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-F write-back [0.00] MTRR variable ranges enabled: [0.00] 0 base 0BDC0 mask FFFC0 uncachable [0.00] 1 base 0BE00 mask FFE00 uncachable [0.00] 2 base 0C000 mask FF000 uncachable [0.00] 3 base 0D000 mask FF000 write-combining [0.00] 4 base 0E000 mask FE000 uncachable [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: last_pfn = 0xbdaac max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000f-0x000f000f] mapped at [880f] [0.00] Base memory trampoline at [88099000] 99000 size 24576 [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] [mem 0x-0x000f] page 4k [0.00] BRK [0x01af4000, 0x01af4fff] PGTABLE [0.00] BRK [0x01af5000, 0x01af5fff] PGTABLE [0.00] BRK [0x01af6000, 0x01af6fff] PGTABLE [0.00] init_memory_mapping: [mem 0x23fe0-0x23fff] [0.00] [mem 0x23fe0-0x23fff] page 2M [0.00] BRK [0x01af7000, 0x01af7fff] PGTABLE [0.00] init_memory_mapping: [mem 0x23c00-0x23fdf] [0.00] [mem 0x23c00-0x23fdf] page 2M [0.00] init_memory_mapping: [mem 0x2-0x23bff] [0.00] [mem 0x2-0x23bff] page 2M [0.00] init_memory_mapping: [mem 0x0010-0xbdaabfff] [0.00] [mem 0x0010-0x001f] page 4k [0.00] [mem 0x0020-0xbd9f] page 2M [0.00] [mem 0xbda0-0xbdaabfff] page 4k [0.00] init_memory_mapping: [mem 0x1-0x1] [0.00] [mem 0x1-0x1] page 2M [0.00] BRK [0x01af8000, 0x01af8fff] PGTABLE [0.00] BRK [0x01af9000, 0x01af9fff] PGTABLE [0.00] RAMDISK: [mem 0x3637c000-0x371b5fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F0400 24 (v02 CORE ) [0.00] ACPI: XSDT 0xBDAB60E0 54 (v01 CORE COREBOOT CORE ) [0.00] ACPI: FACP 0xBDAB9A30 F4 (v03 CORE COREBOOT CORE ) [0.00] ACPI: DSDT 0xBDAB6250 0037D5 (v03 COREv4 COREBOOT 20090419 INTL 20150204) [0.00] ACPI: FACS 0xBDAB6210 40 [0.00] ACPI: SSDT 0xBDAB9B30 00034E (v02 CORE COREBOOT 002A CORE 002A) [0.00] ACPI: MCFG 0xBDAB9E80 3C (v01 CORE COREBOOT CORE ) [0.00] ACPI: APIC 0xBDAB9EC0 68 (v01 CORE
Re: [coreboot] T400 screen issue / EDID handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/07/15 15:57, Francis Rowe wrote: Thank you. Unfortunately, I was unable to see anything suspicious in there. Libreboot seems to strip of the coreboot revision it uses from the banner, which is not good. It might be in the revision file in CBFS. Libreboot builds coreboot without the .git directory, so it's not possible to get the coreboot revision. You can find out what version of coreboot it is by looking at resources/scripts/helpers/download/coreboot He is using libreboot 20150518, so the coreboot revision that he's using is e19c8b0091022ae3f490601aed0c290cd5171b79 See http://git.savannah.gnu.org/cgit/libreboot.git/tree/resources/scripts/helpers/download/coreboot?id=r20150518fix Note: this bug also affects coreboot upstream, using no additional patches, from the latest version in the master branch from http://review.coreboot.org/coreboot -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVmUZmAAoJEP9Ft0z50c+UGw8IAMCziSv5jfp078b9lokEapUb kuWPtXAGPrAaZN92kaQRRlGPcp5OF0vAJxhpBPQlMBzl7taizhCb0+BSXKVncusY GL/eXc2eKRt/sYRWCJxM8Eu3uukUH3ybhHLubR/kOmQ1gi2fuzYXbo+qb2ViJ5dZ +wF+lyIHxj9RxCEY2TvuLO7c0MjdduC3GdUmlp9am7P+5qWbFr22lok0VznkZ54B QKorLCxrLPrZnmpZJr1rL0UfkgGZ6uurtK6kbMYhdIsOXTlvgvuu22lnjqKr9fJ2 EwcLWAM9ywq8Aph4HyhEMcVCbj2izVdAURTsK7vGUAwaV7R9s2yfVCLcWmr7mXQ= =71Qg -END PGP SIGNATURE- -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't understand why you're removing the .git directory. But anyhow, you should patch the coreboot version script. The script should take your specific version of your libreboot build script git repo. Please prefix the version with libreboot, it makes all our live easier to know what version is running and from where the version comes from. And btw. this makes your coreboot' build reproducible, which isn't it atm. Libreboot removes all of the blobs from coreboot. In doing so, a diff showing those deletions (therefore, containing the blobs) is shown. The git history in coreboot also shows blobs that have been added or deleted, over time. By not deleting the .git directory, libreboot would be distributing blobs. That's why it's deleted. However, your comment is valid; I should patch the build system in coreboot so that it shows libreboot-insert revision here in the coreboot-libre boot logs (as seen from serial output, EHCI debug output or cbmem -c). I've added a note for myself, reminding me to do this. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVmZtuAAoJEP9Ft0z50c+UW3AH+QGjaH5w/rIEWhKCYvXUDFOj U6yNgGFT8kkXEWaS+vZY1iVrDdIGbEx9SM27ZXroUWLlIS90XiHyzYGqztJgzfrB 3XaYFI17WYwpoQ5f3OGyF8uycc1JlQQQ8zs7xDZywNNVYR4pJUkXHleaYEOb9k3U GJ4PdO22fqTcyZH5XZXk0ga0oZp8N3ChLJgA2gy7L0fGfX73VxQL0CvQ/bMdMsOG hERR4wf7cy4Z6BV1p65lt4Hi60kbEiQ5JpTBawQ80xGUCq2yVyxjJDrY+Pn/1W2l vHmyeM2iBpAroUEZ0f2XnWH8KDEAkoMiM1H6vu6ZHybGrK/JNqf+Le9AXA5oWfo= =p9+b -END PGP SIGNATURE- -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
On Sun, 05 Jul 2015 15:57:30 +0100 Francis Rowe i...@gluglug.org.uk wrote: Libreboot builds coreboot without the .git directory, so it's not possible to get the coreboot revision. You can find out what version I don't understand why you're removing the .git directory. But anyhow, you should patch the coreboot version script. The script should take your specific version of your libreboot build script git repo. Please prefix the version with libreboot, it makes all our live easier to know what version is running and from where the version comes from. And btw. this makes your coreboot' build reproducible, which isn't it atm. Best lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@jabber.ccc.de mobile: +4915123277221 pgpULr62CkR9s.pgp Description: OpenPGP digital signature -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear Paul, dear Ron, thank you for your messages! I used a pre-compiled libreboot ROM image for flashing my T400: t400_8mb_ukqwerty_vesafb.rom (source: http://mirrors.mit.edu/libreboot/20150518/rom/) I attached most of the requested information, I hope I found the right information: requested information - attached file or remark .config of coreboot - config_t400_8mb_libreboot and the payload - the 4 files beginning with grub_ log files from coreboot (cbmem -c) - cbmem_-c the payload - I dont know to get or find it. and Linux - Do you mean the output of dmesg? output of `build/cbfstool build/coreboot.rom print - cbfstool_t400_8mb_ukqwerty_vesafb.rom (I used cbfstool on the used pre-compiled rom) I attached the EDID dumps from my non working and a working display as well. I hope this helps, if you need further information please let me know and I will try to provide them. If you still need the logs files from the payload and Linux please give me the commands I have to execute. I am kind of a noob using Linux. Thanks again an best regards, Kroms Am 03.07.2015 23:19 schrieb Paul Menzel: Dear Kroms, Am Freitag, den 03.07.2015, 16:27 +0200 schrieb kr...@posteo.be: I allready contacted Francis from libreboot and he forwared me to this list, because it seems to be an issue regarding coreboot. welcome and thank you for writing a message to the mailing list. I have flashed a Lenovo T400 with libreboot. The T400 has an Intel GPU and I am able to use it with an external display connected to the onboard vga-port. The issue is, that I can't use the internal display, which is an 1440x900 Samusung LTN141WD-L05, EDID dump: https://paste.debian.net/plainh/b3699c60 Please attach such information in the future instead of pasting it. It seems like the internal screen is powered on while booting but it stays black. Francis assumes that this is due to bugs in how coreboot handles the EDID. Here is an EDID dump of a working display: http://paste.debian.net/plainh/776705d5 Ditto. Anyone is able to help? Please send us your configuration (.config of coreboot and the payload) and the log files from coreboot (cbmem -c), the payload and Linux. That’s one of the advantages of using coreboot, that you have logs. Please also provide the output of `build/cbfstool build/coreboot.rom print`. Thanks, Paultrisquel@trisquel:~$ sudo i2cdump -y 2 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef 00: 00 ff ff ff ff ff ff 00 30 ae 31 40 00 00 00 000?1@ 10: 00 12 01 03 80 1e 13 78 ea b3 85 95 58 53 8a 28.??xXS?( 20: 25 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01%PT...?? 30: 01 01 01 01 01 01 26 1b 00 7d 50 20 16 30 30 20???.}P ?00 40: 36 00 30 be 10 00 00 18 8b 16 00 7d 50 20 16 306.0??..???.}P ?0 50: 30 20 36 00 30 be 10 00 00 18 00 00 00 0f 00 810 6.0??..?...?.? 60: 0a 32 81 0a 28 14 01 00 30 e4 28 01 00 00 00 fe?2??(??.0?(?...? 70: 00 4c 50 31 34 31 57 58 33 2d 54 4c 52 31 00 d8.LP141WX3-TLR1.? 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef 00: XX ff ff ff ff ff ff 00 30 ae 33 40 00 00 00 00X...0?3@ 10: 00 0f 01 03 80 1e 13 78 ea cd 75 91 55 4f 8b 26.??x??u?UO? 20: 21 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01!PT...?? 30: 01 01 01 01 01 01 b0 27 a0 60 51 84 2d 30 30 20???'?`Q?-00 40: 36 00 2f be 10 00 00 19 d5 1f a0 40 51 84 1a 306./??..@Q??0 50: 30 20 36 00 2f be 10 00 00 19 00 00 00 0f 00 900 6./??..?...?.? 60: 0a 32 90 0a 28 14 01 00 4c a3 42 44 00 00 00 fe?2??(??.L?BD...? 70: 00 4c 54 4e 31 34 31 57 44 2d 4c 30 35 0a 00 32.LTN141WD-L05?.2 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff coreboot-4.0 Mon May 18 03:42:26 UTC 2015
[coreboot] T400 screen issue / EDID handling
Hello, I allready contacted Francis from libreboot and he forwared me to this list, because it seems to be an issue regarding coreboot. I have flashed a Lenovo T400 with libreboot. The T400 has an Intel GPU and I am able to use it with an external display connected to the onboard vga-port. The issue is, that I can't use the internal display, which is an 1440x900 Samusung LTN141WD-L05, EDID dump: https://paste.debian.net/plainh/b3699c60 It seems like the internal screen is powered on while booting but it stays black. Francis assumes that this is due to bugs in how coreboot handles the EDID. Here is an EDID dump of a working display: http://paste.debian.net/plainh/776705d5 Anyone is able to help? Thanks in advance! -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Gee, what fun. There are lots of things that can go wrong, to get some idea, see the display handling for HP Falco, in which we managed 4 different types of displays. I'll try to take a look later, but just keep in mind that the displays are frequently not all the same on different production runs of a laptop so something that works fine on one gives black screen on another ... ron On Fri, Jul 3, 2015 at 7:35 AM kr...@posteo.be wrote: Hello, I allready contacted Francis from libreboot and he forwared me to this list, because it seems to be an issue regarding coreboot. I have flashed a Lenovo T400 with libreboot. The T400 has an Intel GPU and I am able to use it with an external display connected to the onboard vga-port. The issue is, that I can't use the internal display, which is an 1440x900 Samusung LTN141WD-L05, EDID dump: https://paste.debian.net/plainh/b3699c60 It seems like the internal screen is powered on while booting but it stays black. Francis assumes that this is due to bugs in how coreboot handles the EDID. Here is an EDID dump of a working display: http://paste.debian.net/plainh/776705d5 Anyone is able to help? Thanks in advance! -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T400 screen issue / EDID handling
Dear Kroms, Am Freitag, den 03.07.2015, 16:27 +0200 schrieb kr...@posteo.be: I allready contacted Francis from libreboot and he forwared me to this list, because it seems to be an issue regarding coreboot. welcome and thank you for writing a message to the mailing list. I have flashed a Lenovo T400 with libreboot. The T400 has an Intel GPU and I am able to use it with an external display connected to the onboard vga-port. The issue is, that I can't use the internal display, which is an 1440x900 Samusung LTN141WD-L05, EDID dump: https://paste.debian.net/plainh/b3699c60 Please attach such information in the future instead of pasting it. It seems like the internal screen is powered on while booting but it stays black. Francis assumes that this is due to bugs in how coreboot handles the EDID. Here is an EDID dump of a working display: http://paste.debian.net/plainh/776705d5 Ditto. Anyone is able to help? Please send us your configuration (.config of coreboot and the payload) and the log files from coreboot (cbmem -c), the payload and Linux. That’s one of the advantages of using coreboot, that you have logs. Please also provide the output of `build/cbfstool build/coreboot.rom print`. Thanks, Paul signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
