+- PINE64 (https://forum.pine64.org)
+-- Forum: PINE A64(+) (https://forum.pine64.org/forumdisplay.php?fid=4)
+--- Forum: Linux on Pine A64(+) (https://forum.pine64.org/forumdisplay.php?fid=6)
+--- Thread: Minimal 64bit ARM RootFS for Debian and Ubuntu (/showthread.php?tid=87)
Minimal 64bit ARM RootFS for Debian and Ubuntu - umiddelb - 01-03-2016
Hi,
I've prepared two tar archives containing a minimal 64bit ARM root filesystem for Debian Jessie (login: debian, passwd: 111111) and Ubuntu Trusty (login ubuntu, passwd: 111111). You can find the scripts for creating the root filesystems and some additional information about the tar archives here. Once the kernel image / modules and the boot loader are available for the PINE64, I'll try to build a complete image.
Cheers
Uli
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - Debcool - 01-23-2016
Salut,
Very kind of you. Can't wait to get the device in my hands
A+
Debcool
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - tllim - 01-23-2016
(01-03-2016, 01:58 AM)umiddelb Wrote: Hi,
I've prepared two tar archives containing a minimal 64bit ARM root filesystem for Debian Jessie (login: debian, passwd: 111111) and Ubuntu Trusty (login ubuntu, passwd: 111111). You can find the scripts for creating the root filesystems and some additional information about the tar archives here. Once the kernel image / modules and the boot loader are available for the PINE64, I'll try to build a complete image.
Cheers
Uli
Cool and thanks :-)
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - umiddelb - 02-12-2016
The Archlinux ARM community provided generic rootfs for arm64 runs on the pine64 as well.
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - tllim - 02-12-2016
(02-12-2016, 05:32 PM)umiddelb Wrote: The Archlinux ARM community provided generic rootfs for arm64 runs on the pine64 as well.
This porting already going on by Sunxi and hopefully release on this week. Stays tune.
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - umiddelb - 02-13-2016
(02-12-2016, 05:32 PM)umiddelb Wrote: The Archlinux ARM community provided generic rootfs for arm64 runs on the pine64 as well.
And it evens runs Docker ...
Code:
[root@alarm docker]# docker info
DEBU[2641] Calling GET /v1.22/info
DEBU[2641] GET /v1.22/info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 1.10.1
Storage Driver: overlay
Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: null host bridge
Kernel Version: 4.5.0-rc1+
Operating System: Arch Linux ARM
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 780.2 MiB
Name: alarm
ID: W3UG:DDAD:5PSR:FECO:X7CN:QCR5:EBAH:RA76:6JOJ:IVI3:MMQW:LCWN
Debug mode (server): true
File Descriptors: 14
Goroutines: 27
System Time: 2016-02-05T17:00:08.85349Z
EventsListeners: 0
Init SHA1: 14d42f7cde8f432216a470821fd5fffb5cfa549b
Init Path: /usr/lib/docker/dockerinit
Docker Root Dir: /var/lib/dockerRE: Minimal 64bit ARM RootFS for Debian and Ubuntu - patrickhwood - 02-13-2016
Nice. I assume this is with the 4.4.0 kernel?
I tried to boot this with the android kernel, but it doesn't want to start a getty on ttyS0. I haven't worked with systemd before (one of the reasons I'm dreading the upcoming ubuntu LTS release), but I followed the instructions on the Archlinux site to enable it and set the right baud rate. I get a message that it's attempting to start the getty, but no login prompt:
[ *** ] A start job is running for dev-ttyS0.device (15s / 1min 30s)
Eventually, it times out:
[ TIME ] Timed out waiting for device dev-ttyS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyS0.
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - umiddelb - 02-13-2016
(02-13-2016, 11:45 AM)patrickhwood Wrote: Nice. I assume this is with the 4.4.0 kernel?
I tried to boot this with the android kernel, but it doesn't want to start a getty on ttyS0. I haven't worked with systemd before (one of the reasons I'm dreading the upcoming ubuntu LTS release), but I followed the instructions on the Archlinux site to enable it and set the right baud rate. I get a message that it's attempting to start the getty, but no login prompt:
[ *** ] A start job is running for dev-ttyS0.device (15s / 1min 30s)
Eventually, it times out:
[ TIME ] Timed out waiting for device dev-ttyS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyS0.
I use this base image and added Arch on an additional partition. This base image comes with the 4.4 kernel. I've updated the kernel to 4.5 but kept the 4.4 dtb. To activate the serial console on Arch, I've simply added
Code:
c0:2345:respawn:/sbin/agetty 115200 ttyS0 linuxFor Ubuntu, please add
Code:
T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100How did you build the android kernel?
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - patrickhwood - 02-13-2016
Are you using the latest aarch64 rootfs? SysV init isn't supported out of the box in that -- systemd is the default init system. Also, ubuntu hasn't used /etc/inittab for quite a while. i enabled getty on ttyS0 with this script in /etc/init/ttyS0.conf:
start on runlevel [2345]
respawn
script
exec /sbin/getty -8 -a root 115200 ttyS0
end script
RE: Minimal 64bit ARM RootFS for Debian and Ubuntu - patrickhwood - 02-13-2016
(02-13-2016, 05:12 PM)umiddelb Wrote: How did you build the android kernel?
I didn't build it; I pulled the android boot image from partition 6 and used abootimg to replace the ramdisk with one containing busybox and this in /init:
Code:
#!/bin/sh +x
# mount local virtual fs
mount -t proc proc /proc
mount -t devtmpfs dev /dev
mount /dev/mmcblk0p1 /root
# mount /dev in new rootfs, cause we'll need one
mount -t devtmpfs dev /root/dev
exec chroot /root /sbin/initI supposed I could have modified uboot's environment or script.bin to change the root= setting in the kernel's args, but that would have entailed mucking around with allwinner's uboot, and I'd prefer to spend my time elsewhere.