Linux-Hardware Digest #726, Volume #10 Sat, 10 Jul 99 16:13:32 EDT
Contents:
Re: Windows easy to install? BULLSHIT! (Brian Hartman)
Re: Cant get Creative Ensoniq AudioPCI to work (Tim Moore)
Re: How Close is the Mobo temp to the CPU temp???? (John Hagen)
Re: Fibre channel (Tim Moore)
Help with sound driver for Aztech card (AZT1023 PNP) ("B. Christopher Felaco")
3c589d pcmcia installation (Thierry Nivon)
Re: Will My Wheel Mouse Work w/ Linux? ([EMAIL PROTECTED])
Re: asus TNT v3400 problems (Thomas Kochak)
Re: Cant get Creative Ensoniq AudioPCI to work (Thomas Kochak)
Re: Tekram DC-390F SCSI Card ? (Michael Meissner)
----------------------------------------------------------------------------
From: Brian Hartman <[EMAIL PROTECTED]>
Subject: Re: Windows easy to install? BULLSHIT!
Date: Sat, 10 Jul 1999 14:35:11 -0400
JLKirkham wrote:
> >doesn't mean that Linux is a good system for a beginner to upgrade to (or even
> start out with)
>
> I'd have to disagree - much better to start out "hands on" and understand
> what's going on rather than watch the pretty pictures and never be able to fix
> it when it breaks (and you know it's gonna break).
>
The problem is, people don't buy computers to become computer-savvy. They buy
computers to get their work done. You shouldn't have to be "hands-on" to get your
work done.
>
> >As it is, too much of the hardware driver problems are self-service issues for
> it to be worth it for newbies.
>
> I'll agree to a point - a total newbie like my mom (get-a-cluebie) wouldn't
> know what to do with a driver problem. They'd be better off having friends or
> family who does know what they're doing or buying a system ready to go. But
> that's not unique to Linux, I'd say the same thing about win95/98 and probably
> any other OS or system.
>
I'd agree to a certain extent. A complete newbie might have a problem finding the
drivers, but once found, they would have an easier time with Windows, on the
average.
>
> >But for someone who has no interest in computers as a hobby, it's much more
> important to just fire up the PC, get what
> >you need to do done, and get out. In many cases, that's easier to do with
> Windows than Linux.
>
> ???sounds like people who have more dollars than sense, if you ask me, in which
> case they get what they deserve. You're describing my mother, who comes and
> sits in front of my computer after I've opened a program, does what she needs
> to do, and then I format it and save it for her. She has no business owning a
> computer, and she knows it.
>
Don't take this personally, but that's exactly the problem with many in the Linux
community: The attitude, "If you don't want to learn about computers, you
shouldn't use them" is rampant. It's not a realistic argument. Computers need to
become easier to use. People shouldn't have to be forced to learn them. No OS is
completely idiot-proof, but Windows comes closer to the goal than Linux. One
example: You can't, to my knowledge, simply run an install program for an app and
expect it to work in Linux. You also need to compile it for your machine, tweak
config files, run make or "make install" etc. (And if something goes wrong during
compilation or make, what's a newbie to do?) These processes need to be
simplified. Plug and play for Linux also needs to be improved. Too few devices
are recognized on bootup in the standard kernel configuration. These kinds of
changes will make Linux easier to use and justify it as a viable OS for end users.
>
> >Instant gratification is the entire point
>
> As I said, more dollars than sense... people with this attitude more often than
> not get what they deserve.
>
See above.
>
> >As I've said before, computers are tools to make our lives easier.
>
> So are curling irons, sewing machines, and timing lights. And if you don't
> know how to work them and aren't willing to learn, you have no business buying
> one.
>
None of the items mentioned above are nearly as complex as a Linux system. And
none are as indispensable to business and home users alike as a computer. Think
about what you're saying: If the learning curve stays where it is for Linux, and
businesses adopt it, they will need to invest in all kinds of training and
technical services people just for what should be simple tasks ("Hey, I'm not able
to print" or "Hey, my CD-ROM drive isn't working"). What you're asking people to
do is to harken back to the days of DOS. If those in the Linux community continue
to have an elitist attitude about what kind of person should or should not be
allowed to use a computer, M$ will only increase its lead in the marketplace.
Let's not shoot ourselves in the foot with exclusionary rhetoric.
>
> >I don't think it's a monopoly in a conventional sense.
>
> Janet Reno may disagree with you...
>
She may think it's a monopoly. But it's *not* a monopoly in a *conventional*
sense. If it was, we'd all be running Windows. As it is, you're free to buy
whatever OS you want. Hell, even OEM's aren't *forced* to install Windows.
M$ simply makes them sign contracts for per-processor use if they want to install
Windows on any of their machines. This is obviously anti-competitive, but it's
not monopolistic. The reason OEMs feel like they're over a barrel in these
situations is because Windows is so popular they feel like they have to install it
to be competitive. No one's forcing it on them, though, so it's not strictly
speaking monopolistic.
>
> >No one is forced at gunpoint to use Windows
>
> No, but how many people's jobs depend on it?
>
That's irrelevant to whether or not it's a monopoly. M$ makes deals with
companies to make their products more attractive than competitors (which is why
WordPerfect was forced out of many corporations). M$ uses its predominance as an
OS manufacturer to spur most of these deals. (The company I work for was
approached with the deal, "If you choose Office as your productivity suite, we'll
give you a good price on 95." (which my company was upgrading to.)) The bottom
line is that Windows isn't the only OS out there, and MS isn't the only software
producer. Their position as market leader (which IMHO IBM and the OS/2 marketing
fiasco is mostly to blame for) simply gives them an edge.
>
> Jana
> Wherever you go, there you are.
------------------------------
Date: Sat, 10 Jul 1999 11:59:04 -0700
From: Tim Moore <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.help,comp.os.linux.misc,comp.os.linux.questions,comp.os.linux.setup
Subject: Re: Cant get Creative Ensoniq AudioPCI to work
> #PCI devices found: Bus 0, device 10, function 0:
> # Multimedia audio controller: Ensoniq Unknown device (rev 6).
> # Vendor id=1274. Device id=1371. Slow devsel. IRQ 11. Master
> #Capable. Latency=64. Min Gnt=12.Max Lat=128. I/O at 0xe800.
I'm running 2.0.37. Here's my card which is also based on the 1371
chip. I believe you have one of the newer creative/ensoniq cards.
Check on the chips for ES1370 or ES1371:
Bus 0, device 9, function 0:
Multimedia audio controller: Ensoniq AudioPCI (rev 0).
Slow devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=12.Max
Lat=128.
I/O at 0xd000.
> #alias sound sb
> #options -k sb io=0x220 irq=11 dma=1
Here's a problem. The Ensoniq is not a SB or SB 100% compat. According
to your .config entries below you are running inline sound code not
modules, so these entries in /etc/conf.modules don't do anything.
> i get this on boot up :
> #Sound initialization started
> #Sound initialization complete
> not once did I get something in between :(
Nothing missing.
Jul 10 09:51:48 asus kernel: Sound initialization started
Jul 10 09:51:48 asus kernel: Sound initialization complete
> maybe im missing something in the sound configuration part of compilation?
>
> CONFIG_SOUND=y
> CONFIG_SB=y
> CONFIG_AUDIO=y
> CONFIG_YM3812=y
> SBC_BASE=220
> SBC_IRQ=11
> SBC_DMA=1
> SB_DMA2=-1
> SB_MPU_BASE=388
> SB_MPU_IRQ=-1
> DSP_BUFFSIZE=65536
Too much. Try getting rid of everything but this:
CONFIG_SOUND=y
CONFIG_AUDIO=y
--
direct replies substitute timothymoore for user name
"Everything is permitted. Nothing is forbidden."
WS Burroughs.
------------------------------
Date: Sat, 10 Jul 1999 11:29:51 +0000
From: John Hagen <[EMAIL PROTECTED]>
Subject: Re: How Close is the Mobo temp to the CPU temp????
Jae Il \"Joker\" Ko wrote:
>
> Hey all,
> I own an Asus P2B and as much as i love it, it doesn't really have a
> temperature sensor that tells me what it's exact temp is. But i can read
> the mobo temp. Is there an usual ratio of the temperatures of the mobo to
> the CPU??? Better yet is there a program that can tell me the CPU temp on
> than what's in the BIOS?? Thanks. Also, I've heard of rumours of a
> softmenu for the P2B. IS thiS TRUE???? is there a new BIOS for the P2B
> that's softmenu???? That would be great! Thanks again.
>
> --
> -Jae Il "Joker" Ko
> .
> .
> .
Hi,
Please don't cross-post so much (if at all).
Read the following if you have the time to check this NG after checking all the
others you posted to:
I have a recent P5A and know that you should be able to see the temps w/ the
program on the disk that came w/ the mobo (you do still have it, don't you?).
This requires a Windoze boot to use the Wincentric s/w on the CD.
OTW, reboot and check the 'Power Management' paramaters in the BIOS setup.
PPS. Hey, is this Motherboard Monitor a Linux program? If not, it's off-topic.
:-)
PPPS. WTF is a softmenu???
HTH,
--
john hagen ~ [EMAIL PROTECTED]
=============================
------------------------------
Date: Sat, 10 Jul 1999 12:14:42 -0700
From: Tim Moore <[EMAIL PROTECTED]>
Subject: Re: Fibre channel
> While trying to get the best deal on a new hard drive, I had the
> mistake of buying a very nice fibre channel one (From an auction site).
> To be honest, I thought the term "fibre channel" was some marketing
> gimmick and that it would work with the normal EIDE protocol. I soon
> discovered that I was wrong. This seems to be a very good protocol that
> linux supports. I am only missing the controller card. If anyone know
> really anything about this protocol, it's use in linux, as well as a
> place to get a <100$ controller, I would be very grateful. Thanks.
FC controllers use SCSI protocol across copper or glass but are
currently at the bleeding edge and very expensive. Qlogic and others
make chipsets. 2.2.x did not have support last time I checked.
Advantages: 100MB/s theoritical, ~50-60 devices on a single loop
(practical).
--
direct replies substitute timothymoore for user name
"Everything is permitted. Nothing is forbidden."
WS Burroughs.
------------------------------
From: "B. Christopher Felaco" <[EMAIL PROTECTED]>
Subject: Help with sound driver for Aztech card (AZT1023 PNP)
Date: Sat, 10 Jul 1999 20:39:38 +0000
I'm running kernel 2.2.5-15 (RedHat 6.0) and I can't get my sound card working.
I've finally got the isapnp setup right, using isapnp-1.18 with patches a&b.
I'm using the exact same configuration as on Windows which works.
I've tried sndconfig, and it set up the sgalaxy driver, but seemed to get
confused by the disables IDE device on the card, and was configuring the wrong
ports and interrupts in isapnp.conf.
I've tried each of these drivers configured in my conf.modules:
alias midi opl3
options opl3 io=0x388
options sgalaxy io=0x534 irq=5 dma=1 dma2=3 sgbase=0x220
options sb io=0x220 irq=5 dma=1
options cs4232 io=0x534 irq=5 dma=1 dma2=3
The opl3 driver loads, but I don't have anything to test it with. I'm mostly
interested in playback and possibly recording.
With sgalaxy I get these messages and the driver doesn't load:
Jul 10 15:42:16 felaco modprobe: can't locate module sound-slot-0
Jul 10 15:42:17 felaco modprobe: can't locate module sound-service-0-3
There are no such modules that I can find. Do I need to get a new kernel
version?
The sb driver gives me this:
Jul 10 16:19:51 felaco kernel: Soundblaster audio driver Copyright (C) by
Hannu Savolainen 1993-1996
Jul 10 16:19:51 felaco kernel: SB 3.01 detected OK (220)
Jul 10 16:19:51 felaco kernel: sb: Interrupt test on IRQ5 failed - Probable
IRQ conflict
Jul 10 16:19:51 felaco kernel: SB DSP version is just 3.01 which means that
your card is
Jul 10 16:19:51 felaco kernel: several years old (8 bit only device) or
alternatively the sound driver
Jul 10 16:19:51 felaco kernel: is incorrectly configured.
The driver loads, but I hear nothing when I cat a .au file to /dev/audio. The
play command says:
sox: Unable to set the sample size to 16
With cs4232 I get:
/lib/modules/2.2.5-15/misc/cs4232.o: init_module: Device or resource busy
Jul 10 16:28:25 felaco kernel: cs4232: set synthio and synthirq to use the
wavefront facilities.
I believe my audio and dsp dev files are OK:
crw------- 1 chris sys 14, 4 Apr 17 15:53 /dev/audio
crw------- 1 chris sys 14, 3 Apr 17 15:53 /dev/dsp
Here's my isapnp.conf file stripped of most of the crud:
# (DEBUG)
(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
# Logical device id AZT0500
# Device support I/O range check register
# Device supports vendor reserved register @ 0x38
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
#
(CONFIGURE AZT1023/-1 (LD 0
# ANSI string -->IDE CDROM DISABLED<--
(NAME "AZT1023/-1[0]{IDE CDROM DISABLED }")
(ACT N)
))
#
# Logical device id AZT1019
# Device support I/O range check register
# Device supports vendor reserved register @ 0x38
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if
required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE AZT1023/-1 (LD 1
# ANSI string -->AUDIO<--
# Multiple choice time, choose one only !
# Start dependent functions: priority preferred
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0220
# Maximum IO base address 0x0220
# IO base alignment 16 bytes
# Number of IO addresses required: 16
(IO 0 (SIZE 16) (BASE 0x220) (CHECK))
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0388
# Maximum IO base address 0x0388
# IO base alignment 8 bytes
# Number of IO addresses required: 8
(IO 1 (SIZE 8) (BASE 0x0388) (CHECK))
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0534
# Maximum IO base address 0x0534
# IO base alignment 4 bytes
# Number of IO addresses required: 4
(IO 2 (SIZE 4) (BASE 0x0534) (CHECK))
# IRQ 5.
# High true, edge sensitive interrupt
(INT 0 (IRQ 5 (MODE +E)))
# First DMA channel 1.
# 8 bit DMA only
# Logical device is not a bus master
# DMA may execute in count by byte mode
# DMA may not execute in count by word mode
# DMA channel speed in compatible mode
(DMA 0 (CHANNEL 1))
# Next DMA channel 3.
# 8 bit DMA only
# Logical device is not a bus master
# DMA may execute in count by byte mode
# DMA may not execute in count by word mode
# DMA channel speed in compatible mode
(DMA 1 (CHANNEL 3))
# End dependent functions
(NAME "AZT1023/-1[1]{AUDIO }")
(ACT Y)
))
#
# Logical device id AZT2001
# Device support I/O range check register
# Device supports vendor reserved register @ 0x38
# Device supports vendor reserved register @ 0x39
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if
required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE AZT1023/-1 (LD 2
# ANSI string -->MPU401 MIDI<--
# Multiple choice time, choose one only !
# Start dependent functions: priority preferred
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0330
# Maximum IO base address 0x0330
# IO base alignment 2 bytes
# Number of IO addresses required: 2
(IO 0 (SIZE 2) (BASE 0x0330) (CHECK))
# IRQ 9.
# High true, edge sensitive interrupt
(INT 0 (IRQ 9 (MODE +E)))
# End dependent functions
(NAME "AZT1023/-1[2]{MPU401 MIDI }")
(ACT Y)
))
#
# Logical device id AZT3001
# Device support I/O range check register
# Device supports vendor reserved register @ 0x38
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if
required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE AZT1023/-1 (LD 3
# ANSI string -->GAME PORT<--
# Start dependent functions: priority acceptable
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0208
# Maximum IO base address 0x0208
# IO base alignment 8 bytes
# Number of IO addresses required: 8
(IO 0 (SIZE 8) (BASE 0x0208) (CHECK))
# End dependent functions
(NAME "AZT1023/-1[3]{GAME PORT }")
(ACT Y)
))
# End tag... Checksum 0x00 (OK)
# Card 2: (serial identifier 38 3d c4 34 5c 56 15 90 08)
# Vendor Id BDP1556, Serial Number 1036268636, checksum 0x38.
# Version 1.0, Vendor version 0.0
# ANSI string -->Best Data Products Inc. Smart One 56SPS Plug and Play
Modem<--
#
# Logical device id BDP1556
# Device supports vendor reserved register @ 0x38
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if
required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE BDP1556/1036268636 (LD 0
# Start dependent functions: priority acceptable
# Logical device decodes 10 bit IO address lines
# Minimum IO base address 0x02f8
# Maximum IO base address 0x02f8
# IO base alignment 8 bytes
# Number of IO addresses required: 8
(IO 0 (SIZE 8) (BASE 0x02f8))
# IRQ 3.
# High true, edge sensitive interrupt (by default)
(INT 0 (IRQ 3 (MODE +E)))
# End dependent functions
(NAME "BDP1556/1036268636[0]{Best Data Products Inc. Smart One 56SPS Plug and
Play Modem}")
(ACT Y)
))
# End tag... Checksum 0x00 (OK)
# Returns all cards to the "Wait for Key" state
(WAITFORKEY)
==============================================================================
Thanks in advance for all help!
--
-----------------------------------------------------------------------------
Chris Felaco mailto:[EMAIL PROTECTED]
-----------------------------------------------------------------------------
------------------------------
From: Thierry Nivon <[EMAIL PROTECTED]>
Subject: 3c589d pcmcia installation
Date: Sat, 10 Jul 1999 18:56:25 +0000
After some unsuccessless tries to configure my 3c589d
pcmcia card, i
send an SOS.
my pcmcia driver is ok, becaus I use it presently with a
modem card.
but with my 3c589D, it always says
unresolved symbol netif_rx_....
unresolved symbol dev_tint_....
...
...
when I try to load it by insmod
also at load time it says to me it can not fint net-pf-4
or
net-pf-5,
but I don't know if it's in relation.
Could I have some answer, please.
Thanks for all
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Will My Wheel Mouse Work w/ Linux?
Date: Sat, 10 Jul 1999 19:52:31 GMT
I appreciate the link, however, i've already tried
that page. It is rather old and I have a hard time
sorting through all the stuff there. I was hoping
that someone with a similar set up has had success
with scrolling. Anyone done it?
In article <[EMAIL PROTECTED]>,
Tim Moore <[EMAIL PROTECTED]> wrote:
>
http://www.inria.fr/koala/colas/mouse-wheel-scroll
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Thomas Kochak <[EMAIL PROTECTED]>
Subject: Re: asus TNT v3400 problems
Date: Sat, 10 Jul 1999 13:53:23 -0500
Get the linux drivers for riva tnt from nvidia.
W Thompson wrote:
> I recently got a new AGP card, asus TNT v3400, its a 2D/3D card with a riva
> TNT chip.
> I am haveing trouble configuring xwindows, it worked perfectly fine with my
> old AGP card, Trident 3DImage.
> I tried to reconfigure it and used the asus riva128 driver but when i try to
> run xwindows the screen goes all black and there are colours over the
> screen.
> I am not to knowledgable on the subject so could someone please tell me if i
> have to get a new driver or is there something else i have to do.
>
> thanks in advance
> ~Wayne~
------------------------------
From: Thomas Kochak <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.help,comp.os.linux.misc,comp.os.linux.questions,comp.os.linux.setup
Subject: Re: Cant get Creative Ensoniq AudioPCI to work
Date: Sat, 10 Jul 1999 13:45:16 -0500
What is ALSA ?
[EMAIL PROTECTED] wrote:
> I use ALSA with Ensoniq PCIaudio, RH6.0 2.2.15-22 kernel (custom compiled).
> I am completely satisfied.
>
> Muuga wrote:
> >
> > Alot of ppl swear by this card(thats why I bought it), but it doesnt
> > configure too well under linux.
> >
> > Under Win98 its irq=11 I/O=220 DMA=1
> > of course it works great under windoze :/
> >
> > this is what it looks like under /proc/pci
> >
> > #PCI devices found: Bus 0, device 10, function 0:
> > # Multimedia audio controller: Ensoniq Unknown device (rev 6).
> > # Vendor id=1274. Device id=1371. Slow devsel. IRQ 11. Master
> > #Capable. Latency=64. Min Gnt=12.Max Lat=128. I/O at 0xe800.
> >
> > and /etc/conf.modules
> >
> > #alias sound sb
> > #options -k sb io=0x220 irq=11 dma=1
> >
> > I running RH 5.1 with a recompliled 2.0.37 kernel
> > on a FIC 503+ k6 300
> > I must have recompiled 2 dozen times(just for the sound section of make
> > menuconfig , since I got the card.
> >
> > i get this on boot up :
> > #Sound initialization started
> > #Sound initialization complete
> > not once did I get something in between :(
> >
> > maybe im missing something in the sound configuration part of compilation?
> >
> > CONFIG_SOUND=y
> > CONFIG_SB=y
> > CONFIG_AUDIO=y
> > CONFIG_YM3812=y
> > SBC_BASE=220
> > SBC_IRQ=11
> > SBC_DMA=1
> > SB_DMA2=-1
> > SB_MPU_BASE=388
> > SB_MPU_IRQ=-1
> > DSP_BUFFSIZE=65536
> >
> > if you have this card and got it working under linux , please tell me how
> > you have you box configured.
> > Thanks
------------------------------
Subject: Re: Tekram DC-390F SCSI Card ?
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 10 Jul 1999 15:36:14 -0400
Bryan <Bryan@[EMAIL PROTECTED]> writes:
> Michael Meissner <[EMAIL PROTECTED]> wrote:
> : Bryan <Bryan@[EMAIL PROTECTED]> writes:
>
> : > Richard Bumby <[EMAIL PROTECTED]> wrote:
> : >
> : > : In linux, older kernels (before 2.0.3x) needed some help from files on
> : > : the TekrAm site, but the current 53C8xx driver gives you support right
> : > : out of the box.
> : >
> : > except for ONE minor nit - the disk activity led doesn't work ;-(
> : >
> : > it does under 'doze - I know I have mine hooked up ok - but under the linux
> : > driver, the led display is not operational. anyone know why?
>
> : Back when I had TekRam scsi controllers as my main scsi, the led display worked
> : for me using 2.2.x kernels. I vaguely remember real old drivers not supporting
> : the LED.
>
> I tried the 2.0.36 driver from the tekram site and it used the led,
> but the 2.2 driver I'm using keeps it dark ;-(
>
> maybe I'm using the wrong driver. there are SEVERAL that appear to be
> very similar - which one would you recommend I use?
NCR53C8XX, and if available SYM53C8XX. The config flags I use are:
CONFIG_SCSI_NCR53C8XX=y
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_PQS_PDS is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
--
Michael Meissner, Cygnus Solutions
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886
email: [EMAIL PROTECTED] phone: 978-486-9304 fax: 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 (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
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
******************************
