Jump to content

CHBMB

Community Developer
  • Content Count

    10588
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by CHBMB

  1. #!/bin/bash #Set your Unraid version here in the form 6-7-3 UNRAID_VERSION="6-8-2" # Set the type of build you want here - nvidia or stock BUILD_TYPE="nvidia" #Set the download location here DOWNLOAD_LOCATION="/mnt/cache/downloads/nvidia" echo Downloading v$UNRAID_VERSION of the $BUILD_TYPE build to the $DOWNLOAD_LOCATION folder #Make target directory [[ ! -d ${DOWNLOAD_LOCATION} ]] && \ mkdir -p ${DOWNLOAD_LOCATION} #download files wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzimage -O ${DOWNLOAD_LOCATION}/bzimage wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzroot -O ${DOWNLOAD_LOCATION}/bzroot wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzroot-gui -O ${DOWNLOAD_LOCATION}/bzroot-gui wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzfirmware -O ${DOWNLOAD_LOCATION}/bzfirmware wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzmodules -O ${DOWNLOAD_LOCATION}/bzmodules #download sha356 files wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzimage.sha256 -O ${DOWNLOAD_LOCATION}/bzimage.sha256 wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzroot.sha256 -O ${DOWNLOAD_LOCATION}/bzroot.sha256 wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzroot-gui.sha256 -O ${DOWNLOAD_LOCATION}/bzroot-gui.sha256 wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzfirmware.sha256 -O ${DOWNLOAD_LOCATION}/bzfirmware.sha256 wget https://lsio.ams3.digitaloceanspaces.com/unraid-nvidia/${UNRAID_VERSION}/${BUILD_TYPE}/bzmodules.sha256 -O ${DOWNLOAD_LOCATION}/bzmodules.sha256 #check sha256 files BZIMAGESHA256=$(cat ${DOWNLOAD_LOCATION}/bzimage.sha256 | cut -c1-64) BZROOTSHA256=$(cat ${DOWNLOAD_LOCATION}/bzroot.sha256 | cut -c1-64) BZROOTGUISHA256=$(cat ${DOWNLOAD_LOCATION}/bzroot-gui.sha256 | cut -c1-64) BZFIRMWARESHA256=$(cat ${DOWNLOAD_LOCATION}/bzfirmware.sha256 | cut -c1-64) BZMODULESSHA256=$(cat ${DOWNLOAD_LOCATION}/bzmodules.sha256 | cut -c1-64) #calculate sha256 on downloaded files BZIMAGE=$(sha256sum $DOWNLOAD_LOCATION/bzimage | cut -c1-64) BZROOT=$(sha256sum $DOWNLOAD_LOCATION/bzroot | cut -c1-64) BZROOTGUI=$(sha256sum $DOWNLOAD_LOCATION/bzroot-gui | cut -c1-64) BZFIRMWARE=$(sha256sum $DOWNLOAD_LOCATION/bzfirmware | cut -c1-64) BZMODULES=$(sha256sum $DOWNLOAD_LOCATION/bzmodules | cut -c1-64) #Compare expected with actual downloaded files [[ $BZIMAGESHA256 == $BZIMAGE ]]; echo "bzimage passed sha256 verification" [[ $BZROOTSHA256 == $BZROOT ]]; echo "bzroot passed sha256 verification" [[ $BZROOTGUISHA256 == $BZROOTGUI ]]; echo "bzroot-gui passed sha256 verification" [[ $BZFIRMWARESHA256 == $BZFIRMWARE ]]; echo "bzfirmware passed sha256 verification" [[ $BZMODULESSHA256 == $BZMODULES ]]; echo "bzmodules passed sha256 verification" That script will do it. Need to change the 3 parameters to suit. chmod +x it to make it executable, if all the SHA256 sums match copy it across to your flash disk.
  2. Just realised you're using a mobile GPU on a laptop. Probably going to be the issue
  3. Just took a look at this and I'm confused, on v6.8.2 those modules are present as far as I can tell. I'm a bit confused as both of these are present in the v6.8.2 Nvidia build.... they may have been missing on v6.8.1 (I can't remember) root@server:/# ls -la /lib/modules/4.19.98-Unraid/kernel/drivers/net/ethernet/realtek | grep r8169 -rw-r--r-- 1 root root 33728 Feb 2 20:52 r8169.ko.xz root@server:/# ls -la /lib/modules/4.19.98-Unraid/kernel/drivers/net/ethernet/broadcom | grep tg3 -rw-rw-rw- 1 root root 66572 Feb 2 20:51 tg3.ko.xz
  4. Try running this command and post the output. nvidia-smi --query-gpu=gpu_name,gpu_bus_id,gpu_uuid --format=csv,noheader | sed -e s/00000000://g | sed 's/\,\ /\n/g'
  5. 05:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f] Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:2003] Kernel driver in use: tg3 Kernel modules: tg3 05:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f] Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:2003] Kernel driver in use: tg3 Kernel modules: tg3 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:8677] Kernel driver in use: r8169 Kernel modules: r8169 You have two different NICs, which one isn't working? I'm assuming these logs were from a stock Unraid?
  6. Fair enough. I might have been thinking about the Intel stuff or something else, I can't really remember, could have been Jellyfin as well. Dunno.....
  7. v6.8.2 uploaded. Delayed for a few reasons, had problems (and still do) with the nvidia container runtime, worked around it in the end, but not a long term solution looking forward, I'm working like a dog at the moment as my current real life job finishes in 2 days and I'm having to put a ton of extra hours in, wife a bit ungainly at the moment as very heavily pregnant so I'm having to do a bit more for our existing beast, and to add to that bass_rock has been away for work, so kind of a perfect storm of not having much time to sit down with this, although I have been trying to get it working every chance I've had. Anyways, I've tested this version, think everything is working, and I believe all the out of tree drivers are squared away. Last version (v6.8.1) might have been missing the Intel 1gb driver as I hadn't realised that it was different to the 10gb driver.
  8. v6.8.2 uploaded LibreELEC, TBS-OS, Digital Devices
  9. I'm not sure the Emby official container will work with the Nvidia stuff, we made our container specifically with the Unraid Nvidia stuff in mind.
  10. https://github.com/linuxserver/Unraid-DVB/blob/master/build_scripts/kernel-compile-module.sh https://github.com/linuxserver/Unraid-DVB/blob/master/build_scripts/libreelec-module.sh Pull requests welcome.
  11. He's right, we don't need to be told, the rate limiting step isn't when we notice a new Unraid build, it's when I get a chance to build it, trust me, I'm an Unraid user, I get the same notifications as everyone else, I know when there's a new release.
  12. @Benjamin Picard @wreave Pushed a new build. I think it should be good, but had some issues with the overall build process and did it manually, and it's half two in the morning, so be grateful if you can test and let me know.
  13. I have zero desire in creating any more custom Unraid builds. Currently the Nvidia one technically isn't a custom kernel as I change nothing there, it's more about adding extra packages and custom container runtime. DVB adds DVB drivers and some extra firmware (LibreELEC version) TBS and Digital Devices are completely different branches on the media_tree. I did help with the HP RMRR version as well, but I don't maintain it, and iirc there's currently no kernel patch for the kernel version we're using anyway. I had a play around with some docker swarm kernel parameters a while ago but that's about it. I don't enable anything else custom and don't want to.
  14. Hmmm, Going to be honest, I didn't even realise realtek oot drivers were needed on this release, I must have missed that in the release notes. I'll build a new release, not a big problem. Sent from my Mi A1 using Tapatalk
  15. I briefly tried the office stuff which didn't work for me, but I already have collabora so I reverted to that. I'm sure any niggles will get ironed out with time and patience. Sent from my Mi A1 using Tapatalk
  16. You can, but they stagger the OTA updates, so you can only do it when it's offered to you. Using the terminal you can update whenever you want. Whatever method you're using the "hub" features will not automatically be enabled with an upgrade, you still need to enable the relevant plugins, whereas a fresh install they will be enabled out of the box. Sent from my Mi A1 using Tapatalk
  17. A new install will have the features by default, an existing install will not, and you will need to manually add the relevant apps/plugins via the Nextcloud webui. I have upgraded manually to check everything is working, but not really had time to check it all out yet as spent last night working on something else, which reminds me, I need to upload that. Sent from my Mi A1 using Tapatalk
  18. v6.8.1 LibreELEC, TBS-OS, Digital Devices done. @BRiT I wholeheartedly agree with you, DVB on Linux is a mess, always has been, probably always will be. Network tuners are by far and away the best solution, and I migrated from DVB myself to a network tuner, no regrets.....
  19. Nothing, that's why when things are fixed you delete that tag. Sent from my Mi A1 using Tapatalk
  20. I'll try and take a look at this tomorrow. Main issue at the moment is I need to sort out the Wireguard OOT drivers. Any new OOT driver is a PITA
  21. And I refer people to my last lengthy post on here to help put this in perspective how much work this takes. And on a daily basis me and the other linuxserver guys are dealing with the other stuff we do, ie docker, and trying to answer support stuff. Just saying.....
  22. You've obviously got some ideas, why not do it? Problem is I see time and time again, is people keep telling us what we should be doing and how quick we should be doing it, now, don't be offended because this is a general observation, rather than personal. It's ten to one in the morning, I've just got back from work, I have a toddler that is going to get up in about five hours, my wife is heavily pregnant, Unraid Nvidia and beta testing just isn't up there in my list of priorities at this point. I've already looked at it and I need to look at compiling the newly added WireGuard out of tree driver. I will get around to it, but when I can. And if that means some Unraid users have to stick on v6.8.0 for a week or two then so be it, or, alternatively, forfeit GPU transcoding for a week or two, then so be it. I've tried every way I could when I was developing this to avoid completely repacking Unraid, I really did, nobody wanted to do that less than me. But, if we didn't do it this way, then we just saw loads of seg faults. I get a bit annoyed by criticism of turnaround time, because, as this forum approaches 100,000 users, how many actually give anything back? And of all the people who tell us how we should be quicker, how many step up and do it themselves? TL:DR It'll be ready when it's ready, not a moment sooner, and if my wife goes into labour, well, probably going to get delayed. My life priority order: 1. Wife/kids 2. Family 3. Work (Pays the mortgage and puts food on the table) @Marshalleq The one big criticism I have is comparing this to ZFS plugin, no disrespect, that's like comparing apples to oranges. Until you understand, and my last lengthy post on this thread might give you some insight. Please refrain from complaining. ZFS installs a package at boot, we replace every single file that makes up Unraid other than bzroot-gui. I've said it before, I'll say it again. WE ARE VOLUNTEERS Want enterprise level turnaround times, pay my wages.
  23. What's that got to do with Calibre-web? You've mentioned several different containers, none of which are related to this support thread..... Sent from my Mi A1 using Tapatalk