1. My copy of the Bering 1.2 modules tarball has 2 different 3c59x.o modules in it -- one in ./2.4.20/net, the other in ./2.4.20/kernel/drivers/net . They are different sizes so, presumably, different in some way that matters in use. Which did you try (or did you try both)?
2. What happens if, from the command line, you enter "insmod 3c59x.o"? Do you get any informative error messages? Are the interfaces now created (not configured, which refers to their having IP addresses)? I think "ip link show" lists all interfaces, including unconfigured ones ... though I have no available unconfigured interfaces to test this memory conveniently ... "ip addr show" does only list configured interfaces, though.
3. Are you using the right modules package for your version of Bering (that is, for the kernel it uses)? They need to match exactly, which is why your use of the module from Red Hat will not work here.
4. Are you certain that the NICs (especially the onboard one) are 3c905s? It's been a long time since I had a Dell Optiplex, and it was a different model number, but mine used the eepro100 module for its onboard NIC.
5. Does Bering have the "lspci" command available? I don't recall. If it does, can you run it and see the NICs as present on the PCI bus?
6. Are there any instructive messages in the logs ... either from the modules themselves or from ip when it tries to configure (presumably) non-existent interfaces?
At 12:50 PM 1/21/2004 -0500, Tibbs, Richard wrote:
Hello List: I have tried implementing a bering fw (floppy boot) on Dell Optiplex GX150 with two NICS. One is an "integrated" nic on the motherboard (3c905b), and the other is a PCI card 3c905c. Both are PCI devices, and RedHat 9 finds them both and configures them. Under RH9 (booting from the hard drive) I can ping from both interfaces to devices on either subnet. With Bering, using the 3c59x.o module found via the Bering installation guide, neither interface is brought up.
Neither an ip addr sho nor ip link sho command shows these interfaces (get nothing but lo and dummy0).
I even tried swapping in the RH9 3c59x.o to replace the one from sourceforge. Still no luck. So I am wondering if the PCI scan utility (whatever it is in Bering --- under Dachstein I load a pciscan module) is not happy with such an integrated NIC.
Immediately after boot, a dmesg command shows nothing that looks like an error. The "probing PCI hardware" line appears, and no other complaints seem to arise.
In the interfaces file in /etc/network, both eth0 and eth1 are mentioned in an auto command, and are given static Ips. auto eth0 iface eth0 inet static address 192.168.10.254 masklen 24 broadcast 192.168.10.255 gateway 137.45.192.186 # # Option 1.3: PPP/PPPOE (modem connected to eth0) #auto ppp0 #iface ppp0 inet ppp # pre-up ip link set eth0 up # provider dsl-provider eth0 # # Option 1.4: PPP modem #auto ppp0 #iface ppp0 inet ppp # provider provider
# Step 2: configure internal interface # Default: eth1 / fixed IP = 192.168.1.254 auto eth1 iface eth1 inet static address 137.45.192.185 masklen 24 broadcast 137.45.192.255
# ....
In /etc/modules there is a single uncommented line 3c59x Above the usual ip_conntrack and ip_nat stuff.
What could be wrong?
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
