From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael D Labriola <michael.d.labriola@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>, David Airlie <airlied@linux.ie>,
Michael D Labriola <mlabriol@gdeb.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: gma500: invalid frequency for monitor
Date: Sat, 4 Feb 2012 11:41:01 +0000 [thread overview]
Message-ID: <20120204114101.28b90fdf@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <85aa4zs1q8.fsf@gmail.com>
> My system boots up, loads drm, loads gma500_gfx, and then my monitor's
> OSD says "Out of Frequency". Pretty much the same behavior with the
> old psb_gfx module and the new gma500_gfx module.
They are all basically the same logic until the most recent release which
at least queries the monitor for the actual system ports it knows how to.
>
> My system is configured with a LVDS-VGA adapter board, which is
> plugged into the VGA port on a 1680x1050 LCD. The BIOS for the Ocelot
> is configured for a 1280x1024 LVDS panel, which seems like a
> resolution my monitor should be able to handle. I've attached
> relevant kernel log with drm.debug set to 999.
I don't have a setup with an LVDS-VGA adapter board to test, but my guess
would be that even if we pick a mode the panel can do we'll pick a clock
rate that it cannot.
> I think my setup is correct, because the vesa frambuffer seems to work
> correctly. All is well unless I load the gma500_gfx driver and let it
> set the mode.
What mode is the vesa driver using and if you set the same mode what
happens ?
> [ 110.197942] ioremap error for 0x7f7f8000-0x7f7fb000, requested 0x10, got 0x0
That is expected
> [ 110.206418] [drm:drm_mode_debug_printmodeline], Modeline 0:"1280x1024" 0 108000 1280 1328 1440 1688 1024 1025 1028 1072 0x8 0x0
So we picked 1280x1024
> [ 110.257714] [drm:drm_sysfs_connector_add], adding "LVDS-1" to sysfs
> [ 110.257932] [drm:drm_sysfs_hotplug_event], generating hotplug event
> [ 110.269604] [drm:psb_intel_sdvo_read_byte], i2c transfer returned -6
> [ 110.269633] [drm:psb_intel_sdvo_init], No SDVO device found on SDVOB
We found the LVDS, we found nothing on the SDVO
> [ 110.561304] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1]
> [ 110.586242] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1] probed modes :
> [ 110.586274] [drm:drm_mode_debug_printmodeline], Modeline 10:"1280x1024" 40 71500 1280 1328 1440 1688 1024 1025 1028 1072 0x8 0x0
And we probed a 1280x1024 mode with a clock of 71.5 (which might be a bit
high for the panel ?)
> [ 110.637467] [drm:drm_crtc_helper_set_config], crtc has no fb, full mode set
> [ 110.637484] [drm:drm_crtc_helper_set_config], modes are different, full mode set
We didn't have a mode before, we have one now.
> [ 110.637500] [drm:drm_mode_debug_printmodeline], Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
> [ 110.637529] [drm:drm_mode_debug_printmodeline], Modeline 11:"1280x1024" 40 71500 1280 1328 1440 1688 1024 1025 1028 1072 0x8 0x0
> [ 110.637564] [drm:drm_crtc_helper_set_config], encoder changed, full mode switch
> [ 110.637580] [drm:drm_crtc_helper_set_config], crtc changed, full mode switch
> [ 110.637599] [drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] to [CRTC:4]
Do a full load
> [ 110.637618] [drm:drm_crtc_helper_set_config], attempting to set mode from userspace
> [ 110.637634] [drm:drm_mode_debug_printmodeline], Modeline 11:"1280x1024" 40 71500 1280 1328 1440 1688 1024 1025 1028 1072 0x8 0x0
> [ 110.637678] [drm:drm_crtc_helper_set_mode], [CRTC:4]
> [ 110.658501] [drm:drm_mode_debug_printmodeline], Modeline 11:"1280x1024" 40 71500 1280 1328 1440 1688 1024 1025 1028 1072 0x8 0x0
> [ 110.699109] [drm:drm_crtc_helper_set_mode], [ENCODER:8:LVDS-8] set [MODE:11:1280x1024]
> [ 110.977395] [drm:drm_calc_timestamping_constants], crtc 4: hwmode: htotal 1688, vtotal 1072, vdisplay 1024
> [ 110.977415] [drm:drm_calc_timestamping_constants], crtc 4: clock 71500 kHz framedur 25307776 linedur 23608, pixeldur 13
We set it all up and seem happy.
> [ 110.977439] [drm:drm_crtc_helper_set_config], Setting connector DPMS state to on
> [ 110.977453] [drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] set DPMS on
> [ 111.032366] Console: switching to colour frame buffer device 160x64
> [ 111.064932] fb0: psbfb frame buffer device
> [ 111.064944] drm: registered panic notifier
> [ 111.066827] gma500 0000:00:02.0: Backlight lvds set brightness 7a120000
> [ 111.066860] [drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0
Do you have a different monitor around to try and also hand setting lower
modes ?
next prev parent reply other threads:[~2012-02-04 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 3:42 Michael D Labriola
2012-02-04 11:41 ` Alan Cox [this message]
2012-02-05 3:05 ` Michael Labriola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120204114101.28b90fdf@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=airlied@linux.ie \
--cc=alan@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.d.labriola@gmail.com \
--cc=mlabriol@gdeb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome