Alpine Linux - User contributions [en]

Odroid-C2

2025-12-21T14:18:32Z

Yuu: Added dmesg and /etc/os-release

==Introduction==

The Odroid-C2 single board computer is now well supported by Alpine/Linux and the "Generic U-Boot (aarch64)" build contains everything we need !

What about the hardware side ?
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* Debug only : USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Prepare the micro-SD card==
With a blank SD card, we can now format-it using the vfat file system.

'''WARNING''' : DOUBLE-CHECK <code>/dev/sda1</code> is indeed your SD card ! Or you'll loose all your data ! You have been warned !
For this, it's preferable to run <code>dmesg -We</code> to check for the name, for example:
<pre>
[ +0,004725] ums-realtek 1-1:1.0: USB Mass Storage device detected
[ +0,002985] scsi host0: usb-storage 1-1:1.0
[ +1,020024] scsi 0:0:0:0: Direct-Access Generic- SD/MMC/MS PRO 1.00 PQ: 0 ANSI: 4
[ +0,000591] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ +1,314707] sd 0:0:0:0: [sda] 15269888 512-byte logical blocks: (7.82 GB/7.28 GiB)
[ +0,000352] sd 0:0:0:0: [sda] Write Protect is off
[ +0,000008] sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00
[ +0,000408] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ +0,062938] sda: sda1
[ +0,000238] sd 0:0:0:0: [sda] Attached SCSI removable disk
</pre>
And also verify with <code>fdisk -l</code>
<pre>
Disk /dev/sda: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Disk model: SD/MMC/MS PRO
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 15269887 15267840 7.3G b W95 FAT32
</pre>

Now we are sure that <code>/dev/sda</code> is really our SD card device and we can format our SD card using <code>mkfs.vfat /dev/sda1</code>

==Extract Alpine Linux==
Then mount and extract the Alpine Linux archive, for example if you do everything as root:
<pre>
mount /dev/sda1 /mnt/sd
tar xvzfp /home/user/Downloads/alpine-uboot-3.23.2-aarch64.tar.gz -C /mnt/sd
</pre>

Then, don't forget to flush changes before unmounting the device. Note that it can be a little slow depending of the speed of your device.
<pre>
sync && umount /mnt/sd
</pre>

==Sign u-boot==
We don't need to build u-boot from source as the version provided does autoboot properly:
<pre>git clone --depth 1 https://github.com/LibreELEC/amlogic-boot-fip.git</pre>

Copy the u-boot.bin from your sd card to the git repository, and sign Amlogic u-boot binaries:
<pre>
cd amlogic-boot-fip/
/mnt/sd/u-boot/odroid-c2/u-boot.bin alpine.u-boot.bin
./build-fip.sh odroid-c2 alpine.u-boot.bin my-output-dir
</pre>

==u-boot flashing==
'''WARNING''' : Make sure your device is <code>/dev/sda</code> !
Also, check that the device is un-mouted using <code>umount /dev/sda1</code>, then use dd to write u-boot
For example, using /dev/sda from previous commands and the signed u-boot (u-boot.bin.sd.bin) from amlogic-boot-fip tool.
<pre>
dd if=./amlogic-boot-fip/my-output-dir/u-boot.bin.sd.bin of=/dev/sda conv=fsync,notrunc bs=512 skip=1 seek=1
dd if=./amlogic-boot-fip/my-output-dir/u-boot.bin.sd.bin of=/dev/sda conv=fsync,notrunc bs=1 count=444
</pre>

==Booting==
Connect at least your USB keyboard and your HDMI monitor to check the boot and all should work nicely :)
If not, check the Debugging part of this wiki.

==Debugging==
Connect your USB to TTL converter on your board : I noticed that you don't need to connect all wires, pin 1 don't seems to be is not mandatory at all.
<pre>
_____UART____
|Pin 4 - GND|
|Pin 3 - RXD|
|Pin 2 - TXD|
|Pin 1 - VCC|
\___________|
</pre>

All details are available on the odroid wiki : https://wiki.odroid.com/accessory/development/usb_uart_kit

I use minicom for this:
<pre>
TERM=linux minicom -b 115200 -D /dev/ttyUSB0
</pre>

==Boot log==
<pre>
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 6.18.1-0-lts (buildozer@build-3-23-aarch64) (cc (Alpine 15.2.0) 15.2.0, GNU ld (GNU Binutils) 2.45.1) #1-Alpine SMP PREEMPT_DYNAMIC 2025-12-15 07:25:33
[ 0.000000] Machine model: Hardkernel ODROID-C2
[ 0.000000] efi: EFI v2.11 by Das U-Boot
[ 0.000000] efi: RTPROP=0x7af1c040 SMBIOS 3.0=0x7bf74000 INITRD=0x7aefd040 RNG=0x7aefc040 MEMRESERVE=0x7aefb040
[ 0.000000] random: crng init done
[ 0.000000] Reserved memory: created CMA memory pool at 0x000000005d000000, size 256 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] OF: reserved mem: 0x000000005d000000..0x000000006cffffff (262144 KiB) map reusable linux,cma
[ 0.000000] OF: reserved mem: 0x0000000000000000..0x0000000000ffffff (16384 KiB) nomap non-reusable hwrom@0
[ 0.000000] OF: reserved mem: 0x0000000010000000..0x00000000101fffff (2048 KiB) nomap non-reusable secmon@10000000
[ 0.000000] OF: reserved mem: 0x0000000005000000..0x00000000052fffff (3072 KiB) nomap non-reusable secmon@5000000
[ 0.000000] OF: reserved mem: 0x0000000005300000..0x00000000072fffff (32768 KiB) nomap non-reusable secmon@5300000
[ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x7f83e040-0x7f8505ff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000000ffffff]
[ 0.000000] node 0: [mem 0x0000000001000000-0x0000000004ffffff]
[ 0.000000] node 0: [mem 0x0000000005000000-0x00000000072fffff]
[ 0.000000] node 0: [mem 0x0000000007300000-0x000000000fffffff]
[ 0.000000] node 0: [mem 0x0000000010000000-0x00000000101fffff]
[ 0.000000] node 0: [mem 0x0000000010200000-0x000000007abfffff]
[ 0.000000] node 0: [mem 0x000000007ac00000-0x000000007ac00fff]
[ 0.000000] node 0: [mem 0x000000007ac01000-0x000000007af1bfff]
[ 0.000000] node 0: [mem 0x000000007af1c000-0x000000007af1cfff]
[ 0.000000] node 0: [mem 0x000000007af1d000-0x000000007af1dfff]
[ 0.000000] node 0: [mem 0x000000007af1e000-0x000000007af3ffff]
[ 0.000000] node 0: [mem 0x000000007af40000-0x000000007bf73fff]
[ 0.000000] node 0: [mem 0x000000007bf74000-0x000000007bf74fff]
[ 0.000000] node 0: [mem 0x000000007bf75000-0x000000007df4ffff]
[ 0.000000] node 0: [mem 0x000000007df50000-0x000000007df5ffff]
[ 0.000000] node 0: [mem 0x000000007df60000-0x000000007fe5afff]
[ 0.000000] node 0: [mem 0x000000007fe5b000-0x000000007fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv0.2 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] percpu: Embedded 34 pages/cpu s100952 r8192 d30120 u139264
[ 0.000000] pcpu-alloc: s100952 r8192 d30120 u139264 alloc=34*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: ARM erratum 843419
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-lts modules=loop,squashfs,sd-mod,usb-storage quiet
[ 0.000000] Unknown kernel command line parameters "modules=loop,squashfs,sd-mod,usb-storage", will be passed to user space.
[ 0.000000] printk: log buffer data + meta data: 131072 + 458752 = 589824 bytes
[ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.000000] software IO TLB: SWIOTLB bounce buffer size adjusted to 2MB
[ 0.000000] software IO TLB: area num 4.
[ 0.000000] software IO TLB: mapped [mem 0x000000007f29f000-0x000000007f49f000] (2MB)
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 524288
[ 0.000000] Policy zone: DMA
[ 0.000000] mem auto-init: stack:all(zero), heap alloc:on, heap free:off
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] kmemleak: Kernel memory leak detector disabled
[ 0.000000] ftrace: allocating 45359 entries in 178 pages
[ 0.000000] ftrace: allocated 178 pages with 4 groups
[ 0.000000] Dynamic Preempt: voluntary
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=4.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[ 0.000000] RCU Tasks Rude: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[ 0.000000] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000800] kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[ 0.001028] Console: colour dummy device 80x25
[ 0.001040] printk: legacy console [tty0] enabled
[ 0.001209] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=24000)
[ 0.001223] pid_max: default: 32768 minimum: 301
[ 0.001379] LSM: initializing lsm=lockdown,capability,landlock,yama
[ 0.001551] landlock: Up and running.
[ 0.001556] Yama: becoming mindful.
[ 0.001675] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.001694] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.004293] rcu: Hierarchical SRCU implementation.
[ 0.004313] rcu: Max phase no-delay instances is 400.
[ 0.004552] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
[ 0.006137] Remapping and enabling EFI services.
[ 0.006487] smp: Bringing up secondary CPUs ...
[ 0.007630] Detected VIPT I-cache on CPU1
[ 0.007776] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.009079] Detected VIPT I-cache on CPU2
[ 0.009200] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.010412] Detected VIPT I-cache on CPU3
[ 0.010531] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.010662] smp: Brought up 1 node, 4 CPUs
[ 0.010676] SMP: Total of 4 processors activated.
[ 0.010681] CPU: All CPU(s) started at EL2
[ 0.010699] CPU features: detected: 32-bit EL0 Support
[ 0.010703] CPU features: detected: 32-bit EL1 Support
[ 0.010711] CPU features: detected: CRC32 instructions
[ 0.010721] CPU features: detected: PMUv3
[ 0.010765] alternatives: applying system-wide alternatives
[ 0.011888] Memory: 1527796K/2097152K available (15744K kernel code, 2970K rwdata, 12020K rodata, 3712K init, 3510K bss, 301136K reserved, 262144K cma-reserved)
[ 0.012919] devtmpfs: initialized
[ 0.019322] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[ 0.019382] posixtimers hash table entries: 2048 (order: 3, 32768 bytes, linear)
[ 0.019460] futex hash table entries: 1024 (65536 bytes on 1 NUMA nodes, total 64 KiB, linear).
[ 0.023417] 23216 pages in range for non-PLT usage
[ 0.023441] 514736 pages in range for PLT usage
[ 0.023773] pinctrl core: initialized pinctrl subsystem
[ 0.024728] SMBIOS 3.7.0 present.
[ 0.024746] DMI: Hardkernel Co., Ltd. ODROID-C2/ODROID-C2, BIOS 2025.10 10/01/2025
[ 0.024784] DMI: Memory slots populated: 0/0
[ 0.027296] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.029185] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[ 0.030098] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.031290] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.031356] audit: initializing netlink subsys (disabled)
[ 0.031614] audit: type=2000 audit(0.029:1): state=initialized audit_enabled=0 res=1
[ 0.032703] thermal_sys: Registered thermal governor 'fair_share'
[ 0.032710] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.032716] thermal_sys: Registered thermal governor 'step_wise'
[ 0.032721] thermal_sys: Registered thermal governor 'user_space'
[ 0.032781] cpuidle: using governor ladder
[ 0.032805] cpuidle: using governor menu
[ 0.032952] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.033051] ASID allocator initialised with 65536 entries
[ 0.033915] Serial: AMBA PL011 UART driver
[ 0.038430] /soc/interrupt-controller@c4301000: Fixed dependency cycle(s) with /soc/interrupt-controller@c4301000
[ 0.038607] /soc/vpu@d0100000: Fixed dependency cycle(s) with /soc/hdmi-tx@c883a000
[ 0.038630] /soc/hdmi-tx@c883a000: Fixed dependency cycle(s) with /soc/vpu@d0100000
[ 0.045891] /soc/vpu@d0100000: Fixed dependency cycle(s) with /soc/hdmi-tx@c883a000
[ 0.046143] /soc/vpu@d0100000: Fixed dependency cycle(s) with /soc/hdmi-tx@c883a000
[ 0.046205] /soc/hdmi-tx@c883a000: Fixed dependency cycle(s) with /soc/vpu@d0100000
[ 0.049641] /soc/hdmi-tx@c883a000: Fixed dependency cycle(s) with /hdmi-connector
[ 0.049721] /hdmi-connector: Fixed dependency cycle(s) with /soc/hdmi-tx@c883a000
[ 0.051188] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.051206] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.051213] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.051217] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.051223] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.051228] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.051234] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.051238] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.053003] ACPI: Interpreter disabled.
[ 0.053613] iommu: Default domain type: Translated
[ 0.053625] iommu: DMA domain TLB invalidation policy: lazy mode
[ 0.057233] pps_core: LinuxPPS API ver. 1 registered
[ 0.057254] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.057271] PTP clock support registered
[ 0.057622] EDAC MC: Ver: 3.0.0
[ 0.057896] scmi_core: SCMI protocol bus registered
[ 0.057957] efivars: Registered efivars operations
[ 0.059895] vgaarb: loaded
[ 0.060354] clocksource: Switched to clocksource arch_sys_counter
[ 0.061045] VFS: Disk quotas dquot_6.6.0
[ 0.061085] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.061557] pnp: PnP ACPI: disabled
[ 0.068400] NET: Registered PF_INET protocol family
[ 0.068648] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.108233] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[ 0.108372] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.108481] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.108718] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear)
[ 0.109068] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.109414] MPTCP token hash table entries: 2048 (order: 4, 49152 bytes, linear)
[ 0.109521] UDP hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.109600] UDP-Lite hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.109804] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.109844] NET: Registered PF_XDP protocol family
[ 0.109864] PCI: CLS 0 bytes, default 64
[ 0.110179] Trying to unpack rootfs image as initramfs...
[ 0.119795] kvm [1]: nv: 568 coarse grained trap handlers
[ 0.120337] kvm [1]: IPA Size Limit: 40 bits
[ 0.123491] kvm [1]: vgic interrupt IRQ9
[ 0.123540] kvm [1]: Hyp nVHE mode initialized successfully
[ 0.125490] Initialise system trusted keyrings
[ 0.125735] workingset: timestamp_bits=37 max_order=19 bucket_order=0
[ 0.126143] Key type asymmetric registered
[ 0.126155] Asymmetric key parser 'x509' registered
[ 0.126241] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[ 0.126464] io scheduler mq-deadline registered
[ 0.126476] io scheduler kyber registered
[ 0.126533] io scheduler bfq registered
[ 0.127930] irq_meson_gpio: 133 to 8 gpio interrupt mux initialized
[ 0.160777] soc soc0: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) Detected
[ 0.166402] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.170303] Serial: AMBA driver
[ 0.171277] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 14, base_baud = 1500000) is a meson_uart
[ 0.171332] printk: legacy console [ttyAML0] enabled
[ 0.185811] brd: module loaded
[ 0.190075] meson-sm: secure-monitor enabled
[ 0.192230] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 (0,8000003f) counters available
[ 0.194651] gre: GRE over IPv4 demultiplexer driver
[ 0.194813] NET: Registered PF_INET6 protocol family
[ 0.196113] Segment Routing with IPv6
[ 0.196163] In-situ OAM (IOAM) with IPv6
[ 0.196511] Key type dns_resolver registered
[ 0.207852] registered taskstats version 1
[ 0.208756] Loading compiled-in X.509 certificates
[ 1.890951] Freeing initrd memory: 161572K
[ 1.915766] Loaded X.509 cert 'alpinelinux.org: Alpine Linux kernel key: 87fa969a47f3e2a6aa35859eb932a17c95abcd82'
[ 1.925972] Demotion targets for Node 0: null
[ 1.926394] Key type .fscrypt registered
[ 1.926408] Key type fscrypt-provisioning registered
[ 1.990532] clk: Disabling unused clocks
[ 1.990750] PM: genpd: Disabling unused power domains
[ 1.997464] Freeing unused kernel memory: 3712K
[ 1.997642] Run /init as init process
[ 1.997651] with arguments:
[ 1.997657] /init
[ 1.997663] with environment:
[ 1.997668] HOME=/
[ 1.997673] TERM=linux
[ 1.997678] modules=loop,squashfs,sd-mod,usb-storage
[ 2.035274] Alpine Init 3.13.0-r0
[ 2.038758] Loading boot drivers...
[ 2.059104] loop: module loaded
[ 2.064737] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 2.080813] SCSI subsystem initialized
[ 2.103687] usbcore: registered new interface driver usbfs
[ 2.103764] usbcore: registered new interface driver hub
[ 2.103843] usbcore: registered new device driver usb
[ 2.111310] usbcore: registered new interface driver usb-storage
[ 2.180617] [drm] Initialized simpledrm 1.0.0 for 7fe5b000.framebuffer on minor 0
[ 2.183224] fbcon: Deferring console take-over
[ 2.183248] simple-framebuffer 7fe5b000.framebuffer: [drm] fb0: simpledrmdrmfb frame buffer device
[ 2.192025] Loading boot drivers: ok.
[ 2.198046] Mounting boot media...
[ 2.378869] meson-gx-mmc d0072000.mmc: Got CD GPIO
[ 2.456331] lima d00c0000.gpu: gp - mali450 version major 0 minor 0
[ 2.456438] lima d00c0000.gpu: pp0 - mali450 version major 0 minor 0
[ 2.456514] lima d00c0000.gpu: pp1 - mali450 version major 0 minor 0
[ 2.456584] lima d00c0000.gpu: pp2 - mali450 version major 0 minor 0
[ 2.456625] lima d00c0000.gpu: l2_cache0 8K, 4-way, 64byte cache line, 128bit external bus
[ 2.456639] lima d00c0000.gpu: l2_cache1 64K, 4-way, 64byte cache line, 128bit external bus
[ 2.457168] lima d00c0000.gpu: bus rate = 166666667
[ 2.457179] lima d00c0000.gpu: mod rate = 24000000
[ 2.457269] lima d00c0000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
[ 2.463630] lima d00c0000.gpu: devfreq_add_device: Unable to find governor for the device
[ 2.463824] lima d00c0000.gpu: Couldn't initialize GPU devfreq
[ 2.463832] lima d00c0000.gpu: Fatal error during devfreq init
[ 2.517377] lima d00c0000.gpu: probe with driver lima failed with error -22
[ 2.583042] mmc0: new high speed SDHC card at address 59b4
[ 2.603130] meson-drm d0100000.vpu: Queued 1 outputs on vpu
[ 2.650630] meson-drm d0100000.vpu: CVBS Output connector not available
[ 2.671777] meson-drm d0100000.vpu: Couldn't bind all components
[ 2.975512] meson-drm d0100000.vpu: CVBS Output connector not available
[ 2.996876] meson-drm d0100000.vpu: Couldn't bind all components
[ 3.001616] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq
[ 3.001665] meson-drm d0100000.vpu: CVBS Output connector not available
[ 3.023778] meson-drm d0100000.vpu: Couldn't bind all components
[ 3.030231] meson-drm d0100000.vpu: CVBS Output connector not available
[ 3.045224] mmc1: Failed to initialize a non-removable card
[ 3.051765] meson-drm d0100000.vpu: Couldn't bind all components
[ 3.061777] meson-drm d0100000.vpu: CVBS Output connector not available
[ 3.072815] mmcblk0: mmc0:59b4 USDU1 14.9 GiB
[ 3.075908] mmcblk0: p1
[ 3.083517] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 3.084214] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 3.084830] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops [meson_dw_hdmi])
[ 3.087221] [drm] Initialized meson 1.0.0 for d0100000.vpu on minor 0
[ 3.087571] meson-drm d0100000.vpu: [drm] Cannot find any crtc or sizes
[ 3.087876] meson-drm d0100000.vpu: [drm] Cannot find any crtc or sizes
[ 3.262226] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 3.335730] Mounting boot media: ok.
[ 3.341301] Loading user settings from /media/mmcblk0p1/c2.apkovl.tar.gz...
[ 3.377619] Loading user settings from /media/mmcblk0p1/c2.apkovl.tar.gz: ok.
[ 4.232143] Installing packages to root filesystem...
[ 5.557258] Installing packages to root filesystem: ok.
[ 13.281481] meson_ee_pwrc c883c000.system-controller:power-controller: sync_state() pending due to c9410000.ethernet
[ 18.229705] loop0: detected capacity change from 0 to 509712
[ 19.928765] stmmaceth c9410000.ethernet: IRQ eth_wake_irq not found
[ 19.928792] stmmaceth c9410000.ethernet: IRQ eth_lpi not found
[ 19.928800] stmmaceth c9410000.ethernet: IRQ sfty not found
[ 19.928909] stmmaceth c9410000.ethernet: PTP uses main clock
[ 19.929231] stmmaceth c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[ 19.929252] stmmaceth c9410000.ethernet: DWMAC1000
[ 19.929261] stmmaceth c9410000.ethernet: DMA HW capability register supported
[ 19.929268] stmmaceth c9410000.ethernet: RX Checksum Offload Engine supported
[ 19.929274] stmmaceth c9410000.ethernet: COE Type 2
[ 19.929281] stmmaceth c9410000.ethernet: TX Checksum insertion supported
[ 19.929288] stmmaceth c9410000.ethernet: Wake-Up On Lan supported
[ 19.929564] stmmaceth c9410000.ethernet: Normal descriptors
[ 19.929582] stmmaceth c9410000.ethernet: Ring mode enabled
[ 19.929589] stmmaceth c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 20.249379] Registered IR keymap rc-odroid
[ 20.263322] IR NEC protocol handler initialized
[ 20.284506] rc rc0: meson-ir as /devices/platform/soc/c8100000.bus/c8100580.ir/rc/rc0
[ 20.284665] input: meson-ir as /devices/platform/soc/c8100000.bus/c8100580.ir/rc/rc0/input0
[ 20.284847] rc rc0: sw decoder init
[ 20.284920] meson-ir c8100580.ir: receiver initialized
[ 20.308460] platform-mhu c883c404.mailbox: Platform MHU Mailbox registered
[ 20.452494] dwc2 c9100000.usb: supply vusb_d not found, using dummy regulator
[ 20.452658] dwc2 c9100000.usb: supply vusb_a not found, using dummy regulator
[ 20.504703] dwc2 c9100000.usb: DWC OTG Controller
[ 20.504745] dwc2 c9100000.usb: new USB bus registered, assigned bus number 1
[ 20.504787] dwc2 c9100000.usb: irq 43, io mem 0xc9100000
[ 20.504991] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.18
[ 20.505002] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 20.505010] usb usb1: Product: DWC OTG Controller
[ 20.505017] usb usb1: Manufacturer: Linux 6.18.1-0-lts dwc2_hsotg
[ 20.505024] usb usb1: SerialNumber: c9100000.usb
[ 20.505695] hub 1-0:1.0: USB hub found
[ 20.505742] hub 1-0:1.0: 1 port detected
[ 20.781387] usb 1-1: new high-speed USB device number 2 using dwc2
[ 20.956690] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
[ 20.956713] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 20.956721] usb 1-1: Product: USB2.0 Hub
[ 20.960535] hub 1-1:1.0: USB hub found
[ 20.960938] hub 1-1:1.0: 4 ports detected
[ 21.400017] NET: Registered PF_PACKET protocol family
[ 22.049733] stmmaceth c9410000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 22.126395] stmmaceth c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=38)
[ 22.141555] stmmaceth c9410000.ethernet eth0: No Safety Features support found
[ 22.159969] stmmaceth c9410000.ethernet eth0: PTP not supported by HW
[ 22.160000] stmmaceth c9410000.ethernet eth0: configuring for phy/rgmii link mode
[ 25.021598] stmmaceth c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 27.551668] fbcon: Taking over console
</pre>

<pre>
# cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.23.2
PRETTY_NAME="Alpine Linux v3.23"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
</pre>

[[Category:ARM]]
[[Category:Hardware]]

Odroid-C2

2025-12-21T14:07:54Z

Yuu:

Odroid-C2

2025-12-21T13:56:26Z

Yuu: Changed platform : generic arm to generic uboot

Odroid-C2

2025-12-21T10:21:50Z

Yuu: Alpine Linux now boot just fine for me :)

==Introduction==

The Odroid-C2 single board computer is now well supported by Alpine/Linux and the "Generic ARM (aarch64)" build contains everything we need !

What about the hardware side ?
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* Debug only : USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Prepare the micro-SD card==
With a blank SD card, we can now format-it using the vfat file system.

'''Warning''' : DOUBLE-CHECK /dev/sda1 is indeed your SD card ! Or you'll loose all your data ! You have been warned !
For this, it's preferable to run <pre>dmesg -We</pre> to check for the name, for example:
<pre>
[ +0,004725] ums-realtek 1-1:1.0: USB Mass Storage device detected
[ +0,002985] scsi host0: usb-storage 1-1:1.0
[ +1,020024] scsi 0:0:0:0: Direct-Access Generic- SD/MMC/MS PRO 1.00 PQ: 0 ANSI: 4
[ +0,000591] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ +1,314707] sd 0:0:0:0: [sda] 15269888 512-byte logical blocks: (7.82 GB/7.28 GiB)
[ +0,000352] sd 0:0:0:0: [sda] Write Protect is off
[ +0,000008] sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00
[ +0,000408] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ +0,062938] sda: sda1
[ +0,000238] sd 0:0:0:0: [sda] Attached SCSI removable disk
</pre>
And also verify with <pre>fdisk -l</pre>
<pre>
Disk /dev/sda: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Disk model: SD/MMC/MS PRO
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 15269887 15267840 7.3G b W95 FAT32
</pre>

Now we are sure that `/dev/sda` is really our SD card device and we can format our SD card:
<pre>mkfs.vfat /dev/sda1</pre>

==Extract Alpine Linux==
Then mount and extract the Alpine Linux archive, for example if you do everything as root:
<pre>
# mount /dev/sda1 /mnt/sd
# tar xvzfp /home/user/Downloads/alpine-uboot-3.23.2-aarch64.tar.gz -C /mnt/sd
</pre>

Then, don't forget to flush changes before unmounting the device. Note that it can be a little slow depending of the speed of your device.
<pre>
sync && umount /mnt/sd
</pre>

==Sign u-boot==
We don't need to build u-boot from source as the version provided does autoboot properly:
<pre>git clone --depth 1 https://github.com/LibreELEC/amlogic-boot-fip.git</pre>

Copy the u-boot.bin from your sd card to the git repository, and sign Amlogic u-boot binaries:
<pre>
cd amlogic-boot-fip/;
/mnt/sd/u-boot/odroid-c2/u-boot.bin alpine.u-boot.bin;
./build-fip.sh odroid-c2 alpine.u-boot.bin my-output-dir
</pre>

==u-boot flashing==
Now, make sure your device is un-mouted <pre>umount /dev/sda1</pre>, then use dd to write u-boot.
For example, using /dev/sda from previous commands and the signed u-boot (u-boot.bin.sd.bin) from amlogic-boot-fip tool.
<pre>
dd if=./amlogic-boot-fip/my-output-dir/u-boot.bin.sd.bin of=/dev/sda conv=fsync,notrunc bs=512 skip=1 seek=1
dd if=./amlogic-boot-fip/my-output-dir/u-boot.bin.sd.bin of=/dev/sda conv=fsync,notrunc bs=1 count=444
</pre>

==Booting==
Connect at least your USB keyboard and your HDMI monitor to check the boot and all should work nicely :)
If not, check the Debugging part of this wiki.

==Debugging==
Connect your USB to TTL converter on your board : I noticed that you don't need to connect all wires, pin 1 don't seems to be is not mandatory at all.
<pre>
_____UART____
|Pin 4 - GND|
|Pin 3 - RXD|
|Pin 2 - TXD|
|Pin 1 - VCC|
\___________|
</pre>

All details are available on the odroid wiki : https://wiki.odroid.com/accessory/development/usb_uart_kit

I use minicom for this:
<pre>
TERM=linux minicom -b 115200 -D /dev/ttyUSB0
</pre>

[[Category:ARM]]
[[Category:Hardware]]

Upgrading Alpine Linux to a new release branch

2022-08-16T20:20:05Z

Yuu: Update alpine version example

This page covers upgrading to newer releases.

Doing regular security updates with the package manager is shown at [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading a running system]].

{{Warning|Before actually upgrading your system, make sure that you have a backup of your important data.}}

== Upgrading an Alpine Linux Hard-disk installation ==

=== Upgrading from older versions ===

In case an older version needs to be upgraded, i.e. not just upgrading from the last release to the subsequent version as covered by the individual release notes, also check [[Upgrading from older versions]] for potential specifically required upgrade steps.

=== Upgrading to latest release ===

When Alpine Linux is installed in '''sys''' mode, e.g. on a hard drive, upgrading to the next stable version should be a straightforward package manager operation. However, for specific info always refer to the appropriate release notes.

{{:Include:Upgrading to latest release}}

=== Upgrading to Edge ===
{{:Include:Upgrading to Edge}}

== Upgrading Alpine Linux on CD ==

=== Boot media ===

If the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO.

If booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box.

=== Update local package installations ===

If you have locally installed and configured additional packages using [[How_to_enable_APK_caching|APK caching]] you should also perform the following steps.

Backup the local configuration prior to upgrading.
{{Cmd|lbu ci}}

{{:Include:Upgrading to latest release}}

After upgrading the packages, save the upgraded configuration changes.
{{Cmd|lbu ci}}

== Upgrading Alpine Linux on other removable media (such as CF/USB) ==

The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Updating your repositories using [[#Upgrading_an_Alpine_Linux_Hard-disk_installation|the procedures detailed above]], then running:
{{Cmd|apk upgrade --update-cache --available}}
will suffice for some purposes. (If you want the new packages to be used after a reboot, you should [[How_to_enable_APK_caching|enable APK caching]].)

However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). That is what the following steps describe how to do.

{{:Include:Upgrading_Alpine_environmentvars}}

=== Upgrade Operating System ===

Start by checking that you have enough space on your media. For a '''standard''' Alpine image, you need at least 400MB available space.
{{Cmd|df -h {{!}} grep "Filesystem\{{!}}$LBU_MEDIA"}}

==== Download and verify new release ====

Make sure the media that holds your Alpine system is mounted readwrite.
{{Cmd|mount -oremount,rw /media/$LBU_MEDIA}}

'''If using Alpine Linux 2.2.3 or newer''': Download the latest release, {{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/<arch>/<image>.iso}} and then use the following command to mount and copy files as needed for you: {{Cmd|setup-bootable -u alpine-extended-<version>-<arch>.iso /media/$LBU_MEDIA}} Once the command completes, proceed to the [[#Save changes|Save changes]] section.

==== For older versions of Alpine ====
Start downloading a new '.iso' and a '.sha1' file
{{Cmd|cd /media/$LBU_MEDIA
wget -c {{#latestalp:alpine|url}}
wget {{#latestalp:alpine|url}}.sha1}}

Check integrity of the downloaded files ''(it might take some time)'':
{{Cmd|sha1sum -c {{#latestalp:alpine|file}}.sha1}}
''The output of the above command should say 'OK'. ''
''If says 'FAILED', delete the iso file and download it again.''

'''If using Alpine Linux 1.10.4 or newer''': there is a tool ''setup-bootable'' that will mount and copy the image you just downloaded to your boot medium. With this tool simply do: {{Cmd|setup-bootable -u {{#latestalp:alpine|file}} /media/$LBU_MEDIA}}

[[Upgrading from older versions#Upgrading_a_removable_medium_from_Alpine_before_1.10.4|Instructions for older versions of Alpine]] are located elsewhere.

=== Save changes ===
Now that all upgrades are done, we should save our settings to our media (which you hopefully have backed up prior to doing this upgrade).
{{Cmd|lbu ci}}

=== Load new kernel ===
In most cases you will need to reboot Alpine Linux (especially if there are changes in the kernel):
{{Cmd|sync
reboot}}

{{Note|If you know what you are doing, you might not need to reboot. But make sure that all services affected by the upgrade are restarted.}}

=== Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) ===
On Alpine 3.X and newer, kernel is not upgraded when using <code>apk upgrade</code> and <code>setup-bootable</code> does not work properly.

If you want to upgrade your kernel, you will need to get it from the latest release, but first you must have and run :
{{Cmd|apk update; apk version -l '<';
apk upgrade;
lbu ci;}}

So now all your packages are upgraded, you can upgrade your kernel.

1. We need to get some variables :
{{Cmd|. /etc/os-release;
. /etc/lbu/lbu.conf;
ARCH=$(cat /etc/apk/arch);}}

2. You '''must''' verify if they are correctly set, using this :
{{Cmd|echo "alpine version : $VERSION_ID";
echo "lbu media : $LBU_MEDIA";
echo "arch : $ARCH"}}

3. And it will output something like this (if not, do not continue this process) :
{{Cmd|alpine version : 3.16.2
lbu media : mmcblk0p1
arch : armhf}}

4. Then you can run this script (WARNING : config.txt will be overwritten!) :
{{Cmd|cd /media/$LBU_MEDIA;
mount -oremount,rw /media/$LBU_MEDIA;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz</nowiki>;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256</nowiki>;
sha256sum -c *.sha256;
rm /media/$LBU_MEDIA/apks/$ARCH/*;
rm /media/$LBU_MEDIA/cache/*;
apk update && apk cache -v download;
tar xzf alpine-rpi-$VERSION_ID-$ARCH.tar.gz;
rm alpine-rpi-$VERSION_ID-$ARCH.tar.gz alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256;
sync;
reboot;}}

5. Test-it !
{{Cmd|uname -a}}

=== Update local package installations ===

This is done just as at [[#Update local package installations]], above.

== Updating a USB/CF diskless install without setup-bootable ==
It is possible to update a diskless install of Alpine from another system, or without using the setup-bootable script. This was tested for the 3.13 to the 3.14 upgrade on a Raspberry Pi.

Before starting, update /etc/apk/repositories file to retrieve packages for the new release. Then update all packages with:
{{Cmd|apk update && apk upgrade -i -a --update-cache}}

We can then use update-conf to check for changes to configurations from the new packages.
{{Cmd|# check apk-new config changes
update-conf -a -l
update-conf -a
}}

We now need to prepare to update the kernel and boot materials. To do this, we stop the modloop (which is the loopback mount providing kernel modules) and remount the SD media as read/write.

We can also shutdown the system, eject the media, and perform the next steps on another machine (if so, skip this command block)

{{Cmd|/etc/init.d/modloop stop
mount /media/mmcblk0p1 -o remount,rw
cd /media/mmcblk0p1
}}

At this point, remove all files from the SD media '''except for /cache, *.apkvol.tar.gz, usercfg.txt, and config.txt''' Rename config.txt to config.txt.bak temporarily, as extracting the new tar file will overwrite the file.

We can now download the new release and extract it. This example is for an Alpine Raspberry Pi release, so feel free to adjust the URLs for your system.

{{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz.sha256
wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz
sha256sum -c *.sha256
tar zxf *-aarch64.tar.gz && sync
rm alpine-rpi-*
}}

Restore the original config.txt:
{{Cmd|mv config.txt.bak config.txt}}

Update the persistent storage using lbu:
{{Cmd|lbu ci -d}}

We can now reboot, and this should boot into the new kernel. Once this is done, we can clean up and re-download apk caches:
{{Cmd|mount /media/mmcblk0p1 -o remount,rw
rm /media/mmcblk0p1/cache/*
sync && apk update && apk cache -v download
mount /media/mmcblk0p1 -o remount,ro
}}

[[Category:Installation]]
[[Category:Package Manager]]

Upgrading Alpine Linux to a new release branch

2022-08-16T20:19:38Z

Yuu: Re-populate cache after deleting it

This page covers upgrading to newer releases.

Doing regular security updates with the package manager is shown at [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading a running system]].

{{Warning|Before actually upgrading your system, make sure that you have a backup of your important data.}}

== Upgrading an Alpine Linux Hard-disk installation ==

=== Upgrading from older versions ===

In case an older version needs to be upgraded, i.e. not just upgrading from the last release to the subsequent version as covered by the individual release notes, also check [[Upgrading from older versions]] for potential specifically required upgrade steps.

=== Upgrading to latest release ===

When Alpine Linux is installed in '''sys''' mode, e.g. on a hard drive, upgrading to the next stable version should be a straightforward package manager operation. However, for specific info always refer to the appropriate release notes.

{{:Include:Upgrading to latest release}}

=== Upgrading to Edge ===
{{:Include:Upgrading to Edge}}

== Upgrading Alpine Linux on CD ==

=== Boot media ===

If the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO.

If booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box.

=== Update local package installations ===

If you have locally installed and configured additional packages using [[How_to_enable_APK_caching|APK caching]] you should also perform the following steps.

Backup the local configuration prior to upgrading.
{{Cmd|lbu ci}}

{{:Include:Upgrading to latest release}}

After upgrading the packages, save the upgraded configuration changes.
{{Cmd|lbu ci}}

== Upgrading Alpine Linux on other removable media (such as CF/USB) ==

The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Updating your repositories using [[#Upgrading_an_Alpine_Linux_Hard-disk_installation|the procedures detailed above]], then running:
{{Cmd|apk upgrade --update-cache --available}}
will suffice for some purposes. (If you want the new packages to be used after a reboot, you should [[How_to_enable_APK_caching|enable APK caching]].)

However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). That is what the following steps describe how to do.

{{:Include:Upgrading_Alpine_environmentvars}}

=== Upgrade Operating System ===

Start by checking that you have enough space on your media. For a '''standard''' Alpine image, you need at least 400MB available space.
{{Cmd|df -h {{!}} grep "Filesystem\{{!}}$LBU_MEDIA"}}

==== Download and verify new release ====

Make sure the media that holds your Alpine system is mounted readwrite.
{{Cmd|mount -oremount,rw /media/$LBU_MEDIA}}

'''If using Alpine Linux 2.2.3 or newer''': Download the latest release, {{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/<arch>/<image>.iso}} and then use the following command to mount and copy files as needed for you: {{Cmd|setup-bootable -u alpine-extended-<version>-<arch>.iso /media/$LBU_MEDIA}} Once the command completes, proceed to the [[#Save changes|Save changes]] section.

==== For older versions of Alpine ====
Start downloading a new '.iso' and a '.sha1' file
{{Cmd|cd /media/$LBU_MEDIA
wget -c {{#latestalp:alpine|url}}
wget {{#latestalp:alpine|url}}.sha1}}

Check integrity of the downloaded files ''(it might take some time)'':
{{Cmd|sha1sum -c {{#latestalp:alpine|file}}.sha1}}
''The output of the above command should say 'OK'. ''
''If says 'FAILED', delete the iso file and download it again.''

'''If using Alpine Linux 1.10.4 or newer''': there is a tool ''setup-bootable'' that will mount and copy the image you just downloaded to your boot medium. With this tool simply do: {{Cmd|setup-bootable -u {{#latestalp:alpine|file}} /media/$LBU_MEDIA}}

[[Upgrading from older versions#Upgrading_a_removable_medium_from_Alpine_before_1.10.4|Instructions for older versions of Alpine]] are located elsewhere.

=== Save changes ===
Now that all upgrades are done, we should save our settings to our media (which you hopefully have backed up prior to doing this upgrade).
{{Cmd|lbu ci}}

=== Load new kernel ===
In most cases you will need to reboot Alpine Linux (especially if there are changes in the kernel):
{{Cmd|sync
reboot}}

{{Note|If you know what you are doing, you might not need to reboot. But make sure that all services affected by the upgrade are restarted.}}

=== Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) ===
On Alpine 3.X and newer, kernel is not upgraded when using <code>apk upgrade</code> and <code>setup-bootable</code> does not work properly.

If you want to upgrade your kernel, you will need to get it from the latest release, but first you must have and run :
{{Cmd|apk update; apk version -l '<';
apk upgrade;
lbu ci;}}

So now all your packages are upgraded, you can upgrade your kernel.

1. We need to get some variables :
{{Cmd|. /etc/os-release;
. /etc/lbu/lbu.conf;
ARCH=$(cat /etc/apk/arch);}}

2. You '''must''' verify if they are correctly set, using this :
{{Cmd|echo "alpine version : $VERSION_ID";
echo "lbu media : $LBU_MEDIA";
echo "arch : $ARCH"}}

3. And it will output something like this (if not, do not continue this process) :
{{Cmd|alpine version : 3.13.5
lbu media : mmcblk0p1
arch : armhf}}

4. Then you can run this script (WARNING : config.txt will be overwritten!) :
{{Cmd|cd /media/$LBU_MEDIA;
mount -oremount,rw /media/$LBU_MEDIA;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz</nowiki>;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256</nowiki>;
sha256sum -c *.sha256;
rm /media/$LBU_MEDIA/apks/$ARCH/*;
rm /media/$LBU_MEDIA/cache/*;
apk update && apk cache -v download;
tar xzf alpine-rpi-$VERSION_ID-$ARCH.tar.gz;
rm alpine-rpi-$VERSION_ID-$ARCH.tar.gz alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256;
sync;
reboot;}}

5. Test-it !
{{Cmd|uname -a}}

=== Update local package installations ===

This is done just as at [[#Update local package installations]], above.

== Updating a USB/CF diskless install without setup-bootable ==
It is possible to update a diskless install of Alpine from another system, or without using the setup-bootable script. This was tested for the 3.13 to the 3.14 upgrade on a Raspberry Pi.

Before starting, update /etc/apk/repositories file to retrieve packages for the new release. Then update all packages with:
{{Cmd|apk update && apk upgrade -i -a --update-cache}}

We can then use update-conf to check for changes to configurations from the new packages.
{{Cmd|# check apk-new config changes
update-conf -a -l
update-conf -a
}}

We now need to prepare to update the kernel and boot materials. To do this, we stop the modloop (which is the loopback mount providing kernel modules) and remount the SD media as read/write.

We can also shutdown the system, eject the media, and perform the next steps on another machine (if so, skip this command block)

{{Cmd|/etc/init.d/modloop stop
mount /media/mmcblk0p1 -o remount,rw
cd /media/mmcblk0p1
}}

At this point, remove all files from the SD media '''except for /cache, *.apkvol.tar.gz, usercfg.txt, and config.txt''' Rename config.txt to config.txt.bak temporarily, as extracting the new tar file will overwrite the file.

We can now download the new release and extract it. This example is for an Alpine Raspberry Pi release, so feel free to adjust the URLs for your system.

{{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz.sha256
wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz
sha256sum -c *.sha256
tar zxf *-aarch64.tar.gz && sync
rm alpine-rpi-*
}}

Restore the original config.txt:
{{Cmd|mv config.txt.bak config.txt}}

Update the persistent storage using lbu:
{{Cmd|lbu ci -d}}

We can now reboot, and this should boot into the new kernel. Once this is done, we can clean up and re-download apk caches:
{{Cmd|mount /media/mmcblk0p1 -o remount,rw
rm /media/mmcblk0p1/cache/*
sync && apk update && apk cache -v download
mount /media/mmcblk0p1 -o remount,ro
}}

[[Category:Installation]]
[[Category:Package Manager]]

Odroid-C2

2022-04-11T20:48:54Z

Yuu: Aligments

==Introduction==

The Odroid-C2 single board computer is not very well supported by Alpine/Linux. However the "Generic ARM (aarch64)" build contains almost everything we need !

What do we need ?
* kernel : provided kernel by the Alpine team does not boot
* u-boot : provided u-boot does not autoboot without serial
* system files : everything is okay

On the hardware side:
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Required environement and toolchain==
Using GNU/Linux is recommended and this guide and here are the required dependencies, for Debian (as example) :
<pre>
apt install bc bison flex make gcc gcc-aarch64-linux-gnu libssl-dev libncurses-dev git squashfs-tools
</pre>
We need to set specific environment variables IF you are not using an arm64 machine. Usually, you should be running on a x64 architecture (Intel or AMD I guess), so you would like to cross-compile.
<pre>
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu
</pre>

==Build u-boot from source==
We need to build uboot from source as the u-boot provided does not autoboot without UART connected.
<pre>
git clone --depth 1 https://source.denx.de/u-boot/u-boot.git -b v2022.01 u-boot-denx.de
cd u-boot-denx.de
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make odroid-c2_defconfig
</pre>

We used the specific deconfig for the Odroid-C2 but, as mentionned before : we want to autoboot with or without UART connection.
You can still access the SPL prompt by pressing the 'Enter' key twice before the two seconds countdown.
<pre>
sed -i -e 's/.*CONFIG_SD_BOOT.*/CONFIG_SD_BOOT=y/' .config
sed -i -e 's/.*CONFIG_AUTOBOOT_KEYED .*/CONFIG_AUTOBOOT_KEYED=y/' .config
echo "CONFIG_AUTOBOOT_FLUSH_STDIN=y" >> .config
echo "CONFIG_AUTOBOOT_PROMPT="Press quickly 'Enter' twice to stop autoboot: %d\n"" >> .config
echo "# CONFIG_AUTOBOOT_ENCRYPTION is not set" >> .config
echo "CONFIG_AUTOBOOT_DELAY_STR=""" >> .config
echo "CONFIG_AUTOBOOT_STOP_STR="\xd\xd"" >> .config
echo "CONFIG_AUTOBOOT_KEYED_CTRLC=y" >> .config
</pre>

Then, it's time to build :
<pre>
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make odroidc2_defconfig
time make -j$(nproc)
</pre>

Amlogic doesn’t provide sources for the firmware and for tools needed to create the bootloader image, so it is necessary to obtain them from the git tree published by the board vendor.

So, you need to get Amlogic u-boot's fork to assemble the u-boot binary :
<pre>
cd ..
git clone --depth 1 https://github.com/hardkernel/u-boot.git -b odroidc2-v2015.01 u-boot
cd u-boot
</pre>

Copy "u-boot.bin" from the previous git repository (source.denx.de) to the amlogic u-boot repository:
<pre>cp ../u-boot-denx.de/u-boot.bin .</pre>

Then, generate u-boot using amlogic fip tools:
<pre>
./fip/fip_create --bl30 ./fip/gxb/bl30.bin --bl301 ./fip/gxb/bl301.bin --bl31 ./fip/gxb/bl31.bin --bl33 u-boot.bin ./fip.bin
./fip/fip_create --dump ./fip.bin
cat ./fip/gxb/bl2.package ./fip.bin > ./boot_new.bin
./fip/gxb/aml_encrypt_gxb --bootsig --input ./boot_new.bin --output ./u-boot.img
dd if=./u-boot.img of=./u-boot.gxbb bs=512 skip=96
</pre>

==Build the latest LTS kernel from source==
<pre>
git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git -b linux-5.15.y linux-stable
cd linux-stable
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make defconfig
</pre>
We need to adapt the default arm64 generated by defconfig. This configuration is required for Alpine/Linux and not enabled by default.
<pre>
sed -i -e 's/.*CONFIG_SQUASHFS_XZ.*/CONFIG_SQUASHFS_XZ=y/' .config
sed -i -e 's/.*CONFIG_UEVENT_HELPER.*/CONFIG_UEVENT_HELPER=y/' .config
sed -i -e 's/.*CONFIG_BLK_DEV_RAM.*/CONFIG_BLK_DEV_RAM=y/' .config
echo CONFIG_UEVENT_HELPER_PATH=\"/sbin/hotplug\" >> .config
echo CONFIG_BLK_DEV_RAM_COUNT=16 >> .config
echo CONFIG_BLK_DEV_RAM_SIZE=4096 >> .config
</pre>

We can also disable unrequired DRM modules. Hence you'll get les modules, vmlinux will be smaller and building kernel will be faster.
Note that you can also disable more modules or functionalities, by removing all DRM drivers or disable sound if you like it. It'll be perfect for a headless machine.
<pre>
sed -i -e 's/CONFIG_DRM_$.*$=.*/# CONFIG_DRM_\1 is not set/' .config
sed -i -e 's/.*CONFIG_DRM_LIMA.*/CONFIG_DRM_LIMA=m/' .config
sed -i -e 's/.*CONFIG_DRM_PANFROST.*/CONFIG_DRM_PANFROST=m/' .config
</pre>

If you want to enable DVFS for the s905 amlogic cpu :
<pre>
git apply --ignore-space-change --ignore-whitespace - << EOF
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247..027df3756 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -348,7 +348,8 @@ &saradc {
};

&scpi_clocks {
- status = "disabled";
+ /* Works only with new blobs that have limited DVFS table */
+ status = "okay";
};

/* SD */
EOF
</pre>

The, build your kernel, associated modules and the [https://elinux.org/Device_Tree_Reference#What_Is_Device_Tree DTB] (Device Tree Blob) from the source :
<pre>
time make -j$(nproc) Image dtbs modules
</pre>

Create modloop:
<pre>
rm -rf installed-modules && mkdir installed-modules
INSTALL_MOD_PATH=installed-modules make modules_install
find installed-modules -type l -delete
rm -f modloop
mksquashfs installed-modules/lib/ modloop -b 1048576 -comp xz -Xdict-size 100% -all-root
rm -rf installed-modules
</pre>

==Assembly==
Kernel part:
<pre>
DST="/mnt/mmcblk0p1"
gzip -c arch/arm64/boot/Image > ${DST}/vmlinuz
cp .config ${DST}/config
cp modloop ${DST}/modloop
cp System.map ${DST}/System.map
</pre>

Copy dtb:
<pre>
mkdir ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dtb ${DST}/boot/dtbs
</pre>

System part:
<pre>
tar -C $DST -xzf alpine-uboot-3.15.4-aarch64.tar.gz ./.alpine-release ./alpine.apkovl.tar.gz ./apks ./boot/initramfs-lts 2>/dev/null
</pre>

==U-Boot scripting==
Create boot.cmd file to /dev/mmcblk0:

<pre>
DST="/mnt/mmcblk0p1"
cat << EoF > boot.cmd
#------------------------------------------------------------------------------------------------------
#
# HELP:
# boot.cmd = source file for humans
# boot.scr = destination file needed for the board
# recompile-me with:
# mkimage -C none -A arm -T script -d boot.cmd boot.scr
#
#------------------------------------------------------------------------------------------------------

# init.
setenv modloop "/boot/modloop"
setenv console "tty1"
setenv condev "console=ttyAML0,115200n8"
setenv verbosity "7"
setenv display_autodetect "true"

# console arguments configuration
setenv consoleargs "modules=loop,squashfs,sd-mod,usb-storage modloop=\${modloop} \${condev} console=\${console} panic=10"
setenv bootargs "\${consoleargs} loglevel=\${verbosity}"

# load files
setenv devtype "mmc"
setenv devnum "0:1"
load \${devtype} \${devnum} \${kernel_addr_r} /boot/vmlinuz
load \${devtype} \${devnum} \${ramdisk_addr_r} /boot/initramfs-lts
load \${devtype} \${devnum} \${fdt_addr_r} /boot/dtbs/meson-gxbb-odroidc2.dtb

# boot
booti \$kernel_addr_r \$ramdisk_addr_r:3200000 \$fdt_addr_r
EoF
</pre>

Then, build this file for u-boot. The mkimage binary is available in the ./tools/ directory from the source.denx.de repository (see "Build u-boot from source" part).
<pre>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
</pre>

Please note that those two files must be placed in the /boot/ directory.

==Booting==

Connect your USB to TTL converter on your board : I noticed that you don't need to connect all wires, pin 1 don't seems to be is not mandatory at all.
<pre>
_____UART____
|Pin 4 - GND|
|Pin 3 - RXD|
|Pin 2 - TXD|
|Pin 1 - VCC|
\___________|
</pre>

All details are available on the odroid wiki : https://wiki.odroid.com/accessory/development/usb_uart_kit

Odroid-C2

2022-04-11T20:46:23Z

Yuu: Removed troubleshooting section

{{TOC right}}
{{Style}}

(Parts of this page are WIP, still incomplete and some might be incorrect.)

==Introduction==

The Odroid-C2 single board computer is not very well supported by Alpine/Linux. However the "Generic ARM (aarch64)" build contains almost everything we need !

What do we need ?
* kernel : provided kernel by the Alpine team does not boot
* u-boot : provided u-boot does not autoboot without serial
* system files : everything is okay

On the hardware side:
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Required environement and toolchain==
Using GNU/Linux is recommended and this guide and here are the required dependencies, for Debian (as example) :
<pre>
apt install bc bison flex make gcc gcc-aarch64-linux-gnu libssl-dev libncurses-dev git squashfs-tools
</pre>
We need to set specific environment variables IF you are not using an arm64 machine. Usually, you should be running on a x64 architecture (Intel or AMD I guess), so you would like to cross-compile.
<pre>
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu
</pre>

==Build u-boot from source==
We need to build uboot from source as the u-boot provided does not autoboot without UART connected.
<pre>
git clone --depth 1 https://source.denx.de/u-boot/u-boot.git -b v2022.01 u-boot-denx.de
cd u-boot-denx.de
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make odroid-c2_defconfig
</pre>

We used the specific deconfig for the Odroid-C2 but, as mentionned before : we want to autoboot with or without UART connection.
You can still access the SPL prompt by pressing the 'Enter' key twice before the two seconds countdown.
<pre>
sed -i -e 's/.*CONFIG_SD_BOOT.*/CONFIG_SD_BOOT=y/' .config
sed -i -e 's/.*CONFIG_AUTOBOOT_KEYED .*/CONFIG_AUTOBOOT_KEYED=y/' .config
echo "CONFIG_AUTOBOOT_FLUSH_STDIN=y" >> .config
echo "CONFIG_AUTOBOOT_PROMPT="Press quickly 'Enter' twice to stop autoboot: %d\n"" >> .config
echo "# CONFIG_AUTOBOOT_ENCRYPTION is not set" >> .config
echo "CONFIG_AUTOBOOT_DELAY_STR=""" >> .config
echo "CONFIG_AUTOBOOT_STOP_STR="\xd\xd"" >> .config
echo "CONFIG_AUTOBOOT_KEYED_CTRLC=y" >> .config
</pre>

Then, it's time to build :
<pre>
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make odroidc2_defconfig
time make -j$(nproc)
</pre>

Amlogic doesn’t provide sources for the firmware and for tools needed to create the bootloader image, so it is necessary to obtain them from the git tree published by the board vendor.

So, you need to get Amlogic u-boot's fork to assemble the u-boot binary :
<pre>
cd ..
git clone --depth 1 https://github.com/hardkernel/u-boot.git -b odroidc2-v2015.01 u-boot
cd u-boot
</pre>

Copy "u-boot.bin" from the previous git repository (source.denx.de) to the amlogic u-boot repository:
<pre>cp ../u-boot-denx.de/u-boot.bin .</pre>

Then, generate u-boot using amlogic fip tools:
<pre>
./fip/fip_create --bl30 ./fip/gxb/bl30.bin --bl301 ./fip/gxb/bl301.bin --bl31 ./fip/gxb/bl31.bin --bl33 u-boot.bin ./fip.bin
./fip/fip_create --dump ./fip.bin
cat ./fip/gxb/bl2.package ./fip.bin > ./boot_new.bin
./fip/gxb/aml_encrypt_gxb --bootsig --input ./boot_new.bin --output ./u-boot.img
dd if=./u-boot.img of=./u-boot.gxbb bs=512 skip=96
</pre>

==Build the latest LTS kernel from source==
<pre>
git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git -b linux-5.15.y linux-stable
cd linux-stable
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make defconfig
</pre>
We need to adapt the default arm64 generated by defconfig. This configuration is required for Alpine/Linux and not enabled by default.
<pre>
sed -i -e 's/.*CONFIG_SQUASHFS_XZ.*/CONFIG_SQUASHFS_XZ=y/' .config
sed -i -e 's/.*CONFIG_UEVENT_HELPER.*/CONFIG_UEVENT_HELPER=y/' .config
sed -i -e 's/.*CONFIG_BLK_DEV_RAM.*/CONFIG_BLK_DEV_RAM=y/' .config
echo CONFIG_UEVENT_HELPER_PATH=\"/sbin/hotplug\" >> .config
echo CONFIG_BLK_DEV_RAM_COUNT=16 >> .config
echo CONFIG_BLK_DEV_RAM_SIZE=4096 >> .config
</pre>

We can also disable unrequired DRM modules. Hence you'll get les modules, vmlinux will be smaller and building kernel will be faster.
Note that you can also disable more modules or functionalities, by removing all DRM drivers or disable sound if you like it. It'll be perfect for a headless machine.
<pre>
sed -i -e 's/CONFIG_DRM_$.*$=.*/# CONFIG_DRM_\1 is not set/' .config
sed -i -e 's/.*CONFIG_DRM_LIMA.*/CONFIG_DRM_LIMA=m/' .config
sed -i -e 's/.*CONFIG_DRM_PANFROST.*/CONFIG_DRM_PANFROST=m/' .config
</pre>

If you want to enable DVFS for the s905 amlogic cpu :
<pre>
git apply --ignore-space-change --ignore-whitespace - << EOF
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247..027df3756 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -348,7 +348,8 @@ &saradc {
};

&scpi_clocks {
- status = "disabled";
+ /* Works only with new blobs that have limited DVFS table */
+ status = "okay";
};

/* SD */
EOF
</pre>

The, build your kernel, associated modules and the [https://elinux.org/Device_Tree_Reference#What_Is_Device_Tree DTB] (Device Tree Blob) from the source :
<pre>
time make -j$(nproc) Image dtbs modules
</pre>

Create modloop:
<pre>
rm -rf installed-modules && mkdir installed-modules
INSTALL_MOD_PATH=installed-modules make modules_install
find installed-modules -type l -delete
rm -f modloop
mksquashfs installed-modules/lib/ modloop -b 1048576 -comp xz -Xdict-size 100% -all-root
rm -rf installed-modules
</pre>

==Assembly==
Kernel part:
<pre>
DST="/mnt/mmcblk0p1"
gzip -c arch/arm64/boot/Image > ${DST}/vmlinuz
cp .config ${DST}/config
cp modloop ${DST}/modloop
cp System.map ${DST}/System.map
</pre>

Copy dtb:
<pre>
mkdir ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dtb ${DST}/boot/dtbs
</pre>

System part:
<pre>
tar -C $DST -xzf alpine-uboot-3.15.4-aarch64.tar.gz ./.alpine-release ./alpine.apkovl.tar.gz ./apks ./boot/initramfs-lts 2>/dev/null
</pre>

==U-Boot scripting==
Create boot.cmd file to /dev/mmcblk0:

<pre>
DST="/mnt/mmcblk0p1"
cat << EoF > boot.cmd
#------------------------------------------------------------------------------------------------------
#
# HELP:
# boot.cmd = source file for humans
# boot.scr = destination file needed for the board
# recompile-me with:
# mkimage -C none -A arm -T script -d boot.cmd boot.scr
#
#------------------------------------------------------------------------------------------------------

# init.
setenv modloop "/boot/modloop"
setenv console "tty1"
setenv condev "console=ttyAML0,115200n8"
setenv verbosity "7"
setenv display_autodetect "true"

# console arguments configuration
setenv consoleargs "modules=loop,squashfs,sd-mod,usb-storage modloop=\${modloop} \${condev} console=\${console} panic=10"
setenv bootargs "\${consoleargs} loglevel=\${verbosity}"

# load files
setenv devtype "mmc"
setenv devnum "0:1"
load \${devtype} \${devnum} \${kernel_addr_r} /boot/vmlinuz
load \${devtype} \${devnum} \${ramdisk_addr_r} /boot/initramfs-lts
load \${devtype} \${devnum} \${fdt_addr_r} /boot/dtbs/meson-gxbb-odroidc2.dtb

# boot
booti \$kernel_addr_r \$ramdisk_addr_r:3200000 \$fdt_addr_r
EoF
</pre>

Then, build this file for u-boot. The mkimage binary is available in the ./tools/ directory from the source.denx.de repository (see "Build u-boot from source" part).
<pre>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
</pre>

Please note that those two files must be placed in the /boot/ directory.

==Booting==

Connect your USB to TTL converter on your board : I noticed that you don't need to connect all wires, pin 1 don't seems to be is not mandatory at all.
<pre>
_____UART____
|Pin 4 - GND|
|Pin 3 - RXD|
|Pin 2 - TXD|
|Pin 1 - VCC|
\___________|
</pre>

All details are available on the odroid wiki : https://wiki.odroid.com/accessory/development/usb_uart_kit

Odroid-C2

2022-04-11T20:45:55Z

Yuu: Booting part

Odroid-C2

2022-04-11T20:27:26Z

Yuu: Added booting part

Odroid-C2

2022-04-11T20:26:26Z

Yuu: Change title

Odroid-C2

2022-04-11T20:25:06Z

Yuu: Added spacing

{{TOC right}}
{{Style}}

(Parts of this page are WIP, still incomplete and some might be incorrect.)

==Introduction==

The Odroid-C2 single board computer is not very well supported by Alpine/Linux. However the "Generic ARM (aarch64)" build contains almost everything we need !

What do we need ?
* kernel : provided kernel by the Alpine team does not boot
* u-boot : provided u-boot does not autoboot without serial
* system files : everything is okay

On the hardware side:
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Required environement and toolchain==
Using GNU/Linux is recommended and this guide and here are the required dependencies, for Debian (as example) :
<pre>
apt install bc bison flex make gcc gcc-aarch64-linux-gnu libssl-dev libncurses-dev git squashfs-tools
</pre>
We need to set specific environment variables IF you are not using an arm64 machine. Usually, you should be running on a x64 architecture (Intel or AMD I guess), so you would like to cross-compile.
<pre>
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu
</pre>

==Build u-boot from source==
We need to build uboot from source as the u-boot provided does not autoboot without UART connected.
<pre>
git clone --depth 1 https://source.denx.de/u-boot/u-boot.git -b v2022.01 u-boot-denx.de
cd u-boot-denx.de
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make odroid-c2_defconfig
</pre>

We used the specific deconfig for the Odroid-C2 but, as mentionned before : we want to autoboot with or without UART connection.
You can still access the SPL prompt by pressing the 'Enter' key twice before the two seconds countdown.
<pre>
sed -i -e 's/.*CONFIG_SD_BOOT.*/CONFIG_SD_BOOT=y/' .config
sed -i -e 's/.*CONFIG_AUTOBOOT_KEYED .*/CONFIG_AUTOBOOT_KEYED=y/' .config
echo "CONFIG_AUTOBOOT_FLUSH_STDIN=y" >> .config
echo "CONFIG_AUTOBOOT_PROMPT="Press quickly 'Enter' twice to stop autoboot: %d\n"" >> .config
echo "# CONFIG_AUTOBOOT_ENCRYPTION is not set" >> .config
echo "CONFIG_AUTOBOOT_DELAY_STR=""" >> .config
echo "CONFIG_AUTOBOOT_STOP_STR="\xd\xd"" >> .config
echo "CONFIG_AUTOBOOT_KEYED_CTRLC=y" >> .config
</pre>

Then, it's time to build :
<pre>
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make odroidc2_defconfig
time make -j$(nproc)
</pre>

Amlogic doesn’t provide sources for the firmware and for tools needed to create the bootloader image, so it is necessary to obtain them from the git tree published by the board vendor.

So, you need to get Amlogic u-boot's fork to assemble the u-boot binary :
<pre>
cd ..
git clone --depth 1 https://github.com/hardkernel/u-boot.git -b odroidc2-v2015.01 u-boot
cd u-boot
</pre>

Copy "u-boot.bin" from the previous git repository (source.denx.de) to the amlogic u-boot repository:
<pre>cp ../u-boot-denx.de/u-boot.bin .</pre>

Then, generate u-boot using amlogic fip tools:
<pre>
./fip/fip_create --bl30 ./fip/gxb/bl30.bin --bl301 ./fip/gxb/bl301.bin --bl31 ./fip/gxb/bl31.bin --bl33 u-boot.bin ./fip.bin
./fip/fip_create --dump ./fip.bin
cat ./fip/gxb/bl2.package ./fip.bin > ./boot_new.bin
./fip/gxb/aml_encrypt_gxb --bootsig --input ./boot_new.bin --output ./u-boot.img
dd if=./u-boot.img of=./u-boot.gxbb bs=512 skip=96
</pre>

==Build the latest LTS kernel from source==
<pre>
git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git -b linux-5.15.y linux-stable
cd linux-stable
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make defconfig
</pre>
We need to adapt the default arm64 generated by defconfig. This configuration is required for Alpine/Linux and not enabled by default.
<pre>
sed -i -e 's/.*CONFIG_SQUASHFS_XZ.*/CONFIG_SQUASHFS_XZ=y/' .config
sed -i -e 's/.*CONFIG_UEVENT_HELPER.*/CONFIG_UEVENT_HELPER=y/' .config
sed -i -e 's/.*CONFIG_BLK_DEV_RAM.*/CONFIG_BLK_DEV_RAM=y/' .config
echo CONFIG_UEVENT_HELPER_PATH=\"/sbin/hotplug\" >> .config
echo CONFIG_BLK_DEV_RAM_COUNT=16 >> .config
echo CONFIG_BLK_DEV_RAM_SIZE=4096 >> .config
</pre>

We can also disable unrequired DRM modules. Hence you'll get les modules, vmlinux will be smaller and building kernel will be faster.
Note that you can also disable more modules or functionalities, by removing all DRM drivers or disable sound if you like it. It'll be perfect for a headless machine.
<pre>
sed -i -e 's/CONFIG_DRM_$.*$=.*/# CONFIG_DRM_\1 is not set/' .config
sed -i -e 's/.*CONFIG_DRM_LIMA.*/CONFIG_DRM_LIMA=m/' .config
sed -i -e 's/.*CONFIG_DRM_PANFROST.*/CONFIG_DRM_PANFROST=m/' .config
</pre>

If you want to enable DVFS for the s905 amlogic cpu :
<pre>
git apply --ignore-space-change --ignore-whitespace - << EOF
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247..027df3756 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -348,7 +348,8 @@ &saradc {
};

&scpi_clocks {
- status = "disabled";
+ /* Works only with new blobs that have limited DVFS table */
+ status = "okay";
};

/* SD */
EOF
</pre>

The, build your kernel, associated modules and the [https://elinux.org/Device_Tree_Reference#What_Is_Device_Tree DTB] (Device Tree Blob) from the source :
<pre>
time make -j$(nproc) Image dtbs modules
</pre>

Create modloop:
<pre>
rm -rf installed-modules && mkdir installed-modules
INSTALL_MOD_PATH=installed-modules make modules_install
find installed-modules -type l -delete
rm -f modloop
mksquashfs installed-modules/lib/ modloop -b 1048576 -comp xz -Xdict-size 100% -all-root
rm -rf installed-modules
</pre>

==Assembly==
Kernel part:
<pre>
DST="/mnt/mmcblk0p1"
gzip -c arch/arm64/boot/Image > ${DST}/vmlinuz
cp .config ${DST}/config
cp modloop ${DST}/modloop
cp System.map ${DST}/System.map
</pre>

Copy dtb:
<pre>
mkdir ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dtb ${DST}/boot/dtbs
</pre>

System part:
<pre>
tar -C $DST -xzf alpine-uboot-3.15.4-aarch64.tar.gz ./.alpine-release ./alpine.apkovl.tar.gz ./apks ./boot/initramfs-lts 2>/dev/null
</pre>

==Booting==
Create boot.cmd file to /dev/mmcblk0:

<pre>
DST="/mnt/mmcblk0p1"
cat << EoF > boot.cmd
#------------------------------------------------------------------------------------------------------
#
# HELP:
# boot.cmd = source file for humans
# boot.scr = destination file needed for the board
# recompile-me with:
# mkimage -C none -A arm -T script -d boot.cmd boot.scr
#
#------------------------------------------------------------------------------------------------------

# init.
setenv modloop "/boot/modloop"
setenv console "tty1"
setenv condev "console=ttyAML0,115200n8"
setenv verbosity "7"
setenv display_autodetect "true"

# console arguments configuration
setenv consoleargs "modules=loop,squashfs,sd-mod,usb-storage modloop=\${modloop} \${condev} console=\${console} panic=10"
setenv bootargs "\${consoleargs} loglevel=\${verbosity}"

# load files
setenv devtype "mmc"
setenv devnum "0:1"
load \${devtype} \${devnum} \${kernel_addr_r} /boot/vmlinuz
load \${devtype} \${devnum} \${ramdisk_addr_r} /boot/initramfs-lts
load \${devtype} \${devnum} \${fdt_addr_r} /boot/dtbs/meson-gxbb-odroidc2.dtb

# boot
booti \$kernel_addr_r \$ramdisk_addr_r:3200000 \$fdt_addr_r
EoF
</pre>

Then, build this file for u-boot. The mkimage binary is available in the ./tools/ directory from the source.denx.de repository (see "Build u-boot from source" part).
<pre>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
</pre>

Please note that those two files must be placed in the /boot/ directory.

==Troubleshooting==
''Work in progress''

Odroid-C2

2022-04-11T20:22:53Z

Yuu: Mkimage precisions

{{TOC right}}
{{Style}}

(Parts of this page are WIP, still incomplete and some might be incorrect.)

==Introduction==

The Odroid-C2 single board computer is not very well supported by Alpine/Linux. However the "Generic ARM (aarch64)" build contains almost everything we need !

What do we need ?
* kernel : provided kernel by the Alpine team does not boot
* u-boot : provided u-boot does not autoboot without serial
* system files : everything is okay

On the hardware side:
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Required environement and toolchain==
Using GNU/Linux is recommended and this guide and here are the required dependencies, for Debian (as example) :
<pre>
apt install bc bison flex make gcc gcc-aarch64-linux-gnu libssl-dev libncurses-dev git squashfs-tools
</pre>
We need to set specific environment variables IF you are not using an arm64 machine. Usually, you should be running on a x64 architecture (Intel or AMD I guess), so you would like to cross-compile.
<pre>
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu
</pre>

==Build u-boot from source==
We need to build uboot from source as the u-boot provided does not autoboot without UART connected.
<pre>
git clone --depth 1 https://source.denx.de/u-boot/u-boot.git -b v2022.01 u-boot-denx.de
cd u-boot-denx.de
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make odroid-c2_defconfig
</pre>

We used the specific deconfig for the Odroid-C2 but, as mentionned before : we want to autoboot with or without UART connection.
You can still access the SPL prompt by pressing the 'Enter' key twice before the two seconds countdown.
<pre>
sed -i -e 's/.*CONFIG_SD_BOOT.*/CONFIG_SD_BOOT=y/' .config
sed -i -e 's/.*CONFIG_AUTOBOOT_KEYED .*/CONFIG_AUTOBOOT_KEYED=y/' .config
echo "CONFIG_AUTOBOOT_FLUSH_STDIN=y" >> .config
echo "CONFIG_AUTOBOOT_PROMPT="Press quickly 'Enter' twice to stop autoboot: %d\n"" >> .config
echo "# CONFIG_AUTOBOOT_ENCRYPTION is not set" >> .config
echo "CONFIG_AUTOBOOT_DELAY_STR=""" >> .config
echo "CONFIG_AUTOBOOT_STOP_STR="\xd\xd"" >> .config
echo "CONFIG_AUTOBOOT_KEYED_CTRLC=y" >> .config
</pre>

Then, it's time to build :
<pre>
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make odroidc2_defconfig
time make -j$(nproc)
</pre>

Amlogic doesn’t provide sources for the firmware and for tools needed to create the bootloader image, so it is necessary to obtain them from the git tree published by the board vendor.

So, you need to get Amlogic u-boot's fork to assemble the u-boot binary :
<pre>
cd ..
git clone --depth 1 https://github.com/hardkernel/u-boot.git -b odroidc2-v2015.01 u-boot
cd u-boot
</pre>

Copy "u-boot.bin" from the previous git repository (source.denx.de) to the amlogic u-boot repository:
<pre>cp ../u-boot-denx.de/u-boot.bin .</pre>

Then, generate u-boot using amlogic fip tools:
<pre>
./fip/fip_create --bl30 ./fip/gxb/bl30.bin --bl301 ./fip/gxb/bl301.bin --bl31 ./fip/gxb/bl31.bin --bl33 u-boot.bin ./fip.bin
./fip/fip_create --dump ./fip.bin
cat ./fip/gxb/bl2.package ./fip.bin > ./boot_new.bin
./fip/gxb/aml_encrypt_gxb --bootsig --input ./boot_new.bin --output ./u-boot.img
dd if=./u-boot.img of=./u-boot.gxbb bs=512 skip=96
</pre>

==Build the latest LTS kernel from source==
<pre>
git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git -b linux-5.15.y linux-stable
cd linux-stable
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make defconfig
</pre>
We need to adapt the default arm64 generated by defconfig. This configuration is required for Alpine/Linux and not enabled by default.
<pre>
sed -i -e 's/.*CONFIG_SQUASHFS_XZ.*/CONFIG_SQUASHFS_XZ=y/' .config
sed -i -e 's/.*CONFIG_UEVENT_HELPER.*/CONFIG_UEVENT_HELPER=y/' .config
sed -i -e 's/.*CONFIG_BLK_DEV_RAM.*/CONFIG_BLK_DEV_RAM=y/' .config
echo CONFIG_UEVENT_HELPER_PATH=\"/sbin/hotplug\" >> .config
echo CONFIG_BLK_DEV_RAM_COUNT=16 >> .config
echo CONFIG_BLK_DEV_RAM_SIZE=4096 >> .config
</pre>

We can also disable unrequired DRM modules. Hence you'll get les modules, vmlinux will be smaller and building kernel will be faster.
Note that you can also disable more modules or functionalities, by removing all DRM drivers or disable sound if you like it. It'll be perfect for a headless machine.
<pre>
sed -i -e 's/CONFIG_DRM_$.*$=.*/# CONFIG_DRM_\1 is not set/' .config
sed -i -e 's/.*CONFIG_DRM_LIMA.*/CONFIG_DRM_LIMA=m/' .config
sed -i -e 's/.*CONFIG_DRM_PANFROST.*/CONFIG_DRM_PANFROST=m/' .config
</pre>

If you want to enable DVFS for the s905 amlogic cpu :
<pre>
git apply --ignore-space-change --ignore-whitespace - << EOF
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247..027df3756 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -348,7 +348,8 @@ &saradc {
};

&scpi_clocks {
- status = "disabled";
+ /* Works only with new blobs that have limited DVFS table */
+ status = "okay";
};

/* SD */
EOF
</pre>

The, build your kernel, associated modules and the [https://elinux.org/Device_Tree_Reference#What_Is_Device_Tree DTB] (Device Tree Blob) from the source :
<pre>
time make -j$(nproc) Image dtbs modules
</pre>

Create modloop:
<pre>
rm -rf installed-modules && mkdir installed-modules
INSTALL_MOD_PATH=installed-modules make modules_install
find installed-modules -type l -delete
rm -f modloop
mksquashfs installed-modules/lib/ modloop -b 1048576 -comp xz -Xdict-size 100% -all-root
rm -rf installed-modules
</pre>

==Assembly==
Kernel part:
<pre>
DST="/mnt/mmcblk0p1"
gzip -c arch/arm64/boot/Image > ${DST}/vmlinuz
cp .config ${DST}/config
cp modloop ${DST}/modloop
cp System.map ${DST}/System.map
</pre>

Copy dtb:
<pre>
mkdir ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dtb ${DST}/boot/dtbs
</pre>

System part:
<pre>
tar -C $DST -xzf alpine-uboot-3.15.4-aarch64.tar.gz ./.alpine-release ./alpine.apkovl.tar.gz ./apks ./boot/initramfs-lts 2>/dev/null
</pre>

==Booting==
Create boot.cmd file to /dev/mmcblk0:

<pre>
DST="/mnt/mmcblk0p1"
cat << EoF > boot.cmd
#------------------------------------------------------------------------------------------------------
#
# HELP:
# boot.cmd = source file for humans
# boot.scr = destination file needed for the board
# recompile-me with:
# mkimage -C none -A arm -T script -d boot.cmd boot.scr
#
#------------------------------------------------------------------------------------------------------

# init.
setenv modloop "/boot/modloop"
setenv console "tty1"
setenv condev "console=ttyAML0,115200n8"
setenv verbosity "7"
setenv display_autodetect "true"

# console arguments configuration
setenv consoleargs "modules=loop,squashfs,sd-mod,usb-storage modloop=\${modloop} \${condev} console=\${console} panic=10"
setenv bootargs "\${consoleargs} loglevel=\${verbosity}"

# load files
setenv devtype "mmc"
setenv devnum "0:1"
load \${devtype} \${devnum} \${kernel_addr_r} /boot/vmlinuz
load \${devtype} \${devnum} \${ramdisk_addr_r} /boot/initramfs-lts
load \${devtype} \${devnum} \${fdt_addr_r} /boot/dtbs/meson-gxbb-odroidc2.dtb

# boot
booti \$kernel_addr_r \$ramdisk_addr_r:3200000 \$fdt_addr_r
EoF
</pre>

Then, build this file for u-boot. The mkimage binary is available in the ./tools/ directory from the source.denx.de repository (see "Build u-boot from source" part).
<pre>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
</pre>

Please note that those two files must be placed in the /boot/ directory.

==Troubleshooting==
''Work in progress''

Odroid-C2

2022-04-11T20:18:35Z

Yuu: Added u-boot assembly

{{TOC right}}
{{Style}}

(Parts of this page are WIP, still incomplete and some might be incorrect.)

==Introduction==

The Odroid-C2 single board computer is not very well supported by Alpine/Linux. However the "Generic ARM (aarch64)" build contains almost everything we need !

What do we need ?
* kernel : provided kernel by the Alpine team does not boot
* u-boot : provided u-boot does not autoboot without serial
* system files : everything is okay

On the hardware side:
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Required environement and toolchain==
Using GNU/Linux is recommended and this guide and here are the required dependencies, for Debian (as example) :
<pre>
apt install bc bison flex make gcc gcc-aarch64-linux-gnu libssl-dev libncurses-dev git squashfs-tools
</pre>
We need to set specific environment variables IF you are not using an arm64 machine. Usually, you should be running on a x64 architecture (Intel or AMD I guess), so you would like to cross-compile.
<pre>
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu
</pre>

==Build u-boot from source==
We need to build uboot from source as the u-boot provided does not autoboot without UART connected.
<pre>
git clone --depth 1 https://source.denx.de/u-boot/u-boot.git -b v2022.01 u-boot-denx.de
cd u-boot-denx.de
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make odroid-c2_defconfig
</pre>

We used the specific deconfig for the Odroid-C2 but, as mentionned before : we want to autoboot with or without UART connection.
You can still access the SPL prompt by pressing the 'Enter' key twice before the two seconds countdown.
<pre>
sed -i -e 's/.*CONFIG_SD_BOOT.*/CONFIG_SD_BOOT=y/' .config
sed -i -e 's/.*CONFIG_AUTOBOOT_KEYED .*/CONFIG_AUTOBOOT_KEYED=y/' .config
echo "CONFIG_AUTOBOOT_FLUSH_STDIN=y" >> .config
echo "CONFIG_AUTOBOOT_PROMPT="Press quickly 'Enter' twice to stop autoboot: %d\n"" >> .config
echo "# CONFIG_AUTOBOOT_ENCRYPTION is not set" >> .config
echo "CONFIG_AUTOBOOT_DELAY_STR=""" >> .config
echo "CONFIG_AUTOBOOT_STOP_STR="\xd\xd"" >> .config
echo "CONFIG_AUTOBOOT_KEYED_CTRLC=y" >> .config
</pre>

Then, it's time to build :
<pre>
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make odroidc2_defconfig
time make -j$(nproc)
</pre>

Amlogic doesn’t provide sources for the firmware and for tools needed to create the bootloader image, so it is necessary to obtain them from the git tree published by the board vendor.

So, you need to get Amlogic u-boot's fork to assemble the u-boot binary :
<pre>
cd ..
git clone --depth 1 https://github.com/hardkernel/u-boot.git -b odroidc2-v2015.01 u-boot
cd u-boot
</pre>

Copy "u-boot.bin" from the previous git repository (source.denx.de) to the amlogic u-boot repository:
<pre>cp ../u-boot-denx.de/u-boot.bin .</pre>

Then, generate u-boot using amlogic fip tools:
<pre>
./fip/fip_create --bl30 ./fip/gxb/bl30.bin --bl301 ./fip/gxb/bl301.bin --bl31 ./fip/gxb/bl31.bin --bl33 u-boot.bin ./fip.bin
./fip/fip_create --dump ./fip.bin
cat ./fip/gxb/bl2.package ./fip.bin > ./boot_new.bin
./fip/gxb/aml_encrypt_gxb --bootsig --input ./boot_new.bin --output ./u-boot.img
dd if=./u-boot.img of=./u-boot.gxbb bs=512 skip=96
</pre>

==Build the latest LTS kernel from source==
<pre>
git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git -b linux-5.15.y linux-stable
cd linux-stable
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make defconfig
</pre>
We need to adapt the default arm64 generated by defconfig. This configuration is required for Alpine/Linux and not enabled by default.
<pre>
sed -i -e 's/.*CONFIG_SQUASHFS_XZ.*/CONFIG_SQUASHFS_XZ=y/' .config
sed -i -e 's/.*CONFIG_UEVENT_HELPER.*/CONFIG_UEVENT_HELPER=y/' .config
sed -i -e 's/.*CONFIG_BLK_DEV_RAM.*/CONFIG_BLK_DEV_RAM=y/' .config
echo CONFIG_UEVENT_HELPER_PATH=\"/sbin/hotplug\" >> .config
echo CONFIG_BLK_DEV_RAM_COUNT=16 >> .config
echo CONFIG_BLK_DEV_RAM_SIZE=4096 >> .config
</pre>

We can also disable unrequired DRM modules. Hence you'll get les modules, vmlinux will be smaller and building kernel will be faster.
Note that you can also disable more modules or functionalities, by removing all DRM drivers or disable sound if you like it. It'll be perfect for a headless machine.
<pre>
sed -i -e 's/CONFIG_DRM_$.*$=.*/# CONFIG_DRM_\1 is not set/' .config
sed -i -e 's/.*CONFIG_DRM_LIMA.*/CONFIG_DRM_LIMA=m/' .config
sed -i -e 's/.*CONFIG_DRM_PANFROST.*/CONFIG_DRM_PANFROST=m/' .config
</pre>

If you want to enable DVFS for the s905 amlogic cpu :
<pre>
git apply --ignore-space-change --ignore-whitespace - << EOF
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247..027df3756 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -348,7 +348,8 @@ &saradc {
};

&scpi_clocks {
- status = "disabled";
+ /* Works only with new blobs that have limited DVFS table */
+ status = "okay";
};

/* SD */
EOF
</pre>

The, build your kernel, associated modules and the [https://elinux.org/Device_Tree_Reference#What_Is_Device_Tree DTB] (Device Tree Blob) from the source :
<pre>
time make -j$(nproc) Image dtbs modules
</pre>

Create modloop:
<pre>
rm -rf installed-modules && mkdir installed-modules
INSTALL_MOD_PATH=installed-modules make modules_install
find installed-modules -type l -delete
rm -f modloop
mksquashfs installed-modules/lib/ modloop -b 1048576 -comp xz -Xdict-size 100% -all-root
rm -rf installed-modules
</pre>

==Assembly==
Kernel part:
<pre>
DST="/mnt/mmcblk0p1"
gzip -c arch/arm64/boot/Image > ${DST}/vmlinuz
cp .config ${DST}/config
cp modloop ${DST}/modloop
cp System.map ${DST}/System.map
</pre>

Copy dtb:
<pre>
mkdir ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dtb ${DST}/boot/dtbs
</pre>

System part:
<pre>
tar -C $DST -xzf alpine-uboot-3.15.4-aarch64.tar.gz ./.alpine-release ./alpine.apkovl.tar.gz ./apks ./boot/initramfs-lts 2>/dev/null
</pre>

==Booting==
Create boot.cmd file to /dev/mmcblk0:

<pre>
DST="/mnt/mmcblk0p1"
cat << EoF > boot.cmd
#------------------------------------------------------------------------------------------------------
#
# HELP:
# boot.cmd = source file for humans
# boot.scr = destination file needed for the board
# recompile-me with:
# mkimage -C none -A arm -T script -d boot.cmd boot.scr
#
#------------------------------------------------------------------------------------------------------

# init.
setenv modloop "/boot/modloop"
setenv console "tty1"
setenv condev "console=ttyAML0,115200n8"
setenv verbosity "7"
setenv display_autodetect "true"

# console arguments configuration
setenv consoleargs "modules=loop,squashfs,sd-mod,usb-storage modloop=\${modloop} \${condev} console=\${console} panic=10"
setenv bootargs "\${consoleargs} loglevel=\${verbosity}"

# load files
setenv devtype "mmc"
setenv devnum "0:1"
load \${devtype} \${devnum} \${kernel_addr_r} /boot/vmlinuz
load \${devtype} \${devnum} \${ramdisk_addr_r} /boot/initramfs-lts
load \${devtype} \${devnum} \${fdt_addr_r} /boot/dtbs/meson-gxbb-odroidc2.dtb

# boot
booti \$kernel_addr_r \$ramdisk_addr_r:3200000 \$fdt_addr_r
EoF
</pre>

Then, build this file for u-boot. This binary is available in the ./tools/ directory from the source.denx.de repository (see "Build u-boot from source" part).
<pre>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
</pre>

Please note that those two files must be placed in the /boot/ directory.

==Troubleshooting==
''Work in progress''

Odroid-C2

2022-04-11T20:11:46Z

Yuu: Added booting part

{{TOC right}}
{{Style}}

(Parts of this page are WIP, still incomplete and some might be incorrect.)

==Introduction==

The Odroid-C2 single board computer is not very well supported by Alpine/Linux. However the "Generic ARM (aarch64)" build contains almost everything we need !

What do we need ?
* kernel : provided kernel by the Alpine team does not boot
* u-boot : provided u-boot does not autoboot without serial
* system files : everything is okay

On the hardware side:
* [https://wiki.odroid.com/odroid-c2/odroid-c2 Odroid-C2]
* Official PSU or just a micro-SD cable (notes : the barrel plug (inner(positive) diameter 0.8mm and outer(negative) diameter 2.5mm) is recommended, without the J1 jumper)
* micro-SD (or eMMC)
* USB to TTL ([https://wiki.odroid.com/accessory/development/usb_uart_kit official] or [https://duckduckgo.com/?q=CP2102+ttl&t=h_&iax=images&ia=images CP2102 chipset] or an old rpi)

==Required environement and toolchain==
Using GNU/Linux is recommended and this guide and here are the required dependencies, for Debian (as example) :
<pre>
apt install bc bison flex make gcc gcc-aarch64-linux-gnu libssl-dev libncurses-dev git squashfs-tools
</pre>
We need to set specific environment variables IF you are not using an arm64 machine. Usually, you should be running on a x64 architecture (Intel or AMD I guess), so you would like to cross-compile.
<pre>
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu
</pre>

==Build u-boot from source==
We need to build uboot from source as the u-boot provided does not autoboot without UART connected.
<pre>
git clone --depth 1 https://source.denx.de/u-boot/u-boot.git -b v2022.01 u-boot-denx.de
cd u-boot-denx.de
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make odroid-c2_defconfig
</pre>

We used the specific deconfig for the Odroid-C2 but, as mentionned before : we want to autoboot with or without UART connection.
You can still access the SPL prompt by pressing the 'Enter' key twice before the two seconds countdown.
<pre>
sed -i -e 's/.*CONFIG_SD_BOOT.*/CONFIG_SD_BOOT=y/' .config
sed -i -e 's/.*CONFIG_AUTOBOOT_KEYED .*/CONFIG_AUTOBOOT_KEYED=y/' .config
echo "CONFIG_AUTOBOOT_FLUSH_STDIN=y" >> .config
echo "CONFIG_AUTOBOOT_PROMPT="Press quickly 'Enter' twice to stop autoboot: %d\n"" >> .config
echo "# CONFIG_AUTOBOOT_ENCRYPTION is not set" >> .config
echo "CONFIG_AUTOBOOT_DELAY_STR=""" >> .config
echo "CONFIG_AUTOBOOT_STOP_STR="\xd\xd"" >> .config
echo "CONFIG_AUTOBOOT_KEYED_CTRLC=y" >> .config
</pre>

Then, it's time to build :
<pre>
time make -j$(nproc)
</pre>

Amlogic doesn’t provide sources for the firmware and for tools needed to create the bootloader image, so it is necessary to obtain them from the git tree published by the board vendor.
''Work in progress''

==Build the latest LTS kernel from source==
<pre>
git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git -b linux-5.15.y linux-stable
cd linux-stable
export ARCH=arm64 && export CROSS_COMPILE=aarch64-linux-gnu-
make mrproper && make defconfig
</pre>
We need to adapt the default arm64 generated by defconfig. This configuration is required for Alpine/Linux and not enabled by default.
<pre>
sed -i -e 's/.*CONFIG_SQUASHFS_XZ.*/CONFIG_SQUASHFS_XZ=y/' .config
sed -i -e 's/.*CONFIG_UEVENT_HELPER.*/CONFIG_UEVENT_HELPER=y/' .config
sed -i -e 's/.*CONFIG_BLK_DEV_RAM.*/CONFIG_BLK_DEV_RAM=y/' .config
echo CONFIG_UEVENT_HELPER_PATH=\"/sbin/hotplug\" >> .config
echo CONFIG_BLK_DEV_RAM_COUNT=16 >> .config
echo CONFIG_BLK_DEV_RAM_SIZE=4096 >> .config
</pre>

We can also disable unrequired DRM modules. Hence you'll get les modules, vmlinux will be smaller and building kernel will be faster.
Note that you can also disable more modules or functionalities, by removing all DRM drivers or disable sound if you like it. It'll be perfect for a headless machine.
<pre>
sed -i -e 's/CONFIG_DRM_$.*$=.*/# CONFIG_DRM_\1 is not set/' .config
sed -i -e 's/.*CONFIG_DRM_LIMA.*/CONFIG_DRM_LIMA=m/' .config
sed -i -e 's/.*CONFIG_DRM_PANFROST.*/CONFIG_DRM_PANFROST=m/' .config
</pre>

If you want to enable DVFS for the s905 amlogic cpu :
<pre>
git apply --ignore-space-change --ignore-whitespace - << EOF
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247..027df3756 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -348,7 +348,8 @@ &saradc {
};

&scpi_clocks {
- status = "disabled";
+ /* Works only with new blobs that have limited DVFS table */
+ status = "okay";
};

/* SD */
EOF
</pre>

The, build your kernel, associated modules and the [https://elinux.org/Device_Tree_Reference#What_Is_Device_Tree DTB] (Device Tree Blob) from the source :
<pre>
time make -j$(nproc) Image dtbs modules
</pre>

Create modloop:
<pre>
rm -rf installed-modules && mkdir installed-modules
INSTALL_MOD_PATH=installed-modules make modules_install
find installed-modules -type l -delete
rm -f modloop
mksquashfs installed-modules/lib/ modloop -b 1048576 -comp xz -Xdict-size 100% -all-root
rm -rf installed-modules
</pre>

==Assembly==
Kernel part:
<pre>
DST="/mnt/mmcblk0p1"
gzip -c arch/arm64/boot/Image > ${DST}/vmlinuz
cp .config ${DST}/config
cp modloop ${DST}/modloop
cp System.map ${DST}/System.map
</pre>

Copy dtb:
<pre>
mkdir ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts ${DST}/boot/dtbs
cp arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dtb ${DST}/boot/dtbs
</pre>

System part:
<pre>
tar -C $DST -xzf alpine-uboot-3.15.4-aarch64.tar.gz ./.alpine-release ./alpine.apkovl.tar.gz ./apks ./boot/initramfs-lts 2>/dev/null
</pre>

==Booting==
Create boot.cmd file to /dev/mmcblk0:

<pre>
DST="/mnt/mmcblk0p1"
cat << EoF > boot.cmd
#------------------------------------------------------------------------------------------------------
#
# HELP:
# boot.cmd = source file for humans
# boot.scr = destination file needed for the board
# recompile-me with:
# mkimage -C none -A arm -T script -d boot.cmd boot.scr
#
#------------------------------------------------------------------------------------------------------

# init.
setenv modloop "/boot/modloop"
setenv console "tty1"
setenv condev "console=ttyAML0,115200n8"
setenv verbosity "7"
setenv display_autodetect "true"

# console arguments configuration
setenv consoleargs "modules=loop,squashfs,sd-mod,usb-storage modloop=\${modloop} \${condev} console=\${console} panic=10"
setenv bootargs "\${consoleargs} loglevel=\${verbosity}"

# load files
setenv devtype "mmc"
setenv devnum "0:1"
load \${devtype} \${devnum} \${kernel_addr_r} /boot/vmlinuz
load \${devtype} \${devnum} \${ramdisk_addr_r} /boot/initramfs-lts
load \${devtype} \${devnum} \${fdt_addr_r} /boot/dtbs/meson-gxbb-odroidc2.dtb

# boot
booti \$kernel_addr_r \$ramdisk_addr_r:3200000 \$fdt_addr_r
EoF
</pre>

Then, build this file for u-boot. This binary is available in the ./tools/ directory from the source.denx.de repository (see "Build u-boot from source" part).
<pre>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
</pre>

Please note that those two files must be placed in the /boot/ directory.

==Troubleshooting==
''Work in progress''

Odroid-C2

2022-04-11T20:04:04Z

Yuu: Carriage return

Odroid-C2

2022-04-11T20:00:07Z

Yuu: Added system part extraction

Odroid-C2

2022-04-11T19:06:28Z

Yuu: Linux kernel : disable unnecessary DRM modules

Odroid-C2

2022-04-05T19:54:02Z

Yuu: Fix pre tag

Odroid-C2

2022-04-05T19:52:59Z

Yuu: Device tree is required to boot

Odroid-C2

2022-04-05T19:49:24Z

Yuu: DVFS for s905

Odroid-C2

2022-04-03T15:15:57Z

Yuu: Kernel assembly

Odroid-C2

2022-04-03T14:52:53Z

Yuu: missing squashfs-tools package

Odroid-C2

2022-04-03T14:35:39Z

Yuu: libssl-dev is required to build kernel from source

Odroid-C2

2022-04-03T14:34:58Z

Yuu: fix kernel branch name, add ARCH and CROSS_COMPILE options

Upgrading Alpine Linux to a new release branch

2022-04-01T17:04:07Z

Yuu: Remove cached APK before extracting Alpine update

This page covers upgrading to newer releases.

Doing regular security updates with the package manager is shown at [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading a running system]].

{{Warning|Before actually upgrading your system, make sure that you have a backup of your important data.}}

== Upgrading an Alpine Linux Hard-disk installation ==

=== Upgrading from older versions ===

In case an older version needs to be upgraded, i.e. not just upgrading from the last release to the subsequent version as covered by the individual release notes, also check [[Upgrading from older versions]] for potential specifically required upgrade steps.

=== Upgrading to latest release ===

When Alpine Linux is installed in '''sys''' mode, e.g. on a hard drive, upgrading to the next stable version should be a straightforward package manager operation. However, for specific info always refer to the appropriate release notes.

{{:Include:Upgrading to latest release}}

=== Upgrading to Edge ===
{{:Include:Upgrading to Edge}}

== Upgrading Alpine Linux on CD ==

=== Boot media ===

If the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO.

If booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box.

=== Update local package installations ===

If you have locally installed and configured additional packages using [[How_to_enable_APK_caching|APK caching]] you should also perform the following steps.

Backup the local configuration prior to upgrading.
{{Cmd|lbu ci}}

{{:Include:Upgrading to latest release}}

After upgrading the packages, save the upgraded configuration changes.
{{Cmd|lbu ci}}

== Upgrading Alpine Linux on other removable media (such as CF/USB) ==

The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Updating your repositories using [[#Upgrading_an_Alpine_Linux_Hard-disk_installation|the procedures detailed above]], then running:
{{Cmd|apk upgrade --update-cache --available}}
will suffice for some purposes. (If you want the new packages to be used after a reboot, you should [[How_to_enable_APK_caching|enable APK caching]].)

However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). That is what the following steps describe how to do.

{{:Include:Upgrading_Alpine_environmentvars}}

=== Upgrade Operating System ===

Start by checking that you have enough space on your media. For a '''standard''' Alpine image, you need at least 400MB available space.
{{Cmd|df -h {{!}} grep "Filesystem\{{!}}$LBU_MEDIA"}}

==== Download and verify new release ====

Make sure the media that holds your Alpine system is mounted readwrite.
{{Cmd|mount -oremount,rw /media/$LBU_MEDIA}}

'''If using Alpine Linux 2.2.3 or newer''': Download the latest release, {{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/<arch>/<image>.iso}} and then use the following command to mount and copy files as needed for you: {{Cmd|setup-bootable -u alpine-extended-<version>-<arch>.iso /media/$LBU_MEDIA}} Once the command completes, proceed to the [[#Save changes|Save changes]] section.

==== For older versions of Alpine ====
Start downloading a new '.iso' and a '.sha1' file
{{Cmd|cd /media/$LBU_MEDIA
wget -c {{#latestalp:alpine|url}}
wget {{#latestalp:alpine|url}}.sha1}}

Check integrity of the downloaded files ''(it might take some time)'':
{{Cmd|sha1sum -c {{#latestalp:alpine|file}}.sha1}}
''The output of the above command should say 'OK'. ''
''If says 'FAILED', delete the iso file and download it again.''

'''If using Alpine Linux 1.10.4 or newer''': there is a tool ''setup-bootable'' that will mount and copy the image you just downloaded to your boot medium. With this tool simply do: {{Cmd|setup-bootable -u {{#latestalp:alpine|file}} /media/$LBU_MEDIA}}

[[Upgrading from older versions#Upgrading_a_removable_medium_from_Alpine_before_1.10.4|Instructions for older versions of Alpine]] are located elsewhere.

=== Save changes ===
Now that all upgrades are done, we should save our settings to our media (which you hopefully have backed up prior to doing this upgrade).
{{Cmd|lbu ci}}

=== Load new kernel ===
In most cases you will need to reboot Alpine Linux (especially if there are changes in the kernel):
{{Cmd|sync
reboot}}

{{Note|If you know what you are doing, you might not need to reboot. But make sure that all services affected by the upgrade are restarted.}}

=== Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) ===
On Alpine 3.X and newer, kernel is not upgraded when using <code>apk upgrade</code> and <code>setup-bootable</code> does not work properly.

If you want to upgrade your kernel, you will need to get it from the latest release, but first you must have and run :
{{Cmd|apk update; apk version -l '<';
apk upgrade;
lbu ci;}}

So now all your packages are upgraded, you can upgrade your kernel.

1. We need to get some variables :
{{Cmd|. /etc/os-release;
. /etc/lbu/lbu.conf;
ARCH=$(cat /etc/apk/arch);}}

2. You '''must''' verify if they are correctly set, using this :
{{Cmd|echo "alpine version : $VERSION_ID";
echo "lbu media : $LBU_MEDIA";
echo "arch : $ARCH"}}

3. And it will output something like this (if not, do not continue this process) :
{{Cmd|alpine version : 3.13.5
lbu media : mmcblk0p1
arch : armhf}}

4. Then you can run this script (WARNING : config.txt will be overwritten!) :
{{Cmd|cd /media/$LBU_MEDIA;
mount -oremount,rw /media/$LBU_MEDIA;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz</nowiki>;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256</nowiki>;
sha256sum -c *.sha256;
rm /media/$LBU_MEDIA/apks/$ARCH/*;
rm /media/$LBU_MEDIA/cache/*;
tar xzf alpine-rpi-$VERSION_ID-$ARCH.tar.gz;
rm alpine-rpi-$VERSION_ID-$ARCH.tar.gz alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256;
sync;
reboot;}}

5. Test-it !
{{Cmd|uname -a}}

6. Populate apk cache :
{{apk update && apk cache -v download}}

=== Update local package installations ===

This is done just as at [[#Update local package installations]], above.

== Updating a USB/CF diskless install without setup-bootable ==
It is possible to update a diskless install of Alpine from another system, or without using the setup-bootable script. This was tested for the 3.13 to the 3.14 upgrade on a Raspberry Pi.

Before starting, update /etc/apk/repositories file to retrieve packages for the new release. Then update all packages with:
{{Cmd|apk update && apk upgrade -i -a --update-cache}}

We can then use update-conf to check for changes to configurations from the new packages.
{{Cmd|# check apk-new config changes
update-conf -a -l
update-conf -a
}}

We now need to prepare to update the kernel and boot materials. To do this, we stop the modloop (which is the loopback mount providing kernel modules) and remount the SD media as read/write.

We can also shutdown the system, eject the media, and perform the next steps on another machine (if so, skip this command block)

{{Cmd|/etc/init.d/modloop stop
mount /media/mmcblk0p1 -o remount,rw
cd /media/mmcblk0p1
}}

At this point, remove all files from the SD media '''except for /cache, *.apkvol.tar.gz, usercfg.txt, and config.txt''' Rename config.txt to config.txt.bak temporarily, as extracting the new tar file will overwrite the file.

We can now download the new release and extract it. This example is for an Alpine Raspberry Pi release, so feel free to adjust the URLs for your system.

{{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz.sha256
wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz
sha256sum -c *.sha256
tar zxf *-aarch64.tar.gz && sync
rm alpine-rpi-*
}}

Restore the original config.txt:
{{Cmd|mv config.txt.bak config.txt}}

Update the persistent storage using lbu:
{{Cmd|lbu ci -d}}

We can now reboot, and this should boot into the new kernel. Once this is done, we can clean up and re-download apk caches:
{{Cmd|mount /media/mmcblk0p1 -o remount,rw
rm /media/mmcblk0p1/cache/*
sync && apk update && apk cache -v download
mount /media/mmcblk0p1 -o remount,ro
}}

[[Category:Installation]]
[[Category:Package Manager]]

Upgrading Alpine Linux to a new release branch

2022-04-01T17:00:30Z

Yuu: /* Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) */

This page covers upgrading to newer releases.

Doing regular security updates with the package manager is shown at [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading a running system]].

{{Warning|Before actually upgrading your system, make sure that you have a backup of your important data.}}

== Upgrading an Alpine Linux Hard-disk installation ==

=== Upgrading from older versions ===

In case an older version needs to be upgraded, i.e. not just upgrading from the last release to the subsequent version as covered by the individual release notes, also check [[Upgrading from older versions]] for potential specifically required upgrade steps.

=== Upgrading to latest release ===

When Alpine Linux is installed in '''sys''' mode, e.g. on a hard drive, upgrading to the next stable version should be a straightforward package manager operation. However, for specific info always refer to the appropriate release notes.

{{:Include:Upgrading to latest release}}

=== Upgrading to Edge ===
{{:Include:Upgrading to Edge}}

== Upgrading Alpine Linux on CD ==

=== Boot media ===

If the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO.

If booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box.

=== Update local package installations ===

If you have locally installed and configured additional packages using [[How_to_enable_APK_caching|APK caching]] you should also perform the following steps.

Backup the local configuration prior to upgrading.
{{Cmd|lbu ci}}

{{:Include:Upgrading to latest release}}

After upgrading the packages, save the upgraded configuration changes.
{{Cmd|lbu ci}}

== Upgrading Alpine Linux on other removable media (such as CF/USB) ==

The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Updating your repositories using [[#Upgrading_an_Alpine_Linux_Hard-disk_installation|the procedures detailed above]], then running:
{{Cmd|apk upgrade --update-cache --available}}
will suffice for some purposes. (If you want the new packages to be used after a reboot, you should [[How_to_enable_APK_caching|enable APK caching]].)

However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). That is what the following steps describe how to do.

{{:Include:Upgrading_Alpine_environmentvars}}

=== Upgrade Operating System ===

Start by checking that you have enough space on your media. For a '''standard''' Alpine image, you need at least 400MB available space.
{{Cmd|df -h {{!}} grep "Filesystem\{{!}}$LBU_MEDIA"}}

==== Download and verify new release ====

Make sure the media that holds your Alpine system is mounted readwrite.
{{Cmd|mount -oremount,rw /media/$LBU_MEDIA}}

'''If using Alpine Linux 2.2.3 or newer''': Download the latest release, {{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/<arch>/<image>.iso}} and then use the following command to mount and copy files as needed for you: {{Cmd|setup-bootable -u alpine-extended-<version>-<arch>.iso /media/$LBU_MEDIA}} Once the command completes, proceed to the [[#Save changes|Save changes]] section.

==== For older versions of Alpine ====
Start downloading a new '.iso' and a '.sha1' file
{{Cmd|cd /media/$LBU_MEDIA
wget -c {{#latestalp:alpine|url}}
wget {{#latestalp:alpine|url}}.sha1}}

Check integrity of the downloaded files ''(it might take some time)'':
{{Cmd|sha1sum -c {{#latestalp:alpine|file}}.sha1}}
''The output of the above command should say 'OK'. ''
''If says 'FAILED', delete the iso file and download it again.''

'''If using Alpine Linux 1.10.4 or newer''': there is a tool ''setup-bootable'' that will mount and copy the image you just downloaded to your boot medium. With this tool simply do: {{Cmd|setup-bootable -u {{#latestalp:alpine|file}} /media/$LBU_MEDIA}}

[[Upgrading from older versions#Upgrading_a_removable_medium_from_Alpine_before_1.10.4|Instructions for older versions of Alpine]] are located elsewhere.

=== Save changes ===
Now that all upgrades are done, we should save our settings to our media (which you hopefully have backed up prior to doing this upgrade).
{{Cmd|lbu ci}}

=== Load new kernel ===
In most cases you will need to reboot Alpine Linux (especially if there are changes in the kernel):
{{Cmd|sync
reboot}}

{{Note|If you know what you are doing, you might not need to reboot. But make sure that all services affected by the upgrade are restarted.}}

=== Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) ===
On Alpine 3.X and newer, kernel is not upgraded when using <code>apk upgrade</code> and <code>setup-bootable</code> does not work properly.

If you want to upgrade your kernel, you will need to get it from the latest release, but first you must have and run :
{{Cmd|apk update; apk version -l '<';
apk upgrade;
lbu ci;}}

So now all your packages are upgraded, you can upgrade your kernel.

1. We need to get some variables :
{{Cmd|. /etc/os-release;
. /etc/lbu/lbu.conf;
ARCH=$(cat /etc/apk/arch);}}

2. You '''must''' verify if they are correctly set, using this :
{{Cmd|echo "alpine version : $VERSION_ID";
echo "lbu media : $LBU_MEDIA";
echo "arch : $ARCH"}}

3. And it will output something like this (if not, do not continue this process) :
{{Cmd|alpine version : 3.13.5
lbu media : mmcblk0p1
arch : armhf}}

4. Then you can run this script (WARNING : config.txt will be overwritten!) :
{{Cmd|cd /media/$LBU_MEDIA;
mount -oremount,rw /media/$LBU_MEDIA;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz</nowiki>;
wget <nowiki>https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256</nowiki>;
sha256sum -c *.sha256;
rm /media/$LBU_MEDIA/cache/*;
tar xzf alpine-rpi-$VERSION_ID-$ARCH.tar.gz;
rm alpine-rpi-$VERSION_ID-$ARCH.tar.gz alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256;
sync;
reboot;}}

5. Test-it !
{{Cmd|uname -a}}

6. Re-download cached apk :
{{apk update && apk cache -v download}}

=== Update local package installations ===

This is done just as at [[#Update local package installations]], above.

== Updating a USB/CF diskless install without setup-bootable ==
It is possible to update a diskless install of Alpine from another system, or without using the setup-bootable script. This was tested for the 3.13 to the 3.14 upgrade on a Raspberry Pi.

Before starting, update /etc/apk/repositories file to retrieve packages for the new release. Then update all packages with:
{{Cmd|apk update && apk upgrade -i -a --update-cache}}

We can then use update-conf to check for changes to configurations from the new packages.
{{Cmd|# check apk-new config changes
update-conf -a -l
update-conf -a
}}

We now need to prepare to update the kernel and boot materials. To do this, we stop the modloop (which is the loopback mount providing kernel modules) and remount the SD media as read/write.

We can also shutdown the system, eject the media, and perform the next steps on another machine (if so, skip this command block)

{{Cmd|/etc/init.d/modloop stop
mount /media/mmcblk0p1 -o remount,rw
cd /media/mmcblk0p1
}}

At this point, remove all files from the SD media '''except for /cache, *.apkvol.tar.gz, usercfg.txt, and config.txt''' Rename config.txt to config.txt.bak temporarily, as extracting the new tar file will overwrite the file.

We can now download the new release and extract it. This example is for an Alpine Raspberry Pi release, so feel free to adjust the URLs for your system.

{{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz.sha256
wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz
sha256sum -c *.sha256
tar zxf *-aarch64.tar.gz && sync
rm alpine-rpi-*
}}

Restore the original config.txt:
{{Cmd|mv config.txt.bak config.txt}}

Update the persistent storage using lbu:
{{Cmd|lbu ci -d}}

We can now reboot, and this should boot into the new kernel. Once this is done, we can clean up and re-download apk caches:
{{Cmd|mount /media/mmcblk0p1 -o remount,rw
rm /media/mmcblk0p1/cache/*
sync && apk update && apk cache -v download
mount /media/mmcblk0p1 -o remount,ro
}}

[[Category:Installation]]
[[Category:Package Manager]]

Odroid-C2

2022-03-22T19:45:59Z

Yuu:

Alpine on ARM

2022-03-20T16:01:06Z

Yuu: Added link to internal guide to install Alpine on the Odroid-C2

{{TOC right}}
{{Style}}
{{Move|ARM SOCs}}

(Parts of this page are WIP, still incomplete and some might be incorrect.)

==Supported SoCs==

Currently Alpine supports armv6/armhf arch on the following SoCs

(This is taken from the DTBs which Alpine includes)

{| class="wikitable collapsible"
| am335x-base0033
| am335x-bone
| am335x-boneblack
| am335x-evm
| am335x-evmsk
| am335x-nano
| am335x-pepper
| am3517-craneboard
| am3517-evm
| am3517_mt_ventoux
| am437x-gp-evm
|-
| am437x-sk-evm
| am43x-epos-evm
| exynos4210-origen
| exynos4210-smdkv310
| exynos4210-trats
| exynos4210-universal_c210
| exynos4412-odroidu3
| exynos4412-odroidx
| exynos4412-odroidx2
| exynos4412-origen
| exynos4412-smdk4412
| exynos4412-tiny4412
|-
| exynos4412-trats2
| exynos5250-arndale
| exynos5250-smdk5250
| exynos5250-snow
| exynos5260-xyref5260
| exynos5410-smdk5410
| exynos5420-arndale-octa
| exynos5420-peach-pit
| exynos5420-smdk5420
| exynos5440-sd5v1
| exynos5440-ssdk5440
| exynos5800-peach-pi
|-
| imx1-ads
| imx1-apf9328
| imx25-eukrea-mbimxsd25-baseboard-cmo-qvga
| imx25-eukrea-mbimxsd25-baseboard-dvi-svga
| imx25-eukrea-mbimxsd25-baseboard-dvi-vga
| imx25-eukrea-mbimxsd25-baseboard
| imx25-karo-tx25
| imx25-pdk
| imx27-apf27
| imx27-apf27dev
| imx27-eukrea-mbimxsd27-baseboard
| imx27-pdk
|-
| imx27-phytec-phycard-s-rdk
| imx27-phytec-phycore-rdk
| imx31-bug
| imx35-eukrea-mbimxsd35-baseboard
| imx35-pdk
| imx50-evk
| imx51-apf51
| imx51-apf51dev
| imx51-babbage
| imx51-digi-connectcore-jsk
| imx51-eukrea-mbimxsd51-baseboard
| imx53-ard
|-
| imx53-m53evk
| imx53-mba53
| imx53-qsb
| imx53-qsrb
| imx53-smd
| imx53-tx53-x03x
| imx53-tx53-x13x
| imx53-voipac-bsb
| imx6dl-aristainetos_4
| imx6dl-aristainetos_7
| imx6dl-cubox-i
| imx6dl-dfi-fs700-m60
|-
| imx6dl-gw51xx
| imx6dl-gw52xx
| imx6dl-gw53xx
| imx6dl-gw54xx
| imx6dl-gw552x
| imx6dl-hummingboard
| imx6dl-nitrogen6x
| imx6dl-phytec-pbab01
| imx6dl-rex-basic
| imx6dl-riotboard
| imx6dl-sabreauto
| imx6dl-sabrelite
|-
| imx6dl-sabresd
| imx6dl-tx6dl-comtft
| imx6dl-tx6u-801x
| imx6dl-tx6u-811x
| imx6dl-wandboard-revb1
| imx6dl-wandboard
| imx6q-arm2
| imx6q-cm-fx6
| imx6q-cubox-i
| imx6q-dfi-fs700-m60
| imx6q-dmo-edmqmx6
| imx6q-gk802
|-
| imx6q-gw51xx
| imx6q-gw52xx
| imx6q-gw53xx
| imx6q-gw5400-a
| imx6q-gw54xx
| imx6q-gw552x
| imx6q-hummingboard
| imx6q-nitrogen6x
| imx6q-phytec-pbab01
| imx6q-rex-pro
| imx6q-sabreauto
| imx6q-sabrelite
|-
| imx6q-sabresd
| imx6q-sbc6x
| imx6q-tx6q-1010-comtft
| imx6q-tx6q-1010
| imx6q-tx6q-1020-comtft
| imx6q-tx6q-1020
| imx6q-tx6q-1110
| imx6q-udoo
| imx6q-wandboard-revb1
| imx6q-wandboard
| imx6sl-evk
| imx6sx-sdb
|-
| armada-3720-espressobin-v7-emmc
|-
| omap3-beagle-xm-ab
| omap3-beagle-xm
| omap3-beagle
| omap3-cm-t3517
| omap3-cm-t3530
| omap3-cm-t3730
| omap3-devkit8000
| omap3-evm-37xx
| omap3-evm
| omap3-gta04a3
| omap3-gta04a4
| omap3-gta04a5
|-
| omap3-ha-lcd
| omap3-ha
| omap3-igep0020
| omap3-igep0030
| omap3-ldp
| omap3-lilly-dbb056
| omap3-n9
| omap3-n900
| omap3-n950
| omap3-overo-alto35
| omap3-overo-chestnut43
| omap3-overo-gallop43
|-
| omap3-overo-palo43
| omap3-overo-storm-alto35
| omap3-overo-storm-chestnut43
| omap3-overo-storm-gallop43
| omap3-overo-storm-palo43
| omap3-overo-storm-summit
| omap3-overo-storm-tobi
| omap3-overo-summit
| omap3-overo-tobi
| omap3-sbc-t3517
| omap3-sbc-t3530
| omap3-sbc-t3730
|-
| omap3-thunder
| omap3-zoom3
| omap3430-sdp
| omap4-duovero-parlor
| omap4-panda-a4
| omap4-panda-es
| omap4-panda
| omap4-sdp-es23plus
| omap4-sdp
| omap4-var-dvk-om44
| omap4-var-stk-om44
| omap5-cm-t54
|-
| omap5-sbc-t54
| omap5-uevm
| qcom-apq8064-cm-qs600
| qcom-apq8064-ifc6410
| qcom-apq8074-dragonboard
| qcom-apq8084-ifc6540
| qcom-apq8084-mtp
| qcom-ipq8064-ap148
| qcom-msm8660-surf
| qcom-msm8960-cdp
| qcom-msm8974-sony-xperia-honami
| sun4i-a10-a1000
|-
| sun4i-a10-ba10-tvbox
| sun4i-a10-cubieboard
| sun4i-a10-hackberry
| sun4i-a10-inet97fv2
| sun4i-a10-mini-xplus
| sun4i-a10-olinuxino-lime
| sun4i-a10-pcduino
| sun5i-a10s-olinuxino-micro
| sun5i-a10s-r7-tv-dongle
| sun5i-a13-hsg-h702
| sun5i-a13-olinuxino-micro
| sun5i-a13-olinuxino
|-
| sun6i-a31-app4-evb1
| sun6i-a31-colombus
| sun6i-a31-hummingbird
| sun6i-a31-m9
| sun7i-a20-cubieboard2
| sun7i-a20-cubietruck
| sun7i-a20-hummingbird
| sun7i-a20-i12-tvbox
| sun7i-a20-olinuxino-lime
| sun7i-a20-olinuxino-micro
| sun7i-a20-pcduino3
| sun8i-a23-ippo-q8h-v5
|-
| vexpress-v2p-ca15-tc1
| vexpress-v2p-ca15_a7
| vexpress-v2p-ca5s
| vexpress-v2p-ca9
| vf610-colibri-eval-v3
| vf610-cosmic
| vf610-twr
|}

==Install Alpine on supported SoCs==

=== Generic information ===

(If anyone has one of the above devices and has successfully installed Alpine on it, please consider adding the missing info here.)

==== Example with Wandboard ====

===== Get latest Alpine image =====
Download the last Generic ARM image on https://alpinelinux.org/downloads/
Extract the archive somewhere.

===== Prepare SD Card =====
First install SPL and u-boot.img (this could change for other board):
in root, write the SPL from Alpine extracted files :
dd if=u-boot/wandboard/SPL of=/dev/sdX seek=1 bs=1k
and the u-boot.img :
dd if=u-boot/wandboard/u-boot.img of=/dev/sdX seek=69 bs=1k

After create the partition on the sd-card with fdisk, then copy folders apks/ boot/ efi/ extlinux/ u-boot/ to the sd-card partition. (I'm not sure all folder as useful).

After you can put the sd-card in the Wandboard and boot it with serial console connected. 
The board should boot on the sd-card. When the prompt ask a login, enter 'root'.
Then launch 'setup-alpine' to configure the system.

=== Specific guides ===

* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [[Raspberry_Pi]]
* [[Raspberry_Pi_4_-_Persistent_system_acting_as_a_NAS_and_Time_Machine]]
* [[Odroid-C2]]

==Unupported SoCs==

If you have an armv6/armv7 SoC which is not listed above but is supported by mainline uboot/kernel then it's still possible to install Alpine

===Requiremnets===

* Alpine's forked uboot to support tarballs (fabled?)
* serial console
* crosscompiler/toolchain if you can not compile natively

===The embedded world===

A lot of the SoCs have their own way of doing things, although they use uboot and Linux kernel but often they are heavily modified to suit easy flashing of "ROMs" or other unknown reasons, e.g. Rockchip's notion "partition" are neither DOS nor GPT partitions.
We will discuss to install Alpine in a more standard way like x86 with either DOS or GPT partitions. You will most likely have to install/flash the mainline uboot, which can be non-destructive if you use external storage.

====Storage====

One can load uboot from the following block devices if it's supported.
* NAND
* eMMC
* SD card
* USB

====Power on====

Some SoCs need both SPL and uboot, you need to check uboot for your board. Most (if not all) boards boots from the internal storage first (either NAND or eMMC) you will have to check documentation of your board if you wish to boot the SPL/uboot from SD/USB.

One can view SPL+uboot as BIOS and boot-loader on PC. Think that you could put the BIOS on an external storage :D

Once you have loaded the "standard" uboot, things are more or less like on x86.

====Partitioning====

Either DOS or GPT patitions should work. Start of the first partition should be on block 2048 so there is space for SPL/uboot and marked bootable (with
the MBR bootable flag, or GPT legacy_bios_bootable attribute).
* SPL starts at block 64 (please consult the docs for your board)
* uboot starts at block 256 (please consult the docs for your board)
Just dd SPL and boot with the correct offset to the media you wish to boot

====Booting Linux kernel====

* uboot uses extlinux.conf file to locate the kernel/initramfs/... just like syslinx, you need to put that file on the partitions which is marked bootable in the /boot directory
* there should be an extra line "FDTDIR" which points to the DTBs
e.g.
<pre>
label Fedora (3.17.0-0.rc4.git2.1.fc22.armv7hl) 22 (Rawhide)
kernel /boot/vmlinuz-3.17.0-0.rc4.git2.1.fc22.armv7hl
append ro root=UUID=8eac677f-8ea8-4270-8479-d5ddbb797450 console=ttyS0,115200n8 LANG=en_US.UTF-8 drm.debug=0xf
fdtdir /boot/dtb-3.17.0-0.rc4.git2.1.fc22.armv7hl
initrd /boot/initramfs-3.17.0-0.rc4.git2.1.fc22.armv7hl.img
</pre>

==Using QEMU==

<pre>
qemu-system-arm -M vexpress-a9 -kernel zImage -initrd initramfs-grsec -dtb vexpress-v2p-ca9.dtb -hda hda.img -serial stdio
</pre>

== References ==

* [http://www.armadeus.org/wiki/index.php?title=Kernel-with-device-tree dtb (Device Tree Binary)]
* [https://forum.odroid.com/viewtopic.php?t=30459 Odroid-C2] 2018 ''([https://archlinuxarm.org/platforms/armv8/amlogic/odroid-c2 ARMv8, AArch64]; [https://forum.odroid.com/viewtopic.php?f=138&t=32608 Alpine Linux custom build])''
* [https://cusdeb.com/ CusDeb.com] - bootstrap SD-card images for single-board computers online; ''([https://github.com/tolstoyevsky/pieman Pieman])''
* [https://kernelci.org/soc/ <s>Available</s> SoCs]

[[Category:Hardware]]
[[category:ARM]]

Odroid-C2

2022-03-19T10:30:06Z

Yuu:

Odroid-C2

2022-03-19T10:15:25Z

Yuu:

Odroid-C2

2022-03-19T10:05:32Z

Yuu:

Odroid-C2

2022-03-19T10:05:13Z

Yuu: Alpine/Linux support for Odroid-C2

Upgrading Alpine Linux to a new release branch

2021-08-29T15:28:33Z

Yuu: /* Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) */

This page covers upgrading to newer releases.

Doing regular security updates with the package manager is shown at [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading a running system]].

{{Warning|Before actually upgrading your system, make sure that you have a backup of your important data.}}

== Upgrading an Alpine Linux Hard-disk installation ==

=== Upgrading from older versions ===

In case an older version needs to be upgraded, i.e. not just upgrading from the last release to the subsequent version as covered by the individual release notes, also check [[Upgrading from older versions]] for potential specifically required upgrade steps.

=== Upgrading to latest release ===

When Alpine Linux is installed in '''sys''' mode, e.g. on a hard drive, upgrading to the next stable version should be a straightforward package manager operation. However, for specific info always refer to the appropriate release notes.

{{:Include:Upgrading to latest release}}

=== Upgrading to Edge ===
{{:Include:Upgrading to Edge}}

== Upgrading Alpine Linux on CD ==

=== Boot media ===

If the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO.

If booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box.

=== Update local package installations ===

If you have locally installed and configured additional packages using [[How_to_enable_APK_caching|APK caching]] you should also perform the following steps.

Backup the local configuration prior to upgrading.
{{Cmd|lbu ci}}

{{:Include:Upgrading to latest release}}

After upgrading the packages, save the upgraded configuration changes.
{{Cmd|lbu ci}}

== Upgrading Alpine Linux on other removable media (such as CF/USB) ==

The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Updating your repositories using [[#Upgrading_an_Alpine_Linux_Hard-disk_installation|the procedures detailed above]], then running:
{{Cmd|apk upgrade --update-cache --available}}
will suffice for some purposes. (If you want the new packages to be used after a reboot, you should [[How_to_enable_APK_caching|enable APK caching]].)

However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). That is what the following steps describe how to do.

{{:Include:Upgrading_Alpine_environmentvars}}

=== Upgrade Operating System ===

Start by checking that you have enough space on your media. For a '''standard''' Alpine image, you need at least 400MB available space.
{{Cmd|df -h {{!}} grep "Filesystem\{{!}}$LBU_MEDIA"}}

==== Download and verify new release ====

Make sure the media that holds your Alpine system is mounted readwrite.
{{Cmd|mount -oremount,rw /media/$LBU_MEDIA}}

'''If using Alpine Linux 2.2.3 or newer''': Download the latest release, {{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/<arch>/<image>.iso}} and then use the following command to mount and copy files as needed for you: {{Cmd|setup-bootable -u alpine-extended-<version>-<arch>.iso /media/$LBU_MEDIA}} Once the command completes, proceed to the [[#Save changes|Save changes]] section.

==== For older versions of Alpine ====
Start downloading a new '.iso' and a '.sha1' file
{{Cmd|cd /media/$LBU_MEDIA
wget -c {{#latestalp:alpine|url}}
wget {{#latestalp:alpine|url}}.sha1}}

Check integrity of the downloaded files ''(it might take some time)'':
{{Cmd|sha1sum -c {{#latestalp:alpine|file}}.sha1}}
''The output of the above command should say 'OK'. ''
''If says 'FAILED', delete the iso file and download it again.''

'''If using Alpine Linux 1.10.4 or newer''': there is a tool ''setup-bootable'' that will mount and copy the image you just downloaded to your boot medium. With this tool simply do: {{Cmd|setup-bootable -u {{#latestalp:alpine|file}} /media/$LBU_MEDIA}}

[[Upgrading from older versions#Upgrading_a_removable_medium_from_Alpine_before_1.10.4|Instructions for older versions of Alpine]] are located elsewhere.

=== Save changes ===
Now that all upgrades are done, we should save our settings to our media (which you hopefully have backed up prior to doing this upgrade).
{{Cmd|lbu ci}}

=== Load new kernel ===
In most cases you will need to reboot Alpine Linux (especially if there are changes in the kernel):
{{Cmd|sync
reboot}}

{{Note|If you know what you are doing, you might not need to reboot. But make sure that all services affected by the upgrade are restarted.}}

=== Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) ===
On Alpine 3.X and newer, kernel is not upgraded when using <code>apk upgrade</code> and <code>setup-bootable</code> does not work properly.

If you want to upgrade your kernel, you will need to get it from the latest release, but first you must have and run :
{{Cmd|apk update; apk version -l '<';
apk upgrade;
lbu ci;}}

So now all your packages are upgraded, you can upgrade your kernel.

1. We need to get some variables :
{{Cmd|. /etc/os-release;
. /etc/lbu/lbu.conf;
ARCH=$(cat /etc/apk/arch);}}

2. You '''must''' verify if they are correctly set, using this :
{{Cmd|echo "alpine version : $VERSION_ID";
echo "lbu media : $LBU_MEDIA";
echo "arch : $ARCH"}}

3. And it will output something like this (if not, do not continue this process) :
{{Cmd|alpine version : 3.13.5
lbu media : mmcblk0p1
arch : armhf}}

4. Then you can run this script (WARNING : config.txt will be overwritten!) :
{{Cmd|cd /media/$LBU_MEDIA;
mount -oremount,rw /media/$LBU_MEDIA;
wget https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz;
wget https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/$ARCH/alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256;
sha256sum -c *.sha256;
tar xzf alpine-rpi-$VERSION_ID-$ARCH.tar.gz;
rm alpine-rpi-$VERSION_ID-$ARCH.tar.gz alpine-rpi-$VERSION_ID-$ARCH.tar.gz.sha256;
sync;
reboot;}}

5. Test-it !
{{Cmd|uname -a}}

=== Update local package installations ===

This is done just as at [[#Update local package installations]], above.

== Updating a USB/CF diskless install without setup-bootable ==
It is possible to update a diskless install of Alpine from another system, or without using the setup-bootable script. This was tested for the 3.13 to the 3.14 upgrade on a Raspberry Pi.

Before starting, update /etc/apk/repositories file to retrieve packages for the new release. Then update all packages with:
{{Cmd|apk update && apk upgrade -i -a --update-cache}}

We can then use update-conf to check for changes to configurations from the new packages.
{{Cmd|# check apk-new config changes
update-conf -a -l
update-conf -a
}}

We now need to prepare to update the kernel and boot materials. To do this, we stop the modloop (which is the loopback mount providing kernel modules) and remount the SD media as read/write.

We can also shutdown the system, eject the media, and perform the next steps on another machine (if so, skip this command block)

{{Cmd|/etc/init.d/modloop stop
mount /media/mmcblk0p1 -o remount,rw
cd /media/mmcblk0p1
}}

At this point, remove all files from the SD media '''except for /cache, *.apkvol.tar.gz, usercfg.txt, and config.txt''' Rename config.txt to config.txt.bak temporarily, as extracting the new tar file will overwrite the file.

We can now download the new release and extract it. This example is for an Alpine Raspberry Pi release, so feel free to adjust the URLs for your system.

{{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz.sha256
wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/aarch64/alpine-rpi-3.13.0-aarch64.tar.gz
sha256sum -c *.sha256
tar zxf *-aarch64.tar.gz && sync
rm alpine-rpi-*
}}

Restore the original config.txt:
{{Cmd|mv config.txt.bak config.txt}}

Update the persistent storage using lbu:
{{Cmd|lbu ci -d}}

We can now reboot, and this should boot into the new kernel. Once this is done, we can clean up and re-download apk caches:
{{Cmd|mount /media/mmcblk0p1 -o remount,rw
rm /media/mmcblk0p1/cache/*
sync && apk update && apk cache -v download
mount /media/mmcblk0p1 -o remount,ro
}}

[[Category:Installation]]
[[Category:Package Manager]]

Upgrading Alpine Linux to a new release branch

2021-05-13T10:38:59Z

Yuu: /* Upgrading Alpine Linux on other removable media (such as CF/USB) */

This page covers upgrading to newer releases.

Doing regular security updates with the package manager is shown at [[Alpine_Linux_package_management#Upgrade_a_Running_System|Upgrading a running system]].

{{Warning|Before actually upgrading your system, make sure that you have a backup of your important data.}}

== Upgrading an Alpine Linux Hard-disk installation ==

=== Upgrading Alpine v2.x to v3.x ===

{{Warning|Alpine Linux 3.x switched to a different libc implementation compared to previous versions. Because the new Musl libc is not ABI compatible with uClibc, there are additional steps required for an upgrade.}}

==== Installing statically linked tools ====

Statically linked version of apk-tools is needed, because the old musl version would stop working after a libc change (possibly in the middle of upgrade). Static version of busybox can be handy in case of the recovery from a failure.

{{Cmd|apk add busybox-static apk-tools-static}}

==== Changing repositories to v3.x ====

To begin, you need to update your {{Path|/etc/apk/repositories}} file. Here are some shortcuts for doing so:
:* Launch {{Cmd|setup-apkrepos}} Enter {{Key|e}} to edit {{Path|/etc/apk/repositories}}. Change the version number by hand.
:* Or, edit the file in place. This is how you'd change <var>v2.7</var> to <var>v3.0</var>: {{Cmd|sed -i -e 's/<var>v2\.7</var>/<var>v3.0</var>/g' /etc/apk/repositories}}

==== Upgrading system ====

Use statically linked version of apk to update content of repository:

{{Cmd|apk.static update}}

Simulating upgrade is recommended in order to detect issues beforehand:

{{Cmd|apk.static upgrade --no-self-upgrade --available --simulate}}

With no problems encountered or after resolving them, start proper upgrade:

{{Cmd|apk.static upgrade --no-self-upgrade --available}}

=== Upgrading to latest release ===
{{:Include:Upgrading to latest release}}

=== Upgrading to Edge ===
{{:Include:Upgrading to Edge}}

=== Upgrading from older versions ===

See [[Upgrading from older versions]].

== Upgrading Alpine Linux on CD ==

You may have an installation where the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information. In this case, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO. If you are booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box.

=== Update remaining packages from Web repository ===

If you are using [[How_to_enable_APK_caching|APK caching]] you should also perform the following steps.
{{:Include:Using_Internet_Repositories_for_apk-tools}}

If you're upgrading from a version of Alpine before 2.3.0_rc1, ensure you have the latest available version of the Alpine Linux Package Manager first before upgrading anything else:
{{Cmd|apk add --upgrade apk-tools}}

Next, upgrade all your packages:

{{Cmd|apk upgrade --available
sync}}

The <code>--available</code> switch is used to force all packages to be upgraded, even if they have the same version numbers. Sometimes changes in uClibc require doing this.

After upgrading packages, save any configuration changes (you should have backed up your earlier configuration prior to upgrading).
{{Cmd|lbu ci}}

== Upgrading Alpine Linux on other removable media (such as CF/USB) ==

The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Updating your repositories using [[#Upgrading_an_Alpine_Linux_Hard-disk_installation|the procedures detailed above]], then running:
{{Cmd|apk upgrade --update-cache --available}}
will suffice for some purposes. (If you want the new packages to be used after a reboot, you should [[How_to_enable_APK_caching|enable APK caching]].)

However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). That is what the following steps describe how to do.

{{:Include:Upgrading_Alpine_environmentvars}}

=== Upgrade Operating System ===

Start by checking that you have enough space on your media. For a '''standard''' Alpine image, you need at least 400MB available space.
{{Cmd|df -h {{!}} grep "Filesystem\{{!}}$LBU_MEDIA"}}

==== Download and verify new release ====

Make sure the media that holds your Alpine system is mounted readwrite.
{{Cmd|mount -oremount,rw /media/$LBU_MEDIA}}

'''If using Alpine Linux 2.2.3 or newer''': Download the latest release, {{Cmd|wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/<arch>/<image>.iso}} and then use the following command to mount and copy files as needed for you: {{Cmd|setup-bootable -u alpine-extended-<version>-<arch>.iso /media/$LBU_MEDIA}} Once the command completes, proceed to the [[#Save changes|Save changes]] section.

==== For older versions of Alpine ====
Start downloading a new '.iso' and a '.sha1' file
{{Cmd|cd /media/$LBU_MEDIA
wget -c {{#latestalp:alpine|url}}
wget {{#latestalp:alpine|url}}.sha1}}

Check integrity of the downloaded files ''(it might take some time)'':
{{Cmd|sha1sum -c {{#latestalp:alpine|file}}.sha1}}
''The output of the above command should say 'OK'. ''
''If says 'FAILED', delete the iso file and download it again.''

'''If using Alpine Linux 1.10.4 or newer''': there is a tool ''setup-bootable'' that will mount and copy the image you just downloaded to your boot medium. With this tool simply do: {{Cmd|setup-bootable -u {{#latestalp:alpine|file}} /media/$LBU_MEDIA}}

[[Upgrading from older versions#Upgrading_a_removable_medium_from_Alpine_before_1.10.4|Instructions for older versions of Alpine]] are located elsewhere.

=== Save changes ===
Now that all upgrades are done, we should save our settings to our media (which you hopefully have backed up prior to doing this upgrade).
{{Cmd|lbu ci}}

=== Load new kernel ===
In most cases you will need to reboot Alpine Linux (especially if there are changes in the kernel):
{{Cmd|sync
reboot}}

{{Note|If you know what you are doing, you might not need to reboot. But make sure that all services affected by the upgrade are restarted.}}

=== Update to latest kernel on armhf (eg. Raspberry Pi 0 or 1) ===
On Alpine 3.X and newer, kernel is not upgraded when using <code>apk upgrade</code> and <code>setup-bootable</code> does not work properly.

If you want to upgrade your kernel, you will need to get it from the latest release, but first you must have and run :
{{Cmd|apk update; apk version -l '<';
apk upgrade;
lbu ci;}}

So now all your packages are upgraded, you can upgrade your kernel.

1. We need to get some variables :
{{Cmd|. /etc/os-release;
. /etc/lbu/lbu.conf;}}

2. You '''must''' verify if they are correctly set, using this :
{{Cmd|echo "alpine version : $VERSION_ID";
echo "lbu media : $LBU_MEDIA";}}

3. And it will output something like this (if not, do not continue this process) :
{{Cmd|alpine version : 3.13.5
lbu media : mmcblk0p1}}

4. Then you can run this script :
{{Cmd|cd /media/$LBU_MEDIA;
mount -oremount,rw /media/$LBU_MEDIA;
wget https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/armhf/alpine-rpi-$VERSION_ID-armhf.tar.gz;
wget https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/armhf/alpine-rpi-$VERSION_ID-armhf.tar.gz.sha256;
sha256sum -c *.sha256;
tar xzf alpine-rpi-$VERSION_ID-armhf.tar.gz;
rm alpine-rpi-$VERSION_ID-armhf.tar.gz alpine-rpi-$VERSION_ID-armhf.tar.gz.sha256;
sync;
reboot;}}

5. Test-it !
{{Cmd|uname -a}}

=== Update remaining packages from Web repository ===
If you are using [[How_to_enable_APK_caching|APK caching]] you should follow the instructions to [[#Update_remaining_packages_from_Web_repository|Update remaining packages from Web repository]], above.

[[Category:Installation]]
[[Category:Package Manager]]