1 1
kaytros

Orange Pi Plus Images Request

Recommended Posts

Dear Users,

 

I bought a new 'Orange Pi Plus' board to learning pi. But i can not install  it by stable image.

 

 

I treid a lot of image what i found.

(Debian,ubuntu etc) 

 

I want a image  with ( Gpio driver and ir driver and desktop gui) not more.

 

Please help me. 

 
i can buy it.  
Thanks best regards.
 
Murat.

 

 

Share this post


Link to post
Share on other sites

Dear sir i did what you said. 

I instaled orange plus with   tursty image.  then  updated and alsu upgrate it. also install gpio driver  by modprobe . 

I noticed  the the image does not aprove ( security wifi network  -wpa/wpa2/web etc) it connects  wifi network   without security only. I received 'bad password'

Share this post


Link to post
Share on other sites

I noticed  the the image does not aprove ( security wifi network  -wpa/wpa2/web etc) it connects  wifi network   without security only. I received 'bad password'

 

I think no one has touched the wireless driver yet. At least you can try to compile some alternatives out of the box.

Share this post


Link to post
Share on other sites

Hi

I use

Armbian_5.05_Orangepiplus_Debian_jessie_3.4.110_desktop.zip

Same problem here it see my access point and others OK with SSID but 'bad password'

when I try to connect.

Also it seems something is wrong if I type set in a console.

lots of stuff there :-)

Share this post


Link to post
Share on other sites

Same problem here it see my access point and others OK with SSID but 'bad password'

 

Please read again what Igor wrote: "I think no one has touched the wireless driver yet." and think about the contents of the H3 Mini FAQ: "Known to NOT work (reliably) yet: onboard Wi-Fi (it works somehow but chip/driver are cheap and bad -- we can't do much to improve the situation)"

 

So what do you expect? You should keep in mind that most of the Armbian devs do not even tried this crappy onboard Wi-Fi out so things won't improve unless someone experienced, interested in slow onboard WiFi and skilled enough to fix things starts to work on it and contributes his work back.

 

And what do you expect as an answer or reaction to "Also it seems something is wrong if I type set in a console."?

Share this post


Link to post
Share on other sites

Hi i am a user of a OrangePiPlus2 too. I tried different images, but iam a beginner. i had different problems with monitor size or a notworking wlan but I used the onboard wlan (sdio: rtl8189etv) on the ubuntu vivid mate image from loboris without problems. (Kernel 3.4.39-01-lobo, MATE 1.8.2)

if i can help to fix the problem with armbian please ask. what kind of parameters do you need?

 

ludwich

Share this post


Link to post
Share on other sites

notworking wlan but I used the onboard wlan (sdio: rtl8189etv) on the ubuntu vivid mate image from loboris without problems. (Kernel 3.4.39-01-lobo, MATE 1.8.2)

if i can help to fix the problem with armbian please ask. what kind of parameters do you need?

 

No idea. At least I will not spend a second on these problems since the onboard WiFi of all the Oranges sucks anyway, I don't have one and I would never buy an SBC with crappy ultra slow WiFi. We're also aware that the WiFi GUI sucks and are open for suggestions to replace it. But no idea if anybody will look into. I believe the only Armbian dev owning such a device is Igor. And I would suspect priorities too look into are very low (reasons already pointed out above).

 

But you could help others that might try to address these problems by describing what's different with loboris' image regarding WiFi.

Share this post


Link to post
Share on other sites

And what do you expect as an answer or reaction to "Also it seems something is wrong if I type set in a console."?

Hi. Thanks for your reply.

Well I'm not a Linux expert but I always used the "set" command to see the state of various variables.

May be I'm wrong as "man set " gives no answer.

Anyway it always worked for me.

Except with this distribution .

As for the wlan interface my message was just a confirmation to kaytros 's one.

I use Ethernet and the only use I have of WIFI is as an access point but I didn't try it yet with that distribution.

Share this post


Link to post
Share on other sites

Well I'm not a Linux expert but I always used the "set" command to see the state of various variables.

May be I'm wrong as "man set " gives no answer.

 

So what's the problem now? You said there's something wrong with 'set' and now it's the missing manual page for set (which is quite normal since set is a so called 'shell builtin' for which no separate manual pages are available). If you feel it's about reporting errors to enable us to fix them it's necessary to be a bit more precise. Otherwise this is just a waste of time for everyone...

 

So in case 'man set' produces no output (this is what you said in your 2nd post) then this strange since it should produce an error message 'no manual page for set available'. In case 'something is wrong if I type set in a console' it would be helpful if you elaborate a bit on what you expect and what do you get instead ('something's wrong' is not that precise ;) )

Share this post


Link to post
Share on other sites

If I didn't gave more details it is because:

"set > dumpfile"

results in a more than 100KB dumpfile that I didn't analyse

It just seemed strange to me and as a result set in a console

is useless.

Share this post


Link to post
Share on other sites

If I didn't gave more details it is because:

"set > dumpfile"

results in a more than 100KB dumpfile that I didn't analyse

 

There's still nothing to analyse, you should just start to understand what you're doing. Again: set is a 'shell builtin' and not an own command (compare with 'type $command' in this case 'type set') therefore you might find an explanation in bash's manual page (if you spend a few days reading through ;) )

 

The behaviour of set depends on whether bash is in POSIX mode or not. Number 39 here: http://www.gnu.org/software/bash/manual/html_node/Bash-POSIX-Mode.html

 

That's all, you compare jessie defaults with other defaults. That might be different but is not a bug :)

 

Consider adding 'set -o posix' to the appropriate bash startup files so that you get the bevaviour back you're used to. Or think about switching to a shell that is more user friendly (eg. zsh).

 

Final note: Since we're in some sort of beta test with Armbian for Orange Pis it might be better to ask why something's different than to post 'something seems wrong'. That might help both you and us :)

Share this post


Link to post
Share on other sites

Just got my Orange Pi Plus 2 and was under the impression from this thread that I shouldn't expect the internal WiFi to work with Armbian. While building/installing drivers for my 300Mbps WiFi dongle, I was shocked to see WiFi working *without* my dongle plugged in. At first, I thought the drivers activated the internal WiFi (8192eu vs 8192etv), but starting with a fresh image of Armbian (Jessie server), I realized that the internal WiFi worked all along.

 

This should let you set the SSID and Password

sudo apt-get install -y network-manager
sudo /usr/bin/nmtui-connect

It looks like I can push ~40Mbps through the internal WiFi, while my "300Mbps" WiFi dongle manages ~75Mbps. The internal giga ethernet gets ~775Mbps.

Share this post


Link to post
Share on other sites

At first, I thought the drivers activated the internal WiFi (8192eu vs 8192etv)

 

According to both linux-sunxi wiki and product page the Orange Pi Plus 2 uses RTL8189ETV. Can you please elaborate a bit which hardware is really used (and also output of 'sudo lshw -C network' would be nice)

Share this post


Link to post
Share on other sites

Sorry, my bad, I misread the linux-sunxi page.. according to lshw, it is rt8189es (or at least the driver)

root@orangepiplus2:~#  lshw -C network
  *-network:0
       description: Wireless interface
       physical id: 8
       logical name: wlan1
       serial: da:47:10:fe:e2:ae
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8189es driverversion=3.4.110-sun8i firmware=N/A link=no multicast=yes wireless=unassociated
  *-network:1
       description: Wireless interface
       physical id: 9
       logical name: wlan0
       serial: d8:47:10:fe:e2:ae
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8189es driverversion=3.4.110-sun8i firmware=N/A ip=192.168.1.28 link=yes multicast=yes wireless=IEEE 802.11bgn
  *-network:2 DISABLED
       description: Ethernet interface
       physical id: a
       logical name: eth0
       serial: e6:15:2b:93:4a:64
       capabilities: ethernet physical
       configuration: broadcast=yes ip=192.168.1.42 multicast=yes

It does have a weird quirk in that two wireless interfaces show up (wlan0 and wlan1) with different HWaddr, but seem to refer to same device. Also, ssh through the internal wireless seems to pause for a second every so often so maybe not everything is working perfectly.

Share this post


Link to post
Share on other sites

Thx for confirmation. I wouldn't count on the currently available driver at all. If Hans' modifications also work with 3.4.x then it might be worth a look whether the driver can be backported (volunteers needed), otherwise I would simply ignore the onboard Wifi of all currently available Orange Pi.

 

Xunlong realised in the meantime that it's better to replace the WiFi with the next models: http://www.orangepi.org/orangepibbsen/forum.php?mod=redirect&goto=findpost&ptid=1300&pid=11081

 

BTW: Regarding mainline kernel things are really progressing nicely, see eg. https://groups.google.com/d/msg/linux-sunxi/EIeU32D5kpM/gPvPUwgwAwAJ

Share this post


Link to post
Share on other sites
Here my HW-List output, Device: OrangePiPlus2, Realtek 8189ETV SDIO Chip
It works with the Loboris Debian Mate Image
 
I see there is a other driverversion #17
 
root@OrangePI:~# lshw -C network
  *-network:0             
       Beschreibung: Kabellose Verbindung
       Physische ID: 6
       Logischer Name: wlan1
       Seriennummer: 5a:63:56:cc:c1:e8
       Fähigkeiten: ethernet physical wireless
       Konfiguration: broadcast=yes driver=rtl8189es driverversion=3.4.39-01-lobo firmware=N/A ip=192.168.178.44 link=yes multicast=yes wireless=IEEE 802.11bgn
  *-network:1
       Beschreibung: Ethernet interface
       Physische ID: 7
       Logischer Name: eth0
       Seriennummer: d2:d8:4b:1a:f7:7a
       Größe: 10Mbit/s
       Kapazität: 1Gbit/s
       Fähigkeiten: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       Konfiguration: autonegotiation=on broadcast=yes driver=sunxi_geth driverversion=SUNXI Gbgit driver V1.1 duplex=half link=no multicast=yes port=MII speed=10Mbit/s
 
Please ask if i can help :-) ludwich

Share this post


Link to post
Share on other sites

I see there is a other driverversion

 

That's just the kernel version. I don't have any device with this WiFi chip and I don't plan to use one ever (living in a crowded area 802.11n @ 2.4GHz is pretty useless) so anyone interested in potential differences... here are the starting points:

 

Loboris:

https://github.com/loboris/OrangePI-Kernel/tree/master/linux-3.4/drivers/net/wireless/rtl8189es

 

The kernel we use (+ a few thousand patches on top ;) ):

https://github.com/O-Computers/linux-sunxi/tree/h3-wip/drivers/net/wireless/rtl8189es

 

include/config/rtl8189es.h is identical but maybe sources are different or in his image(s) something else is tweaked regarding WiFi.

 

EDIT: Seems there are differences or at least different offsets without meaning (won't spend further time looking into it):

 

 

diff -r drivers/net/wireless/rtl8189es/8189es.mod.c /../../Armbian/sources/linux-sun8i/h3-wip/drivers/net/wireless/rtl8189es/8189es.mod.c
22,25c22,25
< 	{ 0x4d2e22d8, "module_layout" },
< 	{ 0x516c2af4, "register_netdevice" },
< 	{ 0x8168ea38, "sdio_writeb" },
< 	{ 0xa5e42fb2, "sdio_readb" },
---
> 	{ 0x83e82633, "module_layout" },
> 	{ 0x83046f80, "register_netdevice" },
> 	{ 0xd197626, "sdio_writeb" },
> 	{ 0xb8ba1756, "sdio_readb" },
27c27
< 	{ 0x364e72aa, "neigh_lookup" },
---
> 	{ 0xec8da8bf, "neigh_lookup" },
30,31c30,31
< 	{ 0xa0db100e, "complete_and_exit" },
< 	{ 0xb5e6be8e, "wiphy_free" },
---
> 	{ 0xd4fab16, "complete_and_exit" },
> 	{ 0x868ef5af, "wiphy_free" },
33c33,34
< 	{ 0xbedb42b9, "cfg80211_unlink_bss" },
---
> 	{ 0x795645b0, "cfg80211_unlink_bss" },
> 	{ 0x311b7963, "_raw_spin_unlock" },
36c37
< 	{ 0x6d08af6a, "single_open" },
---
> 	{ 0xd3ba6b6, "single_open" },
41c42
< 	{ 0xc683e282, "dev_set_drvdata" },
---
> 	{ 0xdb3902b, "dev_set_drvdata" },
44,45c45,46
< 	{ 0x2925d108, "single_release" },
< 	{ 0xf1f61c8a, "find_vpid" },
---
> 	{ 0xd60bbc7, "single_release" },
> 	{ 0x895736a1, "find_vpid" },
47,54c48,55
< 	{ 0x44c5c97, "cfg80211_inform_bss_frame" },
< 	{ 0xadae3641, "sdio_enable_func" },
< 	{ 0x5b95a539, "arp_tbl" },
< 	{ 0xebc4ffa1, "sdio_claim_irq" },
< 	{ 0xa775c082, "sock_release" },
< 	{ 0x44b1ee96, "netif_carrier_on" },
< 	{ 0x3b502f70, "_raw_spin_lock_bh" },
< 	{ 0x982ef621, "skb_clone" },
---
> 	{ 0x81b28ddc, "cfg80211_inform_bss_frame" },
> 	{ 0xa654a19, "sdio_enable_func" },
> 	{ 0xa9767929, "arp_tbl" },
> 	{ 0x323d23c8, "sdio_claim_irq" },
> 	{ 0x2b198dd3, "sock_release" },
> 	{ 0x40b3546e, "netif_carrier_on" },
> 	{ 0x8bd94317, "_raw_spin_lock_bh" },
> 	{ 0x4114396a, "skb_clone" },
57c58
< 	{ 0xb889e748, "skb_copy" },
---
> 	{ 0xc0826e50, "skb_copy" },
59c60
< 	{ 0xa389c945, "down_interruptible" },
---
> 	{ 0x38f42821, "down_interruptible" },
61,62c62,63
< 	{ 0x87ec9512, "sock_recvmsg" },
< 	{ 0xd67319, "seq_printf" },
---
> 	{ 0xa5041e46, "sock_recvmsg" },
> 	{ 0x8d676f78, "seq_printf" },
64c65
< 	{ 0xe7935b9, "netif_carrier_off" },
---
> 	{ 0x17d80b74, "netif_carrier_off" },
66,68c67,69
< 	{ 0x577d4dbd, "remove_proc_entry" },
< 	{ 0xc0166260, "cfg80211_rx_mgmt" },
< 	{ 0x683dc04a, "filp_close" },
---
> 	{ 0x29e2c71b, "remove_proc_entry" },
> 	{ 0xdcf5f5e4, "cfg80211_rx_mgmt" },
> 	{ 0xbcc75ae3, "filp_close" },
72c73
< 	{ 0xe860eb4a, "mutex_unlock" },
---
> 	{ 0x8d9ec35d, "mutex_unlock" },
75,76c76,77
< 	{ 0x5976185a, "neigh_destroy" },
< 	{ 0xe6d8a04c, "cfg80211_del_sta" },
---
> 	{ 0x93f661e, "neigh_destroy" },
> 	{ 0xd6ae18b1, "cfg80211_del_sta" },
78,79c79,80
< 	{ 0xa6126a16, "seq_read" },
< 	{ 0xa685d240, "kthread_create_on_node" },
---
> 	{ 0x45ece345, "seq_read" },
> 	{ 0x52ff650e, "kthread_create_on_node" },
81c82
< 	{ 0xf5096cac, "sdio_get_host_pm_caps" },
---
> 	{ 0xabccc9df, "sdio_get_host_pm_caps" },
84,86c85,87
< 	{ 0x317ebdb1, "cfg80211_mgmt_tx_status" },
< 	{ 0x6e4f032c, "netif_rx" },
< 	{ 0xa7ecf324, "__init_waitqueue_head" },
---
> 	{ 0x6db15bd3, "cfg80211_mgmt_tx_status" },
> 	{ 0xd53d8e44, "netif_rx" },
> 	{ 0x4467122a, "__init_waitqueue_head" },
89,90c90,91
< 	{ 0xb6e24399, "vfs_read" },
< 	{ 0x617f0481, "sdio_writel" },
---
> 	{ 0xdd68c38a, "vfs_read" },
> 	{ 0x81530d85, "sdio_writel" },
94,95c95,96
< 	{ 0x25ba811a, "proc_mkdir" },
< 	{ 0xf57cde66, "__ieee80211_get_channel" },
---
> 	{ 0x5c6531f7, "proc_mkdir" },
> 	{ 0x1c9d37ae, "__ieee80211_get_channel" },
97,98c98,99
< 	{ 0x8ddab831, "_raw_spin_unlock_irqrestore" },
< 	{ 0x99ef6fb1, "cfg80211_get_bss" },
---
> 	{ 0x74c97f9c, "_raw_spin_unlock_irqrestore" },
> 	{ 0x777648f3, "cfg80211_get_bss" },
100,101c101,102
< 	{ 0xe0e2c2aa, "mutex_lock_interruptible" },
< 	{ 0xa7aed735, "__mutex_init" },
---
> 	{ 0xe09bbdb2, "mutex_lock_interruptible" },
> 	{ 0x2ca4c5c1, "__mutex_init" },
105,107c106,108
< 	{ 0x9a272f07, "sock_sendmsg" },
< 	{ 0xa7c665a1, "free_netdev" },
< 	{ 0x645db27d, "wiphy_unregister" },
---
> 	{ 0x4ff89f2, "sock_sendmsg" },
> 	{ 0xeca9d84f, "free_netdev" },
> 	{ 0x7093e288, "wiphy_unregister" },
110,111c111,112
< 	{ 0x65935db9, "register_netdev" },
< 	{ 0x2b78e030, "sdio_readl" },
---
> 	{ 0x251aedfe, "register_netdev" },
> 	{ 0xefb05e2e, "sdio_readl" },
114,118c115,119
< 	{ 0x54454935, "skb_push" },
< 	{ 0xdcc163f4, "cfg80211_connect_result" },
< 	{ 0x32a11b08, "cfg80211_michael_mic_failure" },
< 	{ 0xc096e1ee, "wiphy_apply_custom_regulatory" },
< 	{ 0x636a79a2, "dev_get_by_index" },
---
> 	{ 0x93b75a6b, "skb_push" },
> 	{ 0x8289efd0, "cfg80211_connect_result" },
> 	{ 0x88e4ae06, "cfg80211_michael_mic_failure" },
> 	{ 0x7230e29b, "wiphy_apply_custom_regulatory" },
> 	{ 0x2aea4a15, "dev_get_by_index" },
121c122
< 	{ 0x3d6fa2dc, "kill_pid" },
---
> 	{ 0xf18a745c, "kill_pid" },
124,126c125,127
< 	{ 0x6f0d0433, "skb_pull" },
< 	{ 0x31fc18a8, "cfg80211_ibss_joined" },
< 	{ 0x217d3ab3, "init_net" },
---
> 	{ 0xe5cffb5b, "skb_pull" },
> 	{ 0x291b1183, "cfg80211_ibss_joined" },
> 	{ 0x96751483, "init_net" },
128c129
< 	{ 0x8ab63809, "dev_kfree_skb_any" },
---
> 	{ 0xd1458cb0, "dev_kfree_skb_any" },
132,136c133,137
< 	{ 0x7fa4ddee, "flush_signals" },
< 	{ 0x80217ac2, "sdio_unregister_driver" },
< 	{ 0x9b19a744, "sdio_f0_writeb" },
< 	{ 0xcfae46eb, "sdio_set_host_pm_flags" },
< 	{ 0x48f245f8, "netif_device_attach" },
---
> 	{ 0x2c087bf2, "flush_signals" },
> 	{ 0x87016992, "sdio_unregister_driver" },
> 	{ 0x7f3be7a4, "sdio_f0_writeb" },
> 	{ 0x3e14ff5c, "sdio_set_host_pm_flags" },
> 	{ 0x83f21b2f, "netif_device_attach" },
138c139
< 	{ 0xcfef38b, "cfg80211_roamed" },
---
> 	{ 0x99a31a6b, "cfg80211_roamed" },
140,142c141,143
< 	{ 0x6d0c07f4, "__alloc_skb" },
< 	{ 0x307eb9c7, "wiphy_new" },
< 	{ 0x3ecdc8e, "wiphy_register" },
---
> 	{ 0x467e3e19, "__alloc_skb" },
> 	{ 0x3e6c46, "wiphy_new" },
> 	{ 0x800c4fed, "wiphy_register" },
145,146c146,147
< 	{ 0xc73dd955, "_raw_spin_unlock_bh" },
< 	{ 0x5d131bc7, "sdio_release_irq" },
---
> 	{ 0xb368ec89, "_raw_spin_unlock_bh" },
> 	{ 0x5f53fa4c, "sdio_release_irq" },
149c150
< 	{ 0x68b2efd4, "cfg80211_ready_on_channel" },
---
> 	{ 0xd2c58e8e, "cfg80211_ready_on_channel" },
151,155c152,156
< 	{ 0x23456443, "eth_type_trans" },
< 	{ 0x27e93d91, "sdio_f0_readb" },
< 	{ 0x83c43ad, "wake_up_process" },
< 	{ 0xb655ba51, "cfg80211_disconnected" },
< 	{ 0xc4097c34, "_raw_spin_lock" },
---
> 	{ 0x5a17701b, "eth_type_trans" },
> 	{ 0xa75993ef, "sdio_f0_readb" },
> 	{ 0xe2451cd9, "wake_up_process" },
> 	{ 0x15a2b1c7, "cfg80211_disconnected" },
> 	{ 0xc2161e33, "_raw_spin_lock" },
157,159c158,160
< 	{ 0x1a9b678e, "_raw_spin_lock_irqsave" },
< 	{ 0x879de1fa, "unregister_netdevice_queue" },
< 	{ 0xda0dddd3, "cfg80211_new_sta" },
---
> 	{ 0xbd7083bc, "_raw_spin_lock_irqsave" },
> 	{ 0xb36e7a45, "unregister_netdevice_queue" },
> 	{ 0x1c9535e5, "cfg80211_new_sta" },
161,164c162,165
< 	{ 0x8162fa1, "sdio_memcpy_toio" },
< 	{ 0x11153cbb, "proc_create_data" },
< 	{ 0xede62530, "sdio_writew" },
< 	{ 0x9f22605a, "seq_lseek" },
---
> 	{ 0x82f6f88d, "sdio_memcpy_toio" },
> 	{ 0x10747048, "proc_create_data" },
> 	{ 0x673fa641, "sdio_writew" },
> 	{ 0x32b5f952, "seq_lseek" },
168c169
< 	{ 0x186b9c84, "dev_alloc_name" },
---
> 	{ 0xbfec8a35, "dev_alloc_name" },
170,174c171,175
< 	{ 0x867383da, "sock_create" },
< 	{ 0xa72dab62, "up" },
< 	{ 0x439d12ed, "skb_dequeue" },
< 	{ 0xf053db3f, "cfg80211_remain_on_channel_expired" },
< 	{ 0xf3787ccd, "unregister_netdev" },
---
> 	{ 0xcad86d3a, "sock_create" },
> 	{ 0x2eb22412, "up" },
> 	{ 0xaf088504, "skb_dequeue" },
> 	{ 0x5338d101, "cfg80211_remain_on_channel_expired" },
> 	{ 0xe3f91cc4, "unregister_netdev" },
177c178
< 	{ 0xad998077, "complete" },
---
> 	{ 0x4f7f2d1b, "complete" },
179c180
< 	{ 0x5b5e2508, "__netif_schedule" },
---
> 	{ 0x329e48fb, "__netif_schedule" },
181,184c182,185
< 	{ 0xfa8e345a, "sdio_readw" },
< 	{ 0x12fb791c, "sdio_register_driver" },
< 	{ 0x23128005, "sdio_memcpy_fromio" },
< 	{ 0x8b85d477, "sdio_claim_host" },
---
> 	{ 0x1b588509, "sdio_readw" },
> 	{ 0xb9cbf904, "sdio_register_driver" },
> 	{ 0xbc4c5f3e, "sdio_memcpy_fromio" },
> 	{ 0xea7935a2, "sdio_claim_host" },
186c187
< 	{ 0x8adb83ee, "cfg80211_scan_done" },
---
> 	{ 0xfe57149a, "cfg80211_scan_done" },
188,189c189,190
< 	{ 0x2ba4051d, "skb_put" },
< 	{ 0x9b5fd507, "wait_for_completion_timeout" },
---
> 	{ 0x64a72e0f, "skb_put" },
> 	{ 0x48d316aa, "wait_for_completion_timeout" },
191,193c192,194
< 	{ 0x347e470, "skb_copy_bits" },
< 	{ 0xd03cdbcf, "dev_get_drvdata" },
< 	{ 0x73494eed, "sdio_set_block_size" },
---
> 	{ 0x604f1e24, "skb_copy_bits" },
> 	{ 0x66f8672c, "dev_get_drvdata" },
> 	{ 0x41af52f4, "sdio_set_block_size" },
196c197
< 	{ 0x9d1ad43c, "sdio_disable_func" },
---
> 	{ 0xf49b98b5, "sdio_disable_func" },
198c199
< 	{ 0x11103100, "sdio_release_host" },
---
> 	{ 0x1109b8c4, "sdio_release_host" },
200,201c201,202
< 	{ 0x455a9de6, "filp_open" },
< 	{ 0xe9db75a8, "alloc_etherdev_mqs" },
---
> 	{ 0x11d091e1, "filp_open" },
> 	{ 0x995d64ec, "alloc_etherdev_mqs" }, 

 

 

Share this post


Link to post
Share on other sites

Thx for confirmation. I wouldn't count on the currently available driver at all. If Hans' modifications also work with 3.4.x then it might be worth a look whether the driver can be backported (volunteers needed), otherwise I would simply ignore the onboard Wifi of all currently available Orange Pi.

 

Xunlong realised in the meantime that it's better to replace the WiFi with the next models: http://www.orangepi.org/orangepibbsen/forum.php?mod=redirect&goto=findpost&ptid=1300&pid=11081

 

BTW: Regarding mainline kernel things are really progressing nicely, see eg. https://groups.google.com/d/msg/linux-sunxi/EIeU32D5kpM/gPvPUwgwAwAJ

 

I'm not sure the effort for a backport is warranted.. the performance of the onboard WiFi is anemic compared to a cheap USB 300N wifi dongle. I would rather see all effort made towards mainline kernel. It does look like they are really progressing well on it. 

 

An upgraded Orange Pi PC with onboard Flash would be nice--even if you want to boot from MicroSD, the onboard flash should make for (hopefully) faster scratch storage. If they even manage to put a decent OS pre-installed on there, it should greatly help adoption or Orange Pi.

 

However, I really, really wish they would drop the onboard WiFi.. if I need WiFi, I would rather get a better WiFi dongle (300N or AC600) than what I know they will include. 

Share this post


Link to post
Share on other sites

the performance of the onboard WiFi is anemic compared to a cheap USB 300N wifi dongle.

 

Of course. Some of these crappy onboard WiFi 'solutions' do even lead to stability problems (see Lamobo R1). And the very same vendor (SinoVoip or 'Team BPi' how they call themselves) now has a board in stock with non-functional WiFi where you have to desolder a resistor to be able to use WiFi reliably: http://linux-sunxi.org/Banana_Pi_M3#Wi-Fi (but users don't care and buy this crap because of onboard WiFi and the slowest USB-to-SATA bridge in the world)

 

Users don't care. The WiFi was already there when they bought their board, it's obviously crap but they want to use it anyway even if they have to place their board 2m next to the router.

 

An Orange Pi PC Plus with eMMC and WiFi is announced for $5-$6 more. The problem with onboard eMMC and an additional SD card on Allwinner boards is that the SD card will normally preferred when available at boot by the SoC. But the best location for the rootfs (and user homedirs when a desktop image is used) is the eMMC since random I/O is often magnitudes faster. But this would require bootloader on SD card and rootfs on eMMC which is already possible with Armbian after some tweaking but might become a future installation option.

Share this post


Link to post
Share on other sites

Hi

I think users mainly want to use the on-board WIFI to save a USB port.

Even if the range is limited this is not a too bad idea.

Sharing USB ports with a hub can also lead to problems.

But in that scope I think the on board WIFI should be compatible with

blue tooth and access point use .

This don't seems to be the case on the Orange.

Same goes for the SATA port it seems an additional USB port would be

more useful for most users.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
1 1