thr3ads.net - freebsd stable - interface re0 [Mar 2007]

If this information is useful, please help other people find it:
Share via:

Eilko Bos

2007-Mar-20 23:26 UTC

interface re0

Hi,

I recently bought a Sweex Gigabit nic. Loading if_re.ko did not result in an
extra interface, after cvsupping (RELENG_6) and rebuilding the kernel, I still
see this message:

re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
0xb800-0xb8ff mem 0xf7000000-0xf70000ff irq 11 at device 15.0 on pci0
re0: MII without any phy!
device_attach: re0 attach returned 6

Does anybody have an idea how this can be fixed? This is my complete dmesg-
output:

-----------------------
Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-STABLE #0: Tue Mar 20 23:26:15 CET 2007
    root@xena.home.brasapen.org:/usr/src/sys/i386/compile/XENA
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(TM)Processor (1000.04-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x642  Stepping = 2
 
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
T,PSE36,MMX,FXSR>
  AMD Features=0xc0440800<SYSCALL,<b18>,MMX+,3DNow+,3DNow>
real memory  = 268353536 (255 MB)
avail memory = 257282048 (245 MB)
kbd1 at kbdmux0
acpi0: <ASUS A7V266-E> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <VIA 8367 (KT266/KY266x/KT333) host to PCI bridge> mem
0xfc000000-0xfdffff
ff at device 0.0 on pci0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
pci0: <multimedia, audio> at device 5.0 (no driver attached)
ed0: <RealTek 8029> port 0xd400-0xd41f at device 13.0 on pci0
ed0: Ethernet address: 52:54:05:df:a6:4e
ed0: type RTL8029 (16 bit) 
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem
0xf7800000-0xf780
007f at device 14.0 on pci0
miibus0: <MII bus> on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:10:5a:cb:2f:c7
re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
0xb800-0xb8ff mem
 0xf7000000-0xf70000ff at device 15.0 on pci0
re0: MII without any phy!
device_attach: re0 attach returned 6
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 8233 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,
0xb400-0xb40f at device 17.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <serial bus, USB> at device 17.2 (no driver attached)
pci0: <serial bus, USB> at device 17.3 (no driver attached)
pci0: <serial bus, USB> at device 17.4 (no driver attached)
fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on
acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcafff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 1000042585 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 39205MB <Maxtor 2F040J0 VAM51JJ0> at ata0-master UDMA100
acd0: CDRW <SAMSUNG CD-R/RW DRIVE SW-252F/R802> at ata1-master UDMA33
Trying to mount root from ufs:/dev/ad0s1a
re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
0xb800-0xb8ff mem
 0xf7000000-0xf70000ff irq 11 at device 15.0 on pci0
re0: MII without any phy!
device_attach: re0 attach returned 6
uhci0: <VIA 83C572 USB controller> port 0xb000-0xb01f irq 9 at device 17.2
on pc
i0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xa800-0xa81f irq 9 at device 17.3
on pc
i0
uhci1: [GIANT-LOCKED]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <VIA 83C572 USB controller> port 0xa400-0xa41f irq 9 at device 17.4
on pc
i0
uhci2: [GIANT-LOCKED]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pci0: <network, ethernet> at device 15.0 (no driver attached)
re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
0xb800-0xb8ff mem
 0xf7000000-0xf70000ff irq 11 at device 15.0 on pci0
re0: MII without any phy!
device_attach: re0 attach returned 6
----------------------------------

Kind regards,
--
Eilko

Tom Samplonius

2007-Mar-21 03:54 UTC

head link

interface re0

----- "Eilko Bos" <eilko@bos-zuidema.nl> wrote:
...> I still
> see this message:
> 
> re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
> 0xb800-0xb8ff mem 0xf7000000-0xf70000ff irq 11 at device 15.0 on pci0
> re0: MII without any phy!
> device_attach: re0 attach returned 6
> 
> Does anybody have an idea how this can be fixed? This is my complete...

  Well, MII, stands for media-independent-interface.  Since there are many
different types of ethernet media, the idea was to develop a standard hardware
interface for the media chip (which is called the PHY).  Then you can can
connect any media chip to any controller chip, and you'd have a NIC. 
Apparently, your card claims to have use a MII, but when the driver probes the
MII, it does not find a PHY.  But your NIC might not actually use the MII, and
might have the PHY function directly incorporated in the NIC (the
"Single-chip" reference is a hint).

  I recommend you do a rebose boot (which will print the PCI id of the card),
and attach it to  a PR.  Perhaps the re maintainer can hack the driver for a
special exception for your NIC.

  But em cards (Intel Pro1000GT Desktop) cards are very cheap, and do work.  Why
buy RealTek?  RealTek has been outputting overly simplistic hardware since the
beginning.  If there was a corner that could be cut when building a NIC, a
RealTek engineer thought of it first.

Tom

Eilko Bos

2007-Mar-21 08:12 UTC

head link

interface re0

Hi,
>From the keyboard of Tom Samplonius, written on Tue, Mar 20, 2007 at
08:56:57PM -0700:
> > re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
> > 0xb800-0xb8ff mem 0xf7000000-0xf70000ff irq 11 at device 15.0 on pci0
> > re0: MII without any phy!
> > device_attach: re0 attach returned 6
> > 
> > Does anybody have an idea how this can be fixed? This is my complete
> ...
> 
>   I recommend you do a rebose boot (which will print the PCI id of the
card), and attach it to  a PR.  Perhaps the re maintainer can hack the driver
for a special exception for your NIC.
Spooky, I removed the other cards (xl0/3com and ed0), rebooted and the card was
recognized. Then I inserted the NICS again, one by one, each time followed by
a reboot to see if the card keeps working. Now it works every time I boot the
system:

ed0: <RealTek 8029> port 0xd400-0xd41f at device 13.0 on pci0
ed0: Ethernet address: 52:54:05:df:a6:4e
ed0: type RTL8029 (16 bit) 
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem
0xf7800000-0xf780
007f at device 14.0 on pci0
miibus0: <MII bus> on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:10:5a:cb:2f:c7
re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
0xb800-0xb8ff mem
 0xf7000000-0xf70000ff at device 15.0 on pci0
miibus1: <MII bus> on re0
rgephy0: <RTL8169S/8110S media interface> on miibus1
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-F
DX, auto
re0: Ethernet address: 00:16:0a:05:71:5f
re0: [FAST]

However, this behaviour does not give me a real good feeling...
>   But em cards (Intel Pro1000GT Desktop) cards are very cheap, and do work.
Why buy RealTek?  RealTek has been outputting overly simplistic hardware since
the beginning.  If there was a corner that could be cut when building a NIC, a
RealTek engineer thought of it first.
I asked a friend to buy me a 100Mbit NIC (he works next to a computer store),
but those were out of stock. So he bought me this one and since it is
recognized (as re0) I assumed it would work :) And because it does right now,
I can live with it. It is not a critical interface, if it happens again that
it does not work, I will post the pciconf -lv output.

Grtz,
--
Eilko.

freebsd stable - Mar 2007 - interface re0

interface re0

interface re0

interface re0