PCI-e card denying network connections when installed?

    • OMV 4.x
    • PCI-e card denying network connections when installed?

      I have an new NAS build - I'm a bit of a noob. I have installed OMV 4.0.14. Install went fine, installed extras, etc. Have Plex server running, network connection and SMB sharing on multiple PCs on my network. NAS operates as expected.

      Decided to install Hauppauge WinTV-quadHD PCI-e card so I can start streaming and recording OTA broadcasts.

      When I install the card in it causes the NAS to stop connecting to the network; it throws an error as it is booting and running through all the pass/fails regarding network interfaces being unable to be established.

      I ran through the install for the card located here: hauppauge.com/site/support/linux.html and had no problems...or so I think.

      Has anyone else run across this issue and found a good fix for it?

      Thanks
    • The problem i see is that they are distributing a whole Linux kernel package to give the drivers. they should either supply a dkms package or the drivers source, not a whole kernel for just one driver.

      Just to make sure for your card to work you need to boot their supplied kernel. Use Omv-extras to select their boot kernel or at boot time with grub, then check everything works.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • LordZ wrote:

      I would use the recommends from the wiki at linuxtv.org. With their help, I managed to get my dvb card to work correctly. For your card they recommend either no extra files for the northern American version or one fw file for the european version.

      See here:

      linuxtv.org/wiki/index.php/Hau…WinTV-quadHD_(DVB-T/T2/C)
      This is what is confusing - for North America there are no additional files to load and the kernel (4.8) should be supported by current OMV 4.0.14...unless I'm missing something.
    • aetherBRO wrote:

      This is what is confusing - for North America there are no additional files to load and the kernel (4.8) should be supported by current OMV 4.0.14...unless I'm missing something.
      Indeed, no additional firmware or drivers required, full kernel support out of the box.

      Please post ouput of:
      # lspci
      # lsusb
      # cat /proc/interrupts

      You will need to investiage potential IRQ issues ...

      Also, do you have a network controller and/or DHCP server that is somehow part of the issue/cause of the issue? Investigate device IP addresses/mac addresses that are online and visible in the controller to elimnate potential sources of error.

      If you find that there is an IRQ conflict or a DHCP/MAC address issue, you may have the options in your BIOS to manually set the IRQ for the Hauppauge tuner to avoid the interrupt conflict ... and similarly, in your controller, be able to implement a proper configuration to avoid addressing issues.

      Cheers,
      ;)
    • ransur0t wrote:

      Please post ouput of:
      # lspci
      # lsusb
      First screenshot is ethernet connnect via USB adapter, Second is ethernet directly to jack:

      ransur0t wrote:

      aetherBRO wrote:

      This is what is confusing - for North America there are no additional files to load and the kernel (4.8) should be supported by current OMV 4.0.14...unless I'm missing something.
      Indeed, no additional firmware or drivers required, full kernel support out of the box.
      Please post ouput of:
      # lspci
      # lsusb
      # cat /proc/interrupts

      You will need to investiage potential IRQ issues ...

      Also, do you have a network controller and/or DHCP server that is somehow part of the issue/cause of the issue? Investigate device IP addresses/mac addresses that are online and visible in the controller to elimnate potential sources of error.

      If you find that there is an IRQ conflict or a DHCP/MAC address issue, you may have the options in your BIOS to manually set the IRQ for the Hauppauge tuner to avoid the interrupt conflict ... and similarly, in your controller, be able to implement a proper configuration to avoid addressing issues.

      Cheers,
      ;)
      First screenshot is ethernet connnect via USB adapter, Second is ethernet directly to jack


      Images
      • IMG_1713.gif

        116.41 kB, 770×334, viewed 232 times
    • ransur0t wrote:

      Please post ouput of:
      # lspci
      # lsusb
      First screenshot is ethernet connnect via USB adapter, Second is ethernet directly to jack:

      ransur0t wrote:

      aetherBRO wrote:

      This is what is confusing - for North America there are no additional files to load and the kernel (4.8) should be supported by current OMV 4.0.14...unless I'm missing something.
      Indeed, no additional firmware or drivers required, full kernel support out of the box.
      Please post ouput of:
      # lspci
      # lsusb
      # cat /proc/interrupts

      You will need to investiage potential IRQ issues ...

      Also, do you have a network controller and/or DHCP server that is somehow part of the issue/cause of the issue? Investigate device IP addresses/mac addresses that are online and visible in the controller to elimnate potential sources of error.

      If you find that there is an IRQ conflict or a DHCP/MAC address issue, you may have the options in your BIOS to manually set the IRQ for the Hauppauge tuner to avoid the interrupt conflict ... and similarly, in your controller, be able to implement a proper configuration to avoid addressing issues.

      Cheers,
      ;)
      First screenshot is ethernet connnect via USB adapter, Second is ethernet directly to jack