Re: [Unichrome-devel] Issues with unichrome on K8M800

[Philip P. <phi...@re...>]

Well, I got the CVS sources for the VIA drivers and built them as
part of 6.8.1 (thanks Terry). The only change I had to make was to
add in my motherboard:

http://www.msicomputer.com/product/p_spec.asp?model=K8MM-V&class=mb

and I've added the diff at the end of this mail.

I then tried to startx with a fairly simple xorg.conf file (which I didn't
attach, but I could if you all think it would help.)

Saw the messages:

(II) VIA(0): ViaI2CInit
(II) VIA(0): ViaI2CBus1Init
(II) VIA(0): I2C bus "I2C bus 1" initialized.
(II) VIA(0): ViaI2cBus2Init
(II) VIA(0): I2C bus "I2C bus 2" initialized.
(II) VIA(0): ViaI2CBus3Init
(II) VIA(0): I2C bus "I2C bus 3" initialized.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib64/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) VIA(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.
(II) VIA(0): I2C device "I2C bus 1:ddc2" removed.


but didn't think twice about it. Perhaps 1 of the 3 I2C busses isn't
connected...

Then I noticed:

(II) VIA(0): ViaValidMode: Validating 640x350 (31500)
(II) VIA(0): ViaModePrimaryVGAValid
(II) VIA(0): Not using default mode "640x350" (no clock available for mode)
(II) VIA(0): Not using default mode "320x175" (bad mode 
clock/interlace/doublescan)


(etc). I've never seen "no clock available for mode".

This is a curious one. And finally:

(WW) VIA(0): Mode pool is empty
(EE) VIA(0): No valid modes found
...
(EE) Screen(s) found, but none have a usable configuration.


Anyone want to venture a guess? I'd be happy to try out a patch
or gather more debugging info. I haven't hacked X in 20 years,
though... So I'm a bit rusty... and things are very different from
the old Vaxstation-II hardware. ;-)

-Philip