LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-02-2003, 11:28 AM   #1
Shibby
LQ Newbie
 
Registered: Sep 2003
Posts: 27

Rep: Reputation: 15
Total linux Newbie


hello all.

I am a total to linux i chose slackware cause of it small size to fit on my 1gb hard drive fitting in to a celeron 466mhz with 384mb of ram and a pny pci geforce 4 fx 4200. i have windows xp on another drive but i do not want to touch it. this pc is a system i use to putput movies to my tv in the lounge. anyway,

i installed it they was fairly sort of easy once the floopy boot and root disks stop to stop working.

i ran the xf86 setups configs alot of times and i got linux booting up from lilo on a floopy.

when i type "startx" i get

Quote:
USing authority file /root/.Xauthority
writing autority file /root/.Xauthority

XFree86 version 4.3.0
Release date : 27 feburay 2003
X Protocol Version 11, Revision 0, release 6.6
Build operating system : Linux 2.4.20 i686 [ELF]
bulid date: 01 match 2003

module load present
makers : I keep this out.
(==) log file : "/var/log/XFree86.0.log", time tue sep 2 16:46:12 2003
(==)using config file : "/root/XF86Config"
(WW)VGA: no matching device section for instance (busid) pci:1:0:0 found
(EE) vga(0):Virtual height (0) is to small for the hardware (min1)
(EE) screen(s) found, but none have a usable configuration

Fater server error
no screens dound

when reporting a problem related to a server crash please send the full output, not just the last messages.
this can be found in the log file "/car/log/XFree86.0.log".
please report problems to xfree86@xfree86.org

XIO: fatel IO error 104(connection resrt by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
this is what is says.

how can i solve this so i can get in to the KDE.

if i need to open stuff edit stuff please tell me as i have no idea about commands as i am still sorta learning.

also pico does not work.
 
Old 09-02-2003, 11:41 AM   #2
JROCK1980
Member
 
Registered: Aug 2003
Distribution: FreeBSD
Posts: 490

Rep: Reputation: 30
Talking RE: Linux Newbie

That error happens because you probably did not setup X right. Go to /etc/X11 and look for your config file for X server. Post that up so we can see what you have setup. Try using emacs instead.
 
Old 09-02-2003, 12:05 PM   #3
Moominpeikko
LQ Newbie
 
Registered: Aug 2003
Distribution: Slackware 9.0
Posts: 11

Rep: Reputation: 0
Looks to me like you chose the wrong monitor options and/or selected the wrong gfx card. Try running xf86config again and select other settigns, there are 2 pages of video cards so if your card isn't on the first page just press enter and you'll have another list to choose from.
 
Old 09-02-2003, 01:12 PM   #4
Shibby
LQ Newbie
 
Registered: Sep 2003
Posts: 27

Original Poster
Rep: Reputation: 15
Unhappy

thanks i keep changing the config files and nothing.

also what is the file name for the x server config? all i got is XF86Config XF86Config-vesa XF86Config-fbdev

and the folders

fs
mwm
rstart
xdm
xkb
xsm
app-defaults
ibproxy
proxymngr
twm
xinit
xserver
 
Old 09-02-2003, 01:54 PM   #5
grim1234
Member
 
Registered: Aug 2003
Location: UK
Distribution: Slackware 10.2, Fluxbox.
Posts: 64

Rep: Reputation: 15
the XF86Config file is the file that is read when you startx. I assume you ran the xf86config command to set up your config file? the -vesa and -fbdev files are ready made 'generic' setup files that you can use. I took the monitor / card settings from the vesa file to get a working x system (that I will get around to customising for my graphics card eventually).

hope this helps,

 
Old 09-02-2003, 04:09 PM   #6
Shibby
LQ Newbie
 
Registered: Sep 2003
Posts: 27

Original Poster
Rep: Reputation: 15
hmmm i am still having bad luck i am still getting the messages i even booted to Knoppix to see what it got as my monitor and for my gfx card i got 1 which is vga.

shell i post my config file if so where about are they and i will try to put them to floopy and then carry them on my windows pc to show u.
 
Old 09-02-2003, 04:47 PM   #7
grim1234
Member
 
Registered: Aug 2003
Location: UK
Distribution: Slackware 10.2, Fluxbox.
Posts: 64

Rep: Reputation: 15
how about - try running xf86config and selecting option 0 (vesa comp) for your graphics card. If this fails try vga (generic) - unless this what knoppix selected?. Do you know which graphics chipset you have (nvidea?)? Monitor specs are also useful. It may be worth trying redhat linux (as it configured my system very well) - shame it runs slowly compared to slack.
 
Old 09-02-2003, 05:02 PM   #8
h1tman
Member
 
Registered: Jul 2003
Distribution: Slackware 11
Posts: 439

Rep: Reputation: 30
try this for now

# 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.
# **********************************************************************

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me.

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy!
# -- volkerdi@slackware.com
#

# **********************************************************************
# 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 font modules
Load "type1"
Load "freetype"
Load "speedo"

# This loads the GLX module
Load "glx"

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/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
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><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" "pc104"
Option "XkbLayout" "gb"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

# 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 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 31.5 - 50.0

# 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 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# 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 "VESA Framebuffer"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
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
 
Old 09-02-2003, 05:57 PM   #9
Shibby
LQ Newbie
 
Registered: Sep 2003
Posts: 27

Original Poster
Rep: Reputation: 15
hitman what am i to do with this?

if it a file what file type should it be and where about to go.

also since i am so new to linux what are the commands to do so.

many thanks.

also grim i tryed both vga vesa and nvida and still no luck.
and as u can see my card is a geforce 4 fx 5200 so it s nvidia.
and when i ran knoppix i looked at it monitor settings and it gave me this.

Herizonal sync freq khz
28-96

vertical
50-76

640x480

vertical 60

colour 8

sorry for a few mistakes as i am 15 and have bad spelling and grammer. also sorry about the monitor details i wrote them down quickly.

ah now i just found my monitor model and did a search on google and i got a pdf

sorry it did not look right in here so i will add a screenshot

Click here for screen shot

Last edited by Shibby; 09-02-2003 at 06:17 PM.
 
Old 09-02-2003, 06:16 PM   #10
zsejk
Member
 
Registered: Apr 2003
Distribution: Slackware
Posts: 345
Blog Entries: 5

Rep: Reputation: 30
Hitman just gave us his entire XF86Config file, which is in the following directory:

/etc/X11

To open it and edit it so that it looks like the one above (I'm assuming hitman changed all values to match your specs), type the following at the command prompt:

pico XF86Config

The PICO editor will then open the file for you, and you can scroll down and edit using regular word processing keys. When your done, the bottom of your screen will have the command to save the file and exit (I believe CTRL + O is for saving, but check to make sure).

Note that to edit this XF86Config file you need to be root. To become root, type the following at the prompt:

su

And then enter your password.

After you're done editing, make sure you type "exit" at the prompt to stop being root. Now you can start X again by typing "startx".

Good luck!



-zsejk


edit:

Note that when you run "xf86config" (by typing that at the command prompt as root), you will be basically changing the XF86Config file as well, only by other means. So I suggest you try that command one more time, keeping in mind all the info you just looked up on your monitor etc. The most important thing is to not set the refresh rates at higher than their maximum. It's always better to be on the conservative side with these settings. So, run "xf86config" again, see if that works. If not, edit your XF86Config file, and see if that works. If not, come back here and post both your error message again and the part from your XF86Config file that relates to your monitor (so just the Monitor Section basically).

Last edited by zsejk; 09-02-2003 at 06:19 PM.
 
Old 09-02-2003, 06:25 PM   #11
Shibby
LQ Newbie
 
Registered: Sep 2003
Posts: 27

Original Poster
Rep: Reputation: 15
thanks i will do it once hitman has said that it is edited for my system.

but one prob pico does not work but VI does

to exit and save is it Control-Q Control-C ESC Z Z

but to exit it is

Control-Q Control-C ESC : q ! ENTER
 
Old 09-02-2003, 06:31 PM   #12
zsejk
Member
 
Registered: Apr 2003
Distribution: Slackware
Posts: 345
Blog Entries: 5

Rep: Reputation: 30
Yeah, I know. I just have this inexplicable hatred of all things vi.



I usually use emacs, but if you're good with vi, I say go with vi. I was just giving you the simplest editor (i.e. PICO), since you are a newbie (but I guess not *that* much of a newbie ).

-zsejk


edit:

It looks like h1tman's values are within your monitor's specs (those in your screenshot anyway). So how about you go ahead and change the bits in the Monitor Section according to h1tman's values, and report back here afterwards.

Last edited by zsejk; 09-02-2003 at 06:34 PM.
 
Old 09-02-2003, 06:32 PM   #13
LinFreak!
Member
 
Registered: Jul 2003
Location: England
Distribution: slack9.1
Posts: 209

Rep: Reputation: 30
try typing "mc" and use F4 to edit a file. Be careful to double check for mistakes though!
 
Old 09-02-2003, 06:34 PM   #14
Shibby
LQ Newbie
 
Registered: Sep 2003
Posts: 27

Original Poster
Rep: Reputation: 15
thanks.

just tryed the xf86config again with my monitor settings and it still gives an error
 
Old 09-02-2003, 06:53 PM   #15
zsejk
Member
 
Registered: Apr 2003
Distribution: Slackware
Posts: 345
Blog Entries: 5

Rep: Reputation: 30
When you're in that program and it asks you if you want to see the videocard database, did you type "yes"? If so, did you scroll through the entire thing to pick out the one that matches your actual card exactly? What kind of card, for that matter, do you have? Could you perhaps post the output of "lspci"?

-zsejk
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Total Linux Programming Newbie binarybob0001 Programming 4 04-01-2005 03:12 PM
Total newbie interested in linux Kushan Linux - Newbie 17 08-14-2004 09:22 PM
Total linux newbie I don't know anything and need help hanleychan Linux - Newbie 16 09-29-2003 09:03 PM
Total newbie to Linux needs help. Please jarget Linux - Software 3 08-24-2003 07:31 PM
Total Linux Newbie Ghengis_Khan LinuxQuestions.org Member Intro 2 05-19-2003 01:48 PM


All times are GMT -5. The time now is 08:30 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration