4 4
tkaiser

Orange Pi R1

Recommended Posts

3 minutes ago, thanh_tan said:

Can this board be used as wifi marketing device?


Why not. It has onboard WiFi which can be configured as AP. It's not very powerful one and can't handle many clients at once. 

Share this post


Link to post
Share on other sites
4 hours ago, Igor said:


Why not. It has onboard WiFi which can be configured as AP. It's not very powerful one and can't handle many clients at once. 

Do you assume that this board can handle how many client at the same time?

Share this post


Link to post
Share on other sites

spotted the first Orange Pi R1 at eBay (but only 3 x2 in auction).... dont know why so less :(

 

Orange Pi R1 H2 Quad Core Cortex-A7 Open-source 256MB DDR3 GPU/600MHz RJ45 Board
Item numbers:

 

382244596378

 

362116564021

 

311974248848

 

Share this post


Link to post
Share on other sites
On 20.10.2017 at 3:51 PM, DreamDreams said:

I booted my R1 with Orange Pi Zero Ubuntu image. Both ethernet ports work, no wifi though

As expected. To get at least some information inserted into this thread what about posting output from 'armbianmonitor -u'? :)

Share this post


Link to post
Share on other sites

I've not checked recently but if there's still no schematics released on orangepi.org but there are OS images available claiming working Wi-Fi then anyone of you should download such an OS image, see whether Wi-Fi works and if that's the case we need script.bin ('apt install sunxi-tools' then bin2fex is available) and the output of the following uploaded to an online pasteboard service:

lsmod
dmesg
iwconfig

It's only about the mmc1/wlan nodes in sys_config.fex (script.bin). As soon as they're known and adapted loading the 8189es driver should work (I guess you already tried out a 'modprobe 8189es' already?)

 

Edit: Hmm... I checked for this with an old OS image from Xunlong already half a year ago: 

 

So does 'modprobe 8189es' work or not? In case someone tried out please output of 'iwconfig' afterwards and armbianmonitor -u again.

 

Share this post


Link to post
Share on other sites
On 21/10/2017 at 8:49 AM, tkaiser said:

I've not checked recently but if there's still no schematics released on orangepi.org but there are OS images available claiming working Wi-Fi then anyone of you should download such an OS image, see whether Wi-Fi works and if that's the case we need script.bin ('apt install sunxi-tools' then bin2fex is available) and the output of the following uploaded to an online pasteboard service:


lsmod
dmesg
iwconfig

It's only about the mmc1/wlan nodes in sys_config.fex (script.bin). As soon as they're known and adaptec loading the 8189es driver should work (I guess you already tried out a 'modprobe 8189es' already?)

 

Edit: Hmm... I checked for this with an old OS image from Xunlong already half a year ago: 

 

So does 'modprobe 8189es' work or not? In case someone tried out please output of 'iwconfig' afterwards and armbianmonitor -u again.

 

7

root@orangepizero:~# modprobe 8189es
modprobe: FATAL: Module 8189es not found in directory /lib/modules/4.13.8-sunxi

 

EDIT: there is an 8189fs but no 8189es module

 

root@orangepizero:~# iwconfig
enxc0742bfffc8c  no wireless extensions.

eth0      no wireless extensions.

lo        no wireless extensions.

 

http://sprunge.us/ARKT

 

There is an official OS image that has a working wifi:

https://mega.nz/#F!VG4l1aTL!JNWI52f-5NT0pyijQ-50Lw!VHpGHLbY

 

Share this post


Link to post
Share on other sites
10 minutes ago, the-ice said:

modprobe: FATAL: Module 8189es not found in directory /lib/modules/4.13.8-sunxi

Boring. Why not using an Armbian image where 8189es is known to work (legacy)?

10 minutes ago, the-ice said:

There is an official OS image that has a working wifi:

https://mega.nz/#F!VG4l1aTL!JNWI52f-5NT0pyijQ-50Lw!VHpGHLbY

So someone can boot this image on the device, extract contents of script.bin and upload that and output from dmesg, lsmod and iwconfig to an online pasteboard service.

Share this post


Link to post
Share on other sites
47 minutes ago, tkaiser said:

Boring. Why not using an Armbian image where 8189es is known to work (legacy)?

 

Tried, no wifi.

 

48 minutes ago, tkaiser said:

So someone can boot this image on the device, extract contents of script.bin and upload that and output from dmesg, lsmod and iwconfig to an online pasteboard service.

 

Will do

 

Share this post


Link to post
Share on other sites
2 hours ago, the-ice said:

Tried, no wifi

 

I forgot to mention that of course contents of /etc/modules have to be adjusted prior to such tests (at least removing the xradio occurences there).

Share this post


Link to post
Share on other sites

Xradio is turned OFF in the kernel. Got the same issue
 

root@orangepizero:~# modprobe 8189es
modprobe: FATAL: Module 8189es not found in directory /lib/modules/4.13.9-sunxi

Will check if it is available in the kernel config...

Share this post


Link to post
Share on other sites
On 22.10.2017 at 2:00 PM, tkaiser said:

I forgot to mention that of course contents of /etc/modules have to be adjusted prior to such tests (at least removing the xradio occurences there).

 

@tkaiser @the-ice @Ivan Voronov because my OrangePi R1 did arrive today I did download today

the legacy xenial ubuntu and did a apt update/upgrade and cleared the 2 xradio entrys in /etc/modules:
 

root@orangepirone:/etc# more modules
#w1-sunxi
#w1-gpio
#w1-therm
#sunxi-cir
g_serial

Also deleted the entry for xradio in /etc/modprobe.d/ = xradio_wlan.conf

 

After a reboot the mod 8189es is loaded automatically (the OPi R1 did this already before) :
 

root@orangepirone:~# lsmod
Module                  Size  Used by
8189es               1076034  0
pcf8591                 3363  0
bmp085                  3487  0
cdc_ether               3679  0
usbnet                 14096  1 cdc_ether
g_serial               27617  2
btrfs                 712409  0

but no WiFi :(
A short Google-search did tell me that : RTL8189ftv is corresponding to 8189fs.ko, while RTL8189etv isc orresponding to 8189es.ko
(in https://de.scribd.com/document/356867489/OrangePi-Win-win-Plus-A64-User-Manual-v0-9-1 )

 

So the 8189es is WRONG for the RTL8189ftv on the OPi R1 Mainboard.

A short test of "modprobe 8189fs":
 

root@orangepirone:~# lsmod
Module                  Size  Used by
8189fs               1050451  0
8189es               1076034  0
pcf8591                 3363  0
bmp085                  3487  0
cdc_ether               3679  0
usbnet                 14096  1 cdc_ether
g_serial               27617  2
btrfs                 712409  0

8189fs loaded successfully - AND some time before I did configure via nmtui  a WiFi-Connection I did get instantly my wlan0 with the configured address in ifconfig :)
 

root@orangepirone:~# ifconfig
enxc0742bffe8ff Link encap:Ethernet  HWaddr c0:74:2b:ff:e8:ff
          inet addr:192.168.6.151  Bcast:192.168.6.255  Mask:255.255.255.0
          inet6 addr: fe80::c274:2bff:feff:e8ff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1301 errors:0 dropped:0 overruns:0 frame:0
          TX packets:854 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:118959 (118.9 KB)  TX bytes:133607 (133.6 KB)

eth0      Link encap:Ethernet  HWaddr e2:fc:56:2f:d5:dc
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:510 (510.0 B)
          Interrupt:114

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6030 (6.0 KB)  TX bytes:6030 (6.0 KB)

wlan0     Link encap:Ethernet  HWaddr 08:ea:40:7c:02:ad
          inet addr:192.168.6.101  Bcast:192.168.6.101  Mask:255.255.255.255
          inet6 addr: fe80::aea:40ff:fe7c:2ad/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:654 errors:0 dropped:2 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:107527 (107.5 KB)  TX bytes:2689 (2.6 KB)
          
root@orangepirone:~# iwconfig
lo        no wireless extensions.

enxc0742bffe8ff  no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"My_SSID"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.462 GHz  Access Point: C0:25:E9:44:71:68
          Bit Rate:72.2 Mb/s   Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=71/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

but now I did try to unload 8189es via

modprobe -r 8189es

 

Did work, BUT then wlan0 disappears :(
In this moment it looks like to me that 8189fs.ko will only work if 8189es.ko is loaded (which armbian did automatically).

After reloading 8189es with

modprobe 8189es

wlan0 re-appears and is visible in ifconfig

 

For Information about this installation: 

root@orangepirone:~# armbianmonitor -u
/var/log/armhwinfo.log has been uploaded to http://sprunge.us/QLbe

and a dmesg as attachment :)
 

dmesg_OPi_R1.txt

Share this post


Link to post
Share on other sites

After successfully having wlan0 in legacy kernel (with using 8189es and 8189fs) I did take a look at 

Armbian_5.34.171104_Orangepizero_Ubuntu_xenial_next_4.13.11

 

This 4.13.11 hasnt loaded xradio and did modprobe 8189fs fine: 

root@orangepizero:/rtl8189ES_linux# lsmod
Module                  Size  Used by
8189fs                802816  0

but there is no 8189es. So I couldnt test if the combination of 8189es and 8189fs does work for the next kernel and wlan0.

 

So I did take a look at @y52s thread

and did try to compile the module 8189es on the next kernel:

armbian-config -> install kernel headers
exit

root@orangepizero:~# cd /usr/src/linux-headers-4.13.11-sunxi
root@orangepizero:/usr/src/linux-headers-4.13.11-sunxi# make scripts
 CHK     scripts/mod/devicetable-offsets.h

root@orangepizero:/usr/src/linux-headers-4.13.11-sunxi# cd /
root@orangepizero:~# git clone https://github.com/jwrdegoede/rtl8189ES_linux

root@orangepizero:/usr/src/linux-headers-4.13.11-sunxi# cd /rtl8189ES_linux/

root@orangepizero:/rtl8189ES_linux# make ARCH=arm CROSS_COMPILE= -C /usr/src/linux-headers-4.13.11-sunxi M=/rtl8189ES_linux
make: Entering directory '/usr/src/linux-headers-4.13.11-sunxi'
  Building modules, stage 2.
  MODPOST 0 modules
make: Leaving directory '/usr/src/linux-headers-4.13.11-sunxi'

But there is no module generated/compiled :(
Iam wondering about only ONE line after the "make script" in the linux-header directory because at the other thread there was many more line output:
 

root@orangepiplus:/usr/src/linux-headers-3.4.110-sun8i# make scripts
  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTLD  scripts/mod/modpost
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/conmakehash

 

The next-kernel seems to produce less heat than the legacy kernel :)

As information:
root@orangepizero:/rtl8189ES_linux# armbianmonitor -u
/var/log/armhwinfo.log has been uploaded to http://sprunge.us/LQbY
 

 

Share this post


Link to post
Share on other sites
14 hours ago, guidol said:

So the 8189es is WRONG for the RTL8189ftv on the OPi R1 Mainboard

 

Can you try the following please on the image with legacy kernel and report back:

echo 'blacklist 8189es' >/etc/modprobe.d/blacklist-8189es.conf
update-initramfs -u
reboot

 

Share this post


Link to post
Share on other sites
18 minutes ago, tkaiser said:

 

Can you try the following please on the image with legacy kernel and report back:


echo 'blacklist 8189es' >/etc/modprobe.d/blacklist-8189es.conf
update-initramfs -u
reboot

 

The same as I did wrote yesterday... OK when blacklisted the module 8189es wouldnt be loaded, but after a

modprobe 8189fs only the module is loaded and I couldnt see wlan0 with ifconfig:
 

root@orangepirone:~# lsmod
Module                  Size  Used by
8189fs               1050451  0
pcf8591                 3363  0
bmp085                  3487  0
cdc_ether               3679  0
usbnet                 14096  1 cdc_ether
g_serial               27617  2
btrfs                 712409  0

when loading 8189es "in top of 8189fs" I could see my wlan0 - so neither in legacy nor in next kernel 8189fs as a single module does enable wlan0:

root@orangepirone:~# modprobe 8189es

root@orangepirone:~# lsmod
Module                  Size  Used by
8189es               1076034  0
8189fs               1050451  0
pcf8591                 3363  0
bmp085                  3487  0
cdc_ether               3679  0
usbnet                 14096  1 cdc_ether
g_serial               27617  2
btrfs                 712409  0

root@orangepirone:~# iwconfig
lo        no wireless extensions.

enxc0742bffe8ff  no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"MySSID"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.462 GHz  Access Point: C0:25:E9:44:71:68
          Bit Rate:72.2 Mb/s   Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=97/100  Signal level=71/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

 

Share this post


Link to post
Share on other sites
6 hours ago, guidol said:

root@orangepirone:~# modprobe 8189es

 

Ok, let's stop (I neither understand what you're doing now either on an 'orangepione' or using the image for this board nor do I understand why you claim 8189es is wrong and still try to load the module).

 

None of us devs has this board yet (Xunlong for whatever reasons never sent out the promised dev samples), there are no schematics that match reality released, I assumed it would be 8189ETV based on pictures of the board, you're the first user having the hardware in his hands pointing out that it's 8189FTV in reality (true?).

 

Edit: Realized that it reads 'orangepirone' and not 'orangepione' -- though still a waste of time...

Share this post


Link to post
Share on other sites
1 hour ago, tkaiser said:

 

Ok, let's stop (I neither understand what you're doing now either on an 'orangepione' or using the image for this board nor do I understand why you claim 8189es is wrong and still try to load the module).

... pointing out that it's 8189FTV in reality (true?).

 

 

OK - I did think its a 8189FTV because when I used my magnifying glass I only could read 8189FTV (not seeing the bottom line of the E) AND

on the Orange Pi R1 product page they also wrote 8189FTV ( Onboard WIFI Realtek RTL8189FTV, IEEE 802.11 b/g/n):
http://www.orangepi.org/OrangePiR1/

and as third I could get a wlan0 with ifconfig.

 

So while thinking its a 8189FTV I did read the following in a Orange Pi Handbook:
 

RTL8189ftv is corresponding to 8189fs.ko, while RTL8189etv isc orresponding to 8189es.ko

And after having module 8189es (loaded by armbian boot) I did load 8192fs and did (now I know its wrong - but surprisingly it worked) gives me a working wlan0

 

This in mind I did try this in the next kernel....but there is no 8189es.ko - and 8189fs did modprobe without errors.

 

So now the only idea I got is the difference between USB and SDIO compiled Realtek Drivers ( http://linux-sunxi.org/Wifi#Realtek )

OPi_R1_lower.jpg

OPi_R1_upper.jpg

OPi_R1_WLAN_Chip.jpg

Share this post


Link to post
Share on other sites
6 minutes ago, guidol said:

And after having module 8189es (loaded by armbian boot)

Well, thanks for confirming that it is an 8189ETV. Then we have the following 'issues':

In other words: As already explained in this thread it's absolutely useless to try out this board with mainline kernel yet (since driver not ready) and there might be different settings needed to correctly get the Wi-Fi module running.

 

So we know we have no schematics that correctly describe the hardware, we know that Xunlong's own OS image correctly enables Wi-Fi, I asked several times in the meantime for a few bits of information (the f*cking fex file, lsmod and dmesg output!) and what happens instead? Not the needed information is provided but people only try what can't work as already explained. Please also note that all three links above are from this very same thread here. It's frustrating.

Share this post


Link to post
Share on other sites
2 hours ago, tkaiser said:

 

Can you try the following please on the image with legacy kernel and report back:


echo 'blacklist 8189es' >/etc/modprobe.d/blacklist-8189es.conf
update-initramfs -u
reboot

 

Strange - the whole time I had to load 8189fs additionally to 8189es for wlan0 in legacy....but now i reverted the change above (because we have a 8189ETV Chip) and now after a reboot legacy shows me wlan0 without the 8189fs

 

root@orangepirone:~# dmesg|grep -i wifi
[    1.670725] [rf_pm]: set losc_out 32k out[wifi_pm]: set wl_reg_on 1 !
[    1.771327] [wifi_pm]: get wifi_sdc_id failed
[    1.871370] [wifi_pm]: wifi gpio init is OK !!
[   11.955034] [wifi_pm]: set wl_reg_on 1 !

 

Share this post


Link to post
Share on other sites
37 minutes ago, tkaiser said:

 

So we know we have no schematics that correctly describe the hardware, we know that Xunlong's own OS image correctly enables Wi-Fi, I asked several times in the meantime for a few bits of information (the f*cking fex file, lsmod and dmesg output!) and what happens instead? Not the needed information is provided but people only try what can't work as already explained. Please also note that all three links above are from this very same thread here. It's frustrating.

 

@tkaiser Dont be frustrated -  now that I got my R1 here is fex-file, lsmod, iwconfig and dmesg from their image for the R1: ubuntu_server_xenial_H2_R1_V0.1.img

ubuntu_server_xenial_H2_R1_V0.1.img:
Linux OrangePizero 3.4.39 #2 SMP PREEMPT Fri Apr 14 14:05:55 CST 2017 armv7l armv7l armv7l GNU/Linux
(running hot like the armbian legacy)

root@OrangePizero:~# iwconfig
gre0      no wireless extensions.

lo        no wireless extensions.

tunl0     no wireless extensions.

wlan1     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth1      no wireless extensions.

wlan5     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

sit0      no wireless extensions.

eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

root@OrangePizero:~# lsmod
Module                  Size  Used by
r8152                  49914  0
cdc_ether               3187  0
usbnet                 14152  1 cdc_ether
sunxi_ir_rx             9150  0
gpio_sunxi              8265  0
8189es                996645  0

root@OrangePizero:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 76:92:b2:d9:2d:6d
          inet6 addr: fe80::7492:b2ff:fed9:2d6d/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:510 (510.0 B)
          Interrupt:114

eth1      Link encap:Ethernet  HWaddr c0:74:2b:ff:e8:ff
          inet addr:192.168.6.153  Bcast:192.168.6.255  Mask:255.255.255.0
          inet6 addr: fe80::c274:2bff:feff:e8ff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1253 errors:0 dropped:0 overruns:0 frame:0
          TX packets:994 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:122366 (122.3 KB)  TX bytes:133846 (133.8 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:142 errors:0 dropped:0 overruns:0 frame:0
          TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11895 (11.8 KB)  TX bytes:11895 (11.8 KB)

wlan1     Link encap:Ethernet  HWaddr 0e:ea:40:7c:02:ad
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan5     Link encap:Ethernet  HWaddr 08:ea:40:7c:02:ad
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@OrangePizero:~# find / -name script.bin
/media/boot/script.bin

root@OrangePizero:/media/boot# ls
boot.scr  script.bin  System Volume Information  uImage

root@OrangePizero:/boot# ls
boot0_OPI.fex             script.bin.OPI-PC_1080p50    script.bin.OPI-PLUS_1080p60  uImage
script.bin.OPI-2_1080p50  script.bin.OPI-PC_1080p60    script.bin.OPI-PLUS_720p50   uImage_OPI-2
script.bin.OPI-2_1080p60  script.bin.OPI-PC_720p50     script.bin.OPI-PLUS_720p60   uImage_OPI-2_NO_BUDGET_COOLING
script.bin.OPI-2_720p50   script.bin.OPI-PC_720p60     u-boot_OPI-emmc.fex          uImage_OPI-PLUS
script.bin.OPI-2_720p60   script.bin.OPI-PLUS_1080p50  u-boot_OPI.fex               uImage_OPI-PLUS_NO_BUDGET_COOLING

 

dmesg_Opi_R1.txt

script.bin

script.fex

Share this post


Link to post
Share on other sites
51 minutes ago, guidol said:

ubuntu_server_xenial_H2_R1_V0.1.img

Here's http://kaiser-edv.de/tmp/NumpU8/Armbian_5.34_Orangepi-r1_Ubuntu_xenial_default_3.4.113.img.xz based on the fex contents from there (MD5 sum: 566d614f3bc7a0dd27e2bd848be6f5ee)

 

Please connect a single Ethernet cable to one of the two ports, boot it, login through network or serial console, if the image asks for a reboot (likely due to rootfs resize), then reboot and finally provide output from 'armbianmonitor -u' and iwconfig.

 

Please note that /etc/network/interfaces is empty on this image so you either configure everything with nmtui (recommended) or fiddle around filling this file. But at least I would be interested in results from using nmtui only, configuring both eth interfaces with static or dynamic settings and also activate Wi-Fi (if possible). Then of course 'armbianmonitor -u' and iwconfig again :)

Share this post


Link to post
Share on other sites
1 hour ago, tkaiser said:

tkaiser OPi R1 Image:
Linux orangepi 3.4.113-sun8i #13 SMP PREEMPT Sat Nov 4 07:45:43 PDT 2017 armv7l armv7l armv7l GNU/Linux

 

After resize-boot armbianmonitor/iwconfig:

root@orangepi:~# armbianmonitor -u
/var/log/armhwinfo.log has been uploaded to http://sprunge.us/EVRd

root@orangepi:~# iwconfig
lo        no wireless extensions.

enxc0742bffe8ff  no wireless extensions.

wlan0     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

after configuring the interfaces via nmtui - without problems:

root@orangepi:~# armbianmonitor -u
/var/log/armhwinfo.log has been uploaded to http://sprunge.us/HOVb

root@orangepi:~# iwconfig
lo        no wireless extensions.

enxc0742bffe8ff  no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"MySSID"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.462 GHz  Access Point: C0:25:E9:44:71:68
          Bit Rate:72.2 Mb/s   Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=70/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

root@orangepi:~# ifconfig
enxc0742bffe8ff Link encap:Ethernet  HWaddr c0:74:2b:ff:e8:ff
          inet addr:192.168.6.154  Bcast:192.168.6.255  Mask:255.255.255.0
          inet6 addr: fe80::c274:2bff:feff:e8ff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10302 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1086 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1316838 (1.3 MB)  TX bytes:349868 (349.8 KB)

eth0      Link encap:Ethernet  HWaddr e2:fc:56:2f:d5:dc
          inet addr:192.168.6.101  Bcast:192.168.6.101  Mask:255.255.255.255
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:238 (238.0 B)
          Interrupt:114

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:388 errors:0 dropped:0 overruns:0 frame:0
          TX packets:388 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:95697 (95.6 KB)  TX bytes:95697 (95.6 KB)

wlan0     Link encap:Ethernet  HWaddr 08:ea:40:7c:02:ad
          inet addr:192.168.6.152  Bcast:192.168.6.255  Mask:255.255.255.0
          inet6 addr: fe80::aea:40ff:fe7c:2ad/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8559 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1553591 (1.5 MB)  TX bytes:3347 (3.3 KB)
          
root@orangepi:~# lsmod
Module                  Size  Used by
8189es               1075930  0
zram                    8964  4
pcf8591                 3363  0
bmp085                  3487  0
cdc_ether               3679  0
usbnet                 14096  1 cdc_ether
g_serial               28549  0
btrfs                 712409  0

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
4 4