OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> ArchLinuxARM Minimal RootFS, Experimental ArchLinuxARM rootfs for Sharp Zaurus C3x00
greguu
post Jan 12 2016, 01:18 AM
Post #1





Group: Moderators
Posts: 358
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



ArchLinuxARM RooFS Update:

Download: alarm-zaurus-c3x00-minimal-rootfs-february2018.tar.xz (200 MB)

ChangeLog:

- Based on http://archlinuxarm.org/os/ArchLinuxARM-armv5-latest.tar.gz (7th February 2018)
- updated to Linux 4.14.18
- added pccardctl, hostap-utils, dropbear, mc, tmux, screen, rsync, hostapd, wpa_supplicant

Quick Install Guide:

- Extract as root to a SD card formatted with ext4 using your favourite Linux distribution. (Min. 4GB SD card required).

Note : the ext4 needs to be created with e2fsprogs version <=1.43.9. Any version >=1.44 does create an fs not readable by 3.10.y kexecboot.

Note : Make sure you extract the tar.xz via a desktop / laptop linux computer and not on the Zaurus.
- Install arch-kexecboot from this github. Instructions included in the arch-kexeboot tar.
https://github.com/greguu/linux-3.10.y-c3x0...xec-r0/releases
- Enter rootfs SD card into Z and boot via kexecboot.
- Login to minimal alarm rootfs (user : root , password : root)
- Follow the Arch Guide and Wiki to complete your setup. https://wiki.archlinux.org
- Create a private key for Dropbear SSH client/server:
dropbearkey -t rsa -f /etc/dropbear/dropbear_rsa_host_key
- Extract the roofs to the internal CF drive and change /boot/boot.cfg and /etc/fstab to match your layout.
- Create a swap partition if needed

Instructions:

More detailed instructions (but a bit outdated) can be found here. (Thanks Danboid) https://github.com/greguu/ZALARM-install

C1000/Akita:

This roofs may also work on your C1000/Akita. See this post for more details: C1000/Akita

This post has been edited by greguu: Apr 7 2018, 01:10 AM
Go to the top of the page
 
+Quote Post
linx
post Apr 6 2018, 05:48 AM
Post #2





Group: Members
Posts: 13
Joined: 17-March 08
Member No.: 21,518



I don't know if this post is meant for support. Feel free to move the reply. I extracted the rootfs to an SD card but kexec fails to mount it. debug info shows that it recognized ext4 as a filesystem but next command which is supposed to mount the card for the menu to appear fails "can't mount /dev/mmcblk0p1 invalid arguments". It doesn't fail on the micro harddrive of the c3200 where I have a previous rootfs installed with kernel 4.4.0. Any info on why this happens and what to do? I tried two cards one 2gb and a 16gb, both show the same error. After I'm booted in the previous rootfs from the hard drive I can mount the sd card without any problems. Thanks for the info.
Go to the top of the page
 
+Quote Post
greguu
post Apr 6 2018, 05:05 PM
Post #3





Group: Moderators
Posts: 358
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



QUOTE(linx @ Apr 7 2018, 02:48 AM) *
I don't know if this post is meant for support. Feel free to move the reply. I extracted the rootfs to an SD card but kexec fails to mount it. debug info shows that it recognized ext4 as a filesystem but next command which is supposed to mount the card for the menu to appear fails "can't mount /dev/mmcblk0p1 invalid arguments". It doesn't fail on the micro harddrive of the c3200 where I have a previous rootfs installed with kernel 4.4.0. Any info on why this happens and what to do? I tried two cards one 2gb and a 16gb, both show the same error. After I'm booted in the previous rootfs from the hard drive I can mount the sd card without any problems. Thanks for the info.


Hi linx,

there maybe something wrong with the file-system and/or partition on that card(s). If kexec can not mount it, maybe try a "fsck" on the partition or start from scratch if that does not fix it (re-partition the card and mkfs.ext4 /dev/mmcblk0p1). If you use the kexecboot kernel 3.10.y on a C3200 it should be able to mount and boot ext2/3/4 and f2fs file-systems from CF and SD. The issue is unlikely related to the rootfs itself. Do you have another card you can try with ? When mounting the card from within a running arch session, do you get any errors in your "dmesg" ?

Greguu
Go to the top of the page
 
+Quote Post
greguu
post Apr 7 2018, 01:18 AM
Post #4





Group: Moderators
Posts: 358
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



Hi,

Thanks for reporting the issue, linx.

After some troubleshooting it was determined that the issue is with the kexecboot version used in kernel 3.10.y and any ext4 file system created with e2fsprogs version >=1.43.9.

Check your e2fsprogs version (mke2fs -V) before creating a rootfs filesystem. If ex2fsprogs is <=1.43.9 then you should be fine.

Alternatively, use ext3 or f2fs. (remember to update boot.cfg and fstab accordingly in this case)

We will work on a new kexecboot kernel that can mount newer ext4 properly.

Cheers,

Greguu
Go to the top of the page
 
+Quote Post
greguu
post May 23 2018, 12:52 AM
Post #5





Group: Moderators
Posts: 358
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



Update: If the file system is to be created with a newer e2fsprogs version, exclude the metadata checksum feature. The ext4 fs will then work fine with kexecboot.

Example:
CODE
mkfs.ext4 /dev/sdc1 -O^metadata_csum

Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st August 2019 - 03:28 PM