Linux-Hardware Digest #967, Volume #13 Fri, 1 Dec 00 09:13:09 EST
Contents:
V90 PCI Modem Recommendation Please ("PC Wizard")
Source Code: ([EMAIL PROTECTED])
Re: I want to watch tv on my linux machine (Harri Haataja)
Pb with Tekram DC-395UW ([EMAIL PROTECTED])
Re: scsi-DAT timeout & hangs ("D. Stimits")
MSI 694D Board .. any good? (Sascha Bohnenkamp)
Re: Backup Hard Drive... (Volker Apelt)
Aureal Vortex 2 and mysterious lock-ups ("Adam Short")
Re: hdparm -I output ("Guennadi V. Liakhovetski")
Configuring a cd-rw (Doddy)
Anyone had any experiance with ga-6vxdc7 ? ([EMAIL PROTECTED])
Re: USB and IrDA Development on Linux (ich)
I am confident you will help me with "LI" from LILO; I'm one answer away from the
Linux promised land ("Dan Jacobson")
Re: "lp0 on fire" (Lew Pitcher)
ASUS V7700 pro pure ... any problems? (Sascha Bohnenkamp)
----------------------------------------------------------------------------
Reply-To: "PC Wizard" <[EMAIL PROTECTED]>
From: "PC Wizard" <[EMAIL PROTECTED]>
Subject: V90 PCI Modem Recommendation Please
Date: Fri, 1 Dec 2000 02:22:05 -0700
I would like a recommendation for an internal pci v.90 56k modem. It also
needs drivers for Windows 98SE, Windows 2000, and Redhat Linux 6.2 (or know
where I could get them).
Thanks,
Keith
------------------------------
From: [EMAIL PROTECTED]
Subject: Source Code:
Date: Fri, 01 Dec 2000 10:01:27 GMT
Here's the relevant code (manual copy):
#!/usr/in/perl
@VendorID = ();
@DeviceID = ();
$PciFile = '/proc/pci';
# $PciFle = 'bobo.txt';
$InstallDir = '.';
$InstallFilesExt = 'inf';
open (PCI, "$PciFile") or
die "Can't open '$PciFile' file: $!\n";
while (<PCI>)
{
next unless /^\s*Vendor\s*id\s*=\s*(.{4}).+Dvice\s*id\s*=\s*(.
{4}).*$/io;
$Id{uc $1} = uc $2;
# push(@VendorID, uc $1);
# push(@DeviceID, uc $2);
}
close(PCI);
opendir(DIR, "$InstallDir") or
die "Can't open '$InstallDir' directory: $!\n";
@Files = grep(/\.$InstallFilesExt$/io, readdir(DIR));
close(DIR);
my $inf_file_found = 0, $inf2bin_ret = 0;
SEARCH_INF_FILES:
for my $file (@Files)
{
open (INSTALLFILE, "$file") or
die "Can't open '$file' file: $!\n";
while (<INSTALLFILE>)
{
next unless /^.*PCI\\VEN_(.{4}&DEV_(.{4})(&SUBSYS_.
{8})?/o;
if (defined $Id{c $1})
{
if (uc $2 eq $Id{uc $1})
{
print "Matching INF file is '$file'\n";
&InstallModem($file, $1, $2);
$inf_file_found = 1;
last SEARCH_INF_FILES;
}
}
}
close(INSTALLFILE);
}
if ( 1 == $inf_file_found )
{
print "INF file processing finished ok.\n";
}
print "No matching INF file found!!!\n";
exit -1;
...(more code here)
NOTE... it IS finding: lin_hsf.inf in @Files
it IS iterating: While (<INSTALLFILE>)
it DOES access: if (defined $Id{c $1}) 3 times
By removing the comments I get:
Vendor Id's: 104C 104C 1013 127A 1002
Device ID's: AC1C AC1C 6005 2013 4C42
%Id{uc }
... then it accesses the if (defined.... etc.) 3 times
No matching INF file found!!!
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Harri Haataja)
Subject: Re: I want to watch tv on my linux machine
Date: Fri, 01 Dec 2000 10:51:53 GMT
>Lou wrote:
>>
>> I am new to linux, and I can't get my tv software to work properly. I
>> launch xawtv or kwintv and I don't get any channels. I've tried all the
>> options, pal, ntsc, and the different countries broadcasts, and still no
>> channels. I've tried the bttv how-to and still no luck. can someone
>> please help me. if I can fix this, then I never have to use windows.
I can't even get xawtv to start. Can't open /dev/video (yes, exists).
I have an ASUS v3400 with tv-in and the Philips SAA7111 chip on the board
got me trying. I've loaded the module but I guess it's not working.
Anyone with similiar experience (and hopefully a cure)?
------------------------------
From: [EMAIL PROTECTED]
Subject: Pb with Tekram DC-395UW
Date: Fri, 01 Dec 2000 11:04:50 GMT
Hello
I got pb with my new SCSI DD.
The most frequently message is:
SCSI0 channel0: resetting for second half of retries
SCSI bus is being reset for host 0 shannel 0
SCSI disk error: host0 chan.0 id0 lun0 return code
= 18000002
[valid=0] Info fld=0x0, Current sd 08:02: sense
key aborted command
scsi I/O error: dev 08:02, sector XXXXXX
This message appears lot of times during 1-2
minutes with cdrom access (when bus is resetted)
when I begin session. Sometimes this crash the
system, sometimes I could continue with no more
problems.
Under win; no porblem...
my hardware is:
P166MMX 96Mo SDRAM hda 2,5Go
DD Fujitsu 9Go M2949Q ID 0
CDROM Plextor PX40TS ID 3
my system is debian2.2 but the problem is the same
with Suse 6.4.
Do you know this problem or could you explain me
what mean these message?
Thanks
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: Fri, 01 Dec 2000 04:44:10 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: scsi-DAT timeout & hangs
Risto K Virtanen wrote:
>
> Thanks for the advice. I checked the docs & the drive, there were 10 dips,
> and no. 10 was the Inquiry setting, which was OFF. Changing it to ON didn't
> help, though:( I'm still getting the same error messages in boot, and
> reading process is hanged.
>
> The controller is in fact Adaptec AIC-7899 Ultra 160/m SCSI host adapter:
> scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.28/3.2.4
> <Adaptec AIC-7899 Ultra 160/m SCSI host adapter>
>
> Browsing the older meassages once again I noticed a discussion about
> APIC/NOAPIC. What is this? Could this have something to do with the problem?
If it runs on a motherboard with the i840 chipset, then it is not just
possible, but probable cause. Other chipsets usually run fine, such as
the BX which is quite solid. On the i840, rapid mounting and umount of
even a CDROM will cause failure; other times high i/o load. You can
disable the IO-APIC at the LILO prompt during boot...when you get the
LILO prompt, and hit the tab key to see the available images (assume
your favorite image is 2.2.15smp, just for argument's sake), enter:
2.2.15smp noapic
If it turns out you need noapic, this will save much grief (not all,
most though), at the cost of losing responsiveness (without the IO-APIC
only one cpu can handle hardware interrupts). FYI, the aic7xxx on
Ultra160 is extremely stable.
>
> Thanks,
>
> Risto K Virtanen
> [EMAIL PROTECTED]
>
> William Arnold wrote:
>
> > This particular drive is designed to work intwo modes, one which you are
> > in now. On the drive is a set of dip switches labeled S1 through S8,
> > some models offer S9 and S10 also. Look at S7 and change it to ON this
> > puts the drive in Seagate inquiry mode. The Archive inquiry provides
> > compatibility with older archive software. Check the product manual for
> > additional info you can get it from Seagate if you don't have it. I have
> > the same drive and run mine in the Seagate inquiry mode with no
> > problems.
------------------------------
From: Sascha Bohnenkamp <[EMAIL PROTECTED]>
Subject: MSI 694D Board .. any good?
Date: Fri, 01 Dec 2000 12:51:04 +0100
Hello
is the MSI 694D pro Board any good?
especially with 2x850 MHz P3 and 2GB ram?
------------------------------
From: [EMAIL PROTECTED] (Volker Apelt)
Crossposted-To: comp.os.linux.misc
Subject: Re: Backup Hard Drive...
Date: 1 Dec 2000 12:56:45 +0200
Jeffrey Hood <[EMAIL PROTECTED]> wrote:
[ he wants to backup or clone his PC to a second hard drive
because serious tape backup solutions are to expensive
for his environment.
]
You know that backup is more than just having a second
copy of everything? good backup software maintains an
archive, too.
The linux solution to GHOST is dd.
# copy entire harddisk from scsi drive 1 to scsi drive 2
# (a hard copy, including partitions ... )
dd if=/dev/sda of=/dev/sdb
see 'man dd'
--
Volker Apelt Group of Prof. Dr. Ch. Griesinger
Johann Wolfgang Goethe Universitaet
Frankfurt am Main (Germany)
no_spam_va|org.chemie.uni-frankfurt.de (use va@ instead of ...| )
------------------------------
From: "Adam Short" <[EMAIL PROTECTED]>
Subject: Aureal Vortex 2 and mysterious lock-ups
Date: Fri, 01 Dec 2000 12:01:05 GMT
I have a Vortex 2 sound card which I am generally very happy with. However,
in Linux I think it may be the cause of some unusual phenomena. I used the
drivers from sourceforge to install it and it works perfectly as far as I
can tell. When I use xmms to play mp3s it all goes a little pear shaped. I
posted on comp.os.linux that I had problems with xmms and some kind soul
told me that I needed to update glibc to the newest version. I did this and
everything went swimmingly for about 30 minutes. Glibc seems to have fixed a
couple of other niggles I had but not the xmms problem. What happens is
this: I put an mp3 track on (usually from a cd), it plays quite happily for
a while, then suddenly locks up completely without warning. There is nothing
wrong with the sound quality and I'm running an almost virgin install of
Mandrake 7.1 (the one that came with PC Plus a while back). I am going
through the list of things that could possibly be wrong, now that I have
ruled out glibc as the culprit, I am turning my attention to the sound
drivers. I know these are a tad flaky and other users have had a lot of
problems with them so I thought I'd ask if this could be the cause of my
trouble.
Anyone know?
My system is an AMD Athlon Tbird 800, ABIT KT7 RAID MB, 128MB PC100 RAM,
20gig Western Digital Caviar HD (partitioned into a 10gig win98 partition, a
/home (~ 9gig), a / (~1 gig) and a swap (128MB)), ATI Xpert 2000 32MB,
Aureal Vortex 2 and I think the rest is likely to be unimportant. The Linux
I am using is Linux Mandrake 7.1 (from PC Plus coverdisk), the only thing I
have changed from a basic install is the sound drivers (au88030), glibc (to
2.2) and my isapnp.conf (to support an ISA PNP modem)
Thanks in advance
Adam
------------------------------
From: "Guennadi V. Liakhovetski" <[EMAIL PROTECTED]>
Subject: Re: hdparm -I output
Date: Fri, 1 Dec 2000 11:56:59 +0000
Thanks again
Ok, so, if
> hdparm gets its info directly from the drive itself.
how do we interpret the following combination:
> >>> DMA=yes, maxDMA=0(slow)
> >>> DMA modes: mword0 mword1 *mword2
and
> >hdparm -d1 produces an error:
> >/dev/hda:
> > setting using_dma to 1 (on)
> > HDIO_SET_DMA failed: Operation not permitted
> > using_dma = 0 (off)
??? The question is - which parts do and which don't support DMA? Where is
hdparm's -d1 attempt stopped? Can compiling hdparm with -g and running it
in a debugger help? To see what function produces this error
> If the drive
> supports DMA
not sure, but I think so - as I told before, Western Digital's docs are
contradictory. If you compare WD's documents at:
http://www.westerndigital.com/service/FAQ/dtr.html
and
http://www.westerndigital.com/products/non-current/drives/ac21600.html
they, respectively ,say:
UDMA if CCC is A8-AG (AH is not UDMA), D5-D7, Bx, or Cx All others -- PIO
Mode 4
and
16.6 MB/s (burst Mode 4 PIO) *
16.6 MB/s (burst Mode 2 DMA) **
33.3 MB/s (Mode 2 Ultra DMA) ***
*Max PIO burst rate is specified at 16.6 MB/s using the IORDY signal.
**Max DMA and multi-word DMA burst rate is specified using the DMARQ and
DMACK signals.
***Mode 2 Ultra DMA is supported in the following firmware revisions (CCC
Codes: A8, AA, AC, AD, AG, D5, D6, D7, Bx, Cx).
Which one is true? Do non-UDMA AC21600H (I've got CCC F6) support DMA? And
what about those DMARQ and DMACK signals?
> and the kernel doesn't have support for the DAM
> capabilities of your IDE chipset, forget setting hdparm -d1.
I've done everything I could think of (including ide-patch) to enable PIIX
in the kernel.
> Don't know for sure, but you may be running into a CPU bottleneck. IDE
> is fairly CPU-intensive compared to SCSI, and a P-75 can get bogged down
> trying to shovel data. If your PCI bus doesn't go at 33MHz, that's
> another problem, since the PCI bus is always supposed to be at 33MHz.
> Have you tried enabling the IDE ports in the BIOS?
Everything looks fine in BIOS, although I didn't change anything in
default settings. There isn't much to play with. BIOS well may not support
DMA, but is it a problem? ide.txt says Linux is not using BIOS to work
with hard disks...
> Might make a
> difference. FWIW, -m16 -u1 -c1 helps a lot even if you can't get DMA
> going.
Already. This improved performance by ~60% (was 2.9 became 4.8).
> Heck, when I enabled DMA with hdparm -d1 on my system, it didn't
> make any difference to HD throughput. Hedrick's IDE patch made it
> impossible to use -d1, but the boot messages said "(U)DMA timing config
> success" and throughput rose anyway.
I applied the patch too. It added couple lines to dmesg, but none of them
is optimistic... I am not getting the above message:-(
I don't know what's going on there...
Thanks
Guennadi
___
Dr. Guennadi V. Liakhovetski
Department of Applied Mathematics
University of Sheffield, U.K.
email: [EMAIL PROTECTED]
------------------------------
From: Doddy <[EMAIL PROTECTED]>
Subject: Configuring a cd-rw
Date: Fri, 01 Dec 2000 12:30:03 -0000
I have just installed SuSe v7, but it hasn't recognised my cd-roms.
I have managed to install my standard cd-rom drive which is primary on the
second channel.
However I'm still having trouble with the CD-RW drive.
Can anyone help with instructions please, on installing and then using it
productively
Thanks
doddy
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED]
Subject: Anyone had any experiance with ga-6vxdc7 ?
Date: Fri, 01 Dec 2000 12:40:28 GMT
Hi All,
I'm building a new system for my Linux box, and want to know if anyone
has used Gigabyte's GA-6XVDC7.
Alternatively, what other boards are Linux tested for SMP with an AGP
slot?
Thanks in advance,
Colin.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: ich <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.help,comp.os.linux.misc,comp.os.linux.questions
Subject: Re: USB and IrDA Development on Linux
Date: Fri, 01 Dec 2000 13:50:31 +0100
Hi Alan,
How about
http://irda.sourceforge.net/
or
http://www.lirc.org/index.html
[EMAIL PROTECTED]
Alan Po wrote:
> Dear All
>
> I am trying to develop an application by using a USB IrDA. I have found some
> information about USB development under Linux. Unluckily, I cannot find the
> information of IrDA on Linux.
>
> Would you give me some ideas, advices or resources to help me to solve my
> problem?
>
> Alan PO
>
> [EMAIL PROTECTED]
------------------------------
From: "Dan Jacobson" <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux.mandrake,comp.os.linux.setup,comp.sys.ibm.pc.hardware.storage
Subject: I am confident you will help me with "LI" from LILO; I'm one answer away from
the Linux promised land
Date: Fri, 1 Dec 2000 21:13:31 +0800
Dear sirs, I am able to boot Mandrake 7.2 by floppy, however from hard
disk I am stuck at lilo's "LI", which I use as it is better documented
than grub (stuck too). I have windows on hda and boot linux on
hdb. Apparantly hdb's geometry is not properly autodetected in BIOS. I
suppose the strategy is to enter the manufacturer's specs into BIOS
and lilo.conf rather than put wrong info found in BIOS into
lilo.conf. Below are excerpts.
# dmesg
Linux version 2.2.17-21mdk Thu Oct 5 13:16:08 CEST 2000
SiS5597
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
hdb: QUANTUM FIREBALLlct15 30, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdb: QUANTUM FIREBALLlct15 30, 28629MB w/418kB Cache, CHS=58168/16/63, UDMA(33)
***58168/16/63 aparantly has the number of cylenders upped to
agree with the true size instead of the artificially low 16383 specified by
Quantum. I wonder how the kernal gets this number.
Partition check:
hdb: [PTBL] [8191/32/63] hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 >
***is the wrong 8191/32/63 now imprinted into my kernal from what the
bios said that day I installed mandrake? Shall I worry
about this even though I can boot by floppy?
Shall I reinstall mandrake after manually editing bios cmos settings?
If I say yes to LBA in my bios it forces heads=255.
Would just using "normal" instead of "lba" be ok when configuring
bios?
my bios:
BIOS Date: 01/22/98
BIOS Type: Award Modular BIOS v4.51PG
BIOS ID: 01/22/98-SiS-5598-<SP97_V>C-00
# hdparm -g /dev/hdb
geometry = 8191/32/63, sectors = 58633344, start = 0
***ok, these incorrect values are spread far and wide
in my computer, but i thought it doesn't matter at least to linux...
# hdparm -i /dev/hdb
Model=QUANTUM FIREBALLlct15 30, FwRev=A01.0F00, SerialNo=614019446573
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
BuffType=DualPortCache, BuffSize=418kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=58633344
***yes, 16383/16/63 is what the quantum docs say
I assume the number of cylinders are delibrately kept below a barrier.
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
# hdparm -I /dev/hdb
RawCHS=16/21298/0, TrkSize=63, SectSize=0, ECCbytes=12590
(maybe): CurCHS=63/64528/251, CurSects=-1400897264, LBA=yes, LBAsects=458752
***could these two rawly reported lines give me a clue as to how hdb actually
talks to my computer?
# fdisk -l /dev/hdb
Disk /dev/hdb: 32 heads, 63 sectors, 29084 cylinders
Units = cylinders of 2016 * 512 bytes
****again, wrong values branded into place...
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 507 511024+ 83 Linux
***well, one puts /boot on a low cylinder
I assume lilo doesn't need to read "/" to know where /boot is.
/dev/hdb2 508 11194 10772496 5 Extended
/dev/hdb5 508 760 254992+ 82 Linux swap
/dev/hdb6 761 1774 1022080+ 83 Linux
/dev/hdb7 1775 5837 4095472+ 83 Linux
/dev/hdb8 5838 9222 3412048+ 83 Linux
/dev/hdb9 9223 10236 1022080+ 83 Linux
/dev/hdb10 10237 11194 965632+ 83 Linux
# cat /etc/lilo.conf
boot=/dev/hdb
map=/boot/map
install=/boot/boot.b
vga=normal
default=linux
keytable=/boot/us.klt
#lba32
#linear
prompt
timeout=150
message=/boot/message
menu-scheme=wb:bw:wb:bw
# get the numbers from your drive's docs:
disk=/dev/hdb
# bios=0x81
sectors=63
heads=16
cylinders=16383
image=/boot/vmlinuz
label=linux
root=/dev/hdb6
initrd=/boot/initrd.img
append=" hdc=ide-scsi"
# append=" hdc=ide-scsi hd=16383,16,63" ***i have a lilo problem
not a kernal problem, so no need to pass this line?
read-only
# lilo -v -v -v
Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
63 sectors. Partition offset: 63 sectors.
Secondary loader: 11 sectors.
Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
63 sectors. Partition offset: 63 sectors.
Mapping message file /boot/message
Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
63 sectors. Partition offset: 63 sectors.
Message: 1 sector.
Boot image: /boot/vmlinuz
Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
63 sectors. Partition offset: 63 sectors.
Setup length is 7 sectors.
Mapped 1301 sectors.
Mapping RAM disk /boot/initrd.img
Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
63 sectors. Partition offset: 63 sectors.
RAM disk: 748 sectors.
Added linux *
<dev=0x81,hd=2,cyl=3,sct=46>
"ro root=346 hdc=ide-scsi"
Boot image: /boot/vmlinuz
Device 0x0341: BIOS drive 0x81, 16 heads, 16383 cylinders,
63 sectors. Partition offset: 63 sectors.
Setup length is 7 sectors.
Mapped 1301 sectors.
By the way, to those who plan to tinker,
http://einstein.et.tudelft.nl/~robn/linux-docs/chs-translation-how-it-works
though dated, says:
"Read this so that you understand the possible data integrity
problem that a WD EIDE type BIOS creates. Any BIOS that has a
"LBA mode" in the BIOS setup could be a WD EIDE BIOS. Be very
careful and NEVER chage the "LBA mode" setting after you have
partitioned and installed your software."
--
www.geocities.com/jidanni E-mail: restore ".com." �n����
Tel:+886-4-5854780; starting in year 2001: +886-4-25854780
------------------------------
From: [EMAIL PROTECTED] (Lew Pitcher)
Subject: Re: "lp0 on fire"
Reply-To: [EMAIL PROTECTED]
Date: Fri, 01 Dec 2000 13:28:01 GMT
On Thu, 30 Nov 2000 14:39:00 -0500, Carter Brey <[EMAIL PROTECTED]>
wrote:
>Hello--
>
>I run the RH 7 distro on a Dell Inspiron 7500 attached to an Epson
>Stylus Color 640 printer, and the system usually works happily.
>Unfortunately, once in a great while /dev/lp0 gets into a funk and
>blocks up. Running "tail -f /var/log/messages" shows the message "lp0 on
>fire". Nothing I do can free it up. I've tried various lpc commands
>(down, up, kill, abort) and tried "tunelp /dev/lp0," but this merely
>returns the message "device or resource busy". Back when I had a Windows
>partition, I could reboot into Windows, print something, then boot back
>into Linux, and it would be fine. I've recently removed my Windows
>partition and no longer have this option.
>
>Any suggestions would be most gratefully accepted.
"lp0 on fire" is a driver-generated message, and it indicates that the
printer returned a status that indicates a serious hardware problem
exists. Sometimes the status lies, but the driver has no choice but to
believe it.
Since the driver thinks that the printer is dead, any programs using
the driver (i.e. anything with /dev/lp0 open) may now be hung in an IO
wait state, and can't be killed until the hardware problem is fixed.
You _might_ be able to force-unload/reload the parallel-port module(s)
to free up the stuck processes, but the better bet is to fix your
printer, and clear the 'on fire' condition that way.
Lew Pitcher
Information Technology Consultant
Toronto Dominion Bank Financial Group
([EMAIL PROTECTED])
(Opinions expressed are my own, not my employer's.)
------------------------------
From: Sascha Bohnenkamp <[EMAIL PROTECTED]>
Subject: ASUS V7700 pro pure ... any problems?
Date: Fri, 01 Dec 2000 14:37:32 +0100
------------------------------
** 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
******************************
