On Thu, 05 Jul 2007 11:24:14 +0200 Brice Goglin <[EMAIL PROTECTED]> wrote:
> Clayton wrote: > > On Wed, 13 Jun 2007 20:37:07 +0200 > > Brice Goglin <[EMAIL PROTECTED]> wrote: > > > > > >>> I also tried the vesa module, and had exactly the same result: > >>> blank screen, unresponsive keyboard. > >>> > >> I wonder whether it could be related to > >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424684 (vesa > >> driver broken) which has a candidate patch pending. > >> > > > > Hmmm, 424684 is reporting: > > (EE) VESA(0): No matching modes > > For vesa, in my log I am seeing: > > (EE) Screen(s) found, but none have a usable configuration. > > But I can't say that I remember actually ever *seeing* vesa run on > > this machine. It is just notable that in the current messed-up > > state behavior is exactly the same as when using the Silicon Motion > > driver. > > xserver-xorg-core 2:1.3.0.0.dfsg-7 has been uploaded to unstable > today. It contains a VBE/VESA fix which might help with your > siliconmotion driver too. No progress I am afraid, the same blank screen and locked keyboard for both the vesa and silicon motion drivers using latest unstable xorg. Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
