On Sat, Jun 13, 2009 at 2:30 AM, Brice Goglin wrote:
> Does this still happen with latest intel driver in unstable or
> experimental?
I haven't tried in quite some time. After failing to get the intel
driver to work, I installed an nvidia based card and started using
that. It's been my intention
I upgraded to version 2:2.4.2-1 today, and the problem is not yet
resolved.
I cannot get the driver to run at 1080p/i at all. It tries to run at
1920x540 instead, and the display can't handle that. No amount of
manual modeline settings in the config file seem to make any difference.
I can't seem
> I just uploaded 2.4.1 to experimental. Let me know if you have better
> luck with that version; if it's still broken, we'll have to report it
> upstream.
I'm not getting a lockup with this version, but I don't have a usable
display either. It's insisting on picking a display resolution
which i
> I just uploaded 2.4.1 to experimental. Let me know if you have better
> luck with that version; if it's still broken, we'll have to report it
> upstream.
Thanks, I'll try it shortly.
> For lenny, we'll make X choose the vesa driver for the new intel
> chipsets, as that's more likely to work th
> By the way does the version in sid work? (I tried to backport the
> necessary patches for non-HDMI output from 2.4, but may have missed some
> and have no G4x hardware to test.)
I've tried downgrading back to the version in sid, but I'm no longer
able to get it to work at all with sid's driver.
> probably needs this commit:
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?h=xf86-video-intel-2.4-branch&id=01bbbd8c6c73229b5cb0c88e8eb2ac9b49a5dad8
Ok. I can merge that patch in and build a new package to test.
> By the way does the version in sid work? (I tried to backpo
> probably needs this commit:
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?h=xf86-video-intel-2.4-branch&id=01bbbd8c6c73229b5cb0c88e8eb2ac9b49a5dad8
After applying that patch manually, rebuilding and reinstalling the
package, and restarting the X server, I saw no change in be
(0xb010) indicate ring
buffer not flushed
(WW) intel(0): Existing errors found in hardware state.
I'm running in 32-bit mode (both kernel and userland).
Switching to the vesa driver allows X to work, but, of course,
performance is lacking.
Eric Sharkey
-- Package-specific info:
Conten
Package: xbase-clients
Version: 4.3.0.dfsg.1-10
Severity: normal
When xclock is started without the -norender option, on a system with
xinerama enabled, the clock is completely blank when not on monitor 0.
I'm using the Matrox driver, and a dual head AGP G400 and a
PCI Millenium II.
Eric
-- Sy
9 matches
Mail list logo