Opened 2 years ago

Last modified 4 months ago

#13536 new bug

Monitor complains with message: "Input Not Supported" with an Intel i965Q

Reported by: CodeforEvolution Owned by: kallisti5
Priority: normal Milestone: R1/beta2
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Hello! I am having a problem where my monitor will complain with a message saying "Input Not Supported" even though Haiku still runs like normal behind the hovering message. I am running hrev 51185 and unfortunately, I can't remember in which hrev the problem started. I'm running an Intel i965Q which makes use of the intel_extreme driver. Something to point out is that all the modes to use in the Screen prefs does not work, except the default configuration on boot.

Attachments (2)

syslog (112.2 KB ) - added by CodeforEvolution 2 years ago.
Haiku hrev51185 syslog
syslog.2 (227.5 KB ) - added by CodeforEvolution 2 years ago.
Haiku Alpha 4.1 Syslog

Download all attachments as: .zip

Change History (17)

by CodeforEvolution, 2 years ago

Attachment: syslog added

Haiku hrev51185 syslog

comment:1 by CodeforEvolution, 2 years ago

Has a Patch: set

comment:2 by CodeforEvolution, 2 years ago

Don't know why it says "patch set".

comment:3 by pulkomandy, 2 years ago

Has a Patch: unset

comment:4 by pulkomandy, 2 years ago

A syslog from alpha4.1 (if you can't find anything more recent that still doesn't show the bug) and/or the output from "intel_reg dump" on Linux could help seeing what changed.

As for the "patch set" thing, it is a bug in Trac since the latest update.

comment:5 by diver, 2 years ago

Component: DriversDrivers/Graphics/intel_extreme
Owner: changed from nobody to kallisti5

by CodeforEvolution, 2 years ago

Attachment: syslog.2 added

Haiku Alpha 4.1 Syslog

comment:6 by CodeforEvolution, 2 years ago

Has a Patch: set

comment:7 by CodeforEvolution, 2 years ago

Here is the log for Haiku Alpha 4.1 Interesting enough, it works without showing the "Input Not Supported" Message, and all the proposed dispaly modes, frequencies, and Color amount options work. (Except two very low resolution options at the 640x* range)

Last edited 2 years ago by CodeforEvolution (previous) (diff)

comment:8 by pulkomandy, 2 years ago

Alpha4.1:

1896	KERN: intel_extreme : hardware mode will actually be 1024x768
1897	KERN: PLL limits, min: p 5 (p1 1, p2 10), n 5, m 70 (m1 12, m2 7)
1898	KERN: PLL limits, max: p 80 (p1 8, p2 5), n 10, m 120 (m1 22, m2 11)
1899	KERN: required MHz: 65
1900	KERN: found: 65.1429 MHz, p = 28 (p1 = 2, p2 = 14), n = 6, m = 114 (m1 = 21, m2 = 9)
1901	KERN: PLL limits, min: p 5 (p1 1, p2 10), n 5, m 70 (m1 12, m2 7)
1902	KERN: PLL limits, max: p 80 (p1 8, p2 5), n 10, m 120 (m1 22, m2 11)
1903	KERN: required MHz: 65
1904	KERN: found: 65.28 MHz, p = 30 (p1 = 3, p2 = 10), n = 5, m = 102 (m1 = 19, m2 = 7)

Strange thing: why does it perform the search twice, and why does it not find the same result for the same input?

Nightly:

KERN: intel_extreme: SetDisplayMode: Analog A 1024x768
174	KERN: intel_extreme: compute_dpll_9xx: required MHz: 65
175	KERN: intel_extreme: PLL limits, min: p 5 (p1 1, p2 10), n 5, m 70 (m1 12, m2 7)
176	KERN: intel_extreme: PLL limits, max: p 80 (p1 8, p2 5), n 10, m 120 (m1 22, m2 11)
177	KERN: intel_extreme: compute_dpll_9xx: best MHz: 65.28 (error: 0.28)
178	KERN: intel_extreme: compute_pll_divisors: found: p = 30 (p1 = 3, p2 = 10), n = 5, m = 102 (m1 = 16, m2 = 10)

It finds the same timing as alpha4 second try, but with a different setting for the M1/M2 values. Maybe it results in a less stable clock, which your monitor then complains about? And why does it not pick the better solution at 65.1429MHz?

comment:9 by CodeforEvolution, 2 years ago

One thing I noticed when searching through the source code was that in the alpha, the pll calculation was done in the same source code file as the mode switcher, while in the nightlies, a whole separate source code file houses the pll calculation.

comment:10 by pulkomandy, 2 years ago

Has a Patch: unset

comment:11 by pulkomandy, 2 years ago

Has a Patch: unset

In the current driver, the PLL calculation handles several more generations of intel devices, each having different constraints on acceptable PLL values. This makes the PLL code somewhat more complex and this is why it was moved to a different file to keep things clear.

comment:12 by pulkomandy, 10 months ago

Milestone: UnscheduledR1/beta2

comment:13 by waddlesplash, 5 months ago

Has a Patch: unset

Please retest after hrev53040.

comment:14 by CodeforEvolution, 5 months ago

Well, the boot splash is showing again. However, after the boot splash completes, the screen remains black. I believe Haiku is still running in the background as the shutdown button still seems to work, with a little delay (while Haiku closes all applications assumably) and disk activity occurring before the computer completely turns off.

comment:15 by CodeforEvolution, 4 months ago

I can confirm that Haiku works as normal after blacklisting the intel_extreme driver. I still need to find a way to get a syslog to see what the intel_extreme driver was trying todo. The issue is I'm currently only using Haiku on a usb flash drive with the "livecd" image.

Note: See TracTickets for help on using tickets.