problems to install 4.2 for raspi1
-
- downloaded the
retropie-4.2-rpi1_zero.img.gz
from the official website to install it on my raspi1. - checked the md5sum and it's fine.
- extracted the .img file from the .gz file.
- copied the .img to the sdcard using
dd
:
sudo dd bs=4M if=retropie-4.2-rpi1_zero.img of=/dev/mmcblk0 status=progress
dd
finished with no failures, put the sdcard on the raspi1 and turned it on.- raspi1 boots and show the "Resized root filesystem. Rebooting in 5 seconds..." message and reboots. And this step repeat infinitely.
- copied the img to the sdcard using
dd bs=1M
as suggested in the Raspberry Pi official instructions. - same problem.
- copied the img to the sdcard using the Etcher program.
- same problem
Unfortunately I don't have other sdcard available to assure that the problem is in the sdcard. But after copying the .img file in the sdcard, and facing that problem on boot, and plugging the sdcard back to my Linux Mint, I can see the partitions
retropie
andboot
, as usually. But I noticed that the sdcard is NOT resized. And this leads me to believe that the problem lies in the resizing procedure. BTW: I'm sure the sdcard isn't "locked" (read-only).Pi Model: raspi1 B
Power Supply used: Samsung Galaxy Note 10.1 AC Charger (output: 5V-2.2A)
RetroPie Version Used: 4.2
Built From: raspi1_zero pre made SD Image on RetroPie website -retropie-4.2-rpi1_zero.img.gz
USB Devices connected: nothing, not even a joystick
Guide used: first useddd
to install the .img file following the official Raspberry Pi INSTALLING OPERATING SYSTEM IMAGES ON LINUX instructions. And after I tried using the Etcher program.
How to replicate the problem: install the image on a sdcard and try to boot on a raspi1b. - downloaded the
-
@meleu i will look into it.
-
@BuZz just for curiosity, I've tried the 4.1.20 image from your google drive. Same problem.
-
@meleu other people have used that image without issues i think. Maybe try another sdcard.
-
@meleu I tried the Google drive image with my pi 0 W and it worked fine. A common issue is that USB hubs have caused a hang on boot. Unplug everything but what's necessary to boot then try again.
-
Latest image works fine here - so I guess it's an issue with your sdcard or another issue with your set-up.
-
@BuZz yeah, it can be the sdcard. I'll try with another one when I have a chance and update the info here.
Thanks for the great work! -
15 days later I finally got enough time and another sdcard to try it again. Confirmed: the problem was the old sdcard. Sorry for the false alarm. Or let's be optimistic, a false positive is better than a real bug. :-)
Thanks guys!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.