You're probably right about going for name brand, you get better performance
etc, though the HOWTO gave me the impression that the Realtek 8029 was a
well supported chipset, though I see what you mean, the driver might just
assume it's an ISA card.
Fortunately the vendor I purchased from actually sells Linux Mandrake
pre-installed (www.trinix.com.au). They sold me a card they knew would work
with Linux, if I hadn't worked it out myself by the following Monday, I'm
sure they would have helped me out. In mess around home systems, where
there is nothing critical happening, it becomes harder to justify to the
missus the extra cost of high performance network cards.
Oh well, at home I have 10M for two computers, at work there is 10M for 30.
I can't complain.
Aaron
> -----Original Message-----
> From: John Aldrich [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, November 04, 1999 12:14 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [newbie] ne2000 netcard
>
> On Tue, 02 Nov 1999, you wrote:
> > Any idea why the ne2k-pci driver didn't work? Re-reading the
> ethernet-HOWTO
> > it says if the current ne2k-pci driver doesn't detect a particular PCI
> card
> > to contact the maintainers of the driver. Is this my big chance, my
> once in
> > a life time opportunity, for I, a mere newbie, to contribute towards the
> > greater body of Linux knowledge? <cue music> ;-)
> >
> Hmm....only thing I can figure is that the pci driver isn't
> set up to recognize that chipset as a valid PCI network
> card. That's why I try and get "name brand" chipsets (for
> example, at home, I'm using a DEC Tulip chipset card made
> by Kingston <G>)
> John
