natiz

I can't get Fan Control to work on Dell PowerEdge T420. On the Fan Control tab, a popup appears: But there's no Configure button (Fan control is indeed stopped). Note that I am able to control the fan manually using the ipmitool (installed via NerdTools), eg `ipmitool raw 0x30 0x30 0x01 0x00` and `ipmitool raw 0x30 0x30 0x02 0xff 0x20` to set it to 20%.

Thanks for the info, @BRiT. I found a workaround, updated to the TBS OS build, and used mksquashfs to append the missing fw file (dvb-demod-m88rs6000.fw) to bzfirmware and it worked!

Is there a guide on how to compile the kernel? I am looking to add the https://github.com/LibreELEC/dvb-firmware/blob/master/firmware/dvb-demod-m88rs6000.fw package to TBS version. I currently use the TBS CrazyCat build, but it seems its not updated anymore. This would allow me to use TBS6281SE for DVB-C and DVBSKy S952 V3 for DVB-S.

@CHBMB do you think dvb-demod-m88rs6000.fw can be added to the TBS OS build? if not can you please provide instructions how/where to run the build scripts to compile my own version of the kernel?

@alturismo I tried LibreELEC, but then my TBS card doesn't even show up 😕 I have 2 cards, TBS6281SE for DVB-C and DVBSKy S952 V3 for DVB-S. I rolled back to TBS Crazycat for now, this is how it looks: I think its because only dvb-fe-cx24117.fw is included in the TBS (OpenSource) build, see here: https://github.com/linuxserver/Unraid-DVB/blob/master/build_scripts/tbs-os-module.sh#L46-L55

I upgraded from TBS (CrazyCat) 6.7.2 build to the TBS (Open Source) 6.8.2 build and I'm having issues. It seems that dvb-demod-m88rs6000.fw is missing. It does seem to exist in their github repo: https://github.com/LibreELEC/dvb-firmware/blob/master/firmware/dvb-demod-m88rs6000.fw Can I install it manually? why is it missing?

Thanks saarg, I couldn't find anything in the thread. Can anyone else confirm?

What happened to the TBS (CrazyCat) builds? I only see TBS (OpenSource) on the dropdown. I am currently with the TBS (CrazyCat) DVB-S(2) & DVB-T(2) build v6.5.2 of unraid, wanting to upgrade to the latest.

Anyone? This is the error I get: EDIT: The CrazyCat seems to do the trick, although the devices are still ordered wried, but I guess its fine as long as it works

Quick question about which build to install - I have both a DVBSky S952, and TBS 6281SE. Until today I worked only with the DVBSky one with the LibreELEC build. Now that I want to use both, I first tried TBS (Open Source) 6.4.0.rc9f but then 2 issues had ocurred: 1) The DVBSky had failed on: "Direct firmware load for dvb-demod-m88rs6000.fw failed with error -2" (haven't tried the TBS one) 2) The order of the adapters was off (1 DVBSky, 2 TBS, 3 DVBSky, 4 TBS) With #2 I can live, but #1 makes me believe I am not using the right build - which one should I be using?

yep, working again - thanks!

+1 for the 6.3.5 / DVBSky issue mentioned above

Well, I feel a bit ashamed I tried removing/changing as you suggested, and then I started triple-checking my router is forwarding as it should As it turns out, I'm using a VERY old firmware version of DD-WRT (DD-WRT v24-sp2 (12/24/13) std). After some reading, there seem to be a known issue around NAT loopback/port forwarding which was fixed in later versions There's a workaround available but I decided to upgrade to the latest firmware, which seem to resolve the issue. All is working as expected - thanks @CHBMB

After reading a bit on certbot I think I understand better - the script runs certbot in standalone mode - it itself listens on 443 to perform the verification. I did some troubleshooting (built the image w/o the starter script, nginx turned off) from the container itself: certbot certonly --verbose --non-interactive --renew-by-default --standalone --preferred-challenges tls-sni --rsa-key-size 4096 --email "[email protected]" --agree-tos -d "x.mydomain.com" Same error, only this time, I ran watch on curl https://localhost, and after a few seconds, got this: After that certbot finished and from then it was connection refused (which is fine).. btw, here's my docker run cmd (Router routes both 443 and 80 to 443 and 81): docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e HOST_OS="unRAID" -e "EMAIL"="[email protected]" -e "URL"="mydomain.com" -e "SUBDOMAINS"="x," -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -p 81:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt

Yes its resolved and answered. I do think its trying to connect, as the error clearly says: also, see this: https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.3