Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
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.
|
|
06-25-2003, 05:49 AM
|
#1
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Rep:
|
FA310TX NICs not working with RH8.0
I just installed RedHat 8.0 on a Compaq Presario 2266 which is equiped with a Cyrix MII 225MHz CPU, 4.2 GB HD, 256MB SDRAM, and 2 Netgear FA310TX Fast Ethernet PCI Cards.
I have added "apm=off" to the kernel boot parameters because the system hung during bootstrap.
The current problem is that I cannot get the system to recognize my NICs. I have tried installing the TULIP driver but to no avail. I have copied tulip.c into /home/root and tried to compile it and get only about 2000 errors. C and C program development is not my forte, nor is any of the X flavors.
My goal is to incorporate this box into my LAN which is comprised of several W2K boxes, a W95 laptop, and an old WFW311 386 box. TCP/IP networking and Windows, I know, but Linux is at this point, a mystery to me.
Thanks in advance.
|
|
|
06-28-2003, 07:51 PM
|
#2
|
Member
Registered: Jun 2003
Location: Netherlands
Distribution: Red Hat Linux 9, FreeBSD 4.8, Knoppix 3.2
Posts: 182
Rep:
|
According to :
"http://www.geocities.com/SiliconValley/Lab/6125/linux/fa31x.html"
"https://listman.redhat.com/archives/redhat-install-list/1999-April/msg00410.html"
this card uses the tulip driver.
What does "modprobe tulip" do?
What does "lsmod" give?
What does "dmesg |grep 310" give?
|
|
|
06-29-2003, 06:34 PM
|
#3
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Original Poster
Rep:
|
>What does "modprobe tulip" do?
Returns nothing
>What does "lsmod" give?
Returns "tulip 43552 0 (unused)
>What does "dmesg |grep 310" give?
Returns "Inode cache hash table entries: 16384 (order 5,131072 butes)
----------
I'm afraid I'm probably going to just buy a 3com nic. I haven't got a book on linux yet & am even having trouble mounting an MSDOS formatted FAT12 diskette.
Thanks to Bill Gates, I never learned a real OS.
Oh, well.
|
|
|
06-29-2003, 08:49 PM
|
#4
|
Member
Registered: Apr 2003
Distribution: Mandrake 9.1/slack 9.0/BSD
Posts: 30
Rep:
|
I have had problems in the past with many TX-based NIC's. Many of them use additional drivers(besides the main driver itself) for initialization that not even windows gets right at times. You might want to check into this.
|
|
|
06-30-2003, 04:58 PM
|
#5
|
Member
Registered: Jun 2003
Location: Netherlands
Distribution: Red Hat Linux 9, FreeBSD 4.8, Knoppix 3.2
Posts: 182
Rep:
|
Cougar : Don't rush to the store yet. :-)
What does the command: "lspci -v |grep -i ether" say?
Oh, and also please post the output of the command : "/sbin/ifconfig -a"
|
|
|
07-01-2003, 07:30 AM
|
#6
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Original Poster
Rep:
|
lspci -v | grep -i ether
00:0d.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
00:12.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
/sbin/ifconfig -a
lo link encap:local loopback
inet addr:127.0.0.1 Mask 255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5218 (5.0 Kb) TX bytes:5218 (5.0 Kb)
|
|
|
07-01-2003, 07:35 AM
|
#7
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Original Poster
Rep:
|
deanrantala - I meant to note to you that the NICs did not require any additional drivers when W2K was loaded on that box. I initially was going to use it for a firewall, thus the two NICs, but I wound up using it as a security sandbox on my LAN.
|
|
|
07-01-2003, 06:23 PM
|
#8
|
Member
Registered: Jun 2003
Location: Netherlands
Distribution: Red Hat Linux 9, FreeBSD 4.8, Knoppix 3.2
Posts: 182
Rep:
|
Cougar : I found the following instructions at the Linksys Knowledge Base, I've modified them for Red Hat Linux 8.0. Because I cannot test this, I can't guarantee if it's going to work :
1. Log in as root (with the command "su -")
2. From the console, type in: ifup eth0
3. From the console, type in: ifup eth1
4. After running the command in step 2 and 3 the cards should be
initialized, then input : redhat-config-network
5. After the configuring the card with step 2 and 3, input : ifconfig
6. After running "ifconfig" you should have seen two devices, eth0 and lo.
7. From the console Input : vi /etc/modules.conf
8. Input the following at the beginning of the file : alias eth0 tulip
9. Save changes.
10. You would be back at the console, type in init 6 to restart the system.
After you do that - and with a little bit of luck - your LNE100 will be setup.
|
|
|
07-02-2003, 07:35 AM
|
#9
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Original Poster
Rep:
|
Okay, here are the results of the ifup command:
ifup eth0
/sbin/ifup: configuration for eth0 not found
Usage: ifup <device name>
ifup eth1
/sbin/ifup: configuration for eth1 not found
Usage: ifup <device name>
---
btw: I had not mentioned this yet, but I appreciate your and deanrantala's assistance.
|
|
|
07-02-2003, 08:44 AM
|
#10
|
Member
Registered: Apr 2003
Distribution: Mandrake 9.1/slack 9.0/BSD
Posts: 30
Rep:
|
WIn 2k and XP are usually pretty good with these cards - a big improvement over 95,98,ME. Anyway, it's just that I *always* have lost of issues when trying to get these cards running under linux.
Tell you what, find your inet1 (or rc.inet1) file. It is usually somewhere under /etc/ . This is the main file responsible for your network cards configuration. If you can't find it, do a
whereis inet1
or
whereis rc.inet1
this will help you locate the script. Once you find that, copy the first half of so, post it back here and I will take a look at it.
|
|
|
07-02-2003, 01:19 PM
|
#11
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Original Poster
Rep:
|
There is no rc.inet1 file. There is an rc.local & an rc.sysinit, but I don't know of those are related.
|
|
|
07-05-2003, 02:35 PM
|
#12
|
Member
Registered: Jun 2003
Location: Netherlands
Distribution: Red Hat Linux 9, FreeBSD 4.8, Knoppix 3.2
Posts: 182
Rep:
|
Cougar, try the following commands :
"su -"
<root password>
"modprobe tulip"
"lsmod |grep tulip" <-----(do you see that it has been loaded?)
"dmesg |tail -n 5" <-----(what does this report?)
"ifconfig eth0 10.0.0.1"
"ifconfig" <-----(what does this report?)
Do you see, besides a device called 'lo', the 'eth0' device?
|
|
|
07-19-2003, 09:32 PM
|
#13
|
LQ Newbie
Registered: Jun 2003
Posts: 7
Original Poster
Rep:
|
Thanx for all your help guys, but I just threw in a couple 3COM NICs and saved myself and you all a whole lot of time. The NICs were free & it took all of 10 minutes to swap them.
Anyhoo, thanx to those that offered your assistance!
|
|
|
All times are GMT -5. The time now is 12:20 PM.
|
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
|
|