Re: ethernet support in 2.2.20-20011202 kernel
>> I have been "tinkering" with debian on my old IIci (120MB HD, 20 MB RAM, farallon ethernet card) and I
>> gotten to the stage that it boots fine and I can mount the mac hfs partition and an external zip on the
>> bus. All fine and good.
>> However, I don't seem to be able to get ethernet up and running. I put in all the settings for a "local"
>> network during the installation. If I do "ifconfig", I now see what I think is indicative of functional
>> (ie it gives the IP address, lots of other stuff and is "up"). However, if I ping the computer from my
>> laptop (connected via a 10baseT crossover cable), I get no response (all packets lost). Likewise in the
>This indicates that the kernel does actually see your ethernet card.
>What kernel version are you using. Some of the earlier 2.2.x series
>kernels actually used the wrong address to try to drive some of the 8390
>based cards. Run dmesg and look for the line indicating the mac8390.c
>driver was loaded. What is the version number of the mac8390 driver?
>The latest version is 0.4 2001-05-15 This version fixed some problems.
I powered up debian last night and ran dmesg as you suggested. Very interesting. The mac8390.c driver is
"v0.1 1999-10-18 David Huggins-Daines". Hence, way earlier than the 0.4 2001-05-15 version.
I also saw that there are two lines for eth0 in the list. They go something like:
eth0 failed to detect memery resource for slot D probing...
eth0 found ethernet slot D (type farallon)
I also notice when I run ifconfig that the hardware address of the card is displayed. Hence, the driver
certainly "sees" the card. However, it sounds like the newer driver should be used. This means (I'm afraid)
How/where do I get it?
How do I get it into the kernel? (I suspect the answer to this might be kernel recompiling - something I read
a bit about, but did not think I would have to do...)
I thought that the kernel I had downloaded (details in subject line of email) was the latest one available of
the 2.2.x series (it was at the top of the list).
Any help greatly appreciated as ever,
>> Both network cards give "green lights" on their leds, indicating a link. Both machines are set to have the
>> same subnet mask (255.255.255.0) and have sequential IP addresses of 192.168.0.1 (debian) and 220.127.116.11
>> (win95 laptop).
>> I spent quite a long time trying to figure out how to add the necessary module for the ethernet card,
>> saw that the "alias eth0 ..." line was not in the conf.modules file. I then found out from looking at some
>> mailing list entries that ethernet drivers are built into the kernel. Is this correct??? Certainly when it
>> boots I can see a line something like (from memory) "ethernet card in slot D type farallon". I am assuming
>> that this means debian knows the card is there. What I don't know is whether something else needs to be
>> Sorry if this is a really stupid and simple question. I am new to linux and coming from a mac background I
>> finding it quite (to put it politely!) hard adjusting. However, I do want to keep at it and get it working
>> fully, since the eventual aim is to use it as a little web server (if I can get apache running on it).
>> However, first stage is get networking going.....
>> Many thanks,
>Another issue that can cause the symptoms you are experiencing is the
>setting of the jumper on the card. Some of the Farallon cards have a
>jumper just to the right of the Nubus PROM. This jumper should be set
>to the type of connection you are using (i.e. Thin, AUX or TP).