@Boken-Lin , Kernel upgrade didn't go up to 3.13.0-68-generic for some reason.
I can only bring it up to 3.13.0-55-generic. insmod seemed to work, but the connection still isn't working.
After all those failed attempts, I decided to upgrade to the latest long-term supported kernel 4.1.13. I used the instructions shown at:
http://linuxg.net/install-kernel-4-1-x-on-ubuntu/
Then followed the instruction for installing the cp210x driver.
And the serial connection works now!
Anyone have problems with factory reseting their omega? I'm using the expansion dock. Pressing the reset button for 10 to 30 seconds definitely reboots the omega, but it doesn't seem to change the omega back to its factory settings.
@Anthony-Sadarangani Try expanding the storage by using USB storage. Check out Boken's tutorial on using pivot-overlay. I expanded my rootfs to 8GB by following his tutorial.
https://wiki.onion.io/Tutorials/Using-USB-Storage-as-Rootfs
One more useful package to install:
opkg update; opkg install macchanger
Also, to use the Omega in monitoring mode, remember that you can't simultaneously monitor the network and remain in the managed mode. So that means you'll need to have a very reliable USB serial connection to the Omega to configure it back to the normal mode (i.e. managed mode).
Breakthrough! I'm answering my own questions:
To be able to use the "iwconfig" command, I needed to install the wireless-tools pkg:
opkg update; opkg install wireless-tools
To be able to use the "tcpdump" command, I needed to install the tcpdump pkg:
opkg update; opkg install tcpdump
To be able to use the "airmon-ng" command, I needed to install the aircrack-ng pkg:
opkg update; opkg install aircrack-ng
I've been doing a lot of searches on how to turn-ff the LEDs completely, but nothing is working on my Omega2 Expansion Dock and Omega2.
I've seen the documentation on how to turn-off the RGB LED on the Omega 1 expansion dock, which doesn't apply here.
Any help would be appreciated.
@Boken-Lin The reset button works when using the standard Omega image. But it didn't work for me when I had the cross-compiled image loaded on the Omega. I know there's also another discussion somewhere in this Community site about having a list of the standard omega packages that are missing in the cross-compiled image. That would be nice to have a list of those packages -- kinda giving us the ability to build the standard omega image from scratch.
Solved this problem by following the tutorial on reflashing the firmware with the Ethernet dock.
https://wiki.onion.io/Tutorials/Reflash-The-Firmware-With-Ethernet-Expansion
@Boken-Lin -- Yes, both oupgrade and wifisetup work. One minor thing on oupgrade: It rightfully identified that b259 is in the device, but it says the latest firmware is b251 -- and that I have the latest firmware anyway.
@Boken-Lin -- It worked!
Interesting event though after I reflashed the omega. I downloaded another image in a folder on the root directory...and forgetting that I didn't expand the rootfs with pivot-overlay, I filled up the storage. When I rebooted the omega and went back to delete the .bin image file, it kept telling me that it's a read-only file system and that I can't delete any file or folder. Even with a "rm -rf <directory_name>", the omega kept telling me that the file system is read only.
I fixed it by pressing the factory reset button -- which is also a good test that it's now working again.
Thanks for helping me through this issue. I learned so much from this event.
@Boken-Lin -- I wish I took a snapshot of the log. I didn't, unfortunately. I just remember that when I finally got back to my setup, the omega's orange light was completely off, and the screen was either blanked out or just frozen. (Normally, after a reflash and reboot, I have to hit carriage return to get back to the omega's terminal prompt....but this time, it didn't do anything and the omega was completely off.)
Any estimate on when that tutorial to un-brick the omega will come out?
Thanks for your responsiveness!
Yes, I do. Not sure that's what happened...I left the omega for at least an hour while it was reflashing. But when I came back to it, the LED was off and nothing was happening on the screen.
@Boken-Lin -- I'm 100% sure. And after various attempts of sysupgrades from a new .bin file from my cross compile environmnt, my omega still wouldn't get flashed. Then my last flash of was actually a fresh image from the repo site: v0.0.5-b259.bin.
After it went through the flash process, the LED on the omega turned off and it stayed off -- I assume the system just stopped. So I powercycled the dock using the on/off switch. I saw a lot of lines that generated the same errors that says "jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00ea003c: 0x0f56 instead"
See the final screen below:
It looks like there's finally a critical failure of some kind and the only thing I could get into at this point is the portion where I hit any key to stop the autobooting (I assume that the U-Boot for the Onion Omega.
@Boken-Lin -- Even after I was able to assign the ip address, broadcast, and netmask to the omega, it errors out when executing the following wget:
wget https://raw.githubusercontent.com/OnionIoT/wifisetup/master/wifisetup.sh
So I had to download manually through my Ubuntu VM, then transfer the two files via python SimpleHTTPServer.
Here's the result of running wifisetup.sh:
root@OpenWrt:/tmp2# ./wifisetup.sh Onion Omega Wifi Setup Select from the following: 1) Scan for Wifi networks 2) Type network info q) Exit Selection: 1 Scanning for wifi networks... Command failed: Not found Failed to parse message data WARNING: Variable 'results' does not exist or is not an array/object ERROR: no networks detected... try again in a little while root@OpenWrt:/tmp2#
And here's the result of running oupgrade.sh (after running opkg update):
root@OpenWrt:/tmp2# ./oupgrade.sh ./oupgrade.sh: .: line 4: can't open '/usr/lib/onion/lib.sh' root@OpenWrt:/tmp2#
If this issue persists, maybe I can help write up a tutorial on how to manually install the base/factory files into the omega without flashing (if that's even possible). It seems that there are some foundational files and folders/directories missing in the OpenWRT baseline that is in my omega.
Not sure why even the factory reset is not working.
If all else fails, can I send my omega back for replacement?