Re: i810 driver and X
Hi all
been fiddling a little since the original post.
i did try the xorg packages suggested - unfortunately no change.
i also noticed some other funnies with xorg (at least the packages i
downloaded - later said to be dated and buggy). in any case, i've been
scared off the xorg packages, probably until they hit testing.
its a bummer that this problem exists as i intend to use the laptop for
presentations and demos. i think i'll switch to the vesa driver as this
doesn't garbage the display on either screen - can't really notice any
difference in the display under vesa with the apps i'm running (not
doing any 3d crap or other graphics intensive apps).
will try again with the i810 driver when debian xorg matures -
particularly the settings as described in
http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-May/026680.html
thanks to all that replied.
Takis
On Mon, 2005-07-11 at 00:05 +1000, Takis Diakoumis wrote:
> Hi
>
> i'm experiencing a problem when switching views from laptop lcd to
> external display and back or with both.
>
> i have an IBM ThinkPad R51 2887GVM running debian testing.
>
> it uses the i855GM video chip and i'm using the i810 driver in X.
> i have the relevant modules loaded in the kernel (custom debian kernel
> 2.6.11) - i830 and intel_agp.
>
> when switching to external display the top of the screen is garbage and
> the screen has moved down. when switching to both screens - both exhibit
> the top 50 or so pixels as garbage and when switching back to laptop
> screen only it stays as garbage. the only way i can retrieve that part
> of the screen is to restart X.
>
> i have posted a shot of both screens at:
> for the external monitor -
> http://www.executequery.org/linuxthinkpad/thinkpad-monitor.jpg
> for the laptop lcd -
> http://www.executequery.org/linuxthinkpad/thinkpad-screen.jpg
>
> interestingly, using the vesa driver in X instead of i810 does not cause
> this issue - it works as expected.
>
> has anyone else experienced this with the xfree i810 driver?
> is there a way i can fix this? a work around - other than "use the vesa
> driver" ;)
>
> any suggestions would be appreciated.
>
> thanks
> Takis
>
>
>
>
Reply to: