Linux-Hardware Digest #612, Volume #14           Thu, 12 Apr 01 13:13:09 EDT

Contents:
  Re: HPT370 Driver Request (Emyr James)
  Re: Help wanted. Linux problems using AMD K6-2 (Magnus)
  BIOS Upgrades (Was: Via + Maxtor + kernel 2.4.3 = crash?) (Harold Stevens 
US.972.952.3293)
  Re: Gigabyte GA-7ZX5-1 Motherboard w/AC97 Sound (Peter Christy)
  Re: Support for LCD Monitors? (Michael Meissner)
  Re: linux driver for Canon S400 (Andrey Vlassov)
  Re: Epson Stylus 777, problems printing (Andrey Vlassov)
  Re: Best RAID controller for Linux (Joshua Baker-LePain)
  sis900 on silver book PC (Allen Ahoffman)
  Re: linux driver for Canon S400 (Andrey Vlassov)

----------------------------------------------------------------------------

From: Emyr James <[EMAIL PROTECTED]>
Subject: Re: HPT370 Driver Request
Date: Thu, 12 Apr 2001 17:20:14 +0100

Am I understanding this right ? My Raid 0 installation of win2k is actually
doing it's thang in software not hardware ? Does that mean that the ABIT KT7
with onboard raid controller is no such thing cause it's all done in software
anyway ?
What a fucking con!!!!
(pardon my french...)

Juergen Sauer wrote:

> Emyr James <[EMAIL PROTECTED]> schrieb
> am Wed, 11 Apr 2001 15:05:41 +0100 in comp.os.linux.hardware:
>
> > Please can some nice driver guru sort out raid support for an ABIT KT7
> > RAID mobo (very popular board) ?
> > Win2K handles it fine, surely it must be possible to get Linux to do it
> > properly as well...or are there some complications ?
> > Is there support for this in the pipeline ?
> > Any news appreciated.
>
> Kernel 2.4.x has it in, called there HPT366, runns fine.
> No Raid functions avaible, because the 'HTP370' does Raid only as
> shitty Software in Windump ...
> mfG
>         Jojo
>
> --
> J�rgen Sauer - AutomatiX GmbH, +49-4209-4699, [EMAIL PROTECTED]
> http://www.automatix.de to Mail me: remove: -not-for-spawm-


------------------------------

From: [EMAIL PROTECTED] (Magnus)
Crossposted-To: comp.os.linux.help
Subject: Re: Help wanted. Linux problems using AMD K6-2
Date: 12 Apr 2001 16:29:45 GMT
Reply-To: [EMAIL PROTECTED]

In article <[EMAIL PROTECTED]>, P Ashton wrote:
> I am have having numerous problems using linux (Redhat 7.0) on my k6-2
> based machine. Are there any known problems with K6-2s and what are the
> fixes?

No answer to the problem, but I just want to let you know that I run RedHat 7
on my k6-2 without any problems at all. 

-- 
Mvh Magnus Lundin
       
www.algonet.se/~elp

------------------------------

From: [EMAIL PROTECTED] (Harold Stevens US.972.952.3293)
Crossposted-To: 
comp.os.linux.questions,comp.os.linux.development.system,comp.os.linux.misc
Subject: BIOS Upgrades (Was: Via + Maxtor + kernel 2.4.3 = crash?)
Date: Thu, 12 Apr 2001 16:40:20 GMT

In <9b4io8$96n$[EMAIL PROTECTED]>, Mark Hahn:

[Snip...]

>gross.  flash an updated bios or turn off "optimum" settings in bios.

On this topic, I need pointers on BIOS upgrades, especially where to find
them, as I haven't had any luck at all with Google to date.

Just added a 32 MB stick for a total of 64 MB as required by yast2 ("old"
yast needs less apparently) for a SuSE 7.1 install I've started.

Rebooting resulted in a kernel panic which I almost expected on these old
BIOS versions (Award 4.51PG i430VX) from reading threads I found. Figured
redoing LILO with the append="mem=64M" thingy was the ticket but a kernel
panic still resulted. OK, threads mentioned this may be a BIOS limit with
such old ones, so upgrade the BIOS. Simple. Not. After mergers and such I
could hardly find working vendor sites, and email totally ignored.

This is a point of dimishing returns for me, so any tips welcomed. Even a
"you can't get there from here" if the BIOS is too old; I'll just save us
all some time, and go back to yast instead of yast2, if it's moot.

-- 

Regards, Weird (Harold Stevens) * IMPORTANT EMAIL INFO FOLLOWS *
Pardon the bogus email domain (dseg etc.) in place for spambots.
Really it's (wyrd) at raytheon, dotted with com. DO NOT SPAM IT.
Standard Disclaimer: These are my opinions not Raytheon Company.


------------------------------

From: Peter Christy <[EMAIL PROTECTED]>
Subject: Re: Gigabyte GA-7ZX5-1 Motherboard w/AC97 Sound
Date: Thu, 12 Apr 2001 17:40:52 +0100
Reply-To: [EMAIL PROTECTED]

JNJ wrote:

> Am running the above with RedHat 7, but cannot get the sound to work for
> the
> life of me.  Anyone else worked with these and been able to get the sound
> running?  Any other known issues between these motherboards and RedHat 7?
> 
> James
> [EMAIL PROTECTED]
> 
> 
> 

I've got the GA-7ZM, and you need the Alsa drivers to get it to work! I'm 
using the 0.9.0beta3 drivers which seem to give the best results. I had no 
success at all with the kernel drivers, though some people have managed to 
get them working.

There is quite a good "howto" on the linuxnewbie site (www.linuxnewbie.org) 
about getting AC97 sound working.

-- 
Pete
[EMAIL PROTECTED]

------------------------------

Crossposted-To: comp.os.linux.misc,alt.uu.comp.os.linux.questions,uk.comp.os.linux
Subject: Re: Support for LCD Monitors?
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 12 Apr 2001 12:47:14 -0400

Michael Meissner <[EMAIL PROTECTED]> writes:

> The Radeon VE supports DVI flat panels with the vesa framebuffer support, but
> there is no X support at the present time.  Given ATI claims to work with the
> Xfree86 developers, it is probably just a matter on months until it is
> supported.  Until then, constructing an X server that uses the framebuffer
> might work.

Following up on my own post, I did get the Radeon VE that I bought (before
finding out that there was no X support) to work using the VESA framebuffer and
X support on my ViewSonic VP181 using the digital input.  For the framebuffer,
I use the lilo options:

        append  = "video=vesa:mtrr"
        vga     = 0x31b

For a 32-bit 1280x1024 framebuffer console.  My 4.02 XF86Config-4 file looks
like (note, netscape does not like 24-bit displays, and VESA doesn't support
32-bit displays, so I set the default to be 16-bit):

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

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

#       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     50-100

EndSection


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

# Any number of graphics device sections may be present

Section "Device"
        Identifier      "Standard Vesa"
        VendorName      "Unknown"
        BoardName       "Unknown"
        Driver          "vesa"
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    16

        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


-- 
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: Andrey Vlassov <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: linux driver for Canon S400
Date: Thu, 12 Apr 2001 17:05:08 GMT

Hi Francois,

check next webpage. I do not have Canon and can not help more. Your
printer is not on the list. But there you will find Canon S450 and it's
driver can work for you. 

http://gimp-print.sourceforge.net/p_Supported_Printers.php3

Andrey

francois reygagne wrote:
> 
> I recently bought a Canon S400 and I'm looking for a linux driver.
> I appreciate if someone knows the path.
> 
> Bye.
> 
> Fran�ois REYGAGNE. Software Architect.
> opt[e]way S.A., 2881 route des Cr�tes, BP308
> 06906 Sophia Antipolis Cedex, FRANCE
> t�l: +33 (0)4 92 95 27 01    http://www.opteway.com

--

------------------------------

From: Andrey Vlassov <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Epson Stylus 777, problems printing
Date: Thu, 12 Apr 2001 17:02:08 GMT

Hi Stephen,

just check this project (URL bellow). I have Epson 860 and with this
piece of software getting a very good result. Your printer on the list
supported but require testing.

http://gimp-print.sourceforge.net/p_Supported_Printers.php3

Andrey

Stephen Coursen wrote:
> 
> I have a major problem with my Epson 777.  First off, I know the hardware
> involved works fine, because the printer behaves properly when I boot the
> machine into Win2000.  However, under Linux (kernel 2.2.19/smp, redhat 6.2),
> the parallel port is probed and the printer is detected.  But, I can't print
> anything, whether through lpd or direct to /dev/lp0.
> 
> I get no errors from these printing items, I just don't get any output on
> the printer.  Any ideas?
> 
> TIA,
> Steve Coursen

--

------------------------------

From: Joshua Baker-LePain <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.raid
Subject: Re: Best RAID controller for Linux
Date: 12 Apr 2001 17:02:21 GMT

Hubba Bubba <[EMAIL PROTECTED]> wrote:
>       There is a *significant* difference in having hardware XOR
> onboard vs. not having it at all. Raid logic is software based, but
> there are several hardware components involved in "skinning" the cat
> so to say. It is generally considered that if you do not have hardware
> XOR onboard, that you are not utilizing what what would be considered
> a good hardware solution.

First, please stop top quoting.  It makes it very hard to follow the flow of
the conversation.  Second, could you give examples of hardware raid
(IDE or SCSI) solutions which do have hardware XOR, and exactly what you
mean by that?

>       Given that these little lunchboxes only do Raid 0 and 1, you
> get what you pay for.

Sorry, but you are completely wrong here.  Our group has a Syneraid-800
(aka Brownie Raid from Axus Microsystems).  The controller in this unit
(which is the same controller used in Zero-D's G-Force series)
is based on the Intel i960RN (64-bit) processor, which is also used in
SCSI RAID products, e.g. the Adaptec 3200S and 3400S and the Mylex
AcceleRAID 352.  The system supports RAID levels 0, 1, 3, 5, and 0+1, as
well as hot swap, hot spare, automatic drive rebuilds, and 2 redundant,
hot-swappable power supplies.  The channel to the host is U2W SCSI.

Our unit is configured with 8 80GB 5400RPM Maxtor drives and 128MB of cache
RAM.  It is setup as a RAID 5 with no hot spare (560GB useable space) and
having a stripe size of 128 blocks (per disk).  We consistently get 25-30MB/s
reading *and* writing to the system.  It cost ~$US6000.  That's what I
call price/performance.


> On Mon, 09 Apr 2001 22:47:18 GMT,
> [EMAIL PROTECTED] () wrote:

>>On Mon, 09 Apr 2001 21:30:48 GMT, Hubba Bubba <[EMAIL PROTECTED]> wrote:
>>>     Both of the below referenced external raid boxes have
>>>*software* raid logic built in, not hardware (no XOR onboard). 
>>
>>
>>So?  *ALL* raid controllers do it via software.  If the CPU isn't burdened w/
>>handling the raid software then it can be considered a hardware solution.
>>
>>>
>>>
>>>
>>>On 1 Mar 2001 14:03:14 GMT, Joshua Baker-LePain
>>><[EMAIL PROTECTED]> wrote:
>>>
>>>>[EMAIL PROTECTED] wrote:
>>>>
>>>>> Anyone know of a hardware IDE raid solution that *works*?
>>>>
>>>>Look at the products from Zero-D and Syneraid -- external IDE RAID
>>>>enclosures that talk SCSI to the host.
>>>


-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

------------------------------

From: Allen Ahoffman <[EMAIL PROTECTED]>
Subject: sis900 on silver book PC
Date: 12 Apr 2001 09:27:01 -0400



anyone know how to make the sis900 network onbaord work in a silver book
PC?


-- 
Announce Communications Inc.
5004 W. Lanham Dr.
Hyattsville, MD 20784
301-731-5786
[EMAIL PROTECTED]

------------------------------

From: Andrey Vlassov <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: linux driver for Canon S400
Date: Thu, 12 Apr 2001 17:09:26 GMT

Hi Francois,

it is again me. Check next webpage which claims that your printer will
work.

http://www.linuxprinting.org/show_printer.cgi?recnum=602258

Andrey

francois reygagne wrote:
> 
> I recently bought a Canon S400 and I'm looking for a linux driver.
> I appreciate if someone knows the path.
> 
> Bye.
> 
> Fran�ois REYGAGNE. Software Architect.
> opt[e]way S.A., 2881 route des Cr�tes, BP308
> 06906 Sophia Antipolis Cedex, FRANCE
> t�l: +33 (0)4 92 95 27 01    http://www.opteway.com

--

------------------------------


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

Reply via email to