Baslinux mailing list

[baslinux AT lists.ibiblio.org]

Message from Steven
===================

> i cannot connect to my local ethernet. 
> 
> After loading the 8390.o and smc-ultra.o modules, 
> 
> smc-ultra.c: Presently autoprobing (not recommended) for a single card.
> smc-ultra.c:v2.02 2/3/98 Donald Becker (becker AT cesdis.gsfc.nasa.gov)
> eth0: SMC Ultra at 0x300, 00 00 C0 DB 4F D4, IRQ 10 memory 0xcc000-0xcffff.

So far, so good.  eth0 is activated.

> Next i configure the interface eth0 

What command did you use for that?  

> with the following result:
>
> eth0  Link encap:Ethernet  HWaddr 00:00:C0:DB:4F:D4  
>       inet addr:192.168.1.18  Bcast:192.168.1.255  Mask:255.255.255.0
>       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>       RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>       TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>       collisions:0 txqueuelen:100 
>       RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>       Interrupt:10 Base address:0x310 Memory:cc000-d0000 

Good.  You should be able to use the network now.

> However, after issuing the 'ifconfig 192.168.1.18 up' command, 

Why are you doing that?  eth0 is already up.

> The system does not respond to ping-requests nor is 
> it possible to ping other machines. 

Did you try the pings before your unnecessary ifconfig up
command?  Or after?  If it was after, I suggest you power
off the system, reboot BL3 and then issue only the following 
commands:
--------------------------
insmod 8390
insmod smc-ultra
ifconfig eth0 192.168.1.18
ping 192.168.1.x            # where x = a valid address
--------------------------

If the ping fails, there are three possibilities:
(1) fault in the cable
(2) wrong cable type (crossover/normal)
(3) wrong network address assigned
(4) fault in the eth0 card

> Doing the same with TRINUX on the same machine works fine. 

OK, that eliminates the various faults listed above.
Perhaps your problem is here:

> After loading the 8390.o and smc-ultra.o modules, which 
> i downloaded from a slackware 4 site

You got the modules from the wrong place.  Please go to
the BasicLinux site:  http://www.basiclinux.com.ru
There you will see the following paragraph:
----------------------------------------------------
BasicLinux has a slim IDE kernel and a small set of 
common modules.   Additional modules and alternative 
kernels are here.
----------------------------------------------------
Click on the word HERE and go into the directory for
2.2.26 kernel modules.  In the net subdirectory you 
will find the correct modules.

> Trying to run BasicLinux on another machine, with a 
> different network card and hence a different network 
> driver module leads to similar results: it doesn't 
> work either. 

Did you get that module from Slackware 4 too?
Slackware 4 uses a much older kernel than BL3.
We use application packages from Slackware 4, 
but not the old modules.

Cheers,
Steven