Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
12-31-2000, 11:10 PM
|
#1
|
LQ Newbie
Registered: Dec 2000
Location: Edmonton
Distribution: Kubuntu 7.04
Posts: 13
Rep:
|
I'm running Red Hat 7.0 in an 800 mHz machine with 256 megs of ram and a 30 gig hard drive.
My problem is that I have a Linksys Etherfast LNE100TX card that is not recognized during bootup. I have ensured that eth0 has a tulip driver, but during bootup I get the message that eth0 has failed and that eth0 initialization is delayed.
When I list the interrupts or the ioports, eth0 is not shown.
When I run ifconfig, the lo is shown, but not eth0.
If I try "insmod tulip" I get the reply that "init_module: Device or resource is busy." and then a hint that "insmod errors can be caused by incorrect module parameters, including incorrect IO or IRQ parameters."
I have tried to set the parameters by using netconf as well as netcfg. Netcfg shows that the card is inactive, and it cannot be set to active.
The IP is supposedly set by a DHCP server, and I am running the card into a Linksys router and from there into an ADSL Cisco modem.
Everything else appears to be working just fine EXCEPT the network card, which I need to connect to the internet.
What else can I do to get it to work?
|
|
|
01-02-2001, 11:51 AM
|
#2
|
LQ Newbie
Registered: Jan 2001
Location: N. virginia
Posts: 2
Rep:
|
Could be that you need a new driver for your card. I had a similar incident where the drivers that came with Linux didn't match the card I had. The easiest thing to do is to go to the companies website and download the driver.
|
|
|
01-02-2001, 11:51 AM
|
#3
|
LQ Newbie
Registered: Jan 2001
Location: N. virginia
Posts: 2
Rep:
|
Could be that you need a anew driver for your card. I had a similar incident where the drivers that came with Linux didn't match the card I had. The easiest thing to do is to go to the companies website and download the driver.
|
|
|
01-09-2001, 07:42 AM
|
#4
|
LQ Guru
Registered: Jan 2001
Posts: 24,149
|
Redhat 7.0 has its problems.....
Hello,
I have the same ethernet card and tried to install RH 7.0 and came up with the same problems. I even tried to compile the drivers off the linksys disk which has the linux drivers on them. The worse thing though is I found out after trying to compile the driver with the directions off Linksys website, I later found out RH 7.0 gcc compilers don't work. When I was trying to compile it would od nothing....so I even tried ifconfig, had no eth0 shown. I tried netcfg and linuxconf for an easier way to install and select the driver cause I know previous versions of RH had the tulip drivers.
I totally was disgusted with 7.0 and ended up going back to 6.2 which detected my card during install, and I even setup my internet configuration with ease.
Let me know if you actually get that card to work in 7.0, I wouldn't mind having 7.0 installed on one of my machines. Personally I think 7.0 is a flop, needs an update badly.
|
|
|
02-01-2001, 11:55 AM
|
#5
|
LQ Newbie
Registered: Feb 2001
Posts: 4
Rep:
|
tulip driver problems
There are definately problems with the Tulip driver and the LinkSys ethernet card in RedHat 7.0. I would recommend rebuilding the module using kgcc instead of gcc (gcc in RedHat 7.0 is experimental and unfit for regular use) and including the include flag I/usr/src/linux/include. I know that some people have gotten the tulip driver to work for them, but it wasn't pretty.
|
|
|
All times are GMT -5. The time now is 10:04 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|