Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

888 profile views
  1. @Atharmian, no worries. Thanks for suggesting to look at Omega2. Debian/Armbian is a much better fit for my purpose than OpenWRT though. @Igor, it seems you missed that "If I should not use an OPI0 for my purpose, what device should I use that can run stable?" is a rhetorical question. I for one don't believe the OPI0 can't be used for anything requiring stability but will stand corrected if being told so by the people who actually have in-depth knowledge of this SBC and the OS (drivers). If it is true that Armbian-on-OPI0 is a total waste of time from all perspectives, as tkaiser seems to suggest, then that might be true for any of the other boards supported by Armbian too, right? Or would you suggest I buy one of each, try to get Armbian running on it, ask a question here if something fails, possibly get abused verbally for asking and then .... eh, leave? And please, if you can, stay friendly and amicable. @zador.blood.stained, thanks for answering and suggesting to have a look at the NanoPi Air. Are you saying I can expect stability from the OPI0 running Armbian, except for the wireless? Some here (tkaiser for example) seem to suggest that I can't really expect anything with a price tag of <$10 to work at all and that I'm actually rather stupid thinking I could! I am well aware that Armbian is a non-commercial open source project, hence my thoughts to give something back (in this case $$) in appreciation for the work done. I must say though that being the recipient of abusive language (not from you) simply for asking a few questions after reading through the many posts (granted: not all) on this subject is quite effective as a disincentive.
  2. Hi everyone, The topic I submitted my first two messages to on this forum is now locked and I've been referred to this thread so the below might appear to be a bit out of context. I was asked a question by hmartin: "Xunlong never advertised the Orange Pi Zero as an AP! Please, show me where they said "use the Orange Pi Zero as a WiFi router". The advertisement can be found here: http://www.orangepi.org/orangepizero, look for "What can I do with Orange Pi Zero". One of the bullet points is "wireless server". I think an AP qualifies as a "wireless server". As to "Why the hell do people buy an SBC if they want an AP instead? Is it really saving the few bucks? Why are people that weird and believe in advertising and then add also (wrong) assumptions to that ("if there's Wi-Fi I expect it to be performant and stable, it has to be useable as access point and of course with monitor mode too")?" by tkaiser, in my case I'm prototyping a solar controller. The OPI0 - if it's possible to get it to work stable - would be an absolute perfect fit. One of it's many functions would be to allow someone to connect to it wirelessly and see a few webpages with some graphs. I don't need any serious throughput, I'd be very happy with "crappy 2.4GHz single antenna" wifi performing at a few Mbps covering a short range (say 10 meters) only - if it's stable. Besides it's really simple to replace the antenna with something with a bit more gain but that's besides the point here. I'm not using it as a wireless AP in the traditional sense, that was just an initial test. I guess one could say I picked the right test as it provided the answer I'm seeking. Apologies for not detailing in many words (as I've done now in this post) how I was intending to use the OPI0 as an AP: not to stream Youtube but to serve a few simple webpages to a few wireless connected clients. Before I however embark on picking the OPI0 (and ordering a box full of them), I need to find out if it actually works. Having paid <$10, I kept in mind that it indeed might not work. There are plenty alternatives. It'd however be great if the board I end up with can run my favorite OS (full fledged Debian) and use Python. Since this is a non-commercial open source project, it would be great if costs can be kept down too. Heck I even almost made a donation to Armbian in appreciation for all the work the people involved with this project have put into it making it work with the OPI0. I'm glad I didn't (yet). I'm reading a very clear message (please correct me if I'm wrong) here. Apparently, the OPI0 is too cheap to be useable for any purpose (not even a paper weight ;-) ). If that is the case, I don't understand why people are even bothering supporting Armbian on a device like the OPI0. Why would you if you can't really use it for anything requiring stability? Which brings up the following question. If I should not use an OPI0 for my purpose, what device should I use that can run stable? Clearly I can't trust advertising ;-). Anything costing more than $XX (please define XX)? Any (none?) of the other devices supported by Armbian? Or if anyone got the OPI0 to work with "crappy wireless performance" but stable nevertheless, then I'd be very happy to hear from you. I know, I should not expect that much... As to calling people weird and/or whining, I'd like to extend the invitation to keep an open mind to use cases that you might not have thought of before you do so as a matter of keeping conversations pleasant and civilised. best regards
  3. Hi everyone, To all people saying that we can't expect much from a <$10 board. It may be true that the board is cheap, however I think it's reasonable to expect that it works as advertised (which includes using it as an AP). I don't think anyone would accept flipping 0.000001% of the bits in memory, not even for a cheap board ;-) Thanks to the Armbian folks, we have a great OS that we can use on this board. I'm working on a solar controller hopefully based on the OPI0. It has everything I need - except reliable wireless as it stands now.
  4. Hi everyone, First of all I'd like to express my appreciation for the folks working on Armbian. I recently discovered the OPI0 and see many applications that could use an inexpensive yet full fledged embedded linux system. I'm not too concerned about the wireless throughput of the OPI0 but I do need stability, which I have not been able to achieve so far. I'm using the OPI0 as an AP with it's wireless interface bridged to the LAN interface. DHCP, DNS, gateway etc all provided for by another node on the network. A wireless device associates successfully, get's a bit of network access but as soon as I play a Youtube video it all starts failing. Here are some parts of dmesg and syslog although I guess most of you have already seen the message related to XRADIO (I've removed the bits that are likely not relevant). Has anyone been able to get the wireless to work reliably? [ 6.601429] [XRADIO] Driver Label:L34M.01.08.0002 Nov 14 2016 08:41:12 [ 6.601543] [XRADIO] Allocated hw_priv @ d5bf1240 [ 6.602314] [sBUS] XRadio Device:sdio clk=50000000 [ 6.602643] xradio wlan power on [ 6.754844] [XRADIO] Detect SDIO card 1 [ 7.101435] [XRADIO_ERR] xradio_load_firmware: can't read config register, err=-110. [ 7.101473] [XRADIO_ERR] xradio_load_firmware failed(-110). [ 7.437706] xradio wlan power off [ 7.437753] gpio wl_reg_on set val 0, act val 0 [ 7.487840] [XRADIO] Remove SDIO card 1 [ 7.488148] mmc1: card 0001 removed [ 7.488590] [mmc]: sdc1 power_supply is null [ 7.500494] systemd[1]: Started Journal Service. [ 7.540998] [XRADIO_ERR] xradio_host_dbg_init failed=2599 [ 7.541040] [XRADIO] Driver Label:L34M.01.08.0002 Nov 14 2016 08:41:12 [ 7.541148] [XRADIO] Allocated hw_priv @ d5bf1240 [ 7.541741] xradio wlan power on [ 7.541774] gpio wl_reg_on set val 1, act val 1 [ 7.591834] gpio wl_reg_on set val 0, act val 0 [ 7.593888] gpio wl_reg_on set val 1, act val 1 [ 7.694070] [XRADIO] Detect SDIO card 1 [ 7.695583] [mmc]: sdc1 power_supply is null [ 7.749447] mmc1: new high speed SDIO card at address 0001 [ 7.750272] [sBUS] XRadio Device:sdio clk=50000000 [ 7.751341] [XRADIO] XRADIO_HW_REV 1.0 detected. [ 7.947908] [XRADIO] Bootloader complete [ 8.185099] [XRADIO] Firmware completed. [ 8.187818] [WSM] Firmware Label:XR_C01.08.0043 Jun 6 2016 20:41:04 [ 8.196411] [XRADIO] Firmware Startup Done. [ 8.198911] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 8.313819] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x48) [ 8.315067] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x48, dev addr: 0x48) [ 8.318255] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x77) [ 8.318316] bmp085: probe of 0-0077 failed with error -70 [ 8.966173] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 9.344995] Adding 131068k swap on /var/swap. Priority:-1 extents:1 across:131068k SS [ 10.927838] systemd-journald[173]: Received request to flush runtime journal from PID 1 [ 11.372011] Bridge firewalling registered [ 14.440409] PHY: gmac0-0:00 - Link is Up - 100/Full [ 14.441407] br0: port 1(eth0) entered forwarding state [ 77.913076] device wlan0 entered promiscuous mode [ 77.913240] br0: port 2(wlan0) entered forwarding state [ 78.040468] [AP_WRN] ap restarting! [ 78.092772] [AP_WRN] vif0, AP/GO mode THROTTLE=35 [ 92.960132] br0: port 2(wlan0) entered forwarding state root@opi55:/lib/firmware/xr819# tail -f /var/log/syslog Feb 1 18:18:14 localhost systemd[1]: Started Session 3 of user root. Feb 1 18:18:18 localhost kernel: [ 92.960132] br0: port 2(wlan0) entered forwarding state Feb 1 18:21:06 localhost kernel: [ 261.050133] [AP_WRN] Multicast delivery timeout. ...snap... Feb 1 18:21:39 localhost kernel: [ 293.860293] [WSM_ERR] wsm_flush_tx:No pengding, but hw_bufs_used=1 ...snap... Feb 1 18:21:59 localhost kernel: [ 314.740116] [AP_WRN] Multicast delivery timeout. Feb 1 18:22:30 localhost kernel: [ 345.220307] [bH_WRN] miss interrupt! Feb 1 18:22:42 localhost kernel: [ 357.570241] [AP_WRN] Multicast delivery timeout. Feb 1 18:23:35 localhost kernel: [ 409.991567] [WSM_WRN] Too many attempts to requeue a frame. Frame is dropped, fctl=0x4208. Feb 1 18:23:35 localhost kernel: [ 410.350102] [AP_WRN] Multicast delivery timeout. Feb 1 18:23:41 localhost kernel: [ 415.997716] [WSM_WRN] Too many attempts to requeue a frame. Frame is dropped, fctl=0x4208. Feb 1 18:24:56 localhost kernel: [ 491.690269] [bH_WRN] miss interrupt! Feb 1 18:24:57 localhost kernel: [ 491.850202] [AP_WRN] Multicast delivery timeout. Feb 1 18:25:12 localhost kernel: [ 507.073815] [WSM_WRN] Too many attempts to requeue a frame. Frame is dropped, fctl=0x4208. Feb 1 18:25:38 localhost kernel: [ 533.210214] [AP_WRN] Multicast delivery timeout. Feb 1 18:25:54 localhost kernel: [ 549.137943] [WSM_ERR] wsm_flush_tx:No pengding, but hw_bufs_used=1 Feb 1 18:26:14 localhost kernel: [ 569.650088] [AP_WRN] Multicast delivery timeout. Feb 1 18:26:15 localhost kernel: [ 570.162082] [WSM_WRN] Too many attempts to requeue a frame. Frame is dropped, fctl=0x4208. Feb 1 18:26:23 localhost kernel: [ 578.290174] [AP_WRN] Multicast delivery timeout. ^C root@opi55:/lib/firmware/xr819# ls -al total 144 drwxr-xr-x 2 root root 4096 Nov 14 21:14 . drwxr-xr-x 12 root root 4096 Nov 14 21:14 .. -rw-r--r-- 1 root root 2308 Nov 11 00:14 boot_xr819.bin -rw-r--r-- 1 root root 975 Nov 11 00:14 device-xradio.mk -rw-r--r-- 1 root root 126416 Nov 11 00:14 fw_xr819.bin -rw-r--r-- 1 root root 744 Nov 11 00:14 sdd_xr819.bin root@opi55:/lib/firmware/xr819# uname -a Linux opi55 3.4.113-sun8i #50 SMP PREEMPT Mon Nov 14 08:41:55 CET 2016 armv7l GNU/Linux [ENDS]
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines