Search the Community

Hi All, I'm new here, well been lurking a while reading heaps, just not posting before now. My Orange Pi's arrived a few days ago so I have been playing, I have Ubuntu_xenial_3.4.112 image on both types and am able to connect to home wifi and do apt-get update/upgrade so all good here. One thing I wanted to do is use batman-adv, but the kernel module seems to have been disabled on the armbian images: @orangepipcplus:~# cat /boot/config-3.4.112-sun8i |grep BATMAN # CONFIG_BATMAN_ADV is not set It took me a while to figure out how to confirm this was the case but another post pointed me to the /boot/config-3.4.112-sun8i file. So this is where I need some pointers on how to move forward. I'm guessing it's not as simple as un-commenting CONFIG_BATMAN_ADV and adding =y I'm also guessing that at least the kernel module will need to be compiled and maybe the whole kernel? I have never done this so don't really know what to do, but I am willing to learn if someone can give a a pointer or two. My understanding from what I have read is this module should already be in the kernel sources so hopefully this won't be too difficult. I am also open to changing to a different build if necessary/easier to get batman-adv working. FYI my hardware is: - Orange Pi PC+ - Orange Pi Lite Dave.

Hi all. I recently bought an Orange Pi Lite. After trying to get the power switch to work as a power switch (by this I mean booting the board when it was previously shutdown), and after searching for a while, it seems that the power switch in the Orange Pi Lite is not a real one, but it's instead connected to a GPIO. Do you guys know of any Orange Pi board that implements a proper power switch? Thanks.

Hello everybody, I have recently bought an Orange Pi Lite. First, I have downloaded an image with Ubuntu Mate, but it finally decided to take the Armbian one which seems more precise and well prepared. First of all, great thanks for the work already done. I have encountered 2 problems during my installation: Everything was preestablished for US, and it is sometimes boring or difficult to use it. I have some problems with the display. Note that I have taken the Xenial image, and I expect it is the Linux 4 version on which we cannot run Xorg. I start with the easier one: Internationalisation (and I have not written internationalization to remind US people that even English language may change from one country to another). We will have to interact with the machine.The keyboard needs to be configured directly at first boot. The password 1234 selected for root is perfect, but it is really difficult to remember the US keyboard configuration. Even h3disp is difficult, because the m key is located on US keyboard where the question mark is located on mine. Please, run dpkg-reconfigure at first boot, because we can use it with <Enter>,<Tab> and <Space>. Also, I think a good idea to start dpkg-reconfigure tzdata. The second one is a problem. After having searched, I guess the answer is located in the fex file but I cannot find the script.bin file (on some topic, suposed to be in a separate partition) and I do not dare to change it directly without help. Display problem.Symptom: On my screen, I loose 4 characters on the left of the line, and one line at the bottom of the display. In other words, when "4 updates are available. Run apt-get upgrade." is written, I cannot see "4 up". And when I enter a command, I cannot see the text. More detailed symptom:I have two displays: My TV (LG 42LG5500, HD capable), and a standard display (LG W2252V, RVB/DVI @ 1680 x 1050 + HDMI @ 1080i/p @ 50/60 Hz). I have two HDMI cables: The first one is an old Meliconi cable, and the second one is bought on AliExpress (Premium V1.4 HDMI Male to Male HD Cable High Speed Gold Plated). On the TV: I can use a lot of HDMI modes (selected with h3disp), but I loose characters. I have to zoom on the TV with the ratio button, and I take something perfect with 1080p when requesting the "Select original signal" to drive the zoom. On the display: The second cable does not work, in any mode, while it was working on the TV. On the display, with the Meliconi cable, various modes a working properly except that I loose characters and I have no way to adjust it. Analysis:I think the new cable has less wires inside, even if it is supposed to be Ethernet capable. It is probably the reason why the new cable does not work properly on my standard display. This information is mainly to inform new users to check the device with various displays and cables, before telling it does not work. Also, for technicians (if any), it could give a clue. For the display shift, I consider that the synchronization does not start at the right moment. I do not know the way the HDMI is defined, but with previous standards was found that synchronization could be positive or negative. I suppose that this parameter still exists in the video chip/part of the chip, and that an extra argument should/could be added to h3disp to change it. Also, maybe it can be a value of an offset, adjusting when the synchronization should start (earlier/later), or something like a scale factor. If so, it could be harder to change it easily. Solutions?Is there a way to easily change the synchronization? Is there another origin of my problem? Thanks in advance for your help, Jean-Dominique, Annecy, France, Europe, Earth, Sun system, Milky way, Somewhere...

For some reason still unknow to me, my OrangePi Lite Wifi became unreachable twice. I should have checked whether it was something more. Anyhow, temperature is an issue that everyone says about, but I do not believe it is. To determine when Orange Pi Lite Wifi becomes unreachable I wrote a Python script (nothing special, similar to many on the Internet) that posts the ARM7 temperature of Orange Pi Lite to ThingSpeak platform (owned by Matlab). If, and when my Orange Pi Lite Wifi, becomes unreachable I will know as it will stop sending posts to ThingSpeak. Besides the main interest, I do something useful as I monitor the temperature of ARM7. (the image though it shows I created the ThingSpeak channel many hours ago I only got the Python script working this morning so there are no many readings).

Hello, I recently received my first orange pi. When I shutdown lite from armbian menu, yellow light does not turn off. The only way to make it turn off is remove the power plug. Is this normal? Also, I can't restart armbian by pressing the power button after shutting down. I have to unplug and plug the power cable for restart every time. Is that normal too?

Members of the forum may like to know that I have used Armbian's image of Debian Jessie for Orange Pi Lite Wifi that I found quite easy to set up. I have connected Orange Pi to a PIC device to control it with Telegram bot. My tutorial can be read at my blog Redacacia: https://redacacia.me/2016/07/17/telegram-bot-control-with-orange-pi-lite-wifi-and-axe056-board-with-picaxe-18m2/

Hello. I have a annoying problem each time i burn with 'dd' a armbian*raw image (custom) in linux my orange pi lite not boot, i must format and write in windows (write32...) then works. any idea? [ 998.313215] usb 3-7: new high-speed USB device number 6 using xhci_hcd [ 998.443018] usb 3-7: New USB device found, idVendor=058f, idProduct=6331 [ 998.443026] usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 998.443030] usb 3-7: Product: Mass Storage Device [ 998.443033] usb 3-7: Manufacturer: Generic [ 998.443036] usb 3-7: SerialNumber: 058F091111B [ 998.443733] usb-storage 3-7:1.0: USB Mass Storage device detected [ 998.446321] scsi host7: usb-storage 3-7:1.0 [ 999.445719] scsi 7:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0 [ 999.446157] sd 7:0:0:0: Attached scsi generic sg4 type 0 [ 999.959293] sd 7:0:0:0: [sde] 15548416 512-byte logical blocks: (7.96 GB/7.41 GiB) [ 999.959733] sd 7:0:0:0: [sde] Write Protect is off [ 999.959739] sd 7:0:0:0: [sde] Mode Sense: 03 00 00 00 [ 999.960115] sd 7:0:0:0: [sde] No Caching mode page found [ 999.960119] sd 7:0:0:0: [sde] Assuming drive cache: write through [ 999.964855] sde: sde1 [ 999.967051] sd 7:0:0:0: [sde] Attached SCSI removable disk root@diego-trantor:~/Armbian/output/images# [ 996.770245] usb 3-8: reset high-speed USB device number 4 using xhci_hcd [ 997.311523] sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 997.311533] sd 6:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] [ 997.311540] sd 6:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed [ 997.311546] sd 6:0:0:0: [sde] tag#0 CDB: Write(10) 2a 00 00 00 a4 90 00 00 f0 00 [ 997.311551] blk_update_request: I/O error, dev sde, sector 42128 [ 997.311557] Buffer I/O error on dev sde1, logical block 5010, lost async page write [ 997.311567] Buffer I/O error on dev sde1, logical block 5011, lost async page write [ 997.311571] Buffer I/O error on dev sde1, logical block 5012, lost async page write [ 997.311576] Buffer I/O error on dev sde1, logical block 5013, lost async page write [ 997.311580] Buffer I/O error on dev sde1, logical block 5014, lost async page write [ 997.311584] Buffer I/O error on dev sde1, logical block 5015, lost async page write [ 997.311594] Buffer I/O error on dev sde1, logical block 5016, lost async page write [ 997.311599] Buffer I/O error on dev sde1, logical block 5017, lost async page write [ 997.311603] Buffer I/O error on dev sde1, logical block 5018, lost async page write [ 997.311607] Buffer I/O error on dev sde1, logical block 5019, lost async page write [ 997.684441] VFS: Dirty inode writeback failed for block device sde1 (err=-5). [ 997.688937] sde: sde1 [ 998.085631] usb 3-8: reset high-speed USB device number 4 using xhci_hcd [ 998.635907] sde: sde1 [ 999.317134] usb 3-8: reset high-speed USB device number 4 using xhci_hcd [ 999.862662] sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 999.862672] sd 6:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] [ 999.862679] sd 6:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed [ 999.862686] sd 6:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 00 08 18 00 00 08 00 [ 999.862690] blk_update_request: I/O error, dev sde, sector 2072 [ 999.871627] sde: sde1 [ 1000.096850] usb 3-8: reset high-speed USB device number 4 using xhci_hcd [ 1000.642201] sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 1000.642206] sd 6:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] [ 1000.642209] sd 6:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed [ 1000.642212] sd 6:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 00 02 00 00 00 f0 00 [ 1000.642214] blk_update_request: I/O error, dev sde, sector 512 [ 1000.649077] sde: sde1

Orange Pi Lite, it comes with H3 SoC, 512MB DDR3 SDRAM and WiFi, NO ethernet port WiFi: Xunlong said they replace 8189ETV used on the older OPi with 8189FTV on OPi Lite, PC Plus and Plus 2E (Thx TK). Is now available for USD 12.- Some critical words about it. Edit: added WiFi information

Hello, my Orange Pi Lite WiFi (RTL 8189FTV) @ armbian 5.13 for OPi Lite works well on 20 MHz WiFi channels however is not usable on 40 MHz channels. The signal strength vary between 79 to 95 % on 20 MHz channel(s) while from -1 to 36 % on 40 MHz channel(s) and the connection is not possible. It seems the driver still needs some more tweak. Other WiFi devices have no problems with 40 MHz. The router I use to connect to is Asus RT-N18U (Broadcom BCM47081A0). Thank you for your efforts vojtvop

Does anyone have a countermeasure using Onboard Wifi of Orange Pi Lite?