That's actually a feature from OpenWRT (not strictly to the Omega itself) to save space on embedded devices, since most of them won't have the luxury to spend precious space with a list of packages that's not-so-often used
Posts made by Igor Moura
RE: [RESOLVED] `opkg update` resets when rebooting?
RE: Wireless connection instructions on 0.0.8 b297 ?
@None-None You can connect through a serial connection, edit the /etc/config/wireless file to enable your connection on that list (change the option disabled from 1 to 0) and run the wifi command, that way you will have a network connection until you reboot (that's enough to update the packages and get all running for sure)
Unable to connect to Wifi after update
After updating my omega to 0.0.8 I can't connect to my wireless network anymore.
That's the output of wifisetup:
root@Omega-0AAD:/# wifisetup 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: Scan failed, try again > ERROR: specified ssid not in the database
Here is the output of uci show wireless | grep disabled
root@Omega-0AAD:/# uci show wireless | grep disabled wireless.radio0.disabled='0' wireless.@wifi-iface.disabled='1'
When I try to change the value from 1 to 0 and reboot, it goes back to 1.
Error while trying to install with npm
After updating my onion and installing node/npm, I can't install anything using npm, all it does is throw me the following error:
npm ERR! Linux 3.18.27 npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "npm@latest" npm ERR! node v4.3.1 npm ERR! npm v2.14.12 npm ERR! code ENOTFOUND npm ERR! errno ENOTFOUND npm ERR! syscall getaddrinfo npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Please include the following file with any support request: npm ERR! /root/npm-debug.log
It's worth saying that I don't have a proxy and I'm able to ping/curl without problems.