Jump to content

Search the Community

Showing results for tags 'orangepiprime'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. Hello, I'm trying the currently offered Armbian Bookworm images for the Orange Pi Prime, using kernels 6.1.30 and 6.2.16, and notice that there is no support for SoC temperature monitoring, neither in armbianmonitor, nor in /sys/devices/virtual/thermal/. Here is the debug info from 6.2.16: https://paste.armbian.com/cetovulubu Is that a known issue? An older Armbian image that I have downloaded previously, using the kernel 5.15.93, shows the temperature just fine.
  2. Can you power Prime with OTG port? Or does only PSU work?
  3. Hey all, So recently I got myself an Orange Pi Prime so I could attempt to do some SPI flashing through spidev and flashrom. I have been going at it, set up the board, got an actually decent power supply, and set up everything. Eventually I got myself into the steps of setting up the pins for spi use. At first, I used armbian-config to enable the spidev into /boot/armbianEnv.txt then I added param_spidev_spi_bus=0 into armbianEnv.txt I rebooted and the spi device file still doesn't show up, any ideas? I have: went through armbian-config (System -> Hardware -> spi-spidev) added param_spidev_spi_bus=0 to armbianEnv.txt I even decided to read up on dtb files and dts overlays and decompiled my sun50i-h5-spi-spidev.dtbo file manually went ahead and "enabled" the spi devices by editing the dtbo file, recomplied it, and moved them into /boot/dtb/allwinner/overlays/sun50i-h5-spi-spidev.dtbo nothing. thank you for your time. armbianEnv.txt
  4. When i first tried out my orange pi prime in october 2020 i thought i recalled that the wifi worked. With a current armbian image, the wifi can't authenticate. I tried several of the available kernel images. I'm sure that the wpa2 password is correct because I control the router and other devices connect all the time. If i plug in an ath9x usb wifi dongle, that is able to connect, so it would appear to be an issue with the onboard rtl8723bs driver.
  5. Hi! Armbian_21.08.1_Orangepiprime_focal_current_5.10.60_xfce_desktop sometime failed to boot. No green indicator, and black screen. Tried to decrease CPU max frequency sudo nano /etc/default/cpufrequtils ### ENABLE=true MIN_SPEED=480000 MAX_SPEED=1200000 GOVERNOR=ondemand ### but still failed to boot sometimes. Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20_desktop have been installed before and boot fine during 2 years.
  6. Hello, please tell me why Chromium does not work on Orange Pi Prime? Здравствуйте, подскажите пожалуйста, почему не работает Chromium на Orange Pi Prime?
  7. My board works pretty well upto 1 000 00 Hz without fan and up to 1 200 000 Hz with (noctua) fan. However I am still using an usb wifi card, to be able to connect with ssh. Anyone having wifi with the built in wifi card work properly? Mine just shuts off. With an external wifi usb card, it works like a charm. Since my 3-d printers are in the living room I i have the orange pi:s in the living room. They are primary used for octoprint. I would like to have the built in wifi on orangepi prime to work.
  8. Help me! 1. I was downloaded images from https://www.armbian.com/orange-pi-prime/ 2. then write to SD Card (32Mb) using Etcher (i was try Ubuntu and Debian) 3. insert card, turn on power, begin loading 4. but i see "starting kernel" message and loading stopped! Why?
  9. I'm trying to run an executable on an OrangePi Prime. The message is: -bash: <filename>: No such file or directory The output of the file command on the executable is: <filename>: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, BuildID[sha1]=xxx, not stripped The app runs fine on OrangePi One, OrangePi Zero and Raspberry Pi.
  10. Hi, My Orange Pi Prime stopped working within an hour of use. Setup: Orange Pi Prime v1.0 (201811) Official PSU, rated 5V 3A Official plastic case (without heatsinks) Display attached using HDMI Network attached 100mA keyboard attached SD Card: Sandisk 64G Ultra SD Card tested "The real thing" SD Card formatted to factory defaults Images (Armbian Stretch next for Orange Pi Prime) checked for authenticity and integrity SD flashed using Etcher First boot succesful Installed tmux Set up SSH using armbian-config and used it to connect Installed docker using armbian-config successfully When trying to install ISPConfig: the SSH connection timed out, and when I switched my screen back to HDMI I could see the display was corrupted (colored streaks), armbian-config's did give a generic error message (something like "Error during installation"). The Pi Prime did not respond, the case was quite warm. After that I could not get it to boot again. I've tried both Armbian images, and one of the Debian server Orange Pi Prime images. Measured supply voltage (at the barrel connector's pins): 5.25V On further inspection I saw some discoloration on the CPU and on one of the memory chips: The ambient room temperature is around 21 degrees celcius I don't have a USB to TTL converter yet. I also measured some of the resistors and found that R3 (KEYADC to AVCC and KEYLADC) was only 39K instead of 100K as it should be according to the schematics.
  11. Hi Has anyone got the on board Bluetooth going on their OP Prime ?
  12. Hi! I was using armbian 5.60 with 4.14.70 kernel and WiFi AP worked flawsessly. Today I had to rebuild my sd card, so I downloaded the latest available build Armbian Stretch mainline kernel 4.19.y I can connect to WiFi from the board, also able to setup a WiFi AP on the board. But when I try to connect to the new AP I see the following message in terminal and the connecting device fails after several seconds: Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 349.842020] Internal error: Oops: 96000004 [#1] SMP Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 350.021242] Process RTW_CMD_THREAD (pid: 607, stack limit = 0x0000000068aba9f4) Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 350.069577] Code: f9405ae0 a90a0ba0 11000421 8b02001b (b8626800)
  13. RTL8211D PHY on OrangePi Prime is not detected neigther in uBoot mode or Kernel mode. Will share the logs ASAP. Please suggest!
  14. Hi folks, A few months back, I set up an Orange Pi Prime on Armbian Bionic (Armbian_5.52.180715_Orangepiprime_Ubuntu_bionic_dev_4.18.0-rc4.7z). I'm now putting together a home automation workshop around this configuration, but it looks like it's now missing from the website (https://www.armbian.com/orange-pi-prime/) and download site (https://dl.armbian.com/orangepiprime/). Is Bionic no longer supported for this board, or was this an oversight? Is there something I can do to help?
  15. Hi everybody, burned the latest armbian for opi prime since I got the board, and the greed led is working, but after all I cannot find it with “arp -a” and the ethernet led is flash, both color. Anyone have the idea? I don't have a screen or tv even a router here course I am at university. So I directly connected my computer with the board. Don't think anything is wrong.
  16. After update to Armbian 5.60 (Debian 9) hostapd became unable to start. ``` # /usr/sbin/hostapd -B -P /run/hostapd.pid /etc/hostapd/hostapd.conf.orig -dd random: Trying to read entropy from /dev/random Configuration file: /etc/hostapd/hostapd.conf.orig ctrl_interface_group=0 nl80211: Supported cipher 00-0f-ac:1 nl80211: Supported cipher 00-0f-ac:5 nl80211: Supported cipher 00-0f-ac:2 nl80211: Supported cipher 00-0f-ac:4 nl80211: Supported cipher 00-0f-ac:6 nl80211: Using driver-based off-channel TX nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 3 iftype 3 (AP) nl80211: Failed to set interface 3 to mode 3: -1 (Operation not permitted) nl80211: Try mode change after setting interface down nl80211: Set mode ifindex 3 iftype 3 (AP) nl80211: Failed to set interface 3 to mode 3: -1 (Operation not permitted) Could not set interface wlan0 flags (UP): Operation not permitted nl80211: Failed to set interface up after switching mode nl80211: Interface mode change to 3 from 0 failed nl80211: Could not configure driver mode nl80211: deinit ifname=wlan0 disabled_11b_rates=0 nl80211: Remove monitor interface: refcount=0 netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP) nl80211: Set mode ifindex 3 iftype 2 (STATION) nl80211 driver initialization failed. hostapd_interface_deinit_free(0xaaaac3834970) hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1 hostapd_interface_deinit(0xaaaac3834970) wlan0: interface state UNINITIALIZED->DISABLED hostapd_bss_deinit: deinit bss wlan0 wlan0: AP-DISABLED hostapd_cleanup(hapd=0xaaaac3835c20 (wlan0)) hostapd_free_hapd_data: Interface wlan0 wasn't started hostapd_interface_deinit_free: driver=(nil) drv_priv=(nil) -> hapd_deinit hostapd_interface_free(0xaaaac3834970) hostapd_interface_free: free hapd 0xaaaac3835c20 hostapd_cleanup_iface(0xaaaac3834970) hostapd_cleanup_iface_partial(0xaaaac3834970) hostapd_cleanup_iface: free iface=0xaaaac3834970 ``` ``` # cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepiprime BOARD_NAME="Orange Pi Prime" BOARDFAMILY=sun50iw2 VERSION=5.60 LINUXFAMILY=sunxi64 BRANCH=next ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image # cat /etc/debian_version 9.5 # uname -a Linux mxopipr01 4.14.70-sunxi64 #274 SMP Wed Sep 19 12:09:30 CEST 2018 aarch64 GNU/Linux ``` ``` # whoami root # iwconfig wlan0 mode master Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not permitted. ``` ``` # iw list Wiphy phy0 max # scan SSIDs: 9 max scan IEs length: 2304 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * monitor Band 1: Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) (no IR) * 2472 MHz [13] (20.0 dBm) (no IR) * 2484 MHz [14] (20.0 dBm) (no IR) Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * set_bss * join_ibss * set_pmksa * del_pmksa * flush_pmksa * frame * set_channel * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 WoWLAN support: * wake up on anything (device continues operating normally) software interface modes (can always be added): * monitor interface combinations are not supported Device supports scan flush. ``` Also have lots of this logs ``` # dmesg -T | tail -n 3 [Fri Oct 26 14:47:45 2018] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [Fri Oct 26 14:47:45 2018] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [Fri Oct 26 14:47:46 2018] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin # ll /lib/firmware/rtlwifi/ total 856 drwxrwxr-x 2 root root 4096 Oct 25 17:47 ./ drwxrwxr-x 19 root root 4096 Oct 25 17:47 ../ -rw-rw-r-- 1 root root 11216 Sep 19 08:07 rtl8188efw.bin -rw-rw-r-- 1 root root 13904 Sep 19 08:07 rtl8188eufw.bin -rw-rw-r-- 1 root root 16192 Sep 19 08:07 rtl8192cfw.bin -rw-rw-r-- 1 root root 14818 Sep 19 08:07 rtl8192cfwU.bin -rw-rw-r-- 1 root root 16332 Sep 19 08:07 rtl8192cfwU_B.bin -rw-rw-r-- 1 root root 16014 Sep 19 08:07 rtl8192cufw.bin -rw-rw-r-- 1 root root 16116 Sep 19 08:07 rtl8192cufw_A.bin -rw-rw-r-- 1 root root 16096 Sep 19 08:07 rtl8192cufw_B.bin -rw-rw-r-- 1 root root 16116 Sep 19 08:07 rtl8192cufw_TMSC.bin -rw-rw-r-- 1 root root 31376 Sep 19 08:07 rtl8192defw.bin -rw-rw-r-- 1 root root 31818 Sep 19 08:07 rtl8192eefw.bin -rw-rw-r-- 1 root root 25264 Sep 19 08:07 rtl8192eu_ap_wowlan.bin -rw-rw-r-- 1 root root 31818 Sep 19 08:07 rtl8192eu_nic.bin -rw-rw-r-- 1 root root 25878 Sep 19 08:07 rtl8192eu_wowlan.bin -rw-rw-r-- 1 root root 80208 Sep 19 08:07 rtl8192sefw.bin -rw-rw-r-- 1 root root 122328 Sep 19 08:07 rtl8712u.bin -rw-rw-r-- 1 root root 22172 Sep 19 08:07 rtl8723aufw_A.bin -rw-rw-r-- 1 root root 24118 Sep 19 08:07 rtl8723aufw_B.bin -rw-rw-r-- 1 root root 19200 Sep 19 08:07 rtl8723aufw_B_NoBT.bin -rw-rw-r-- 1 root root 30746 Sep 19 08:07 rtl8723befw.bin -rw-rw-r-- 1 root root 20886 Sep 19 08:07 rtl8723bs_ap_wowlan.bin -rw-rw-r-- 1 root root 32108 Sep 19 08:07 rtl8723bs_nic.bin -rw-rw-r-- 1 root root 26398 Sep 19 08:07 rtl8723bs_wowlan.bin -rw-rw-r-- 1 root root 20886 Sep 19 08:07 rtl8723bu_ap_wowlan.bin -rw-rw-r-- 1 root root 32108 Sep 19 08:07 rtl8723bu_nic.bin -rw-rw-r-- 1 root root 26398 Sep 19 08:07 rtl8723bu_wowlan.bin -rw-rw-r-- 1 root root 11662 Sep 19 08:07 rtl8723fw.bin -rw-rw-r-- 1 root root 22996 Sep 19 08:07 rtl8723fw_B.bin -rw-rw-r-- 1 root root 28984 Sep 19 08:07 rtl8821aefw.bin -rw-rw-r-- 1 root root 19858 Sep 19 08:07 rtl8821aefw_wowlan.bin ``` No ideas yet. Thanks in advance!
  17. My Prime is reasonably stable now, except for running youtube videos in fullscreen 1920x1080, which drives the heat up (I've seen 87 !), and after a few minutes freezes the video with the sound continuing. I can't find any mention of YouTube in the documentation, and only video URLs in the forum. Is there some trick I have missed?
  18. Following the suggestion that if I didn't like the documentation, I should write it myself, here is my version of what I was hoping for, (how to get started) instead of the formal definition style of a reference manual. Please feel free to correct the errors and use it how you wish. How to set up OS for development boards General This tutorial should apply to any board supported by Armbian, it uses the example of Orange Pi Prime. 0. Introduction The Prime's hardware is good, but can only work properly if the OS has all the drivers for the chips used on the board and only a few OS versions have them right. The most common faults are insufficient power (5V, 2.5A), poor or slow micro-SD cards, and CPU chip (Allwinner H5) overheating due to overclocking. The driver for the CPU chip watches the temperature and reduces the clock speed to keep temperatures in the safe zone (the lower the better, extending the board's life). Because of the overheating problems, I recommend NOT putting your Prime in a plastic box - mount it somehow in a vertical plane, and buy a heatsink for it, the bigger the better, and run a temperature monitor (LXDE has one built in). 1. Choosing the OS In my experience, only Armbian has the right approach, so I recommend downloading your OS from http://armbian.com/download. Your first choice is whether to have a GUI, and which desktop to use. The "desktop" Armbian version uses XFCE, which I dislike - I MUCH prefer LXDE. So download the non-desktop ("server") version and install LXDE afterwards. It is very hard to switch desktops from XFCE, because the login screen doesn't have an icon to choose the new desktop environment, and its a waste of electrons downloading it if you are going to use another one. 2. Copy to micro-SD Having downloaded and unzipped your image, you have to copy it to the micro-SD card. You need Etcher to do this, (http://etcher.io/download). It will also do a verify pass for you. You should also do a checksum check on it. If your SD card has a checksum error, it will NEVER work. 3. First boot Put the Micro-SD card in the TF slot on your new board, and the cables for ethernet, HDMI, and lastly power. After 5 seconds it will have loaded the bootloader, switched on the green LED, put something temporarily on the screen and started loading the Linux kernel. During the boot, nothing will appear on the screen for 8 seconds (while the screen driver loads), then a cursor will flash in top left of the screen for about 30 seconds (first time only, later 10 seconds), and then you will be invited to log in. The username is "root" and the password is "1234". It will then give an interesting readout of some basic values, and a CLI prompt. Congratulations, you have successfully booted ! If you get a red LED, you have messed up - either the power supply or the micro-SD card or the checksum. The first thing you must now do is change the root password, and the second is to nominate the first non-root user and password. Then you can reboot: sudo reboot now and log in as the non-root user. As the Armbian OS download will be slightly out of date, you will then need to do: sudo apt update sudo apt upgrade to get the updates since the download file was produced. 4. Copying file system to USB-SATA (optional) At this point you can plug in an empty disk drive via USB (on a powered USB hub), a 60GB SSD is sufficient for this. Remember that SSDs do not like being unplugged when they are busy, and you can't tell when that is, so DON'T DO IT. The entire OS is first saved on the micro-SD card, and the boot section will always remain there, but you now have the option to copy the root filesystem to SSD for faster and safer booting: sudo armbian-config which offers you a menu of options, choose System, which will load a bunch more options, choose "micro-SD to USB/SATA installation". The next questions should only offer you one option - to format /sda1 as ext4. Then it will start the copy, which is very slow and boring, and then tidy up. After this you must reboot and log in as the non-root user. 5. Second boot Other armbian-config options include setting your timezone, hostname, and making your user login compulsory. Finally we get to install the X server and our desktop environment, in this case: LXDE (alternatives XFCE4, KDE, GNOME3, Mint, etc ...) sudo apt install xorg lxde The LXDE package includes the lightdm display manager package, and as part of its installation it will ask you if you want lightdm to be your current display manager instead of Armbian desktop's nodm, say yes. 6. Second reboot And now when we reboot: sudo reboot now it should end up in the GUI at the login screen of lightdm. Click the icon to check that it is going to use the LXDE desktop. Enter your username and password, and it should go to your new desktop. The taskbar is at the bottom and is black, and the background of the desktop is dark grey - yuck. But you can right click on the taskbar and choose Panel Settings, and move the panel to the left margin (the natural place with wide screens) and change its colour. Right-clicking the desktop will give you options to choose you own colour or photo as the desktop background. Hurray! Now you can start installing all your apps and fine-tuning their settings. 7. Trouble-shooting If it doesn't manage to get into the GUI desktop, it will probably go into the CLI interface instead. This probably means an instance of the X server is not running, which can be fixed by: startx The keyboard shortcut Alt-f7 should switch to tty7, which is the GUI screen. Control-Alt-f1 should switch to tty1, which is the CLI screen. There are too many ways for this set up to go wrong to cover them all. Ask (politely) at the Armbian Forum, http://forum.armbian.com saying precisely what you did (that worked), and what you did that didn't, including screenshots, logs and exact error messages. armbianmonitor -u will produce a log of the boot process and upload it to a public webspace, so you can post that URL with your question. Remember the forum helpers are unpaid, busy people, and they will expect you to have searched the documentation and forums first.
  19. Hello. When the browser starts (chromium), the board hangs, the screen turns gray. when in LibreOffice Writer I build graphics or draw figures or lines, the board hangs, the screen turns gray. load on the processor and memory for 100% console applications - all in order. What is the problem?
  20. Hello to everyone , I'm trying to read NMEA messages from GPS receiver via UART . But can't read anything on pins 8,10 & 38,40 .. What coulb be a reason ? GPS receiver is working fine , I can read it via USB-UART converter on the same board ... Thanks in advance ! Here's my system (UARTs are enabled via armbian config utility): root@orangepiprime:/boot# cat armbianEnv.txt verbosity=1 console=both overlay_prefix=sun50i-h5 rootdev=UUID=aca8c4ac-41d0-4e0b-ae7e-1d727baa4d43 rootfstype=ext4 overlays=pps-gpio uart1 uart2 uart3 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@orangepiprime:/boot# uname -a Linux orangepiprime 4.14.70-sunxi64 #274 SMP Wed Sep 19 12:09:30 CEST 2018 aarch64 GNU/Linux
  21. Orange Pi Prime (H5) Armbian_5.59_Orangepiprime_Debian_stretch_next_4.14.65.img 1. Installed OK, installed LXDE-desktop OK, removed XFCE4 OK. 2. Normal temperature 42, ocassionally up to 73, occasional reset. Ordered some heatsinks. 3. Keepass2 fails to load (runs under mono): dk@orangepiprime:~$ keepass2 Gtk-Message: Failed to load module "atk-bridge" System.ArgumentException: A null reference or invalid value was found [GDI+ status: InvalidParameter] at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x0009b] in <1917aa1c39d94b1a91807b8cd9f03350>:0 at System.Drawing.Bitmap..ctor (System.Int32 width, System.Int32 height, System.Drawing.Imaging.PixelFormat format) [0x00017] in <1917aa1c39d94b1a91807b8cd9f03350>:0 at System.Drawing.Bitmap..ctor (System.Drawing.Image original, System.Int32 width, System.Int32 height) [0x00000] in <1917aa1c39d94b1a91807b8cd9f03350>:0 at System.Drawing.Bitmap..ctor (System.Drawing.Image original, System.Drawing.Size newSize) [0x00010] in <1917aa1c39d94b1a91807b8cd9f03350>:0 at (wrapper remoting-invoke-with-check) System.Drawing.Bitmap:.ctor (System.Drawing.Image,System.Drawing.Size) at System.Windows.Forms.XplatUIX11.DefineCursor (System.Drawing.Bitmap bitmap, System.Drawing.Bitmap mask, System.Drawing.Color cursor_pixel, System.Drawing.Color mask_pixel, System.Int32 xHotSpot, System.Int32 yHotSpot) [0x0004e] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.XplatUI.DefineCursor (System.Drawing.Bitmap bitmap, System.Drawing.Bitmap mask, System.Drawing.Color cursor_pixel, System.Drawing.Color mask_pixel, System.Int32 xHotSpot, System.Int32 yHotSpot) [0x00000] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.Cursor.CreateCursor (System.IO.Stream stream) [0x00058] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.Cursor..ctor (System.Type type, System.String resource) [0x00021] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.Cursors.get_SizeNWSE () [0x0001a] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.SizeGrip..ctor (System.Windows.Forms.Control CapturedControl) [0x00006] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.SizeGrip:.ctor (System.Windows.Forms.Control) at System.Windows.Forms.ScrollableControl.CreateScrollbars () [0x000c2] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.ScrollableControl..ctor () [0x000b0] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.ContainerControl..ctor () [0x0000e] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at System.Windows.Forms.Form..ctor () [0x00012] in <d5b72d15d4f7424c8a1538e3f19ec2e3>:0 at KeePass.Forms.MainForm..ctor () [0x00146] in <0219da3f853d44e8843bebc0d0fe91e3>:0 at (wrapper remoting-invoke-with-check) KeePass.Forms.MainForm:.ctor () at KeePass.Program.Main (System.String[] args) [0x0053d] in <0219da3f853d44e8843bebc0d0fe91e3>:0 dk@orangepiprime:~$ Some discussion of this being due to inotify. 4. GUFW > Add Rule fails, warns of / having permissions 777, but it is 755. Very odd. 5. Thunderbird very slow to load (30 seconds at 100% of 1 core). Message Filters > New also slow, Local Folders dropdown list of subfolders empty (!) 6. Benchmark: CPU Cryptohash: 29 , versus 22 for OPi PC (H3) 7. Otherwise everything working very well - well done and thank you.
  22. Old post below, here is what I found out thanks to some help from linux-sunxi IRC, I think this is a bug in the ondemand governor When using ASIX AX88772B USB to ethernet adapter and the cpu-governor is on ondemand, transfer speed is very slow. If governor is set to conservative or performance (yes that's right) speed is ok, 50 Mbit at least. So the problem has nothing to do with cpu speed as such (it's working @ steady 480Mhz and @ steady 1200Mhz) for now I'll stick with conservative as I don't want my board to burn up, but It would be nice if someone could take a look at that ondemand governor. Additional info: Changing SMP-affinity on USB IRQs (cat /proc/interrupts |grep ehci_hcd:usb) also improved performance a bit, but not much, this seems to be missing for OrangePi Prime in /etc/init.d/armhwinfo: for i in $(awk -F':' '/ehci_hcd:usb/{print $1}' </proc/interrupts | sed 's/\ //g'); do echo 2 >/proc/irq/$i/smp_affinity done ---- Is the mainline USB support (4.14.34-sunxi64) known to be slow/ have bugs on H5 devices? I'm using a ASIX AX88772B USB to ethernet adapter (100Mbit) as a second network interface which can hardly reach 13Mbit. Also when using USB keys and copying large amounts of data the kernel sometimes crashes and until then ksoftirqd uses up to 40% cpu. A normal usb key (storage device) attached can reach 50Mbit which is not great but ok I guess. The ASIX adapter itself, works @80Mbit on the Rpi3, so it's not the adapter as such which is causing the problems. It's connected as high speed device (Driver=asix, 480M) I just would like to know if this is a know restriction/bug, in the current mainline kernel in which case I can just wait.
  23. Hi, I am using the Ubuntu desktop image found here https://www.armbian.com/orange-pi-prime/ I am able to start the board, it lights up and connects to the network via ethernet -- I see it come up in my DHCP table and am then able to connect via SSH Docs say to use root:1234 for login, but I get Access denied. I found another forum post that says root is disabled via SSH by default. When I try to connect locally, I get no video from HDMI so I don't know what it's loading up to. I had hoped to be able to configure via SSH but can't get in. Any ideas on how I can proceed? Thank you!
  24. Hi, I'm running armbian ubuntu image 4.13.14-sunxi64 on Orange Prime, and have a problem. Wifi wont work. I can see a wlan0 as a result of ifconfig, but it neither find a wireless network, nor connect to provided. From dmesg i can see driver is spamming with message [ 303.336420] RTL8723BS: ERROR sd_recv_rxfifo: alloc recvbuf FAIL! I have /var/log overflow in several minutes and also frequent system freezes. rmmod r8723bs causes all this stuff to stop. Can anyone suggest where should i look? Thanks. Btw, self built debian stretch image 4.14 gives the same behaviour. I understand that H5 support is experimental, I just want to solve this issue.
  25. Hi all, I was struggling to have a stable Wifi connection on my new Orange Pi Primes, and believe I found a solution, so I thought it's nice to share it Symptoms: Wifi would connect right after reboot, but would disappear if Orange Pi Prime was idle for about 30min. The only way to reactivate would be to either pull the cable out (as there are no buttons yet), or to login via ethernet, perform ifconfig down && if config up. I didn't liked either of the options, so I decided to investigate. My log was full of: [89201.577208] RTL8723BS: nolinked power save enter [89201.967063] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [89202.187266] RTL8723BS: nolinked power save leave [89208.120724] RTL8723BS: nolinked power save enter [89214.307901] RTL8723BS: nolinked power save leave It's clear that power saving was a culprit, so I needed to find how to disable it. Attempts to solve the issue I tried disabling power saving using iwconfig command, but that didn't work: $ sudo iwconfig wlan0 power off Error for wireless request "Set Power Management" (8B2C) : SET failed on device wlan0 ; Operation not permitted. I also tried doing that from Network Manager, by editing /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf: $ cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf [connection] # 2 = power saving off # 3 = power saving on wifi.powersave = 2 $ mv /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf but that didn't work either (even after reboot). Working solution Seems that RTL8723B (Wifi driver user by Orange Pi Prime) can only set powermode during module load, so I created /etc/modprobe.d/r8723bs.conf with following content: $ cat /etc/modprobe.d/r8723bs.conf options r8723bs rtw_power_mgnt=0 rtw_enusbss=0 $ ls -lsa /etc/modprobe.d/r8723bs.conf 4 -rw-r--r-- 1 root root 47 Jan 11 10:07 /etc/modprobe.d/r8723bs.conf (make sure ownership and permissions are right), and after a reboot, Wifi remained up and running for days. Hope this helps someone.
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines