RE: Intel NIC issues
I opened the case and the motherboard does not match what was supposed to be in the machine. I will contact the supplier and see what happens from there. Maybe it was just a mistake, but i bet not. At least here putting other cheaper products in computer and getting a price for the expensive one - is very common practice in polish shops. Simply because most people buy more expensive because it's "better" and will not see a difference then - so such cheating works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Intel NIC issues
-Original Message- From: Graeme Dargie [mailto:a...@tangerine-army.co.uk] Sent: 02 June 2009 21:56 To: freebsd-questions@freebsd.org Subject: Intel NIC issues I opened the case and the motherboard does not match what was supposed to be in the machine. I will contact the supplier and see what happens from there. Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Intel NIC issues
On Tue, Jun 2, 2009 at 4:07 PM, Erik Trulsson wrote: Using kenv smbios.system.product might be a good indication of what you have too. Running "kenv smbios.system.product" on two of my machines with Supermicro motherboards gives me "P4SSE" and "P4DC6" which are both correct. I know Supermicro has made variants of boards for vendors; for example, I have a P4DC6 which has no RAID card slot (the solder pads are there, not the card connector) although this is alleged to be a standard feature of the P4DC6 in the Supermicro manual. I have a 1U server (the P4SSE) with a "bge" gigabit Ethernet NIC; rather than fight with the cards issues I installed an Intel PCI-X gigabit card, cost $15. Now that the "bge" problems appear to be solved I may go back to it, however. (The Intel NIC uses an internal riser which allows for one card). If your vendor promised you two gigabit NICs this may be the cheap solution (other than replacing the motherboard). I'm using Intel Pro/1000 and Pro/100 cards exclusively, except in a notebook, and I've never found FreeBSD to incorrectly identify the card. Mike Squires ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Intel NIC issues
On Tue, Jun 2, 2009 at 4:07 PM, Erik Trulsson wrote: > On Tue, Jun 02, 2009 at 09:56:01PM +0100, Graeme Dargie wrote: > > Hi all > > > > > > > > Ok lets not go to war over this I just need some advice. > > > > > > > > I have a 1u rack system that has one of these motherboards > > http://www.supermicro.com/products/motherboard/Xeon/E7501/X5DPR-iG2+.cfm > > Are you *sure* that you actually have that particular motherboard? > > As you can see if you look through their product listings > ( http://www.supermicro.com/products/motherboard/Xeon1333/#e7501 ) > Supermicro has > several other similar models, some of which are equipped with one Gigabit > NIC and one 100Mbit NIC much like you seem to have.. > > > > > > > > > Now according to where I got the server and that page it is supposed to > > have dual gigabit nics on board. > > > > > > > > Dmesg shows the following > > > > > > > > em0: port 0x3000-0x301f mem > > 0xfc22-0xfc23,0xfc20-0xfc21 irq 31 at device 4.0 on pci3 > > > > em0: [FILTER] > > > > em0: Ethernet address: 00:30:48:24:84:f2 > > > > > > > > fxp0: port 0x4400-0x443f mem > > 0xfc321000-0xfc321fff,0xfc30-0xfc31 irq 17 at device 2.0 on pci4 > > > > miibus0: on fxp0 > > > > inphy0: PHY 1 on miibus0 > > > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > > fxp0: Ethernet address: 00:30:48:24:84:f3 > > > > fxp0: [ITHREAD] > > > > > > Now for reasons I can not fathom, one nic is showing just fine and the > > other is using a different driver and only speeds of upto 100mbs. > > The obvious reason is that there is two different ethernet controllers > on that board - one Gigabit and one 100Mbit. > > It is worth noting that according to the above, they are found on different > PCI-buses, while the dual-gigabit controller you thought you had is a > single > chip where obviously both ports would be connected to the same bus. > > > > > > > > > I have tried both 7.1 and 7.2 So is the information on the board wrong > > or is there something I am missing. > > Most likely you have a different motherboard than you think you have. > The *complete* dmesg output as well as the output of 'pciconf -lv' might > be useful in determining what you actually have. (Opening the box and > checking for any useful labels on the motherboard can also of course be > useful, but is not something we can help you doing.) > Using kenv smbios.system.product might be a good indication of what you have too. Good luck. Nothing like troubleshooting a piece of hardware from remote. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Intel NIC issues
On Tue, Jun 02, 2009 at 09:56:01PM +0100, Graeme Dargie wrote: > Hi all > > > > Ok lets not go to war over this I just need some advice. > > > > I have a 1u rack system that has one of these motherboards > http://www.supermicro.com/products/motherboard/Xeon/E7501/X5DPR-iG2+.cfm Are you *sure* that you actually have that particular motherboard? As you can see if you look through their product listings ( http://www.supermicro.com/products/motherboard/Xeon1333/#e7501 ) Supermicro has several other similar models, some of which are equipped with one Gigabit NIC and one 100Mbit NIC much like you seem to have.. > > > > Now according to where I got the server and that page it is supposed to > have dual gigabit nics on board. > > > > Dmesg shows the following > > > > em0: port 0x3000-0x301f mem > 0xfc22-0xfc23,0xfc20-0xfc21 irq 31 at device 4.0 on pci3 > > em0: [FILTER] > > em0: Ethernet address: 00:30:48:24:84:f2 > > > > fxp0: port 0x4400-0x443f mem > 0xfc321000-0xfc321fff,0xfc30-0xfc31 irq 17 at device 2.0 on pci4 > > miibus0: on fxp0 > > inphy0: PHY 1 on miibus0 > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > fxp0: Ethernet address: 00:30:48:24:84:f3 > > fxp0: [ITHREAD] > > > Now for reasons I can not fathom, one nic is showing just fine and the > other is using a different driver and only speeds of upto 100mbs. The obvious reason is that there is two different ethernet controllers on that board - one Gigabit and one 100Mbit. It is worth noting that according to the above, they are found on different PCI-buses, while the dual-gigabit controller you thought you had is a single chip where obviously both ports would be connected to the same bus. > > > > I have tried both 7.1 and 7.2 So is the information on the board wrong > or is there something I am missing. Most likely you have a different motherboard than you think you have. The *complete* dmesg output as well as the output of 'pciconf -lv' might be useful in determining what you actually have. (Opening the box and checking for any useful labels on the motherboard can also of course be useful, but is not something we can help you doing.) -- Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Intel NIC issues
em0: port 0x3000-0x301f mem 0xfc22-0xfc23,0xfc20-0xfc21 irq 31 at device 4.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:24:84:f2 fxp0: port 0x4400-0x443f mem 0xfc321000-0xfc321fff,0xfc30-0xfc31 irq 17 at device 2.0 on pci4 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:30:48:24:84:f3 fxp0: [ITHREAD] I have tried both 7.1 and 7.2 So is the information on the board wrong or is there something I am missing. If that board would be really 2*1000Mbps, for sure producer would use 2 the same chips. Then - it's impossible that FreeBSD would detect one chip properly and other - the same - improperly. It's just wrong info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
