I plugged i845G host t2240, normally used with an EDID-less CRT into a
Viewsonic 1400x1050 LCD to see what happens. The CRT works at up to 2048x1536
as long as I have a properly configured xorg.conf. I deleted xorg.conf and
rebooted t2240 after connecting the LCD. KDM comes up as expected, and login
proceeds normally most of the way into the KDE desktop, then the screen goes
black except for the mouse pointer. Can someone tell from
http://fm.no-ip.com/Tmp/Linux/Xorg/xsession-errors-i845G-114-t2240 what's
going wrong so I can find or file a bug against the right component? (another
dup and 2.6.37-22 kernel did not help)
--
"How much better to get wisdom than gold, to choose
understanding rather than silver." Proverbs 16:16 NKJV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
I have two systems with RC1 and this video chip, one with an Dell BIOS, for
which I filed https://bugzilla.novell.com/show_bug.cgi?id=671140 . The other
has an Intel BIOS. Unlike the other, it loads the Intel driver, but KDM/KDE
only partly work.
Regardless whether I use an xorg.conf or not, KDM & startx give little more
than black screens. .xsession-errors excerpts:
(EE) intel(0): Detected a hung GPU, disabling acceleration
(EE) intel(0): failed to set cursor: Input/output error
(EE) intel(0): [DRI2] DRI2SwapBuffers: drawable has no back or front?
= GDB Backtrace =
==================== Backtrace ================
Thread 1 (Thread 0xb72a26c0 (LWP 2561)):
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb74008f3 in __waitpid_nocancel () from /lib/libc.so.6
#2 0x080ee84c in xorg_backtrace ()
#3 0x080a2aaa in ?? ()
No symbol table info available.
#4 <signal handler called>
No symbol table info available.
#5 0xb71a3d72 in ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
No symbol table info available.
#6 0xb71eefa9 in ?? () from /usr/lib/xorg/modules/extensions/libdri2.so
No symbol table info available.
#7 0xb71f0cd7 in ?? () from /usr/lib/xorg/modules/extensions/libdri2.so
No symbol table info available.
#8 0x0807a717 in ?? ()
No symbol table info available.
#9 0x080668f5 in _start ()
No symbol table info available.
==================== Backtrace End ============
Segmentation fault at address 0xbababad2
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
t2240 was a minimal install experiment last time, so I installed fresh from
RC1 iso, but it didn't change anything. The KDE splash came up for a while
from startx (at least once), then the screen went black except for mouse
pointer. Ctrl-Alt-BS Ctrl-Alt-BS escapes the GUI, but startx fails to exit,
requiring Ctrl-C to get a prompt back. Init 5 won't even bring up a mouse
pointer from KDM.
I've not found a bug that looks like this in Novell's bugzilla, at least not
yet. Anyone have any insight?
--
"How much better to get wisdom than gold, to choose
understanding rather than silver." Proverbs 16:16 NKJV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
Hello,
I have a very serious problem with the nvidia drivers (since the
version, that come with the original openSuse 64 Bit system up to the
current version - see attached info document - I just installed the
latest version from the repository just before the test) on my system.
Each time I start the X-Server the system /crashes/ to point, that I
cannot do anything except pressing the reset button. Not even the
Num-lock, Shift-lock or Scroll-lock Leds work any more.
The bug-report file is attached.
I also did a dmesg in a loop from a remote login and, after staightening
it out (removed thousands of those NVRM: os_schedule: lines and
duplicate lines, cause by dmesg running in a loop, because there is not
-f flag like with tail) I got the following result, though I am not sure
what caused this stack trace).
I also did an strace /etc/init.d/kdm start, but for some reason, I did
not manage to capture it and I did not have the time to redo the strace.
I only remember that, there was a message on saying some like "X in
D-State, leaving it alone".
Also something I noticed, that running applications, e.g. top or the
strace did not stop, but when I stopped the X-Server, the shell did no
longer accept any key press and even ssh did not allow itself to be
stopped using ~.
Hope, somebody can help.
Thanks in advance
Dieter
--
Dieter Wörz