Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
I installed slackware a few days ago. I have a linksys network card, and it worked with the bare.i kernel that comes with slackware. However, I wanted to install a more functional kernel, so I downloaded kernel 2.6.7 from kernel.org. I know that my card uses the normal tulip driver.
When I was menuconfig'ing the kernel, I made sure to select tulip. It was only available as a built-in, not a module, so this is what I selected. I did compile and install the kernel. My computer is recognizing my card, because it lists it when I use 'lspci'. I have no idea what to do now. I have done quite a bit of searching, on this forum also, but all of the documentation I've found on how to use the tulip driver is information on how to load it as a module. How do I use it if it's not compiled as a module, but as part of the kernel?
Sorry if I'm incredibly ignorant, I switched to slackware from Fedora, and Fedora does everything for you. Not good.
There's a bunch of options under tulip support in kernel config, which you should be able to select as modules.
If a driver is compiled in, ususally it will load automagically on boot if the kernel detects the presence of the device.
Originally posted by escargot22026 I installed slackware a few days ago. I have a linksys network card, and it worked with the bare.i kernel that comes with slackware. However, I wanted to install a more functional kernel, so I downloaded kernel 2.6.7 from kernel.org. I know that my card uses the normal tulip driver.
When I was menuconfig'ing the kernel, I made sure to select tulip. It was only available as a built-in, not a module, so this is what I selected. I did compile and install the kernel. My computer is recognizing my card, because it lists it when I use 'lspci'. I have no idea what to do now. I have done quite a bit of searching, on this forum also, but all of the documentation I've found on how to use the tulip driver is information on how to load it as a module. How do I use it if it's not compiled as a module, but as part of the kernel?
Sorry if I'm incredibly ignorant, I switched to slackware from Fedora, and Fedora does everything for you. Not good.
Thanks in advance,
Edward S. Rice
Are you sure you got the actually module and not just the support for the family of cards you should be able to select that as a module.
Code:
[HappyTux:/home/stephen]# grep -i tulip /boot/config-2.6.8-rc2-ck6
# Tulip family network device support
CONFIG_NET_TULIP=y
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
If you have both selected then can we see the output of ifconfig -a.
You suggest looking through the /boot/config file to see what the current kernel's configuration is. I didn't copy a config file of my kernel to the boot folder when I installed the new kernel. Sorry, should I copy one?
Originally posted by escargot22026 You suggest looking through the /boot/config file to see what the current kernel's configuration is. I didn't copy a config file of my kernel to the boot folder when I installed the new kernel. Sorry, should I copy one?
You can either copy it or just look in the .config in the kernel tree and see if you have the support, I was thinking the Debian method there.
Found config file, now which option do I choose in menuconfig
Alright, found the config file.
CONFIG_NET_TULIP=y, but CONFIG_TULIP isn't set. Odd. . .
I suppose that CONFIG_TULIP should be on also, or at least set to mod like you described earlier. Should I edit the .config file by hand and simply set CONFIG_TULIP to m, or should I redo menuconfig and look for some option like this? In menuconfig, in the Tulip menu, there is a root option (Tulip family network device support) first. I assume that this is CONFIG_NET_TULIP. There are five sub-obtions: Early DECchip. . ., DECChip Tulip PCI. . ., Generic DECChip. . .PCI/EISA, Winbond. . ., and Davicom. . .
Re: Found config file, now which option do I choose in menuconfig
Quote:
Originally posted by escargot22026 Alright, found the config file.
CONFIG_NET_TULIP=y, but CONFIG_TULIP isn't set. Odd. . .
I suppose that CONFIG_TULIP should be on also, or at least set to mod like you described earlier. Should I edit the .config file by hand and simply set CONFIG_TULIP to m, or should I redo menuconfig and look for some option like this? In menuconfig, in the Tulip menu, there is a root option (Tulip family network device support) first. I assume that this is CONFIG_NET_TULIP. There are five sub-obtions: Early DECchip. . ., DECChip Tulip PCI. . ., Generic DECChip. . .PCI/EISA, Winbond. . ., and Davicom. . .
Which should I choose?
Regards,
Edward S. Rice
I believe you want the Tulip PCI one, but you can tell easily enough when using menuconfig just highlight the option the use the SHIFT and ? keys at the same time and the help for the module will come up and it will tell you what the name of the module will be.
Didn't know about the little shift ? trick. That's helpful. I'm sure that it'll work now that I'm installing the right module . Thanks for all of your help. Having a working network card on your computer does make it a more enjoyable experience.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.