No, I think the most logical solution is to find the message in the kernel and rebuild the platform without it. However, that's more risk than I can take. I'll pry end up implementing my own syslog receiver so I can filter it out.

I've been hunting, but I'm not finding what I want. I know I can use sysfs to poll for GPIO interrupts, but Kit Bishop also had the GPIO signal interrupt working for the Omega. I'm wondering if that GPIO signal interrupt capability is available for the 2+ in the latest builds somehow? There is no gpio-irq kernel module available in opkg that I can find, and as built, /sys/kernel/debug/gpio-irq doesn't exist. I know I can build the gpio-irq .ko for this board, but am still working on getting kernel modules to build for the Onion. Hope to solve that today or tomorrow depending on time.

The big question is, does this still work like it used to, or are we limited to sysfs and poll()?

Thank you.

Thank you, it wasn't. I had forgotten the oledSetTextColumns() call. Fixed it, thanks for the reminder/help.

I have the latest firmware, 0.3.2 b218, and the C library for the OLED control seems to ignore newlines. Strings with newlines work fine if I write using oled-exp, but they don't when calling oledWrite("string"). Has anyone else noticed this? Is there a workaround?

I'm going to file a bug here shortly.

I suspect this is either a bug in the iwinfo binary, or just a missing bit of statistical data from the WiFi firmware. It doesn't work on mine either.

I suspect they do this to save money. There isn't a compelling reason to have an Onion on both WiFi AND Ethernet at the same time as the chip itself isn't that powerful, so the only problem it would solve is to allow the chip to be on two different subnets at the same time. The network speed won't improve much by having both connected. I suspect it's a trade off they chose to take advantage of.

DHCP servers generally use MAC addresses for association in a database. It gets the MAC, stores some association data, and then sends out the response package. Since the connection TO the DHCP server is functionally anonymous from the requester, using MAC provides a very easy way to store associated data for lease continuation and what not. What you are seeing is two requests from two different interfaces into a DHCP server which just sees the same request twice, so it sends back the same results twice.

There isn't much you can do about this, but the question would be, do you need both active at the same time? If not, turn one off.

Replying to my own. I don't see GDB in the package database, so I simply built it from the LEDE system and copied it to my target.

Is it possible to disable the following logd message?

kern.info ap_client: 'apcli0' assoc: yes, mac: 10:c3:7b:d1:e1:f0

This happens every 8 seconds while the unit is up. The problem is that I'm sending log data to my NAS as my application is using the logd service to write diagnostic and error data that I want to be able to keep. Can this message be turned off somewhere? It's not useful as a debug mechanism, and I can't filter on the NAS to ignore that message. It's drowning out my application data.

Thanks in advance.

Is this something dumb I'm doing? Why can't I get gdb on my Onion? Using the opkg install gdb command fails with a no package found. I can find valgrind, but that doesn't help, and is the only thing that really shows up when I dig into searching opkg packages. Is this something I need to build myself? I can do that, but would rather just install it. Or did I miss a step somewhere?

Running latest firmware 0.2.2 b200 if someone knows the answer. Thanks.

Did you ever figure this out? I think if you just want a server running, install the latest firmware, and you have one running. Connect your omega to a local wifi network, and you have a .local available address on your subnet. I do this as I use an Omega2 as my MQTT server for my local network. I changed my hostname to mosquitto and now through my network via the web console app and I can connect to this server using mosquitto.local from other hosts. It doesn't take a lot of setup.

Or, was your question related to something else?