Linux-Hardware Digest #403, Volume #12 Sat, 4 Mar 00 19:13:07 EST
Contents:
Twinhead Slimnote XL 200 TK (Sebastian Raue)
Configure a Canon BJC-4100 ? (kondor)
Creative Geforce card and KDE ("Martin")
SoundBlaster Awe64 PCI? (Bo B)
Sound refuses to play after invoking sox. ([EMAIL PROTECTED])
PCMCIA on Compaq Armada 7300T Laptop ([EMAIL PROTECTED])
Asus K7M / Redhat 6.1 64meg limitation? ([EMAIL PROTECTED])
Re: dual modem in RH linux (John Kicklighter)
ALSA Hangs System
Re: X driver for onboard SiS card ("Jason Byrne")
controllerless modem ([EMAIL PROTECTED])
SCSI tape drive, device not ready ([EMAIL PROTECTED])
Re: Binary compatibility ("Eckhard.Meding")
Re: Asus K7M / Redhat 6.1 64meg limitation? (matthew)
Re: SB AWE 64 GOLD issues (^Vigil^)
Getting Geforce DDR to work ("s barnes")
Re: Binary compatibility ("Barry Kiernan")
----------------------------------------------------------------------------
From: Sebastian Raue <[EMAIL PROTECTED]>
Subject: Twinhead Slimnote XL 200 TK
Date: Sat, 04 Mar 2000 20:16:18 +0100
Hi
I'm looking for an XFreeConfig-File for
the Twinhead Slimnote XL 200 TK.
I got that laptop without any infos.
It has to loudspeakers. Does anybody kow
if it has a build in soundcard and if so
which chip it has on it?
Thanks in advance
Sebastian
------------------------------
From: kondor <[EMAIL PROTECTED]>
Subject: Configure a Canon BJC-4100 ?
Date: Sat, 04 Mar 2000 20:29:37 +0100
Hi, I've got a Slackware 7.0 and their is no tools like printtools, and
I
am not able to configure my bjc-4100
I don't know what tu put in /etc/printcap
and how to configure lpr with gohstview to print .ps files.
Can you help me ?
please write to me at :
[EMAIL PROTECTED]
THANKS!
------------------------------
From: "Martin" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Creative Geforce card and KDE
Date: Sat, 4 Mar 2000 19:29:55 -0000
I have recently installed a Creative Geforce graphics card. When trying to
start xwindows I get an error message that keeps flashing up as the monitor
is trying to synch. I have tried reconfiguring xf86config, but still cant
get xwindows going.
Any help would be appreciated.
Martin
------------------------------
From: Bo B <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: SoundBlaster Awe64 PCI?
Date: Sat, 04 Mar 2000 14:57:03 -0500
Is there a SB Awe64 PCI version on the market? (ES1371 chip??)
I found a store selling a SB PCI card, with an ES1371 chip
with no drivers or docs, pretending to be Awe64, but it's nowhere
written on the card. The only thing I could find was ES1371 chip.
I know that Awe64 is usually ISA.
But if it is awe64 PCI, does it work with linux kernel 2.2.14?
Thanks
Bo
------------------------------
From: [EMAIL PROTECTED]
Subject: Sound refuses to play after invoking sox.
Date: Sat, 04 Mar 2000 20:02:42 GMT
Hi All,
I once had an old ESS1868 in my comp and i got it (finally)
playing using 'play'. After finding out that it was just a wrapper for
sox i ran that one and i got an "invalid buffer size 0" or something
like that.
I tried a few things to correct the problem, but nothing worked. The
sound card was working as it was though, in winbloze. Thinking the sound
card was faulty, (and it was old anyway), I went and purchased an OEM
Creative PCI64. Recompiled the kernel and got it working. Tried playing
sound but still no go. Same error.
I can't see any other way out than probably.. I dont know. I thought
of reinstalling linux but it doesn't make sense. I mean, where would the
error be?
At the moment I'm using kernel 2.2.13 in slackware 7 on a BH6 m/b.
Also another question - what other stuff should I include with my
sound card drivers when configuring my kernel? The OSS modules? OPL3?
etc? The driver that's there has the exact number of my sound card's
chipset. Should I compile support as built-in? Modules? The ESS1868
required the crap to be as modules only. Not sure about this one.
Any help very very much appreciated. I hate when things don't work.
$%&@$%&@$%&@$%*#%^
Cheers,
Penggu
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Subject: PCMCIA on Compaq Armada 7300T Laptop
Date: Sat, 04 Mar 2000 20:12:58 GMT
Hi,
Hope you can help. I've had Linux installed on my laptop for some time
and recently decided to get the PCMCIA cards working. However, the
problem I have is that every card inserted gets recognised as a memory
card and the module memory_cs gets loaded (and fails obviously). The
sockets seem to get recognised OK (see output from /proc/pci below).
Any ideas?
Specs :
Compaq Armada 7330T with Texas Instruments PCI1131 (rev 1)
cardbus bridge (which uses the i82365 PCIC according to the
PCMCIA_HOWTO)
Linux kernel - Slakware 2.0.35
Card Services v3.1.9 (pcmcia-cs-3.1.9)
PCMCIA cards being used are US Robotics Sportster 28,800 (with
xjack) and 3com Etherlink III, both supported cards
Ouput of lsmod before card insert :
Module: #pages Used by:
ds 2 2
i82365 5 2
pcmcia_core 9 [ds i82365] 0
Messages received when card inserted :
cs: unable to map card memory!
cs: unable to map card memory!
Output of lsmod after card inserted :
Module: #pages Used by:
memory_cs 2 0
ds 2 2
i82365 5 2
pcmcia_core 9 [ds i82365] 0
Contents of /var/lib/pcmcia/stab (when card in) :
Socket 0: empty
Socket 1: Anonymous Memory
The kernel has been configured for networking as per the PCMCIA_HOWTO.
It also mentions about modifying the cis_speed option for the
pcmcia_core driver from the default of 300 to something higher for card
recognition problems. I doubled it and it had no affect.
Like I said, it seems to recognise the cardbus fine, it just sees all
cards as memory cards and so loads the memory_cs driver.
Thanks in advance.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.install
Subject: Asus K7M / Redhat 6.1 64meg limitation?
Date: Sat, 04 Mar 2000 20:14:49 GMT
Hi,
I am using a K7M with AMD K7-700 and 256 meg of SDRAM
running RedHat 6.1 (kernel 2.2.12-20). The BIOS detects
all 256 meg but RedHat Linux only detects only upto 64 meg.
Win95 on the same machine detects the correct size.
I am using two Micron 128 Meg 8 ns PC100 SDRAMs.
I've tried disabling SDRAM timing, rearranging the memory
slots, slowing down the bus speed to no avail.
Has anyone else run into similar problems?
Thank you.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: John Kicklighter <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,alt.comp.linux.isp
Subject: Re: dual modem in RH linux
Date: Sat, 04 Mar 2000 20:24:31 GMT
You would need to find a way to make linux do what is called a multipoint
connection and also confirm that your ISP will allow a multipoint
connection. Simply connecting two modems will not do the job for you. The
ISPs modem banks need to be able to combine them at the ISP side.
Hope that helps.
[EMAIL PROTECTED] wrote:
> Hi,
> I was thinking of increasing my internet connection speed to my isp by
> using 2 modems (i.e. 2 simultaneous connections), but not sure if this
> is possible in linux, or win95 for that matter.
> say, if i setup two 56k modem on my linux machine to connect to my
> isp, would i get 112k for the connection speed? Or am i talking nonsense
> here ?
> If this is actually possible, could you tell me how i can do that? I
> have been looking for a how-to, but i have yet to find one that
> describes a dual-modem setup.
>
> Any help is greatly appreciated.
>
> Thanks,
> ch
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
------------------------------
From: <[EMAIL PROTECTED]>
Subject: ALSA Hangs System
Date: Sat, 04 Mar 2000 20:30:22 GMT
I have ESS Solo1 sound card, with the alsa drivers. They loaded fine. But,
when i play a sound, the system hangs, and i have to reboot.
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "Jason Byrne" <[EMAIL PROTECTED]>
Subject: Re: X driver for onboard SiS card
Date: Sat, 4 Mar 2000 12:40:57 -0800
There are drivers in newer versions of XFree86 if you look for the card (run
'xf86config')
btw... SuSE 6.3... 'sax' autodetects the card 'out of the box'
also... www.sis.com.tw lists drivers (xsis.tgz or xsis.rpm with some hints
in a text file)
or... I believe the same 'xsis' drivers are at www.suse.com
btw... what board do you have... and which Linux distribution are you using?
I might be able to help you with a lot more.
I have a similar board (maybe the same one - PCChips M748LMRT).. and I have
'everything' working... including the 'winmodem'
Martin Fluck <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi,
> I'm having problems setting up the display on an instalation of Linux, the
> problem being that my vga, network, mouse etc "cards" are all onboard and
> Linux is not recognising them, the drivers supplied with the motherboard
are
> for windows only! Does anyone know how to get round this, or, have a
Sis620
> driver for linux?
> cheers.
> martin
------------------------------
From: [EMAIL PROTECTED]
Subject: controllerless modem
Date: Sat, 04 Mar 2000 21:48:03 GMT
Hi,
I have the Diamond SupraMax voice PCI. I want to make it work on linux.
The people of Diamond say it is a controllerless modem. What does that
mean and what would I have to do to make it work in Linux.
Or shall I buy another modem?
Thank you
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup
Subject: SCSI tape drive, device not ready
Date: Sat, 04 Mar 2000 22:32:07 GMT
Hi. Please help...
I have a Seagate TapeStor DAT 24 internal SCSI tape drive, and a
Adaptec 2930 Ultra SCSI card. I'm on RH Linux 6.1, kernel 2.2.12.
If root does "mt -f /dev/nst0 erase" (or rewind), the reply to stderr
is "/dev/nst0: Input/output error". Also, each time root tries this,
something like these two lines is appended to /var/log/messages :
Mar 4 13:33:12 madhanilab kernel: Device not ready. Make sure there
is a disc in the drive.
Mar 4 13:33:44 madhanilab last message repeated 31 times
The number of repeats is usually 31, but not always. "mt -f /dev/nst0
status" yields:
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (10000):
IM_REP_EN
I don't think the problem is the SCSI card, since I can read&write
to my SCSI CD-RW just fine. Also, I think that the SCSI tape drive
is being detected OK, since the above "mt ... status" works, and
because /var/log/messages would probably say something different.
Oh yeah, the behaviour outlined above is the same regardless of
whether the cartridge is physically in the drive.
Thanks for any help you can give.
Aaron
PS The following are details that may be less important:
===========
The two SCSI devices on my system are the tape drive and a CD-RW
(Yamaha CRW6416sz), both internal. They share the same cable; the
CD-RW has termination enabled (internally), and the tape drive has
termination disabled. I believe they are connected correctly - on the
cable they share, the SCSI card is at one end, the tape drive is in
the middle, and the CD-RW is at the other end.
The SCSI IDs are 7 for the card, 0 for the tape drive, and 3 for the
CD-RW.
The drive has status leds on the front. When I boot up until I try to
access the drive, the leds indicate the drive is ready for reading and
writing; after I try to access it (using mt), the leds indicate that a
hardware fault occured, and seem to stay in this state forever (even
if I remove the tape and put it back in, or if I rmmod the SCSI tape
module (st.o) and re-insmod it.)
I've tried this on the two different DAT cartridges that came with the
drive--no difference. Also, refering to /dev/st0 instead of /dev/nst0
makes no difference in behavior.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Eckhard.Meding" <[EMAIL PROTECTED]>
Subject: Re: Binary compatibility
Date: Sun, 5 Mar 2000 00:24:26 +0100
How funny it is seeing every time coming up a us
highschool or college guy presenting questions he has to
answer for an assignment. Often there is a sharp contrast in the formulation
of the questions itself and the surrounding stuff (which is obviously from
the person itself and not from the teacher.).
;-))
Greetings
"David C." <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]...
> "Barry Kiernan" <[EMAIL PROTECTED]> writes:
> >
> > In order to appreciate the value of COM (component object model), I need
to
> > understand why it's hard to get compiled code to talk to other code. It
> > would help if somebody could explain
>
> This is the wrong newsgroup for your questions. This group is meant for
> people asking questions about how to get their hardware to work under
> Linux.
>
> Nevertheless, here's an answer for you.
>
> > 1. Linux and Windows both run on Intel x86 processors. What stops code
> > compiled on one platform from not running on the other (ie why does
> > the OS make a difference)?
>
> Back in the good ol' days of DOS and CP/M, operating systems didn't
> amount to much. They'd manage files on disks and do little else.
>
> The result was that programs had free access to the hardware. They
> could, and did, access any piece of memory and any I/O device they
> wanted to.
>
> But this practice doesn't work well under a multitasking environment.
> Your program could crash the system if it accesses a device or a piece
> of memory that some other program is trying to access at the same time.
>
> So people put more advanced resource-management facilities into
> operating systems. Under this scenario (which almost all operating
> systems use), applications can no longer directly access the hardware.
> The OS accesses the hardware on behalf of the applications. The
> applications, when they need the OS to do this access, make requests to
> the OS. These requests are made in the form of system calls.
>
> This is why apps aren't immediately compatible. Every OS has a
> different set of system calls. A program on Windows that wants to
> request 1M of memory from the OS will make one kind of system call. A
> program on UNIX or OS/2 that wants to make that same request will make a
> different kind of system call.
>
> Furthermore, the mechanism used to make system calls themselves differs
> from OS to OS, and between hardware platforms that run the "same" OS.
>
> > 2. Even on the same platform (e.g win95) the object code generated
> > from one source (C say) doesn't work with object code from another
> > source (pascal for instance). Why not?
>
> While the instruction to add two 32-bit memory locations together may be
> identical, the system calls used are completely different. Without
> system calls, a program can't do much of anything. Some of the commonly
> used calls include:
>
> - request and release memory
> - read/write files on the disk
> - read input from the keyboard and mouse
> - write output to the screen, sound card and printer
> - read/write the network
>
> etc.
>
> > 3. When you run your program, what is the extent of the interaction
> > with the OS? (eg the OS stops user programs from accessing memory
> > allocated to other processes. Does it have to vet each single machine
> > code instruction in order to do this?)
>
> Modern CPUs have hardware for this. Memory is allocatd in pages
> (typically 4K chunks on x86 processors). Each page of memory has
> various protection bits set, which the OS can modify. If an app tries
> to read or write a page that it doesn't have access to, the OS is
> alerted by the hardware (usually via an interrupt.) The OS can then
> take action - which usually means that the app is shut down, although
> other actions could also be taken.
>
> Similarly, I/O ports and some assembly instructions can also be
> protected from applications.
>
> The processor typically runs in two or more protection modes. (The x86
> processor supports four, but few operating systems use all four.) The
> main modes are kernel mode and user mode.
>
> When the processor is in kernel mode, it can do anything. It can touch
> any memory, access any I/O port, and execute any assembly instruction.
>
> When the processor is in user mode, various faults (interrupts) will be
> triggered if the program accesses memory, I/O ports or instructions that
> are protected.
>
> Hardware interrupts (say, from timers, or faults, or I/O devices) throw
> the processor into kernel mode. This way, the kernel's interrupt
> handler can take action. This typically involves a call into a device
> driver. When it is done handlingt the interrupt, it resets itself back
> to user mode before returning control to the application.
>
> Apps are protected from each other with this mechanism. When the kernel
> is entered (either via an interrupt or a system call), the kernel will
> decide which app should get the CPU next. If it decides to switch from
> the active app to another, it stores the first app's state away
> somewhere, updates the tables of which memory pages are protected, and
> loads the second app's state - then it switches to user mode and
> "returns" to the second app - which will run until a system call or
> interrupt causes a return to kernel mode.
>
> For more information, check out any good book on operating system
> design.
>
> -- David
------------------------------
From: matthew <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install
Subject: Re: Asus K7M / Redhat 6.1 64meg limitation?
Date: Sat, 4 Mar 2000 13:19:59 -0500
Try this at the boot prompt
linux mem=256
also, what kind of videocard are you using? Have you tried installing in text
mode?
On Sat, 04 Mar 2000, [EMAIL PROTECTED] wrote:
>Hi,
>
>I am using a K7M with AMD K7-700 and 256 meg of SDRAM
>running RedHat 6.1 (kernel 2.2.12-20). The BIOS detects
>all 256 meg but RedHat Linux only detects only upto 64 meg.
>Win95 on the same machine detects the correct size.
>I am using two Micron 128 Meg 8 ns PC100 SDRAMs.
>I've tried disabling SDRAM timing, rearranging the memory
>slots, slowing down the bus speed to no avail.
>Has anyone else run into similar problems?
>
>Thank you.
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
------------------------------
From: @. (^Vigil^)
Subject: Re: SB AWE 64 GOLD issues
Date: Sat, 04 Mar 2000 23:26:10 GMT
i dream of getting my awe64gold to work in linux :-(
------------------------------
From: "s barnes" <[EMAIL PROTECTED]>
Subject: Getting Geforce DDR to work
Date: Sat, 4 Mar 2000 23:29:39 -0000
Im a newbie to Linux, and I'd really like to learn more about this
potentially Windows-arsekicking software, but my nieve foolishness betrays
me, and I'd REALLY appreciate any help that you experts could impart.
When installing Linux I cant seem to get my video card to work properly. I
enter the Xconfiguration program, but it detects a 'problem with my video
memory', forcing me to configure it manually.
After choosing the relevant options (8+ RAM, Non-listed chipset, 15" Monitor
w/50-90 v-refresh, 1024X728@70Hz) It EITHER:
Presents me with a dialogue box saying 'Can you see this dialogue
box?'.......Of course I say YES, but then it loads linux in a ludicrously
low resolutions..I cant see the bottom of windows, etc!
States there was a problem probing my card OR a problem with my video
cards memory. I load into linux and, yet agin, ive got a very low res. Ive
tried setting it up completely manually, but even when I select just one
resolution from the menu, it refuses to dispay it.
Do I need drivers to let Linux access my card's SVGA abilities, or am I
doing something tragically wrong here? Ive tried loading 'Xconfigurator'
from the 'execute command' menu on right-clicking on the menu, but it does
nothing!
Ive exhausted all possible solutions as far as I can see, is there
something vital I'm missing?
Help!
------------------------------
From: "Barry Kiernan" <[EMAIL PROTECTED]>
Subject: Re: Binary compatibility
Date: Sat, 4 Mar 2000 23:48:03 -0000
Er.. not quite. As it happens, I finished studying over 5 years ago. I even
spent a year at RWTH Aachen. The questions are all my own work I regret to
say.
Cheers.
Eckhard.Meding <[EMAIL PROTECTED]> wrote in message
news:89s5nc$un3$[EMAIL PROTECTED]...
> How funny it is seeing every time coming up a us
> highschool or college guy presenting questions he has to
> answer for an assignment. Often there is a sharp contrast in the
formulation
> of the questions itself and the surrounding stuff (which is obviously from
> the person itself and not from the teacher.).
>
> ;-))
>
> Greetings
> "David C." <[EMAIL PROTECTED]> schrieb im Newsbeitrag
> news:[EMAIL PROTECTED]...
> > "Barry Kiernan" <[EMAIL PROTECTED]> writes:
> > >
> > > In order to appreciate the value of COM (component object model), I
need
> to
> > > understand why it's hard to get compiled code to talk to other code.
It
> > > would help if somebody could explain
> >
> > This is the wrong newsgroup for your questions. This group is meant for
> > people asking questions about how to get their hardware to work under
> > Linux.
> >
> > Nevertheless, here's an answer for you.
> >
> > > 1. Linux and Windows both run on Intel x86 processors. What stops code
> > > compiled on one platform from not running on the other (ie why does
> > > the OS make a difference)?
> >
> > Back in the good ol' days of DOS and CP/M, operating systems didn't
> > amount to much. They'd manage files on disks and do little else.
> >
> > The result was that programs had free access to the hardware. They
> > could, and did, access any piece of memory and any I/O device they
> > wanted to.
> >
> > But this practice doesn't work well under a multitasking environment.
> > Your program could crash the system if it accesses a device or a piece
> > of memory that some other program is trying to access at the same time.
> >
> > So people put more advanced resource-management facilities into
> > operating systems. Under this scenario (which almost all operating
> > systems use), applications can no longer directly access the hardware.
> > The OS accesses the hardware on behalf of the applications. The
> > applications, when they need the OS to do this access, make requests to
> > the OS. These requests are made in the form of system calls.
> >
> > This is why apps aren't immediately compatible. Every OS has a
> > different set of system calls. A program on Windows that wants to
> > request 1M of memory from the OS will make one kind of system call. A
> > program on UNIX or OS/2 that wants to make that same request will make a
> > different kind of system call.
> >
> > Furthermore, the mechanism used to make system calls themselves differs
> > from OS to OS, and between hardware platforms that run the "same" OS.
> >
> > > 2. Even on the same platform (e.g win95) the object code generated
> > > from one source (C say) doesn't work with object code from another
> > > source (pascal for instance). Why not?
> >
> > While the instruction to add two 32-bit memory locations together may be
> > identical, the system calls used are completely different. Without
> > system calls, a program can't do much of anything. Some of the commonly
> > used calls include:
> >
> > - request and release memory
> > - read/write files on the disk
> > - read input from the keyboard and mouse
> > - write output to the screen, sound card and printer
> > - read/write the network
> >
> > etc.
> >
> > > 3. When you run your program, what is the extent of the interaction
> > > with the OS? (eg the OS stops user programs from accessing memory
> > > allocated to other processes. Does it have to vet each single machine
> > > code instruction in order to do this?)
> >
> > Modern CPUs have hardware for this. Memory is allocatd in pages
> > (typically 4K chunks on x86 processors). Each page of memory has
> > various protection bits set, which the OS can modify. If an app tries
> > to read or write a page that it doesn't have access to, the OS is
> > alerted by the hardware (usually via an interrupt.) The OS can then
> > take action - which usually means that the app is shut down, although
> > other actions could also be taken.
> >
> > Similarly, I/O ports and some assembly instructions can also be
> > protected from applications.
> >
> > The processor typically runs in two or more protection modes. (The x86
> > processor supports four, but few operating systems use all four.) The
> > main modes are kernel mode and user mode.
> >
> > When the processor is in kernel mode, it can do anything. It can touch
> > any memory, access any I/O port, and execute any assembly instruction.
> >
> > When the processor is in user mode, various faults (interrupts) will be
> > triggered if the program accesses memory, I/O ports or instructions that
> > are protected.
> >
> > Hardware interrupts (say, from timers, or faults, or I/O devices) throw
> > the processor into kernel mode. This way, the kernel's interrupt
> > handler can take action. This typically involves a call into a device
> > driver. When it is done handlingt the interrupt, it resets itself back
> > to user mode before returning control to the application.
> >
> > Apps are protected from each other with this mechanism. When the kernel
> > is entered (either via an interrupt or a system call), the kernel will
> > decide which app should get the CPU next. If it decides to switch from
> > the active app to another, it stores the first app's state away
> > somewhere, updates the tables of which memory pages are protected, and
> > loads the second app's state - then it switches to user mode and
> > "returns" to the second app - which will run until a system call or
> > interrupt causes a return to kernel mode.
> >
> > For more information, check out any good book on operating system
> > design.
> >
> > -- David
>
>
------------------------------
** 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
******************************
