You are not logged in.
Pages: 1
* On machine with little memory, set iommu=off in your kernel boot parameters to get some extra 64 MB RAM back.
* When creating an ext4-filesystem switch off the 64-bit option if you don't have big harddisks (which you usually don't
have on those machines anyway): mkfs.ext4 -O ^64bit /dev/sda1
Offline
What is the partition limit for 32-bit ext4? I should probably remake my partitions when I jiggle them about to get my /usr off this 7.9GB disc, but I'm wondering about my 105GB /home/ partition
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Offline
* When creating an ext4-filesystem switch off the 64-bit option if you don't have big harddisks (which you usually don't
have on those machines anyway): mkfs.ext4 -O ^64bit /dev/sda1
Can this be done after creating the partition with tune2fs also? What difference does it make? I think these notes should be included in the top of https://archlinux32.org/download/ as well.
Last edited by egils (2020-08-31 22:15:27)
Offline
Yes, according to tune2fs's man page, the 64bit FS option can be cleared using it on a pre-formatted ext filesystem. It doesn't say to use fsck after setting it, but I'd be tempted to. It should only save you a couple of bytes of directory info per file, but with computers these days having tens of thousands of files on them that's 20kib saved, which is better than a poke in the eye.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
* On machine with little memory, set iommu=off in your kernel boot parameters to get some extra 64 MB RAM back.
The official arch linux installation guide claims 512M as the minimum memory requirement for a system, with "more memory ... needed to boot the live system for installation". Is this any lower for ArchLinux 32?
Offline
I originally installed Archlinux back when it still had a 32bit variant on a machine with from memory no more than 64MB of RAM. That was, I suspect in 2015 and software has grown over time, but I'd be surprised in archlinux32 needs 512MB to boot the live media. Unfortunately in terms of testing, all I've got here is a machine with 2048MB of RAM, but I'd guess anyone here using the i486 variant build has much less ram.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
The standard ISO (with ramdisk) showed the following behaviour:
64MB KASLR error message, then hangs
128MB failed to execute /init
256MB Mounting archiso ARCH_201804, then hangs
272MB Initramfs unpacking failed: write error
288MB boots
320MB boots
384MB boots
512MB boots
Note that you have to set up a swap as very first action before using pacstrap (as pacman uses more memory).
If you use the "external pacstrap method" (installing from another machine and make rootfs bootable) from another machine, I'm running Archlinux32 with 128MB, see https://bbs.archlinux32.org/viewtopic.php?id=2876, text mode should be doable starting with 64MB.
I had an old i486 boot ISO (not using RAMdisks at all), but it's completly outdated now (so I removed it), had issues with missing keyrings and missing
compression algorithms. But I didn't have time to make a new one yet..
Offline
* When creating an ext4-filesystem switch off the 64-bit option if you don't have big harddisks (which you usually don't
have on those machines anyway): mkfs.ext4 -O ^64bit /dev/sda1
I just tried this, and discovered that the option needs too be put in quotes, like this:
mkfs.ext4 -O '^64bit' /dev/sda1
Hope that helps someone :-)
Last edited by esuhl (2021-01-23 12:41:55)
Offline
64MB KASLR error message, then hangs
128MB failed to execute /init
256MB Mounting archiso ARCH_201804, then hangs
272MB Initramfs unpacking failed: write error
288MB boots
320MB boots
384MB boots
512MB boots
This sept. 28, 2021, I did tested on a Dell Optiplex G260 with 256 Mb of RAM ==> Failed "Initramfs unpacking failed: write error"
I did configure the AGP Memory at the minimum (32 MB) within the Bios Setup.
I did started from USB Boot with iommu=off (pressing TAB key when seeing first linux boot message to add extra parameter).
I will try later with bigger RAM.
Dominique
Offline
Hi, try the i486 ISO, it has much less requirements.
There might be some other things you have to set, see:
https://git.archlinux32.org/archi486/tree/motd
You can set the Architecture=pentium4 before doing the pacstrap
when installing.
Offline
What does it mean by mounting swap partition in i486 version? Mounting /tmp to /mnt/tmp will not work on a read only system.
I have created a swap partition on local drive ;-)
Create und mount swap
Should that be 'and' ....
Offline
Ah. Thanks, yes, my "Germanisms" are sometimes creeping in.
Yes, Swap and /tmp have both to be mounted directly on the destination partition(s),
as there is no writeable root partition on the ramdisk or on the iso.
I should mention that the 486 ISO is still very alpha. :-)
Offline
I love alpha software ;-) can see installing archlinux32 i486 is going to be a challenge. Let me do some testing see if I can install anything!
Am cheating a little as I am running it in a VM, do not have an old thinkpad laying around....
Offline
Ok so I tried to mount swap partition ans was getting errors, so I mounted second partition /dev/sda2 [ext4] to /tmp/mnt. Pacman would not work so went with pacstrap and it ran and installed packages to /tmp/mnt. Of course this does not allow syslinux to install/run under chroot as it is not / device. Will try again later.. with mounting to /tmp.
Interesting
Offline
Did a normal install with /dev/sda2 mounted on /mnt ... got network up and then used pacstrap to install system, genfstab .... arch-chroot /mnt mkinitcpio -P blah blah blah....
Forgot dhcpcd ;-( and got lazy did not set timezone/locales... so could not log in.
Syslinux was not happy so ended up with grub.
Guess I am cheating a little as I have nearly 4Gb of ram attached to VM...
Let me load/fix networking then I will try to install X
Offline
Offline
* On machine with little memory, set iommu=off in your kernel boot parameters to get some extra 64 MB RAM back.
* When creating an ext4-filesystem switch off the 64-bit option if you don't have big harddisks (which you usually don't
have on those machines anyway): mkfs.ext4 -O ^64bit /dev/sda1
can you make a step by step info im not getting it?/
Offline
Pages: 1