root@Omega-5286:~# opkg install kmod-usb-net-cdc-ether
Installing kmod-usb-net-cdc-ether (4.14.81-1) to root...
* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-net-cdc-ether:
* kernel (= 4.14.81-1-4d99ecc9745adb4d8a275d8e3a38961b) * kernel (= 4.14.81-1-4d99ecc9745adb4d8a275d8e3a38961b) * kernel (= 4.14.81-1-4d99ecc9745adb4d8a275d8e3a38961b) *
* opkg_install_cmd: Cannot install package kmod-usb-net-cdc-ether.
> Device Firmware Version: 0.3.2 b233
> Checking latest version online...
> Repo Firmware Version: 0.3.2 b233
> Comparing version numbers
> Device firmware is up to date!
root@Omega-5286:~# wget http://repo.onioniot.com/omega2/packages/core/kmod-usb-net-cdc-ether_4.14.81-1_mipsel_24kc.ipk
root@Omega-5286:~# opkg install kmod-usb-net-cdc-ether_4.14.81-1_mipsel_24kc.ipk --nodeps
Package kmod-usb-net-cdc-ether (4.14.81-1) installed in root is up to date.
To enable netconsole logging, you will specify the interface used to reach the syslog server, the IP and port of the syslog server, and optionally the MAC address of that server www.mcdvoice.com thank you
I will attempt to upgrade my image and pip install it. Pip install failed last time I tried. If you are interested in my use case, or have done something similar, here the talk : https://www.youtube.com/watch?v=mxyziRuSefI . Please let me know if there is something I have missed, hopefully I will have a working solution with the Onion as the high level processor soon.
@Michael-Mayo Hopefully the second one will work well.
I'm only guessing - probably the first one did not survive your soldering process.
The HW_RST_N (pin 5) (ie. the Hardware Reset Input) does not work on Omega2+ / Omemega2S+ at all.
You should make a Software RESET BUTTON:
GPIO_38/SW_RST (pin 4) --- 1 kOhm resistor --- a normally open momentary push button --- +3.3V
If Omega2 successfully boots press this button - a short press will Reset it - a long press will perform a Factory Reset
@Peter-Carr I aggree, with some common sense I was able do it, but I would urgently ask the Onion team to update their documentation. Obviously there are some differences in newer firmware versions like b233
I added a 1 GB SD-card. it was already formatted and automatically mounted. So I only had to start the slightly modified tar command and then I had to modify /etc/config/fstab file
(But before that it took me hours and several firmware resets)
After some troubleshooting< I determined the following:
Older Omega2+ (with older firmware) worked as expected. No problems connecting using SSH on PuTTY.
I was able to connect to my new Omega2 using SSH on my older computer which had an older version of Putty.
I uninstalled and removed all Putty files (not as easy as one would hope) then reinstalled and tried again with the same results.
Finally, I noticed that I had the 32-bit version of Putty and installed the 64-bit version instead. That finally worked. So there is something with using the latest 32-bit putty on 64-bit windows that gives this fatal error with the latest version of Omega2+ firmware when doing SSH.
At least it's working now so I can move on to the next step.
I am a member of this project. Last week I was asked to fork a repo from the project. I tried but received a permission error. The person who manages this Azure DevOps project made some changes and now I cannot see the repo at all. Could you please take a look what can be the problem krogerfeedback.com survey
@William-Jones yes I have 3 or 4 on WEP (reluctantly) all on one site and router. I would suggest you try another router, WEP is inherently insecure so I don't think anyone is going to fix an issue related to WEP.
Thanks. I'd seen that before, ran into bigger problems with the pigpio build (eg no ldconfig available for the omega). That said, I found a method to use with the smbus2 package that allowed me what I needed.