I created my own experimental installer program that will download Armtix and put it on my
SD card with some server app that I like, so I won't have to configure all that next time
I want to have a second/third server of the same kind.
After finishing the install,
I put my SD card into my raspberry Pi and it shows nothing.
So obviously it's not booting.
I chose to have my installer create two partitions and have btrfs as the filesystem used for root and use fat32 for boot.
Then create two subpartitions for system folder and home.
Unless someone tells me otherwise, I do believe that's the best setup.
Below is my end result and I'm sure I've done things wrong.
Can anyone spot what I'm doing incorrectly?
$ lsblk
sdc 8:32 1 119,4G 0 disk
├─sdc1 8:33 1 480M 0 part /run/media/folaht/BASTIJ_SIN
└─sdc2 8:34 1 118,9G 0 part /run/media/folaht/BASTIJ_FUT
BASTIJ_SIN = boot partition
BASTIJ_FUT = root partition
$ ls -lha /run/media/folaht/BASTIJ_SIN
total 331M
drwxr-xr-x 4 folaht folaht 16K 1 jan 1970 .
drwxr-x---+ 4 root root 80 22 feb 10:15 ..
drwxr-xr-x 18 folaht folaht 8,0K 7 dec 18:48 dtbs
drwxr-xr-x 18 folaht folaht 8,0K 21 feb 12:02 dtbs-lts
-rw-r--r-- 1 folaht folaht 39M 15 feb 12:45 Image
-rw-r--r-- 1 folaht folaht 15M 15 feb 12:45 Image.gz
-rw-r--r-- 1 folaht folaht 93M 21 feb 13:10 initramfs-linux-fallback.img
-rw-r--r-- 1 folaht folaht 7,6M 21 feb 13:03 initramfs-linux.img
-rw-r--r-- 1 folaht folaht 49M 21 feb 13:02 initramfs-linux-lts-fallback.img
-rw-r--r-- 1 folaht folaht 71M 21 feb 12:21 initramfs-linux-lts-fallback.img.tmp
-rw-r--r-- 1 folaht folaht 7,7M 21 feb 12:55 initramfs-linux-lts.img
-rw-r--r-- 1 folaht folaht 39M 15 feb 16:14 ltsImage
-rw-r--r-- 1 folaht folaht 15M 15 feb 16:14 ltsImage.gz
$ ls -lha /run/media/folaht/BASTIJ_FUT1/@
total 28K
drwxr-xr-x 1 root root 112 21 feb 13:10 .
drwxr-xr-x 1 root root 12 21 feb 11:57 ..
lrwxrwxrwx 1 root root 7 26 nov 15:49 bin -> usr/bin
drwxr-xr-x 1 root root 0 21 feb 11:57 boot
drwxr-xr-x 1 root root 0 7 dec 18:47 dev
drwxr-xr-x 1 root root 1,8K 21 feb 13:10 etc
drwxr-xr-x 1 root root 0 21 feb 11:57 home
lrwxrwxrwx 1 root root 7 26 nov 15:49 lib -> usr/lib
drwxr-xr-x 1 root root 0 26 nov 15:49 mnt
drwxr-xr-x 1 root root 0 26 nov 15:49 opt
dr-xr-xr-x 1 root root 0 7 dec 18:47 proc
drwxr-x--- 1 root root 54 21 feb 13:10 root
drwxr-xr-x 1 root root 0 7 dec 18:47 run
lrwxrwxrwx 1 root root 7 26 nov 15:49 sbin -> usr/bin
drwxr-xr-x 1 root root 14 7 dec 18:47 srv
dr-xr-xr-x 1 root root 0 7 dec 18:47 sys
drwxrwxrwt 1 root root 0 7 dec 18:47 tmp
drwxr-xr-x 1 root root 60 7 dec 18:47 usr
drwxr-xr-x 1 root root 100 7 dec 18:47 var
Did you install uboot? Alternatively, if it's pi4 (or maybe pi5), you should configure its internal bootloader to load proper kernel file, initramfs and dtb
For debug purpose you need uart cable
Also, this thread should be moved to ARMtix board
No I did not install uboot.
I saw that the image had bootfiles readily available, so I simply moved them there
It IS a pi4.
$ ls -lha
total 305M
drwxr-xr-x 4 folaht folaht 4,0K 1 jan 1970 .
drwxr-x---+ 4 root root 80 23 feb 17:49 ..
-rw-r--r-- 1 folaht folaht 128 23 feb 17:46 command.txt
-rw-r--r-- 1 folaht folaht 131 23 feb 17:40 config.txt
drwxr-xr-x 18 folaht folaht 4,0K 7 dec 18:48 dtbs
drwxr-xr-x 18 folaht folaht 4,0K 23 feb 16:20 dtbs-lts
-rw-r--r-- 1 folaht folaht 39M 15 feb 12:45 Image
-rw-r--r-- 1 folaht folaht 15M 15 feb 12:45 Image.gz
-rw-r--r-- 1 folaht folaht 93M 23 feb 17:32 initramfs-linux-fallback.img
-rw-r--r-- 1 folaht folaht 7,6M 23 feb 17:25 initramfs-linux.img
-rw-r--r-- 1 folaht folaht 93M 23 feb 17:24 initramfs-linux-lts-fallback.img
-rw-r--r-- 1 folaht folaht 7,7M 23 feb 17:17 initramfs-linux-lts.img
-rw-r--r-- 1 folaht folaht 39M 15 feb 16:14 ltsImage
-rw-r--r-- 1 folaht folaht 15M 15 feb 16:14 ltsImage.gz
$ cat command.txt
console=ttyS1,115200 earlyprintk=serial,ttyS1,115200 root=/dev/mmcblk1p2 rw rootwait smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0
$ cat config.txt
enable_uart=1
arm_64bit=1
kernel=/Image
initramfs /initramfs-linux.img followkernel
device-tree=/dtbs/broadcom/bcm2711-rpi-4-b.dtb
https://info.armtixlinux.org/raspberrypi4.html
Then you need config.txt and cmdline.txt files and additional firmware packages from ALARM
How come ARMtix doesn't have these packages?
I see no problem using ALARM mirrors for ARM-specific packages if they have built ones