Posts by chewitt

This is still being looked into, and it's one of those tasks that's programmatically not quite as simple as it initially sounds due to how DNS lookups and DNS caching work.

Can you name a series that is not being scraped?

No worriess, 32-bit boot firmware isone of the more obscure niches of the distro

LE uses syslinux for 64-bit x86_64 boot environments and grub for 32-bit, so presence of grub might just indicate the device is super low-end and has 32-bit boot firmware. Those devices have always been fairly rare so our experience with them is limited, but historically they were always rather awkward to install onto. You might get further removing the ATA! drive and writing the image directly to the HDD via USB > IDE adaptor. You might also need to experiment to BIOS settings (disable EFI, set legacy, or similar).

Can this not be added to other conf files? (which is what the folder is really for) .. sorry i'm not much of a pulse expert (as we don't really use it).

echo "options cfg80211 ieee80211_regdom=DE” > /storage/.config/modprobe.d/cfg80211.conf

^ see if that helps, it will be something you can set via the GUI in LE 9.2.3

I watch live TV on an RPi4 in Dubai from a TVH server (DVB-C) shared by one of Kodi developers in Helsinki with all traffic routed via a WireGuard tunnel that egresses in the UK, but without any noticeable issues that aren't easily explained by other things consuming bandwidth on the Dubai to UK leg, or bad weather in Finland. Why? .. because there is no terrestrial TV in Dubai and no option to use a Satellite receiver in the development where I live so it's the only way I get to test DVB related things. I also have access to a TVH server in Germany but the Finns don't dub everything and my schoolboy German sucks so the Helsinki server is more usable

No need to whitelist the non-1080p resolutions. Set Kodi GUI to 1080p60.

Re-reading the original post, I think you need to solve the server side issues as bad signal/reception or processing in the server is going to result in issues that can't be resolved client side. I doubt the client is the issue, although some of your original config wouldn't help.

I'm not much good with the server end as I never self-host it..

What's the DNS issue?

See if you can override it by creating /storage/.config/pulse-daemon.conf.d/default.pa? .. although I think this folder targets .conf files only.

Quote from kapqa

would you please investigate this?

Nope. I have absolutely no interest in reopening the firmly-closed pandora's box that is AppleTV support. I haven't touched that codebase in 3.5 years, so if it works for you that's great, but if it doesn't, sorry..

I think Oleg bumped mesa to HEAD which means he picked up lima/ppir: more tex rework and optimization (!4975) · Merge Requests · Mesa / mesa · GitLab which causes the problem, and is resolved in lima/ppir: use a ready list in node_to_instr (!5092) · Merge Requests · Mesa / mesa · GitLab which has been acked but not merged into mesa yet.

No, and due to a complete lack of cross-platform "casting" solutions that Kodi could implement, that's unlikely to change.

I've been told the AllowedIP setting is for internal WireGuard logic and WireGuard is not controlling the routing table. However, the WG connection is higher in the list of connman services (as it was created most recently) which means it becomes the primary service and default route. To change this we can change the service order via connmanctl, e.g.

connmanctrl move-after vpn_138_116_14_12_wg_domain_tld ethernet_1cf05e0b93f0_cable
Moved vpn_138_116_14_12_wg_domain_tld after ethernet_1cf05e0b93f0_cable

So syntax is: connmanctl move-after <service_to_move> <service_to_move_it_after>

So for scenarios where you want to connect via WireGuard to access content on a remote server, but otherwise still want/need the Internet connection to be as-normal from the local network, we can add another ExecStart in the connman.service file, e.g.

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/connmanctl connect vpn_138_116_14_12_wg_domain_tld
ExecStart=/usr/bin/connmanctl move-after vpn_138_116_14_12_wg_domain_tld ethernet_1cf05e0b93f0_cable
ExecStop=/usr/bin/connmanctl disconnect vpn_138_116_14_12_wg_domain_tld

NB: I haven't tested this, but it makes sense to me, so please have a play and report back.

NOTE: I have subsequently been told that the move-after changes are persistent, so would only need to be done once.

If using deinterlaced media make sure the 1080p@25/29.97/30 modes are NOT enabled in the whitelist so that Kodi will default to 50/59.94/60; as Kodi only outputs progressive and needs to render each interlaced half-frame as a full frame, requiring double the frame rate. Also set "Adjust refresh" to start/stop not always.

The one upgrade you can do that would make a difference is to replace the ATA drive with an SSD, as the stock drive is 5400rpm (and likely around a decade old - the fact it hasn't failed is a miracle) and although RAM is an unresolvable issue, swapping on an SSD is greatly improved. I've used SATA SSDs via an adapter in the past, but Amazon/eBay show mSATA to IDE/ATA drive converters now which would be easier to fit inside the case.

Which LE release?

Do you have "WireGuard.PersistentKeepalive" in your config?

I don't see issues with the connection dropping from LE, but I sometimes see issues from macOS to the same WG server.