LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 01-29-2009, 02:00 PM   #1
chiendarret
Member
 
Registered: Mar 2007
Posts: 234

Rep: Reputation: 15
startx failure


Hi:
With a multisocket Supermicro H8QC8 motherboard, used for computation and rarely for starting X, I had a RAM problem (one slot damaged; replaced OK). Probably on that occasion, when debian amd6a lenny failed to start, a problem arose with X, which I have only now noticed, as X is needed. startx does not work any more. It tries to launch, and something of the screen appears for a moment but X fails.

The error message is:

Command startx returns:

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux deb64 2.6.24-1-amd64 #1 SMP Sat May 10
09:28:10 UTC 2008 x86_64
Build Date: 09 January 2009 02:16:05AM

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 Jan 25 15:47:02 2009
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ddc" already built-in
(II) Module "ddc" already built-in
(II) Module "ramdac" already built-in
(II) Module "i2c" already built-in

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x48dd0a]
1: /lib/libc.so.6 [0x2ab82827df60]

Fatal server error:
Caught signal 11. Server aborting

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"

after 0 requests (0 known processed) with 0 events remaining.
=====
Information on the related hardware (I could pride lshw output, or sections of that, on request):

(WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/Type1" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi" does not exist.
(WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
does not exist.
(WW) MACH64(0): Cannot shadow an accelerated frame buffer.
============

Section "Module"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "Device"
Identifier "ATI Technologies Inc Rage XL"
Driver "ati"
BusID "PCI:3:1:0"
EndSection
=================

03:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
===============
The script in my .bashrc reads:

#!/bin/sh
xrdb -load$HOME/.Xresources
exec xterm
=====

If .Xresources is read from /etc/X11/Xsession.d/30x11-common
(of which I am not sure), 30x11-common reads:

# $Id: 30x11-common_xresources 305 2005-07-03 18:51:43Z dnusinow $

# This file is sourced by Xsession(5), not executed.

# If xrdb (from xbase-clients) is installed, merge system-wide X resources.
# Then merge the user's X resources, if the options file is so configured.
if /usr/bin/which xrdb >/dev/null 2>&1; then
if [ -d "$SYSRESOURCES" ]; then
RESOURCEFILES=$(run-parts --list $SYSRESOURCES)
if [ -n "$RESOURCEFILES" ]; then
for RESOURCEFILE in $RESOURCEFILES; do
xrdb -merge $RESOURCEFILE
done
fi
fi

if grep -qs ^allow-user-resources "$OPTIONFILE"; then
if [ -f "$USRRESOURCES" ]; then
xrdb -merge $USRRESOURCES
fi
fi
else
# Comment out this command if you desire a legacy-free X environment, and find
# the warning spurious.
message "warning: xrdb command not found; X resources not merged."
fi

# vim:set ai et sts=2 sw=2 tw=80:
======

Comparing with the ssh-bound desktop, running on debian i386 lenny, and where startx works regularly, the xorg.conf files are identical on the two machines.

The script startx is also identical on the two machine.

The files present in /etc/X11 are the same on the two machines, except, for the 64 bit machine, four additional xorg.conf.############## (where # are arabic numerals, from the attempted reconfigurations) and an additional directory, XvMCConfig containing libXvMC.so.1, although I never tried to have 3D acceleration, which I do not need.
==
I tried

#dpkg-reconfigure xserver -xorg

setting:

kernel framebuffer device interface: yes

Keyboard layout: pc104

but id did not help.




Thanks for your help

chiendarret
 
Old 01-29-2009, 02:26 PM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,621

Rep: Reputation: Disabled
Usually, when X fail I find error (EE) messages in X logs. Try:
Code:
tail --lines 200 /var/log/Xorg.0.log|grep EE
Replace Xorg.0.log by the last log's filename if needed.
 
Old 01-29-2009, 06:41 PM   #3
chiendarret
Member
 
Registered: Mar 2007
Posts: 234

Original Poster
Rep: Reputation: 15
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1280x768" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1280x800" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1152x768" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1152x864" (width too large for virtual size)
(II) MACH64(0): Not using default mode "576x432" (hsync out of range)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "700x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "700x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "700x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "700x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1440x900" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1600x1024" (width too large for virtual size)
(II) MACH64(0): Not using default mode "800x512" (hsync out of range)
(II) MACH64(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "840x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1920x1200" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1920x1200" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(--) MACH64(0): Virtual size is 1024x768 (pitch 1024)
(**) MACH64(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Driver mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz
(II) MACH64(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
(**) MACH64(0): *Driver mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Driver mode "1024x768": 63.5 MHz, 47.8 kHz, 59.9 Hz
(II) MACH64(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz)
(**) MACH64(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Driver mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) MACH64(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) MACH64(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) MACH64(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Driver mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) MACH64(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) MACH64(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Driver mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) MACH64(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) MACH64(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) MACH64(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) MACH64(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) MACH64(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "720x450": 54.4 MHz, 56.9 kHz, 60.2 Hz (D)
(II) MACH64(0): Modeline "720x450"x60.2 54.42 720 736 940 956 450 459 463 473 doublescan +hsync +vsync (56.9 kHz)
(**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) MACH64(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Driver mode "640x480": 30.2 MHz, 35.0 kHz, 66.7 Hz
(II) MACH64(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
(**) MACH64(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) MACH64(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) MACH64(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) MACH64(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(**) MACH64(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(**) MACH64(0): *Default mode "640x400": 41.7 MHz, 49.7 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "640x400"x60.0 41.73 640 672 740 840 400 400 402 414 doublescan (49.7 kHz)
(**) MACH64(0): *Default mode "640x384": 40.1 MHz, 47.7 kHz, 60.1 Hz (D)
(II) MACH64(0): Modeline "640x384"x60.1 40.07 640 672 740 840 384 384 386 397 doublescan (47.7 kHz)
(**) MACH64(0): *Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D)
(II) MACH64(0): Modeline "576x384"x54.8 32.50 576 589 657 736 384 385 388 403 doublescan +hsync +vsync (44.2 kHz)
(**) MACH64(0): *Default mode "512x384": 39.4 MHz, 60.0 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
(II) MACH64(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
(II) MACH64(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
(II) MACH64(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
(II) MACH64(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(II) MACH64(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) MACH64(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
(II) MACH64(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) MACH64(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz)
(**) MACH64(0): Display dimensions: (300, 230) mm
(**) MACH64(0): DPI set to (86, 84)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.2.0
ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module "i2c" already built-in
(II) MACH64(0): I2C bus "Mach64" initialized.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xfe4ff000 - 0xfe4fffff (0x1000) MS[B]
[1] 0 0 0xfd000000 - 0xfdffffff (0x1000000) MS[B]
[2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[6] -1 0 0xfe9c0000 - 0xfe9dffff (0x20000) MX[B]
[7] -1 0 0xfe9e0000 - 0xfe9fffff (0x20000) MX[B]
[8] -1 0 0xfeaff000 - 0xfeafffff (0x1000) MX[B]
[9] -1 0 0xfeafe000 - 0xfeafefff (0x1000) MX[B]
[10] -1 0 0xfe7fe000 - 0xfe7fefff (0x1000) MX[B]
[11] -1 0 0xfe7ff000 - 0xfe7fffff (0x1000) MX[B]
[12] -1 0 0xfe7e0000 - 0xfe7e00ff (0x100) MX[B]
[13] -1 0 0xfe7fd000 - 0xfe7fdfff (0x1000) MX[B]
[14] -1 0 0xfc600000 - 0xfc61ffff (0x20000) MX[B](B)
[15] -1 0 0xfe4ff000 - 0xfe4fffff (0x1000) MX[B](B)
[16] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU)
[18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU)
[19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU)
[20] 0 0 0x0000b800 - 0x0000b8ff (0x100) IS[B]
[21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[23] -1 0 0x0000f800 - 0x0000f83f (0x40) IX[B]
[24] -1 0 0x0000fc00 - 0x0000fc3f (0x40) IX[B]
[25] -1 0 0x0000c800 - 0x0000c80f (0x10) IX[B]
[26] -1 0 0x0000cc00 - 0x0000cc03 (0x4) IX[B]
[27] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B]
[28] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B]
[29] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B]
[30] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[31] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[32] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[33] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[34] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[35] -1 0 0x00003000 - 0x0000300f (0x10) IX[B]
[36] -1 0 0x00004c40 - 0x00004c7f (0x40) IX[B]
[37] -1 0 0x00004c00 - 0x00004c3f (0x40) IX[B]
[38] -1 0 0x00004cc0 - 0x00004cdf (0x20) IX[B]
[39] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B](B)
[40] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[41] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(==) MACH64(0): Write-combining range (0xfd000000,0x800000)
(II) MACH64(0): [drm] SAREA 2200+1208: 3408
(II) MACH64(0): DRIScreenInit for fglrx driver
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed

Backtrace:
0: X(xf86SigHandler+0x6a) [0x48dd0a]
1: /lib/libc.so.6 [0x2b1686b4ef60]

Fatal server error:
Caught signal 11. Server aborting
 
Old 01-29-2009, 11:56 PM   #4
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,400

Rep: Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584
it looks like this says it all
Quote:
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
how much ram is on this system
 
Old 01-30-2009, 02:45 AM   #5
chiendarret
Member
 
Registered: Mar 2007
Posts: 234

Original Poster
Rep: Reputation: 15
UMA-type machine DDR1 ECC registered 24GB

cat /proc/sys/kernel/shmmax
24284856000

No, the problem is not there.
 
Old 01-30-2009, 03:22 AM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,621

Rep: Reputation: Disabled
Then the problem could be related to direct rendering. Try disallowing DRI, and please post your whole /etc/X11/xorg.conf, surrounded by [CODE] tags so it be easier to read (when posting, hit the 'Go Advanced' button and you will find a button to do that after highlighting xorg.conf).
 
Old 01-30-2009, 03:48 AM   #7
chiendarret
Member
 
Registered: Mar 2007
Posts: 234

Original Poster
Rep: Reputation: 15
I am unfamiliar with "disabling DRI". As a very long computation (which can not be restarted!) is on the way, involving 100% all CPU,s, I would prefer to delay that to avoid risks. As to the requested xorg.conf:

# xorg.conf (X.Org 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 "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
EndSection

Section "Device"
Identifier "Configured Video Device"
Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
EndSectionthanks
 
Old 01-30-2009, 04:35 AM   #8
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,621

Rep: Reputation: Disabled
If that is really everything you have in xorg.conf, it is missing a lot of information. If not please send whole content of that file.

As far as I know, among many other settings you should have at least one "Server Layout" section and you are missing a lot of information in your "Screen" section, as DefaultDepth and "Display" subsections for every depth with available modes. And you are missing HorizSync and VertRefresh settings in your "Monitor" section.

For your information here is a decent xorg.conf content as shipped with Slackware 12.2:
Code:
# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **********************************************************************

# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
    Load        "freetype"
    #Load        "speedo"

# This loads the GLX module
    Load       "glx"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath	"/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
# 

    FontPath   "/usr/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/OTF/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

#    ModulePath "/usr/lib/xorg/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option     "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option     "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option     "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option     "DontZoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option     "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option     "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option     "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option     "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

#    Option      "blank time"    "10"    # 10 minutes

# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

#    Option      "standby time"  "20"
#    Option      "suspend time"  "30"
#    Option      "off time"      "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option   "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.

#    Option     "AutoRepeat"    "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

#    Option     "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    Option     "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
#    Option     "XkbLayout"     "de"
#
# or:
#
#    Option     "XkbLayout"     "de"
#    Option     "XkbVariant"    "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
#    Option     "XkbOptions"    "ctrl:swapcaps"


# These are the default XKB settings for X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

#    Option     "Protocol"      "Auto"

# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
    Option "Protocol"    "PS/2"

# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"	"Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"		"9600"
#    Option "SampleRate"	"150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection

# Some examples of extended input devices

# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"

# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 50.0

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "VESA Framebuffer"
    Monitor     "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#   DefaultDepth 8
#   DefaultDepth 16
   DefaultDepth 24
#   DefaultDepth 32

# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

    Subsection "Display"
        Depth       8
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1024x768" "800x600" "640x480"
    EndSubsection

EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"

    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Last edited by Didier Spaier; 01-30-2009 at 04:40 AM.
 
Old 01-30-2009, 06:24 AM   #9
chiendarret
Member
 
Registered: Mar 2007
Posts: 234

Original Poster
Rep: Reputation: 15
I try to keep the computing amd64 machine (the one with startx issues) and the ssh-linked i386 desktop configured the same way, as far as possible. Both debian lenny (amd64 vs i386). The xorg.cong of i386 (where startx is OK) is identical to the one that I posted for the amd64. I suspect that debian has different locations for the lacking stuff you are referring to. I had posted some days ago the startx problems of my amd64 to the debian list but I did not receive any suggestion. While I thank you for your advice, I apologize for my scarce ability as a system maintainer. I know the problems with electronic and mechanical molecular calculations better. It turns out that I need to start the X system to verify graphically the correctness of the molecule for a new input file. Incidentally, is X.Org X server 1.4.2 of my computers the same as for the XFree 86 Project that you posted?
chiendarret = francesco pietra, although that refers to my Epagneul breton.
 
Old 01-30-2009, 06:42 AM   #10
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,621

Rep: Reputation: Disabled
Quote:
Originally Posted by chiendarret View Post
Incidentally, is X.Org X server 1.4.2 of my computers the same as for the XFree 86 Project that you posted?
Yes Francesco, despite the Copyright notice I have the same server as yours:
Code:
bash-3.1$ X -version

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux machine 2.6.27.7-smp #1 SMP Thu Nov 20 22:18:02 CST 2008 i686
Build Date: 30 June 2008  11:35:29PM
 
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
bash-3.1
I hope you will find out what goes wrong.

[EDIT]Feel brave? Just make a copy of your xorg.conf, replace it by mine then startx, it shouln't break anything. May be X will not start but in this case look at the logs, at least you will have a basis that you can tune after looking at error messages.

Last edited by Didier Spaier; 01-30-2009 at 12:41 PM. Reason: Sugestion added
 
Old 01-30-2009, 12:18 PM   #11
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,400

Rep: Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584Reputation: 2584
renaming "xorg.conf" to xorg.conf-backup
and rebooting ( forcing a new conf to be made ) might help ?
 
Old 01-30-2009, 01:33 PM   #12
chiendarret
Member
 
Registered: Mar 2007
Posts: 234

Original Poster
Rep: Reputation: 15
I'll try as soon as this longer-than-expected calculation is finished. The code does not allow restarting.
Thanks
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
(nvidia) First startx = blank screen, second startx = works ?!? BuckRogers01 Linux - Hardware 2 04-07-2006 06:26 PM
startx failure raiden4201 Mandriva 5 10-20-2004 12:17 AM
Bug / Xwindows / startx : xinit works but startx crash www.rzr.free.fr Linux - Software 4 10-17-2004 09:06 AM
startx vs startx -- :2 (font dimension is different!!) moly82 Linux - General 7 09-15-2003 01:11 PM
power failure toasts startx and nfs keirobyn Linux - General 1 04-29-2002 08:07 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:17 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration