NIC driver for Netgear ReadyNAS NVX (Intel 'Tolapai' EP80579 SoC)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • NIC driver for Netgear ReadyNAS NVX (Intel 'Tolapai' EP80579 SoC)

      Hi,
      Merry Christmas and Happy New Year :)

      I'm trying to install OMV 1.0.20 on my Netgear ReadyNAS NVX, which uses an Intel EP80579 CPU/SoC (a.k.a. Intel Tolapai, a x86 32-bit SoC with embedded gigabit Ethernet).
      I can access the mainboard BIOS and boot from an USB pen, start OMV installation and see it through the RS232 console (no VGA on this NAS unit). The problem is that Debian doesn't recognize the embedded NIC. Intel has a driver for linux available, but only for kernel 2.6.x, not for Wheezy. I can't find a working driver anywhere, and compiling/porting the driver source to compile on kernel 3.x is a bit too complex for me. I also looked at the Intel e1000e driver to see if I could add the PnP IDs for Tolapai's Ethernet, but there's a lot of hardware specific code, and not enough info available to do this.

      Can anyone help, please? Are there other solutions/workarounds ? A precompiled driver would be ideal :)

      Thanks,
      Zybex
    • Hey Subzero, thanks for replying!
      This is not a separate chipset per se, this a a System-on-chip (SoC), a full all-in-one CPU+chipset, including the ethernet controller:
      Specs: en.wikipedia.org/wiki/Tolapai
      Datasheet: intel.com/content/www/us/en/in…oduct-line-datasheet.html

      The latest driver I found is here (Intel driver for Linux kernel 2.6.x); it has no README or any other compile instructions. I did fix the first few compile errors on Debian 7.7, but still got many more to fix.
      downloadmirror.intel.com/17759…se.Patch.L.1.0.7-5.tar.gz

      Product download page is here, with older drivers (intel download site seems to be down right now).
      Most of the embedded devices are relatively unknown, since these are very market-specific chips. LSpci shows mostly a lot of unknown device IDs, including the 3 gigabit ports:

      Terabox:~# lspci
      00:00.0 Host bridge: Intel Corporation Unknown device 5020 (rev 01)
      00:00.1 Class ff00: Intel Corporation Unknown device 5021 (rev 01)
      00:01.0 System peripheral: Intel Corporation Unknown device 5023 (rev 01)
      00:02.0 PCI bridge: Intel Corporation Unknown device 5024 (rev 01)
      00:03.0 PCI bridge: Intel Corporation Unknown device 5025 (rev 01)
      00:04.0 PCI bridge: Intel Corporation Unknown device 5037 (rev 01)
      00:1d.0 USB Controller: Intel Corporation Unknown device 5033 (rev 01)
      00:1d.7 USB Controller: Intel Corporation Unknown device 5035 (rev 01)
      00:1f.0 ISA bridge: Intel Corporation Unknown device 5031 (rev 01)
      00:1f.2 SATA controller: Intel Corporation Unknown device 5029 (rev 01)
      00:1f.3 SMBus: Intel Corporation Unknown device 5032 (rev 01)
      01:00.0 Ethernet controller: Intel Corporation Unknown device 5040 (rev 01)
      01:01.0 Ethernet controller: Intel Corporation Unknown device 5044 (rev 01)
      01:02.0 Ethernet controller: Intel Corporation Unknown device 5048 (rev 01)

      01:03.0 Class ff00: Intel Corporation Unknown device 503e (rev 01)
      01:04.0 Serial bus controller [0c09]: Intel Corporation Unknown device 5039 (rev 01)
      01:05.0 Serial bus controller [0c09]: Intel Corporation Unknown device 503a (rev 01)
      01:06.0 Communication controller: Intel Corporation Unknown device 503b (rev 01)
      01:07.0 Communication synchronizer: Intel Corporation Unknown device 503c (rev 01)
      01:08.0 Bridge: Intel Corporation Unknown device 503d (rev 01)
      01:09.0 Co-processor: Intel Corporation Unknown device 502c (rev 01)
      01:0a.0 System peripheral: Intel Corporation Unknown device 503f (rev 01)
      01:0c.0 Performance counters: Intel Corporation Unknown device 5030 (rev 01)
      03:00.0 IDE interface: Marvell Technology Group Ltd. Unknown device 6121 (rev b2)

      Thanks for helping :)
    • You're not gonna find here kernel driver developers. What you can do is install omv 0.5 then upgrade to wheezy and 1.0. And keep booting omv 1.0 with the old kernel. No idea what will come from that
      Other than that I remember you can insert vendor id and model id into built modules. I did it a long time ago. This is the information that I've found.
      ha19.no/usb/
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server