Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 34CE32235D0 for <~alpine/devel@lists.alpinelinux.org>; Thu, 1 Jan 2026 11:35:43 +0000 (UTC) Received: from fews04-sea.riseup.net (fews04-sea-pn.riseup.net [10.0.1.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4dhlBP3wFWzDqTR for <~alpine/devel@lists.alpinelinux.org>; Thu, 1 Jan 2026 11:35:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riseup.net; s=squak; t=1767267341; bh=opNkX1LgMFiGnyPeemGaL5Am2+uRpLDiMRmo8ON5fkk=; h=Date:Subject:To:References:From:In-Reply-To:From; b=ZVIRBiEAmqA2wuLK0K7vJerHoIU/g53DvHundl7iwEW5tg/OkkC4I0Sdcfmbuo1eE tw6UbNeQPHcbHH5bAxRILLhnLrHHmCGFly6qV5+Nc9izJ7t0BrN4fh14jLOy3q2E9G vmlnYJVHrQK79OhoBLKCnvMcPfcVdysMEqClahX4= X-Riseup-User-ID: DA63813452B906466D9AE4FAE9518E7E8C0652EC6F3EC71C63C0908566CAED4E Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews04-sea.riseup.net (Postfix) with ESMTPSA id 4dhlBN447Kz5yrM for <~alpine/devel@lists.alpinelinux.org>; Thu, 1 Jan 2026 11:35:40 +0000 (UTC) Message-ID: Date: Thu, 1 Jan 2026 15:05:38 +0330 MIME-Version: 1.0 Subject: Re: RPI3 not booting To: ~alpine/devel@lists.alpinelinux.org References: <6E2A60C2-2299-43B3-9FC6-D20DEF21855F@whitelist.co.in> <822DEF5A-0F1F-4EEF-A707-9C4D854E41BD@gmail.com> <260BE49B-359C-409A-A346-AFE4D5167393@whitelist.co.in> <20260101073442.Horde.2j_HdMMU5C6FkORtKJC3432@mindloot.net> Content-Language: en-US From: Farooq Karimi Zadeh In-Reply-To: <20260101073442.Horde.2j_HdMMU5C6FkORtKJC3432@mindloot.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Thank you Simon for these pointers. I haven't got an RPi 3. But I'm quite a SBC lover and I've got two Libre Computer boards ;) On 1/1/26 10:04, Simon Rupf wrote: > Hello Sagar, > > I hope I've not missed someone else's reply to you. > >> Yes, I have used the Raspberry Pi ISO, not the general one. It is not >> booting. >>>> [...] >>>> I flashed the iso file and tried to boot older versions like 21 and >>>> recent 23.2 on RPI3B+. >>>> >>>> There is no boot screen. Does it require flashing u-boot? > > I can confirm to you that the 3.21 armv7 tar-archive (and image-file, > but I recommend to use the more flexible tar-ball) do work on the > Raspberry Pi 3B+. I assume the aarch64 ones and later releases do as > well, but just to give you a data point on what others have gotten > working. > > The image (.img.gz file) works like other ISO images and you can > dd-copy it straight to your SD card. But it is a very small single > partition and will quickly run out of disk space if you want to > install more than a few basic packages and simple scripts. > > Hence it is better to use the tar-archive method. This requires that > you create a FAT32 partition by yourself of the appropriate size (I'd > recommend at least 4 GiB). It does not need to be marked bootable, but > must be the first partition and at the start of that SD-card. You then > unpack the contents of the tar archive onto it and are ready to boot > it up. More details on that process in the wiki at: > https://wiki.alpinelinux.org/wiki/Raspberry_Pi#Manual_method > > Keep in mind that this gives you a disk-less install[1], so any > changes, like installed packages or configuration changes and manually > created scripts or data need to be persisted using the lbu utility[2]. > So make sure that FAT32-partition is large enough to hold all the > installed packages and any other data you want to persist. > > [1] https://wiki.alpinelinux.org/wiki/Diskless_Mode > [2] https://wiki.alpinelinux.org/wiki/Alpine_local_backup > > The nice thing about this mode is that if you make any mistake or if > power fails you boot back up into a clean state. Also the SD-card will > last a lot longer as it is only used during boot and when you persist > changes with the lbu command. > > HTH Simon >