Posts made by T NT
RE: Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ... and a possible reason
These are interesting findings, they suggest there may be a bug in the wifi driver than can be triggered by variations in local circumstance.
Hmmm I am wondering now if that is why out of the 3 APs I have both on G and N my Omega only sees one. I tried playing around with the channels encryption cyphers etc. But to no avail.
RE: Are there 2 versions of the Expansion Dock?
For the record it appears that despite label differences the GPIO assignments are the same. So I am able to use GPIO 0, 14, 18, 19, 23 and 26 no problem. I can probally also use 12 & 13 as well.
This is good news for me because I had already hot-snoted my expansion dock in place and did not fancy pulling it apart again.
FYI: Omega 2+ can be powered down.
So I was experimenting with my shutdown procedure and power-down and power-off are pretty useless in that regard in so much as they don't poweroff and halt the CPU but instead reboot it.
However, I have discovered if I used Linux's magic sysrq interface to send the 'Power off immediately' command. It does just that. The led goes out and the dock is dead until power is reset.
Test it yourself. Just remember that it is immediate power off so no syncing of any kind will happen. You will have to manually sync and unmount disks yourself.
echo "o" >/proc/sysrq-trigger
Still handy to have at the end of a shutdown script though.
RE: Are there 2 versions of the Expansion Dock?
omega2 will not work in first omega
Umm.. mine is. Just the labels on the GPIO expansion differ a little. So I am not 100% sure where GPIO11 is for example because it is not shown on my dock.
This is what it looks like:
Also this dock still provides a console over USB. I've used that to debug wifi problems before.
RE: Connect Omega2 to CanBus
Well looks like you would need to build some sort of interface to talk over the UART on the Omega but aside that on the software side seems there is something in LEDE.
canutils - 0e3ff3b3-2 - CAN userspace utilities and tools
canutils-asc2log - 0e3ff3b3-2 - Utility asc2log from the CAN utilities package.
canutils-bcmserver - 0e3ff3b3-2 - Utility bcmserver from the CAN utilities package.
canutils-can-calc-bit-timing - 0e3ff3b3-2 - Utility can-calc-bit-timing from the CAN utilities package.
canutils-canbusload - 0e3ff3b3-2 - Utility canbusload from the CAN utilities package.
canutils-candump - 0e3ff3b3-2 - Utility candump from the CAN utilities package.
canutils-canfdtest - 0e3ff3b3-2 - Utility canfdtest from the CAN utilities package.
canutils-cangen - 0e3ff3b3-2 - Utility cangen from the CAN utilities package.
canutils-cangw - 0e3ff3b3-2 - Utility cangw from the CAN utilities package.
canutils-canlogserver - 0e3ff3b3-2 - Utility canlogserver from the CAN utilities package.
canutils-canplayer - 0e3ff3b3-2 - Utility canplayer from the CAN utilities package.
canutils-cansend - 0e3ff3b3-2 - Utility cansend from the CAN utilities package.
canutils-cansniffer - 0e3ff3b3-2 - Utility cansniffer from the CAN utilities package.
canutils-isotpdump - 0e3ff3b3-2 - Utility isotpdump from the CAN utilities package.
canutils-isotpperf - 0e3ff3b3-2 - Utility isotpperf from the CAN utilities package.
canutils-isotprecv - 0e3ff3b3-2 - Utility isotprecv from the CAN utilities package.
canutils-isotpsend - 0e3ff3b3-2 - Utility isotpsend from the CAN utilities package.
canutils-isotpserver - 0e3ff3b3-2 - Utility isotpserver from the CAN utilities package.
canutils-isotpsniffer - 0e3ff3b3-2 - Utility isotpsniffer from the CAN utilities package.
canutils-isotptun - 0e3ff3b3-2 - Utility isotptun from the CAN utilities package.
canutils-log2asc - 0e3ff3b3-2 - Utility log2asc from the CAN utilities package.
canutils-log2long - 0e3ff3b3-2 - Utility log2long from the CAN utilities package.
canutils-slcan_attach - 0e3ff3b3-2 - Utility slcan_attach from the CAN utilities package.
canutils-slcand - 0e3ff3b3-2 - Utility slcand from the CAN utilities package.
canutils-slcanpty - 0e3ff3b3-2 - Utility slcanpty from the CAN utilities package.
These are all taken from the Linux CAN Project
Are there 2 versions of the Expansion Dock?
I just noticed that the Expansion dock I am using (from the first Onion campaign ) has a different pin out from the one in the documentation.
Was there more than one version of the dock? In which case should I follow the documentation pin out for new dock given it is plugged into the Omega 2+ or should I follow the markings on the dock itself?
I am mindful that I must not use some pins that are needed for the boot process so I don't want to make a mistake.
RE: bluetooth libraries?
It is not obluez, it is just bluez.
bluez-daemon - 5.38-1 - Bluetooth daemon
bluez-examples - 5.38-1 - contains many examples apps for bluetooth, requiring python
bluez-libs - 5.30-1 - Onion-Customized Bluetooth library
bluez-libs - 5.38-1 - Bluetooth library
bluez-utils - 5.38-1 - Bluetooth utilities
bluez-utils - 5.30-1 - Onion-Customized Bluetooth utilities
RE: SSL Cert for onion.io Expired. PLEASE FIX ASAP!
Sorry about the oversight. It's fixed now.
Yeah.. happens sometimes. But really you should move away from GoDaddy and use letsencrypt's certbot. Then you would not have to manually update it yourself you can have a script update it automatically.
Just a thought.