Whoops, came a bit late to this one.. I had the same problem with 905's. Yes there are two different drivers in the modules tarball, the one that did not work for you requires:
pci-scan.o 3c95x.o And the other one does not. This information is buried somewhere in the modules.dep file. This has one advantage, if you have lots of differing chipsets in the PC, they can all use pci-scan.o, the dependant versions of NIC modules seem to be smaller. My box uses pci-scan.o 3c95x.o rtl8139.o both require pci-scan.o PS Anybody got TI ACX100-based 802.11b cards working? James. -----Original Message----- From: Tibbs, Richard [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 13:44 To: Tony Cc: [EMAIL PROTECTED] Subject: RE: [leaf-user] Bering can't handle Dell GX150 integrated Ethernet? Thanks... Got it Resolved. See Below. Had to use the "other" 3c59x.o in .../2.4.20/kernel/drivers/net. Would be nice if the installation guide pointed you to the right driver. Rick. -----Original Message----- From: Ray Olszewski [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 2:10 PM To: [EMAIL PROTECTED] Subject: Re: [leaf-user] Bering can't handle Dell GX150 integrated Ethernet? A few details to consider. 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)? Only tried the first one (.../2.4.20/net The other one did work !!! Thanks for pointing it out.. I answered the rest of your questions (from bottom to top) before trying the other module -- so FYI. 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)? Ah-hah. An insmod command results in a gazillion unresolved symbol stmts. 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. I downloaded the (first) 3c59x.o from /devel/jnilo/bering/lastest/modules/2.4.20/net The Bering installation guide led me partway along that link. "I vas ohnly following ohrdahs" ;-) 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. Yep. My RH9 tells me they are both 3c905 (one is B and the other is C) 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? Nope, no lspci command. 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? The syslog (in /var/logs) says that something couldn't find the map file. Other than that there are no error messages. 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? -----Original Message----- From: Tony [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 8:15 AM Cc: [EMAIL PROTECTED] Subject: Re: [leaf-user] Bering can't handle Dell GX150 integrated Ethernet? Wouldn't this be accomplished in the modules config, where you identify the modules you want to load? ========= #ne2k-pci # card1,card2 #ne io=0x300,0x350 ========= As I found out, some modules (3c509 for example) don't take these arguments, some modules do (smc-ultra). I would grab the source for the modules and read it to see if there are any clues in there. Good Luck Tony Henning Jebsen wrote: > >> With Bering, using the 3c59x.o module found via the Bering >> installation guide, neither interface is brought up. > > > Did you try to append a boot-Parameter like > ether=0,0,eth0 ether=0,0,eth1 > > The exact syntax for ether= may be found in the ethernet-howto: > ---- snip > There are two ways that you can enable auto-probing for the second > (and third, and...) card. The easiest method is to pass boot-time > arguments to the kernel, which is usually done by LILO. Probing for > the second card can be achieved by using a boot-time argument as > simple as ether=0,0,eth1. In this case eth0 and eth1 will be assigned > in the order that the cards are found at boot. Say if you want the > card at 0x300 to be eth0 and the card at 0x280 to be eth1 then you > could use > LILO: linux ether=5,0x300,eth0 ether=15,0x280,eth1 > ---- snip > > > good luck > > > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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 ------------------------------------------------------- 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 ------------------------------------------------------- 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
