Linux-Hardware Digest #482, Volume #13 Sat, 26 Aug 00 19:13:08 EDT
Contents:
New kernel, Promise 66 PCI, and 2 3c509's (Sean LeBlanc)
Re: d-link problem!!!! help (Kris)
Re: New kernel, Promise 66 PCI, and 2 3c509's (Dances With Crows)
Re: Which ISDN modem do I get? (Dave Lawton)
Warning-Best Buy/Hayes H08-03357 (Rob Clark)
Re: CUECAT-- Spyware? (Matthew J Zukowski)
Re: CUECAT for Linux (Matthew J Zukowski)
Re: New kernel, Promise 66 PCI, and 2 3c509's (Sean LeBlanc)
Re: increase microphone volume (Colin Watson)
Re: New kernel, Promise 66 PCI, and 2 3c509's (Dances With Crows)
how to use SCSI utilities? (Peter Bismuti)
Re: Netgear FA311 ethernet card Not working (A E Lawrence)
Re: Netgear FA311 ethernet card Not working (A E Lawrence)
ethernet - device not found (Peter Bismuti)
----------------------------------------------------------------------------
Subject: New kernel, Promise 66 PCI, and 2 3c509's
From: Sean LeBlanc <[EMAIL PROTECTED]>
Date: Sat, 26 Aug 2000 18:21:00 GMT
I've recently acquired a promise 66 PCI, and hard
drive to go with it.
I was running RedHat 6.1, and I just want to ADD this
hard drive as another partition(s)...so I got kernel
2.2.16, the ide patches for it, and compiled. Then,
I installed new kernel (in addition to old one) and
reboot. So far, so good. I see during boot that
the hard drive dangling off of the the card, and I
can run fdisk /dev/hde, and that works fine. I never
actually formatted it yet, because of a little ol'
problem:
The problem is that during boot, I also see that eth1
fails. eth0 comes up fine. I've gone through several
gyrations where I try moving the Promise PCI card,
the ISA 3c509's around, I even tried changing (via
3Com's DOS utility) the IRQ and base IO of the
troublesome card...but eth1 still fails on boot WITH
THE NEW KERNEL ONLY. If I go back to the old kernel,
network card interfaces both start...with PCI card
and new hard drive still in there. eth1 works, though
I am at a loss at what I should do here...I assume
there is some kind of conflict, but I don't know where
to configure it or prove that hypothesis. Any and all
troubleshooting help is welcome!
Here is what I have in conf.modules for the cards:
alias eth0 3c509
alias eth0 3c509
This has always worked, and still does if I go back
to old kernel...but of course, with old kernel, I
can't use Promise PCI.
On a side note, is there a way to give LILO options to
see a different System.map? I had to ln -s to point to
the new System.map, but that's not desirable if you are
switching kernels a lot....
TIA,
Sean LeBlanc
------------------------------
From: Kris <[EMAIL PROTECTED]>
Subject: Re: d-link problem!!!! help
Date: Sat, 26 Aug 2000 19:50:28 +0100
Jim Broughton writes:
> You need the rtl8139 driver.
>
> place this line in your conf.modules file.
>
> eth0 alias rtl8139
>
> If slackware defaults to a completely modular system then this
> module should be available to you.
Are you sure about that? My DFE-530TX uses the via-rhine driver... It
rings a bell that the TX+ uses rtl8139, but I'm sure that the TX uses
via-rhine.
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: New kernel, Promise 66 PCI, and 2 3c509's
Date: 26 Aug 2000 19:11:32 GMT
Reply-To: [EMAIL PROTECTED]
On Sat, 26 Aug 2000 18:21:00 GMT, Sean LeBlanc wrote:
>The problem is that during boot, I also see that eth1 fails. eth0 comes
>up fine. I've gone through several gyrations where I try moving the
>Promise PCI card, the ISA 3c509's around, I even tried changing (via
>3Com's DOS utility) the IRQ and base IO of the troublesome card...but
>eth1 still fails on boot WITH THE NEW KERNEL ONLY. If I go back to the
>old kernel, network card interfaces both start...with PCI card and new
>hard drive still in there. eth1 works, though
>
>I am at a loss at what I should do here...I assume there is some kind
>of conflict, but I don't know where to configure it or prove that
>hypothesis. Any and all troubleshooting help is welcome!
>
>Here is what I have in conf.modules for the cards:
>alias eth0 3c509
>alias eth0 3c509
>This has always worked, and still does if I go back to old kernel...but
>of course, with old kernel, I can't use Promise PCI.
ITYM "alias eth0 3c509 alias eth1 3c509". And where is the "options
3c509 irq=X,Y" line? If you think there's an IRQ or I/O port conflict,
you can get a look at the kernel's map of the IRQs and I/O ports with
"cat /proc/ioports && cat /proc/interrupts". Generally, the 3c509
module requires the IRQ of the card, so it can probe for the I/O ports
effectively, as the autoprobing doesn't always work. What do you get if
you "rmmod 3c509" and then "insmod 3c509 irq=X,Y" where X and Y are the
IRQs your cards are set to?
2.2.16 was kind of rushed out the door IMO; I haven't been able to get
it to work with parport ZIP drives while 2.2.12--2.2.15 all worked just
fine.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Those who do not understand Unix are
http://www.brainbench.com / condemned to reinvent it, poorly.
=============================/ ==Henry Spencer
------------------------------
From: Dave Lawton <[EMAIL PROTECTED]>
Subject: Re: Which ISDN modem do I get?
Date: Sat, 26 Aug 2000 17:06:13 +0100
Reply-To: Dave Lawton <[EMAIL PROTECTED]>
In article <8o3d92$95c$[EMAIL PROTECTED]>, Morten Skaarup Jensen
<URL:mailto:[EMAIL PROTECTED]> wrote:
> Sorry for this question, but I'm stuck trying to find out what ISDN modem to
> get. I'm just trying to find out in general what I should be looking for.
>
> I'd like an internal modem (I have enough loose wires around), but of course
> only if it works well with Linux. Are ISDN modems like analog modems in that
> internal ones usually don't work? Are some faster than others on a 64k line?
>
Some, and as far as I know, no.
> I'll be grateful for any help I can get.
>
> Morten
>
> (Running SuSE 6.4, Linux 2.2.14)
>
>
Using the distribution as you, I use a DLink DMI-128I (128K PCI),
works great.
--
To reply, please click here > <[EMAIL PROTECTED]>
------------------------------
Subject: Warning-Best Buy/Hayes H08-03357
From: [EMAIL PROTECTED] (Rob Clark)
Date: Sat, 26 Aug 2000 20:09:08 GMT
This is a warning for people shopping for a PCI modem for Linux.
Best Buy is selling the Hayes H08-03357 with "Linux compatible"
on the shelf label.
** THIS LABEL IS MISLEADING! **
H08-03357 is a Lucent LT WinModem. It will work with Linux, but only
with the Lucent "Linmodem" driver for your particular kernel version.
It has a DSP, but it is host-controlled, just like a 3Com Winmodem.
A better choice at Best Buy would be the Actiontec PCI56012-01CW (Lucent
Venus hardware modem) for $20 more.
I am currently updating the "ROUGH GUIDE" for Best Buy and Circuit City
at http://www.o2.net/~gromitkc/rg/
This particular modem was sold out, and I hope it had nothing to do with
the labeling at the store :(
Rob Clark, [EMAIL PROTECTED]
http://start.at/modem <-- Linux/modem compatibility list
------------------------------
From: Matthew J Zukowski <[EMAIL PROTECTED]>
Subject: Re: CUECAT-- Spyware?
Date: 26 Aug 2000 20:46:00 GMT
I totally agree. In the same cord as the safeway club card, this company
does gain access to your buying habbits. And as a result can custom
advertising based on things they know you want in order to maximixe
emotional manipluation. But like the safeway club card, there are ways to
make sure that your buying habbits actually don't windup in the wrong
hands.
Even worse yet, but they didn't seem to think to actually use one of the
existing databases on the subject of bar-codes, but rather allow the
masses to compile them for them. Rather sneeky I'd say. Smart, but
sneekie.
If they had a database of stuff the approperate size, then it might even
be worth considering using their service.
The only positive affect I can see from this commercial venture is putting
barcodes back into the spotlight, so perhaps companies will actually use
them the way they were designed, to identify products. Who makes that
motherboard for example.
But at present, the only people interested in the above device are
hackers, who will actually make practical what this company as decided to
offer as a premium to find out that people like my self prefer
"JOLT" (tm).
But at present, I know of only one major public database for the public
archival of barcodes, and that's http://grover.mta.ca/upc.
Valentin Guillen <[EMAIL PROTECTED]> wrote: : Am I the only
one here who thinks that this is but another example of : "stealth"
spyware?
: Anyone know of what kind of hidden port activity this "cute" little
: program generates, and who it reports to, and what it reports?
: Any and all comments would be appreciated.
: Valentin Guillen
------------------------------
From: Matthew J Zukowski <[EMAIL PROTECTED]>
Subject: Re: CUECAT for Linux
Date: 26 Aug 2000 20:48:15 GMT
Martin Warnett <[EMAIL PROTECTED]> wrote:
: Matthew J Zukowski wrote:
:> Actually I was thinking that it still would be pretty cool to do an
:> inventory of your stuff, despite the fact that it's input is
:> encrypted. It's readings are pretty consistent, and if someone out there
:> were to write lets say a spread function to decrypt the data it would
:> prove to be most useful. The fact that it operates on the standard AT
:> keyboard interface makes the hardware intergration much easier.
:>
:>
:>
:> Personaly I think I would prefer an independent project behind this
:> venture, or at-least independent software. It's a useful enough idea that
:> I'm sure companies would pay good money to advertise on such a bar-code to
:> product database.
:>
: Checkout Readerware, I just added support for the :CueCat. It is a book
: cataloging program. Scan in a bar code, Readerware extracts the ISBN, goes out
: on the net searches for the book, extracts the data, including images, and
: builds a local database.
: http://www.readerware.com
Actually I can't get the package to run. Claims can't find files to copy,
or somthing to that effect. Will try the Linux edition before talking to
techsupport (ick!). I suspect a problem with me running Windows ME, and
no one else having a copy to take into account it's diffrences.
------------------------------
Subject: Re: New kernel, Promise 66 PCI, and 2 3c509's
From: Sean LeBlanc <[EMAIL PROTECTED]>
Date: Sat, 26 Aug 2000 20:58:17 GMT
Wow. Thanks for the quick response. I tried rmmod 3c509, but that didn't
find the module - turns out I compiled 3c509 support into kernel, not
as a module. Could that be a problem?
I tried making my conf.modules line look like this:
alias eth0 3c509
alias eth1 3c509
options 3c509 io=0x210,0x310 irq=5,3
For the new kernel, this has the same result as if I left it like
it was before (eth0 works, and it takes irq 5, base addr 210, eth1
fails)
When I do cat /proc/ioports and cat /proc/interrupts, for the
new kernel, I see no entry at all for IRQ 3 or base addr 310.
Interestingly, when I left conf.modules like it is shown above,
and boot into old kernel, NEITHER interface comes up, and ioports
and interrupts show no entries for IRQ 3,5 or base 310,210, so
for old kernel to work, I changed it back to this:
alias eth0 3c509
alias eth0 3c509 and commented out the option 3c509 line...
Any more suggestions? I really appreciated your response, BTW.
[EMAIL PROTECTED] (Dances With Crows) writes:
> On Sat, 26 Aug 2000 18:21:00 GMT, Sean LeBlanc wrote:
> >The problem is that during boot, I also see that eth1 fails. eth0 comes
> >up fine. I've gone through several gyrations where I try moving the
> >Promise PCI card, the ISA 3c509's around, I even tried changing (via
> >3Com's DOS utility) the IRQ and base IO of the troublesome card...but
> >eth1 still fails on boot WITH THE NEW KERNEL ONLY. If I go back to the
> >old kernel, network card interfaces both start...with PCI card and new
> >hard drive still in there. eth1 works, though
> >
> >I am at a loss at what I should do here...I assume there is some kind
> >of conflict, but I don't know where to configure it or prove that
> >hypothesis. Any and all troubleshooting help is welcome!
> >
> >Here is what I have in conf.modules for the cards:
> >alias eth0 3c509
> >alias eth0 3c509
> >This has always worked, and still does if I go back to old kernel...but
> >of course, with old kernel, I can't use Promise PCI.
>
> ITYM "alias eth0 3c509 alias eth1 3c509". And where is the "options
> 3c509 irq=X,Y" line? If you think there's an IRQ or I/O port conflict,
> you can get a look at the kernel's map of the IRQs and I/O ports with
> "cat /proc/ioports && cat /proc/interrupts". Generally, the 3c509
> module requires the IRQ of the card, so it can probe for the I/O ports
> effectively, as the autoprobing doesn't always work. What do you get if
> you "rmmod 3c509" and then "insmod 3c509 irq=X,Y" where X and Y are the
> IRQs your cards are set to?
>
> 2.2.16 was kind of rushed out the door IMO; I haven't been able to get
> it to work with parport ZIP drives while 2.2.12--2.2.15 all worked just
> fine.
>
> --
> Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
> Brainbench MVP for Linux Admin / Those who do not understand Unix are
> http://www.brainbench.com / condemned to reinvent it, poorly.
> -----------------------------/ --Henry Spencer
------------------------------
From: [EMAIL PROTECTED] (Colin Watson)
Crossposted-To: comp.os.linux.setup
Subject: Re: increase microphone volume
Date: 26 Aug 2000 19:08:05 GMT
Anton Suchaneck <[EMAIL PROTECTED]> wrote:
>Does someone know whether I can increase the volume the microphone
>receives?
Try 'aumix' or a similar mixer tool.
--
Colin Watson [[EMAIL PROTECTED]]
"Saint Jean le Desincarne, priez pour nous! But please - let us not
have to follow your example for at least another million years."
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: New kernel, Promise 66 PCI, and 2 3c509's
Date: 26 Aug 2000 21:41:22 GMT
Reply-To: [EMAIL PROTECTED]
On Sat, 26 Aug 2000 20:58:17 GMT, Sean LeBlanc wrote:
>Wow. Thanks for the quick response. I tried rmmod 3c509, but that didn't
>find the module - turns out I compiled 3c509 support into kernel, not
>as a module. Could that be a problem?
Yep! If you compile Ethernet support into the kernel, then for more
than one card to be detected at boot, you must pass the "ether=" options
to the kernel at boot time. Kind of like so:
LILO: linux ether=5,0x210,eth0 ether=3,0x310,eth1
Because this can be a little clunky, it's usual to compile Ethernet
stuff as modules. There's nothing particularly wrong with putting
things into the kernel; it just makes finding out what's wrong and
fixing it a bit more difficult sometimes.
>alias eth0 3c509
>alias eth1 3c509
>options 3c509 io=0x210,0x310 irq=5,3
The io= parameter should be unneccessary for 3c509s. At least, when I
put "options 3c509 io=0x380, irq=9" in my conf.modules, attempting to
load 3c509.o resulted in "invalid parameter" error messages. Taking out
the io= made everything work. Looking at the code, I see the driver
finds the right I/O range given the IRQ, and doesn't even have a module
parameter entry for the I/O range.
>When I do cat /proc/ioports and cat /proc/interrupts, for the
>new kernel, I see no entry at all for IRQ 3 or base addr 310.
Entries only appear there when a device module is loaded and/or being used.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Those who do not understand Unix are
http://www.brainbench.com / condemned to reinvent it, poorly.
=============================/ ==Henry Spencer
------------------------------
From: [EMAIL PROTECTED] (Peter Bismuti)
Subject: how to use SCSI utilities?
Date: 26 Aug 2000 22:28:07 GMT
I run Redhat6.0, I had a hardware upgrade/rebuild done, now I can't access
my scsi devices:
[peterb@roughneck Linux]$ dmesg | grep scsi
scsi : 0 hosts.
scsi : detected total.
When booting up, I can type <ctrl>A to fire up a SCSI utility, when
I do that it shows the SCSI controller at id=7 and my cdr at id=4 I
believe. Is there any chance the problem is NOT with hardware? Is
there some configuration i can do with the SCSI utility to make my cdr
visible during bootup? Is termination always a hardware issue? I noticed
that the scsi controller termination was set to <AUTOMATIC>. Is there
anyway to tell in software that the hardware is not configured correctly?
Any advice?
Thanks
------------------------------
From: A E Lawrence <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: Netgear FA311 ethernet card Not working
Date: Sat, 26 Aug 2000 23:37:37 +0100
"@home" wrote:
>
> Ok, I'm a little confused here. Did you get the fa311.c to work successfully
> or not? Your last post seems to indicate you did, but your previous post
> indicates you had lots of problems with it. Also, where did you get fa311 v
> 1.4?
>
Sorry. It wasn't very clear. And as I investigated further, more
problems showed up.
1) There were no problems compiling and installing fa311 as a module
under 2.2.16.
2) And the card then functioned sometimes. It looked as if it was
autonegotiation that failed: even when both ends of the link agreed on
the protocol, they would not necessary operate.
3) When I used Donald's natsemi driver, the performance was rather
better, but the same sorts of failure happened. In that case they could
be investigated with his mii-diag and natsemi-diag utilities which are
available from his website.
4) Since two FA311's would seldom work back-to-back with a cross over
cable, and if they did agree to communicate the bandwidth was almost
always very low, I decided to reject the cards and exchange them for
FX310TXs. That is a tulip design, but since looking at the tulip mailing
list archives, I may have made a mistake in staying with NetGear :-(
The 311 is based on a newish National semiconductor chip, and I
speculate that the problem resides there. I would advise people to stay
away from the FA311 until the problem has been identified and fixed.
ael
--
Dr A E Lawrence (from home)
------------------------------
From: A E Lawrence <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: Netgear FA311 ethernet card Not working
Date: Sat, 26 Aug 2000 23:40:28 +0100
"David N. Haney" wrote:
>
> A E Lawrence wrote:
> >
> > "David N. Haney" wrote:
> > >
> > > I also have the FA311. I tried the fa311.c provided by Netgear without
> > > success.
> Dr. AE Lawrence:
>
> I'm sorry I seem to have lost your correct email. I respect your
I believe that SPAM orginally stood for SPiced hAM :-) So just remove
the SPAM.
ael
--
Dr A E Lawrence (from home with apologies for spam enhanced reply
address)
------------------------------
From: [EMAIL PROTECTED] (Peter Bismuti)
Subject: ethernet - device not found
Date: 26 Aug 2000 22:32:23 GMT
I just a hardware rebuild/upgrade, now the ethernet card is not visible.
I popped off the top and it seems to be connected correctly. If I
try a ifconfig ethernet... I get a message:
eth0: unknown interface: No such device
dmesg | grep eth0 produces nothing.
Is there any chance that this is NOT a hardware problem? It is a NE2000
compatible of the name "delta" I believe, it is about 3 years old.
Any advice?
Thanks
------------------------------
** 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
******************************
