Anyone? Is anyone running Ω-ware 0.2 with a functioning web Console? If so, what's the size of your /usr/bin
, /usr/lib
and /www
directories? Seems like a pretty fundamental issue I've encountered...
Posts made by Heath Raftery
-
RE: Console no longer fits on Omega2 with Ω-ware: 0.2.0 b196?
-
RE: WiFi client broken after update to Ω-ware: 0.1.10 b160
@Lazar-Demin Yeah it worked in 0.2 (see my followup thread with brand new issues). So I guess the issue was that
oupgrade -force
actually downgraded! What a rough ride... -
RE: WiFi client broken after update to Ω-ware: 0.1.10 b160
I wasn't able to solve it and eventually bricked the device, so was forced to start fresh. That fixed my WiFi woes, but now I have space issues.
-
RE: WiFi client broken after update to Ω-ware: 0.1.10 b160
I wasn't able to solve it and eventually bricked the device, so was forced to start fresh. That fixed my WiFi woes, but now I have space issues.
-
Console no longer fits on Omega2 with Ω-ware: 0.2.0 b196?
I've just re-flashed my Omega2 after bricking it again trying to get WiFi working. So I now have a fresh Omega2 with Ω-ware: 0.2.0 b196. I was then able to get WiFi working. The very next thing I did was try to install the console using:
uci set onion.console.setup=1 uci set onion.console.install=1 uci commit onion console-install-tool
Nothing happened for many minutes, until finally I got:
ln: /etc/rc.d/S50php7-fastcgi: No space left on device uci: I/O error
And then a whole bunch more
No space left on device
messages. Once it finished I rebooted, and got:Your JFFS2-partition seems full and overlayfs is mounted read-only. Please try to remove files from /overlay/upper/... and reboot!
I inspected
/overlay/upper/
with a bunch ofdu -a -h -s
commands and found thatwww
contained 11.5MB. Withusr/bin
at 4.3MB andusr/lib
at 3.1MB, it's full!I deleted the entire contents of
www
so they I could continue, but of course I've had to give up Console/OnionOS.Is this to be expected? Does OnionOS no longer fit on an Omega2?
-
RE: WiFi client broken after update to Ω-ware: 0.1.10 b160
This is all that appears in
dmesg
:[ 4654.457604] br-wlan: port 1(ra0) entered disabled state [ 4656.104124] EEPROM:Read from [factory] offset 0x0,length 0x400. [ 4658.588386] ch1 bssid=78:8a:20:71:08:f1 [ 4658.592427] ch1 bssid=c8:3a:35:7a:e9:b4 [ 4658.596409] ch1 bssid=8a:8a:20:71:08:f1 [ 4658.600420] ch1 bssid=7a:8a:20:71:08:f1 [ 4658.604403] ch5 bssid=02:9f:c2:fd:00:c1 [ 4658.608399] ch6 bssid=9a:8a:20:54:4d:3e [ 4658.612381] ch6 bssid=78:8a:20:54:4d:b4 [ 4658.616359] ch6 bssid=00:24:6c:c2:cd:80 [ 4658.620357] ch6 bssid=78:8a:20:54:4d:3e [ 4658.624337] ch6 bssid=8a:8a:20:54:4d:b4 [ 4658.628316] ch6 bssid=8a:8a:20:54:4d:3e [ 4658.632314] ch6 bssid=04:bd:88:21:74:21 [ 4658.636294] ch6 bssid=04:bd:88:21:74:22 [ 4658.640284] ch6 bssid=7a:8a:20:54:4d:b4 [ 4658.644264] ch6 bssid=7a:8a:20:54:4d:3e [ 4658.648242] ch6 bssid=9a:8a:20:54:4d:b4 [ 4658.652239] ch6 bssid=00:24:6c:c2:cd:82 [ 4658.656219] ch11 bssid=6c:72:20:3d:f4:d2 [ 4658.660292] ===================================================== [ 4658.666476] Channel 1 : Dirty = 310, False CCA = 0, Busy Time = 12300, Skip Channel = FALSE [ 4658.674960] Channel 2 : Dirty = 392, False CCA = 0, Busy Time = 2459, Skip Channel = FALSE [ 4658.683369] Channel 3 : Dirty = 428, False CCA = 0, Busy Time = 1305, Skip Channel = FALSE [ 4658.691760] Channel 4 : Dirty = 464, False CCA = 0, Busy Time = 7754, Skip Channel = FALSE [ 4658.700163] Channel 5 : Dirty = 534, False CCA = 0, Busy Time = 8000, Skip Channel = FALSE [ 4658.708559] Channel 6 : Dirty = 932, False CCA = 0, Busy Time = 11740, Skip Channel = FALSE [ 4658.717027] Channel 7 : Dirty = 432, False CCA = 0, Busy Time = 4503, Skip Channel = FALSE [ 4658.725422] Channel 8 : Dirty = 384, False CCA = 0, Busy Time = 6019, Skip Channel = FALSE [ 4658.733819] Channel 9 : Dirty = 336, False CCA = 0, Busy Time = 2408, Skip Channel = FALSE [ 4658.742215] Channel 10 : Dirty = 272, False CCA = 0, Busy Time = 1652, Skip Channel = FALSE [ 4658.750694] Channel 11 : Dirty = 80, False CCA = 0, Busy Time = 2084, Skip Channel = FALSE [ 4658.759085] ===================================================== [ 4658.765263] Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 11 [ 4658.774092] Min Dirty = 80 [ 4658.776834] ExChannel = 0 , 0 [ 4658.779848] BW = 20 [ 4658.811321] br-wlan: port 1(ra0) entered forwarding state [ 4658.816844] br-wlan: port 1(ra0) entered forwarding state [ 4660.808390] br-wlan: port 1(ra0) entered forwarding state
-
WiFi client broken after update to Ω-ware: 0.1.10 b160
I, like many on this forum, have had terrible trouble getting WiFi working. Latest issue is that'd I've just upgraded to
0.1.10 b160
(over functioning WiFi) usingoupgrade -force
, and now I can't reconnect to the WiFi. I've tried everything I could find from the hundred of threads on WiFi issues, but this is the closest I've come:# wifisetup <Select SSID, authentication type is WPA2PSK, enter password> > Restarting wifimanager for changes to take effect sh: 7fff.40a36bc0d67b: unknown operand # wifisetup info { "success": false } # cat /etc/config/network config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix 'fd1d:48c4:7633::/48' config interface 'wlan' option type 'bridge' option proto 'static' option ipaddr '192.168.3.1' option netmask '255.255.255.0' option ip6assign '60' config interface 'wan' option ifname 'eth0' option proto 'dhcp' config interface 'wwan' option ifname 'apcli0' option proto 'dhcp' option hostname 'Omega-D67B' # cat /etc/config/wireless config wifi-device 'ra0' option type 'ralink' option mode '9' option country 'US' option ht '40' option channel 'auto' option disabled '0' config wifi-iface 'ap' option device 'ra0' option mode 'ap' option network 'wlan' option ifname 'ra0' option encryption 'psk2' option key '12345678' option ssid 'Omega-D67B' option ApCliSsid 'TheSSID' option ApCliPassWord 'ThePassword' option ApCliAuthMode 'WPA2PSK' option ApCliEnable '0' config wifi-config option ssid 'TheSSID' option key 'ThePassword' option encryption 'WPA2PSK'
I suspect there's something misconfigured in
network
orwireless
, but I can't figure out a known good default. I've tried changes toApCliEnable
,hwmode
,htmode
,variant
,device_mode
,op_mode
and so on with no better result. My next step would be a manual reflash... again. Would love to know if there's an easier way. -
RE: Problem with the terminal
Oh dear, sounds broke. Perhaps your storage is full or otherwise stuffed. Do you have anything of value on the Omega? It might be worth doing a factory reset:
-
RE: Unable to configure wifi
Hi Subramanian,
No one can help you unless you explain your problem. Wifi generally works fine, so it must be something specific to your Omega, your Wifi, or the way you're operating it.
Have a read of this: https://opensource.com/life/16/10/how-ask-technical-questions
And try to describe an example that demonstrates the problem, complete with an error messages or undesired output.
Heath
-
RE: Omega2 and cloud and ios browsers
Still a bummer. Just downloaded and tried 3 alternative browsers (Opera, Chrome and Firefox) on iOS, all with the same result. Not many websites that can claim that extent of incompatibility!
The iPad is definitely not my first use-case, but I just wired up my Omega2 to control a mains outlet, and sat on the couch to try out (impress my wife with) wireless lighting control. Bit of a fizzer when not one, but four browsers failed to work!
I eventually resorted to my favourite ssh client on iOS (Termius) and
gpioctl
saved the day, but definitely not the iOS experience I was hoping for! -
RE: GPIO Interrupts Omega2
Looks like this is the most recent thread on GPIO Interrupts. What's the current status on GPIO interrupt support on the Omega2?
In particular:
- what are the typical latencies associated with the sysfs method?
- are there any advantages for the kmod-gpio-irq path?
- if so, is there a reliable way to use kmod-gpio-irq on the Omega2 or is it likely to end in the dead-ends reported in this thread?
Cheers,
Heath