Linux-Hardware Digest #684, Volume #14 Wed, 25 Apr 01 02:13:05 EDT
Contents:
Re: Flat panel (TFT/LCD) with Linux anyone? (Michael Meissner)
High availability webserver ("Bastiaan Schaap")
Re: Networking -- switches vs hubs ?? (Michael Meissner)
----------------------------------------------------------------------------
Subject: Re: Flat panel (TFT/LCD) with Linux anyone?
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 25 Apr 2001 01:44:52 -0400
38.161.118.161 [[EMAIL PROTECTED]] writes:
> Hi, Does anyone have any success with using a flat panel monitor with Linux?
> If so, I would appreciate if you could post the details.
>
> Iam currently running Linux Mandrake 7.2, but would be moving to 8.0 soon. I
> have a Matrox Millennium G400 (Dual head) AGP card. Iam thinking of buying a
> flat panel monitor, but want to make sure I can use it under Linux.
As I posted previously, I have a ViewSonic VP181 monitor (which has both analog
and digital inputs). I tried in vain to get a G400 Max dual-head with digitial
flat panel addition to work with my system (dual processor 500Mhz P-III's, with
an ASUS P2B-DS motherboard), but I could never get any output to the flat
panel, even when only the DFP cable was plugged in. I also tried a PCI G200
with the digital extension with no luck. Note, the G400 digital flat panel
support will take up an extra slot (typically PCI) for dual headed G400's (the
OEM G400 without a second head doesn't take another slot). I don't think the
G450 has a digital output.
In theory, the Matrox framebuffer support has a DFP option that enables the
digital mode. Matrox also has a binary only driver for Xfree86 4.02 that knows
how to active the digital and TV-out modes.
I bought an ATI Radeon VE that has both flat panel and analog outputs, only to
discover that the XFree86 Radeon support is only for the other Radeon's, and
that the VE wasn't yet supported. After buying the VE, I looked at the XFree86
code, and discovered the flat panel support for the Radeon All in Wonder is
commented out. I was able to get the Radeon VE to support to the digital
monitor by using the VESA frame buffer and VESA XFree86 4.02 drivers, but I
noticed there were artifacts in scrolling the screen in netscape & other
applications (if you redraw the screen, everything would be ok). If you use
it, the DGA option (used by VMware for full screen mode) is not supported by
the VESA driver. Also, fonts in netscape didn't look as good, they were more
spindly. So currently I have gone back to using the G400 in analog mode.
For what its worth, here is the XF86Config-4 file I used for the Radeon VE:
# File generated by xf86config, hacked by [EMAIL PROTECTED]
# 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 "freetype"
# 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).
#
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
FontPath "unix/:7100"
# 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" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
# Option "Protocol" "IMPS/2"
# Option "Device" "/dev/mouse"
# Option "ZAxisMapping" "4 5"
# 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
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "ViewSonic VP181"
VendorName "ViewSonic"
ModelName "VP181"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30 - 95
# 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 - 75
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
Identifier "Standard Vesa"
VendorName "ATI"
BoardName "Radeon VE"
Driver "vesa"
# BusID "PCI:1:0:0"
# Screen 1
# Chipset "chipset"
# Ramdac "ramdac-type"
# DacSpeed speed-8 speed-16 speed-24 speed-32
# Clocks clock...
# ClockChip "clockchip-type"
# VideoRam 32768
# BiosBase baseaddress
# MemBase baseaddress
# IOBase baseaddress
# ChipID id
# ChipRev rev
# TextClockFreq freq
# Option "ShadowFB" "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 "Screen vga"
Device "Standard Vesa"
Monitor "ViewSonic VP181"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024"
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024"
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
Subsection "Display"
Depth 32
Modes "1280x1024
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 vga"
# 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
# HISTORY
# $Log: XF86Config-4-vesa,v $
# Revision 1.3 2001/04/18 23:58:16 meissner
# Wheel mouse broke, go back to straight 3 button mouse.
#
# Revision 1.2 2001/04/12 17:02:46 meissner
# Cleanup
#
# Revision 1.1 2001/04/11 22:30:49 meissner
# Initial version.
#
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: "Bastiaan Schaap" <[EMAIL PROTECTED]>
Subject: High availability webserver
Date: Wed, 25 Apr 2001 07:56:51 +0200
Hi all,
I need to build some websites, that will use large quantities of PHP's and
JSP's. Offcourse I can't estimate now what kind of site-traffic I'll receive
once they're online. In order to make a flexible and robust solution I'm
thinking about creating a cluster that would act as one webserver. If my
traffic increases dramatically, I can always add nodes to my cluster. I had
an offer to receive 30 'old' PII systems, I only have to pick 'em up... I
intend to use the Apache webserver offcourse...
- Is this a wise idea?
- Does anyone know of better alternatives?
- Does anyone have experience with this?
- If clustering is a good option, should I go for Beowulf or TurboLinux, or
does anyone know a better alternative?
- I know bandwidth is a very big issue too, is it easy to upgrade to higher
bandwith with this solution?
I know.... a lot of questions, but in my opinion this is the best place to
ask...
TIA,
Bastiaan Schaap
________________________________
make love not war... or get married and do both.
------------------------------
Subject: Re: Networking -- switches vs hubs ??
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 25 Apr 2001 01:57:46 -0400
[EMAIL PROTECTED] (Eric P. McCoy) writes:
> The short answer is that hubs share bandwidth, whereas switches have
> dedicated bandwidth for each port. On a hub, the sum bandwidth of all
> ports cannot exceed the port speed - meaning that if one computer is
> sending out 8Mb/s, the other can only send at 2Mb/s (on a 10BT hub).
> On a switch, each port can operate at maximum speed simultaneously,
> assuming the backplane is good enough to handle it. So on a 10BT
> switch, all computers can be pushing out 10Mb/s at once.
Actually for most cards, on a 10Mb/s network, switches can put the card into
full duplex mode, giving you double the bandwidth (the rating is in terms of
the normal half duplex mode where a network card can be receiving or sending,
but not both at the same time).
In theory, switches can also prevent a host from enabling promiscuous mode on
the ethernet card and reading all packets that come over the wire (with a
switch, they would only see the packets destined for their particular ethernet
adapter, or the broadcast packets that everybody sees).
Another place where you need switches is when you have more hubs than you can
connect together and stay within specs. For example, the spec for 100Mbs
networks is 2 hubs hooked together with a maximum distance between any 2
computers being limited to some value (100 feet?). At one point, I needed to
have 3 hubs in my house due to having computers spread out, and so I got a 5
port switch to connect the 3 hubs together (each hub plugs into the switch).
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
