[Chase, WRFH798]

Hi all, I have a Rpi 4 2GB. I’m running into an issue getting the board to boot with 2.1.2 I have tried three separate SDCards and two separate image builders but I continually get an ACT LED error pattern of unsupported board type. I have confirmed that the board and SDcards tested fine with NOOBS

Also the SHA checksum for 2.1.2 does not match. Not sure if that was just an outdated checksum from the last version or the image is corrupt.

Very cool project though, I look forward to getting this to work

-Chase

[Aaron, N3MBH]

Hello Chase,
If you are saying that the SHA checksum is not matching, that would be my first concern. Note that the checksum should be made on the compressed zip file as it is downloaded and not the uncompressed IMG file. There seems to be some occasional issues where the download may time out and not fully download. 2.1.2 should be about 1.3GB zipped up as I recall. If it has stopped, you should be able to resume it in most major browsers: https://openrepeater.com/knowledgebase/topic/problems-downloading-image-file

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Chase, WRFH798]

Okay, so re-downloaded the zip and confirmed that the checksum matched. Still getting an unsupported board type error. Any ideas?

[Chase, WRFH798]

Also, the installed image comes out to around 260mb on the sd card, that doesn’t seem right.

[Chase, WRFH798]

Ive tried several image builders, here is a log output from Rufus, note I’m not able to change any of the boot settings when building from ISO image

Rufus x86 v3.13.1730
Windows version: Windows 10 64-bit (Build 19041.746)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to ‘en-US’
Found USB 2.0 device ‘Generic Storage Device USB Device’ (048D:1366)
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3806, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x888C135E
Drive has an unknown Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 256 MB (268435968 bytes)
Start Sector: 8192, Boot: No
Partition 2:
Type: GNU/Linux (0x83)
Size: 7.1 GB (7671382016 bytes)
Start Sector: 540672, Boot: No
Found USB 2.0 device ‘Generic Storage Device USB Device’ (048D:1366)
1 device found
No volume information for drive 0x83
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3806, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x888C135E
Drive has an unknown Master Boot Record
Partition 1:
Type: GNU/Linux (0x83)
Size: 7.1 GB (7671382016 bytes)
Start Sector: 540672, Boot: No
Scanning image…
ISO analysis:
‘C:\Users\celli\Downloads\OpenRepeater_RPI_2.1.2_2019-08-24\OpenRepeater_RPI_2.1.2_2019-08-24.img’ doesn’t look like an ISO image
Disk image analysis:
Image has an unknown Master Boot Record
Image is a bootable disk image
Using image: OpenRepeater_RPI_2.1.2_2019-08-24.img (7.4 GB)

Format operation started
Requesting disk access…
No drive letter was assigned…
Will use ‘D:’ as volume mountpoint
No partition to delete on disk
Opened \\.\PhysicalDrive3 for exclusive write access
Requesting logical volume handle…
Writing Image:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Remounted \\?\Volume{7e260f21-5f1b-11eb-8f0a-309c232cdba6}\ as D:

Found USB 2.0 device ‘Generic Storage Device USB Device’ (048D:1366)
1 device found
Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3806, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x888C135E
Drive has an unknown Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 256 MB (268435968 bytes)
Start Sector: 8192, Boot: No
Partition 2:
Type: GNU/Linux (0x83)
Size: 7.1 GB (7671382016 bytes)
Start Sector: 540672, Boot: No

[Aaron, N3MBH]

Sorry I missed the notifications on your reply. Still sounds like a bad image or burn if you are say it is coming out to about 260mb on the card?

If you are saying the checksum is matching on the zip file, then can I assume that you zip file is approximately 1.3GB zipped and around 8GB unzipped (IMG file). That would give me a better indication that you have a good file.

As for imaging software…cannot say I’ve heard of Rufus. My preferred burner is balena Etcher. It is cross platform and the free version does a good job writing cards. The paid version I believe gives you reading options.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Dave, KI6ETL]

I actually ran into something similar. Although the image was updated to include the new Raspberry Pi 4, they’ve seemingly had new revisions of the board. I had to take the SD card and put it in a RPi3, so a
sudo apt-get update
and then
sudo apt-get upgrade
to get the newer kernel and firmware. Once that was completed, I put it back in my new RPi4 and it worked fine.

I’ think the 260mb being seen from the imaging was likely just the FAT32 /boot that would be seen by Windows. From the later post it does show there were other partitions (but Windows doesn’t know how to read them.
If you cut out the other stuff from that post:

Partition 1:
Type: FAT32 LBA (0x0c)
Size: 256 MB (268435968 bytes)
Start Sector: 8192, Boot: No
Partition 2:
Type: GNU/Linux (0x83)
Size: 7.1 GB (7671382016 bytes)
Start Sector: 540672, Boot: No

Windows can’t (without effort) show the contents of that 2nd partition.

My theory is the image is fine and being written correctly, but the current image can’t handle recently made RPi4. This isn’t a terribly uncommon problem with the RPi’s. They get minor updates/tweaks and require updated firmware to be usable.

[Aaron, N3MBH]

Thanks for your reply Dave. Didn’t think that he may only be seeing the boot (FAT32) partition and not the main Linux partition.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Author]

Posts