Need XF86Config for WD90C24 chipset. HELP?
Forum: Laptops
Topic: Need XF86Config for WD90C24 chipset. HELP?
started by: famewolf
Posted by famewolf on June 23 2005,13:10
I have installed the XFREE86.dsl package because the Ibm Thinkpad 360CE needs the SVGA server for the WD90C24 chipset it uses. I have made the changes to the .xserverrc file required by XFREE86.dsl. I am unable to locate ANY XF86Config that will work..they all tell me "no screens found"...I've tried all the included configs...hit google..found two different WD90C24 configs and tried them both...all tell me "no screens found"..one of them is available here: http://www.angelfire.com/nt/sucks/XF86Config.htmlAnother is here: < http://www.geocities.com/dueze/XF86Config-lte475.txt >
Can anyone tell me what I need to do to get this old laptop working with DSL? Delinux works with it but DSL is so much better.
Posted by ke4nt1 on June 23 2005,15:39
That is a version 3 of xfree86 config file you have posted ..You need to find a version 4 for the xfree86.dsl built for DSL.
( search google for an ' XF86config-4 ' file for your box. )
Also, did you try using the standard-fare XF86config-4 file
for vesa that comes in the xfree86.dsl package ?
73
ke4nt
Posted by clivesay on June 23 2005,16:20
Yes, google your lappy with the xf86config word also. I couldn't get the stock ones to work with my toshiba 430cdt but did some googling and eventually found one that worked for my lil' old toshiba. Remember if your lappy likes framebuffer or xvesa. There is a toshiba SVGA file in the .dsl package but it's framebuffer and my toshiba needed xvesa. Good luck
Chris
Posted by famewolf on June 23 2005,16:36
I tried ALL of the stock config's included the SVGA_FB and the vesa...vesa one just gives me a blank screen..can't see anything...SVGA_FB one and every other one I've located all give me no screen found errors...I don't think anyone has actually generated an XF86Config-4 for a 486 50mhz/ 36 meg of memory/ 500 meg hard drive...is there a way to convert them or to generate one?
Posted by famewolf on June 23 2005,16:41
Here is another I found ..is this the right revision? It gave me an error when I ran it but I'm willing to try again and do some debugging if I know I have the right one.[CODE]
# File generated by xf86config.
#
# Copyright © 1995 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.
# **********************************************************************
# **********************************************************************
# 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/X11R6/lib/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/X11R6/lib/X11/fonts/misc/:unscaled"
# FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
# FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
# For OSs that support Dynamically loaded modules, ModulePath can be
# used to set a search path for the modules. This is currently supported
# for Linux ELF, FreeBSD 2.x and NetBSD 1.x. The default path is shown
# here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which dynamically loadable modules to load. Dynamically loadable
# modules are currently supported only for Linux ELF, FreeBSD 2.x
# and NetBSD 1.x. Currently, dynamically loadable modules are used
# only for some extended input (XInput) device drivers.
# **********************************************************************
#
# Section "Module"
#
# This loads the module for the Joystick driver
#
# Load "xf86Jstk.so"
#
# 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
# NoTrapSignals
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# DontZap
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# 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.
# DisableVidModeExtension
# Uncomment this to enable the use of a non-local xvidtune client.
# AllowNonLocalXvidtune
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# DisableModInDev
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# AllowNonLocalModInDev
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Keyboard section
# **********************************************************************
Section "Keyboard"
Protocol "Standard"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
# Protocol "Xqueue"
AutoRepeat 500 30
# Let the server do the NumLock processing. This should only be required
# when using pre-R6 clients
# ServerNumLock
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Xleds 1 2 3
# To set the LeftAlt to Meta, RightAlt key to ModeShift,
# RightCtl key to Compose, and ScrollLock key to ModeLock:
# LeftAlt Meta
# RightAlt ModeShift
# RightCtl Compose
# ScrollLock ModeLock
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# XkbDisable
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# XkbModel "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# XkbModel "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# XkbLayout "de"
# or:
# XkbLayout "de"
# XkbVariant "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# XkbOptions "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# XkbRules "xfree86"
# XkbModel "pc101"
# XkbLayout "us"
# XkbVariant ""
# XkbOptions ""
# XkbKeymap "xfree86(us)"
XkbRules "xfree86"
XkbModel "pc102"
XkbLayout "no"
EndSection
# **********************************************************************
# Pointer section
# **********************************************************************
Section "Pointer"
Protocol "MouseManPlusPS/2"
Device "/dev/psaux"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Emulate3Buttons
# Emulate3Timeout 50
EndSection
# **********************************************************************
# Xinput section -- this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "Xinput"
# SubSection "WacomStylus"
# Port "/dev/ttyS1"
# DeviceName "Wacom"
# EndSubSection
# SubSection "WacomCursor"
# Port "/dev/ttyS1"
# EndSubSection
# SubSection "WacomEraser"
# Port "/dev/ttyS1"
# EndSubSection
#
# SubSection "Elographics"
# Port "/dev/ttyS1"
# DeviceName "Elo"
# MinimumXPosition 300
# MaximumXPosition 3500
# MinimumYPosition 300
# MaximumYPosition 3500
# Screen 0
# UntouchDelay 10
# ReportDelay 10
# EndSubSection
#
# SubSection "Joystick"
# Port "/dev/joy0"
# DeviceName "Joystick"
# TimeOut 10
# MinimumXPosition 100
# MaximumXPosition 1300
# MinimumYPosition 100
# MaximumYPosition 1100
# # CenterX 700
# # CenterY 600
# Delta 20
# EndSubSection
#
# The Mouse Subsection contains the same type of entries as the
# standard Pointer Section (see above), with the addition of the
# DeviceName entry.
#
# SubSection "Mouse"
# Port "/dev/mouse2"
# DeviceName "Second Mouse"
# Protocol "Logitech"
# EndSubSection
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
Section "Monitor"
Identifier "LCD"
VendorName "Unknown"
ModelName "Unknown"
Bandwidth 29
HorizSync 30-64
VertRefresh 50-100
Mode "640x480"
DotClock 25.175
HTimings 640 664 760 800
VTimings 480 491 493 525
EndMode
Mode "640x480.28"
DotClock 28.32
HTimings 640 680 720 864
VTimings 480 488 491 521
EndMode
Mode "800x600.36"
DotClock 36
HTimings 800 824 896 1024
VTimings 600 601 603 625
EndMode
Mode "800x600.50"
DotClock 50
HTimings 800 856 976 1040
VTimings 600 637 643 666
Flags "+hsync" "+vsync"
EndMode
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
Section "Device"
Identifier "WD90C24A2(laptop)"
VendorName "Western Digital"
BoardName "RocketChip"
#VideoRam 1024
Chipset "wd90c24"
# Clocks from 'X -probeonly'.
Clocks 25.18 28.32 65.00 36.00 29.98 77.41 62.20 59.96
Clocks 31.50 35.50 75.17 50.11 39.82 72.04 44.74 80.09
Clocks 44.30
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
Section "Screen"
Driver "svga"
Device "WD90C24A2(laptop)"
Monitor "LCD"
Subsection "Display"
Depth 8
Modes "640x480"
ViewPort 0 0
Visual "GrayScale"
EndSubsection
EndSection
[QUOTE]
Posted by famewolf on June 23 2005,22:11
I ran the config I previously posted and get the following:Parse error on line 332 on section Monitor in file /etc/X11/XF86Config-4
"Bandwidth" is not a valid keyword in this section.
Fatal Server error:
no screens found
.....
Commenting out the line with Bandwidth and trying again results in an error:
Data incomplete in file /etc/X11/XF86Config-4
Device Section "WD90C24A2(laptop) must have a Driver line.
and then the same no screens error.
Comments appreciated.
Posted by clivesay on June 23 2005,22:32
Have you tried running the xfree config utility thats in the testing area of the repository?
Posted by famewolf on June 23 2005,22:39
Nope but I'll be happy to if you tell me where I go..I'm VERY new to dsl. I do however notice that the chipset WD90c24 is part of the svga driver and when I look in /usr/X11R6/lib/modules I see ever module EXCEPT for the svga one...am I missing something? I can add a 'Driver "svga"' line to my config but does no good since the module it needs is missing....
Posted by tempestuous on June 25 2005,02:15
famewolf,My understanding is that the SVGA X server is distinctly different from the XFree86 X server.
(Someone correct me if I'm wrong).
The configuration file is the same for both - /etc/X11/XF86Config(-4) ... with different settings of course.
The main difference is in the "Screen" section - "Driver" line. XFree86 will specify a module name (like "neomagic" for example). SVGA specifies "svga" - it doesn't rely on a module. The error message you saw - "no screens found" is complaing that the SVGA driver (/usr/X11R6/bin/XF86_SVGA) cannot be found. It appears that the XFree86.dsl package doesn't contain XF86_SVGA.
And it seems there's no suitable module for XFree86 for you, so SVGA is the way to go. Your chip is in its compatibility list. You can get it from here - < http://www.milanosbar.com/xfree86/knoppix_svga.tgz > ... as mentioned here - < http://damnsmalllinux.org/cgi-bin....hl=svga >
The included XF86Config file is for the neomagic chipset, but should work for you with just a little tweaking.
Follow petergunn's instructions about modifying your /home/dsl/.xserverrc and /home/dsl/.xinitrc.
Regarding the .xserverrc file, I suspect the part "-bpp 16" might not be necessary depending on what's in your XF86Config.
And before you try all this, are you sure that Xfbdev won't work for you?
There are various posts here about getting Xfbdev to work with troublesome laptops like Thinkpads ... such as using the boot option "fb800x600" or "vga=normal" or "vga=771". Try these while booting to the liveCD.
Craig S
Posted by famewolf on June 25 2005,06:34
After installing the SVGA driver using the post provided and making a few tweaks I was able to get the my ibm thinkpad into X! Now a new dilemma....the pointer does not work...the config currently points to /dev/psaux and says it is a ps2 device..should I be using something different?
Posted by tempestuous on June 26 2005,01:55
Like most Linux problems, some trial and error is required.In your XF86Config, in "Section "Pointer"" -
Device "/dev/psaux"
is for an external PS/2 mouse, and also some touchpads. I suggest you first see if an external mouse works.
Then try changing this to -
Device "/dev/mouse"
This is for some touchpads. You might also have to change this as well -
Protocol "GlidePointPS/2"
If still no success, it's vaguely possible that the X server cannot assign a mouse cursor, so as an experiment - in "Section "Files"" try adding -
FontPath "usr/X11R6/lib/X11/fonts/misc/:unscaled"
Posted by tjm4fun on June 27 2005,05:50
For IBM thinkpads, and many toshiba's, you should have the mouse defined as a std ps/2 mouse. the trackpoint acts and is defined the same as any ordinary ps2 connected mous would be. One warining I will tell you: check in setup on your mouse options, it has 3 options I think, disabled, auto, both.Don;t run both. None of the X servers can handle using the internal trackpoint with an external mouse. auto will use the trackpoint if no external is plugged, or the external if it is plugged.
your config should look like this:
Protocol "IMPS2"
Device "/dev/mouse"
if your external has a scrollwheel, add these:
zaxismapping "4 5"
buttons "5"
Enjoy!
Posted by famewolf on June 27 2005,10:55
Thank you..I was able to get both the desktop and my pointer working....the config I downloaded had it defined as "MouseManPS/2" so I changed it to just PS/2 and it worked fine...now only thing left that is aggravating is I have no desktop icons..I'm not sure whether they are on a part of the screen I can't see since I'm in 640x480 or simply not there...and I tried setting both "no icons" and "full enhanced desktop" to see if they would come back. It's annoying but I can live with it..not sure where you tell it to rebuild the desktop to 640x480.