View previous topic :: View next topic |
Author |
Message |
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Fri Aug 20, 2004 3:47 pm Post subject: |
|
|
I have a 7260 ... but my previous experience with an Athlon based HP laptop made me get a tray to use when sitting in the recliner, or laying in bed with the laptop. This one accomodates the 17" displays fine:
Targus Portable LapDesk for Notebooks |
|
Back to top |
|
|
cybrjackle Apprentice
Joined: 09 Jan 2003 Posts: 248 Location: USA
|
Posted: Sun Aug 22, 2004 4:45 pm Post subject: |
|
|
Working xorg.conf (I'm in Fedora Core2, needed to get some stuff done)
But I've mixed a lot of things I've found on the net, my testing with gentoo/suse and here is a working one, with:
Touchpad mouse working
USB mouse working
1680x1050@24 Depth
Code: |
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# RgbPath is 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 (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection
Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "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:
# Option "XkbModel" "pc102"
# 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"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "LCD Panel 1600x1200"
HorizSync 31.5 - 90.0
VertRefresh 60.0 - 60.0
Option "dpms"
UseModes "Modes[0]"
EndSection
Section "Modes"
Identifier "Modes[0]"
Modeline "1680x1050" 147.14 1680 1784 1968 2256 1050 1051 1054 1087
Modeline "1600x1024" 133.96 1600 1704 1872 2144 1024 1025 1028 1059
Modeline "1600x1000" 129.95 1600 1696 1864 2128 1000 1001 1004 1035
Modeline "1400x1050" 120.46 1400 1488 1640 1880 1050 1051 1054 1086
Modeline "1280x1024" 106.97 1280 1360 1496 1712 1024 1025 1028 1059
Modeline "1280x960" 99.36 1280 1352 1488 1696 960 961 964 993
Modeline "1152x864" 80.17 1152 1216 1336 1520 864 865 868 894
Modeline "1024x768" 63.04 1024 1080 1184 1344 768 769 772 795
Modeline "800x600" 37.52 800 832 912 1024 600 601 604 621
Modeline "640x480" 23.46 640 656 720 800 480 481 484 497
Modeline "1400x1050" 120.46 1400 1488 1640 1880 1050 1051 1054 1086
Modeline "1680x1050" 147.14 1680 1784 1968 2256 1050 1051 1054 1087
Modeline "1400x1050" 120.46 1400 1488 1640 1880 1050 1051 1054 1086
Modeline "1280x1024" 106.97 1280 1360 1496 1712 1024 1025 1028 1059
Modeline "1280x960" 99.36 1280 1352 1488 1696 960 961 964 993
Modeline "1152x864" 80.17 1152 1216 1336 1520 864 865 868 894
Modeline "1024x768" 63.04 1024 1080 1184 1344 768 769 772 795
Modeline "800x600" 37.52 800 832 912 1024 600 601 604 621
Modeline "640x480" 23.46 640 656 720 800 480 481 484 497
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce FX (generic)"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1680x1050" "1400x1050" "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1680x1050" "1400x1050" "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
|
|
|
Back to top |
|
|
addicha n00b
Joined: 29 Apr 2004 Posts: 11
|
Posted: Sun Aug 22, 2004 5:35 pm Post subject: flicker issue |
|
|
I have the same notebook as xcable
I have read the brief talk about a flicker, and I've tryed everytrhing and nothing seems to get rif off a flicker about every 30 seconds on kde, usually hapens more oftern if i use the mouse(touchpad), if i dont touch it it doesnt flicker much if not at all.
Is this a problem with kde or my configuration. I hava disabled apm, loaded glx ...etc
I read something about konqueror having a flicker problem but im not sure if thats it.
Thanks |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Sun Aug 22, 2004 11:17 pm Post subject: |
|
|
As far as I know I don't have any flicker ... but I had my machine lockup constantly when trying to setup X.
Through searching this forum, I found that there are some conflicts between the latest gentoo-dev-sources and the nvidia-kernel drivers. For atleast 2.6.7-gentoo-r13 & 2.6.8-gentoo-r1, my machine locks up if I try to use the nvidia driver. The module loads fine, but freezes when X is starting. None of the suggested fixes work: making sure 8k stacks are used, not using USB 2.0 (which would be a killer for me, but I tried it to see if it'd do the trick - no dice), running /sbin/NVmakedevices.sh ... nothing worked.
So I gave up and use the non-accelerated "nv" driver with xorg, and no lock-ups. I'm not looking to do 3d yet anyway, so hopefully this issue sorts out.
My xorg.conf is less sophisticated than what cybrjackle posted, so I won't be redundant. My only difference is that I have an additional USB mouse setup for a USB trackball I like to use.
BTW, with that touchpad, does the scroll-wheel-like functionality work for you? It didn't for me. I'm not sure if I have to set something else up.
Last edited by AnimalMachine on Mon Aug 23, 2004 2:22 am; edited 1 time in total |
|
Back to top |
|
|
cybrjackle Apprentice
Joined: 09 Jan 2003 Posts: 248 Location: USA
|
Posted: Sun Aug 22, 2004 11:51 pm Post subject: |
|
|
No, the wheel doesn't work on the track, |
|
Back to top |
|
|
addicha n00b
Joined: 29 Apr 2004 Posts: 11
|
Posted: Mon Aug 23, 2004 2:46 am Post subject: Reply (flicker) |
|
|
Actually my nvidia drivers works quite well.
and with regard to the scroll thing .. it does work. Read on page two on this thread(either 2 or 3) and youll see the directions for installing the synaptics drivers.
But anyways im gonna quote "bielbyb"
Here is the driver site: http://w1.894.telia.com/~u89404340/touchpad/
make sure you have the (CONFIG_INPUT_EVDEV).
and (CONFIG_MOUSE_PS2) enebled in the kernel.
and finally use these settings from "bielbyb"
Section "InputDevice"
Driver "synaptics"
Identifier "touchpad"
Option "Device" "/dev/mouse"
Option "Protocol" "auto-dev"
Option "LeftEdge" "1900"
Option "RightEdge" "5400"
Option "TopEdge" "1900"
Option "BottomEdge" "4000"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.02"
Option "MaxSpeed" "0.18"
Option "AccelFactor" "0.0010"
Option "SHMConfig" "on"
# Option "Repeater" "/dev/ps2mouse"
EndSection
of course make sure to download the synaptics drivers, extract, go to folder
and type
make
make install
pretty simple .. got it to work the first time |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Tue Aug 24, 2004 2:37 am Post subject: Re: Reply (flicker) |
|
|
addicha wrote: | Actually my nvidia drivers works quite well. |
What kernel are you using? AFAIK, the problems only start with 2.6.7+ or so.
...
At anyrate ... It's late and I can't remember if it was mentioned on this thread or not, but I got the built-in broadcom wireless chip working okay (so far) using ndiswrappers 0.9. The trick is this: you have to disable SMP in the kernel. [edit: atleast for 2.6.8-gentoo-r1] |
|
Back to top |
|
|
addicha n00b
Joined: 29 Apr 2004 Posts: 11
|
Posted: Tue Aug 24, 2004 3:52 am Post subject: |
|
|
well for ndiswrapper 0.8 I have smp enabled and it works fine. And i have used both 2.6.7 and currently using 2.6.8 with not problems at all execpt the flicker.. I just installed gnome to see if it is with both environments, if not i quess ill conclude it's kde.
Tell me if you need me to post my kernel config file.. Pretty much the same as xcable with some minor changes. such as the two things mentioned before
well like you said nv drivers doesnt cause it and now im almost sure its something with nvidia drivers and kernel cuz it did it with gnome as well...
so fo those who are having this flicker problem.. try nv for now and let hope a better drivers gets released by nvidia |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Tue Aug 24, 2004 12:05 pm Post subject: |
|
|
addicha wrote: | well for ndiswrapper 0.8 I have smp enabled and it works fine. And i have used both 2.6.7 and currently using 2.6.8 with not problems at all execpt the flicker.. |
Sorry to be pedantic, but your saying you have ndiswrapper 0.8 working with SMP in kernels 2.6.7 & 2.6.8, right? Are you using gentoo-dev-sources as well? Don't bother with the .config file, I'll do some recompiles when I get home from work this evening.
Thanks for the help addicha. |
|
Back to top |
|
|
GreenPea n00b
Joined: 24 Jan 2003 Posts: 25 Location: Boise ID
|
Posted: Tue Aug 24, 2004 9:31 pm Post subject: |
|
|
Just for reference, I am using the ZD7000 2.6.5-gentoo-r1, SMP enabled, ndiswrapper .8 - > works like a champ especially with the wireless-config script and useing the NVidia--6106 driver with no flicker. Havent been able to get 6111 to compile yet, but at this point, who cares, no flicker. |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Wed Aug 25, 2004 2:17 am Post subject: |
|
|
Well, that was it. Ndiswrapper 0.8 will work with gentoo-dev-sources 2.8.1-gentoo-r1 with SMP enabled where ndiswrapper 0.9 would not.
Thanks again for the help. |
|
Back to top |
|
|
addicha n00b
Joined: 29 Apr 2004 Posts: 11
|
Posted: Wed Aug 25, 2004 7:28 am Post subject: |
|
|
GreenPea which specific card do you have?
AnimalMachine: your welcome, and yes i do use the gentoo-dev-sources 2.6.8. Yes i had the same problem with ndiswrapper... I knew 0.8 and up worked with smp so i tryed 0.9... and after pulling/lossing some hair i gave up and went back to 0.8.
btw, did you get the scroll thing on the touchpad to function? |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Wed Aug 25, 2004 2:59 pm Post subject: |
|
|
I didn't get around to fooling with the touchpad. I've been using my usb trackball almost exclusively, so it hasn't been a big issue for me yet.
PS: This thread suggests that the new nvidia driver problems may be fixed up in 2.6.8.1-mm4. I'm not anxious enough to get it going yet, but maybe I'll test that out tonight. |
|
Back to top |
|
|
GreenPea n00b
Joined: 24 Jan 2003 Posts: 25 Location: Boise ID
|
Posted: Wed Aug 25, 2004 5:38 pm Post subject: |
|
|
addicha wrote: | GreenPea which specific card do you have?
AnimalMachine: your welcome, and yes i do use the gentoo-dev-sources 2.6.8. Yes i had the same problem with ndiswrapper... I knew 0.8 and up worked with smp so i tryed 0.9... and after pulling/lossing some hair i gave up and went back to 0.8.
btw, did you get the scroll thing on the touchpad to function? |
Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02) I use the bcmwl5a.inf for the windows driver. |
|
Back to top |
|
|
GreenPea n00b
Joined: 24 Jan 2003 Posts: 25 Location: Boise ID
|
Posted: Wed Aug 25, 2004 10:49 pm Post subject: |
|
|
ok kernel now at 2.6.8-r2-Gentoo smp , Nvidia drivers at 6111 and ndiswrapper .10 all working well, even got the glx working |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Thu Aug 26, 2004 2:46 am Post subject: |
|
|
With 2.6.8-gentoo-r2 & SMP, I got ndiswrapper 0.10 working also, but the nvidia binary still locked up my system. Oh well. |
|
Back to top |
|
|
cybrjackle Apprentice
Joined: 09 Jan 2003 Posts: 248 Location: USA
|
Posted: Thu Aug 26, 2004 2:51 am Post subject: |
|
|
Ok, had more time.
Gentoo is back up and running, I have 1680x1050 w/ no flickering, I've been typing for the last 30 minutes or so.
Code: |
# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# 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 X.Org Foundation 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 X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# **********************************************************************
# 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)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
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
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# 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.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# 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 "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# 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" "pc102"
# 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" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
# Mouse-speed setting for PS/2 mouse.
Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# 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"
EndSection
Section "InputDevice"
Driver "synaptics"
Identifier "touchpad"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "LeftEdge" "1900"
Option "RightEdge" "5400"
Option "TopEdge" "1900"
Option "BottomEdge" "4000"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.02"
Option "MaxSpeed" "0.18"
Option "AccelFactor" "0.0010"
Option "SHMConfig" "on"
# Option "Repeater" "/dev/ps2mouse"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Monitor0"
# 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 31.5-90
# 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.
VertRefresh 60
Option "dpms"
UseModes "Modes[0]"
EndSection
Section "Modes"
Identifier "Modes[0]"
Modeline "1680x1050" 147.14 1680 1784 1968 2256 1050 1051 1054 1087
Modeline "1600x1024" 133.96 1600 1704 1872 2144 1024 1025 1028 1059
Modeline "1600x1000" 129.95 1600 1696 1864 2128 1000 1001 1004 1035
Modeline "1400x1050" 120.46 1400 1488 1640 1880 1050 1051 1054 1086
Modeline "1280x1024" 106.97 1280 1360 1496 1712 1024 1025 1028 1059
Modeline "1280x960" 99.36 1280 1352 1488 1696 960 961 964 993
Modeline "1152x864" 80.17 1152 1216 1336 1520 864 865 868 894
Modeline "1024x768" 63.04 1024 1080 1184 1344 768 769 772 795
Modeline "800x600" 37.52 800 832 912 1024 600 601 604 621
Modeline "640x480" 23.46 640 656 720 800 480 481 484 497
Modeline "1400x1050" 120.46 1400 1488 1640 1880 1050 1051 1054 1086
Modeline "1680x1050" 147.14 1680 1784 1968 2256 1050 1051 1054 1087
Modeline "1400x1050" 120.46 1400 1488 1640 1880 1050 1051 1054 1086
Modeline "1280x1024" 106.97 1280 1360 1496 1712 1024 1025 1028 1059
Modeline "1280x960" 99.36 1280 1352 1488 1696 960 961 964 993
Modeline "1152x864" 80.17 1152 1216 1336 1520 864 865 868 894
Modeline "1024x768" 63.04 1024 1080 1184 1344 768 769 772 795
Modeline "800x600" 37.52 800 832 912 1024 600 601 604 621
Modeline "640x480" 23.46 640 656 720 800 480 481 484 497
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# 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.
Driver "vga"
# 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
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "GeForce FX Go5700"
Driver "nvidia"
#VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "GeForce FX Go5700"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1680x1050" "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# 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.
Screen "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".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
|
|
|
Back to top |
|
|
addicha n00b
Joined: 29 Apr 2004 Posts: 11
|
Posted: Thu Aug 26, 2004 8:52 am Post subject: |
|
|
Thank you all, i fixed the flicker problem with the latest nvidia drivers... Well i guess i have everything working now. (well almost everything) I LOVE THIS LAPTOP!!!!
thanks again to everyone who made and are still contributing to this thread, forum, and OS in general
|
|
Back to top |
|
|
davidgp n00b
Joined: 13 Mar 2004 Posts: 16
|
Posted: Mon Aug 30, 2004 12:12 pm Post subject: |
|
|
hey!... just two things... I had the same flicker problem two weeks ago... but I forgot to put the solution here... sorry... I could solve you the problem before...
About ndiswrapper, the version 0.9 has no support for SMP, the developers did some changes and broke the SMP again, the new version, 0.10 has support for SMP processors, I'm using it right now without problem.
David GP |
|
Back to top |
|
|
slydini Tux's lil' helper
Joined: 30 Oct 2002 Posts: 129 Location: Virginia Beach, VA
|
Posted: Sun Sep 05, 2004 2:46 pm Post subject: |
|
|
Ok, guys I finally had some time to attack my problem of not being able to get x working. Thanks for posting that latest xorg.conf file cyberjackle. I used most of the settings you have in there and was at least able to startx without error. Now I just have to figure out how to change the resolution to check if I can run at the higher resolutions. The fonts look terrible at the lower resolution right now. I can't see the bottom of the screen. It seems to be stuck near the top of the desktop. Why can't I Crtl-Alt-+ into another resolution?
I had to Crtl - Alt - BS to kill the xserver but it never did recover so I had to reboot from virtual console. _________________ _______________________________________
Oh how I love Linux, especially on gentoo. |
|
Back to top |
|
|
codergeek42 Bodhisattva
Joined: 05 Apr 2004 Posts: 5142 Location: Anaheim, CA (USA)
|
Posted: Tue Sep 14, 2004 6:53 pm Post subject: |
|
|
Awesome post, xcable. I'm actually thinking of buying one of these, and I just had a question (to all that use this laptop with Gentoo): What kind of battery life do you get from these? _________________ ~~ Peter: Programmer, Mathematician, STEM & Free Software Advocate, Enlightened Agent, Transhumanist, Fedora contributor
Who am I? :: EFF & FSF |
|
Back to top |
|
|
xcable Guru
Joined: 15 Aug 2002 Posts: 424 Location: College Station, Texas
|
Posted: Tue Sep 14, 2004 7:27 pm Post subject: |
|
|
2 hours with little or use. 1 to 1.5 hours with regular use (e-mail, web browsing, word processing etc..). 1 hour with heavy use (game or compiling).
heath |
|
Back to top |
|
|
codergeek42 Bodhisattva
Joined: 05 Apr 2004 Posts: 5142 Location: Anaheim, CA (USA)
|
Posted: Tue Sep 14, 2004 7:41 pm Post subject: |
|
|
xcable wrote: | 2 hours with little or use. 1 to 1.5 hours with regular use (e-mail, web browsing, word processing etc..). 1 hour with heavy use (game or compiling).
heath | Sounds decent...thanx, xcable. _________________ ~~ Peter: Programmer, Mathematician, STEM & Free Software Advocate, Enlightened Agent, Transhumanist, Fedora contributor
Who am I? :: EFF & FSF |
|
Back to top |
|
|
Slynix n00b
Joined: 11 May 2003 Posts: 67
|
Posted: Wed Sep 15, 2004 7:55 am Post subject: |
|
|
btw does the fans on zd7000 run noisy alot? _________________ a big bear hug |
|
Back to top |
|
|
AnimalMachine Tux's lil' helper
Joined: 27 Apr 2002 Posts: 106 Location: Milwaukee, WI USA
|
Posted: Sun Sep 19, 2004 12:21 am Post subject: |
|
|
I don't find them to be noisy in light cpu usage. You hear it crank up though on compiles, and there it's quite noticable. It doesn't bother me, but it's pretty subjective. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|