0jay

25.2.3 build fine after upgrade though I had to hold rpi-eeprom, raspi-firmware and raspberrypi-sys-mods Also still getting the Method gave a blank filename apt error

This was my original approach. I don't have the knowledge/experience to parse a script like that and is the reason I was asking here.

Thanks geoW, I look to be having some success with the 25.2.3 build I just have to see if it survives the ugrades

I'm having trouble with the raspberry omv builds. The latest build I can get working is 24.11.1 which doesn't survive an upgrades (I've tried holding the various packages that seem to cause issues which used to work but doesn't work anymore. The suggested trouble shooting on the download page doesn't work either. Currently the 25.11.1 build is stuck in a bootloop, the only irregularity I can identify is failure to load console-setup.service message. I had a working system that lost my soundcard/DAC-hat after trying to address update error messages which's what started this whole refresh process

I believe renegade uses a diff bootloader but seems logical that firmwares would be different given different hardware The Libre tool is designed to inject Renegade firmware to make a Debian system swappable between Rpis and Renegade boards. What I was ultimately hoping to do though is use Rpi builds for other distros like Alpine and inject Renegade/Firefly firmware to make those pi builds usable on a Renegade board

Even just someone kicking in with yes I think it's possible but not sure how or whatever I'd been thinking to ad the armbian repo hosting firmware files but I doubt it's so simple in practice

Can anyone tell me if it's possible to install renegade firmware on a Rasperry Pi build for example? Libre used to host a script for a tool that achieved this but it hasn't been updated since Buster TIA

> if that minimal package were part of the stock system, so the armbian-install doesn't break did your system break following the f2fs-tools install or were you able to format with f2fs and install your system in armbian-config?

Thanks for the reply! I bought used and had no luck at all getting things running (this was some time ago and things are hazy). Have you written up your experience anywhere I could look at? Sent from my iPhone using Tapatalk

I was having some pretty substantial problems with several different builds before developing this hold pattern, Werner

If I hold those packages I don't see any issues at all.

it's a headless unit, Werner. if i can't ssh in then i just use an older build.

bout to try th latest 25.8.2 Edit: still no good – connection refused

may not help you (i'm running the pi4 build) but i find that putting holds on rpi-eeprom, raspi-firmware and raspberrypi-sys-mods from first boot solves this problem

Actually using a zero2w but same image obv as rpi4... unable to login (refused ssh). had to switch back to the 25.2.3 build

I can't wait that long for breakfast werner

is it available for testing?

Hi bschnei, wondering if you still have one of these units in service? I have a Mochabin box and hoped the espressobin image might be compatible but it sounds a lot like globalscale devices are just a lot of trouble without much success Thanks for your time. Oscar

Freezing kernel upgrades just means you can stay with a stable kernel and an update command will leave your kernel as is (in this case remain on the current edge kernel while updating the rest of the system). It's easy to unfreeze and update when there's a new LTS kernel available.

Hey pdieguez, I've layed out the process in the OMV forum here https://forum.openmediavault.org/index.php?thread/54000-catastrophic-wireguard-install/&postID=403856#post403856

Done. Thanks

Hi Igor, any developments with these pre-rolled images? Can I request a Renegade OMV image or will I need to wait for an LTS? Thanks for your time, Oscar

Short summary of process to follow: I burn Armbian with Etcher, update etc and install OMV. From here I use armbian-install (or armbian-config) to transfer to the eMMC. This is the only tool I've found that makes the eMMC transfer simple (thank you!). The eMMC system boots and seems fine but OMV is not functional (though it works fine on the SD it was transferred from). As a result I always just transfer the raw Armbian install to eMMC, boot from there and install OMV direct to the eMMC but it would be very handy to be able to transfer from an SD with a working OMV install fully configured as backup.

Armbian install unfortunately not working to transfer an OMV install on a 3328 renegade board. It boots but OMV is non functional (and seemingly irreparable)

the OMV plugin requires the meta package, that's the reason there's a problem