Sven Arvidsson([EMAIL PROTECTED]) is reported to have said:
> > Took me a few days but finally got the 100+Meg update completed and
> > now find I don't have a working X anymore. Actually it 'might' be
> > working but I can't see it working because the screen is black but
> > the log shows..
>
> Hi,
>
> A few suggestions, apologies in advance if you already have tried
> all this... :-)
>
> Can you provide the full log from X?
>
Log from a user starting X with xserver-xorg-video-tseng
------------------------
xauth: creating new authority file /home/wtopa/.serverauth.6003
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux buddy.mtntop.home 2.6.15y #6 Sun Jul 2 23:10:23
EDT 2006 i686
Build Date: 07 July 2006
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, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 10 16:11:38 2006
(==) Using config file: "/etc/X11/xorg.conf"
dlopen: /usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol:
_glapi_Dispatch
(EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so
(EE) Failed to load module "GLcore" (loader failed, 7)
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc104)+us" };
xkb_geometry { include "pc(pc104)" };
BScreen::BScreen: managing screen 0 using visual 0x23, depth 16
NOTE: There 'was' an error "(EE) AIGLX: Screen 0 is not DRI capable".
I was advised to add
Section "ServerFlags"
Option "AIGLX" "off"
EndSEction
at the end of the xorg.config. That removed the error message.
-------------
log from root starting with xserver-xorg-video-tseng
-------------
xauth: creating new authority file /root/.serverauth.10706
xauth: (stdin):2: unknown command "b1a7854ea2cf0023f25ce4489bf13847"
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux buddy 2.6.18-3-k7 #1 SMP Mon Dec 4 17:23:11 UTC
2006 i686
Build Date: 07 July 2006
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, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 11 13:21:51 2006
(==) Using config file: "/etc/X11/xorg.conf"
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc105)+us" };
xkb_geometry { include "pc(pc104)" };
Failed to read: session.tabs
Setting default value
Failed to read: session.ignoreBorder
Setting default value
Failed to read: session.forcePseudoTransparency
Setting default value
Failed to read: session.numLayers
Setting default value
Failed to read: session.tabPadding
Setting default value
---------------
These Failed to read: messages continue for 3-4 pages
NOTE: The monitor power LEd changes to yellow (standby) when configured
to use the tseng driver.
> Do you think this is similar to bug 394687[0]?
>
I thought not but now I wonder. I had the line "VideoRam 4096" in
the conf when the above errors happened. Which worked with xorg 7.0.
I just commented it out and now the driver fails with
----
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 11 13:51:01 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE) TSENG(0): No valid modes found
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
------
Not like 394687, but it does seem that the ramdac has something to do
with the failure.
> Have you tried to dpkg-reconfigure xserver-xorg and see if it helps?
> (Make a backup copy of xorg.conf first!) I seem to remember having
> to do so after after an X upgrade some time ago.
Yes, many times with many changes but it did not help.
> Have you tried reconfiguring X to use the vesa driver for the time
> being?
{Blush} No. It never occured to me. I just tried it and I do have an
ugly X now though. :-) Thanks for the reminder!!!
>
> Have you considered contacting / filing a bug with upstream directly
> about this? Try Bugzilla[1] or their mailing list[2].
I sent the above user information in a bug report, via reportbug, and sent
a copy to the "Debian X Strike Force" mailing list.
I don't normally use X as root and just tried that today.
> I hope one of the above suggestions can help,
>
Yes they did!!! I will now try getting the display to the resolution
I want and see if that can be done.
I will also try some other changes to the tseng xorg.conf to see if I
can get more information to help the developers track this problem
down.
Tnanks loads Sven! You have help me more than you know. I really
appreciate the 'kick' and hope that long post might help others as well.
Many, Many Thanks.
Best Regards
Wayne
--
Don't hit the keys so hard, it hurts.
_______________________________________________________
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
