difficulty to ping the network
 

my network card is a external network card but i cant ping because my eth0 cant activate.
when i run the command ' ifconfig '. they just show me one paragraph only. that is ....

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:92 errors:0 dropped:0 overruns:0 frame:0
TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5976 (5.8 Kb) TX bytes:5976 (5.8 Kb)

there should be 2 paragraph right?
so anyone has any idea about this problem?

i am using the antech 10/100m ethernet PCI adapter.

i hope that you guy can help me it is because my project is coming up soon.
thanks!

Hmmm, I don't see it in the hardware compatibility list. It may simply not be supported.

post the output of

dmesg |grep antech

or if that gives you nothing, just look through the output of

less /var/log/dmesg

and see if you see anything there pertaining to your card. You can always look through /var/log/messages as well for pertinent error messages.

Let us know...

check the file /etc/network/interfaces , you should configure your interface with the ip address,etc.

then

ifup eth1

if you choose eth1 for that interface

regards

MM

I didn't get anything for dmesg grep antech...
Is there a line or bracket in front of grep?

And both less /var/log/dmesg and less /var/log messages gave me a list of stuff I don't know...Looked through it and didn't see anything concerning the network card or eth0.

Also, I don't have a network folder under my /etc directory so, I can't check the files in etc/network/interfaces. Am I supposed to have this directory? And when I ran ifup eth0 without configuring anything, the terminal just went to the next line without doing anything. Help...

Please post the output of /sbin/lspci to confirm that Linux is seeing your ethernet card. Chances are, you simply haven't inserted the correct driver module into the kernel. Do a Google search on the name of your card and Linux, to see if you can find out what the driver name is. Once you've done that you can hopefully (as root) do 'modprobe <drivername>' (no quotes). If that doesn't work, post the error -- you may need to get the driver from somewhere.

Ok, when I did /sbin/lspci, I got

00:12.0 Ethernet controller: MYSON Technology Inc SURECOM EP-320X-S 100/10M Ethernet PCI Adapter

So that means that my network card is detected right? Anyway, I found a driver at www.driverguide.com and the readme told me to do this:

Installation:

1. copy the source code mtd80x.c to Linux,

2. compile the source code, the instruction for compiling the driver is
as follows:

#gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall
-Wstrict-prototypes -O6 -c mtd80x.c

3. insert the driver as module,

#insmod mtd80x.o

4. bind your card to an IP address

#ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}

5. add your card to IP routing table,

#route add -net ${NETWORK} netmask ${NETMADK} eth0

6. now, you should be able to ping local network.

When I tried the second instruction, I got a long list of stuff ending with the lines

/usr/include/asm/pgalloc.h:63: initializer list being treated as a compound expression
/usr/include/asm/pgalloc.h:63: confused by earlier errors, bailing out

I don't know what to do about that. Anyway, I ignored those and ran the next instruction and I got:

MTD80X.O: The module you are trying to load (MTD80X.O) is compiled with a gcc version 2 compiler while the kernel you are running is compiled with a gcc version 3 compiler. This is known to not work.

So, this problem can be solved by downgrading my gcc compiler right? But that still leaves the earlier one...

run 'gcc -v'.

Since you compiled the souce code yourself, sounds like you have gcc vers. 2 installed instead of something like 3.3.

Hi,

Try
updatedb, and then
locate interfaces or
locate network, in debian the file
/etc/network/interfaces, if you are using other distribution could be in a diferent location or other name related to network or interface.

the file should contain the configuration of each interface.

when you run ifup eth0 the configurations in that file will be applied.

regards
MM

When I ran 'gcc -v', I found out that I'm running gcc version 3.2. So, do I need to downgrade in this case?

And updatedb doesn't work...Also, I don't have the directory /etc/network/interfaces. I'm actually running Red Hat 8...I tried looking for the network interfaces file but I have no luck there...

With any luck, you don't need to actually compile the module yourself -- what does 'modprobe mtd80x' do? If it works, you may be set already.

I get:

modprobe: Can't locate module MTD80X

Tried it with MTD80X.O and MTD80X.C too but it didn't work...

Just for fun, please do 'cat /proc/version' on the command line so we can see a few details of how your kernel was compiled. This is just to confirm that the error message you got from compiling the module is legit and not a red herring.

[root@localhost root]# cat /proc/version
Linux version 2.4.18-14 (bhcompile@stripples.devel.redhat.com) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 13:35:50 EDT 2002
[root@localhost root]#

Is this what you're looking for?

[n] anyone got the solution of this problem?
 

bump

Ive been working on this same problem all night, no luck ether, however, I dont think a downgrade will work, because its not gcc 3 that is the problem, its the fact that your system was built using that version of gcc. What we need, is someone who can decompile MTD80X.O and .C and recompile them using a newer version of gcc. I dont have the knowledge to do that but maybe someone here does.

Untill then Im going to sleep...