em0 Intel Gigabit card, rc.conf processing on boot

[Michael Clark]

Still having frustrating problems with em0 intel card.
Here is a copy of the dmesg.  I have tried adding sleep statements
to the rc files, with no success.  The card still becomes active
after the rc.conf processing.


Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 5.2.1-RELEASE-p8 #0: Wed Jun 30 11:25:22 CDT 2004
    root at monitor.nemschoff.com:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xc09e3000.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (601.37-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x681  Stepping = 1
 
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
PA
T,PSE36,MMX,FXSR,SSE>
real memory  = 268419072 (255 MB)
avail memory = 251097088 (239 MB)
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00f0e70
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> at pcibus 0 on
motherboard
pci0: <PCI bus> on pcib0
pci_cfgintr: 0:4 INTD BIOS irq 5
pci_cfgintr: 0:9 INTA BIOS irq 5
pci_cfgintr: 0:10 INTA BIOS irq 10
pci_cfgintr: 0:11 INTA BIOS irq 11
agp0: <Intel 82443BX (440 BX) host to PCI bridge> mem 0xe4000000-0xe7ffffff
at d
evice 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0xb800-0xb80f at device 4.1 on
pci
0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xb400-0xb41f irq 5 at
dev
ice 4.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.
piix0: <PIIX Timecounter> port 0xe800-0xe80f at device 4.3 on pci0
Timecounter "PIIX" frequency 3579545 Hz quality 0
fxp0: <Intel 82551 Pro/100 Ethernet> port 0xb000-0xb03f mem
0xe1800000-0xe181fff
f,0xe2000000-0xe2000fff irq 5 at device 9.0 on pci0
fxp0: Ethernet address 00:07:e9:1b:a3:34
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: <Intel 82551 Pro/100 Ethernet> port 0xa800-0xa83f mem
0xe0800000-0xe081fff
f,0xe1000000-0xe1000fff irq 10 at device 10.0 on pci0
fxp1: Ethernet address 00:07:e9:1b:a2:c4
miibus1: <MII bus> on fxp1
inphy1: <i82555 10/100 media interface> on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.19> port
0xa400-0xa43f
 mem 0xdf800000-0xdf81ffff,0xe0000000-0xe001ffff irq 11 at device 11.0 on
pci0
em0:  Speed:N/A  Duplex:N/A
orm0: <Option ROMs> at iomem
0xd4000-0xd4fff,0xd0000-0xd17ff,0xcc000-0xcd7ff,0xc
8000-0xcbfff,0xc0000-0xc7fff on isa0
pmtimer0 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port
0x3f7,0x3f
0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0400> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0700> can't assign resources (port)
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0303> can't assign resources (port)
Timecounter "TSC" frequency 601366049 Hz quality 800
Timecounters tick every 10.000 msec
GEOM: create disk ad0 dp=0xc2d82e60
ad0: 38166MB <WDC WD400JB-00ENA0> [77545/16/63] at ata0-master UDMA33
acd0: CDROM <50X CD-ROM> at ata1-master PIO4
Mounting root from ufs:/dev/ad0s1a
em0: Link is up 1000 Mbps Full Duplex
fxp1: promiscuous mode enabled

Michael Clark
Nemschoff Chairs Inc
mclark at nemschoff dot com
CompTIA A+, Network+, Server+, MCP
Voice: (920) 457 7726 x294
Fax:  (920) 453 6594


-----Original Message-----
From: Tom Parquette [mailto:BCSFD204 at twcny.rr.com]
Sent: Tuesday, June 29, 2004 12:50 AM
To: Michael Clark
Cc: freebsd-questions at freebsd.org
Subject: Re: em0 Intel Gigabit card, rc.conf processing on boot


Michael Clark wrote:
> I have 2 fxp Intel 100mb cards in this machine that work fine.  I have ran
> it with 3 fxp 
> cards in the past.  I added an em0, Intel gigabit this morning.  The card
> displays a 
> non active status during the boot process.  RC.conf is processed and the
> card
> does not get an ip address, while the fxp cards do.  Later in the boot
> process
> in bright white letters it shows the card status has changed to active.  I
> believe my
> problems getting rc.conf to assign the IP address are related to this.
Any
> suggestions
> would be appreciated.
> 
> 5.2-p2 (feb)
> 
> 
> Michael Clark
> Nemschoff Chairs Inc
> mclark at nemschoff dot com
> CompTIA A+, Network+, Server+, MCP
> Voice: (920) 457 7726 x294
> Fax:  (920) 453 6594
> 
> 
> CONFIDENTIALITY NOTE: This electronic transmission, including all
> attachments, is directed in confidence solely to the person(s) to whom it
is
> addressed, or an authorized recipient, and may not otherwise be
distributed,
> copied or disclosed. The contents of the transmission may also be subject
to
> intellectual property rights and all such rights are expressly claimed and
> are not waived. If you have received this transmission in error, please
> notify the sender immediately by return electronic transmission and then
> immediately delete this transmission, including all attachments, without
> copying, distributing or disclosing same. 
> 
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"
> 

Your question is almost exactly the one I posted on current at .
The difference is, I'm using a 3Com 3C996B-T.
Question for you: When the card announces that it is active, do you get 
a kernel message along the lines of em0 Gigabit interface active? 
That's what mine does (obviously mine is a bge0 not an em0.  :-)

The one response I got on current@ indicated he had some Netgear cards 
running without a problem.

<ponder mode>
I'm not sure where I'm going with this information except to think there 
may be something about gigabit cards that FBSD may not [completely?] 
account for.
</ponder mode>
Cheers...
_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"


CONFIDENTIALITY NOTE: This electronic transmission, including all
attachments, is directed in confidence solely to the person(s) to whom it is
addressed, or an authorized recipient, and may not otherwise be distributed,
copied or disclosed. The contents of the transmission may also be subject to
intellectual property rights and all such rights are expressly claimed and
are not waived. If you have received this transmission in error, please
notify the sender immediately by return electronic transmission and then
immediately delete this transmission, including all attachments, without
copying, distributing or disclosing same.