Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On Slackware current I have just downloaded the installer from SARPI :
sarpi4-installer_slackcurrent_08Oct20_sp1.img.xz
put in in a FAT32 partition ( the first partition of my SD card ; the other partitions are formatted under f2fs for /home and a partition forv swap ) by making
I have tried to reformat the partition and reput the installer but it is the same result
Where is the problem ?
I performed the exact same procedure as you did as you have described using a 16GB microSD card on a RPi4. here are my results:
Code:
root@torq:/tmp# xz -dc sarpi4-installer_slackcurrent_08Oct20_sp1.img.xz | dd of=/dev/sdb bs=65536
1+20472 records in
1+20472 records out
167772160 bytes (168 MB, 160 MiB) copied, 23.3295 s, 7.2 MB/s
root@torq:/tmp# fdisk -l /dev/sdb
Disk /dev/sdb: 14.91 GiB, 16009658368 bytes, 31268864 sectors
Disk model: STORAGE DEVICE
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: 0x01f4b6fe
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 32 312447 312416 152.5M c W95 FAT32 (LBA)
# After booting the new SD card image
login as: root
root@192.168.1.144's password:
Linux 5.4.70-v7l-sarpi4.
If you're upgrading an existing Slackware system, you might want to
remove old packages before you run 'setup' to install the new ones. If
you don't, your system will still work but there might be some old files
left laying around on your drive.
Just mount your Linux partitions under /mnt and type 'pkgtool'. If you
don't know how to mount your partitions, type 'pkgtool' and it will tell
you how it's done.
To partition your hard drive(s), use 'cfdisk' or 'fdisk'.
To start the main installation (after partitioning), type 'setup'.
root@slackware:~# fdisk -l
Disk /dev/mmcblk0: 14.91 GiB, 16009658368 bytes, 31268864 sectors
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: 0x01f4b6fe
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 32 312447 312416 152.5M c W95 FAT32 (LBA)
root@slackware:~# blkid
/dev/mmcblk0p1: LABEL_FATBOOT="rpi4-boot" LABEL="rpi4-boot" UUID="48DD-82A4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="01f4b6fe-01"
root@slackware:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.9G 0 disk
`-mmcblk0p1 179:1 0 152.5M 0 part
root@slackware:~#
For me it's working as intended. No problems whatsoever.
The reason why there is only one [FAT] partition in the SARPi images is because the Raspberry Pi won't boot without it. Otherwise there would be no [zero] partitions. Unlike Raspbian where the partitions are already created and part of the disk image, it's not the same for the Slackware ARM installer images I create with SARPi. I want users to be forced to create their own partitions before running Slackware 'setup' to suit their individual requirements, rather than decide it for them. This mentality is not limited to setting up partitions but is a general theme I maintain in-line with the 'Slackware way' - or as close as humanly possible. By doing so I hope to offer new users some knowledge and experience they might not otherwise attain, and open doors to areas that are not always addressed in other Linux distros. Rather than a pre-installed image, I want Slackware ARM on a Raspberry Pi users to be exposed to the FULL experience of installing and configuring the Slackware ARM system. Warts and all!
So, on to your FAT partition issue. The /boot [FAT] partition has to be a certain filesystem type in order to boot. The first rule is that it _MUST_ be FAT32 because that's what the proprietary bootloader firmware is designed to work with. If it's anything else it probably won't work. You may use 'fdisk' or 'cfdisk' commands to check and change the filesystem type. If your FAT partition is not type 'b W95 FAT32 ' or 'c W95 FAT32 (LBA)' then this is where the cause of the problem may be. NB: you might also be successful booting with a type '7 HPFS/NTFS/exFAT' filesystem.
I'm not sure if it matters that the FAT partition is the first on the list before all other partitions but I always make sure it is because I know it works. I also do not ever create more than one FAT partition, with /boot as the only FAT partition. All other partitions are usually EXT4 filesystem type.
So, on to your FAT partition issue. The /boot [FAT] partition has to be a certain filesystem type in order to boot. The first rule is that it _MUST_ be FAT32 because that's what the proprietary bootloader firmware is designed to work with. If it's anything else it probably won't work. You may use 'fdisk' or 'cfdisk' commands to check and change the filesystem type. If your FAT partition is not type 'b W95 FAT32 ' or 'c W95 FAT32 (LBA)' then this is where the cause of the problem may be. NB: you might also be successful booting with a type '7 HPFS/NTFS/exFAT' filesystem.
I'm not sure if it matters that the FAT partition is the first on the list before all other partitions but I always make sure it is because I know it works. I also do not ever create more than one FAT partition, with /boot as the only FAT partition. All other partitions are usually EXT4 filesystem type.
I have created this partition of type FAT32 by gparted but after "dding" the SARPI installer on partition 1, I have run "fdisk -l" to see the result of the command :
I saw :
/dev/mmc...p1 * b W95 FAT32
So this partition is well formatted in FAT 32 : why the RPI does not see it ?
Is it related with the 'extended partition" ? Perhaps the firmware does not recognize it and does know where the FAT 32 is ending ?
I have created this partition of type FAT32 by gparted but after "dding" the SARPI installer on partition 1, I have run "fdisk -l" to see the result of the command :
I saw :
/dev/mmc...p1 * b W95 FAT32
So this partition is well formatted in FAT 32 : why the RPI does not see it ?
Is it related with the 'extended partition" ? Perhaps the firmware does not recognize it and does know where the FAT 32 is ending ?
I can try to make only primary partitions
If you would post your full partition list it may reveal something I'm not apprised of at this time. Really not sure why you're having problems with the FAT partition.
Code:
~# fdisk -l
I create primary partitions only for /boot, /swap and root /. I never create extended partitions as I have no use for them. You might like to do some testing to see what works and post your findings here. I'm sure others would benefit from any experience and knowledge you care to share in this area.
Last edited by Exaga; 10-16-2020 at 05:07 AM.
Reason: raindrops keep falling on my head
Finally formatting my SD card with Rufus, I have succedded to boot on the RPI4.
I have well booted and after creating :
- a swap partition with 512 Mo
- an F2FS partition for the system
I have launched the Slackware installation following the instructions of the SARPI web site.
Everything works fine including the suppression of the kernel and kernel modules, installation of the modified kernel and kernel modules
suppression of the initrd.gz , unmouting of the USB key and ... reboot
At the beginning of the boot, all the CPUs are stopping and there is a kernel panic !!!!!!!! ( see attached image )
What is happening ?
Quote:
Originally Posted by Exaga
If you would post your full partition list it may reveal something I'm not apprised of at this time. Really not sure why you're having problems with the FAT partition.
Code:
~# fdisk -l
I create primary partitions only for /boot, /swap and root /. I never create extended partitions as I have no use for them. You might like to do some testing to see what works and post your findings here. I'm sure others would benefit from any experience and knowledge you care to share in this area.
At the beginning of the boot, all the CPUs are stopping and there is a kernel panic !!!!!!!! ( see attached image )
What is happening ?
No apologies for stating the obvious... and your root partition is AWOL. From your screenshot it looks like the kernel is fine but when it comes to loading the OS it can't find the root partition, where it should be located, and that's where it panics.
This error might be caused by any number of factors. Such as (but not limited to); the root partition does not exist, the root partition entry in /etc/fstab points to a different location or is in error, the 'root=' and 'rootfstype=' parameters in /boot/cmdline.txt file point to a different location or the rootfstype is not specified correctly and/either/or is in error, a setting in /boot/config.txt file is overriding the root partition setting. If the partition existed but there was no OS to load you would be receiving a different error.
So this one lies with the partition itself. Not with the OS. The kernel doesn't even try to load the OS because it can't find the root partition.
[EDIT] if you've followed the distructions on how to install Slackware ARM from the SARPi website correctly you would not be seeing this error. You've either done something extra to requirements or not done something required in order to produce this issue.
Last edited by Exaga; 11-09-2020 at 07:41 PM.
Reason: Jaffa cakes required!
No apologies for stating the obvious... and your root partition is AWOL. From your screenshot it looks like the kernel is fine but when it comes to loading the OS it can't find the root partition, where it should be located, and that's where it panics.
This error might be caused by any number of factors. Such as (but not limited to); the root partition does not exist, the root partition entry in /etc/fstab points to a different location or is in error, the 'root=' and 'rootfstype=' parameters in /boot/cmdline.txt file point to a different location or the rootfstype is not specified correctly and/either/or is in error, a setting in /boot/config.txt file is overriding the root partition setting. If the partition existed but there was no OS to load you would be receiving a different error.
So this one lies with the partition itself. Not with the OS. The kernel doesn't even try to load the OS because it can't find the root partition.
[EDIT] if you've followed the distructions on how to install Slackware ARM from the SARPi website correctly you would not be seeing this error. You've either done something extra to requirements or not done something required in order to produce this issue.
@Exaga I think I have found the origin of the problem : here is the cmdline.txt
The filesystem was originally formatted in ext4 but I have reformatted it in f2fs !
Why this has not be rewritten in cmdline.txt I do not know but if I replace ext4 by f2fs it should work !
Yes and the most annoying and sad thing about this is... it's got absolutely nothing to do with "RPI not booting with SARPI installer". Even if it were remotely "SARPi installer" related, the installation guide advises ext4 filesystem type.
If you are going to make fundamental changes to the OS without fully understanding the implications then it will be wise and prudent to investigate the potential ramifications beforehand. Given that we all learn from our mistakes, let this be one of yours.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
