Re: tulip with 3CSOHO100B-TX on Redhat 9
CP <[email protected]> Thu, 17 Apr 2003 11:12:50 -0700
| Newsgroups | gmane.linux.drivers.tulip.general |
|---|---|
| Message-ID | <[email protected]> |
Don, thanks for the quick and helpful response !
I could not load pci-scan with "modprobe tulip", it gave :
r/oot@localhost root]# modprobe tulip
/lib/modules/2.4.20-9/kernel/drivers/net/tulip/tulip.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid
IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-9/kernel/drivers/net/tulip/tulip.o: insmod
/lib/modules/2.4.20-9/kernel/drivers/net/tulip/tulip.o failed/
but when I executed :
modprobe pci-scan
modprobe tulip
both loaded without errors and eth0 came up immediately
I will take a look at the modprobe tulip issue further, thanks again for
the help !!
CP
Donald Becker wrote:
>On Wed, 16 Apr 2003, CP wrote:
>
>
>
>>I just built the netdrivers suite by straight compiling and also
>>building the RPMS on Redhat 9 (2.4.20-8).
>>
>>either way, insmod tulip.o gives the following error(s):
>>
>>unresolved symbol pci_drv_unregister
>>unresolved symbol pci_drv_register
>>
>>
>
>You must load the 'pci-scan' module first.
>This is done automatically when you use modprobe instead of insmod
> /sbin/modprobe tulip
>
>
>
>
_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip