Re: cardbus wired NIC trouble, any suggestions?
On Tue, Nov 01, 2011 at 12:11:44AM +0100, Christoph Egger wrote:
> Hi Yongari!
> Adding you into the loop as per suggestion by Robert Millan. I'm
> having trouble getting my cardbus NIC to work on the FreeBSD
> kernel. Apart from the debian 8.2 9.0 and 10.0 Kernels I have now also
> tested the "original" FreeBSD 9.0 RC1 memory stick image (from
> www.freebsd.org) which exhibits the exact same problem detailed below. I
> don't have a problem with patching and recompiling my kernel if I can be
> of any help.
I'm not familiar with Cardbus based controller so I have no clean
idea how to attack this at this moment. Basically all Cardbus
controllers are seen as PCI device in device driver. Because re(4)
successfully attached to the controller and re(4) supports RTL8110
based controller I think you may want to try enabling a loader
tunable like the following in /boot/loader.conf file.
If /boot/loader.conf does not exist on your box, try crate it and
reboot and let me know whether that makes any difference on your box.
> Christoph Egger <email@example.com> writes:
> > I bought a Dlink DGE-660TDE cardbus NIC not thinking that there might
> > be any trouble with wired NICs and freebsd. It seems to be based on a
> > fairly common ralink 8110 or 8169 (depending which tool you ask) and
> > doesn't work on kfreebsd (-8 -9 and -10 with and without firmware
> > enhancement):
> > re0: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port 0x9000-0x90ff mem 0xe4303000-0xe43031ff irq 16 at device 0.0 on cardbus0
> > re0: Chip rev. 0x10000000
> > re0: MAC rev. 0x00000000
> > re0: PHY write failed
> > re0: PHY write failed
> > re0: PHY read failed
> > re0: attaching PHYs failed
> > device_attach: re0 attach returned 6
> > lspci:
> > 16:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
> > Subsystem: D-Link System Inc Device 4301
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Latency: 168 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
> > Interrupt: pin A routed to IRQ 16
> > Region 0: I/O ports at 9000
> > Region 1: Memory at e4303000 (32-bit, non-prefetchable)
> > Expansion ROM at cfdc0000 [disabled]
> > Capabilities: [dc] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
> > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> > pciconf -lv (freebsd chroot):
> > re0@pci0:22:0:0: class=0x020000 card=0x43011186 chip=0x816910ec rev=0x10 hdr=0x00
> > vendor = 'Realtek Semiconductor'
> > device = 'Single Gigabit LOM Ethernet Controller (RTL8110)'
> > class = network
> > subclass = ethernet
> > Google turned some stuff up for combinations of chipset / errormessage
> > and freebsd. However most, if not all points to stuff that is said to at
> > least be fixed in 8/stable so I wouldn't expect any of these to turn up
> > on -9.
> > Anyone an idea for debugging this further?
> > Regards
> > Christoph
> 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
> Debian Developer | Lisp Hacker | CaCert Assurer