How to install drivers? Simple question but I'm a beginner

    • OMV 4.x

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

    • How to install drivers? Simple question but I'm a beginner

      Hi guys!
      This is a simple question but I have no idea how to do it.
      I have my NAS working but due to certain space limitations I have my NAS quite far from the router. I am using an "ethernet over power" device which basically uses the house's wires to transmit ethernet.
      I am having slow transfer rates so I'm trying to troubleshoot where my bottleneck is.
      Given that I used a very old PC, I was worried it could be a very old ethernet port limited to 10MBPS.

      So I bought a new PCIe ethernet card in order to see if using it improves the transfer rate. After I installed the card, it the NAS would not connect to my network. But if I plug the lan cable in my original port then the NAS shows up on the network. This makes me assume it is a driver issue and my new ethernet card is not recognised.

      How on earth do I install drivers on openmediavault? I know how to SSH into the unit but that's basically it. I have no knowledge in linux whatsoever. The adapter is "
      TP-Link TG-3468 " (amazon.com/gp/product/B003CFAT…age_o00_s00?ie=UTF8&psc=1).

      Thanks!
    • gderf wrote:

      Start by running this command and post the results:

      lspci -vv |grep -i ethernet

      From that it should be possible to ID the chipset the card is using and get the driver. Probably a Realtek variant.
      Thank you for replying!
      This is what I get:

      root@Hekmat-Server:~# lspci -vv |grep -i ethernet
      00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
      pcilib: sysfs_read_vpd: read failed: Input/output error
      03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

      Just to be clear, my NAS is currently connected through the older ethernet built-in on the motherboard. The new PCI ethernet is plugged into the motherboard but I don't know if it can "read" it.

      Thanks!
    • gderf wrote:

      Well, I doubt very much that that inexpensive TP Link card has an Intel chip, so it must be Realtek.

      Run this command and post the result:

      uname -a

      Also, it's a good idea to properly tag your posts with the OMV version you are on.
      uname gave this:

      Linux Hekmat-Server 4.17.0-0.bpo.3-amd64 #1 SMP Debian 4.17.17-1~bpo9+1 (2018-08-27) x86_64 GNU/Linux

      I thought I did tag it. It is 4.1.10 arrakis. thanks
    • gderf wrote:

      My bad I didn't see the tag.

      Your kernel is late enough that it should have the driver built in. Run this and post the result:

      ifconfig
      It's ok :)
      Here's the result from tthe ifconfig:

      eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>mtu 1500
      inet 192.168.1.3netmask 255.255.255.0broadcast 192.168.1.255
      ether b8:ca:3a:b0:54:98txqueuelen 1000(Ethernet)
      RX packets 15820bytes 5156140 (4.9 MiB)
      RX errors 0dropped 60overruns 0frame 0
      TX packets 12972bytes 8710060 (8.3 MiB)
      TX errors 0dropped 0 overruns 0carrier 0collisions 0
      device interrupt 20memory 0xf7e00000-f7e20000

      lo: flags=73<UP,LOOPBACK,RUNNING>mtu 65536
      inet 127.0.0.1netmask 255.0.0.0
      inet6 ::1prefixlen 128scopeid 0x10<host>
      looptxqueuelen 1000(Local Loopback)
      RX packets 22283bytes 7488554 (7.1 MiB)
      RX errors 0dropped 0overruns 0frame 0
      TX packets 22283bytes 7488554 (7.1 MiB)
      TX errors 0dropped 0 overruns 0carrier 0collisions 0
    • Mr.Grape wrote:

      apt-get install r8168-dkms
      I got this:
      root@Hekmat-Server:~# apt-get install r8168-dkms
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      E: Unable to locate package r8168-dkms

      gderf wrote:

      I would go here and try the automatic way for debian:

      unixblogger.com/how-to-get-you…68-working-updated-guide/

      Cross your fingers too.
      The same error message for the automatic way...

      Ay suggestion? Does it look like a dead-end?
    • gderf wrote:

      apt-get install r8168-dkms will NOT work unless you have enabled the non-free repo and run apt-get update. Have you done those?
      I believe so. This is what my sources.list shows:

      #

      # deb cdrom:[Debian GNU/Linux 9 _Stretch_ - Official Snapshot amd64 LIVE/INSTALL Binary 20180330-19:01]/ stretch contrib main non-free

      #deb cdrom:[Debian GNU/Linux 9 _Stretch_ - Official Snapshot amd64 LIVE/INSTALL Binary 20180330-19:01]/ stretch contrib main non-free

      deb ftp.us.debian.org/debian/ stretch main
      deb-src ftp.us.debian.org/debian/ stretch main

      deb security.debian.org/debian-security stretch/updates main contrib non-free
      deb-src security.debian.org/debian-security stretch/updates main contrib non-free

      # stretch-updates, previously known as 'volatile'
      deb ftp.us.debian.org/debian/ stretch-updates main contrib non-free
      deb-src ftp.us.debian.org/debian/ stretch-updates main contrib non-free


      Notice the non-free...
    • gderf wrote:

      Not so fast.

      Run

      ifconfig

      and see if the adapter has been picked up.
      this is ifconfig:

      eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>mtu 1500
      inet 192.168.1.3netmask 255.255.255.0broadcast 192.168.1.255
      ether b8:ca:3a:b0:54:98txqueuelen 1000(Ethernet)
      RX packets 24816bytes 26837051 (25.5 MiB)
      RX errors 0dropped 0overruns 0frame 0
      TX packets 10431bytes 2491099 (2.3 MiB)
      TX errors 0dropped 0 overruns 0carrier 0collisions 0
      device interrupt 20memory 0xf7e00000-f7e20000

      enp3s0: flags=4099<UP,BROADCAST,MULTICAST>mtu 1500
      inet 192.168.1.3netmask 255.255.255.0broadcast 192.168.1.255
      ether 50:3e:aa:05:1f:26txqueuelen 1000(Ethernet)
      RX packets 1865bytes 503626 (491.8 KiB)
      RX errors 0dropped 0overruns 0frame 0
      TX packets 158bytes 24636 (24.0 KiB)
      TX errors 0dropped 0 overruns 0carrier 0collisions 0

      lo: flags=73<UP,LOOPBACK,RUNNING>mtu 65536
      inet 127.0.0.1netmask 255.0.0.0
      inet6 ::1prefixlen 128scopeid 0x10<host>
      looptxqueuelen 1000(Local Loopback)
      RX packets 10812bytes 3224280 (3.0 MiB)
      RX errors 0dropped 0overruns 0frame 0
      TX packets 10812bytes 3224280 (3.0 MiB)
      TX errors 0dropped 0 overruns 0carrier 0collisions 0

      If I understand correctly, it is en3s0 which I should set in my openmediavault ethernet settings?
    • gderf wrote:

      OK, enp3s0 is your new adapter.

      Can you disable the on board adapter in the BIOS and reboot?
      Unfrotunately, I don' t think I can, because my NAS is running headless.
      What I did is go to the network interface and add a new ethernet interface with enp3s0. Then I turned off the NAS, plugged the ethernet cable in the new adapter and booted up.

      However I'm not able to access openmediavault. My router tells me there's a wired device on 192.168.1.17 but it doesn't show the device name (it used to show with the older adapter) and trying to reach that ip gives me no result...

      I'll try logging in again through the older adapter make sure the new adapter is setup...
    • If you look at the ifconfig output you'll see that both ethernet adapters have the same IP address. This can't work.

      You might try running

      omv-firstaid

      and try configuring interfaces there.

      You really want the old one deleted or disabled. But that can be a lockout trap if you are headless and something goes wrong.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • gderf wrote:

      If you look at the ifconfig output you'll see that both ethernet adapters have the same IP address. This can't work.

      You might try running

      omv-firstaid

      and try configuring interfaces there.

      You really want the old one deleted or disabled. But that can be a lockout trap if you are headless and something goes wrong.
      I see your point about the 2 of them having the same IP address...
      Honestly I don't think I'm willing to take the risk. The reason I'm doing this was HOPING that my original ethernet is too old and that "updating" it would give me faster transfers. But I'm realizing that I should just appreciate what I have :P meaning a stable functional system and I should probably not mess it up.
      Would there be a way to measure the transfer speed of a file? I would like to see the overall speed of sending a movie from my laptop through the router to the NAS. Is there a way to see this? Maybe after all it's not that terrible and I should just appreciate it as it is..