Bug#428711: Ping: Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2008-10-04 Thread Clayton
I just tested with the latest and greatest xorg in testing. Behavior is
slightly different now:

$ lspci
Controller 00:02.0 VGA compatible controller: Silicon Motion, Inc.
SM712 LynxEM+ (rev a0)

xorg is trying to drive this graphics card with a neomagic driver now,
which of course fails.

I forced loading of the siliconmotion driver by manually adding
appropriate device and screen entries to xorg.conf, and I am back to a
blank screen and locked up keyboard, just like before.

Clayton



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-09-17 Thread Jonny
Hi,

Is 1.2.99.901-1 or 1.2.99.902-1 generated?
It is remembered that it was between 1.2.99.901-1 and 1.2.99.902-1 that the 
condition 
from which VT is set to blank screen by my machine began to occur.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-08-10 Thread Brice Goglin
Clayton wrote:
> On Thu, 09 Aug 2007 10:05:21 +0200
> Brice Goglin <[EMAIL PROTECTED]> wrote:
>
>   
>> Clayton wrote:
>> 
>>> Brice, I just added the "testing" version of only xserver-xorg-core
>>> to the snapshot.debian.net/archive/2007/03/08/debian/ version of
>>> xorg. And then booted into a blank screen. After downgrading
>>> xserver-xorg-core back down to
>>> snapshot.debian.net/archive/2007/03/08/debian/ everything 
>>>   
>> Hum, these URL are the same :)
>> One of them is version 1.1.1-20. The other is probably 1.3 something.
>> And I guess xserver-xorg-video-siliconmotion is still 1.4.1, right?
>> 
>
> Everything works under snapshot.debian.net/archive/2007/03/08/debian/
> --> xserver-xorg-core=2:1.1.1-19
> --> xserver-xorg-video-siliconmotion=1:1.4.1-4
>
> Replace above xserver-xorg-core (and nothing else changes) with
> xserver-xorg-core=2:1.3.0.0.dfsg-11 from testing and it breaks.
>   

Thanks a lot for the clarification, I'll notify the upstream developer.
He's supposed to look at the problem soon.

Brice



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-08-10 Thread Clayton
On Thu, 09 Aug 2007 10:05:21 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:

> Clayton wrote:
> > Brice, I just added the "testing" version of only xserver-xorg-core
> > to the snapshot.debian.net/archive/2007/03/08/debian/ version of
> > xorg. And then booted into a blank screen. After downgrading
> > xserver-xorg-core back down to
> > snapshot.debian.net/archive/2007/03/08/debian/ everything 
> 
> Hum, these URL are the same :)
> One of them is version 1.1.1-20. The other is probably 1.3 something.
> And I guess xserver-xorg-video-siliconmotion is still 1.4.1, right?

Everything works under snapshot.debian.net/archive/2007/03/08/debian/
--> xserver-xorg-core=2:1.1.1-19
--> xserver-xorg-video-siliconmotion=1:1.4.1-4

Replace above xserver-xorg-core (and nothing else changes) with
xserver-xorg-core=2:1.3.0.0.dfsg-11 from testing and it breaks.

Clayton


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-08-09 Thread Clayton
On Mon, 06 Aug 2007 17:56:23 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:

> Clayton wrote:
> > 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. 
> 
> Ok, if you have a chance to test it, please let me know.

Brice, I just added the "testing" version of only xserver-xorg-core to
the snapshot.debian.net/archive/2007/03/08/debian/ version of xorg. And
then booted into a blank screen. After downgrading xserver-xorg-core
back down to snapshot.debian.net/archive/2007/03/08/debian/ everything
worked again. It would appear the problem is indeed probably in
xserver-xorg-core and not the siliconmotion module.

Clayton


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-08-06 Thread Clayton
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]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-08-06 Thread Brice Goglin
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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-07-14 Thread Clayton
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]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-07-05 Thread Brice Goglin
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.

Thanks,
Brice



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-06-15 Thread Clayton
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.

> > Post upgrade, this machine is now dead in the water.
> 
> Try downgrading with
> http://snapshot.debian.net/archive/2007/03/08/debian/pool/main/x/xorg-server/xserver-xorg-core_1.1.1-20_i386.deb

I actually had to downgrade all of the xorg packages to 
http://snapshot.debian.net/archive/2007/03/08/debian/ to get the xserver to 
run, it was complaining about package versions not matching. But after some 
pulling of the hair, I succeeded (thank you apt-get) and X is working again. So 
we can't say for sure it is xserver-xorg-core, from this experiment.

If I can help debugging in any other way, don't hesitate to ask. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-06-13 Thread Brice Goglin
reassign 428711 xserver-xorg-core
found 428711 2:1.3.0.0.dfsg-6
retitle 428711 black screen and no keyboard on Silicon Motion with
Xserver 1.3
thank you




clayton wrote:
> I track testing with this machine. It was working just fine with 
> xorg/siliconmotion module until I upgraded to the 
> current testing version. Now starting X results in a blank screen, and a 
> locked up keyboard (Ctl-Alt-F1, 
> Ctl-Alt-Backspace seem to have no effect). I can still log in through the 
> network.
>   

Probably related to the upgrade of xserver-xorg-core to 1.3.

> (EE) AIGLX: Screen 0 is not DRI capable
>   

This is harmless and I think it has been changed to a warning for the
next releases.

> 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.

> Post upgrade, this machine is now dead in the water.
>   

Try downgrading with
   
http://snapshot.debian.net/archive/2007/03/08/debian/pool/main/x/xorg-server/xserver-xorg-core_1.1.1-20_i386.deb

Brice



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion

2007-06-13 Thread clayton
Package: xserver-xorg
Version: 1:7.2-5
Severity: important


I track testing with this machine. It was working just fine with 
xorg/siliconmotion module until I upgraded to the 
current testing version. Now starting X results in a blank screen, and a locked 
up keyboard (Ctl-Alt-F1, 
Ctl-Alt-Backspace seem to have no effect). I can still log in through the 
network.

The appended log file contains:

(EE) AIGLX: Screen 0 is not DRI capable

Note that I did make this go away at one point by turning off AIGLX, and 
behavior was unchanged.

I also tried the vesa module, and had exactly the same result: blank screen, 
unresponsive keyboard.

Post upgrade, this machine is now dead in the water.

-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg

/etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum.

X server symlink status:
lrwxrwxrwx 1 root root 13 2006-09-24 18:56 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1736280 2007-06-01 21:28 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Silicon Motion, Inc. SM712 LynxEM+ (rev a0)

/etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 2004 2007-06-14 00:46 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "Emulate3Buttons"   "true"
EndSection

Section "Device"
Identifier  "Generic Video Card"
Driver  "siliconmotion"
BusID   "PCI:0:2:0"
EndSection

Section "Monitor"
Identifier  "Generic Monitor"
Option  "DPMS"
HorizSync   28-40
VertRefresh 43-60
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "Generic Video Card"
Monitor "Generic Monitor"
DefaultDepth24
SubSection "Display"
Depth   1
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   4
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   8
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   15
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   16
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   24
Modes   "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier  "Default Layout"
Screen  "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection


Xorg X server log files on system:
-rw-r--r-- 1 root root 30216 2007-02-06 18:56 /var/log/Xorg.20.log
-rw-r--r-- 1 root root 27690 2007-06-14 00:46 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian
Current Operating System: Linux backup 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 
UTC 2007 i686
Build Date: 01 June 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) u