Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 70750 - tulip NIC driver does not load
Summary: tulip NIC driver does not load
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-11 00:26 UTC by gerd.bitzer
Modified: 2004-11-11 09:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gerd.bitzer 2004-11-11 00:26:20 UTC
The tulip ethernet card driver does not load at least with kernel 2.6.9-gentoo-r1. Errormessage is:

# /etc/init.d/net.eth0 start
  * Bringing eth0 up (192.168.2.254)...
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device    [ !! ]

But with the de4x5 driver the same NIC works without a problem:

BlackHole root # modprobe de4x5
BlackHole root # /etc/init.d/net.eth0 start
BlackHole root # ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=255 time=2.76 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=255 time=1.09 ms

The tulip driver of kernel 2.4.27 works also without a problem. Do not know when it was broken.

Reproducible: Always
Steps to Reproduce:
1. modprobe tulip or
2. /etc/init.d/net.eth0 start
3.

Actual Results:  
see in the details section

Expected Results:  
bring the NIC up

A workaround (which worked on my box) is to use the de4x5 driver instead of the
broken tulip (see also details)
Comment 1 Daniel Drake (RETIRED) gentoo-dev 2004-11-11 08:23:51 UTC
Please post output of "lspci" and "lspci -n"
Comment 2 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-11-11 09:31:50 UTC
Then use the driver that works :)

This isn't a bug, sorry.