Hi guys,
after I've updated to slack current with kde 3.5.2 and custom build a 2.4.32 kernel, also enbled dri on my radeon 9000 mobility card

(Dell Inspiron 8200 laptop-I couldn't believe at first but compared the screen to my other laptop the image quality is better,windows are somwhat more shinier,crisp )

my mouse scroller does not work.

I know about the ZAxisMapping option that used to sort this out nicely,but not now.

In addition I was trying to get my synaptics touchpad to work together with my usb external targus mice,but I can get working just one of these.

I've googled a thread explaining how this has been done in exactly the same touchpad and a usb mouse, but what I tried according to that thread did not do much for my system (suspect it could be for an older version of some of the programs xorg,kde... not sure though).

I'll post my xorg.conf as well shortly.

Thanks.

Section "ServerLayout"

# The Identifier line must be present
# 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.
# 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".
Identifier "Simple Layout"
Screen 0 "aticonfig Screen 0" 0 0
Screen "aticonfig Screen 1" Above "aticonfig Screen 0"
InputDevice "n52_mouse" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

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.
# 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)
#
#
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/TTF"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/CID"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/local"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/local/share/fonts"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
Load "glx"
# This loads the DRI module
Load "dri"
EndSection

Section "InputDevice"

# 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"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# 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:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# 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 Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "inspiron"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"

# Identifier and driver
# the following line.
#?? Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# 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"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
Option "Resolution" "5256"
# Baudrate and SampleRate are only for some Logitech mice. In
Option "ZAxisMapping" "6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection

Section "InputDevice"
Identifier "n52_mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mouse0"
Option "Buttons" "3"
Option "ZAxisMapping" "4 5"
EndSection

Section "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 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.
Identifier "dell"
HorizSync 60.0 - 60.0
VertRefresh 60.0 - 60.0
EndSection

Section "Monitor"
Identifier "aticonfig Monitor 0"
EndSection

Section "Monitor"
Identifier "aticonfig Monitor 1"
EndSection

Section "Device"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection

Section "Device"

# unsupported card
Identifier "rad"
Driver "fglrx"
VideoRam 65536
Option "XVideo" "On"
Option "DevicePresence" "On"
# Insert Clocks lines here if appropriate
EndSection

Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

Section "Device"
Identifier "ATI Graphics Adapter 1"
Driver "fglrx"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Screen"

# Subsection "Display"
# Depth 16
# Modes "1280x1024" "1024x768" "800x600" "640x480"
# ViewPort 0 0
# EndSubsection
Identifier "Screen 1"
Device "rad"
Monitor "dell"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig Screen 0"
Device "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig Screen 1"
Device "ATI Graphics Adapter 1"
Monitor "aticonfig Monitor 1"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection





EDIT: I've also tried setting/changing the ZAxisMapping values to 4 5 or 6 7 for the 2 mouse identfiers but scroller still works just a button..

Checkout my homepage about my Synaptics TouchPad and I use a usb mouse with it.

My xorg.conf is also available on the page

Link is in my sig.

Any questions, just ask

How small is the internet world sometimes

I think that the thread I was talking about was yours, (the mice identifier may even suggest that

I think that I've been on your page as well, browsing again now.

Thanks.

I've tried it according to your laptop website,installed as in INSTALL file in the synaptics driver package ,

but still no result(no synaptics touchpad,nor usb scroller is working)

I can manage to get the touchpad trhough mouseconfig but this way I have to choose either touchpad/usb mouse to work..

Here's my new xorg.conf :


Section "ServerLayout"

# The Identifier line must be present
# 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.
# 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".
Identifier "Simple Layout"
Screen 0 "aticonfig Screen 0" 0 0
Screen "aticonfig Screen 1" Above "aticonfig Screen 0"
InputDevice "n52_mouse" "CorePointer"
InputDevice "Mouse1" "AlwaysCore"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

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.
# 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)
#
#
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/TTF"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/CID"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/local"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/local/share/fonts"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
Load "glx"
# This loads the DRI module
Load "dri"
Load "synaptics"
EndSection

Section "InputDevice"

# 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"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# 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:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# 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 Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "inspiron"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"

# Identifier and driver
# the following line.
#?? Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# 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"
Identifier "Mouse1"
#Section "InputDevice"
# Identifier "Synaptics Mouse"
Driver "synaptics"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "LeftEdge" "1700"
Option "RightEdge" "5300"
Option "TopEdge" "1700"
Option "BottomEdge" "4200"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.09"
Option "MaxSpeed" "0.18"
Option "AccelFactor" "0.0015"
Option "SHMConfig" "on"
# Option "Repeater" "/dev/ps2mouse"
EndSection




# Driver "mouse"
# Option "Protocol" "PS/2"
# Option "Device" "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
# Option "Resolution" "5256"
# Baudrate and SampleRate are only for some Logitech mice. In
# Option "ZAxisMapping" "6 7"
# Emulate3Buttons is an option for 2-button mice
#EndSection

Section "InputDevice"
Identifier "n52_mouse"
Driver "mouse"

Option "Device" "/dev/mouse"
# Option "Device" "/dev/input/mouse0"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
Option "Protocol" "Auto"
EndSection

Section "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 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.
Identifier "dell"
HorizSync 60.0 - 60.0
VertRefresh 60.0 - 60.0
EndSection

Section "Monitor"
Identifier "aticonfig Monitor 0"
EndSection

Section "Monitor"
Identifier "aticonfig Monitor 1"
EndSection

Section "Device"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection

Section "Device"

# unsupported card
Identifier "rad"
Driver "fglrx"
VideoRam 65536
Option "XVideo" "On"
Option "DevicePresence" "On"
# Insert Clocks lines here if appropriate
EndSection

Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

Section "Device"
Identifier "ATI Graphics Adapter 1"
Driver "fglrx"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Screen"

# Subsection "Display"
# Depth 16
# Modes "1280x1024" "1024x768" "800x600" "640x480"
# ViewPort 0 0
# EndSubsection
Identifier "Screen 1"
Device "rad"
Monitor "dell"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig Screen 0"
Device "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig Screen 1"
Device "ATI Graphics Adapter 1"
Monitor "aticonfig Monitor 1"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

I think I know where the problem is and here is some /var/log/xorg.0.log.whatever file:

I am also not sure if I have udev in my kernel, where to llok for it when I run make menuconfig?

I'll be also looking for evdev..

off-topic: I'll be doing a new custom kernel build on 2.4.32 as my current one gives what is known as kernel panic after a couple of hours of work (caps&num lock flash continously(happened before in console mode as well),but I can't see the error msg when I'm in X, So would you give me some guidance on how to avoid these kernel panics-I mean in my previous builds of that same kernel everything was OK?
Could this be because my current kernel is not so "monolithic" as they say - a lot of stuff is compiled as modules..
Basically should I try to compile as much stuff as possible IN the kernel and avoid compiling options as modules?

Thank You very much!




**) Option "Protocol" "Auto"
(**) n52_mouse: Device: "/dev/mouse"
(**) n52_mouse: Protocol: "Auto"
(**) Option "CorePointer"
(**) n52_mouse: Core Pointer
(**) Option "Buttons" "5"
(==) n52_mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) n52_mouse: ZAxisMapping: buttons 4 and 5
(**) n52_mouse: Buttons: 9
(II) Synaptics touchpad driver version 0.14.4 (1404)
Mouse1 no synaptics event device found (checked 42 nodes)
Mouse1 The evdev kernel module seems to be missing
(**) Option "Device" "/dev/psaux"
(**) Option "SHMConfig" "on"
(**) Option "LeftEdge" "1700"
(**) Option "RightEdge" "5300"
(**) Option "TopEdge" "1700"
(**) Option "BottomEdge" "4200"
(**) Option "FingerLow" "25"
(**) Option "FingerHigh" "30"
(**) Option "MaxTapTime" "180"
(**) Option "MaxTapMove" "220"
(**) Option "VertScrollDelta" "100"
Query no Synaptics: 000064
(EE) Mouse1 no synaptics touchpad detected and no repeater device
(EE) Mouse1 Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Mouse1"
(II) UnloadModule: "synaptics"
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "inspiron"
(**) Keyboard1: XkbModel: "inspiron"
(**) Option "XkbLayout" "gb"
(**) Keyboard1: XkbLayout: "gb"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "n52_mouse" (type: MOUSE)
(**) Option "Device" "/dev/mouse"
(II) n52_mouse: GuessProtocol: setting mouse protocol to "PS/2"
(II) n52_mouse: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list!
(WW) Open ACPI failed (/proc/acpi/event) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) n52_mouse: ps2EnableDataReporting: succeeded
(WW) Open ACPI failed (/proc/acpi/event) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) n52_mouse: ps2EnableDataReporting: succeeded

Regarding ZAxisMapping, you should use Protocol "IMPS/2" instead of "auto" or "PS2".
And for Synaptics (quoted from http://web.telia.com/%7Eu89404340/to...e-shooting.txt ):

I've just tried that IMPS/2 and it worked Thanks very much

It just didn't make sense to me to put IMPS/2 as this is not a ps2,but usb mouse

I'm trying the other psaux bit.

tried with /dev/input/mice as suggested..
still no result though (Touchpad & Pointing Stick still not working)

Scroller works at 100% though

Cool.

Sorry I didn't respond quicker, was herding the kiddies.

BTW, the laptop site is a little old (Up to kernel 2.6.17-rc3, and running 'current' from a mirror I keep on a local server. But 99% of the info still works.

The 'imps2' deal is a well documented option to get the usb scroll working, but the install file, and even more, troubleshooting.txt in the synaptics file was invaluable to me.

The major thing I would recommend is to forgo the 2.4 kernel series, and compile a 2.6 kernel. You will be amazed....

GREAT Yikes!!

I was trying to convince myself into getting my hands onto the 2.6 kernel, so thank you very much!!

Now is there any way to have both 2.4 & 2.6 on my machine(being able to choose between both not just between different build of either version)?

I mean how to set it up to use different System.map files

AND

is there any way to be able to keep up the penguin bootsplash logo ( I Need this just for the high console resolution - 1280x1024 though my laptop is running X at 1600x1200)

The only way I have found to do this is using the 2.4.32 Slackware kernel from ftp.slackware.com/ in kernel source folder for 2.4

I couldn't find the same ( I mean 2.6 kernel source provided by Slackware)

Thanks.

Thanks a million!

Compiled 2.6.16.16 kernel, booted in high resolution SPOT ON!!

glxgears reports 200fps though - It should be at least 2000FPS as per previous kernels

and no glxinfo does say no direct rendering....

tried aticonfig to set it as a single head (think that's the option that should be chosen as it's a lapppy with no external screen)

Firewall is not completely started though-it says to check for a module that I think should exist(will check it now)

Unbelievably sound is working without executing any alsa thingies.

The odd skype 1.2.18 still giving me headaches though..

The touchpad/pointing stick is working as well, though it moves very slowly,any suggestion how/from where to fix that?


again Thanks A Million!!!!

In KDE, look in "Settings>Peripherals" for the mouse accel/speed.
For DRI, log in as root after a fresh boot, see what it says then. If DRI=Yes, then append to end of xorg.conf:at the very end.

I will flip over to linux right now to try that as I've managed to fix the firewall (at least it says passed though with some unknown errors however no internet access for some reason provided that the network card is working,also been given information about the dhcp assigning the correct address and then this ip securedd by the firewall..

after 2-3 reboots the sound card does not work for some reason will look further into a new alsa or may be just alsa-drivers..

I was looking for the synaptics bit where you are suggesting but couldn't find anything synaptics-wise, yes I can change these setttings but they apply to the usb mouse as well.. I was sorta looking for something like alps control panel in win

(Mouse issue)Nothing like that, and it will change both. You can change accel/speed in xorg.conf for synaptics alone(Back it up first....)