Bug 93744 - [byt dsi] Wrong PLL on HP Pro Tablet 408
Summary: [byt dsi] Wrong PLL on HP Pro Tablet 408
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-17 13:23 UTC by ettavolt
Modified: 2017-03-27 10:58 UTC (History)
2 users (show)

See Also:
i915 platform: BYT
i915 features: display/DSI


Attachments
Log with drm.debug=14 on kernel command line. (121.02 KB, text/plain)
2016-01-17 13:23 UTC, ettavolt
no flags Details
intel_bios_reader /sys/kernel/debug/dri/0/i915_opregion (intel-gpu-tools 1.13) (40.06 KB, text/plain)
2016-02-13 09:52 UTC, ettavolt
no flags Details

Description ettavolt 2016-01-17 13:23:23 UTC
Created attachment 121091 [details]
Log with drm.debug=14 on kernel command line.

I'm trying to configure Ubuntu 15.10 on HP Pro Tablet 408 G1 (P/N: L3S95AA#ACB if anyone interested). It is based on Z3736F.
Currently I'm stuck with problem in i915. It can't determine PLL divider (?).
With nomodeset I can get to desktop and then xrandr reports this mode: 800 x 1280 (0x26e) 78.848MHz / 98.56kHz / 77 Hz.
In the dmesg.log you can see modified '[drm:vlv_get_dsi_pclk [i915]] *ERROR* wrong m_seed programmed' message, because I thought I could get something useful out of pll_div value. :) Obviously, this was wrong.
I've got picture on LCD connected to HDMI. 'Displays' applet showed both screens active with native resolution set, but tablet's screen was black.
Will it help if I attach log for booting in such configuration? What debug level should I set?
Comment 1 ettavolt 2016-02-13 09:52:12 UTC
Created attachment 121736 [details]
intel_bios_reader /sys/kernel/debug/dri/0/i915_opregion (intel-gpu-tools 1.13)

Here is parsed video bios, if it helps.

Also, I've tried to hardcode
if (pll_div == 454 && p == 5) {
	return 70220;
}
in vlv_get_dsi_pclk. This way I get rid of the error, but unfortunately don't get any picture.
Comment 2 yann 2017-03-17 15:20:50 UTC
(In reply to ettavolt from comment #1)
> Created attachment 121736 [details]
> intel_bios_reader /sys/kernel/debug/dri/0/i915_opregion (intel-gpu-tools
> 1.13)
> 
> Here is parsed video bios, if it helps.
> 
> Also, I've tried to hardcode
> if (pll_div == 454 && p == 5) {
> 	return 70220;
> }
> in vlv_get_dsi_pclk. This way I get rid of the error, but unfortunately
> don't get any picture.

We seem to have neglected the bug a bit, apologies.

ettavolt@gmail.com, since There were improvements pushed in kernel that will benefit to your system, so please re-test with latest kernel and mark as REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log) and RESOLVED/* if you cannot reproduce.
Comment 3 ettavolt 2017-03-27 06:08:08 UTC
I was able to launch 4.10 kernel with live Ubuntu 17.04 beta without nomodeset param and get picture. Kernel log said, that 'i915 20161121 successfully initialized'. Date may not be exact.
X loaded 'i965' (?) driver but was laggy as if there was no acceleration. Maybe I need to install the system actually before it will work correctly.
But that's a story for a different bug.
Comment 4 yann 2017-03-27 10:58:38 UTC
(In reply to ettavolt from comment #3)
> I was able to launch 4.10 kernel with live Ubuntu 17.04 beta without
> nomodeset param and get picture. Kernel log said, that 'i915 20161121
> successfully initialized'. Date may not be exact.
> X loaded 'i965' (?) driver but was laggy as if there was no acceleration.
> Maybe I need to install the system actually before it will work correctly.
> But that's a story for a different bug.

Thanks ettavolt


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.