Are you using tea leaves or a crystal ball to derive this knowledge?
Doesn't the kernel detect devices at boot time?
Posts by Da Flex
-
-
The audio devices seem to be detected correctly. There must be an audio routing error on LE side.
Do this from SSH terminal:
- getedid delete
- reboot
-
Also check different HDMI ports on TV. They often don't have the same capabilities.
-
1. Downloading a bunch of movies and dont use internet at all.
2. Putting a ethernet cable from my bedroom (2nd floor) ALL THE WAY to the living room (1st floor).
3. Buying an Ethernet-to-WiFi adapter.
-
i use a triple boot system, which files do i have to copy to the partion in order to install from scratch. I remember that i had to extract 2 files from the image-file, to get it working...
We have two threads about multi-boot at Showcase section.
-
Install LE from scratch, and then just test with Waipu. Use our log server to provide logs.
-
Thanks but it had nothing to do with the dns service, i use a vpn which i disable when i am testing new builds.
Hmm, I'm still reading VPN messages in your latest log:
Code2025-12-20 09:35:08.570 T:1572 error <general>: VPN Mgr : (service.py) VPN monitor service detected VPN connection is not running when it should be ... 2025-12-20 09:35:12.416 T:1572 info <general>: VPN Mgr : (service.py) VPN connected to de-fra.prod.surfshark.comsurfshark_openvpn_udp ... 2025-12-20 09:43:16.922 T:1572 debug <CAddonSettings[[email protected]]>: trying to load setting definitions from old format...I would uninstall all VPN-related stuff to test Waipu, just to get clean logs. chewitt knows more about VPN...
-
The developer of the Waipu add-on is your target person, but most add-on devs are at Kodi forum. They aren't here.
Try a different DNS service:
Code2025-12-20 09:35:06.904 T:1581 error <general>: CCurlFile::CReadState::FillBuffer - (0x7f176c003fc0) Failed: Could not resolve hostname(6) 2025-12-20 09:35:06.904 T:1581 error <general>: CCurlFile::Open - <https://auth.waipu.tv/oauth/token> Failed with code 0: 2025-12-20 09:35:06.904 T:1581 error <pvr.waipu>: [Http-GET-Request] error. status: -1, body: 2025-12-20 09:35:06.904 T:1581 error <pvr.waipu>: [OAuthRequest] no network connection 2025-12-20 09:35:07.104 T:1581 error <general>: CCurlFile::CReadState::FillBuffer - (0x18002600) Failed: Could not resolve hostname(6) 2025-12-20 09:35:07.104 T:1581 error <general>: CCurlFile::Open - <https://auth.waipu.tv/oauth/token> Failed with code 0: 2025-12-20 09:35:07.104 T:1581 error <pvr.waipu>: [Http-GET-Request] error. status: -1, body: 2025-12-20 09:35:07.104 T:1581 error <pvr.waipu>: [OAuthRequest] no network connection -
Which log files i need to paste? Got couple of them.
Debug log.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
ChatGPT says UPnP/DLNA works for broadcasting from Kodi. I never did that.
-
daniel712 If you need a cheap Netflix box, get an Amazon device (Fire TV, Cube etc.). Netflix isn't well-supported on Kodi (limited resolution). Amazon delivers updates for many years.
The Nvidia Shield is pretty much the king of all set-top boxes. If affordable, get it.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
-
JonnyGators I understand your wishes, but you're asking for a professional solution. LE is made by hobbyists for many different devices. Even if users would be able to answer all setup questions, a bad HDMI cable, or a wrongly selected HDMI port on TV can still destroy the setup.
It's like on all Linux systems: LE is powerful and extremely configurable, but the perfect GUI setup is a truckload of work.
-
Doesn't matter. Dolby Vision costs money per device license. Buy a device with a DV license.
-
Please explain your setup first. Which RPi? Which LE? Which TV?
-
OK, I've concluded - I think - my problem isn't just with tvheadend-related add-ons. As far as I have noticed, I simply can't install add-ons from the LE repository. I get the aforementioned "couldn't connect to server(7)". I can't say I understand how this all works, but I've noticed that the URL for the files to be downloaded starts with "https://addons.libreelec.tv". If I understand, the portion addons.libreelec.tv needs to resolve to a valid IP addr., which according to the DNS server I'm using, it does not. This would explain why LE can't connect. Is this close to correct? I don't exactly understand why I'm apparently the only one who has run across this issue.
You're not the only one:
Seems like a DNS problem, because it works for other users.
Please test those commands on SSH:
Codenslookup addons.libreelec.tv wget https://addons.libreelec.tv/12.2.0/ARMv7/arm/addons.xml.gz -
I can access the Kodi add-on repository, but not the LibreELEC add-ons repo ("could not connect to repository" - timeout?) Happened on both builds.
Also reported by another user. Could be a problem with our LE repo:
