Jump to content

Search the Community

Showing results for tags 'pinebook-pro'.

  • 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


  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







Found 12 results

  1. Also the function keys don't seem to work either. Any fix?
  2. Hello, unfortunatelly I post again, because of the latest problem with broken install of initramfs .... The system is unable to write it to uboot and gives the error about unsupported architecure. Every standard commands are probed, without result. it comes always the same error.
  3. Hello, as already mentioned in topic USB C port doesn't work after upgrading to the latest kernel 6.6.2 . The previous problem with not working left usb 3 port persist no more. Everything is fine. As I remember , before update the usb c port has worked with the adapter and the devices like mouse, usb flash etc. Now it doesn't work any more, furthermore it gives no signal of life. There is 0 amps current measured, also dmesg -W gives no output at all after plugging in the device. PS: I was unable to upload the report file, also the service paste.armbian.com doesn't work at the moment.
  4. !!! Warning !!!: Think twice before you upgrade kernel on your PineBook Pro. After years unfortunately I decided to unlock upgrades Armbian Kernels and upgraded kernel to the newest one (current) - 5.15.93. After reboot Armbian couldn't find my encrypted root disk and booting ended every time in (initramfs). I installed again kernel 5.10.60 #21.08.1 and Armbian finds my encrypted disk again. Of course still there is no information that I have to enter the password to unlock disk but only black screen. Happily I know that I have to enter the password when the screen is black. Every upgrade of Armbian is connected with a dose of stress that I'll have to fix my computer. I thought that every following kernel should fix errors not create them.
  5. does displayport over usb-c dock work for you? It doesn't for me neither on 5.15 nor on 6.1.
  6. I slowly convinced myself that I wanted a PineBook Pro, some time after the first production run. But then COVID, parts shortages, etc. happened and they were not available again until about mid-2022. But when they were, I decided to snap one up. And since then I have not been able to get it to boot Armbian. It came from the factory with Manjaro, which for me being a Debian guy, might as well be useless. So the PBP sat around collecting dust. Since then I have tried a few times to get it to work. I read many forum posts, tried some things. I won't document all that in detail. In this post, I will continue from where I left off here. However to summarize, that was about comparing DTB/DTS files to Kali, which supposedly works. That may become useful later, but I don't think that's the main problem. I think that the main problem is that this new batch came from the factory with no bootloader flashed to the included SPI flash chip. This is a problem on PineBook Pro because the RK3399 has a kind of weird boot order: SPI, eMMC, SD card. Therefore, if you just put in some SD card you flashed, it still boots from the factory Manjaro from the eMMC. Whatever bootloader they are using also apparently will not recognize an otherwise working Armbian image on an SD card. Now, because of the weird boot situation, there is supposed to be a switch to turn off eMMC. However this did not work for me. Which means one of 2 things: The switch does not work. I read at least one other person saying this. Also on the new revision, it's in a slightly different place than the old revision (may be a clue, maybe not). I simply had a bad Armbian image (which I had burned to sd card) that would not boot for whatever reason.[0] But let's put that aside for a moment. As I still think the main problem is the (empty) SPI. And that will be the easiest/best path forward. I confirmed the 'blank SPI' theory 2 different ways. First, as mentioned in a follow-up to the linked post (4 paragraphs above): As Martijn Braam states here: Of course, I like to beat a horse until it's really dead be thorough in my investigations, so today I wasted a lot of time[1] verifying that this indeed was the case. I did so by dd'ing the /dev/mtd0 block device into a file[2]. When I examined the file, it contained all FF, and also it is about 16 MiB in size. To me this confirms that indeed, the SPI on the new batch comes from the factory empty. So what is next? I keep reading that the only people who had success first had to install something like tow-boot to the SPI. That will be my next step. But before I flashed anything to SPI, I wanted to see what really came from the factory (which I did above). I will continue to document my progress whenever time allows for me to work on this. [0] Once I got the bootloader situation sorted, I later used this same image (on the SD card) to boot and install Armbian, so I do not think this was the case. [1] In the end the solution was simple. But first I wasted a lot of time trying to get rkdeveloptool working in Manjaro on the PBP. Only to realize it's intended to be used from a second machine to read the SPI flash via USB in maskrom mode. Anyway, lesson learned. [2] I tried to attach it but maybe it's too big.
  7. Hello all, I got a problem after new update of armbian firmware through your own module (script). The left USB port on pinebook pro has stoped working at all. Before that was occasionaly after 6 -7 boot ups only one time not working (it is used for mouse). Now after x rebooting it doesnt work at all. The right USB port works without problems. On the left, also USB flash drive doesn't work. No idea, what could it be? Before, as already said, it has worked in 90%. Before firmware upgrade.
  8. Myy

    Mainline VPU

    So, I tried to adapt @Kwiboo and @jernej patches on my 5.6 branch, but this made the kernel fail to boot for no visible reason. Since I were able to boot it without the VPU patches, I'm convinced that it's their readaptation that broke something. The patches applied are here : https://github.com/Miouyouyou/RockMyy64 If someone wants to play with them and determine which one break the boot process.
  9. I bought a Pinebook Pro two weeks ago. It came with Manjaro KDE preinstalled on EMMC. I wanted to try out Armbian, so I downloaded the Bookworm XFCE image from May 27th. In order to get the SD booted, I first flashed Tow-Boot for Pinebook Pro (pine64-pinebookPro-2021.10-005.tar.xz) from github Tow-Boot to the SPI. Then during boot after pressing ESC the menu lets you select the SD card for boot. The first boot to Armbian worked well. I could set up user, timezone and everything. The XFCE desktop looks very clean with a reasonable selection of software. Well done, team! But after I upgrade the system with apt update & upgrade, the next time the machine is booted and SD card is selected, armbian won't boot anymore 😞 The upgrade seem to have broken something. I tried it twice, the second time freezed the kernel-upgrades in the armbian-config tool prior to upgrading it. Didn't help. Manjaro from EMMC still boots ok. Attached is a screenshot of the failed boot process, after I selected SD card to boot on the Tow Boot menu.
  10. THE MEDIA SCRIPT IS DEPRECATED, IN FAVOR OF THE LEGACY MULTIMEDIA INTEGRATION. PLEASE REFER TO THIS TOPIC: So finally we have the first version of: The UN-official, UN-supported, etc... RK3399 MEDIA TESTING SCRIPT This is the first release of the RK3399 media testing script. The script provides a functionality similar to its RK3288 equivalent: Installing all the libraries and system configurations necessary for GPU accelerated X desktop, Chromium WebGL, full VPU video play acceleration up to 4k@60 10-bit HEVC (the maximum supported by the SoC), and GLES 3.2 / OpenCL 1.2 support. Three video players supporting full VPU acceleration (RKMPP) and KMS display (GBM or a X11 DRM "hack", as described by the authors), namely: MPV, Gstreamer and Kodi. Two example programs using the OpenCL functionality: Examples form the Arm Compute Library, and a GPU crypto miner (an old version, but small and simple). A library that will act as an OpenGL to OpenGL-ES wrapper, allowing you to run programs that use OpenGL 1.5-2.0. Two additional features, that have no big interest from the Armbian development prospective, but I find them interesting to play with: Chromium browser with support for Flash and DRM-protected commercial web video streaming (tested with Amazon Prime, should also work with Netflix, Hulu, etc.), and a simple Pulseaudio GTK equalizer using LADSPA. Here is a more thorough documentation: >>> DOWNLOAD LINK <<< Prerequisites: You need a fresh Armbian Bionic desktop image with legacy kernel installed. Instructions: Download the file above Untar it: tar xvf media-rk3399_*.txz cd media-script ./media-rk3399.sh Notes: This script is not officially supported by the Armbian project. It is just a community effort to help the development of the main build, by experimenting with a possible implementation of the media capabilities of this particular SoC. Therefore, questions about the script should not be laid out as support requests, but as commentaries or community peer-to-peer assistance. That being said, all commentaries/suggestions/corrections are very welcome. In the same way, I will do my best to help solve any difficulty that may arise regarding the script. Enjoy!
  11. I have a latest ubuntu armbian on a pinebook pro, I use an DUB-1312 gigabit to usb 3.0 for wired connection, I plug it in the usb 3 port of the pinebook but I run iperf I see the same speeds as the other usb 2 port. $ iperf3 -c Connecting to host, port 5201 [ 5] local port 48140 connected to port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 41.7 MBytes 350 Mbits/sec 0 298 KBytes (More thread only made results worst) While the same DUB-1312 plugged in my amd64 ubuntu computer achieve 950Mb/s easly (capped by the other testing device (an odroid-hc1)). Same thing for a random usb 3.1 key I have laying around (so its very unlikely a problem with the ethernet over usb driver). It seems to me that the usb 3 port is only being used with usb 2. Am I the only with this issue ?
  12. I'm trying to make a script to run on the Pinebook Pro and I'm having mpp errors while trying to leverage it in ffmpeg. I'm not sure what might be causing the error but according to THIS THREAD , compiling with `-DHAVE_DRM='ON` should resolve it (which it doesn't in my case). I'm using the 20171218 release of rkmpp and ffmpeg 4.2. Any help is appreciated. mmp build: cmake -DHAVE_DRM='ON' -DCMAKE_BUILD_TYPE:STRING='Release' -DCMAKE_INSTALL_PREFIX:PATH='/usr' \ -DRKPLATFORM:BOOL='ON' -Wno-dev \ -DAVSD_TEST:BOOL='OFF' -DH264D_TEST:BOOL='OFF' -DH265D_TEST:BOOL='OFF' -DJPEGD_TEST:BOOL='OFF' \ -DMPI_DEC_TEST:BOOL='OFF' -DMPI_ENC_TEST:BOOL='OFF' -DMPI_RC2_TEST:BOOL='OFF' \ -DMPI_RC_TEST:BOOL='OFF' -DMPI_TEST:BOOL='OFF' -DMPP_BUFFER_TEST:BOOL='OFF' \ -DMPP_ENV_TEST:BOOL='OFF' -DMPP_INFO_TEST:BOOL='OFF' -DMPP_LOG_TEST:BOOL='OFF' \ -DMPP_MEM_TEST:BOOL='OFF' -DMPP_PACKET_TEST:BOOL='OFF' -DMPP_PLATFORM_TEST:BOOL='OFF' \ -DMPP_TASK_TEST:BOOL='OFF' -DMPP_THREAD_TEST:BOOL='OFF' -DVP9D_TEST:BOOL='OFF' \ -DVPU_API_TEST:BOOL='OFF' .. make -j$THREADS sudo make install ffmpeg build: ./configure --prefix=/usr --enable-gpl --enable-version3 --enable-nonfree --enable-static --enable-gmp \ --enable-gnutls --enable-libass --enable-libbluray --enable-libcdio --enable-libfdk-aac \ --enable-libfreetype --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 \ --enable-libxcb --enable-opencl --enable-libdrm --arch='armv8-a+crc+crypto' \ --cpu='cortex-a72.cortex-a53' --enable-rkmpp --enable-lto --enable-hardcoded-tables \ --disable-debug make -j$THREADS sudo make install sudo ldconfig error: sudo ffmpeg -benchmark -vcodec h264_rkmpp -i demo.mkv -f null - ffmpeg version 4.2 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 9.1.0 (GCC) configuration: --prefix=/usr --enable-gpl --enable-version3 --enable-nonfree --enable-static --enable-gmp --enable-gnutls --enable-libass --enable-libbluray --enable-libcdio --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxcb --enable-opencl --enable-libdrm --arch=armv8-a+crc+crypto --cpu=cortex-a72.cortex-a53 --enable-rkmpp --enable-lto --enable-hardcoded-tables --disable-debug libavutil 56. 31.100 / 56. 31.100 libavcodec 58. 54.100 / 58. 54.100 libavformat 58. 29.100 / 58. 29.100 libavdevice 58. 8.100 / 58. 8.100 libavfilter 7. 57.100 / 7. 57.100 libswscale 5. 5.100 / 5. 5.100 libswresample 3. 5.100 / 3. 5.100 libpostproc 55. 5.100 / 55. 5.100 Input #0, matroska,webm, from 'demo.mkv': Metadata: COMPATIBLE_BRANDS: iso6avc1mp41 MAJOR_BRAND : dash MINOR_VERSION : 0 ENCODER : Lavf58.29.100 Duration: 00:05:13.80, start: -0.007000, bitrate: 2887 kb/s Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 1k tbn, 59.94 tbc (default) Metadata: HANDLER_NAME : ISO Media file produced by Google Inc. DURATION : 00:05:13.780000000 Stream #0:1(eng): Audio: opus, 48000 Hz, stereo, fltp (default) Metadata: DURATION : 00:05:13.801000000 mpi: mpp version: hal_h264d_api: Assertion vcodec_type & ((0x00000200) | (0x00000001) | (0x00000002)) failed at hal_h264d_init:119 hal_h264d_api: hal_h264d_init hard mode error, value=0 hal_h264d_api: Assertion 0 failed at hal_h264d_init:169 mpp_device: mpp_device_init failed to find device for coding 0 type 7 hal_h264d_api: p_hal->vpu_socket <= 0 mpp_hal: mpp_hal_init hal h264d_rkdec init failed ret -2 mpp_hal: mpp_hal_init could not found coding type 7 mpp_dec: mpp_dec_init could not init hal mpp_rt: NOT found ion allocator mpp_rt: found drm allocator mpp: error found on mpp initialization mpp: WARNING: setup buffer group before decoder init mpp: command 310002 param 0xaaab0831a360 ret -1 [h264_rkmpp @ 0xaaab0833b720] Failed to assign buffer group (code = -1) [h264_rkmpp @ 0xaaab0833b720] Failed to initialize RKMPP decoder. Stream mapping: Stream #0:0 -> #0:0 (h264 (h264_rkmpp) -> wrapped_avframe (native)) Stream #0:1 -> #0:1 (opus (native) -> pcm_s16le (native)) Error while opening decoder for input stream #0:0 : Unknown error occurred bench: maxrss=23880kB
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines