Alpha Leia error with newest commit
#31
Here's the GDB and BT outputs:

https://pastebin.com/0KDKDqU1

Please let me know what to try next
Reply
#32
thread all bt
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#33
That returns "invalid thread ID: all bt"
Reply
#34
Come on :-) Read the gdb howto - I type that stuff out of my head: thread apply all bt
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#35
haha first time I've used gdb, give me a break (debug-pun intended)

here's the results:
https://pastebin.com/YRSrrmE7
Reply
#36
No idea, something specific to your machine.

Start looking here:
0xf58230e4 in drmModeAtomicCommit () from /usr/lib/libdrm.so.2 some self hacked kernel?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#37
I checked the libdrm package and discovered it was using a custom repo. So I rebuilt the package to match the config in LibreElec. I also slightly updated the glibc package so it also matches LibreElec as well. Unfortunately, after recompiling both, same behavior. I cleaned up those python error messages during gdb as well, here's an updated pastebin. I believe this is where I run around in circles yelling for help, right?
https://pastebin.com/CqZfA0uQ
Reply
#38
something with your python is broken.
Code:
Could not find platform independent libraries <prefix>Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>].
.
ImportError: No module named site
Reply
#39
Thanks for all the help! Took me some time to figure out the python issue but with your help I was able to get it resolved.
Reply

Logout Mark Read Team Forum Stats Members Help
Leia error with newest commit0