Three core rules for using this forum:
No personal attacks
No offensive language
No advertising or spam
If you break one of the core rules, you're liable to get banned at the discretion of the moderators.
Read on for the full Forum Guidelines and Terms of Service.
@swalker2001 The issue is that of emultion. Check your terminal app to see what emulation it is configured for, I suspect it is probably set to tty. I'm not sure what the official emulation is but Xterm, vt100/102 work well.
The kernel objects in the Linux OS' are very capricious thing and one of the biggest problem. So... kernel object will work only in the same kernel version and build number, well I want to say these are likely static feature than dynamical as it give us.
We (users) can't append sound driver or TFT-display (frame buffer driver and his friends), PCI Express->SATA controller, etc.!
To append your own kernel object you have to build you own firmware - it's not convenient. Second way - build kernel objects on the omega (direct compilation), but it needs special tools, like linux-headers-*, that's out of repositories too.
Let's type code in Python! ((
@crispyoz @Lino-Amorim Absolutely. I didn't linger on the topic long enough to consider causation. You are likely using dynamic IP address allocation at the router. This results in the "dynamic" that isn't really a problem, if you're comfortable with it. The address lease will expire at some time (typical is 24 hours) and the same address will be re-leased if the client is still connected. If the client is not connected at lease expiration the next connection may result in a new IP address, even if you don't have a new router.
In my home I prefer more stability. As such most of the 20 or so IP addresses in use are fixed, with a few dynamic. You can do this by turning off IP address allocation at the router and begin using your Linux box as a dhcp server. You would pair up a device MAC address and the IP address you desire in the /etc/dhcpd.conf file. There's more to it than that, but not much more.
If you'd like to go down this path, please do a little on-line research and take a crack at it. There's assistance available here. The folks on this forum are great!
@Anupam This is a community support forum so we won't have access to any of the details you have previously provided. If you post whatever information you have, members of the community may be able to assist,
-dev(...elopment) files install only inside SDK. Runtime OS doesn't have and need that, you can find only dynamic libraries (*.so). Static libs (*.a) don't install too.
You have to manual compile lib in the SDK, then you can see all files. But why your Python project need c-headers, It seems incorrect?!
@crispyoz thanks for letting me know! It looks like the factory tried to glue it down but didn't apply enough to even reach the connector (or it spilled out — there's a stain on the board below the connector.)
Just to note that this has been yet another FULL three(3) years with no resolution on the current platform provided by the company. No matter what tips or tricks I tried, this piece of garbage STILL doesn't work here in Canada.
Onion please give me a way to return this $h!T and get my money back, ALL of it.
Just write up a doc, tested and verified if you have to that PROVES that this stuff works with a few extra steps. Don't make people read endless efforts and failures for HOURS of wasted time in trying to debug something that WORKED with the original firmware!
Also, provide the ORIGINAL firmware on your download URL (http://repo.onioniot.com/omega2/images/) so that some of us can at least limp along with old crap rather thank a useless brick!
@crispyoz @György-Farkas I don't know if you work for Onion but you seem VERY active here in the forums. Can you please connect this to the right folks and get this escalated?