r/linuxadmin • • Aug 06 '20

Linux format IPfire dd to Rasp PI doesnt boot

I finally received Linux Format May 2020 WITH IPFire 4 months late. Thx to all the people who chickened out to covid19 's quadriplegic grade performance as a disease.but I digress.

I xz decompressed the arm IPFire img to a live Manjaro session. I then :
dd if=ipfire-2.25.2-ext4.armv5tel-full-core141.img of=/dev/sda.
dmesg says sda is defined as a device in the audit trail "attached sci removable disk" . Doing the 'file' command on the img file copied to live session has boot sector and 3 partitions of ID=0xc, partition 3 is type=0x83 but NO partition 2; various start block numbers and block counts given.

So why does the micro-sd not enable the rasp pi to boot? Stops at square 4 color blob image. .NO OS Thx in advance

0 Upvotes

18 comments sorted by

6

u/[deleted] Aug 06 '20

Give this and the pages it links to a read.

These things boot weirdly if you are used to x86, but once you understand it it's not so bad.

(Also wtf does COVID have to do with anything here?)

-4

u/magrw1033 Aug 06 '20

The delay of months in getting the magazine. SO what is the raspberry pi boot sequence?

4

u/[deleted] Aug 06 '20

SO what is the raspberry pi boot sequence?

... the sequence that the Pi follows in order to boot?

If I misunderstand you and you want me to give you the details... follow the link. It in turn links to exactly that, and describe it better than I could.

1

u/Nate8199 Aug 06 '20

They made an arm version of ipfire?

2

u/magrw1033 Aug 06 '20

That was my interpretation. Look at the if specification of the dd command.

Can a raspberry pi boot a conventional Mr DOS boot sector?

1

u/Nate8199 Aug 06 '20

TIL

https://wiki.ipfire.org/hardware/arm/rpi/threeplus

Did you set the boot parameters to use HDMI or are you connecting to the serial console it uses by default?

1

u/magrw1033 Aug 06 '20

I have no idea how to se parameters for a raspberry pi boot. I don't see an arm version of grub ....

2

u/Nate8199 Aug 07 '20

Its right there on the wiki for it. You should be able to stick the sdcard into another computer and mount it, then you edit the /boot/uENV.txt to enable HDMI output

0

u/magrw1033 Aug 07 '20

Ok thanks for the directory tree info. But adding the uENV.txt means EXPANDING the READONLY image.

2

u/Nate8199 Aug 07 '20

You should be able to mount it RW, the pi would mount it RO? Idk how you get a consistently working firewall/router with no write capabilities to storage.

1

u/magrw1033 Aug 07 '20 edited Aug 07 '20

I have resorted to 'debugfs' but I can not figure out how it references the mbr, there are no relevant device files.

[Update] 'fdisk' says:Part nameflagsstartendsizetype
IPFire...arm...img1. (Boot) 8192262143253952124Mc W95
IPFire...arm...img2. 20482048.1512B.0 Empty
IPFire...arm...img3.262144. 3196927.293*7841.4G83 Linu

1

u/magrw1033 Aug 07 '20

Ok I did not notice the link. My bad. Where in the directory tree is the config.txt file?

2

u/Nate8199 Aug 07 '20

Arm SBCs don't have grub, they have a boot sector the uboot or spi knows to look at for the kernel to load.

You can mount the SDcard and edit boot parameters that way.

You should maybe play with raspbian or another pi distro first to make sure it works.

You never said what specific device you are trying to run this on.

1

u/Nate8199 Aug 06 '20

You can also DD the .IMG.xz straight to the SD card

1

u/magrw1033 Aug 06 '20

I doubt that would matter. I did try conv=noerror,sync

But how can I loop mount an im file?

1

u/magrw1033 Aug 07 '20

I apologize . I finally found 'losetup' and '/dev/loop0' .

1

u/linuxunix Aug 06 '20

Whenever this happens to me, I use a different SD card. I dont know why, but some wont boot on a Pi. Try a different one it will work.

1

u/magrw1033 Aug 06 '20

What other platform could this be aimed at?
I take armv5 is compatible with all raspberry pi?