Search the Community
Showing results for 'pinebook' in topics.
-
Description Debian sid desktops have been failing to build for a while due to a dependency issue with ghostscript-x this package has been abandoned... or mostly abandoned.. see Debian Bug #1022718 Removed package from base desktop package lists... Resolves error message below The following packages have unmet dependencies: ghostscript-x : Depends: ghostscript (= 10.01.2~dfsg-1) but 10.02.1~dfsg-1 is to be installed E: Unable to correct problems, you have held broken packages. tested with ./compile.sh build BOARD=pinebook-pro BRANCH=edge BUILD_DESKTOP=yes \ DESKTOP_APPGROUPS_SELECTED='3dsupport browsers internet multimedia' DESKTOP_ENVIRONMENT=cinnamon \ DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=sid View the full article -
hi, make sure you have all the kernel modules in your initramfs as listed here: https://github.com/NixOS/nixos-hardware/blob/master/pine64/pinebook-pro/default.nix i had the same issue with my archilnux installation until i included all of them
-
I found a way to boot after having deleted the U-boot partition, which prevents any useful boot to allow repair. I could then complete the armbian install. This applies to my Pinebook A64, 14" (not the pro pinebook - i cant test that) After removing the U-boot partition, it would only boot to a "busybox" with limited features, not enough to do a repair. I had a copy of armbian jammy on an sd-card, and this had booted OK before my stupid error. But with the SD card inserted, it stilll only booted to the busybox . The trick was to start the boot, and then insert the SD-card mid-boot, and it then booted the working system from the SD-card. During the defective boot, there is a pause with a few lines of text on the screen before it then proceeds with more error messages and into the busybox. I inserted the SD-card during that pause and it completed the boot from the SD-card. (you may need to time this carefully, but it worked on first try for me) Then you have a complete working system and can use armbian-config, > install system to eMMC and it copies the system to the eMMC and fixes the u-boot issue. It will now boot direct from the eMMC. Took me a while to find this trick which I have not seen documented anywhere, but is essential to get a system running to effect a repair.
-
> Hardware support > Debian 11 comes with Mesa 20.3 which supports the Mali 400 and 450 GPUs via the Lima driver, and various Mali G-series and T-series GPUs via the Panfrost driver. This will cover most modern ARM SoCs, including those found in the Pinebook and Pinebook Pro devices. Panfrost supports the Mali T720 (only up to OpenGL 2.1 and OpenGL ES 2.0), Mali T760, Mali T820, Mali T860, Mali G72, Mali G31, and Mali G52. PanfrostLima - Debian Wiki https://wiki.debian.org/PanfrostLima Can I just switch to Armbian Debian 11 and install Panfrost driver to enable GPU on nano pi r4s?
-
Description This brings early support for Linux kernel v6.5 for allwinner boards. Following patches are changed Megous patches: disabled patches.megous/video-fbdev-eInk-display-driver-for-A13-based-PocketBooks.patch to prevent build failure. Will work on re-enabling the same Fixes patches: disabled Fix-depends-only-ARM-eInk-display-FB.patch as it changes code introduce by patch disabled above Armbian patches: disabled drv-clk-sunxi-ng-ccu-sun50i-a64-revert-ccu-Pinebook-A64.patch due to patch application failure. Will check if its still needed. Need help from someone who has a PInebook A64 for the same. removed drv-pmic-add-axp313a.patch as it is upstreamed reworked the overlay support patches to reuse the upstream dtbo support. Due to this rework, overlay patches are updated to use dtso as the file extension Config change: Enabled CW1200 wireless driver as this might bring support for xradio xr819 due to patches from megous kernel How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Build succeeds Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
