Posts by mladen.perisic84

Quote from Iridium

AFAIK changing the port has to be done in the lighttpd.conf file. But any changes at that level will be overwritten with any upgrade.

DNS setting are the upsteam DNS not local. So for DNS1 will be 9.9.9.9 for Quad9, 8.8.8.8 for Google or whatever you fancy. All this can be done in the web gui, so shouldn't be necessary in the script.

I just checked Pi-Hole Docker page here and according to developer:

Quote

Upgrade Notices:

Docker Pi-Hole v4.2.2

• ServerIP no longer a required enviroment variable! Feel free to remove it unless you need it to customize lighttpd
• --cap-add NET_ADMIN no longer required unless using DHCP, leaving in examples for consistency

Docker Pi-Hole v4.1.1+

Starting with the v4.1.1 release your Pi-hole container may encounter issues starting the DNS service unless ran with the following setting:

• --dns=127.0.0.1 --dns=1.1.1.1 The second server can be any DNS IP of your choosing, but the first dns must be 127.0.0.1

Which is good news. I will upgrade to newest version. Script can be simplified and 2 of my concerns are solved

Quote from esenterre

I'm using the add-on. I don't know Docker too much. But I can try the commands if it's the way to go. My concern was those commands (in this thread) seems for the RPi. I don't know how to change it for X86.

Doesn't really matter. I'm on x86 platform and everything works great.

First uninstall add-on version. Then try to follow my post here.

I just installed pi-hole. Excellent piece of SW!

First I tried Linux-Server image and it worked great! I allowed me to set my own port for WebGUI (8084 in my case). I wanted to try newer version, so I uninstaled this one and go to v4.1 by following Iridium's post and punkid's one.

So, after doing:

docker pull pihole/pihole:latest

I created script file:

docker run -d \
--name pihole \
--cap-add NET_ADMIN \
-p 53:53/tcp \
-p 53:53/udp \
-p 80:80 \
-e DNS1=127.0.0.1 \
-e DNS2=1.1.1.1 \
-v /etc/localtime:/etc/localtime \
-v /storage/.config/pihole/:/etc/pihole \
-v /storage/.config/pihole/dnsmasq.d/:/etc/dnsmasq.d \
-v /storage/.config/pihole/html/:/var/www/html/html/ \
-h $(cat /etc/hostname) \
-e ServerIP=$(ip route get 127.0.0.1 | awk '{ print $NF; exit }') \
-e WEBPASSWORD=654321 \
--restart=unless-stopped \
pihole/pihole:latest

And everything worked great. I accessed config page normally. Since v4 pi-hole does not come with any blacklists I decided to add some:

https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts

https://mirror1.malwaredomains.com/files/justdomains

http://sysctl.org/cameleon/hosts

https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt

https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt

https://hosts-file.net/ad_servers.txt

And that's it. Everything works.

But, one option remain problem for me. I already have multiple lighttpd servers runing on LE and in order to accomodate pi-hole I moved one to other port. I tried messing with -p option but everything except 80:80 is not working properly or at all. Any workaround is known?

Also, what about -e ServerIP? I put 127.0.0.1, but Iridium suggested 9.9.9.9 and punkid suggested 192.168.1.x. Should I use DNS address, internal host or LAN IP?

This thread is really useful regarding state of 4K HDR10 playback. It's regularly updated with information.

I'm still waiting for someone to cinfirm LE + 18.0 state. Currently, only info about LE + 17.6 is in a no-go state.

Hahaha, just now when you replied I was going to ask you do you have experience with CAC-1080 adapter.

Now I'm sutck too with my experimental setup. I just installed latest LE alpha (8) and put in RX 580. I have UHD@60Hz, but not HDR! No matter what I try I am stuck at SDR. Under Windows I'm getting HDR and it's working properly. But under LE - no.

Check this AMD link and look under Connectivity. It's written Display Port 1.4 HDR, but on HDMI it's not written HDR. Maybe, just maybe this has some relevance (don't laugh - I'm desperate here)... Uhhh, I don't know anymore. After 3 days I'm really ready to give up.

Hmm... Since I'm looking into those things too (upgrading my PCs) it's always useful to find things like this. According to Intel white paper (page 13) HDR compatibility on 7th or 8-th gen is guaranteed with min. DP 1.3 or HDMI 2.0a with HDCP 2.2 support . Your adapter is DP 1.2->HDMI 2.0 (I couldn't find is it plain HDMI 2.0 or a/b revision).

As I painfully learned, It's really, really important to get compatibility right in HDR PC world.

Did you try setup without AVR?

Hello Mitzsch,

Fortunately, I put on hold every purchase (It's almost 1500€ for new MB, CPU, RAM, AVR) till LE come to final 9 release. It's pretty risky investing at this point.

LE 8.90.006 bumped Linux kernel at 4.18.11 for x86_64. Site I mentioned above note that 4.19 is better for Vega. I will wait for final release and user experience reviews before I decide to upgrade.

Regarding DLNA, it's really easy to turn it on in Kodi. Your TV should be able to see it momentarily. Kodi will sent just frames and your TV will decode it.

Your problem with noise on DTS... Some AVRs can not accept DTS-HD-HRA on first HDMI. Just to be sure, use some other HDMI port on AVR. Somewhere recently I read that on some AVRs 1st HDMI can not recognize correctly 8c@192kHz, but other inputs can. Instead you need to send 8c@192kHz transfered in 2c@192kHz. Not sure. Worth investigating. Also try setting PCM Fixed to On in your AVR settings if your AVR supports it.Your card has DP 1.4 port so it definitely supports DTS-HD. Maybe use high-bandwidth HDMI cable?

Exactly what I was looking for. Several months ago I asked about similar thing: HTPC with HDR support on LE. I asked about going down the way of discrete VGA, but chewitt rightfully discouraged me from doing so.

Fast forward 6 months and I started digging again about 2160p HDR + Dolby Atmos setup. I already picked most of the components: Denon AVR X1400H + Asus TUF B450M-GAMING PLUS + AMD Ryzen 3 2200G, since Asus it's the only MB manufacturer (AFAIK) which officially supports HDMI 2.0b.Then I stumbled on this SFF forums thread. After that I checked LE forums and found this...

Linux 4.18 kernel seems buggy regarding Vega support, but 4.19 is much better (according to tests on here).

Currently, the way I watch HDR content is by putting it in LE Library (DLNA/UPNP streaming turned on), then accessing DLNA library from my TV. HDR works just fine, but the problem is stupid audio support on my TV (no Atmos or DTS HD) and stupid things like forwarding, slow response...

I guess I still need to wait for proper support from Linux in order to fully immerse myself in LE-PC world again.

chewitt This thread can be helpful. It's lengthy and somewhat old, but it contains useful information. It's seems problem could be in kernel.

Chewitt, thank you for responding. I guess I expected that answer

Ok, I'll listen your advice and hold on for a little while. Next time I will do my homework properly before rushing into things.

Hello guys! I wish I was smarter and researched the net before buying new TV.

I really wanted 4K HEVC 10bit HDR. I (wrongly assumed) my good ol' AMD Richland A10-6700 APU (Radeon HD 8670D) would be enough for it. It is not.

Now, I'm thinking of changing things a little while staying on PC/LE platform (S905 is not for me). The easiest way is buying new graphics card. That's how I have gotten to this thread.

As far as I understood LE does not have problem playing 4K. Also, It does not have problem doing it with 10bit x.265. Am I right here?

But, I see the problem arises with HDR10 support. There are many reported problems and I understood it's Kodi's problem (at least in current stable release 17.6)

Since LibreELEC (and before it OE) is my favorite Open source piece, I wanted to ask you what should I do? Should I buy new VGA; will it solve my problem? Should I wait for LE 9 (Kodi 18) for things to get better and then buy it?