screen goes blank when loading gma500_gfx (atom D2500)
19.03.2015 14:56, One Thousand Gnomes wrote: > On Thu, 19 Mar 2015 14:09:29 +0300 > Michael Tokarev wrote: > >> Half a year passed since my first email in this thread, and current kernels >> (4.0-tobe) still does not work properly. Meanwhile, I found this thread: >> http://www.linuxquestions.org/questions/slackware-installation-40/black-screen-on-intel-desktopboard-d2500cc-4175503983/ >> which seems to help. I wonder where they got these boot params from... >> > > Its one of the standard suggestions for dealing with wonky DRM I think. > > If that makes the difference on your box can you send me a dmidecode of > it, and I'll see if we can at least teach the driver that the 2500CC > needs LVDS enabled regardless of what the BIOS reports. Ok. actually this is not so simple. Yes, LVDS:d makes a difference. Namely, it enables monitor connected to VGA-0 to function. But once I plug in a digital monitor (DVI-0), screen goes blank when loading the module again, and this time, it does not matter whenever I specify any video= options (trying to disable any combinations of listed adaptors), screen is always blank. So basically the thing is still unusable. Because d-sub connection isn't stable (picture "trembles" depending on the cable and environment conditions), while digital option does not work. In bios, there's an option to ENable LVDS (it is disabled by default) and once enabled, to make it primary or secondary (with either automatically or manually choosen secondary/primary, being d-sub or dvi). When I enable LVDS with any other monitor in bios, the thing does not work again, the same way (screen goes blank once the module is loaded), but now d-sub/vga monitor does not work too. Ouf of curiocity I tried to run windows7 on this machine. Apparently it works with dvi monitor just fine and supports configuration with 2 monitors. Maybe they have some quirks in the drivers, I dunno... Thanks, /mjt
screen goes blank when loading gma500_gfx (atom D2500)
19.03.2015 23:05, One Thousand Gnomes wrote: >> Yes, with video=LVDS-1:d boot parameter, kernel boots fine and there is >> graphics/video output on the screen, with the following message from kernel >> when loading gma500_gfx: >> >> [6.472859] [drm] forcing LVDS-1 connector OFF >> >> (and a few others). >> >> There's one funky thing still -- the screen size is not calculated correctly >> for the text (vga, d-sub) console, last text line is placed at about 3/4 of >> the screen size, with the rest - 1/4 - of the screen being blank. > > I've seen that in one other case, where what was in fact happening was > that forcing the connector "off" was actually effectively leaving it as > the BIOS set it. When I use LVDS-1:d in the kernel command line, that connector is not shown by utilities such as xrandr, at all. There is, however, another connector, named LVDS-0, and are also DVI-0, DVI-1, and DisplayPort-0, DisplayPort-1, while this mobo only have DVI & D-SUB (and LVDS soldered on board too) and no DP. At least as far as I can see. So at least one LVDS connector is shown anyway (LVDS-0, not LVDS-1), and that one is "not connected". Besides, DisplayPort-1 is shown as "connected" by xrandr, with monitor set to 1024x768 mode, -- I think this is why the text VGA size is calculated wrong.. Lemme see... ..nope. Adding video=DisplayPort-1:d to the kernel command line (in addition to video=LVDS-1:d) makes no difference, DisplayPort-1 is still shown by xrandr as connected @1024x768. > What happens if you then use xrandr to change the > display sizes ? X11 works fine as far as I can see. Xrandr works and changes video modes. Once I switch from X back to the text console the text size occupes 3/4 of the screen only, as if the monitor was smaller. I wonder if it will work with more than one monitor... ;) I'll try hopefully today. Thanks, /mjt
screen goes blank when loading gma500_gfx (atom D2500)
19.03.2015 14:56, One Thousand Gnomes wrote: > On Thu, 19 Mar 2015 14:09:29 +0300 > Michael Tokarev wrote: > >> Half a year passed since my first email in this thread, and current kernels >> (4.0-tobe) still does not work properly. Meanwhile, I found this thread: >> http://www.linuxquestions.org/questions/slackware-installation-40/black-screen-on-intel-desktopboard-d2500cc-4175503983/ >> which seems to help. I wonder where they got these boot params from... > > Its one of the standard suggestions for dealing with wonky DRM I think. > > If that makes the difference on your box can you send me a dmidecode of > it, and I'll see if we can at least teach the driver that the 2500CC > needs LVDS enabled regardless of what the BIOS reports. I think you mean disable, not enable, since this is (again, I think) what video=LVDS-1:d kernel boot parameter does. Yes, with video=LVDS-1:d boot parameter, kernel boots fine and there is graphics/video output on the screen, with the following message from kernel when loading gma500_gfx: [6.472859] [drm] forcing LVDS-1 connector OFF (and a few others). There's one funky thing still -- the screen size is not calculated correctly for the text (vga, d-sub) console, last text line is placed at about 3/4 of the screen size, with the rest - 1/4 - of the screen being blank. However, X seems to work fine, using generic modesetting driver. Below is dmidecode output. Thanks, /mjt === # dmidecode 2.12 SMBIOS 2.7 present. 27 structures occupying 1491 bytes. Table at 0x000EB920. Handle 0x, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Other Manufacturer: Intel(R) Corporation ID: 61 06 03 00 FF FB EB BF Version: Intel(R) Atom(TM) CPU D2500 @ 1.86GHz Voltage: 1.1 V External Clock: 133 MHz Max Speed: 4000 MHz Current Speed: 1868 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0003 L2 Cache Handle: 0x0001 L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 2 Core Enabled: 2 Thread Count: 1 Characteristics: 64-bit capable Multi-Core Execute Protection Handle 0x0001, DMI type 7, 19 bytes Cache Information Socket Designation: Unknown Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 512 kB Maximum Size: 512 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Data Associativity: 8-way Set-associative Handle 0x0002, DMI type 7, 19 bytes Cache Information Socket Designation: Unknown Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 32 kB Maximum Size: 32 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Instruction Associativity: 8-way Set-associative Handle 0x0003, DMI type 7, 19 bytes Cache Information Socket Designation: Unknown Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 24 kB Maximum Size: 24 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Data Associativity: 32-way Set-associative Handle 0x0004, DMI type 0, 24 bytes BIOS Information Vendor: Intel Corp. Version: CCCDT10N.86A.0039.2013.0425.1625 Release Date: 04/25/2013 Address: 0xF Runtime Size: 64 kB ROM Size: 2048 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Function key-initiated network
screen goes blank when loading gma500_gfx (atom D2500)
19.03.2015 14:09, Michael Tokarev wrote: > Half a year passed since my first email in this thread, and current kernels Actually it was more than a year, since Feb-2014 ;) > (4.0-tobe) still does not work properly. Meanwhile, I found this thread: > http://www.linuxquestions.org/questions/slackware-installation-40/black-screen-on-intel-desktopboard-d2500cc-4175503983/ > which seems to help. I wonder where they got these boot params from... > > Thanks, > > /mjt
screen goes blank when loading gma500_gfx (atom D2500)
Half a year passed since my first email in this thread, and current kernels
(4.0-tobe) still does not work properly. Meanwhile, I found this thread:
http://www.linuxquestions.org/questions/slackware-installation-40/black-screen-on-intel-desktopboard-d2500cc-4175503983/
which seems to help. I wonder where they got these boot params from...
Thanks,
/mjt
05.08.2014 20:15, Michael Tokarev wrote:
> 05.08.2014 20:11, Michael Tokarev wrote:
>> Hello again.
>>
>> It's been 4 more months since last message in this thread (which was mine).
>> Now kernel 3.16 has been released, and I decided to give it a try. And it
>> behaves just like all previous kernels, -- once gma500_gfx module is loaded,
>> screen goes blank, monitor turns off ("no signal detected") and nothing to
>> be seen until reboot.
>>
>> Can we try to debug this somehow, after more than half a year?... :)
>
> Current debugging (by 3.16), after:
>
> modprobe drm debug=6
> modprobe gma500_gfx
>
> on a freshly booted system:
>
> [ 46.463381] Linux agpgart interface v0.103
> [ 46.491487] [drm] Initialized drm 1.1.0 20060810
> [ 56.585520] [drm:psb_intel_opregion_setup] Public ACPI methods supported
> [ 56.585528] [drm:psb_intel_opregion_setup] ASLE supported
> [ 56.585563] gma500 :00:02.0: irq 50 for MSI/MSI-X
> [ 56.585591] [drm:psb_intel_init_bios] Using VBT from OpRegion: $VBT
> CEDARVIEW d
> [ 56.585604] [drm:drm_mode_debug_printmodeline] Modeline 0:"1920x1080" 0
> 144000 1920 2016 2080 2176 1080 1088 1092 1100 0x8 0xa
> [ 56.585609] [drm:parse_sdvo_device_mapping] No SDVO device info is found
> in VBT
> [ 56.585617] [drm:parse_edp] EDP timing in vbt t1_t3 2000 t8 10 t9 2000 t10
> 500 t11_t12 5000
> [ 56.585621] [drm:parse_edp] VBT reports EDP: Lane_count 1, Lane_rate 6,
> Bpp 24
> [ 56.585624] [drm:parse_edp] VBT reports EDP: VSwing 0, Preemph 0
> [ 56.598203] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
> [ 56.598902] acpi device:28: registered as cooling_device2
> [ 56.599109] input: Video Bus as
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input11
> [ 56.599326] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [ 56.599366] [drm] No driver support for vblank timestamp query.
> [ 56.650918] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter
> intel drm LVDSDDC_C
> [ 56.651842] [drm:cdv_intel_dp_i2c_init] i2c_init DPDDC-B
> [ 56.652352] [drm:cdv_intel_dp_aux_ch] dp_aux_ch timeout status 0x51440064
> [ 56.652356] [drm:cdv_intel_dp_i2c_aux_ch] aux_ch failed -110
> [ 56.652863] [drm:cdv_intel_dp_aux_ch] dp_aux_ch timeout status 0x51440064
> [ 56.652866] [drm:cdv_intel_dp_i2c_aux_ch] aux_ch failed -110
> [ 56.653706] [drm:cdv_intel_dp_i2c_init] i2c_init DPDDC-C
> [ 56.654014] [drm:cdv_intel_dp_i2c_aux_ch] aux_i2c nack
> [ 56.654223] [drm:cdv_intel_dp_i2c_aux_ch] aux_i2c nack
> [ 56.714765] gma500 :00:02.0: trying to get vblank count for disabled
> pipe 1
> [ 56.714812] gma500 :00:02.0: trying to get vblank count for disabled
> pipe 1
> [ 56.775220] [drm:drm_helper_probe_single_connector_modes_merge_bits]
> [CONNECTOR:10:VGA-1]
> [ 56.900606] [drm:drm_helper_probe_single_connector_modes_merge_bits]
> [CONNECTOR:10:VGA-1] probed modes :
> [ 56.900617] [drm:drm_mode_debug_printmodeline] Modeline 26:"1280x1024" 60
> 108000 1280 1328 1440 1688 1024 1025 1028 1066 0x48 0x5
> [ 56.900624] [drm:drm_mode_debug_printmodeline] Modeline 36:"1280x1024" 75
> 135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5
> [ 56.900630] [drm:drm_mode_debug_printmodeline] Modeline 29:"1280x1024" 72
> 132840 1280 1368 1504 1728 1024 1025 1028 1067 0x0 0x6
> [ 56.900637] [drm:drm_mode_debug_printmodeline] Modeline 28:"1152x864" 75
> 108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5
> [ 56.900643] [drm:drm_mode_debug_printmodeline] Modeline 37:"1024x768" 75
> 78800 1024 1040 1136 1312 768 769 772 800 0x40 0x5
> [ 56.900649] [drm:drm_mode_debug_printmodeline] Modeline 38:"1024x768" 70
> 75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa
> [ 56.900656] [drm:drm_mode_debug_printmodeline] Modeline 39:"1024x768" 60
> 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
> [ 56.900662] [drm:drm_mode_debug_printmodeline] Modeline 40:"832x624" 75
> 57284 832 864 928 1152 624 625 628 667 0x40 0xa
> [ 56.900669] [drm:drm_mode_debug_printmodeline] Modeline 41:"800x600" 75
> 49500 800 816 896 1056 600 601 604 625 0x40 0x5
> [ 56.900675] [drm:drm_mode_debug_printmodeline] Modeline 42:"800x600" 72
> 5 800 856 976 1040 600 637 643
screen goes blank when loading gma500_gfx (atom D2500)
05.08.2014 20:11, Michael Tokarev wrote:
> Hello again.
>
> It's been 4 more months since last message in this thread (which was mine).
> Now kernel 3.16 has been released, and I decided to give it a try. And it
> behaves just like all previous kernels, -- once gma500_gfx module is loaded,
> screen goes blank, monitor turns off ("no signal detected") and nothing to
> be seen until reboot.
>
> Can we try to debug this somehow, after more than half a year?... :)
Current debugging (by 3.16), after:
modprobe drm debug=6
modprobe gma500_gfx
on a freshly booted system:
[ 46.463381] Linux agpgart interface v0.103
[ 46.491487] [drm] Initialized drm 1.1.0 20060810
[ 56.585520] [drm:psb_intel_opregion_setup] Public ACPI methods supported
[ 56.585528] [drm:psb_intel_opregion_setup] ASLE supported
[ 56.585563] gma500 :00:02.0: irq 50 for MSI/MSI-X
[ 56.585591] [drm:psb_intel_init_bios] Using VBT from OpRegion: $VBT
CEDARVIEW d
[ 56.585604] [drm:drm_mode_debug_printmodeline] Modeline 0:"1920x1080" 0
144000 1920 2016 2080 2176 1080 1088 1092 1100 0x8 0xa
[ 56.585609] [drm:parse_sdvo_device_mapping] No SDVO device info is found in
VBT
[ 56.585617] [drm:parse_edp] EDP timing in vbt t1_t3 2000 t8 10 t9 2000 t10
500 t11_t12 5000
[ 56.585621] [drm:parse_edp] VBT reports EDP: Lane_count 1, Lane_rate 6, Bpp
24
[ 56.585624] [drm:parse_edp] VBT reports EDP: VSwing 0, Preemph 0
[ 56.598203] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 56.598902] acpi device:28: registered as cooling_device2
[ 56.599109] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input11
[ 56.599326] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 56.599366] [drm] No driver support for vblank timestamp query.
[ 56.650918] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter
intel drm LVDSDDC_C
[ 56.651842] [drm:cdv_intel_dp_i2c_init] i2c_init DPDDC-B
[ 56.652352] [drm:cdv_intel_dp_aux_ch] dp_aux_ch timeout status 0x51440064
[ 56.652356] [drm:cdv_intel_dp_i2c_aux_ch] aux_ch failed -110
[ 56.652863] [drm:cdv_intel_dp_aux_ch] dp_aux_ch timeout status 0x51440064
[ 56.652866] [drm:cdv_intel_dp_i2c_aux_ch] aux_ch failed -110
[ 56.653706] [drm:cdv_intel_dp_i2c_init] i2c_init DPDDC-C
[ 56.654014] [drm:cdv_intel_dp_i2c_aux_ch] aux_i2c nack
[ 56.654223] [drm:cdv_intel_dp_i2c_aux_ch] aux_i2c nack
[ 56.714765] gma500 :00:02.0: trying to get vblank count for disabled
pipe 1
[ 56.714812] gma500 :00:02.0: trying to get vblank count for disabled
pipe 1
[ 56.775220] [drm:drm_helper_probe_single_connector_modes_merge_bits]
[CONNECTOR:10:VGA-1]
[ 56.900606] [drm:drm_helper_probe_single_connector_modes_merge_bits]
[CONNECTOR:10:VGA-1] probed modes :
[ 56.900617] [drm:drm_mode_debug_printmodeline] Modeline 26:"1280x1024" 60
108000 1280 1328 1440 1688 1024 1025 1028 1066 0x48 0x5
[ 56.900624] [drm:drm_mode_debug_printmodeline] Modeline 36:"1280x1024" 75
135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5
[ 56.900630] [drm:drm_mode_debug_printmodeline] Modeline 29:"1280x1024" 72
132840 1280 1368 1504 1728 1024 1025 1028 1067 0x0 0x6
[ 56.900637] [drm:drm_mode_debug_printmodeline] Modeline 28:"1152x864" 75
108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5
[ 56.900643] [drm:drm_mode_debug_printmodeline] Modeline 37:"1024x768" 75
78800 1024 1040 1136 1312 768 769 772 800 0x40 0x5
[ 56.900649] [drm:drm_mode_debug_printmodeline] Modeline 38:"1024x768" 70
75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa
[ 56.900656] [drm:drm_mode_debug_printmodeline] Modeline 39:"1024x768" 60
65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
[ 56.900662] [drm:drm_mode_debug_printmodeline] Modeline 40:"832x624" 75
57284 832 864 928 1152 624 625 628 667 0x40 0xa
[ 56.900669] [drm:drm_mode_debug_printmodeline] Modeline 41:"800x600" 75
49500 800 816 896 1056 600 601 604 625 0x40 0x5
[ 56.900675] [drm:drm_mode_debug_printmodeline] Modeline 42:"800x600" 72
5 800 856 976 1040 600 637 643 666 0x40 0x5
[ 56.900681] [drm:drm_mode_debug_printmodeline] Modeline 30:"800x600" 60
4 800 840 968 1056 600 601 605 628 0x40 0x5
[ 56.900687] [drm:drm_mode_debug_printmodeline] Modeline 31:"640x480" 75
31500 640 656 720 840 480 481 484 500 0x40 0xa
[ 56.900694] [drm:drm_mode_debug_printmodeline] Modeline 32:"640x480" 73
31500 640 664 704 832 480 489 491 520 0x40 0xa
[ 56.900700] [drm:drm_mode_debug_printmodeline] Modeline 33:"640x480" 67
30240 640 704 768 864 480 483 486 525 0x40 0xa
[ 56.900706] [drm:drm_mode_debug_printmodeline] Modeline 34:"640x480" 60
25200 640 656 752 800 480 490 492 525 0x40 0xa
[ 56.900713] [drm:drm_mode_debug_printmodeline] Modeline 35:
screen goes blank when loading gma500_gfx (atom D2500)
Hello again.
It's been 4 more months since last message in this thread (which was mine).
Now kernel 3.16 has been released, and I decided to give it a try. And it
behaves just like all previous kernels, -- once gma500_gfx module is loaded,
screen goes blank, monitor turns off ("no signal detected") and nothing to
be seen until reboot.
Can we try to debug this somehow, after more than half a year?... :)
Thank you,
/mjt
05.04.2014 12:15, Michael Tokarev wrote:
> Hello again
>
> It's been about 2 months since I sent the original debugging output. Today I
> tried
> out 3.14 kernel. And this one behaves quite similarly, screen goes blank
> right
> when loading gma500_gfx module. Here's the dmesg from a freshly booted system
> after doing
>
> modprobe drm debug=6
> modprobe gma500_gfx
>
> with a monitor connected to VGA port (before loading gma500_gfx, it displays
> the
> regular text console):
>
> [ 39.863330] Linux agpgart interface v0.103
> [ 39.900511] [drm] Initialized drm 1.1.0 20060810
> [ 45.012300] [drm:psb_intel_opregion_setup], Public ACPI methods supported
> [ 45.012308] [drm:psb_intel_opregion_setup], ASLE supported
> [ 45.012345] gma500 :00:02.0: irq 50 for MSI/MSI-X
> [ 45.012371] [drm:psb_intel_init_bios], Using VBT from OpRegion: $VBT
> CEDARVIEW d
> [ 45.012384] [drm:drm_mode_debug_printmodeline], Modeline 0:"1920x1080" 0
> 144000 1920 2016 2080 2176 1080 1088 1092 1100 0x8 0xa
> [ 45.012389] [drm:parse_sdvo_device_mapping], No SDVO device info is found
> in VBT
> [ 45.012397] [drm:parse_edp], EDP timing in vbt t1_t3 2000 t8 10 t9 2000
> t10 500 t11_t12 5000
> [ 45.012401] [drm:parse_edp], VBT reports EDP: Lane_count 1, Lane_rate 6,
> Bpp 24
> [ 45.012405] [drm:parse_edp], VBT reports EDP: VSwing 0, Preemph 0
> [ 45.012478] gma500 :00:02.0: GPU: power management timed out.
> [ 45.026195] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
> [ 45.026891] acpi device:29: registered as cooling_device2
> [ 45.027104] input: Video Bus as
> /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11
> [ 45.027681] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [ 45.027726] [drm] No driver support for vblank timestamp query.
> [ 45.078928] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
> adapter intel drm LVDSDDC_C
> [ 45.079839] [drm:cdv_intel_dp_i2c_init], i2c_init DPDDC-B
> [ 45.080383] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064
> [ 45.080388] [drm:cdv_intel_dp_i2c_aux_ch], aux_ch failed -110
> [ 45.080896] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064
> [ 45.080899] [drm:cdv_intel_dp_i2c_aux_ch], aux_ch failed -110
> [ 45.081754] [drm:cdv_intel_dp_i2c_init], i2c_init DPDDC-C
> [ 45.082062] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack
> [ 45.082272] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack
> [ 45.122742] [drm:cdv_intel_single_pipe_active], pipe enabled 0
> [ 45.142780] gma500 :00:02.0: trying to get vblank count for disabled
> pipe 1
> [ 45.142826] gma500 :00:02.0: trying to get vblank count for disabled
> pipe 1
> [ 45.183207] [drm:cdv_intel_single_pipe_active], pipe enabled 0
> [ 45.203249] [drm:drm_helper_probe_single_connector_modes],
> [CONNECTOR:7:VGA-1]
> [ 45.332286] [drm:drm_helper_probe_single_connector_modes],
> [CONNECTOR:7:VGA-1] probed modes :
> [ 45.332297] [drm:drm_mode_debug_printmodeline], Modeline 23:"1280x1024" 60
> 108000 1280 1328 1440 1688 1024 1025 1028 1066 0x48 0x5
> [ 45.332304] [drm:drm_mode_debug_printmodeline], Modeline 33:"1280x1024" 75
> 135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5
> [ 45.332311] [drm:drm_mode_debug_printmodeline], Modeline 26:"1280x1024" 72
> 132840 1280 1368 1504 1728 1024 1025 1028 1067 0x0 0x6
> [ 45.332318] [drm:drm_mode_debug_printmodeline], Modeline 25:"1152x864" 75
> 108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5
> [ 45.332325] [drm:drm_mode_debug_printmodeline], Modeline 34:"1024x768" 75
> 78800 1024 1040 1136 1312 768 769 772 800 0x40 0x5
> [ 45.332332] [drm:drm_mode_debug_printmodeline], Modeline 35:"1024x768" 70
> 75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa
> [ 45.332338] [drm:drm_mode_debug_printmodeline], Modeline 36:"1024x768" 60
> 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
> [ 45.332345] [drm:drm_mode_debug_printmodeline], Modeline 37:"832x624" 75
> 57284 832 864 928 1152 624 625 628 667 0x40 0xa
> [ 45.332352] [drm:drm_mode_debug_printmodeline], Modeline 38:"800x600" 75
> 49500 800 816 896 1056 600 601 604 625 0x40 0x5
> [ 45.332359] [drm:dr
screen goes blank when loading gma500_gfx (atom D2500)
51935] [drm:drm_target_preferred], looking for preferred mode on connector 9 [ 45.351938] [drm:drm_target_preferred], found mode 1920x1080 [ 45.351942] [drm:drm_target_preferred], looking for cmdline mode on connector 20 [ 45.351945] [drm:drm_target_preferred], looking for preferred mode on connector 20 [ 45.351949] [drm:drm_target_preferred], found mode 1024x768 [ 45.351953] [drm:drm_setup_crtcs], picking CRTCs for 4096x4096 config [ 45.351962] [drm:drm_setup_crtcs], desired mode 1280x1024 set on crtc 3 [ 45.351967] [drm:drm_setup_crtcs], desired mode 1920x1080 set on crtc 4 [ 45.351987] [drm] Initialized gma500 1.0.0 2011-06-06 for :00:02.0 on minor 0 Thank you! /mjt 15.02.2014 22:28, Michael Tokarev wrote: > 10.02.2014 14:44, One Thousand Gnomes wrote: >>> fbcon is loaded so it isn't an issue. >>> >>> I tried 3.10 kernel initially (the above messages are from it), next >>> I tried 3.13 kernel too, and that one behaves exactly the same. >>> >>> As far as I remember, this system never worked with graphics well. >>> Previous kernel (from which I updated) was 3.2 which had no >>> gma500 module (local build). >>> >>> What are the steps to debug this further? >> >> Check you have X86_SYSFB and SIMPLEFB disabled > > Neither of these options exists in 3.10 config. In 3.13 I had X86_SYSFB set > to y initially (SIMPLEFB doesn't exist there too), but setting it to n does > not make any difference. > >> Boot with drm.debug=6 >> >> collect the logs > > I used `modprobe drm debug=6' (initially booting with gma500_gfx module > disabled), followed with `modprobe gma500_gfx'. After loading module > the screen goes blank as before, and monitor says 'no signal detected'. > > Here are the logs: > > [599286.739923] Linux agpgart interface v0.103 > [599286.765176] [drm] Initialized drm 1.1.0 20060810 > [599303.673734] gma500 :00:02.0: setting latency timer to 64 > [599303.673883] [drm:psb_intel_opregion_setup], Public ACPI methods supported > [599303.673887] [drm:psb_intel_opregion_setup], ASLE supported > [599303.673923] gma500 :00:02.0: irq 50 for MSI/MSI-X > [599303.673950] [drm:psb_intel_init_bios], Using VBT from OpRegion: $VBT > CEDARVIEW d > [599303.673959] [drm:drm_mode_debug_printmodeline], Modeline 0:"1920x1080" 0 > 144000 1920 2016 2080 2176 1080 1088 1092 1100 0x8 0xa > [599303.673969] [drm:parse_sdvo_device_mapping], No SDVO device info is found > in VBT > [599303.673975] [drm:parse_edp], EDP timing in vbt t1_t3 2000 t8 10 t9 2000 > t10 500 t11_t12 5000 > [599303.673980] [drm:parse_edp], VBT reports EDP: Lane_count 1, Lane_rate 6, > Bpp 24 > [599303.673984] [drm:parse_edp], VBT reports EDP: VSwing 0, Preemph 0 > [599303.688094] acpi device:29: registered as cooling_device2 > [599303.688446] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) > [599303.688557] input: Video Bus as > /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 > [599303.689160] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). > [599303.689188] [drm] No driver support for vblank timestamp query. > [599303.740423] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent > adapter intel drm LVDSDDC_C > [599303.741222] [drm:cdv_intel_dp_i2c_init], i2c_init DPDDC-B > [599303.741732] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064 > [599303.741736] [drm:cdv_intel_dp_i2c_aux_ch], aux_ch failed -110 > [599303.742242] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064 > [599303.742246] [drm:cdv_intel_dp_i2c_aux_ch], aux_ch failed -110 > [599303.742997] [drm:cdv_intel_dp_i2c_init], i2c_init DPDDC-C > [599303.743305] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack > [599303.743510] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack > [599303.783922] [drm:cdv_intel_single_pipe_active], pipe enabled 0 > [599303.803958] gma500 :00:02.0: trying to get vblank count for disabled > pipe 1 > [599303.803996] gma500 :00:02.0: trying to get vblank count for disabled > pipe 1 > [599303.844370] [drm:cdv_intel_single_pipe_active], pipe enabled 0 > [599303.864408] [drm:drm_helper_probe_single_connector_modes], > [CONNECTOR:7:VGA-1] > [599303.877172] [drm:drm_helper_probe_single_connector_modes], > [CONNECTOR:7:VGA-1] disconnected > [599303.877184] [drm:drm_helper_probe_single_connector_modes], > [CONNECTOR:9:LVDS-1] > [599303.881764] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent > adapter intel drm LVDSBLC_B > [599303.881778] [drm:drm_helper_probe_single_connector_modes], > [CONNECTOR:9:LVDS-1] probed modes : > [599303.881783] [drm:drm_mode_debug_printmodeline], Modeline 22:"1920x1080" > 60 144000 192
screen goes blank when loading gma500_gfx (atom D2500)
10.02.2014 14:44, One Thousand Gnomes wrote: >> fbcon is loaded so it isn't an issue. >> >> I tried 3.10 kernel initially (the above messages are from it), next >> I tried 3.13 kernel too, and that one behaves exactly the same. >> >> As far as I remember, this system never worked with graphics well. >> Previous kernel (from which I updated) was 3.2 which had no >> gma500 module (local build). >> >> What are the steps to debug this further? > > Check you have X86_SYSFB and SIMPLEFB disabled Neither of these options exists in 3.10 config. In 3.13 I had X86_SYSFB set to y initially (SIMPLEFB doesn't exist there too), but setting it to n does not make any difference. > Boot with drm.debug=6 > > collect the logs I used `modprobe drm debug=6' (initially booting with gma500_gfx module disabled), followed with `modprobe gma500_gfx'. After loading module the screen goes blank as before, and monitor says 'no signal detected'. Here are the logs: [599286.739923] Linux agpgart interface v0.103 [599286.765176] [drm] Initialized drm 1.1.0 20060810 [599303.673734] gma500 :00:02.0: setting latency timer to 64 [599303.673883] [drm:psb_intel_opregion_setup], Public ACPI methods supported [599303.673887] [drm:psb_intel_opregion_setup], ASLE supported [599303.673923] gma500 :00:02.0: irq 50 for MSI/MSI-X [599303.673950] [drm:psb_intel_init_bios], Using VBT from OpRegion: $VBT CEDARVIEW d [599303.673959] [drm:drm_mode_debug_printmodeline], Modeline 0:"1920x1080" 0 144000 1920 2016 2080 2176 1080 1088 1092 1100 0x8 0xa [599303.673969] [drm:parse_sdvo_device_mapping], No SDVO device info is found in VBT [599303.673975] [drm:parse_edp], EDP timing in vbt t1_t3 2000 t8 10 t9 2000 t10 500 t11_t12 5000 [599303.673980] [drm:parse_edp], VBT reports EDP: Lane_count 1, Lane_rate 6, Bpp 24 [599303.673984] [drm:parse_edp], VBT reports EDP: VSwing 0, Preemph 0 [599303.688094] acpi device:29: registered as cooling_device2 [599303.688446] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [599303.688557] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 [599303.689160] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [599303.689188] [drm] No driver support for vblank timestamp query. [599303.740423] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter intel drm LVDSDDC_C [599303.741222] [drm:cdv_intel_dp_i2c_init], i2c_init DPDDC-B [599303.741732] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064 [599303.741736] [drm:cdv_intel_dp_i2c_aux_ch], aux_ch failed -110 [599303.742242] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064 [599303.742246] [drm:cdv_intel_dp_i2c_aux_ch], aux_ch failed -110 [599303.742997] [drm:cdv_intel_dp_i2c_init], i2c_init DPDDC-C [599303.743305] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack [599303.743510] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack [599303.783922] [drm:cdv_intel_single_pipe_active], pipe enabled 0 [599303.803958] gma500 :00:02.0: trying to get vblank count for disabled pipe 1 [599303.803996] gma500 :00:02.0: trying to get vblank count for disabled pipe 1 [599303.844370] [drm:cdv_intel_single_pipe_active], pipe enabled 0 [599303.864408] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:VGA-1] [599303.877172] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:VGA-1] disconnected [599303.877184] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:9:LVDS-1] [599303.881764] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter intel drm LVDSBLC_B [599303.881778] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:9:LVDS-1] probed modes : [599303.881783] [drm:drm_mode_debug_printmodeline], Modeline 22:"1920x1080" 60 144000 1920 2016 2080 2176 1080 1088 1092 1100 0x8 0xa [599303.881791] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:12:DVI-D-1] [599303.886292] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter intel drm HDMIB [599303.886298] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:12:DVI-D-1] disconnected [599303.886304] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:14:DP-1] [599303.886811] [drm:cdv_intel_dp_aux_ch], dp_aux_ch timeout status 0x51440064 [599303.886815] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:14:DP-1] disconnected [599303.886820] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:18:DVI-D-2] [599303.891350] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter intel drm HDMIC [599303.891357] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:18:DVI-D-2] disconnected [599303.891362] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:20:DP-2] [599303.891569] [drm:cdv_dp_detect], DPCD: Rev=11 LN_Rate=a LN_CNT=82 LN_DOWNSP=41 [599303.891876] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack [599303.892082] [drm:cdv_intel_dp_i2c_aux_ch], aux_i2c nack [599303.892085] [drm:i2c_algo_dp_aux_xfer], dp_aux_xfer return
screen goes blank when loading gma500_gfx (atom D2500)
Hello. Today I rebooted my router into a new kernel and noticed that the screen goes blank after booting the system (initial bootup messages are visible). After some debugging it turns out that the screen goes blank when loading gma500_gfx module. This is an intel D2500CC motherboard with Atom D5200 built-in, with a monitor connected to a VGA port, the following vga device is reported by lspci: 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) Here are the dmesg output after loading gma500_gfx: [ 176.427071] Linux agpgart interface v0.103 [ 176.452914] [drm] Initialized drm 1.1.0 20060810 [ 176.476037] gma500 :00:02.0: setting latency timer to 64 [ 176.476216] gma500 :00:02.0: irq 50 for MSI/MSI-X [ 176.491675] acpi device:29: registered as cooling_device2 [ 176.492041] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 176.492169] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 [ 176.492357] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 176.492396] [drm] No driver support for vblank timestamp query. [ 176.607485] gma500 :00:02.0: trying to get vblank count for disabled pipe 1 [ 176.607531] gma500 :00:02.0: trying to get vblank count for disabled pipe 1 [ 176.806078] [drm] Initialized gma500 1.0.0 2011-06-06 for :00:02.0 on minor 0 which does not look bad or suspicious to me. fbcon is loaded so it isn't an issue. I tried 3.10 kernel initially (the above messages are from it), next I tried 3.13 kernel too, and that one behaves exactly the same. As far as I remember, this system never worked with graphics well. Previous kernel (from which I updated) was 3.2 which had no gma500 module (local build). What are the steps to debug this further? Thanks, /mjt
VERY slow scrolling on radeon graphics card: debugging a timing issue?
05.01.2011 01:50, Michael Tokarev wrote: > 02.01.2011 12:00, Pavel Machek wrote: >> Hi! >> >>> The thing is: that same scrolling becomes much faster >>> when I "do something" else while it scrolls up. First >>> I noticed this when I wanted to switch to another vt >>> while it were scrolling -- I held down Ctrl key on my >>> keyboard, and out of the sudden the scroll speed up >>> dramatically. >>> >>> It turned out I can speed the thing to about 10 times >>> by generating some load: hit and hold a key on the >>> keyboard (generates interrupts?), run kernel compile >>> in the background (generates disk interrupts?), move >>> mouse... >> >> Try "irqpoll"? > > It turned out to be a bit less easy than I thought. > > The thing is, it appears the issue is not triggered > on fresh boot - scrolling is reasonable fast there. > But slowness returns back after suspend-to-RAM cycle > (not suspend-to-disk). I'm still trying ;) Two more data points. irqpoll "helps" - it makes the scrolling "jumpy", it is slow for a few first lines, next it speeds up but not to full speed still, and the speed varies during one test (while it scrolls, say, dmesg). When performing syspend-to-disk cycle the speed restores back to normal, regardless of irqpoll. So it's definitely something to do with suspend-to-ram. And there's more: the system does not perform suspend-to-ram properly using "simple" way -- "echo mem > /sys/power/state". This way, everything gets turned off (disks, monitor, usb devices etc), but the power indicator stays on, and the system does not react to anything - only hard reset works. When using pm-suspend it performs suspend correctly, and enters state when the power indicator blinks, and power button returns the system back to working state. This is when run from "text" console, but apparently this is another issue and is something new (in 2.6.36), since I _know_ I used simple `echo mem' many times before. Thanks! /mjt >> Will cpu load speed it up, too? (Like yes > /dev/null)? > > Yes, CPU load fixes the issue immediately. But switching > from ondemand to performance CPU governor does not fix it. > >>> Any hints on where to go from there are apprecated. >>> >>> The hardware is an AMD780g-based motherboard with >>> and Athlon CPU, I've seen the same behavour from >>> many other similar boards. Kernels - all up to >>> the current 2.6.36.2, sine the old days when kms >>> for radeon first appeared in staging. >> >> Watch /proc/interrupts to see if radeon uses them and if they appear >> to work? > > I don't see any change in radeon interrupt numbers during the > scrolling, so it's difficult to say. The IRQ is shared between > several devices: > > $ grep radeon /proc/interrupts > 18: 510439 370 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, > ohci_hcd:usb5, radeon > > The counter changes but very slowly (and not during the scroll > test when I don't touch anything), I see on correlation between > it any my actions. > > Thanks! > > /mjt
VERY slow scrolling on radeon graphics card: debugging a timing issue?
02.01.2011 12:00, Pavel Machek wrote: > Hi! > >> The thing is: that same scrolling becomes much faster >> when I "do something" else while it scrolls up. First >> I noticed this when I wanted to switch to another vt >> while it were scrolling -- I held down Ctrl key on my >> keyboard, and out of the sudden the scroll speed up >> dramatically. >> >> It turned out I can speed the thing to about 10 times >> by generating some load: hit and hold a key on the >> keyboard (generates interrupts?), run kernel compile >> in the background (generates disk interrupts?), move >> mouse... > > Try "irqpoll"? It turned out to be a bit less easy than I thought. The thing is, it appears the issue is not triggered on fresh boot - scrolling is reasonable fast there. But slowness returns back after suspend-to-RAM cycle (not suspend-to-disk). I'm still trying ;) > Will cpu load speed it up, too? (Like yes > /dev/null)? Yes, CPU load fixes the issue immediately. But switching from ondemand to performance CPU governor does not fix it. >> Any hints on where to go from there are apprecated. >> >> The hardware is an AMD780g-based motherboard with >> and Athlon CPU, I've seen the same behavour from >> many other similar boards. Kernels - all up to >> the current 2.6.36.2, sine the old days when kms >> for radeon first appeared in staging. > > Watch /proc/interrupts to see if radeon uses them and if they appear > to work? I don't see any change in radeon interrupt numbers during the scrolling, so it's difficult to say. The IRQ is shared between several devices: $ grep radeon /proc/interrupts 18: 510439 370 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5, radeon The counter changes but very slowly (and not during the scroll test when I don't touch anything), I see on correlation between it any my actions. Thanks! /mjt
Re: VERY slow scrolling on radeon graphics card: debugging a timing issue?
02.01.2011 12:00, Pavel Machek wrote: Hi! The thing is: that same scrolling becomes much faster when I do something else while it scrolls up. First I noticed this when I wanted to switch to another vt while it were scrolling -- I held down Ctrl key on my keyboard, and out of the sudden the scroll speed up dramatically. It turned out I can speed the thing to about 10 times by generating some load: hit and hold a key on the keyboard (generates interrupts?), run kernel compile in the background (generates disk interrupts?), move mouse... Try irqpoll? It turned out to be a bit less easy than I thought. The thing is, it appears the issue is not triggered on fresh boot - scrolling is reasonable fast there. But slowness returns back after suspend-to-RAM cycle (not suspend-to-disk). I'm still trying ;) Will cpu load speed it up, too? (Like yes /dev/null)? Yes, CPU load fixes the issue immediately. But switching from ondemand to performance CPU governor does not fix it. Any hints on where to go from there are apprecated. The hardware is an AMD780g-based motherboard with and Athlon CPU, I've seen the same behavour from many other similar boards. Kernels - all up to the current 2.6.36.2, sine the old days when kms for radeon first appeared in staging. Watch /proc/interrupts to see if radeon uses them and if they appear to work? I don't see any change in radeon interrupt numbers during the scrolling, so it's difficult to say. The IRQ is shared between several devices: $ grep radeon /proc/interrupts 18: 510439 370 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5, radeon The counter changes but very slowly (and not during the scroll test when I don't touch anything), I see on correlation between it any my actions. Thanks! /mjt ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: VERY slow scrolling on radeon graphics card: debugging a timing issue?
05.01.2011 01:50, Michael Tokarev wrote: 02.01.2011 12:00, Pavel Machek wrote: Hi! The thing is: that same scrolling becomes much faster when I do something else while it scrolls up. First I noticed this when I wanted to switch to another vt while it were scrolling -- I held down Ctrl key on my keyboard, and out of the sudden the scroll speed up dramatically. It turned out I can speed the thing to about 10 times by generating some load: hit and hold a key on the keyboard (generates interrupts?), run kernel compile in the background (generates disk interrupts?), move mouse... Try irqpoll? It turned out to be a bit less easy than I thought. The thing is, it appears the issue is not triggered on fresh boot - scrolling is reasonable fast there. But slowness returns back after suspend-to-RAM cycle (not suspend-to-disk). I'm still trying ;) Two more data points. irqpoll helps - it makes the scrolling jumpy, it is slow for a few first lines, next it speeds up but not to full speed still, and the speed varies during one test (while it scrolls, say, dmesg). When performing syspend-to-disk cycle the speed restores back to normal, regardless of irqpoll. So it's definitely something to do with suspend-to-ram. And there's more: the system does not perform suspend-to-ram properly using simple way -- echo mem /sys/power/state. This way, everything gets turned off (disks, monitor, usb devices etc), but the power indicator stays on, and the system does not react to anything - only hard reset works. When using pm-suspend it performs suspend correctly, and enters state when the power indicator blinks, and power button returns the system back to working state. This is when run from text console, but apparently this is another issue and is something new (in 2.6.36), since I _know_ I used simple `echo mem' many times before. Thanks! /mjt Will cpu load speed it up, too? (Like yes /dev/null)? Yes, CPU load fixes the issue immediately. But switching from ondemand to performance CPU governor does not fix it. Any hints on where to go from there are apprecated. The hardware is an AMD780g-based motherboard with and Athlon CPU, I've seen the same behavour from many other similar boards. Kernels - all up to the current 2.6.36.2, sine the old days when kms for radeon first appeared in staging. Watch /proc/interrupts to see if radeon uses them and if they appear to work? I don't see any change in radeon interrupt numbers during the scrolling, so it's difficult to say. The IRQ is shared between several devices: $ grep radeon /proc/interrupts 18: 510439 370 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5, radeon The counter changes but very slowly (and not during the scroll test when I don't touch anything), I see on correlation between it any my actions. Thanks! /mjt ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/edid: Fix 1024x768@85Hz
Adam Jackson wrote at Thu May 13 11:55:28 PDT 2010: > Having hsync both start and end on pixel 1072 ain't gonna work very > well. Matches the X server's list. > > Signed-off-by: Adam Jackson > --- > drivers/gpu/drm/drm_edid.c |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c > index 18f41d7..10348d3 100644 Add my Tested-Off-By: Michael Tokarev if necessary. This is definitely a -stable matherial. Thanks! /mjt
Re: [PATCH] drm/edid: Fix 1024x...@85hz
Adam Jackson a...@redhat.com wrote at Thu May 13 11:55:28 PDT 2010: Having hsync both start and end on pixel 1072 ain't gonna work very well. Matches the X server's list. Signed-off-by: Adam Jackson ajax at redhat.com --- drivers/gpu/drm/drm_edid.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c index 18f41d7..10348d3 100644 Add my Tested-Off-By: Michael Tokarev m...@tls.msk.ru if necessary. This is definitely a -stable matherial. Thanks! /mjt ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
