I'm planning on trying a Debian network install this weekend
so the network has to work.  The problem has been this chip.
Some distributions detect it, but can't seem to configure
it correctly so there is no eth0 shown in ifconfig.  Others
show a eth0 card with a lot of errors.  Can anyone confirm
that Etch will detect and configure this card correctly (or
offer the how-to to make it work)? I have searched the net
and the Debian site and there is nothing specifically
mentioned about this chip, at least not in the last year.

Yes, I realize that for $15 I could replace the NIC, but
what's the fun in that?

Thanks,

[ Post a follow-up to this message ]

Dave Boland said:
> I'm planning on trying a Debian network install this weekend
> so the network has to work.  The problem has been this chip.
>   Some distributions detect it, but can't seem to configure
> it correctly so there is no eth0 shown in ifconfig.  Others
> show a eth0 card with a lot of errors.  Can anyone confirm
> that Etch will detect and configure this card correctly (or
> offer the how-to to make it work)? I have searched the net
> and the Debian site and there is nothing specifically
> mentioned about this chip, at least not in the last year.
<snip>

I dunno if the chip works with Debian, but at the "Boot:" prompt type

expertgui

and you will have a chance to configure the card in question.

From their web site:
" 2.2.5. Network

The network can be used during the installation to retrieve files
needed for the installation. Whether the network is used or not
depends on the installation method you choose and your answers to
certain questions that will be asked during the installation. The
installation system supports most types of network connections
(including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After
the installation is completed, you can also configure your system to
use ISDN and PPP.

and

2.6. Network Connectivity Hardware

Almost any network interface card (NIC) supported by the Linux kernel
should also be supported by the installation system; modular drivers
should normally be loaded automatically. This includes most PCI and
PCMCIA cards. Many older ISA cards are supported as well.

As for ISDN, the D-channel protocol for the (old) German 1TR6 is not
supported; Spellcaster BRI ISDN boards are also not supported by the
debian-installer. Using ISDN during the installation is not supported. "

For more read here:

http://www.debian.org/releases/stable/installmanual

HTH,
--
sk8-365

[ Post a follow-up to this message ]

In article <46409ab7$0$8991$4c368faf@roadrunner.com>,
Dave Boland  <NoSpam@stny.rr.com> wrote:
>I'm planning on trying a Debian network install this weekend
>so the network has to work.  The problem has been this chip.
>  Some distributions detect it, but can't seem to configure
>it correctly so there is no eth0 shown in ifconfig.  Others
>show a eth0 card with a lot of errors.  Can anyone confirm
>that Etch will detect and configure this card correctly (or
>offer the how-to to make it work)? I have searched the net
>and the Debian site and there is nothing specifically
>mentioned about this chip, at least not in the last year.
>
>Yes, I realize that for $15 I could replace the NIC, but
>what's the fun in that?
>
>Thanks,
>

Haven't tried Etch... but the chipset's worked well since RH6.2 and all
through the RH series.  Used 'em both on RH7.2 with a four ports board
at work.

Good chips.


The only board with problems is the one I have from Matrox which is NOT
supported anywhere since they did some things with the Shark 4ports card
to make it not work.

I'd give anyone who wants a card if they can get one of these working
under Linux for me.

I've got a couple of these NS100/4 cards I'd like to use.
They'd go great in IPcop firewalls.

from:
http://www.freelabs.com/~whitis/hardware/quartet.html

"The matrox shark NS-100/4 is a four port tulip 21140 based card. To be
truly asinine, they put the EEPROM on the second (or third if you probe
backwards) chip so the tulip driver will not work correctly with or
without reverse_probe=1. This was reportedly a deliberate
incompatibility."

It will only ifconfig and run port eth2 because of the hardware layout
of the on board eeprom.

I think SCO had online driver sources for them as an example of writing
driver code.

Bill

pechter-at-gmail-dot-com

--
--
"When I think back on all the crap I learned in Vax school
It's a wonder I fixed anything at all."   (to the tune of Kodachrome)
pechter-at-gmail.com

[ Post a follow-up to this message ]