Is there a way to see if it’s a possible bug in LE?
Stranding at the boot logo sounds like a sure bet.
We have a bug report sub-forum you can use.
It's important to follow the rules for bug reports.
Post the part of the EFI settings, which do not work for LE (enabled iGPU).
Provide a log file.
If you can login by SSH while stranding at boot logo, then the output of dmesg and lspci would be interesting.
When iGPU and eGPU are enabled, then Linux should select one. Usually it's the eGPU. I guess it's an LE bug not to do so.
To use multiple GPU's at the same time needs compatible GPU's and special driver support. I don't know your iGPU, and I bet it's not compatible to your eGPU. Generally your eGPU can be clustered (adding more eGPU's) by using AMD CrossFire.
I tried posting this in add-on section but there were no replies?
Trust me, we notice what you write, and we think about it, too. You can browse the add-ons, and if you don't find what you need, then it's a feature request. Simple thing.
I'm having similar problems with DHCP failure over 5GHz wifi. Wired is fine and 2.4GHz wifi is fine.
kodi log http://ix.io/20c1
dmesg log http://ix.io/20c2
I know that 5GHz is preferred if you live in a high density WLAN area, where most users take a 2.4GHz channel.
I don't see any WiFi related errors at your logs. My conclusion is that the 5GHz signal of the RPi is too weak to establish a stable connection.
The higher the frequency, the higher the need of energy to generate that frequency.
You could try a stronger PSU, which maybe results in a stronger 5GHz signal. I'm sure it's not a software issue.
I too am having the same issue as above. My log file is similar to OPs.
Since downgrading to LE 9.0.2 I have no safe mode issues on my RPi anymore.
It looks like your microSD card is bad:
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs'.
Program terminated with signal SIGSEGV, Segmentation fault.So check the card for bad blocks, and eventually repair (GParted tool, only for advanced geeks) or replace it.
I don't have Sky Go, but for DAZN Germany I had to downgrade from LE 9.1.x to 9.0.2. Give it a try.
...so I can see the people streaming there...
You are talking about "seeing". Do you mean video mixing, like a split screen?
Use GUI.ShowNotification:
curl -fs -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"GUI.ShowNotification","params":{"title":"'"<TITLE>"'","message":"'"<MESSAGE>"'","image":"'"info"'","displaytime":'"10000"'},"id":1}' http://<HOST>:8080/jsonrpcRead here for info about params. It works for me.
Next attempt will be upgrade through SSH. We will see...
Use wget to download the image at SSH session.
config.txt looks OK. At your asound.conf I don't see a bindings parameter inside pcm.dmixer. Check whether you need to add this.
Maybe you forgot to do the DAC settings at config.txt.
I put the above script, but when restarted, Libreelec freezes and only the logo remains.
Then there is no need to stop /start Kodi, as mentioned by comrade chewitt. Try this:
#!/bin/sh
pactl load-module module-udev-detect
pactl set-default-sink alsa_output.0.iec958-stereo
pactl set-default-source bluez_source.74_9E_AF_73_EC_4F.a2dp_sourceMany thanks Da Flex, at the "Update channel" I see the different versions and I have choosen 9.0 (MR) but the Available Version tab is empty. 9,2 is also empty and 8.0 shows 8.2.5. I upgraded to 8.2.5 sucessfully but 9.0 and 9.2 stills being empty.
How can I upgrade to 9.0 then?
Then download the image manually, and put it into the update folder.
Do you have the update channel 9.0 at the LE settings menu? If yes, then the upgrade should work fine by using the menu, and your settings will stay.
#!/bin/sh
systemctl stop kodi
pactl load-module module-udev-detect
pactl set-default-sink alsa_output.0.iec958-stereo
pactl set-default-source bluez_source.74_9E_AF_73_EC_4F.a2dp_source
systemctl start kodiPut the calls into /storage/.config/autostart.sh.
Seems like my post got deleted from the bug report forum :-s
If you are sure that it has been deleted, then your report maybe don't complies with the rules for bug reports (see first pinned post at the sub-forum). Try again. I think it's worth it, because bugs on RPi 4B are normal at this early state of development.
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs'. Program terminated with signal SIGSEGV, Segmentation fault.
Check your storage device for bad blocks.
