While you’re trying to figure out the issue try do a side by side configuration comparison between 4.2 and 4.3. You can have both addons installed but only one enabled at a time. This should allow you to rule out any configuration issues between a working version 4.2 and a non working version 4.3. Make sure every setting is identical in 4.3.
Posts by petediscrete
-
-
The board is a Hauppauge WinTV-HVR4000(Lite) DVB-S/S2. Dmesg output attached. Also: a mux I defined, copying parameters for one that was successfully set up during an automated scan. No scan was triggered. The status tab shows 1 transport errors and 34 continuity errors, w SNR and signal strength unknown (ditto for the DVB-T tuner for the last two).
From what I can see in dmesg you are running in Docker. Is that correct. Firmware seems to be loading correctly and frontend looks ok. Could you post a screen grab of your tuner settings in TVH. It’s definitely pointing to a configuration issue.
Outside of the Docker is anything else using the Hauppauge tuner.
-
I have tried it in Armbian and received the same result. I'm suspecting the WIFI Module, or antenna might be the culprit. I've started a ticket with Pine64's support team and will keep y'all updated
Good luck with that.
I ended up buying a RPI WIFI dongle which used firmware that Armbian recognised. As far as I can remember this is it https://thepihut.com/products/usb-w…he-raspberry-pi
I couldn’t guarantee that it would work in LE but it might be it’s cheap and worth a try if you need WIFI. Personally I’d ditched WiFi in preference for wired Ethernet.
Development on the RockPro64 is practically non existent and only for LE I’d be using the board as a door stop.
-
Hey all,
I'm trying to set up LibreELEC on my PINE64 RockPro64 and I'm having a few issues with connecting to my network via wifi. I can't really find any great information about it through googling so I'm hoping someone here can help me out. I think the issue here is with software in LibreELEC or with something I am doing incorrectly at the OS level but I can go to the hardware for support if someone can show me how to figure that out.I used the latest (as of 03-22-2023) 11.0.0 arm image and wrote it to the SD Card.
The WIFI Module is plugged in.I can see the wifi networks in Settings > LibreElec > Connections but I cannot connect to the network. I continue to get the error invalid-key.
I've checked my password is correct in my router configuration and I'm 100% sure it's correct.
Plugging in Ethernet I can SSH into the machine and check the network configuration.Code
Display MoreLibreELEC:~/.config/system.d # journalctl -u iwd Mar 23 17:49:48 LibreELEC systemd[1]: Starting iwd.service... Mar 23 17:49:48 LibreELEC iwd[420]: Wireless daemon version 2.3 Mar 23 17:49:48 LibreELEC systemd[1]: Started iwd.service. Mar 23 17:49:48 LibreELEC iwd[420]: station: Network configuration is disabled. Mar 23 17:49:49 LibreELEC iwd[420]: Wiphy: 0, Name: phy0 Mar 23 17:49:49 LibreELEC iwd[420]: Permanent Address: 90:e8:68:73:8a:43 Mar 23 17:49:49 LibreELEC iwd[420]: 2.4Ghz Band: Mar 23 17:49:49 LibreELEC iwd[420]: Bitrates (non-HT): Mar 23 17:49:49 LibreELEC iwd[420]: 1.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 2.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 5.5 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 11.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 6.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 9.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 12.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 18.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 24.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 36.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 48.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 54.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 5Ghz Band: Mar 23 17:49:49 LibreELEC iwd[420]: Bitrates (non-HT): Mar 23 17:49:49 LibreELEC iwd[420]: 6.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 9.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 12.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 18.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 24.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 36.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 48.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: 54.0 Mbps Mar 23 17:49:49 LibreELEC iwd[420]: Ciphers: CCMP-128 TKIP Mar 23 17:49:49 LibreELEC iwd[420]: Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device Mar 23 17:49:49 LibreELEC iwd[420]: Wiphy phy0 will only use the default interface Mar 23 17:49:49 LibreELEC iwd[420]: No default interface for wiphy 0 Mar 23 17:49:49 LibreELEC iwd[420]: Could not register frame watch type 00b0: -22
iwd seems to detect the module and it seems to work ok with those 3 slightly worrying lines at end.
I added a /storage/.config/system.d/iwd.service file where I added the --developer option to the ExecStart option (Is this the right way to modify system.d daemons?)Code
Display MoreLibreELEC:~/.config/system.d # iwctl device list Devices -------------------------------------------------------------------------------- Name Address Powered Adapter Mode -------------------------------------------------------------------------------- wlan0 90:e8:68:73:8a:43 on phy0 station LibreELEC:~/.config/system.d # iwctl device list Devices -------------------------------------------------------------------------------- Name Address Powered Adapter Mode -------------------------------------------------------------------------------- wlan0 90:e8:68:73:8a:43 on phy0 station LibreELEC:~/.config/system.d # iwctl station wlan0 scan LibreELEC:~/.config/system.d # iwctl station wlan0 get-networks Available networks -------------------------------------------------------------------------------- Network name Security Signal -------------------------------------------------------------------------------- My Network psk **** XFINITY 8021x **** xfinitywifi open **** LibreELEC:~/.config/system.d # iwctl station wlan0 connect "My Network" Type the network passphrase for My Network psk. Passphrase: *********** Operation failed LibreELEC:~/.config/system.d # iwctl debug wlan0 get-networks Available Networks (debug) -------------------------------------------------------------------------------- SSID BSSID RSSI Freq Rank MDE -------------------------------------------------------------------------------- xfinitywifi 4e:7a:8a:3f:cb:c2 -65 5200 368 000000 My Network 4c:ed:fb:9e:2f:68 -31 2412 368 000000 XFINITY 6e:7a:8a:3f:cb:c2 -66 5200 327 000000 LibreELEC:~/.config/system.d # iwctl debug wlan0 connect 4c:ed:fb:9e:2f:68 Type the network passphrase for My Network psk. Passphrase: *********** Operation failed
I'm not sure why the operation keeps failing. I can garuntee the passphrase is correct. I'm even copy pasting it in to the same result. I'm not sure how to continue debugging the issue either. Any suggestions?
I do have some questions about where the WIFI module wire/antenna is supposed to go that aren't really covered in any of the docs I've looked into. It has a tiny bit of exposed metal wire with an adhesive pad and I keep wondering if I'm supposed to put that somewhere. It is currently just stuck to the side of the case. The docs I've looked at for the WIFI module are:- http://files.pine64.org/doc/guide/PINE…ation_Guide.pdf (doesn't mention the antenna wire at all)
- https://wiki.pine64.org/wiki/NASCase (just mentions attaching it as the diagram shows but doesn't reference the diagram)
- https://wiki.pine64.org/wiki/ROCKPro64 (A few references to the wifi module and some broken links to their store)
Have you tried to get the WiFi module working in Armbian to confirm it actually works.
-
LibreELEC is a project not a product. Ever evolving like many others on Github. The developers have nobody to answer to, but the user base have everything to be thankful for.
LE comes with no warranty expressed or implied. Unhappy users are welcome at anytime to walk away and try something else . That’s the brilliance of the open source world. Many clearly do not grasp that concept.
-
Why so rude? The problem is known and I am sure problem will get solved soon. Don't forget that many people work for nothing on projects like this. Your attitude is strange to me. Paying for something is not a sign of quality. My systems work quite well - exept that one needs WiFi (no cable possible). So we just have to wait or use our skills to help finding the bug.
Imagine the abuse he’d be giving if he was actually paying for the product.
-
OK, I'll persist (and thanks so much for your persistence). I don't actually know what the benefits of 4.3 are; I've seen reference to better comskip but that's all and that's not something I've used on Linux (used a plugin on Windows Media Center long ago).
Here’s all the benefits of the various builds made in TVH 4.3 https://github.com/tvheadend/tvheadend/commits
I’m convinced your configuration is the problem here. What model of Hauppauge PCI card are you using.
From what you’ve mentioned so far there’s no scanning happening at the moment. Remember there’s been a major Linux kernel change made since LE10. Could you post the output of dmesg.
-
I will probably set up another Pi this weekend with LE 11.0.1 on SSD and 8x4TB WD Red, if that works ok i'll hook up another 8x4TB WD Red. All disks will be NTFS.
Are you running a data centre 😂
-
TVH 4.3 is working fine. Once you’re tuner is correctly configured, you’ve created a DVBS network and added the complete details of at least one active mux on the satellite you are aimed at the remaining muxes will appear and scan. I suggest running the Wizard again and while it’s running click on the Status tab. You’ll be able to see if the scan is actually happening and what signal strength your tuner is displaying.
I only mentioned the fact that the hang up in the Wizard while scanning was resolved purely to highlight that this bug was present in 4.3 at one stage and was addressed. Personally I don’t use the Wizard or predefined muxes. No need as I manually configure everything.
I build my own TVH for a separate server I operate outside of LE. Again up to last nights build everything is functioning fine.
It’s entirely up to you if you want to get 4.3 working or remain with 4.2. I suggest you also post logs to enable us to investigate further. My feeling is an incorrect configuration is being supplied and as a result no valid scan is being performed.
-
Tuner is a Hauppauge model with Conexant CX24116/CX24118 #1 : DVB-S #0
It works perfectly with TVH 4.2, with the predefined muxes there is no issue completing the scan. With 4.3 the scan stops with 28 muxes to go.
That issue of freezing during scan of predefined muxes using Wizard was resolved in a later build of 4.3 TVH which can be seen on the TVH GitHub. It used to freeze at 75%. All you had to do was select Save and Continue tab in the Wizard and it would display what muxes it had found.
When you are adding one mux to scan I assume you are supplying all the relevant information in the Basic Settings section, setting it to Active and applying it.
Finally, are you using an Hauppauge USB tuner. If so read this RE: TBS Drivers on LE10
-
Well, maybe because most people use windows, at home & at work, Linux desktop has a market share of less than 1,5%.
Indeed but using Linux based board points to Linux based file system. I’m amazed the amount of RPI users who look to Windows tools to solve Linux problems.
Maybe if you haven’t already done so list the full details of your setup and how you have it configured. It may help others. Pointless in users posting “not working for me” and not helping in the troubleshooting process.
-
What brand tuners are you using. Have you got them enabled in the DVB Adapters section
-
Connected via USB, yes. No hub, and i boot from SSD, no slow sdcard. And Pi original power supply.
I never did see the point dragging a Windows ntfs formatted drive to a Linux party. Asking for trouble. Windows users find it difficult to “cut the chord”.
If as you say you have four drives ntfs formatted successfully attached to your Pi4 other users in difficulty should try and replicate your setup. That would be a good starting point to resolving their issue.
-
I have 4 (4x6TB) NTFS disks connected to one of mi Pi4's and i have had zero problems so far (not even on nightlys before LE11).
Are they physically connected via USB. Is there a USB powered hub involved.
-
Problems for the Linux kernel NTFS driver as author goes silentConcerns for Paragon CEO, and head kernel boss Torvalds suggests seeking maintainerswww.theregister.com
-
Once you’ve created a network, click on the network and select the Force a Scan tab. I assume you followed the wizard instructions up to the point of Add Predefined Muxes and selected the Cancel tab.
Just remove the network you’ve created, run the Wizard again to reconfigure TVH. Let us know how you get on.
-
Because of the Windows driver it's a tinker project. I would solder connectors onto the speaker contacts to avoid that driver.
With a frequency switch you could also use the subwoofer. If you don't want to invest the time, bring it back downstairs.
Unlike when I bought them there’s a YT video for everything
External Content m.youtube.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.I’ll give this a go over the weekend. Funny thing. The law of unintended consequences kicks in here. I remove the last excuse for anyone having to get off their ass to interact with the system. No manual controller. Kodi remote on all the phones and upstairs will refuse to part with the Companion 5 which I might add is older than the lot of them. I’d forgotten how good it sounded too.
Hi,
You are really playing in another class...
I'm just using this: UDA1334A connected to the RPi3B+ digital sound lines (I2S), with a good amplifier and a pair of old JBL floorstanding speakers.
I wanted something better than the RPi built-in audio-out connector...
That’s the great thing about LE on the RPI. So many possibilities. I’m not great at the tidy up phase of projects. Boards and trailing wires hanging off my media FrankenBox 😂
-
Yep, the Magic 100 is one of the best DAC's you can get, and it's known to work with LE. I mentioned the UMC22 in case you want to connect the Bose speakers to a cheaper DAC that just works.
You don’t mess with Bose equipment. Proprietary connectors. Nightmare. Reminds me of Apple equipment. Doesn’t play well with others.
I’ve nearly worked out how to bypass the Bose controller and let LE do all the lifting. This hopefully will kill off that undocumented Bose Mute feature that appears to be causing all the trouble.
Have to say, an old but still very capable Sony KDL 32inch (expensive in 2006 and HD Ready 🤩) teamed up with the Bose Companion 5 (2004 vintage ) and a humble RPI3b+ sprinkled with the LE fairy dust and you’ve got quite an impressive setup. In fact I’m thinking of bringing it back downstairs 😂