Networking Forums

Networking Forums > Computer Networking > Linux Networking > DEC 21041 problem redhat 9

Reply
Thread Tools Display Modes

DEC 21041 problem redhat 9

 
 
Wolf-D. Perl
Guest
Posts: n/a

 
      10-02-2003, 09:52 AM
hi,

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).

so, before putting the nic on another slot in my machine, it works
with xp and redhat,
after the change i cannot get it working on redhat anymore.

modprobe eth0 shows no errors.
dmesg|grep eth0 shows correct items.

i tried to remove the nic from /etc/sysconfig/hwconf and after reboot
i was able to configure it again with kudzu, but same problem, it is
not attached to my hub.

has anyone out there some tips what i can do about it?

regards, wolf
 
Reply With Quote
 
 
 
 
David Efflandt
Guest
Posts: n/a

 
      10-02-2003, 04:23 PM
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/
 
Reply With Quote
 
Wolf-D. Perl
Guest
Posts: n/a

 
      10-03-2003, 04:02 PM
>
> 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.



Ok, thanks for that tip, i cahnged it in modules.conf and then it is
working now.

but i have the problem you mentioned now, how to get kudzu know the
new hardware setting.

the prob now is when i want to open redhat-config-network the gui
crashes saying

Component: redhat-config-network
Version: 1.2.0
Summary: TB /usr/src/build/228093-i386/install/usr/lib/python2.2/sre.py:137:search:TypeError:
expected string or buffer
Traceback (most recent call last):
File "/usr/sbin/redhat-config-network-gui", line 154, in ?
window = mainDialog()
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py",
line 154, in __init__
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py",
line 225, in load
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py",
line 232, in loadDevices
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/NCDeviceList.py",
line 210, in getDeviceList
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/NCDeviceList.py",
line 117, in load
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/plugins/NCDevWireless.py",
line 34, in load
File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/NCWireless.py",
line 52, in load
File "/usr/src/build/228093-i386/install/usr/lib/python2.2/sre.py",
line 137, in search
return _compile(pattern, flags).search(string)
TypeError: expected string or buffer

Local variables in innermost frame:
pattern: ^s:
flags: 0
string: None


it seems that the kernel don't know the device, so do i have to
recompile my kernel or how can i get the machine know the device
manually?

any hints?

regards wolf
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Debian Etch, DEC 21041 NIC chip set Dave Boland Linux Networking 1 05-12-2007 07:31 PM
RedHat 9 NFS problem nobody Linux Networking 1 12-16-2006 02:07 AM
POP SERVER PROBLEM IN REDHAT Simon Lee Linux Networking 3 08-29-2005 08:42 AM
Knoppix V3.8 CeBIT/DEC 21041 Tulip based NIC's & V3.8/Kernel V2.6.x xxnonexnonexx@tampascanner.info Linux Networking 0 03-27-2005 07:16 AM
Redhat 9.0 PPTPD Problem Michael Walzl Linux Networking 2 12-18-2003 08:30 PM



1 2 3 4 5 6 7 8 9 10 11