On Mon, 6 Aug 2007 16:25:24 +0200 Brice Goglin <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 15, 2007 at 12:20:35AM +0800, Clayton wrote: > > 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, do you know exactly which combination of xserver-xorg-core > and xserver-xorg-video-siliconmotion you tried so far? I forwarded > your bug upstream at > https://bugs.freedesktop.org/show_bug.cgi?id=11845 and the developer > wants to know whether you were using the same driver when you said > xserver-xorg-core 1.1 worked while 1.3 gave a black screen. > > I guess you initially had xserver-xorg-core 1.1 with siliconmotion > 1.4.1 (all from etch). Then you upgraded to 1.3 + 1.5.1 (current > testing) from what I see at the end of your first report. Then you > probably downgraded back to 1.3 + 1.4.1 to get something working > again. > > IIRC xserver-xorg-core 1.3 (testing/unstable) should work with > siliconmotion 1.4.1 (etch/stable). Did/could you check this > combination? It would help us be sure whether the problem is in the > server or the driver. > > Feel free to either reply direct in the upstream bug above or reply > here and will be forward your reply there. > > Thanks, > Brice Hi Brice, I am pretty sure that each time I moved from one version of xorg to another (snapshot.debian.net/archive/2007/03/08/debian/ <--> testing <--> unstable) *all* the xorg modules changed, including the modules. As I recall, apt-get was unwilling to easily let me do otherwise. So I do not think the combination of unstable xserver-xorg-core 1.3 and stable siliconmotion 1.4.1 was ever tested. Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
