Linux-Hardware Digest #370, Volume #14 Mon, 19 Feb 01 15:13:08 EST
Contents:
replacing startx with startx -- +xinerama (Chris Nelson)
CRC Error (Bastian Ballmann)
Replicate/Clone RH6.2 Linux (Steven Conway)
Re: My VooDoo isn't working! (Henrik Carlqvist)
Re: Should I abandon SCSI? ("Ron Reaugh")
Re: Turtle Beach Pinnacle Pro- need help configuring on mandrake 7.0 ("Al Stevens")
ECC memory not needed? (Ed Ohsone)
Re: ASUS vs ABit motherboards (Lee Webb)
Re: RH 7.0 & NE2000 clone ("lobotomy")
Re: ISA PCMCIA Adaptor (Swapbox) Problem ("D Knisely")
----------------------------------------------------------------------------
From: Chris Nelson <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux.redhat,comp.os.linux.admin,comp.os.linux.misc,comp.os.linux.setup
Subject: replacing startx with startx -- +xinerama
Date: Mon, 19 Feb 2001 18:01:32 GMT
Hello: This weekend I finally got a working config file for using 2
monitors on a g400 max.
My problem however is that right now my etc/inittab file has me going to
only run level 3. if I change this value to 5, the systems takes me to a
graphical logon..but with only one monitor. My guess is that the system
is still strying to run startx as opposed to startx -- +xinerama. Where
do I need to make a change so this can be automoated? Any advice is
appreciated...
P.S. Any idea how I can have the system default to KDE as opposed to
gnome? Thought I would throw this in as well
Chris
Enclosed ar emy XF86Config filke and my /etc/inittab files
*********MY inittab file*************
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have
networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
# Things to run in every runlevel.
ud::once:/sbin/update
# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5
# xdm is now a separate service
x:5:respawn:/etc/X11/prefdm -nodaemon
**********My XF86Config File*****************
# File generated by xf86config.
#
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
Section "Files"
RgbPath
"/usr/X11R6/lib/X11/rgb"
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/"
EndSection
# **********************************************************************
# Server flags section
# **********************************************************************
Section "ServerFlags"
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"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbCompat" ""
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier
"Mouse1"
Driver
"mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "817-1"
HorizSync 30-130
VertRefresh 50-180
EndSection
Section "Monitor"
Identifier "815"
HorizSync 30-130
VertRefresh 50-180
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 "maxxx"
Driver "mga"
# unsupported card
#VideoRam 32777
VideoRam 32768
# Insert Clocks lines here if appropriate
EndSection
Section "Device"
Identifier "G400_1"
Driver "mga"
BusID
"PCI:1:0:0"
Screen
0
EndSection
Section "Device"
Identifier "G400_2"
Driver "mga"
BusID
"PCI:1:0:0"
Screen
1
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 15"
Device "maxxx"
Monitor "817-1"
DefaultDepth 16
Subsection "Display"
Depth 8
# Modes "640x480" "800x600" "1024x768" "1280x1024"
Modes
"1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
# Modes "640x480" "800x600" "1024x768" "1280x1024"
Modes
"1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
# Modes "640x480" "800x600" "1024x768" "1280x1024"
Modes
"1280x1024"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Identifier "Screen 1"
Device "G400_1"
Monitor "817-1"
DefaultDepth 16
Subsection "Display"
Depth 8
Modes "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Identifier "Screen 2"
Device "G400_2"
Monitor "815"
DefaultDepth 16
Subsection "Display"
Depth 8
Modes "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024"
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"
Screen "Screen 1" LeftOf "Screen 2" Screen "Screen 2"
# 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
------------------------------
From: Bastian Ballmann <[EMAIL PROTECTED]>
Subject: CRC Error
Date: Mon, 19 Feb 2001 19:12:57 +0100
Reply-To: [EMAIL PROTECTED]
Does anybody know what a CRC Error is?
When I start my linux system lilo failed after uncompressing linux with
this crc error...
Heeeeeelp!!!!
------------------------------
From: Steven Conway <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.misc,comp.os.linux.help,comp.os.linux.networking,comp.os.linux.setup
Subject: Replicate/Clone RH6.2 Linux
Date: Mon, 19 Feb 2001 13:18:54 -0500
I have painstakingly set up old OS/2 Warp (urgh) workstation with
RedHat 6.2.
1) I have correctly configured all of the devices by downloading
patches, recompiling, etc.
2) Updated and changed the kernel.
3) Updated the numerous packages with the latest patches (up2date)
RPMS & .tar.gz).
4) Installed, and tested numerous other third party software packages.
5) tested, tweeked and finally have the computer working exactly how I
want it to.
I now need to replicate/clone this workstation to 25 IDENTICAL
workstations that are all connected over a Private internal network.
I was told to look at RedHats Kickstart but I am not sure if this
approach is the best way to do this as it assumes you are installing
off of a CD and not off of an existing system. Am I correct in this
assumption? Can I even do what I am trying to do.
Steven Conway
------------------------------
From: Henrik Carlqvist <[EMAIL PROTECTED]>
Subject: Re: My VooDoo isn't working!
Date: Sun, 18 Feb 2001 20:11:04 +0100
Constantin Bergemann wrote:
> When I start, for example, Quake 3, I get the message "no hardware
> acceleration found".
> I've installed mesa and the glide libs. Can anyone help me please?
You might find some hints in the readme. Do you have a hardware
accelerated Mesa or do you have software rendering only? Did you try
quake3 +set r_gldriver libMesaVoodooGL.so.3.2
?
regards Henrik
--
spammer strikeback:
root@localhost [EMAIL PROTECTED] [EMAIL PROTECTED]
------------------------------
From: "Ron Reaugh" <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi
Subject: Re: Should I abandon SCSI?
Date: Mon, 19 Feb 2001 18:44:54 GMT
Eric P. McCoy wrote in message <[EMAIL PROTECTED]>...
>"Ron Reaugh" <[EMAIL PROTECTED]> writes:
>
>> >For my personal situation, I am guaranteed to encounter a
>> >non-recoverable data error about every year, for each disk. With two
>> >disks in a RAID0 array, I'd get twice the number of errors in the same
>> >amount of time.
>
>> Well, the rate per terabyte read would still be the same. So twice as
fast
>> gets one to an error sooner but that's an advantage and not a
disadvantage.
>> Such errors can appear for both SCSI or EIDE single drives or RAID 0.
Now
>> what are the undetected and unrecoverable error rates for a RAID 1 array
or
>> RAID 5 array?
>
>For RAID1, presumably half as much.
No, there is no reason to suspect that.
> For RAID5, actually, wouldn't it
>be constant no matter the number of disks in the array?
Maybe.
>> >I have _already_ suffered data errors on _both_ disks in this
>> >computer, and one disk is less than a month old. While it seems like
>> >I've gotten some flakey hardware, I think it should still serve to
>> >show that the likelihood of failure is _not_ small.
>
>> No, it just shows that you should get a professional to configure your
>> machines next time.
>
>When you have some basis for insulting my technical abilities, I'd
>like to hear it.
You've been keying it into this thread for several messages now as several
have noted.
>In the meantime, I've been doing this sort of thing for the past 12
>yeears, and have never had serious problems until now. I've gotten
>more data corruption in the past six months than I have in the
>previous 11.5 years.
OK, so what does that tell you?
> That doesn't suggest anything about flakey
>hardware to you, but instead suggests incompetence on my part?
Yep, your assumption that the problem is hardware does so suggest.
>[...]
>> Every book an RAID says that striping is called RAID 0...get a clue.
>
>Let me see if I have our positions right:
The issue has been well covered by other posters in this thread already and
now you're going on a troll....sorry charlie.
------------------------------
From: "Al Stevens" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake
Subject: Re: Turtle Beach Pinnacle Pro- need help configuring on mandrake 7.0
Date: Mon, 19 Feb 2001 13:48:46 -0000
>Over the last year I have tried to get Linux running on my system a number
>of times. This last time I've worked through almost all my problems except
>for getting my turtle beach pinnacle pro working. It's not listed in
>Lothar. In sndconfig its listed with another TBS card ( I think the Fiji).
>It tells me to download the pinnacle dev kit from tbs. You then have to
>take a piece of code from the kit and do some things that looks like your
>are trying to compile your own driver. At any rate, I haven't been able to
>get it to work. I was hoping someone else may have had some experience with
>this.
I have the same problem. The sndconfig program thinks the Pinnacle Pro has
the same IRQ, etc., setup as the Fiji, which, apparently, it does not. There
seems to be some confusion between the Pinnacle and the Multisound Pinnacle,
which might be Fiji-compatible. I have not yet found a combination of
settings that work for the Pinnacle.
This problem has prevented me from porting my sound and midi processing from
Win98 to Linux. Replacing the sound board is not an acceptable option and I
shouldn't have to. The Pinnacle Pro was expensive and does the job better
than any sound card I've used. Turtle Beach does not provide UNIX or Linux
drivers, but they do provide an SDK and specs for those wishing to develop
software for the hardware.
------------------------------
From: Ed Ohsone <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.ibm.pc.hardware.systems
Subject: ECC memory not needed?
Date: 19 Feb 2001 19:16:15 GMT
In the past I read many posts by apparently knowledgeable people
who stated ecc memories were strongly recommended.
But recently I can find no desktop PCs (not servers) or chipsets which are
designed for non-server systems and ecc-enabled.
(The systems designed for desktop PC, non-server, are characterized by
AGP graphic socket.)
Good examples are systems based on the popular Intel 815E chipset.
It seems to me ecc memory is no longer needed for non-server
platforms or the manifacturers believe so.
Observing the current trend, I have the following questions:
(1) Are Ecc memories no longer needed due to the
improved stability of recent drams?
If so, why are all servers still equipped with ecc memories?
If there is still possibility of errors, which is significant
to servers, then it can be significant to non-server systems
performing mission critical jobs.
Then why there is no or very few motherboard having both AGP
and ecc capabiity?
(2) Do you know of any laptop equipped with ecc memory?
(3) Have you heard of any memory errors occurring in a system
with non-ecc memory?
(4) Are there ecc-capable DDR available?
(5) Do you know any pre-built systems or mother boards which have the
following capabilities:
- ecc supported
- having AGP graphic socket
The last question is for my next system.
Now I am using an old PC which is based on intel motherboard AL400
which is ecc-capable.
I want rock solid reliability for the next system, although it is not
going to be used as server.
The requirements I have in mind are:
- ecc (you may argue and make me drop this item)
- AGP graphic socket
- 133 MHz or higher font side bus speed
- compatible with linux
I rule out rambas memory for undisclosed reason.
Do you have any recommendation?
I can build from parts if needed.
Thanks in advance.
==========
Ed
------------------------------
From: [EMAIL PROTECTED] (Lee Webb)
Subject: Re: ASUS vs ABit motherboards
Date: 19 Feb 2001 19:21:20 GMT
Reply-To: [EMAIL PROTECTED]
On Mon, 19 Feb 2001 10:51:08 GMT, Kenneth R�rvik wrote:
>[EMAIL PROTECTED] (hac) wrote in <[EMAIL PROTECTED]>:
>
>>My 1GHz Tbird ASUS A7V133 works fine. My previous Abit BX6.2 worked
>>fine. But I think that ASUS keeps on top of BIOS updates a bit better
>>than Abit. If features and price match up, I prefer ASUS. I would
>>buy Abit again, though, if there were some feature that met my needs
>>better. For example, the A7V133 has no ISA slots. I don't need any,
>>and it looks like you don't, but someone else may.
>
>Abit seems to have a slight advantage over Abit in terms of performance
^^^^ ^^^^
>too.
>
;-)
I think you meant to say "Abit seems to have a slight advantage over Asus in
terms of performance too."
(Which it does, but it *is* slight - hence my choice of the Asus A7V.)
Lee.
------------------------------
From: "lobotomy" <[EMAIL PROTECTED]>
Subject: Re: RH 7.0 & NE2000 clone
Date: Mon, 19 Feb 2001 19:39:34 GMT
The support certainly hasn't been removed from the kernel, and in fact
the driver module is almost certainly there. So, if it isn't
autodetecting it, just do it manually -- modprobe ne (it can autoprobe if
you don't know the settings).
In article <[EMAIL PROTECTED]>,
"Phil Galbiati" <[EMAIL PROTECTED]> wrote:
> Greetings
>
> I have an old 486 with a Realtek 8019 ISA PnP NIC (NE2000 clone) on
> which I am trying to install RH 7.0, but it asks for a driver disk, and
> the driver image on the cd does not have an NE2000 driver. This card
> worked fine under RH 4.2 & 5.2 -- they didn't actually remove support
> for a working card, did they?
>
> Anyway, where do I get a driver image so I can install the OS with this
> card?
>
> Thanx
>
> --Phil Galbiati
> P.S. Please cc me if you post a reply.
>
--
PC Chips actually goes by many names. PCChips = Ability = Alton = Amptron =
Aristo = Asia Gate = Asiatech = Assa = Atrend = Elpina = Eurone = Fugu =
Fugutech = Hi Sing = Houston = Hsing Tech = H Tech = Matsonic = Minstaple =
PCWare = Pine = Protac = QDI = Warpspeed
------------------------------
From: "D Knisely" <[EMAIL PROTECTED]>
Subject: Re: ISA PCMCIA Adaptor (Swapbox) Problem
Date: Mon, 19 Feb 2001 14:00:26 -0600
Thanks for the reply. I had actually fixed the problem partially in the
mean time by changing the memory lines. I had added "include memory
0xa0000-0x0fffff", but I didn't know what to do about the upper memory.
This was enough to make the PCMCIA adaptor work.
My fix only worked partially, and I was flying blind. When I re-installed
an NE2000 network adaptor, the system would freeze right after PCMCIA
starts.
I will try your settings and play around with it a little while longer.
Thanks again.
D. Knisely
>
> I had the same problem on an old i486 w/ 16MB ram. It worked after
> modifying /etc/pcmcia/config.opts, the last memory-range should be
> tuned.
>
> # remove original lines
> #include memory 0xc0000-0xfffff
> #include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
> # added lines
> include memory 0x0b0000-0x0fffff
> include memory 0x100000-0x7fffffff
>
> Trygve.
------------------------------
** 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
******************************
