Thanks for trimming the xorg.conf down so much. There's a number of
errors and warnings in your log file, although none that look like
they'd cause the problem you're seeing. This one looks unusual; I've
not see this before:
(II) Module sil164: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(EE) intel(0): detecting sil164
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
Soren, can you compare your Xorg.0.log with Chris' to see what errors
you both see in common?
Also, specific modules can be disabled by including this in the
xorg.conf:
Section "Modules"
Disable "<modulename>"
EndSection
It might be of interest to use this to disable modules like sil164 that
are generating errors. I doubt it'll have an effect, but would be easy
to test.
If it's possible, please test this on Tribe 5. That version preceded a
bunch of xserver backport work that pulled in a number of patches,
including a few that affected how the intel driver works. If we can
rule that in or out it'll help narrow the search for the problem.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
