order of enet interface drivers
Hello; I have two identical intel interface cards installed in a ASUS N2M32 pro motherboard. The os version is 6.2 GENERIC running on AMD64, socket AM2. The motherboard has dual interfaces that use Marvell drivers. I cannot use these with this version of FreeBSD as yet. So I got two Intel interface cards that work in PCIe slots. Because of the hardware component situation on this motherboard I cannot use the interfaces in PCIe lane one slots as on of these slots is blocked, physically, and the card will not fit. So I am using the two PCIe lane 16 slots. I modified rc.conf (see PS at bottom) to bring up the interfaces at boot. They both come up and running with network addressess assigned, as em0 an em1. The problem: I can ping em0 from local host and connect to ftp and ssh from the inside network, all is well I cannot ping em1. ifconfig shows it up and running, with no carrier, I.E. no network cable attached but I should be able to ping it from local host, yes? no? Yes. Here is the obvious question the order of interfaces listed by ifconfig is em0 fwe0 em1 the question is: Is it possible that fwe is blocking em1? I have fwe0 down and took it out of rc.conf so it does not come up on boot but still shows up in this order with ifconfig. If this is possible, how do I tell the system to load fwe0 after em1 or not at all to see if I can ping it successfully? copied from ifconfig output: em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.1.16 netmask 0xff00 broadcast 192.168.1.255 ether 00:15:17:19:2c:89 media: Ethernet autoselect (100baseTX full-duplex) status: active fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 options=8VLAN_MTU ether 02:11:d8:bf:40:d4 ch 1 dma -1 em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255 ether 00:15:17:19:2a:b7 media: Ethernet autoselect status: no carrier ping results: am2# ping -c 1 em1 ping: cannot resolve em1: Host name lookup failure am2# ping -c 1 192.168.1.17 PING 192.168.1.17 (192.168.1.17): 56 data bytes --- 192.168.1.17 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss am2# Any clues? Jeff K (being necessarily philosophical at this point) PS I say I edited rc.conf to make network changes because I got the syntax correct for doing this. It does work, not with commands, just variable/value assignments JK ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: order of enet interface drivers
On Saturday 24 March 2007 8:38 pm, jekillen wrote: Hello; I have two identical intel interface cards installed in a ASUS N2M32 pro motherboard. The os version is 6.2 GENERIC running on AMD64, socket AM2. The motherboard has dual interfaces that use Marvell drivers. I cannot use these with this version of FreeBSD I'm working on a similar board. have you looked at: http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html I'm having success with this approach. Ray as yet. So I got two Intel interface cards that work in PCIe slots. Because of the hardware component situation on this motherboard I cannot use the interfaces in PCIe lane one slots as on of these slots is blocked, physically, and the card will not fit. So I am using the two PCIe lane 16 slots. I modified rc.conf (see PS at bottom) to bring up the interfaces at boot. They both come up and running with network addressess assigned, as em0 an em1. The problem: I can ping em0 from local host and connect to ftp and ssh from the inside network, all is well I cannot ping em1. ifconfig shows it up and running, with no carrier, I.E. no network cable attached but I should be able to ping it from local host, yes? no? Yes. Here is the obvious question the order of interfaces listed by ifconfig is em0 fwe0 em1 the question is: Is it possible that fwe is blocking em1? I have fwe0 down and took it out of rc.conf so it does not come up on boot but still shows up in this order with ifconfig. If this is possible, how do I tell the system to load fwe0 after em1 or not at all to see if I can ping it successfully? copied from ifconfig output: em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.1.16 netmask 0xff00 broadcast 192.168.1.255 ether 00:15:17:19:2c:89 media: Ethernet autoselect (100baseTX full-duplex) status: active fwe0: flags=108802BROADCAST,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 options=8VLAN_MTU ether 02:11:d8:bf:40:d4 ch 1 dma -1 em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255 ether 00:15:17:19:2a:b7 media: Ethernet autoselect status: no carrier ping results: am2# ping -c 1 em1 ping: cannot resolve em1: Host name lookup failure am2# ping -c 1 192.168.1.17 PING 192.168.1.17 (192.168.1.17): 56 data bytes --- 192.168.1.17 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss am2# Any clues? Jeff K (being necessarily philosophical at this point) PS I say I edited rc.conf to make network changes because I got the syntax correct for doing this. It does work, not with commands, just variable/value assignments JK ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: order of enet interface drivers
On Mar 24, 2007, at 6:20 PM, Ray wrote: On Saturday 24 March 2007 8:38 pm, jekillen wrote: Hello; I have two identical intel interface cards installed in a ASUS N2M32 pro motherboard. The os version is 6.2 GENERIC running on AMD64, socket AM2. The motherboard has dual interfaces that use Marvell drivers. I cannot use these with this version of FreeBSD I'm working on a similar board. have you looked at: http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html I'm having success with this approach. Ray Thank you for the info. If you like to read, you can hack through my sob story: I have gotten this reference in a query on this issue when I first assembled the board and did not get the two interfaces to show up. I did retrieve the code from this link but I decided against it for the time being. I have not worked with the kernel yet and am trying to get this server up and running. It has been a real circus to date. First I thought PCIe slots would use my 64 bit SCSI card, no way. I had to buy the ASUS board because it was he only AMD64 board I could find with PCIx slots. And because the ASUS board did not have a AMD 939 socket, I had to buy another processor for AM2 socket and I had to then buy DDR2 memory because the ASUS board required it. So I now have one Gigabyte motherboard and AMD64 939 processor and a Gb of DDR memory I cannot use. I then discovered the problem with the onboard inet interfaces. Now I am having serious trouble getting Apache 1.3.37 and php 5 to work together, They won't because for some reason libphp5.so is not being produced when php is configured, built and installed. That is another issue. All I really would like to know at this point is how to get fwe0 to load in a different order so I can eliminate that as a problem or solve it. I am working on a very large php project and if I cannot get php to work with Apache on this machine it is all in vain. Yes I know about ports, and yes I have been greeted with disdain on this list because I have been bypassing ports to install this stuff from source. I have done it successfully on two other FreeBSD Machines with FBSD 6.0 Apache 1.3.34 and php 5.1.2. On this machine I have FBSD 6.2, Apache 1.3.37 and have tried php5.2.1 and 5.1.2 and have had the same problem. I am suspecting either the apxs script with Apache or something in the FBSD install with make or autoconf. But I am not a computer scientist. So now that I have bent your ear all the way around your head. How do I tell FreeBSD to load interface drivers in a different order or is it really an issue? Thanks Jeff K ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
