Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sorry if this should be in the newtwork forum but has anyone had any luck with installling the tulip drivers in conjunction with a 2.6.10 kernel. or any 2.6.* for that matter.
I can't get them to compile.
I think that maybe they were only developed for up to the 2.4* kernels.
Its for a linksys nc100 card.
It worked ok under with previous kernel but Its the last bit of hardware for me to to get working now with my new one.
followed instructs for the build as per thw www.scyld.com site but no joy.
I used the kernel module for the tulip card in my old computer, and it compiled fine with 2.6.11.3 although it doesn't want to connect to the VoIP gateway/router (it works with a direct connection to the main computer with a crossover cable).
lsmod should tell you which driver it's actually using (likely tulip if that's what it was before), so the next time you compile a kernel you can leave out the others
Coincidentally I just installed an unknown card which lspci said was a linksys nc100. I didn't understand all the tulip options in the 2.6.12.3 tulip menuconfig either, but checked them all as modules. But then just 'modprobe tulip' worked fine.
Only the 'tulip' module is loaded. Here's the kernel menuconfig and .config sections I used:
Code:
[*] "Tulip" family network device support
<M> Early DECchip Tulip (dc2104x) PCI support (EXPERIMENTAL)
<M> DECchip Tulip (dc2114x) PCI support
[ ] New bus configuration (EXPERIMENTAL)
[ ] Use PCI shared mem for NIC registers
[ ] Use NAPI RX polling
<M> Generic DECchip & DIGITAL EtherWORKS PCI/EISA
<M> Winbond W89c840 Ethernet support
<M> Davicom DM910x/DM980x support
# Tulip family network device support
#
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
So I guess the DECchip Tulip (dc2114x) option gives the standard 'tulip' module which is all that this generic 'made in china' network card needs.
In fact to figure out which module I needed I just booted up a knoppix CD and checked which network driver got loaded.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.