GDM problem

[hm]

Hi,

I'm runing Debian 2.6 with Gnome successfully for quite a while, however, since a recent system crash the graphical logon doesn't appear anymore. Instead the text-logon appears. I can still logon this way, do 'startx' and work normally, but when I want to do 'Action'->'Logout' it says 'GDM (Gnome Display Manager) not running ...' and freezes. Which is a bit annoying.
Any ideas how to fix this?
Best regards,

hm

[brother_mick]

I seem to remember last time I had that problem I used dpkg-reconfigure

dpkg-reconfigure gdm

[hm]

Thanks brother_mick,

I entered the comman as root and it says:

Reloading GNOME Display Manager Configuration. Changes will take effect when all current X sessions have ended.

My problem however is still the same.
Any more suggestions?
Thanks!

[vidd]

Hi,

I'm runing Debian 2.6 with Gnome successfully for quite a while, however, since a recent system crash the graphical logon doesn't appear anymore. Instead the text-logon appears. I can still logon this way, do 'startx' and work normally, but when I want to do 'Action'->'Logout' it says 'GDM (Gnome Display Manager) not running ...' and freezes. Which is a bit annoying.
Any ideas how to fix this?
Best regards,

hm

The command you want is gdm, not startx.

I beleive if you add gdm to your boot script, it will fix your problem

[bryansmith]

Have you changed your /etc/inittab at all? Perhaps the default runlevel was changed.

Bryan

[hm]

vidd: I entered 'gdm' an it doesn't produce an error message, which as far as I have figured out by now, is a good thing in Linuxland. However, doesn't make any improvement either.

bryansmith: not sure what I should try there. Below is the content of the file you mention.

Thanks!

/etc/inittab:

# /etc/inittab: init( configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:2:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns.
pf:owerwait:/etc/init.d/powerfail start
pn:owerfailnow:/etc/init.d/powerfail now
po:owerokwait:/etc/init.d/powerfail stop

# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

[vidd]

Do you still get the error when logging out?

I compared my /etc/inittab with what you posted and they are identical, so your issue is not in that file.

If worse comes to worse, you can always backup all your data files (pics, MP3's, etc) and reinstall Debian

[hm]

Yes, I still get the same error.
Um, I'd really be happy if I could avoid a reinstallation.
Isn't there some way to track the error, maybe in log files or the like?

[St. Joe]

Isn't there some way to track the error, maybe in log files or the like?

X messages are found in /var/log/Xorg.0.log.

[hm]

Sorry for spamming you, I didn't find xorg.0.log, but xfree86.0.log. I put the contents below, can anybody see something suspitious?

XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14 20050601051219 fabbione@fabbione.net)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.29-pre2 i686 [ELF]
Build Date: 01 June 2005

...
...
...

(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
...
...
[24] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.6
(II) SIS(0): SiS driver (2004/08/20-1)
(II) SIS(0): Copyright (C) 2001-2004 Thomas Winischhofer <thomas@winischhofer.net> and others
(II) SIS(0): Compiled for XFree86 version 4.3.0.1
(II) SIS(0): See http://www.winischhofer.net/linuxsisvga.shtml for documentation and updates
(--) SIS(0): This adapter is primary display adapter
(II) SIS(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0xcc80
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.6
(--) SIS(0): sisfb not found
(--) SIS(0): Relocated IO registers at 0xD000
(**) SIS(0): Depth 24, (--) framebuffer bpp 32
(==) SIS(0): RGB weight 888
(==) SIS(0): Default visual is TrueColor
(==) SIS(0): Using gamma correction (1.0, 1.0, 1.0)
(--) SIS(0): Video BIOS version "0.93.10 " found (new data layout)
(==) SIS(0): Using HW cursor
(==) SIS(0): Color HW cursor is enabled
(II) SIS(0): Using VRAM command queue, size 512k
(II) SIS(0): Hotkey display switching is enabled
(II) SIS(0): WARNING: Using the Hotkey might freeze your machine, regardless
(II) SIS(0): whether enabled or disabled. This is no driver bug.
(==) SIS(0): SiSCtrl utility interface is disabled
(==) SIS(0): DRI disabled
(II) SIS(0): Xv: Chroma key is of same format as video source
(--) SIS(0): DIMM0 is DDR SDRAM
(--) SIS(0): DIMM1 is not installed
(--) SIS(0): DIMM2 is not installed
(--) SIS(0): DRAM type: DDR SDRAM
(--) SIS(0): Memory clock: 166.446 MHz
(--) SIS(0): DRAM bus width: 64 bit
(--) SIS(0): Linear framebuffer at 0xE0000000
(--) SIS(0): MMIO registers at 0xED000000 (size 128K)
(--) SIS(0): VideoRAM: 32768 KB
(II) SIS(0): Using 32192K of framebuffer memory
(--) SIS(0): Hardware supports two video overlays
(II) SIS(0): CRT1 gamma correction is enabled
(II) SIS(0): Separate Xv gamma correction for CRT1 is disabled
(--) SIS(0): Memory bandwidth at 32 bpp is 665.784 MHz
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(--) SIS(0): CRT1 DDC probing failed
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Reloading /usr/X11R6/lib/modules/libvbe.a
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) SIS(0): initializing int10
(II) SIS(0): Primary V_BIOS segment is: 0xc000
(II) SIS(0): VESA BIOS detected
(II) SIS(0): VESA VBE Version 3.0
(II) SIS(0): VESA VBE Total Mem: 32768 kB
(II) SIS(0): VESA VBE OEM: SiS
(II) SIS(0): VESA VBE OEM Software Rev: 1.0
(II) SIS(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp.
(II) SIS(0): VESA VBE OEM Product: 6330
(II) SIS(0): VESA VBE OEM Product Rev: 0.93.10
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) SIS(0): VESA VBE DDC supported
(II) SIS(0): VESA VBE DDC Level none
(II) SIS(0): VESA VBE DDC transfer in appr. 0 sec.
(II) SIS(0): VESA VBE DDC read failed
(==) SIS(0): Min pixel clock is 12 MHz
(--) SIS(0): Max pixel clock is 400 MHz
(II) SIS(0): Replaced entire mode list with built-in modes
(II) SIS(0): "Unknown reason" in the following list means that the mode
(II) SIS(0): is not supported on the chipset/bridge/current output device.
(II) SIS(0): Generic Monitor: Using hsync range of 31.00-96.00 kHz
(II) SIS(0): Generic Monitor: Using vrefresh range of 50.00-120.00 Hz
(II) SIS(0): Clock range: 12.00 to 400.00 MHz
(II) SIS(0): Not using default mode "800x600" (hsync out of range)
(II) SIS(0): Not using default mode "640x480" (vrefresh out of range)
...
...
...
(II) SIS(0): Not using default mode "1360x768" (width too large for virtual size)
(--) SIS(0): Virtual size is 1280x1024 (pitch 1280)
(**) SIS(0): *Default mode "1280x1024": 157.5 MHz, 91.1 kHz, 85.0 Hz
(II) SIS(0): Modeline "1280x1024" 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
...
...
(**) SIS(0): Default mode "320x200": 12.5 MHz, 31.3 kHz, 70.9 Hz (D)
(II) SIS(0): Modeline "320x200" 12.53 320 328 376 400 200 206 207 221 doublescan -hsync +vsync
(++) SIS(0): DPI set to (100, 100)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 1.0.0
ABI class: XFree86 ANSI C Emulation, version 0.2
(II) SIS(0): Accel enabled
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 1.1.0
ABI class: XFree86 Video Driver, version 0.6
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xed000000 - 0xed01ffff (0x20000) MX[B]
[1] 0 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B]
...
...
[26] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[27] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Reloading /usr/X11R6/lib/modules/libvbe.a
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) SIS(0): initializing int10
(II) SIS(0): Primary V_BIOS segment is: 0xc000
(II) SIS(0): VESA BIOS detected
(II) SIS(0): VESA VBE Version 3.0
(II) SIS(0): VESA VBE Total Mem: 32768 kB
(II) SIS(0): VESA VBE OEM: SiS
(II) SIS(0): VESA VBE OEM Software Rev: 1.0
(II) SIS(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp.
(II) SIS(0): VESA VBE OEM Product: 6330
(II) SIS(0): VESA VBE OEM Product Rev: 0.93.10
(II) SIS(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0xcc80
(==) SIS(0): Write-combining range (0xe0000000,0x2000000)
(II) SIS(0): Setting standard mode 0x65
(II) SIS(0): RENDER acceleration enabled
(II) SIS(0): Frame Buffer From (0,0) To (1280,6437)
(II) SIS(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
8x8 color pattern filled rectangles
Solid Lines
Dashed Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
32 8x8 color pattern slots
(==) SIS(0): Backing store disabled
(==) SIS(0): Silken mouse enabled
(**) Option "dpms"
(**) SIS(0): DPMS enabled
(II) SIS(0): Using SiS300/315/330/340 series HW Xv
(II) SIS(0): Default Xv adaptor is Video Overlay
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 5
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Warning: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0
Could not init font path element unix/:7100, removing from list!
Could not init font path element /usr/local/share/fonts, removing from list!
GetModeLine - scrn: 0 clock: 157498
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 1024 vbeg: 1025 vend: 1028 vttl: 1072 flags: 5
(II) SIS(0): SISDisplayPowerManagementSet(0)