So I was experimenting with my shutdown procedure and power-down and power-off are pretty useless in that regard in so much as they don't poweroff and halt the CPU but instead reboot it.

However, I have discovered if I used Linux's magic sysrq interface to send the 'Power off immediately' command. It does just that. The led goes out and the dock is dead until power is reset.

Test it yourself. Just remember that it is immediate power off so no syncing of any kind will happen. You will have to manually sync and unmount disks yourself.

echo "o" >/proc/sysrq-trigger

Still handy to have at the end of a shutdown script though.

@peter-garner-0

Spam is on the increase via forums world wide it seems. But it is a case of active moderation and proper security practices. Sign ups need to be verified yes, but also activity needs to be monitors. Usually discourse handles it pretty well but in practice it requires a moderator to really fine grain things.

I am guessing the onion boys have too much else to do but looking after a community forum should really be left up to the community. A known good contributor and regular to the forums can be deputised to that end and at least fill in the gaps when the admins are away. Time zones are a pain regardless of the industry you are in so might be good to get multiple candidates from different areas of the world to help out.

Just a thought..

Hey Guys.. Upgraded to :

Ω-ware: 0.0.6 b275

but I am still getting the same errors.

opkg install tinc
Installing tinc (1.0.26-1) to root...
Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/tinc_1.0.26-1_ar71xx.ipk.
Collected errors:

• satisfy_dependencies_for: Cannot satisfy the following dependencies for tinc:
• kernel (= 3.18.20-1-7bed08fa9c06eb8089e82c200340ec66) *
• opkg_install_cmd: Cannot install package tinc.

How close are we to sorting this out?

Thanks.

So I have just received my new Oboo Clock and wondering when we are going to open up a forum to discuss things about it. My main gripe atm is where is the developer access to it. SSH is not enabled by default and not sure what is the correct way to enable it.

Is there and SDK for the cards working with the bluetooth app etc..

Lots of questions come to mind.

Thanks.

Need I say more?

Expired Certificate

Hint: Use Letsencrypt.

@Kit-Bishop

Yeah.. I figured it was being put to the back burner but really this is starting to get very frustrating. Standard packages like tinc are available in OpenWRT and so it really should be relatively trivial to compile against the 'Onion' version of the OpenWRT tree. Hell even just putting that source up as a git hub would be enough for people to be able to build packages against the Onion which fit seamlessly into opkg.

Is there a list of what 'customisations' Onion has done to OpenWRT so maybe we can patch an official build with and build from there?

Been asking this for months now guys. Still cannot install tinc because of a mismatch between the repo modules and the running kernel. I am seriously thinking of compiling it all from scratch but am hoping I won't need to do that. Can we use a working repo from onion so we can build modules against the current kernel.

Feeling forgotten here guys

@Boken-Lin

Yeah I figured as much.. but until then can only play around with the Omega and not do any real work with it Still a good update though and very happy to see such active development. Kudos guys. Doing a great job!

Very nice work! Thank you very much. I am so stupid not realising that you needed a 0 to turn it on. Doh! Cheers!

@Chris-Ouellette

I could do with more documentation as well. I have no idea how to play audio from the command line on the Oboo clock. mpg123 is there and everything but there are no audio devices present. I have a sneaking feeling you need to use the mosquitto framework to use the audio but that is not terrible well documented and so not sure if I can do that from the command line easily.

So any central repository for docs would be helpful and know methods to access functions.

@Chris-Ouellette

I could do with more documentation as well. I have no idea how to play audio from the command line on the Oboo clock. mpg123 is there and everything but there are no audio devices present. I have a sneaking feeling you need to use the mosquitto framework to use the audio but that is not terrible well documented and so not sure if I can do that from the command line easily.

So any central repository for docs would be helpful and know methods to access functions.

@will-jenkins

I am a UK user.. Does the same for me. A royal POA.

I really want some sort of dev guiide to be released because I want to customise or blank the cards when not in use as it just confuses the intended target. Plus I have a script I can use to auto dim the display when Daylight savings cut in.

Can we please have a devoted area to discuss such things ?

So I have just received my new Oboo Clock and wondering when we are going to open up a forum to discuss things about it. My main gripe atm is where is the developer access to it. SSH is not enabled by default and not sure what is the correct way to enable it.

Is there and SDK for the cards working with the bluetooth app etc..

Lots of questions come to mind.

Thanks.

@peter-garner-0

Spam is on the increase via forums world wide it seems. But it is a case of active moderation and proper security practices. Sign ups need to be verified yes, but also activity needs to be monitors. Usually discourse handles it pretty well but in practice it requires a moderator to really fine grain things.

I am guessing the onion boys have too much else to do but looking after a community forum should really be left up to the community. A known good contributor and regular to the forums can be deputised to that end and at least fill in the gaps when the admins are away. Time zones are a pain regardless of the industry you are in so might be good to get multiple candidates from different areas of the world to help out.

Just a thought..

@John_L

I noticed in my one the wifisetup script used uci set wireless.radio0.. when of course the device is actuall ra0 now.

That fixed that problem.. but still cannot get it to connect to any of my wifi AP's,

bizarre.

Ok so I flashed this to my OO2P and as I had nothing to lose also factory reset it with firstboot -y

So I was a little surprised when I say a segfault on restart to do with the SPI driver.

[ 11.542654] spidev spi32766.1: buggy DT: spidev listed directly in DT
[ 11.549271] ------------[ cut here ]------------
[ 11.553970] WARNING: CPU: 0 PID: 486 at drivers/spi/spidev.c:720 0x8768833c()
[ 11.561222] Modules linked in: spidev(+) snd_usbmidi_lib slhc rfcomm nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hidp hid_generic hci_uart crc_ccitt cdc_acm btusb btintel bnep bluetooth snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 videobuf2_vmalloc videobuf2_memops videobuf2_core hid v4l2_common videodev evdev snd_soc_core mt_wifi ralink_gdma virt_dma ledtrig_oneshot ledtrig_morse ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables msdos snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat ntfs configfs autofs4 nls_utf8 nls_iso8859_1 nls_cp437 regmap_i2c dma_shared_buffer ecb cmac mmc_block usb_storage sdhci_pltfm sdhci mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache exfat usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 11.666647] CPU: 0 PID: 486 Comm: kmodloader Not tainted 4.4.74 #0
[ 11.672911] Stack : 80380780 00000000 00000001 803d0000 87dab4d4 803cae63 80361c18 000001e6
[ 11.672911] 80413438 0000000c 0000001a 024000c0 80066378 8004af58 80367120 803c0000
[ 11.672911] 00000003 0000000c 80365524 875a7b4c 80066378 80048ec4 00000000 00000000
[ 11.672911] 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.672911] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.672911] ...
[ 11.709089] Call Trace:
[ 11.711629] [<80066378>] module_sect_show+0x0/0x18
[ 11.716513] [<8004af58>] vprintk_default+0x24/0x30
[ 11.721390] [<80066378>] module_sect_show+0x0/0x18
[ 11.726268] [<80048ec4>] printk+0x2c/0x38
[ 11.730352] [<8002552c>] warn_slowpath_common+0xa0/0xd0
[ 11.735683] [<8014de3c>] dump_stack+0x14/0x28
[ 11.740106] [<80014908>] show_stack+0x50/0x84
[ 11.744524] [<8002552c>] warn_slowpath_common+0xa0/0xd0
[ 11.749843] [<8768833c>] 0x8768833c
[ 11.753403] [<800255e4>] warn_slowpath_null+0x18/0x24
[ 11.758560] [<801fb304>] of_match_node+0x20/0x44
[ 11.763272] [<8768833c>] 0x8768833c
[ 11.766846] [<801c0a10>] devm_kfree+0x20/0x44
[ 11.771285] [<801e1bd8>] spi_drv_probe+0x3c/0x84
[ 11.775994] [<801bd540>] driver_probe_device+0x120/0x288
[ 11.781405] [<8008b928>] kstrdup+0x44/0x8c
[ 11.785589] [<801e1ad8>] spi_match_device+0x38/0xa8
[ 11.790567] [<801bd724>] __driver_attach+0x7c/0xb4
[ 11.795442] [<801bb948>] next_device+0x10/0x30
[ 11.799959] [<801bd6a8>] __driver_attach+0x0/0xb4
[ 11.804746] [<801bba04>] bus_for_each_dev+0x9c/0xac
[ 11.809706] [<80303c9c>] klist_add_tail+0x24/0x50
[ 11.814484] [<801bb7d8>] bus_get+0x2c/0x50
[ 11.818679] [<801bcc38>] bus_add_driver+0xec/0x20c
[ 11.823549] [<800ae92c>] exact_match+0x0/0x8
[ 11.827899] [<800aee34>] exact_lock+0x0/0x24
[ 11.832253] [<801bde3c>] driver_register+0xa8/0xf8
[ 11.837133] [<8775a000>] init_module+0x0/0xdc [spidev]
[ 11.842387] [<8775a098>] init_module+0x98/0xdc [spidev]
[ 11.847711] [<80159a08>] kasprintf+0x1c/0x28
[ 11.852061] [<800458b0>] __wake_up+0x24/0x48
[ 11.856412] [<8775a000>] init_module+0x0/0xdc [spidev]
[ 11.861646] [<8000d938>] do_one_initcall+0x1e8/0x214
[ 11.866709] [<800458b0>] __wake_up+0x24/0x48
[ 11.871046] [<8775a000>] init_module+0x0/0xdc [spidev]
[ 11.876291] [<80034568>] call_usermodehelper_exec+0x144/0x160
[ 11.882138] [<80034058>] call_usermodehelper_setup+0x38/0xa8
[ 11.887922] [<80066378>] module_sect_show+0x0/0x18
[ 11.892805] [<80067598>] do_init_module+0x74/0x1cc
[ 11.897700] [<8009f418>] __vunmap+0xf0/0x114
[ 11.902076] [<80068e2c>] load_module+0x16c0/0x1b68
[ 11.906958] [<80066964>] unknown_module_param_cb+0x0/0xac
[ 11.912443] [<8009f90c>] __vmalloc_node+0x34/0x40
[ 11.917260] [<80069368>] SyS_init_module+0x94/0x180
[ 11.922213] [<80069404>] SyS_init_module+0x130/0x180
[ 11.927293] [<8000682c>] syscall_common+0x30/0x54
[ 11.932077] [<80008c58>] __bzero+0xbc/0x164
[ 11.936331]
[ 11.937846] ---[ end trace d1d675f9648aa3a7 ]---

I was also surprised when the promised better performing 'Warp Core' driver did not seem connect to any of my networks. In fact it kept on saying it connected but there was no internet. A blatant falsehood given that my laptop I was using to login via the Serial console was working fine on the same access points.

Anyway of debugging what is going on? If i cannot connect to wifi then not sure how I will ever fix a problem on it again.

@Fabian-Nydegger-0

Install offical firmware:

the trouble with the official firmware and i have complained about this on numerous occasions is it does not track lede/openwrt properly. So the 2 things I want working on my omega are f2fs and tinc. Both of which cannot because the damn kernel version does not match up with any of the tools or packages.

It is for that reason I am using LEDE directly because it is impossible to use the stock firmware with standard packages.

Hey,

Been a few months since I played with my Omega and maybe I have forgotten something. I flashed the latest LEDE image ( 17.01.4) to the 2+ and it broadcasts fine on radio0 but I cannot recall what device I need to call to make it connect to an AP as well.

On the Onion build it is ra0

config wifi-device 'ra0'
option type 'ralink'
option mode '9'
option channel 'auto'
option txpower '100'
option ht '20'
option country 'US'
option disabled '0'

But there is no ra0 device in LEDE. In fact the only devices I see are these.

cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
eth0.1: 0 0 0 0 0 0 0 0 3240 20 0 0 0 0 0 0
lo: 142072 2184 0 0 0 0 0 0 142072 2184 0 0 0 0 0 0
wlan0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth0: 0 0 0 0 0 0 0 0 321263 953 0 0 0 0 0 0
br-wlan: 0 0 0 0 0 0 0 0 3240 20 0 0 0 0 0 0
eth0.2: 0 0 0 0 0 0 0 0 311766 917 0 0 0 0 0 0

So in theory wlan0 should be the device. but when I set it as that I get.

wifi
wlan0(): Interface type not supported
'radio0' is disabled
wlan0(): Interface type not supported
'radio0' is disabled

The wifi device is definitely found because it can be seen via iw.

iw list
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x1fe
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 4,
total <= 4, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing

So what am I missing here? Do I need to specify the device type to something (ie 'ralink' in the default firmware) in which case what should it be?

Any help appreciated.

Thanks.

@Douglas-Kryder

Why is SPI so broken? I know pulling some pins high will stop the Omega from booting but is it more than that ?

Thanks for the link I'll check it out.

I have been given one of these Waveshare 4.2 Inch e-paper module and wonder if anyone has had any experience at trying to get them to work with an Omega?

It supports a variety of platforms like RPi Arduno and STM32 and uses a SPI interface.

Python and C libs are available for the Pi and are GPL2

Any thoughts ?

Thanks.