Linux-Hardware Digest #62, Volume #14 Wed, 20 Dec 00 03:13:05 EST
Contents:
Re: Intel Easy PC camera - cannot be supported in Linux! ("Kyle Jacobs")
/dev/sequencer problem es1371 (Scott Rainaldo)
Re: SuSe on Win98 ("Peter T. Breuer")
Re: Intel Easy PC camera - cannot be supported in Linux! ("Aaron R. Kulkis")
Buffalo SCSI-III PCMICA Card ("owl")
Compaq SCSI ("Ilbey")
Re: open gl + Nvidia 9-5 + Tnt under Redhat 7 ("Don Ward")
Re: any Good MB for Duron? (Nathan Hollingsworth)
Re: RH 7.0 & Promise UATA66 Controller (Nathan Hollingsworth)
Re: ATA-66 drive that only detects as ATA-33 (Nathan Hollingsworth)
Re: bootable raid 1 ([EMAIL PROTECTED])
PCMCIA, winmodems(gag), and Acer TravelMate (Josh)
How to configure ESS688 soundcard to play mp3 files under SUSE 7.0 ("Pierre-Andre
Rovelli")
lm_sensors and a ASUS A7V (Nathan Hollingsworth)
----------------------------------------------------------------------------
From: "Kyle Jacobs" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,alt.linux.sux
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Date: Wed, 20 Dec 2000 05:13:16 GMT
All this hardware works because they all have the fortune of being based
around America's top 10% hardware.
1. Soundblaster Live: PCI sound system from the SB64 base of sound
processors
2. Creative Annihaltor: nVidia GeForce2 GTS; the best, most popular video
graphics chipset in North America
3. Microsoft Intellimouse: It's a mouse. With token support for USB (which
was desgined around supporting MICE and Keyboards) in the Linux kernel, this
works.
4.Xirlink USB camera: Uses the same TWAIN dynamics that digicam's and
scanners used since the Casio QV-10, why it works over USB? Luck.
5.HP LaserJet 2100M: I'll bet you this thing doesn't work outside of 75DPI
printing. This printer features legacy firmware so it can accomidate a lack
of software commands.
6. Adaptec 2940UW: Nothing says generic SCSI adaptor like Adaptec's 2000
series SCSI adaptors.
7.3com 3c905 NIC: Another generic NIC card.
8.USB-ZIP250: Linux's USB layer was engeneered with mice, keyboards and
iomega's USB devices in mind. No DUH that this works.
9.Jaz 1G: It's a tape drive, it's from iomega. But it's still a tape drive.
So you see, your stock collection of top hardware, and hardware based around
other top 10% hardware makes your system the ideal runner for a Linux
distro.
"A transfinite number of monkeys" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Tue, 19 Dec 2000 16:43:00 GMT,
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> : You can argue till you are blue in the face about the evil hardware
> : manufacturers withholding specs but it still boils down to the same
> : thing.
> :
> : Linux sucks at supporting modern hardware.
>
> Obviously why on my PC, such "archaic" hardware as:
>
> SoundBlaster Live!
> Creative Annihilator 2 (GeForce 2 GTS based card)
> Micro$oft USB Intellimouse
> IBM (really Xirlink) USB Camera
> HP LaserJet 2100M
> Adaptec 2940UW
> Asus CUSL2 (i815e based) motherboard
> 3com 3c905 NIC
> USB Zip 250
> Jaz 1G
>
> all work without a hitch, right? Yeah, all of that stuff is ancient,
right?
>
> --
> Jason Costomiris <>< | Technologist, geek, human.
> jcostom {at} jasons {dot} org | http://www.jasons.org/
> Quidquid latine dictum sit, altum viditur.
------------------------------
From: Scott Rainaldo <[EMAIL PROTECTED]>
Subject: /dev/sequencer problem es1371
Crossposted-To: comp.os.linux.setup
Reply-To: [EMAIL PROTECTED]
Date: Wed, 20 Dec 2000 05:23:17 GMT
Hello all,
My soundblaster PCI 64 (es1371) works fine so far for playing CDs, mp3s,
and wavs (all PCM output?). However, whenever I try to play midi files or
even open any program which uses /dev/sequencer I get an error.
Example:
$ kmid
KMid 2.0 Copyright (C) 1997,98,99,2000 Antonio Larrosa Jimenez. Malaga
(Spain)
KMid comes with ABSOLUTELY NO WARRANTY; for details view file COPYING
This is free software, and you are welcome to redistribute it
under certain conditions
ERROR: Couldn't open /dev/sequencer to get some information
Here is what my /etc/modules.conf looks like:
alias char-major-107 3dfx
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
alias usb-interface usb-uhci
alias parport_lowlevel parport_pc
pre-install plip modprobe parport_pc ; echo 7 > /proc/parport/0/irq
alias eth0 3c59x
options es1371 joystick=0x200
alias sound-slot-0 es1371
alias sound-service-0-1 es1371
Can anyone tell me what I am missing or doing wrong? Thank you!
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: SuSe on Win98
Date: Wed, 20 Dec 2000 05:57:34 GMT
Tiefenbacher <[EMAIL PROTECTED]> wrote:
> What do you think of my way of partitioning:
Read the Partition-HOWTO.
Peter
------------------------------
From: "Aaron R. Kulkis" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.development.system
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Date: Wed, 20 Dec 2000 00:56:02 -0500
jtnews wrote:
>
> If I reverse engineer the camera protocol through the USB interface,
> develop a Linux driver, distribute the driver under the GPL
> over the Internet, can I be sued by Intel for violating their
> intellectual property?
>
NOPE!
> Kasper Dupont wrote:
> >
> > jtnews wrote:
> > >
> > > The Intel Easy PC camera is not supported in Linux!
> > > You can't even write a driver for it!
> > >
> > > I got it as a "free" add-on with my new Dell Dimension
> > > L600cx, but now it seems I made the wrong choice!
> > >
> > > Why does a $40 cheapo camera have to be proprietary for
> > > Intel? I thought Intel made all their money because they make
> > > huge volumes of flash memory chips over their competitors.
> > >
> > > I better choose the Lexmark color printer as a free add on next
> > > time!
> > >
> >
> > Of course it is posible to write a driver for that
> > camera, but you would have to reverse engineer the
> > protocols.
> >
> > Depending on how it is connected you could hook in
> > a piece of hardware or software to watch the
> > communication.
> >
> > I don't understand Intel's policy, a Linux driver
> > would allow more people to use the camera and then
> > they could expect to sell more cameras. But
> > perhaps they have some secret agreement with MS.
> >
> > --
> > Kasper Dupont
--
Aaron R. Kulkis
Unix Systems Engineer
DNRC Minister of all I survey
ICQ # 3056642
H: "Having found not one single carbon monoxide leak on the entire
premises, it is my belief, and Willard concurs, that the reason
you folks feel listless and disoriented is simply because
you are lazy, stupid people"
I: Loren Petrich's 2-week stubborn refusal to respond to the
challenge to describe even one philosophical difference
between himself and the communists demonstrates that, in fact,
Loren Petrich is a COMMUNIST ***hole
J: Other knee_jerk reactionaries: billh, david casey, redc1c4,
The retarded sisters: Raunchy (rauni) and Anencephielle (Enielle),
also known as old hags who've hit the wall....
A: The wise man is mocked by fools.
B: Jet Silverman plays the fool and spews out nonsense as a
method of sidetracking discussions which are headed in a
direction that she doesn't like.
C: Jet Silverman claims to have killfiled me.
D: Jet Silverman now follows me from newgroup to newsgroup
...despite (C) above.
E: Jet is not worthy of the time to compose a response until
her behavior improves.
F: Unit_4's "Kook hunt" reminds me of "Jimmy Baker's" harangues against
adultery while concurrently committing adultery with Tammy Hahn.
G: Knackos...you're a retard.
------------------------------
From: "owl" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.networking,comp.os.linux.portable,comp.os.linux.questions,comp.os.linux.setup
Subject: Buffalo SCSI-III PCMICA Card
Date: Wed, 20 Dec 2000 14:20:49 +0800
I has just bought a Buffalo SCSI-III PCMICA Card (Card Bus) and it is about
the half price of Adaptec-1480.
Do anybody know if there is Linux driver for it ?
--
Andy Won
Web Development Engineer
OnLine Service - beenz.com
Greater China
------------------------------
From: "Ilbey" <[EMAIL PROTECTED]>
Subject: Compaq SCSI
Date: Wed, 20 Dec 2000 15:16:37 +0900
Hi ,
I have a compaq scsi adapter with aic3860q chipset.
#echo "scsi add-single-drive 0 0 6 0" >proc/scsi/scsi
cat proc/scsi/scsi dont find my scsi.
Is this a compatibility problem or am i making something wrong?
Any suggestion?
Thanks
------------------------------
From: "Don Ward" <[EMAIL PROTECTED]>
Subject: Re: open gl + Nvidia 9-5 + Tnt under Redhat 7
Date: Wed, 20 Dec 2000 00:21:09 +0000
In article <[EMAIL PROTECTED]>, "Daniel"
<[EMAIL PROTECTED]> wrote:
> Yeah I did remove all the Mesa files that they had listed. Did you use the
> latest drivers? the 0.9-5? I will try rem out that line though and see what
> happens.
>
>
Yep, I am using the 0.9-5 drivers.
> Don Ward wrote:
>>
>>
>> BIG SNIP
--
Don Ward
dwarthogatbresnanlin.knet
Caldera e2.4 KDE2 Xfree401
------------------------------
From: Nathan Hollingsworth <[EMAIL PROTECTED]>
Subject: Re: any Good MB for Duron?
Date: Wed, 20 Dec 2000 06:34:49 GMT
I am running a Duron 700 on a ASUS A7V with no probs too.
Frank Miller wrote:
> [EMAIL PROTECTED] wrote:
> >
> > In article <[EMAIL PROTECTED]>,
> > Frank Miller <[EMAIL PROTECTED]> wrote:
> > > Dack wrote:
> > > >
> > > > For Linux support, which MB are good for AMD Duron?
> > > Look at the AMD site for supported MBs. I am using the Abit KT7 with
> > an
> > > Athlon Socket A 700 MHz CPU with no problems.
> > >
> > Do you have to use a paricular ver of kernel or do you have to recompile
> > the kernel?
> >
> > Sent via Deja.com
> > http://www.deja.com/
> Mandrake 7.2 and Redhat 7 (both download versions) worked with no
> problems.
------------------------------
From: Nathan Hollingsworth <[EMAIL PROTECTED]>
Subject: Re: RH 7.0 & Promise UATA66 Controller
Date: Wed, 20 Dec 2000 06:49:32 GMT
I know with my 2.4 kernel I have to add the kernel option ide=reverse for my
promise card. This makes the kernel boot the onboard ide second and the promise
controller first so that your primary shows up as hda.
James Richard Tyrer wrote:
> Jason Greenbaum wrote:
>
> > I am trying to install Redhat Linux 7.0 on a computer with a Promise Ultra66
> > controller. It seems that Linux cannot find the drive attached to this
> > controller. Does anyone know a workaround?
> >
> > -Jay Greenbaum
>
> I don't understand why, but it appears that the Kernel that Red Hat supplies
> does not have the IDE patch applied.
>
> The HOWTO explains how to install with an unpatched Kernel:
>
> http://www.linuxdoc.org/HOWTO/mini/Ultra-DMA-5.html#ss5.1
>
> Then you need to down load a clean copy of the Kernel from:
>
> http://www.kernel.org
>
> and apply the patch which is available from:
>
> http://www.kernel.org/pub/linux/kernel/people/hedrick/
>
> And, build a new Kernel.
>
> Until you do that, edit your "lilo.conf" file. Add the append option with the
> same parameters that you used to boot for install.
>
> JRT
------------------------------
From: Nathan Hollingsworth <[EMAIL PROTECTED]>
Subject: Re: ATA-66 drive that only detects as ATA-33
Date: Wed, 20 Dec 2000 07:18:17 GMT
Hey everyone,
Fixed my problem. I just enabled the kernel option:
"Ignore word93 validation bits"
on the ATA page of the 2.4 kernel.
And everything works fine now. Here is what I get now:
hda: 26564832 sectors (13601 MB) w/2048KiB Cache, CHS=1653/255/63, UDMA(66)
Nathan Hollingsworth wrote:
> I downloaded the 2.4.0-test12 kernel and tried to get things to work on
> my new Asus K7A board. But whenever I booted my newly compiled kernel
> my western digital 13 gig showed up as
> running only in UDMA 33 mode, though it is a 66 drive. I have a 40 pin
> / 80 conductor ATA66 ide cable and I know the onboard chipset is ATA-66
> capable but yet my drive doesn't want
> to do it. Here is some kernel output:
>
> VP_IDE: IDE controller on PCI bus 00 dev 21
> VP_IDE: chipset revision 16
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:4.1
> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
> PDC20265: IDE controller on PCI bus 00 dev 88
> PCI: Found IRQ 10 for device 00:11.0
> PDC20265: chipset revision 2
> PDC20265: not 100% native mode: will probe irqs later
> PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
> ide2: BM-DMA at 0x8400-0x8407, BIOS settings: hde:pio, hdf:pio
> ide3: BM-DMA at 0x8408-0x840f, BIOS settings: hdg:pio, hdh:pio
> hda: WDC WD136AA, ATA DISK drive
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> hdc: TOSHIBA CD-ROM XM-6702B, ATAPI CDROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 26564832 sectors (13601 MB) w/2048KiB Cache, CHS=1653/255/63,
> UDMA(33)
> hdc: ATAPI 48X CD-ROM drive, 128kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.11
> Partition check:
> hda: hda1 hda2 hda3 < hda5 hda6 >
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
>
> I have my 13gig connected to the VIA hd controller and not the Promise.
> I had the same problem with the Promise too.
>
> I have the appropriate chipset support compiled directly into the kernel
> and I have enable "Use UDMA by default" etc. But it won't run at 66.
> Argh.
>
> Even better I booted the rescue image from my Mandrake 7.2 CD and it
> detected it and run it at ATA66.
>
> Can someone please tell me what I am doing wrong.
>
> Thanks,
> Nathan
>
> P.S. take the SPM out of my email to contact me directly :-)
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
alt.linux,alt.os.linux.mandrake,alt.os.linux.slackware,alt.uu.comp.os.linux.questions,comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.setup,linux.dev.kernel
Subject: Re: bootable raid 1
Date: Wed, 20 Dec 2000 07:18:14 GMT
Reply-To: [EMAIL PROTECTED]
I am pleased that I have
overcome this issue and here are my conclusions.
My previous raid configuration was set up using CHS method for
harddisk geometry. There was no reason for doing this other than it
was a part of the diagnostic procedure for a previous issues regarding
a western digital harddrive that identifies itself to the tyan bios as
being ata66 but really only operates reliably at ata33. The CHS really
had nothing to do with the timing issue, but I suspect that the
partition table arrangement did. The symptom of this timing issue was
not being able to reliably modify the harddrive's partition tables,
strangely enough. Mandrakeuser.org has the write up about certain
western digital harddrives that have this issue.
When using CHS, the block arrangement for the boot partitions on both
the drives is different that with LBA. LBA arranges partition sizes
equally. I am not 100% certain, but this is the only change that I
implemented that made the difference. It might explain why when both
drives were installed that the system booted, but when either was
removed, it would not boot.
Using LBA translation method in both the BIOS and with fdisk using
matching LBA geometries, I can now boot from either drive- the way
raid1 is meant to be . . .
Other Details:
I am using kernel 2.2.18 with all the patches and recommendations that
Godfrey Livingstone provided.
All is well with this and I will be doing benchmarks at 32k size
chunks shortly.
I am using lilo 21.5 and a single lilo.conf.
Here are my partition arrangements OLD and NEW:
OLD:
Disk /dev/hda: 15 heads, 63 sectors, 13328 cylinders
Units = sectors of 1 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 63 68039 33988+ fd Linux raid
autodetect
/dev/hda2 68040 12278384 6105172+ fd Linux raid
autodetect
/dev/hda3 12278385 12594959 158287+ 82 Linux swap
Disk /dev/hdc: 16 heads, 63 sectors, 16278 cylinders
Units = sectors of 1 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 63 66527 33232+ fd Linux raid
autodetect
/dev/hdc2 66528 12275423 6104448 fd Linux raid
autodetect
/dev/hdc3 12275424 12594959 159768 82 Linux swap
NEW
Disk /dev/hda: 255 heads, 63 sectors, 784 cylinders
Units = sectors of 1 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 63 80324 40131 fd Linux raid
autodetect
/dev/hda2 80325 12289724 6104700 fd Linux raid
autodetect
/dev/hda3 12289725 12594959 152617+ 82 Linux swap
Disk /dev/hdc: 255 heads, 63 sectors, 1021 cylinders
Units = sectors of 1 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 63 80324 40131 fd Linux raid
autodetect
/dev/hdc2 80325 12289724 6104700 fd Linux raid
autodetect
/dev/hdc3 12289725 12594959 152617+ 82 Linux swap
Here is my /etc/lilo.conf:
#boot=/dev/hda
boot=/dev/md1
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=vmlinuz
vga=normal
keytable=/boot/us.klt
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinux
label=vmlinux
# root=/dev/hda2
root=/dev/md0
append=" ide3=autotune ide1=autotune ide0=autotune hdh=ide-scsi"
read-only
image=/boot/vmlinuz
label=vmlinuz
# root=/dev/hda2
root=/dev/md0
append=" ide3=autotune ide1=autotune ide0=autotune hdh=ide-scsi"
read-only
Thanks again for all of your help!
Charles Wilkins
On Tue, 19 Dec 2000 07:50:51 -0500, Chas2K
<[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] wrote:
>>
>> t doesn't matter which drive i pull out, i get the same results
>>
>> On Mon, 18 Dec 2000 20:55:19 -0500, Chas2K
>> <[EMAIL PROTECTED]> wrote:
>>
>> >[EMAIL PROTECTED] wrote:
>> >>
>> >> I am currently doing bootable raid 1 with all of the latest patches
>> >> for
>> >> 2.2.18 and then some.
>> >> When I try to boot the system with either drive removed, I get a bunch
>> >> of
>> >> 010101010's in an endless loop.
>> >> Yet, when both drives are in, the system comes up fine. What am I
>> >> doing
>> >> wrong?
>> >>
>> >> Using lilo 21.5
>> >>
>> >> lilo.conf.hda
>> >>
>> >> disk=/dev/md0
>> >> bios=0x80
>> >> sectors=63
>> >> heads=15
>> >> cylinders=13328
>> >> partition=/dev/md1
>> >> start=63
>> >> boot=/dev/hda
>> >> map=/boot/map
>> >> install=/boot/boot.b
>> >> vga=normal
>> >> default=vmlinux
>> >> keytable=/boot/us.klt
>> >> prompt
>> >> timeout=50
>> >> message=/boot/message
>> >> menu-scheme=wb:bw:wb:bw
>> >> image=/boot/vmlinuz
>> >> label=vmlinuz
>> >> root=/dev/md0
>> >> append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi"
>> >> read-only
>> >> image=/boot/vmlinux
>> >> label=vmlinux
>> >> root=/dev/md0
>> >> append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi"
>> >> read-only
>> >>
>> >> lilo.conf.hdc
>> >>
>> >> disk=/dev/md0
>> >> bios=0x81
>> >> sectors=63
>> >> heads=16
>> >> cylinders=16278
>> >> partition=/dev/md1
>> >> start=63
>> >> boot=/dev/hdc
>> >> map=/boot/map
>> >> install=/boot/boot.b
>> >> vga=normal
>> >> default=vmlinux
>> >> keytable=/boot/us.klt
>> >> prompt
>> >> timeout=50
>> >> message=/boot/message
>> >> menu-scheme=wb:bw:wb:bw
>> >> image=/boot/vmlinuz
>> >> label=vmlinuz
>> >> root=/dev/md0
>> >> append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi"
>> >> read-only
>> >> image=/boot/vmlinux
>> >> label=vmlinux
>> >> root=/dev/md0
>> >> append=" ide3=autotune ide1=autotune ide2=autotune hdh=ide-scsi"
>> >> read-only
>> >
>> >Looks like you're pulling out the drive with the boot sector on it. Is
>> >your configuration mirroring all of the drives together, or just the
>> >partitions with data?
>> >
>> >Chas2K
>
>I got this same stream of blits when I took drive 0 off line and thought
>I had made the 2nd drive active. Ok. I'm out of wisdom... anybody else?
------------------------------
From: Josh <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,git.unix.linux
Subject: PCMCIA, winmodems(gag), and Acer TravelMate
Date: Wed, 20 Dec 2000 02:40:15 -0500
I have an Acer TravelMate 737TLV, running red hat 6.2 with kernel
2.2.16. Until now I haven't needed to use a modem since I have a LAN, but
now I'm trying to set up a PPP dialup connection via modem. Does anyone
know the current status of "winmodems" under kernel 2.2.16? Are they dead
weight? If so, I'd like to use a PCMCIA card, which I've been attempting,
with no success. When the OS boots up I get an "OK" from "Starting
pcmcia" but I don't know what device it is, or how to do anything with
it.. could anybody offer a suggestion as to how to go about setting up a
PCMCIA modem and dialing up? Thanks...
Josh Jones
[EMAIL PROTECTED] / [EMAIL PROTECTED]
1641174
------------------------------
From: "Pierre-Andre Rovelli" <[EMAIL PROTECTED]>
Subject: How to configure ESS688 soundcard to play mp3 files under SUSE 7.0
Date: Wed, 20 Dec 2000 07:55:33 +0000 (UTC)
I have installed SUSE 7.0 on a Compaq Deskpro 5120. The Soundcard is a
ESS688 audiodrive. I have installed it manually using YAST2 under ESS688
Audiodrive. I can play WAV and audio-cd files but mp3 doesn't work. Does
anybody know what's wrong ?
Thank you in advance for your help
Pierre-Andre Rovelli
[EMAIL PROTECTED]
------------------------------
From: Nathan Hollingsworth <[EMAIL PROTECTED]>
Subject: lm_sensors and a ASUS A7V
Date: Wed, 20 Dec 2000 08:04:07 GMT
Hey,
Has anyone got lm_sensors to work with an ASUS A7V? I can't seem to get
it to work at all. I am trying to get it to work with a 2.4.0-test12
kernel.
Nathan
------------------------------
** 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
******************************
