| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,697
» Latest member: john9
» Forum threads: 16,260
» Forum posts: 117,187
Full Statistics
|
| Latest Threads |
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: brorean
Yesterday, 08:45 PM
» Replies: 1
» Views: 102
|
Hi everybody!
Forum: General
Last Post: MadisynErnser
11-20-2025, 10:03 PM
» Replies: 2
» Views: 2,255
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 79
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 565
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 148
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 469
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,142
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 89
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 94
|
Second screen mirroring
Forum: General
Last Post: andrekyler
11-17-2025, 01:06 AM
» Replies: 3
» Views: 1,912
|
|
|
| Privacy of Android and Chromium on new PineBook |
|
Posted by: Clea - 10-10-2019, 11:21 AM - Forum: Android on Pinebook
- Replies (3)
|
 |
Hi
I read that "Chromium OS and Android 9 are also available as an option" for PineBook. I wish to buy one.
Are these builds of Android and Chromium for PineBook without spyware from Google? Something like LinageOS/F-Droid? Can you please write a few details about the privacy of those builds?
I have no Google account but wish to use/test Android and Chromium. I cant use pure Debian because my toddler too young for Debian.
|
|
|
|
| Problem transferring rootfs to HDD |
|
Posted by: alexvs - 10-09-2019, 08:38 AM - Forum: Linux on RockPro64
- Replies (1)
|
 |
Hello.
I am using the stretch-openmediavault-rockpro64-0.9.14-1159-armhf.img image
I used instruction to port rootfs to hdd.
The transfer of rootfs to hdd is successful, after which the system boots up, but openmediavault no longer works.
For transfer I used the rsync -ax / / mnt / command. Probably it is necessary to use something else?
|
|
|
|
| Pine Phone Specs |
|
Posted by: bcnaz - 10-08-2019, 05:32 PM - Forum: General
- Replies (2)
|
 |
***
> What kind of 'SD card' can be used in the Pine Phone
Mini-SD Class 10 ???
> or what is recommended ?
> The main drive will be EMMc ?
Thanks
|
|
|
|
| RockPro64 Fan Pins |
|
Posted by: TheUnknownMuncher - 10-08-2019, 10:37 AM - Forum: General Discussion on ROCKPRO64
- Replies (7)
|
 |
Hello,
I have a RockRro64 in the NAS case, with the NAS case fan. I love it and it works fantastically, but I've decided to replace the included fan because it is quite loud (can hear it from an entire room away when it is set to max speed). I've already ordered an 80mm 4-pin 12V PWM fan and just now remembered that the fan pins on the RockPro64 are not standard size as a desktop PC. Can someone point me to an adapter so that I may use my fan? If an adapter does not exist, then it would be possible for me to snip the connector from the existing fan and solder that onto the cabling from the fan that I have ordered, but I'd rather not go with the solution if there is another way. Also will it be a problem that my fan is 4-pin PWM or will that still work fully? I see that the fan header on RockPro64 is 2-pin PWM, but by my understanding PWM is not possible with 2 pins, so this confuses me? I'm more concerned about being able to run the fan at full speed rather than controlling fan speed, but it would be nice to have speed control.
A follow-up question, I see in the Wiki for the NAS case that it is recommended to use the fan as exhaust, rather than intake, for negative pressure. Has anyone tried using for intake? Seems strange to me to pull hot air from the CPU across the hard drives, rather than push cool air from outside the case across the drives and then CPU. I've also thought that generally, positive pressure is more advantageous than negative pressure.
Thanks
|
|
|
|
| Linux Build Help: Stuck at "Starting kernel ..." |
|
Posted by: ihamilton - 10-07-2019, 12:41 PM - Forum: Linux on RockPro64
- Replies (2)
|
 |
I'm trying to build a kernel image for Rockpro64.
I have U-Boot 2019 built and working from https://gitlab.denx.de/u-boot.git.
I have tested a prebuilt debian image on the board and run through some simple tests and the hardware all seems to work.
In U-Boot, I can read/write from both SD card and eMMC module fine. I am wondering about the process to load the kernel image and DTB into memory for booting. I am using a ext4 partition for the file system that is already extracted out.
I have tested with a FAT partition and the ext4 partition and both can load the kernel image (Image) and DTB (rk3399-rockpro64.dtb) but when using booti in U-Boot it hangs at "Starting kernel...".
I am using the following U-Boot commands:
Code: setenv bootargs 'console=ttyS2,1500000n8 rw rootwait root=/dev/mmcblk1p1 rootfstype=ext4 earlycon=uart8250,mmio32,0xff1a0000'
ext4load mmc 1 0x02080000 boot/Image
ext4load mmc 1 0x01f00000 boot/dtbs/rockchip/rk3399-rockpro64.dtb
booti 0x02080000 - 0x01f00000
The output from this is:
Code: => booti 0x02080000 - 0x01f00000
## Flattened Device Tree blob at 0x1f00000
Booting using fdt blob at 0x1f00000
Host not halted after 16000 microseconds.
ERROR: reserving fdt memory region failed (addr=0 size=0)
Loading Device Tree to 000000007df0c000, end 000000007df26810 ... OK
Starting kernel ...
I chose those memory locations as that was the default found in the U-Boot parameters with printenv. I would prefer not to dd the kernel image and rootfs.img to the SD card directly and would rather have them in the /boot directory and load them in U-Boot on the go as this is the method I would like to use on the eMMC as well.
I am trying kernel builds from:
https://github.com/ayufan-rock64/linux-kernel.git
https://github.com/ayufan-rock64/linux-m...kernel.git
It seems to me that the address location I am choosing could be wrong or the device tree is not loading properly but I am lost at the moment. I am still somewhat new to this so any help would be greatly appreciated. Thanks.
|
|
|
|
| Is there another link for Android images? |
|
Posted by: Maalth - 10-07-2019, 04:49 AM - Forum: Android on Pine A64(+)
- Replies (3)
|
 |
I ask this because ayufan's page doesn't load at all due to error messages. The Pine's Android 6.0 build has the corrupt SD card issue. I'm aware the problem has been fixed, but I'm unable to access Ayufan's latest images due to his website issues. Tried two different machines including my ipad and the webpage issues are persistent.
|
|
|
|
[SOLVED] Alpine Linux won't boot |
|
Posted by: rock7 - 10-06-2019, 07:57 PM - Forum: Linux on Rock64
- Replies (1)
|
 |
It should work, according to this thread:
https://forum.pine64.org/showthread.php?tid=5881
I have done the following instructions:
https://wiki.alpinelinux.org/wiki/DIY_Fu...r_ARM_SOCs
https://github.com/ayufan-rock64/linux-b...ash-spi.md
With the help of the following websites:
https://forum.pine64.org/showthread.php?tid=4928
https://a-delacruz.github.io/alpine/alpine-linux.html
U-Boot is now on the SPI memory of the Rock64
Then I tried to boot Alpine Linux from a USB stick:
Quote:Result 1:
Quote:With USB stick and this extlinux.conf:
LABEL Linux 5.3.0
LINUX /boot/vmlinuz-5.3.0
INITRD /boot/initramfs-neu
FDT /boot/dtbs/rk3328-rock64.dtb
APPEND BOOT_IMAGE=/boot/vmlinuz-5.3.0 modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-neu console=${console}
Serial Console output:
U-Boot SPL 2017.09-rockchip-ayufan-1063-g29843fbd42 (Jul 08 2019 - 11:55:08)
board_init_sdmmc_pwr_en
setup_ddr_param 1
booted from SPI flash
Trying to boot from SPI
NOTICE: BL31: v1.3(debug):9d3f591
NOTICE: BL31: Built : 14:39:02, Jan 17 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE iniK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09-rockchip-ayufan-1063-g29843fbd42 (Jul 08 2019 - 11:55:26 +0000)
Model: Pine64 Rock64
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b50303930313500000000023119
serial=7223c9dfddbf101
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 10
Card did not respond to voltage select!
mmc_init: -95, time 9
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: Core Release: 3.10a
USB3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Device 0: Vendor: General Rev: 5.00 Prod: UDisk
Type: Removable Hard Disk
Capacity: 3840.0 MB = 3.7 GB (7864320 x 512)
... is now current device
Scanning usb 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
reading /boot/extlinux/extlinux.conf
233 bytes read in 26 ms (7.8 KiB/s)
1: Linux 5.3.0
Retrieving file: /boot/initramfs-neu
reading /boot/initramfs-neu
7170333 bytes read in 457 ms (15 MiB/s)
Retrieving file: /boot/vmlinuz-5.3.0
reading /boot/vmlinuz-5.3.0
31175168 bytes read in 1876 ms (15.8 MiB/s)
append: BOOT_IMAGE=/boot/vmlinuz-5.3.0 modules=loop,squashfs,sd-mod,usb-storage=
Retrieving file: /boot/dtbs/rk3328-rock64.dtb
reading /boot/dtbs/rk3328-rock64.dtb
36633 bytes read in 38 ms (941.4 KiB/s)
## Loading init Ramdisk from Legacy Image at 04000000 ...
Image Name: initramfs-sunxi
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 7170269 Bytes = 6.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to fc82b000, end fcf018dd ... OK
Loading Device Tree to 00000000fc81f000, end 00000000fc82af18 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.3.0-rc4-1117-ayufan-g01ec52ee6e2e (root@runner-f9
[ 0.000000] Machine model: Pine64 Rock64
[ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff130000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 16 MiB at 0x00000000fe000000
[ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff130000 (options '150000)
MORE IS NOT DISPLAYED, MORE DOES NOT WORK
Quote:Result 2:
Quote:With USB stick and this boot.scr:
setenv bootargs earlyprintk /boot/vmlinuz-5.3.0 modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-neu console=${console}
load mmc 0:1 0x43000000 boot/dtbs/rk3328-rock64.dtb
load mmc 0:1 0x41000000 boot/vmlinuz-5.3.0
load mmc 0:1 0x45000000 boot/initramfs-neu
booti 0x41000000 0x45000000 0x43000000
Serial Console output:
U-Boot SPL 2017.09-rockchip-ayufan-1063-g29843fbd42 (Jul 08 2019 - 11:55:08)
board_init_sdmmc_pwr_en
setup_ddr_param 1
booted from SPI flash
Trying to boot from SPI
NOTICE: BL31: v1.3(debug):9d3f591
NOTICE: BL31: Built : 14:39:02, Jan 17 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE iniK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09-rockchip-ayufan-1063-g29843fbd42 (Jul 08 2019 - 11:55:26 +0000)
Model: Pine64 Rock64
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b50303930313500000000023119
serial=7223c9dfddbf101
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 10
Card did not respond to voltage select!
mmc_init: -95, time 9
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: Core Release: 3.10a
USB3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Device 0: Vendor: General Rev: 5.00 Prod: UDisk
Type: Removable Hard Disk
Capacity: 3840.0 MB = 3.7 GB (7864320 x 512)
... is now current device
Scanning usb 0:1...
Found U-Boot script /boot/boot.scr
reading /boot/boot.scr
383 bytes read in 21 ms (17.6 KiB/s)
## Executing script at 00500000
Card did not respond to voltage select!
mmc_init: -95, time 9
"Synchronous Abort" handler, esr 0x96000210
ELR: fef6af14
LR: fef18fb8
x0 : 0000000000000000 x1 : 0000000000000001
x2 : 0000000000000010 x3 : 0000000000000000
x4 : 000000000000000a x5 : 00000000fef8585b
x6 : 0000000000000001 x7 : 0000000000000008
x8 : 0000000000000044 x9 : 0000000000000008
x10: 00000000fcf02d3e x11: 0000000000000006
x12: 000000000001869f x13: 0000000000000004
x14: 0000000000000004 x15: 00000000ffffffff
x16: 00000000cb5bab3b x17: 00000000800580a1
x18: 00000000fcf0ce08 x19: 0000000000000000
x20: 00000000fcf4f070 x21: 00000000fcf4f000
x22: 00000000fefb2000 x23: 00000000fcf4f020
x24: 0000000000000000 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000fcf4eaf0 x29: 00000000fcf032a0
Resetting CPU …
MORE IS NOT DISPLAYED, MORE DOES NOT WORK
Quote:Result 3:
Quote:With bootable card reader (with Micro-SD) and this boot.scr:
setenv bootargs earlyprintk /boot/vmlinuz-5.3.0 modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-neu console=${console}
load mmc 0:1 0x43000000 boot/dtbs/rk3328-rock64.dtb
load mmc 0:1 0x41000000 boot/vmlinuz-5.3.0
load mmc 0:1 0x45000000 boot/initramfs-neu
booti 0x41000000 0x45000000 0x43000000
Serial Console output:
U-Boot SPL 2017.09-rockchip-ayufan-1063-g29843fbd42 (Jul 08 2019 - 11:55:08)
board_init_sdmmc_pwr_en
setup_ddr_param 1
booted from SPI flash
Trying to boot from SPI
NOTICE: BL31: v1.3(debug):9d3f591
NOTICE: BL31: Built : 14:39:02, Jan 17 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE iniK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09-rockchip-ayufan-1063-g29843fbd42 (Jul 08 2019 - 11:55:26 +0000)
Model: Pine64 Rock64
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b50303930313500000000023119
serial=7223c9dfddbf101
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 9
Card did not respond to voltage select!
mmc_init: -95, time 10
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: Core Release: 3.10a
USB3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... Device NOT ready
Request Sense returned 02 3A 00
Device NOT ready
Request Sense returned 02 3A 00
2 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 2 Storage Device(s) found
Device 0: Vendor: Generic- Rev: 1.00 Prod: USB3.0 CRW -SD
Type: Removable Hard Disk
Capacity: not available
... is now current device
MORE IS NOT DISPLAYED, MORE DOES NOT WORK
My usb stick (newos) looks like this:
/media/ubuntu/newos
/media/ubuntu/newos/apks
/media/ubuntu/newos/apks/.boot_repository
/media/ubuntu/newos/apks/aarch64
/media/ubuntu/newos/apks/aarch64/kbd-bkeymaps-2.0.4-r3.apk
/media/ubuntu/newos/apks/aarch64/wireless-tools-30_pre9-r1.apk
/media/ubuntu/newos/apks/aarch64/openssl-1.1.1c-r0.apk
/media/ubuntu/newos/apks/aarch64/alpine-mirrors-3.5.10-r0.apk
/media/ubuntu/newos/apks/aarch64/busybox-1.30.1-r2.apk
/media/ubuntu/newos/apks/aarch64/ppp-pppoe-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/alpine-base-3.10.1-r0.apk
/media/ubuntu/newos/apks/aarch64/haveged-openrc-1.9.4-r4.apk
/media/ubuntu/newos/apks/aarch64/ncurses-libs-6.1_p20190518-r0.apk
/media/ubuntu/newos/apks/aarch64/openssh-server-8.0_p1-r0.apk
/media/ubuntu/newos/apks/aarch64/musl-1.1.22-r2.apk
/media/ubuntu/newos/apks/aarch64/ppp-daemon-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/ppp-atm-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/libnl3-3.4.0-r0.apk
/media/ubuntu/newos/apks/aarch64/vlan-2.2-r0.apk
/media/ubuntu/newos/apks/aarch64/libcom_err-1.45.2-r0.apk
/media/ubuntu/newos/apks/aarch64/network-extras-1.2-r0.apk
/media/ubuntu/newos/apks/aarch64/APKINDEX.tar.gz
/media/ubuntu/newos/apks/aarch64/openssh-8.0_p1-r0.apk
/media/ubuntu/newos/apks/aarch64/libssl1.1-1.1.1c-r0.apk
/media/ubuntu/newos/apks/aarch64/ppp-passwordfd-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/wpa_supplicant-openrc-2.8-r1.apk
/media/ubuntu/newos/apks/aarch64/pcsc-lite-libs-1.8.25-r1.apk
/media/ubuntu/newos/apks/aarch64/scanelf-1.2.3-r0.apk
/media/ubuntu/newos/apks/aarch64/openssh-server-common-8.0_p1-r0.apk
/media/ubuntu/newos/apks/aarch64/openssh-client-8.0_p1-r0.apk
/media/ubuntu/newos/apks/aarch64/ppp-winbind-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/zlib-1.2.11-r1.apk
/media/ubuntu/newos/apks/aarch64/openrc-0.41.2-r1.apk
/media/ubuntu/newos/apks/aarch64/e2fsprogs-1.45.2-r0.apk
/media/ubuntu/newos/apks/aarch64/alpine-baselayout-3.1.2-r0.apk
/media/ubuntu/newos/apks/aarch64/libcap-2.27-r0.apk
/media/ubuntu/newos/apks/aarch64/ssl_client-1.30.1-r2.apk
/media/ubuntu/newos/apks/aarch64/chrony-3.5-r0.apk
/media/ubuntu/newos/apks/aarch64/ppp-passprompt-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/libedit-20190324.3.1-r0.apk
/media/ubuntu/newos/apks/aarch64/bonding-2.6-r4.apk
/media/ubuntu/newos/apks/aarch64/alpine-keys-2.1-r2.apk
/media/ubuntu/newos/apks/aarch64/libuuid-2.33.2-r0.apk
/media/ubuntu/newos/apks/aarch64/libtls-standalone-2.9.1-r0.apk
/media/ubuntu/newos/apks/aarch64/dbus-libs-1.12.16-r0.apk
/media/ubuntu/newos/apks/aarch64/ppp-l2tp-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/bridge-1.5-r4.apk
/media/ubuntu/newos/apks/aarch64/libcrypto1.1-1.1.1c-r0.apk
/media/ubuntu/newos/apks/aarch64/ncurses-terminfo-base-6.1_p20190518-r0.apk
/media/ubuntu/newos/apks/aarch64/ca-certificates-cacert-20190108-r0.apk
/media/ubuntu/newos/apks/aarch64/alpine-conf-3.8.3-r0.apk
/media/ubuntu/newos/apks/aarch64/ppp-chat-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/wpa_supplicant-2.8-r1.apk
/media/ubuntu/newos/apks/aarch64/busybox-suid-1.30.1-r2.apk
/media/ubuntu/newos/apks/aarch64/tzdata-2019a-r0.apk
/media/ubuntu/newos/apks/aarch64/musl-utils-1.1.22-r2.apk
/media/ubuntu/newos/apks/aarch64/usb-modeswitch-2.5.2-r0.apk
/media/ubuntu/newos/apks/aarch64/ncurses-terminfo-6.1_p20190518-r0.apk
/media/ubuntu/newos/apks/aarch64/libusb-1.0.22-r0.apk
/media/ubuntu/newos/apks/aarch64/openssh-keygen-8.0_p1-r0.apk
/media/ubuntu/newos/apks/aarch64/e2fsprogs-libs-1.45.2-r0.apk
/media/ubuntu/newos/apks/aarch64/apk-tools-2.10.4-r2.apk
/media/ubuntu/newos/apks/aarch64/ppp-radius-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/libc-utils-0.7.1-r0.apk
/media/ubuntu/newos/apks/aarch64/chrony-openrc-3.5-r0.apk
/media/ubuntu/newos/apks/aarch64/busybox-initscripts-3.1-r7.apk
/media/ubuntu/newos/apks/aarch64/haveged-1.9.4-r4.apk
/media/ubuntu/newos/apks/aarch64/ppp-minconn-2.4.7-r6.apk
/media/ubuntu/newos/apks/aarch64/libblkid-2.33.2-r0.apk
/media/ubuntu/newos/apks/aarch64/openssh-sftp-server-8.0_p1-r0.apk
/media/ubuntu/newos/boot
/media/ubuntu/newos/boot/vmlinuz-5.3.0
/media/ubuntu/newos/boot/config-5.3.0
/media/ubuntu/newos/boot/System.map-5.3.0
/media/ubuntu/newos/boot/initramfs-neu
/media/ubuntu/newos/boot/modloop-neu
/media/ubuntu/newos/boot/extlinux
/media/ubuntu/newos/boot/extlinux/extlinux.conf
/media/ubuntu/newos/boot/dtbs
/media/ubuntu/newos/boot/dtbs/rk3328-rock64.dtb
/media/ubuntu/newos/boot/boot.scr
/media/ubuntu/newos/alpine.apkovl.tar.gz
Thanks in advance for your help!
|
|
|
|
| Development Environment on the Pinebook Pro |
|
Posted by: mynameiscalvin - 10-05-2019, 07:25 PM - Forum: Linux on Pinebook Pro
- Replies (46)
|
 |
Hi, I wanted to set up my development environment today, my favorite editor is Atom and that's why I wanted to build it for ARM. Before, I had read that it should be quite easy on the Raspberry Pi, but I had a lot of problems. So far, I have not gotten Atom to build. Does anyone have experience or even a deb package? If I manage to build it and you are interested, I would share my deb package. Do you have cool editors which would be an alternative to Atom and are already compiled for ARM?
|
|
|
|
|