Jump to content

nik012003

  • Posts

    2
  • Joined

  • Last visited

  1. Hi, I've managed to install Armbian_20.05.2_Orangepiplus2e_focal_current_5.4.43_desktop on my board. Now I'd like to get decent web-browsing performance (i.e. 1080 videos on a browser) and I've tried installing the mali drivers with no luck. Is there an updated guide that works with the latest version of armbian? Thanks in advance
  2. Hello, I'm having problems trying to boot armbian (Armbian_20.05.2_Orangepiplus2e_focal_current_5.4.43.img.xz) on this Orange Pi Plus 2e board. I'm using a fast original samsung 32gb sd card and I've tried multiple power adaptors. Here's the output from the serial console: U-Boot SPL 2020.04-armbian (Jun 03 2020 - 07:59:25 +0200) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2020.04-armbian (Jun 03 2020 - 07:59:25 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface7 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3789 bytes read in 2 ms (1.8 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 152 bytes read in 2 ms (74.2 KiB/s) 11634455 bytes read in 556 ms (20 MiB/s) data abort pc : [<bff970de>]. lr : [<0001ea42>] reloc pc : [<4a01a0de>]. lr : [<8a0a1a42>] sp : bbf54b70 ip : bbfc9dd8. fp : bffdc644 r10: 00000000 r9 : bbf5cee0. r8 : 000639f0 r7 : ffff0031 r6 : 00000200. r5 : bffd2784 r4 : ffff0031 r3 : 00000001 r2 : 0001ea41. r1 : 00011160 r0 : 00000006 Flags: nzCv IRQs off FIQs off Mode SVC_32 (T) Code: 4664 eb02 0e03 42ac (6827) d105 Resetting CPU ... resetting ... U-Boot SPL 2020.04-armbian (Jun 03 2020 - 07:59:25 +0200) DRAM: 2048 MiB Trying to boot from MMC1 One time it acutally manage to decompress linux and I even got a display signal with the linux kernel booting, but it stopped after about 10 seconds. The debian image on the organgepi website boots fine, although it's very old and pretty buggy. How can I fix this? Thanks in advance EDIT: I've managed to install that version of armbian on the integrated 16gb emmc memory. Unfortunately armbian only boots when i apply pressure on the circled part of the PCB in the image. I'm really confused. It boots fine debian image I got from the official link( https://drive.google.com/drive/folders/1wAdkC25BmjMwapWahEEQGTvi-yuwo8Gx ), but it refuses to boot armbian unless I apply pressure to that point of the board. EDIT 2: I've 3d printed a case for the orange pi and I've put some spongy material on the circled part of the board in order to get it running. It's been running for 10hrs and I haven't noticed any problem. I'm still confused on why the "stock" images work and armbian doesn't without this mod.
×
×
  • Create New...