[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: URGENT: Intel Corporation Q963/Q965 : xorg problem



It doesn't solve your problem, but at least you are not alone.

I also have this card and if I switch from X to console (sometimes it
happens only if I do it twice).
The console becomes unreadable, with some kind of rows and letters overlaying.
Again, if I use vesa driver, it doesn't happen.

On 10/2/07, Stephane Durieux <durieux42@yahoo.fr> wrote:
> Hello,
>
> I have a serious problem with Q963/Q965 graphic intel
> card. I use the driver i810 and everything seems ok
> except when I try to switch from X to console and to
> back to X.
> Then the display seems to be desynchronised.
>
> I have tried a X restart but without success ...
> The only thing wich succeeds is to reboot
>
> Here are the logs that could help :
>
> (WW) I810(0): Successfully set original devices (WW)
> I810(0): Setting the original video mode instead of
> restoring
>        the saved state
> (WW) I810(0): Extended BIOS function 0x5f05 not
> supported.
> (II) I810(0): BIOS call 0x5f05 not supported, setting
> refresh with VBE 3 method.(II) I810(0):
> xf86UnbindGARTMemory: unbind key 8 (II) I810(0):
> xf86UnbindGARTMemory: unbind key 0
> (II) I810(0): xf86UnbindGARTMemory: unbind key 1
> (II) I810(0): xf86UnbindGARTMemory: unbind key 3
> (II) I810(0): xf86UnbindGARTMemory: unbind key 2
> (II) I810(0): xf86UnbindGARTMemory: unbind key 4
> (II) I810(0): xf86UnbindGARTMemory: unbind key 5
> (II) I810(0): xf86UnbindGARTMemory: unbind key 6
> (II) I810(0): xf86UnbindGARTMemory: unbind key 7
> (WW) I810(0): Successfully set original devices (2)
> (II) I810(0): [drm] removed 1 reserved context for
> kernel
> (II) I810(0): [drm] unmapping 8192 bytes of SAREA
> 0xf8a9c000 at 0xb7b0f000
>
>
> At the beginning, I have suspected a problem with the
> keyboard cause I have a message describing a problem
> with setkeycode .
> So I tried getkeycodes which returned :
>
> Plain scancodes xx (hex) versus keycodes (dec)
> 0 is an error; for 1-88 (0x01-0x58) scancode equals
> keycode
>
> KDGETKEYCODE: Aucun périphérique de ce type
> failed to get keycode for scancode 0x5a
>  0x58:   88  89
>
> But, when I replace i810 by vga driver the problem
> disappears ...
>
> can someone help me ...
>
>
>
> Stephane Durieux
>
>
>
>
>      _____________________________________________________________________________
> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


-- 
Henrique G. Abreu
henrique@turbokit.com.br



Reply to: