Bug#476876: Log is ended up unexpectadly
You logs are incomplete. They are broken before the ScreenInit
section. I think that the hanging occurs before that moment. After the
place where your logs are ended up there must be something like this:
(==) s3(0): Write-combining range (0xf4000000,0x200000)
(==) s3(0): Backing store disabled
(II) s3(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 color pattern filled rectangles
Solid Lines
(II) s3(0): Acceleration enabled
(II) s3(0): Using PIO
(II) s3(0): Using SW cursor
(**) Option "dpms" "off"
(**) s3(0): DPMS enabled
(==) 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 XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(EE) AIGLX: DRI module not loaded
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us,ru"
(**) Keyboard0: XkbLayout: "us,ru"
(**) Option "XkbVariant" ",winkeys"
(**) Keyboard0: XkbVariant: ",winkeys"
(**) Option "XkbOptions" "grp:ctrl_shift_toggle,grp_led:scroll"
(**) Keyboard0: XkbOptions: "grp:ctrl_shift_toggle,grp_led:scroll"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "Protocol" "IMPS/2"
(**) Mouse0: Device: "/dev/input/mouse0"
(**) Mouse0: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/input/mouse0"
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(**) Option "Device" "/dev/input/mouse0"
The first line from this log is reffered to MTRR:
(==) s3(0): Write-combining range (0xf4000000,0x200000)
Is there something like MTRR in Digital Alpha? If not, try to disable
MTRR with option "NoMTRR" as first step and verify your log, whether it
goes further.
Section "Device"
Identifier "Trio64"
Driver "s3"
BusID "PCI:1:9:0"
Option "noaccel"
Option "NoMtrr"
VideoRAM 2048
EndSection
Reply to: