netdev - Realtek 8169 based device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOkhdCf-emWHJ0rB9GtC3MnX6oj3jgRAbYJU+q65GzMUdXmd-Q@mail.gmail.com>
Date:	Fri, 3 Feb 2012 10:17:06 +0000
From:	Andy Hawkins <adhawkins@...il.com>
To:	netdev@...r.kernel.org
Subject: Realtek 8169 based device

Hi,

Firstly, apologies if this is the wrong place to ask this. Please let
me know if somewhere else is more appropriate.

Secondly, I realise that the kernel I'm using here is quite old.
However, this is the kernel provided by the version of Openfiler I'm
using, so updating isn't a simple matter.

I've just installed a Zyxel GN680T NIC into a PC (purchased here:
http://www.dabs.com/products/zyxel-gn680t-gigabit-pci-network-card-75Q5.html).
Initially it wasn't recognised by the device.

lspci -vv reports:

03:01.0 Ethernet controller: Hynix Semiconductor Unknown device 8169 (rev 10)
        Subsystem: Hynix Semiconductor Unknown device 8169
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR+
        Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at de00 [size=256]
        Region 1: [virtual] Memory at fdaff000 (32-bit,
non-prefetchable) [size=256]
        [virtual] Expansion ROM at fd900000 [disabled] [size=128K]
        Capabilities: [5c] #00 [0000]

lspci -n reports:

03:01.0 0200: 106c:8169 (rev 10)

I had a look at the driver source, and it didn't appear to be
correctly recognising the PCI IDs. I managed to recompile the module,
adding in support for this device as follows:

        { PCI_DEVICE(0x106c,    0x8169), 0, 0, RTL_CFG_0 },

When I load this new module, the device is correctly recognised, and
ethtool can give sensible information and report negotiated link
speeds etc. However the network card fails to work (I'm pretty sure it
was reporting transmit time outs).

Can anyone offer any advice on getting this card to work?

Thanks

Andy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html