Pinch

I have been struggling to get gpu passthrough working for some time now, but it just won't work on Unraid. When ESXi is installed on the system, the gf 1070 will pass through fine to a Windows guest, but the same on Unraid will result in code 43 -- the install is a virtual machine. Hyper-V has been set to 'no', but despite of this Windows still clearly states the system is a virtual machine in the task manager*. Nothing's hidden from the guest it seems. Edit: Yeah, turns out Hyper-V should be set to 'yes'. Still didn't fix the problem, but finally got an error in the log. The hardware: Gigabyte Aorus Pro X570 + Asus ROG Strix X570-E Gaming (tried both; same problem) Ryzen X3950 EVGA 1070 I have tried all the xml additions googling help with code 43 will give to no avail. Since the OS is saying it's a virtual machine, I'm not suprised by the Nvidia drivers being aware too... -- this must be the issue, right? Booting without a VNC gpu will give a black screen. ROM has been dumped and set up. Does anyone have any idea why Windows won't get fooled? I am fairly desperate at this point. *On the 'Performance' tab. If the system's not virtual, it will state whether it is virtualization-capable or not.

Has anyone successfully built the custom drivers? I tried twice in two different environments, but got the same script error in both cases. I don't currently have any of the test environments running, so I am unable to provide the exact error -- for now, I'm just curious if anyone's actually managed to build the drivers using the provided scripts?

Sorry, of course: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='openvpn-as' --net='bridge' -e TZ="Europe/Paris" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -p '943:943/tcp' -p '9443:9443/tcp' -p '1194:1194/udp' -v '/mnt/user/appdata/openvpn-as':'/config':'rw' --cap-add=NET_ADMIN 'linuxserver/openvpn-as' Edit: It's fixed, though now idea why. I reinstalled openvpn-as and it threw the "ERROR: Cannot ioctl TUNSETIFF as0t0: Device or resource busy (errno=16)'" in the webui when trying to start the server. Changing nothing, but perhaps trying to start the server a few more times, it was suddenly running and working. It's working, but I don't think the problem is solved.

I am completely stumped by this: My OpenVPN-AS has been running perfectly and then out of nowhere stopped working. When it stopped working I was still able to connect on the TCP port, but after restarting the container a few times, that stopped working too. The unraid server has been restarted to no avail. The logs showed errors pointing to the interface or ports being already in use, which made no sense to me... After having tinkered with some settings (after it stopped working -- setting the container to privileged mode and only listen to UDP on port 1194 in the web ui), I am not seeing any errors in the log, but the server still doesn't listen on the UDP port. Can anyone explain to me what this means: root@Tower:~# netstat -an | grep 943 tcp6 0 0 :::943 :::* LISTEN root@Tower:~# netstat -an | grep 1194 udp6 0 0 :::1194 :::* The web ui (943) is working fine, telnet'ing to 1194 on localhost results in connection refused. UNIX is not my strong suit; what am I to gather from the fact that it doesn't appear to 'LISTEN' on port 1194? If I switch off privileged mode, the errors are back: 2019-08-07T09:22:20+0200 [stdout#info] OVPN 0 ERR: 'Wed Aug 7 09:22:20 2019 ERROR: Cannot ioctl TUNSETIFF as0t0: Device or resource busy (errno=16)' 2019-08-07T09:22:20+0200 [stdout#info] Server Agent initialization status: 2019-08-07T09:22:20+0200 [stdout#info] { 2019-08-07T09:22:20+0200 [stdout#info] "errors": { 2019-08-07T09:22:20+0200 [stdout#info] "iptables_web": [ 2019-08-07T09:22:20+0200 [stdout#info] [ 2019-08-07T09:22:20+0200 [stdout#info] "error", 2019-08-07T09:22:20+0200 [stdout#info] "service failed to start due to unresolved dependencies: set(['web'])" 2019-08-07T09:22:20+0200 [stdout#info] ] 2019-08-07T09:22:20+0200 [stdout#info] ], 2019-08-07T09:22:20+0200 [stdout#info] "openvpn_0": [ 2019-08-07T09:22:20+0200 [stdout#info] [ 2019-08-07T09:22:20+0200 [stdout#info] "error", 2019-08-07T09:22:20+0200 [stdout#info] "process started and then immediately exited: ['Wed Aug 7 09:22:20 2019 ERROR: Cannot ioctl TUNSETIFF as0t0: Device or resource busy (errno=16)']" 2019-08-07T09:22:20+0200 [stdout#info] ], 2019-08-07T09:22:20+0200 [stdout#info] [ 2019-08-07T09:22:20+0200 [stdout#info] "error", 2019-08-07T09:22:20+0200 [stdout#info] "service failed to start or returned error status" 2019-08-07T09:22:20+0200 [stdout#info] ] 2019-08-07T09:22:20+0200 [stdout#info] ], 2019-08-07T09:22:20+0200 [stdout#info] "web": [ 2019-08-07T09:22:20+0200 [stdout#info] [ 2019-08-07T09:22:20+0200 [stdout#info] "error", 2019-08-07T09:22:20+0200 [stdout#info] "process started and then immediately exited: 2019-08-07T09:22:18+0200 [stderr#error] twisted.internet.error.CannotListenError: Couldn't listen on 0.0.0.0:943: [Errno 98] Address already in use." 2019-08-07T09:22:20+0200 [stdout#info] ], 2019-08-07T09:22:20+0200 [stdout#info] [ 2019-08-07T09:22:20+0200 [stdout#info] "error", 2019-08-07T09:22:20+0200 [stdout#info] "service failed to start or returned error status" 2019-08-07T09:22:20+0200 [stdout#info] ] 2019-08-07T09:22:20+0200 [stdout#info] ] 2019-08-07T09:22:20+0200 [stdout#info] }, Netstat is showing the same thing as before. The web ui is loading, but I am unable to sign in using the correct credentials. What happened? Why did this stop working all of the sudden?

I am trying to do the same thing: An Unraid 24/7 file server running a workstation VM with passthrough GPU that is only powered on when needed, but so far the GPU is not powering down when the VM is in any way. Is the answer to this question so obvious it doesn't even merit a response?

Success! Flashing the M1015 on the ASRock resulted in the PAL error, but my trusted old unraid tower with an Asus mb did it without issues. So the M1015 is flashed as an LSI 9211-IT with the latest P17 fw and pass-through is working! I chose to flash the BIOS too, although I have no intention of connecting a boot disk to the controller - is longer boot time really the only drawback of flashing the BIOS? If yes, that's not a problem. An odd thing is that when connecting an old Toshiba 160GB 2.5'' to the M1015 it won't recognize it. It works fine when connecting it to the onboard ASM1062. I have no intention of actually using this disk, but am still wondering why it won't work... I couldn't find a definitive answer for this one: will drive spin-down work? ATM I have a spinner and an SSD connected to the M1015 being passed through; both drives are apparently spun down, which doesn't make sense - my old tower would never show an SSD as spun down, so I don't know if I can trust unraid on this one... EDIT: Silly me, the SSD in the old tower is the cache disk with a lot of plugins running, so even if it was a spinner it would never be spun down - is it normal for unraid to show an SSD as spun down when it's idle?

According to jaddel's link I think I got it wrong: LSI9240 apparently IS the M1015, which can be flashed to an LSI9211. Thanks for the link, jaddel

Hmm, seems like I'm either really unlucky that the ASRock card won't pass-through or there's something wrong with my setup. It doesn't make sense 5.0 doesn't recognize any of the controllers... I took the chance and ordered an M1015... As far as cross flashing goes, I get a lot of hits where people's been flashing it as a LSI-9240-8i, but you mentioned LSI-9211-8i. Any specific reason you're using that controller? Do you happen to have a link of some sort regarding the cross flashing?

I meant the setup utility wouldn't even recognize any controller, so there was no disk available to install to (had one disk hooked up to each controller). 5.5 supports only the Lynx Point controller (don't know about the Marvell controller) 5.1u1 supports both the Lynx Point, ASM1062 and the 88SE9120, but can't pass-through the Marvell 5.0 apparently supports none

Thought I'd give 5.0 a quick try, just to see if it would pass-through the Marvell controller; the initial setup wouldn't recognize any of the three connected controllers, so I think I'm gonna stick with 5.1u1

Think I'll just order the IBM M1015 then... Just to be clear: this card will pass-through (at least using ESXi 5.0), right?

Thanks Keeping this thread on subject, I just moved an ASRock SATA3 (Marvell 88SE9128 / 88SE9120) from the old tower to check if ESXi would recognize it. It does and disks are read fine. But when passing it through to either unRAID or a Win7 VM, neither can see the controller - Win7 doesn't even show anything unrecognized in the system management. I am planning on replacing this controller either way (it only has two ports), but is it odd that ESXi can use it, but apparently not pass it through? Will a different - confirmed working - controller most likely still work?

I have no need for the added features in 5.5, so as long as I'm not the only one having issues, I'll have faith it'll be fixed at some point... If only I knew why plugins aren't being automatically installed, I would be ready to migrate to the new server. It's not really an issue since they can be installed manually, I just hate not knowing why it's not working!

While on the subject of ESXi and unRAID, what's your experience with performance? I am currently not able get more than 50-60MB/s on parity checks - doesn't matter if I only have virtual disks mapped or if only disks on the pass-throughed controller are mapped. Another weird thing is that plugins (.plg) located in /boot/config/plugins won't install automatically. If I installplg them manually they work, also after a reboot... I'm close to being ready to move my current array from my old server, but am still a bit hesitant because of the performance issue and the plugins not installing (it's such a basic feature, makes me think I've set up something incorrect). I'm using the pre-built VMDK from http://lime-technology.com/forum/index.php?topic=26639.0.

So I tried both resetting the BIOS and at the same time installed ESXi 5.1u1 instead of 5.5 - much to my own surprise pass-through worked! Tried reinstalling 5.5, not changing any BIOS setting, and it was broken again, so it appears 5.5 is the issue... I'd like to know why 5.5 fails, but at the moment 5.1u1 works, so I'm happy

Hey BobPhoenix Nice to hear someone's had success passing through onboard devices! I've triple checked the BIOS and everything regarding virtualization has been enabled, but I'll try starting from the bottom and reset to defaults. The MB should be able to automatically fetch updates through the BIOS, which claims there are none.

Thanks for your response. Everything VT-d related has been enabled in the BIOS. Although most people do seem to use addon cards, I haven't come across anything that made it clear that onboard devices won't work, but my issues seem to indicate you're right. I'll try with an addon card.

Hey guys This is an amazingly difficult google and it doesn't seem like any of the existing ESXi threads cover this... This isn't unRAID related as such, but I figured I'd start here: I'm trying to set up unraid on an ESXi build, but am having some trouble using pass-through. I have an ASRock Extreme6 z87 motherboard with an Intel Core i5 4670 connected. Both support VT-d etc. If I pass anything through, unRAID won't recognize it. If I pass it to a Windows VM instead, Windows sees it, but can't use it. It doesn't matter what I try to passthrough, but take fx the ASM1062 SATA3 controller: at first it's recognized as a "SATA controller", but apparently missing the drivers. Installing the drivers enables Windows to see it as "ASM106x controller" but still with a yellow exclamation mark and an error code 10 (can't start the device). I've tried passing through the GPU, SATA controller and NIC, all show the same issue. Is this just a clear sign that my hardware doesn't support pass-through?

So this is odd, for some reason upnp was enabled, disabling it seems to have solved the problem. Having upnp enabled isn't a good idea, is it?

I think it's 30-40% when SAB's running and the disconnects are happening, about 70% when Plex's transcoding and they don't...

I have my unraid connected to a switch, and the switch connected to a router; i tried connecting unraid, like the HD Homerun, directly to the router, but it didn't help. The disconnects actually happen very rarely if SAB isn't working, but if SAB is downloading something, live-tv in XBMC is practically useless. I don't think XBMC is at fault nor the machines running it: my primary HTPC is running OpenELEC 3 with XBMC 12.1, my laptop is running Windows 8 with XBMC 12.0. The disconnects happen on both at the same time. If this is a hardware error, the unraid tower, the router or the hdhomerun should be the main suspects and I highly doubt it could be the hdhomerun. If it's software, it can basically only be unraid that's failing... According to my router (DD-WRT) I have a huge number of active IP connections (1000-3000 out of 4096). Should this be a cause for concern?

I'm usually able to sort problems like this out with a little research/googling, but for once I have no idea where to start searching. This might not even belong on the unraid forums, but unraid seems to be the only common denominator... I'm running a custom 5.0-rc8a (I know, not the latest, but it was hell building this with as little linux experince as I have and it has been running fine till now). Among other plugins, I have tvheadend connected to a HD Homerun Dual and SABnzbd running on unraid. I have XBMC running on a couple of HTPCs. XBMC has randomly started to lose the connection to tvheadend. Out of nowhere it will drop the connection and, if nothing's touched, it'll reconnect a few minutes later. Changing to a different channel (different mux) usually works right away. One thing that's apparently causing the disconnects is when starting a download in SAB; as long as SAB's working, the disconnects will happen very regularly. Capping SABs bandwith (from 40Mbit/s to ~25Mbit/s) appears to help a little, but this is on a gigabit network and XBMC has no problems dealing with higher bitrate video than live-tv served from the same unraid tower. The disconnects happen even if SAB isn't running, so it's not the only thing that can recreate the issue, but I don't know what else is doing it. I can't trigger the disconnects from any other machine on the LAN - it appears to be isolated to the unraid server. Right now I'm only running plugins on the unraid server that I know has been working fine with my live-tv setup. When XBMC disconnects the only thing in the log is this, which is apparently indicative of a buffering issue: WARNING: CDVDMessageQueue(audio)::Get - asked for new data packet, with nothing available The tvheadend log shows nothing, only XBMC trying to reconnect. Does anyone have an idea where I should start searching for the cause of the issue/which logs to look at?

See the edit at the top of the post

Okay, so a while ago I was trying to get TVHeadend working with unRAID 5 rc8a. Since I'm a complete linux illiterate, I had no idea what I was doing, but after a lot of hair-pulling I actually got it working about a month ago. I forgot to write a guide at the time, so writing it now I'm sure some of the commands are wrong/not needed. I have made a note(*) at the commands that I'm not sure are correct. Before this has any potential to go in the wiki, someone should definitely proofread it (also, I have no idea what packages are actually needed - the ones below are the ones needed to install TVHeadend and VirtualBox (but the unRAID 5 plugin takes care of installing TVHeadend))! Install the TVHeadend plugin: http://lime-technology.com/forum/index.php?topic=20782.0 SSH to your unRAID, create a temporary development directory and download the packages: mkdir /mnt/cache/.unraiddev/packages_slack13.1.0 cd /mnt/cache/.unraiddev/packages_slack13.1.0 wget <links from below> http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.4.11.tar.gz http://lime-technology.com/download/doc_download/37-unraid-server-version-50-rc8a-aio http://slackware.osuosl.org/slackware-13.1/slackware/d/gcc-4.4.4-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/glibc-2.11.1-i486-3.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/binutils-2.20.51.0.8-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/make-3.81-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/cxxlibs-6.0.13-i486-2.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/pkgtools-13.1-noarch-1.tgz http://slackware.osuosl.org/slackware-13.1/slackware/d/perl-5.10.1-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/cpio-2.9-i486-2.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/patch-2.5.4-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/ncurses-5.7-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/git-1.7.1-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/libidn-1.5-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/n/curl-7.20.1-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/pkg-config-0.23-i486-2.txz http://slackware.osuosl.org/slackware-13.1/slackware/n/openssl-0.9.8n-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/infozip-6.0-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/gcc-g++-4.4.4-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/gtk+-1.2.10-i486-5.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/gtk+2-2.18.9-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/cmake-2.8.1-i486-1.txz Install the packages: installpkg *.t*z Unzip the downloaded unRAID package: unzip unRAID* -d /mnt/cache/.unraiddev Go to "/usr/src" directory and rename the folder "linux-3.4.11-unRAID" to "linux-3.4.11-unRAID_original". mv /usr/src/linux-3.4.11-unRAID /usr/src/linux-3.4.11-unRAID_original Extract the vanilla kernel file (linux-3.4.11.tar.gz) into "/usr/src": tar -C /usr/src/ -zxvf linux-3.4.11.tar.gz Link the new source directory (linux-3.4.11) to the "linux-3.4.11-unRAID" path: ln -sf /usr/src/linux-3.4.11 /usr/src/linux-3.4.11-unRAID Copy all default drivers and configuration to the new source directory: cp -rf /usr/src/linux-3.4.11-unRAID_original/* /usr/src/linux-3.4.11/ cp -f /usr/src/linux-3.4.11-unRAID_original/.config /usr/src/linux-3.4.11/ Link kernel headers includes to the new source includes: ln -sf /usr/src/linux-3.4.11-unRAID/include/asm-generic /usr/include/asm-generic ln -sf /usr/src/linux-3.4.11-unRAID/include/linux /usr/include/linux ln -sf /usr/src/linux-3.4.11-unRAID/arch/x86/include/asm /usr/include/asm make bzImage make modules make modules_install Copy the created bzImage to the boot directory: cp arch/x86/boot/bzImage /boot/bzimage_new Find and download the Realtek r8168 driver from their website and place it in the .unraiddev dir (it has to be installed manually otherwise unRAID will boot without network access). Extract, build and install: cd /mnt/cache/.unraiddev/ tar -xjf r8168*.tar.bz2 cd /mnt/cache/.unraiddev/r8168-8.032.00 make modules make install Download the latest dvbhdhomerun, place it in the development dir, and extract, build and install*: cd /mnt/cache/.unraiddev tar -xjf dvbhdhomerun*.tar.gz (not sure about the arguments) cd /mnt/cache/.unraiddev/dvbhdhomerun-0.0.11/kernel make clean make make install Download and build libhdhomerun*: cd /mnt/cache/.unraiddev wget http://download.silicondust.com/hdhomerun/libhdhomerun_20120405.tgz tar -xjf libhdhomerun*.tgz (not sure about the arguments) cd /mnt/cache/.unraiddev/libhdhomerun make clean make Configure userhdhomerun: Open /mnt/cache/.unraiddev/dvbhdhomerun-0.0.11/userhdhomerun/CMakelists.txt and change the LIBHDHOMERUN_PATH to the libhdhomerun directory you just untar'ed (/mnt/cache/.unraiddev/libhdhomerun). cd /mnt/cache/.unraiddev/dvbhdhomerun-0.0.11/userhdhomerun make Create a temporary directory and extract the vanilla unRAID bzroot into it: mkdir /mnt/cache/.unraiddev/bz-mod cd /mnt/cache/.unraiddev/bz-mod xzcat ../bzroot | cpio -i -d -H newc --no-absolute-filenames Syncronize (overwrite) the extracted vanilla modules with the newly compiled modules and copy the userhdhomerun file*: rsync -av --delete /lib/modules/3.4.11-unRAID/ /mnt/cache/.unraiddev/temp/bz-mod/lib/modules/3.4.11-unRAID/ cp /usr/bin/userhdhomerun /mnt/cache/.unraiddev/temp/bz-mod/usr/bin/ (I think some arguments are missing here) package the new bzroot: cd /mnt/cache/.unraiddev/bz-mod/ find . | cpio -o -H newc | xz --format=lzma > /boot/bzroot_new Rename the _new files in /boot, restart the server and unRAID should be running with the r8168 and HDHomerun enabled. I have also added this to my go file, although I'm not sure the Realtek part is actually necessary: # Load Realtek r8168 driver cd /lib/modules/3.4.11-unRAID/kernel/drivers/net/ethernet/realtek depmod -a insmod r8168.ko # Start HDHomeRun #! /bin/sh cd /lib/modules/3.4.11-unRAID/extra/ modprobe dvb_hdhomerun sleep 3 /usr/bin/userhdhomerun & Furthermore, the TVHeadend config file won't persist after a reboot, so I've created it on my flash drive and then symlink it in the go file (TVHeadend recognizes my HDHomerun Dual as a DVB-T tuner if this file isn't set up): # Symlink Tvheadend config file ln -s /boot/custom/tvheadend/dvbhdhomerun /etc/dvbhdhomerun

EDIT: It works! Apparently it was all about timing... See http://lime-technology.com/forum/index.php?topic=24303.0 I'm sorry for starting a new thread, since I've already been posting in the thread at http://lime-technology.com/forum/index.php?topic=20782.0, but since this isn't a TVHeadend related issue anymore, I hope it's okay to start a new one. It's probably not even related to unraid 5, but that's what I'm running, so this is where I'm posting EDIT: Sorry, wrong forum - the thread has been moved When trying to build my own TVHeadend-ready rc8a kernel I need to compile and install the Realtek r8168 manually. Problem is whenever I try to "make module" it results in an error. This is what I'm doing: wget the following packages to the dir /mnt/cache/.unraiddev/packages_slack13.1.0 (these are the packages needed to get both TVHeadend and VirtualBox running, so they have nothing to do with what I'm actually trying to build...). http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.4.11.tar.gz http://slackware.osuosl.org/slackware-13.1/slackware/d/gcc-4.4.4-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/glibc-2.11.1-i486-3.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/binutils-2.20.51.0.8-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/make-3.81-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/cxxlibs-6.0.13-i486-2.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/pkgtools-13.1-noarch-1.tgz http://slackware.osuosl.org/slackware-13.1/slackware/d/perl-5.10.1-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/cpio-2.9-i486-2.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/patch-2.5.4-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/ncurses-5.7-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/git-1.7.1-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/l/libidn-1.5-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/n/curl-7.20.1-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/pkg-config-0.23-i486-2.txz http://slackware.osuosl.org/slackware-13.1/slackware/n/openssl-0.9.8n-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/a/infozip-6.0-i486-1.txz http://slackware.osuosl.org/slackware-13.1/slackware/d/gcc-g++-4.4.4-i486-1.txz http://lime-technology.com/download/doc_download/37-unraid-server-version-50-rc8a-aio Install the packages: installpkg *.t*z Download the Realtek driver from: http://218.210.127.131/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false. Place the tar in /mnt/cache/.unraiddev/realtek_r8168 and: tar -xjf r8168*.tar.bz2 cd /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00 make modules This results in the error: make[1]: *** No rule to make target `modules'. Stop. This happens no matter what I try to compile (have also been fiddling with the dvbhdhomerun module). I think this is a simple problem, but my understanding of linux is just too limited to solve it myself. And it's incredible how Google offers absolutely no help at all: I get a lot of hits, but the solutions to the problem are never consistent and never address slackware (mostly ubuntu which involves apt-get and other random packages that isn't part of unraid). I have been an unraid user for ages, but my post count on this forum is relatively low - I have always been able to google my questions, but not in this case... EDIT: I'm just trying to install a driver - is it really supposed to be this complicated? There are builds including both the dvbhdhomerun modules and the r8168, but none of them are based on rc8a. So it's possible, I just have no idea how it's done... I have also tried going a bit further with the kernel customization before trying to compile the modules (using the guide for 4.7 at http://lime-technology.com/wiki/index.php/Installing_Tvheadend_in_unRAID, taking into account the different kernel): Unzip the downloaded unRAID package: unzip unRAID* -d /mnt/cache/.unraiddev/ Go to "/usr/src" directory, and rename the folder "linux" to "linux_original" (notice I'm not using these directories): mv /usr/src/linux-3.4.11-unRAID /usr/src/linux-3.4.11-unRAID_original Extract the vanilla kernel file (e.g. linux-2.6.32.9.tar.gz ) into "/usr/src": tar -C /usr/src/ -zxvf linux-3.4.11.tar.gz Link the new source directory (e.g. linux-2.6.32.9 ) to "/usr/src/linux" path: ln -sf /usr/src/linux-3.4.11 /usr/src/linux-3.4.11-unRAID Copy all default drivers and configuration to the new source directory: cp -rf /usr/src/linux-3.4.11-unRAID_original/* /usr/src/linux-3.4.11/ cp -f /usr/src/linux-3.4.11-unRAID_original/.config /usr/src/linux-3.4.11/ Link kernel headers includes to the new source includes: ln -sf /usr/src/linux-3.4.11-unRAID/include/asm-generic /usr/include/asm-generic ln -sf /usr/src/linux-3.4.11-unRAID/include/linux /usr/include/linux ln -sf /usr/src/linux-3.4.11-unRAID/arch/x86/include/asm /usr/include/asm Configure the kernel: cd /usr/src/linux-3.4.11-unRAID/ make clean make menuconfig and save the configuration. Then I give the r8168 another try: cd /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00 make modules Which now results in: ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. So I: cd /usr/src/linux-3.4.11-unRAID/ make oldconfig && make prepare This creates the /usr/src/linux-3.4.11/include/config/auto.conf, but trying the first step again: cd /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00 make modules Now results in: WARNING: Symbol version dump /usr/src/linux-3.4.11/Module.symvers is missing; modules will have no dependencies and modversions. CC [M] /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00/src/r8168_n.o CC [M] /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00/src/r8168_asf.o CC [M] /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00/src/rtl_eeprom.o CC [M] /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00/src/rtltool.o LD [M] /mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00/src/r8168.o Building modules, stage 2. MODPOST 1 modules /bin/sh: scripts/mod/modpost: No such file or directory make[3]: *** [__modpost] Error 127 make[2]: *** [modules] Error 2 make[2]: Leaving directory `/usr/src/linux-3.4.11' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/mnt/cache/.unraiddev/realtek_r8168/r8168-8.032.00/src' make: *** [modules] Error 2 Can anyone tell me what I'm missing?