Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
on install of gentoo stage1 the only problem I encountered was with gcc-3.3, 3.3 does not support the pentium-m march= flag, so I had to use pentium3 to upgrade gcc before returning to pentium-m and continuing install
only problems are that the screen does not turn off when closed. There was initial difficulty getting xorg to use 2 of the widescreen resolutions, to fix it I had to specify them manually in the monitor section of xorg.conf:
and now it works great! the values for modline were generated by 'The XFree86 Modeline Generator' (http://xtiming.sourceforge.net/cgi-bin/xtiming.pl) and i got the values to use (the max vid card timing) from the /var/log/Xorg-whatever.log I forgot where I was able to get the monitors refresh rates from, it was several hours ago.
Can you post a copy of your X configuration file? I just ordered the same machine today (but with a slower CPU and 1/2 the RAM). I haven't decided what Linux distro to put on it yet though. Thanks
Were you able to get the wireless working during installation (unnecessary, I suppose, if you used the universal cd)? Lspci output said that it recognised the internal wireless (I have the i6000--same 2200 drivers), though I couldn't get it to connect. I had to resort to using a wired connection to download the files when I tried the install. Probably a missed step on my part. I'll most likely do the stage1 install this weekend, as I got tired of messing with it last weekend. Running Kubuntu atm.
on wireless for install on gentoo 2005.0 I did modprobe ipw2200, then dhcpcd -t 10 -d eth# (was 1 on my laptop, might be 0 for you) that was that (not a protected network)
on x config file here it is: (keep updating it since slackware 8.0 came out, may have some out of date stuff)
Code:
# File generated by xf86config.
#
# Copyright (c) 1999 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.
# **********************************************************************
# **********************************************************************
# 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)
#
# 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/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
# 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"
#Option "PciOsConfig" "1"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# 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 XFree86
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbModel" "pc104"
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 "Buttons" "7"
Option "ZAxisMapping" "4 5"
# 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
# **********************************************************************
# 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 XF86Config 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 "LCD"
HorizSync 28.0-96.0
VertRefresh 50.0-75.0
Modeline "1440x900@70" 133.08 1440 1472 1976 2008 900 918 928 946
Modeline "1280x800@75" 111.50 1280 1312 1728 1760 800 815 825 841
Option "DPMS" "on"
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 xf86config:
Section "Device"
Identifier "nvidiaC"
Driver "nvidia"
#VideoRam 131072
# Insert Clocks lines here if appropriate
BusID "PCI:1:0:0"
Option "IgnoreEDID" "true"
Option "NoDCC" "true"
Option "RenderAccel" "true"
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 "ScreenC"
Device "nvidiaC"
Monitor "LCD"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1440x900@70" "1280x800@75" "1152x864" "1024x768" "800x600"
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 "ScreenC"
# 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
Once again it is an old file updated and tweaked for many years now, some stuff might be out of date, a lot of options are commented out from past experiments. but you get modes and stuff in it, and it works fine for xorg w/ enlightenment
correction: I have since changed the config file from original success story, added dpms so I could type xset dpms force off to turn off screen, I added it to acpid to get the screen to automatically turn off when I closed it, also bound it to one of the buttons ont he front (the mute button), bound the others to xmms and amixer for music controls/volume.
fyi for the multimedia keys install 'lineak' and tell it you have the inspiron 9100 keyboard, it will give you the media keys and you can program them to do what you want.
My current wish-list for things yet to configure on the laptop, if anyone figures one of these out please let me know:
1) framebuffer at boot does not go to the resolution I specified in the kernel config for vesafb-tng (1440x900) and instead lowers down to 1024x768, I imagine it is the same reason why I had to specify the mode in the xorg.conf file, but I am not sure how to specify it.
2) I want a better way to control turning off the screen when the lid is closed, currently it only works in X and only when I reload the acpid script after X starts.
I'm with you on curious as to how to get the screen to turn off when closed. I have a Inspiron 5100 and am a complete newbie at Linux, but I'm slowly peicing things together..
I do nto knwo what distro you use, so you will have to figure out the exact install yourself, but there is a program called acpid, acpi-daemon, I used that, when I close the screen it registers an acpi event, acpid will read it and run the program you specify in the config file. I edited the config file to run 'xset dpms force off' that turns off dpms enabled screens. but first you need to modify the xorg.conf file to enable dpms on your monitor, this section:
acpid config is interesting, but I think it is different from distro to distro.
here is the file I modified:
/etc/acpid/default.sh (gentoo)
Code:
#!/bin/sh
# Default acpi script that takes an entry for all actions
#I added this function here:
DoLid()
{
touch /etc/screenstatus #File to keep track of the screen's status, opening and closing the lid both generate the same event
SCREEN=`cat /etc/screenstatus` #Read the screenstatus file into a variable
if [ ! $SCREEN ] || [ "$SCREEN" -ne 1 ]; then #See if screen has a status, and if so see if it is not 1
echo "1" > /etc/screenstatus #There was no status or it was not 1, so we are turning off the screen, set status to 1 in the file
xset dpms force off #turn off screen
logger "Lid closed, screen turned off" #inform the logger
else #Screen was deturmined to be off
echo "0" > /etc/screenstatus #Set screen status to 0 (on)
xset dpms force on #turn on screen
logger "Lid opened, screen turned on" #Inform the logger
fi #Finish
}
#End added function
set $*
group=${1/\/*/}
action=${1/*\//}
case "$group" in button)
case "$action" in
power) /sbin/init 0
;;
lid) DoLid #If 'lid' event is recieved run DoLid function <---Added this as well
;;
*) logger "ACPI action $action is not defined"
;;
esac
;;
*)
logger "ACPI group $group / action $action is not defined"
;;
esac
inspiron 9300
17" wuxga lcd monitor
geforce 6800 256mb video card
60 gig HD 7200 rpm
cd/rw-dvdrom combo drive
1.2gigs of ram
basically what i would like to know is how can i figure out what model my lcd is and then also what the vert and horiz refresh are. Then another thing i would like to figure out is how to get my monitor to display 1920x1200 in any distro i can configure to get that resolution .. obviously i cant use the nvidia drivers for this so .. any help would be great .. keep in mind that i do have a WUXGA lcd .. which is different from the wxga .. anyways thanx in advance .. :]
ive already googled this as im not that much of a newbie .. and could not find anything on it ..accept for this which didnt work .. http://fluffi.info/inspiron9300/single/
there seems to be various different models .. just was wondering if they all have the same specs... as my highest res is 1920x1200 unlike your 1440x900 as you can see.. so anyone else have any ideas ..
seems to be alot of ppl with the wxga model .. so that is why i asked .. anyways thanx for the reply though ..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.