Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
you'll already have the tulip driver installed on your system, you'd need to add a line like "alias eth0 tulip" to /etc/modules.conf and maybe insmod it, and then maybe insmod it, and then use netconfig or such. to be honest, i'm never really sure what to suggest with things like that, as mine always seem to work first time if ever...
I don't think its tulip anyway... it might be tulip_cs, or possibly another one. The pcmcia drivers tend not to be the same drivers as the normal pci cards. You might also be having problems with pcmcia because RedHat switched to in-kernel pcmcia a little early and a number of people are having problems with it. What's the output from "lsmod"?
Is there a 'yenta_socket' listed? also post anything called 'tulip_cs', or for that matter, anything with a '_cs' from "lsmod".
Another big telltale of whether the drivers are loading correctly is the beep-code of pcmcia. If you hear one high-pitched tone on load that's the cardmgr finding the card. If you hear another one, that's the thing loading the module and binding it to the card. If the second tone is more like a "bonk", then it failed to initialize the card.
if i insert "alias eth0 tulip" to /etc/modules.conf
i do have a light on my card but it doesn't work, the light is not green...
the reason i ask how to install that particular module is that they change the offset address to 0x166 instead of 0x170 for it to work with xircom cards (see: http://ivs.cs.uni-magdeburg.de/~danilo/linux.shtml )
i have the driver but i don't know how to load it :-(
Who cares what RH's init scripts think... they're not built for pcmcia. Your pcmcia drivers like pcmcia_core and yenta_socket are getting loaded after all of the normal network boot stuff so of course its failing. If you want to use pre-built scripts, the ones you should be aiming for are /etc/pcmcia/network.opts and if you want to restart networking by hand, invoke:
To see if the nic is working:
ifconfig eth0 126.96.36.199 up
If it keeps settings its ready to roll. Offhand, are you using dhcp or assigning everything statically?
No no, not config.opts, cardmgr reads that, don't fiddle with that, network.opts, should have a section like:
# Network adapter configuration
# The address format is "scheme,socket,instance,hwaddr".
# Note: the "network address" here is NOT the same as the IP address.
# See the Networking HOWTO. In short, the network address is the IP
# address masked by the netmask.
case "$ADDRESS" in
INFO="Sample private network setup"
# Transceiver selection, for some cards -- see 'man ifport'
# Use BOOTP (via /sbin/bootpc, or /sbin/pump)? [y/n]
# Use DHCP (via /sbin/dhcpcd, /sbin/dhclient, or /sbin/pump)? [y/n]
# If you need to explicitly specify a hostname for DHCP requests
# Host's IP address, netmask, network address, broadcast address