On 2 Oct 2003 02:52:32 -0700, Wolf-D. Perl <(E-Mail Removed)> wrote:
> my machine has multiboot winxp and redhat 9.
> i have a dec21041 nic pci 10 mbit which worked on win xp and on
> redhat.
>
> now i needed to change the hardware config, i put the dec nic in
> another pci slot in my pc, and after that on win xp it works,
> and in redhat at boot kudzu asks for configuring newly my nic, so i
> configured it new.
> after redhat is completely up, it is activated as eth0 (with tulip
> driver like before).
>
> my question: i can ping the ip of it, works,
> but when i look at my hub (where it is connected), it is not attached
> there.
> when booting winxp, the nic is attached to the hub (lights on).
For some reason automatic configurations try to use 'tulip' module even
with old 10baseT real DEC chips (SuSE does that too). For my built-in
10baseT nic that lspci -v identifies as "Digital Equipment Corporation
DECchip 21142/43 (rev 41)", the de4x5 module works better. de4x5.txt in
kernel sources says this module recognizes following chips:
DC21040 (no SROM)
DC21041[A]
DC21140[A]
DC21142
DC21143
All I had to do was change my alias eth1 in /etc/modules.conf to de4x5,
but it has been awhile since I used RH, so I am not sure how to tell kudzu
to use the more appropriate de4x5 module.
--
David Efflandt - All spam ignored
http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/