damies

I have a 1/2 dozen Orange Pi Lite's and have encountered the same issue as vasten, the only problem with this is that the MAC address is not fixed so if you upgrade with a newer image the mac address changes, so does the cpu serial number, in fact I haven't found any identifying number that remains the same on these devices (any suggestions?), which is a real pain cause I set my image to auto configure the host name based on the cpu serial number and then labeled them all and after an upgrade to the os they all changed names. Hopefully the physical mac is constant and this works? unfortunately it doesn't help me cause the Orange Pi Lite has no ethernet.

Hi All, I seem to be encountering an issue with setting the MTU for the 8189fs driver on the 4.10.0-sun8i kernel I am trying to set the MTU for wlan0 to 1532. Note this works on the 3.4.113-sun8i kernel without issue. #uname -a Linux orangepipcplus-02c0008115dff7be 4.10.0-sun8i #10 SMP Sun Feb 12 16:51:59 AEST 2017 armv7l armv7l armv7l GNU/Linux /etc/network/interfaces ---------------------------------------------------------------------------------------------------------------------------------- auto wlan0 iface wlan0 inet6 manual wireless-channel 1 wireless-essid batnet6 wireless-mode ad-hoc wireless-ap 02:13:13:13:13:13 mtu 1532 ---------------------------------------------------------------------------------------------------------------------------------- # ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 00:e0:4c:67:db:86 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:12285 errors:0 dropped:3 overruns:0 frame:0 TX packets:673 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1693434 (1.6 MB) TX bytes:63171 (63.1 KB) # ifconfig wlan0 mtu 1532 SIOCSIFMTU: Invalid argument # /bin/ip link set mtu 1532 dev wlan0 RTNETLINK answers: Invalid argument # ifup wlan0 sysctl: setting key "net.ipv6.conf.wlan0.mtu": Invalid argument I did a bit of searching and found http://www.microhowto.info/howto/change_the_mtu_of_a_network_interface.html#idp42736 If this was a hardware restriction It wouldn't work on the 3.4.113-sun8i kernel, so this leads me to think its the driver on the 4.10.0-sun8i kernel. Is anyone here familiar with the code of this driver and able to confirm for me if this is a known issue? Thanks, Dave.

@abramq Sorry I don't know the answer, but maybe I can help..... the Orange Pi Lite's (and the Orange Pi Pc Plus's, but these are the only 2 models I have, so maybe other models too) both load a module 8189fs, Combined with this (https://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/), I believe this is the Realtek 8189fs chipset. When I quickly googled for "Realtek 8189fs wifi direct" I didn't find anything that confirms either way, but did find support for wifi direct with the Realtek 8188 and Realtek 8192 chipsets, so there is some hope that it might be possible. Hopefully this is helpful and steers you in the right direction. Dave.

I've never seen cpu temp below 48ºC when idle but my ambient room temp is never much below 25 (and thats with Aircon), I also don't use heatsinks. Can I ask what you ambient room temp was (roughly) and if you used a heatsink. Dave.

Hi Joao, 1) I have never tried playing games on an Orange Pi, but the CPU should be fast enough for most android games. Some of the Orange Pi's can run Android (i'm not sure about all? not really my area of interest). I would suggest you get one of the Orange Pi models with H3 processor and 1G ram and existing images for Android and Desktop Linux, you can see here for the android images (http://www.orangepi.org/downloadresources/) and here for a linux Desktop image (http://armbian.com/download/) The best bet for you to start out would be to use 2 SD cards, one for the Linux Desktop, one for Android. Use the Android for you games, then switch card when you want to play with linux. 2) Installing software on Linux is easier than Windows, about the same as Android or IOS, On the Armbian linux desktop use the Synaptic Package Manager (it's already installed, more info here: http://www.nongnu.org/synaptic/action.html) 3) The Android version on the Orange Pi is Android, so no. The following is the same for the Orange Pi as for any other Android box that you would plug into a TV: If you are expecting a tablet / phone like experience, you will need a touch screen (I have no experience with this) but from what I understand a touch screen with HDMI and USB would be what you want. I would suggest you try just plugging in the Orange PI to your TV with a USB keyboard and mouse first try it out and see how you go. You may also want to try with a USB game pad, but again I have not tried that either. Well, Hope I've helped.... Good luck, Dave.

Hi @destinqo, You didn't say which OS you are using, since your here on this forum, i'll assume its either debian or ubuntu? Did you define your interfaces in /etc/network/interfaces? if so, under the section iface eth0.10 try adding a line post-up tcpdump -c 10 -i eth0.10 Hope that works for you. Dave.

@jernej - Thanks for the heads up. I don't have any Arduino equipment either, and just a couple of months back we chucked all the old Nokia stuff (when the wife went on a cleaning spree) looks like connecting to another OPi is my best bet, i'll have to find some suitable cables. Thanks @zador this is a big help. Dave.

Hi zador, Thanks, unfortunately I don't have one of those I do have one of these: Will this work If I wire up a serial cable something like this?: Given it takes months for anything to be delivered here, when I order on line (the curse of living outside a major city), and there are no local suppliers, so I can't exactly go racing down to the local shop. If I can make up a cable this way I could be up and running much quicker.

In this tread: http://forum.armbian.com/index.php/topic/2125-armbian-for-orange-pi-does-not-boot/?hl=u-boot It appears that Hugo has used /dev/ttyUSB0 on a linux machine to connect to his Orange Pi+. Is this something unique to the Orange Pi+? when I connect a usb cable to the otg port of my OPi Lite I don't see the u-boot screen, also I can't see it when I connect to a TV with the HDMI. Knowing how to get to see the u-boot screen could help me understand better the issue I' having above. Dave.

Hi All, I'll start with I know this is a dev image...... but I would like to see the 4.x kernels working on the Orange Pi Lite, so would like to be able to find out why it's not and help get that resolved in any way I can. I have 2 images, both were built using the compile.sh: Armbian_5.20_Orangepilite_Ubuntu_xenial_3.4.112.img Armbian_5.21_Orangepilite_Ubuntu_xenial_4.7.6.img I dd'd the 3.4.112 kernel image onto a Micro SD, put it in to my Orange Pi Lite and booted it up and confirmed it was working as expected, the green light flashed, the red one also flashed on first boot, then after the reboot I logged in, changed password etc. I then powered off the Orange Pi Lite, removed the Micro SD card and dd'd the 4.7.6 image, then repeated the process, however this time no green light on the Orange Pi Lite even after waiting over 10 min and pressing the power button a few times. To rule out hardware, I have in both cases used exactly the same hardware (Same Micro SD card, same power supply, same cable, same Orange Pi Lite). After this failed boot, i removed the SD card and mounted on a linux machine to try and figure out what happened, I looked in: $ cat microsd/var/log/dmesg (Nothing has been logged yet.) I looked in a few other files but don't know what I am looking for. I am not that familiar with the boot process of the H3 boards, but I'm guessing by the content of dmesg and the lack of a green light that the kernel never booted? I was also not able to connect via the OTG port. Any suggestions on what I should look at next? I also tried Armbian_5.17_Orangepilite_Ubuntu_xenial_4.7.2.raw a while back and had the same result, but gave up there at that time. Dave.

Ok, now I understand. It works by default as I wanted not as I expected. I was planning to use a battery big enough to power it for 24-48 hours without the solar panel and the location gets 10 hours of sunlight in mid winter so it would take several dark days in a row for this condition to occur, so unlikely but not impossible, maybe a couple of times a decade. I just want to make the system as robust as possible. Thanks everyone for the answers here. Dave.

Actually I don't really care, in my case I just want it to power on and boot up the os after the power is restored regardless of the reason for the power loss. I am planning to embed these boards in a solar powered device, so if the battery goes flat I don't want to be visiting the devices to press the button just to get the OS back up. So I gather I need to change something in /etc/udev/rules.d/72-power-button.rules ? or should that be /etc/udev/rules.d/71-axp-power-button.rules ? Is there some documentation for this file somewhere? Dave.

Hi All, Sorry if this has been asked before, I haven't been able to find the answer yet. I wish to configure my OrangePi's (Lite and PC+) such that they power on automatically whenever the power is restored after a power outage without needing to press the power button. I'm not sure where we could configure this as the OrangePi's don't seem to have a bios like a Desktop PC. Dave.

Thanks, This answered my question.

Hi, I am running a self built image, it's basically the standard Armbian_5.17_Orangepilite_Ubuntu_xenial_3.4.112 with a few extra debs and some pre-configured conf files in /etc. I must be missing something but I cant see how/where you get the power consumption from the output of h3consumption -p? So as I have a few boards up and running with this build, here goes, in all cases below I have ssh'd into the board, run sudo reboot, then after the reboot I have ssh'd back into the board and run sudo h3consumption -p. Also in all cases the boards have no heatsinks and are running inside the plastic cases supplied by xunlong. Hope this helps, Dave.