Re: IBM T22 S3 Savage Video Sarge to Etch Upgrade
On Mon, Apr 16, 2007 at 17:43:38 -0500, John T. Lapp wrote:
> Florian,
>
> egrep '^\((EE|WW)\)' /var/log/Xorg.0.log
[ snip: harmless FontPath warnings ]
> (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
This is not critical.
> (EE) SAVAGE(0): Insufficient Videoram available for 3D -- Try a lower color
> depth or smaller desktop. For integrated savages try increasing the
> videoram in the BIOS.
> (EE) SAVAGE(0): DRI isn't enabled
> (WW) SAVAGE(0): Direct rendering disabled
> (EE) AIGLX: Screen 0 is not DRI capable
Problem number one.
> (EE) xf86OpenSerial: Cannot open device /dev/psaux
> (EE) Configured Mouse: cannot open input device
> (EE) PreInit failed for input device "Configured Mouse"
> (EE) xf86OpenSerial: Cannot open device /dev/psaux
> (EE) PreInit failed for input device "Synaptics Touchpad"
> (WW) No core pointer registered
Problem number two.
> lspci | egrep -i 'vga|video|graphic|display'
> 01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 13)
>
>
> awk '/Section "Device"/,/EndSection/' /etc/X11/xorg.conf
> Section "Device"
> Identifier "S3 Inc. 86C270-294 Savage/IX-MV"
> Driver "savage"
> BusID "PCI:1:0:0"
> VideoRam 4000
> Option "UseFBDev" "true"
> EndSection
You seem to have two problems:
1) graphics card
Try to comment out the "VideoRam 4000" line from xorg.conf. If this does
not make the error go away then you have to reduce your resolution
and/or DefaultDepth. I think this error is not the reason for X to fail
completely, but your graphics rendering will be significantly faster and
use less CPU cycles if you get the DRI (direct rendering infrastructure)
going.
2) mouse and touchpad
There is a problem with the device node for mouse and touchpad. Try to
do "modprobe psmouse" as root and check if you can start X after that.
If this does not help then we need the output of these two commands:
ls -l /dev/input/by-id
awk '/Section "InputDevice"/,/EndSection/' /etc/X11/xorg.conf
Another thing to try is to add
Option "AllowMouseOpenFail" "true"
to the ServerFlags section of your xorg.conf (see "man xorg.conf"). This
will at least tell you if it is really the mouse issue that keeps X from
starting.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: