Gentoo linux on a 4760 - Page 2

I keep getting a "no screens found" error, not the same as the "No Screens Found (x)". I have been Googling, but have not found the solution yet. Do you have any insights?

When I ran XF86Config is selected:
--H refresh as 31.5-57.0
--V refresh as 50-100
--No graphics card from the db
--64meg of memory

Thanks again
David

You ran xf86config or Xconfig right?

Gah stupid submit/edit button - what I mean to add to that was can you post a copy of your XF86Config-4 file here so I can have a better idea

I think the error may be due to the version I am running thru Gentoo, but here is my config.

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/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/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"

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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules""xfree86"
Option "XkbModel""pc101"
Option "XkbLayout""us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier"Mouse1"
Driver"mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

# 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 "my_lcd"

# 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 - 57.0

# HorizSync30-64 # multisync
# HorizSync31.5, 35.2 # multiple fixed sync frequencies
# HorizSync15-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 50-100

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"

# VideoRam256

# Clocks25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "my_gcard"
Driver "vga"
# unsupported card
#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 "my_gcard"
Monitor "my_lcd"
DefaultDepth 16

Subsection "Display"
Depth 8
Modes "1440x900" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1440x900" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1440x900" "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

Almost got it, added a new device to the config. Now X works, just have to figure out how to get K to start. Here is what i added:

Section "Device"
Identifier "ATI Radeon Mobility 9000"
Driver "vesa"
VendorName "ATI Radeon Mobility 9000"
BoardName "ATI Radeon Mobility 9000"
VideoRam 65536
EndSection

edit your .xinitrc file and put startkde in it.

Yeah I already did that. When I first started K the Kpersonalizer hung and I had to kill K. Then next time I ran startx K went thru the initialization and the nothing but a blue screen. No menubars or windows. I can't get anything in my logs.

I mean I don't see anything in my logs, not that I can't get anything in to the log files.

Got it! Just had to restart a few services, not sure exactly why but hey it works. Thanks for all you time!

David

My suggestion - dont run KDE - its a memory hungry little bastard - and not particularly speedy. I recommend WindowMaker

Ok another WM user - time for a shameless plug - check out

WMxmms
wmdf
wmacpiload
wmthrottle

on dockapps.org - I wrote em. They may very well suck but at least I wrote em

i personally like fluxbox, with 3ddesktop on occasion for virtual desktop switching, and gkrellm and a couple dockapps in the slit.

i suppose the real issue is how comfortable you are with straying away from the traditional Windows interface. for a really radical, lightweight departure, you could try ratpoison.

i put kde on the computer in my room that all my friends use. even though it has a lot of overhead, it's the 'prettiest' one out there. that way they won't be scared off when they see that it's not windows.

I like blackbox. Especially now that IronHead and others ported it into a windows version and all my styles still work.

i like fluxbox because it's extremely light - it's minimalist without sacrificing usability. while ratpoison is probably one of the lightest ones out there, it gets to be a little annoying sometimes - when there's not even a titlebar or window border, it makes things a little difficult. everything in flux is run from a right click menu, so there are no icons/menus sitting around taking up space - the menu is just a text file in my home directory that can be modified with any text editor, which fluxbox will automatically sync to on the fly. the slit on the side has all sorts of displays and system readouts with gkrellm and stuff, but is set to auto hide so i can pull it up when i need to see something, but is out of my way otherwise. the only thing that's always on my desktop is a tiny little bar on the bottom with the time and the number (or name) of the virtual desktop i'm on. i can maximize the desktop space usage - windows are pretty much completely fullscreen without hiding or getting hidden by anything.

and on that note, that's the other thing i like about fluxbox - the virtual desktop system. while virtual desktops are nothing new, fluxbox makes it extremely easy by flipping through desktops with the mouse wheel. i usually do lots of things at once - and while the default of four is usually enough, sometimes i end up opening up to 10 or more virtual desktops. and at that point, i can click the middle mouse button, have a 3d display of what's on all my virtual desktops with 3ddesktop, scroll to the one i want, and click to flip right to it.

and if i don't want so many desktops and need to consolidate, i can tab things together by category - for example, all internet-related windows end up grouped to each other and accessed through tabs.

it's like blackbox with updated and new features. there's not much that's extremely unique, but it's a good combination of things that i like.

Yup WindowMaker does all that - and has a groovy cool tool that allows changing of stuff on the fly.

I however do not want to get into a my window manager is better than your window manager

naturally, everyone will think that theirs is best, or else they probably would not have chosen to use it in the first place.