I did that and it worked. Thank you! Why don't memstick .img files work well in Ventoy?Use the .ISO file in ventoy, not the memstick .img
It isn't, but theoretically should be irrelevant because Ventoy is supposed to be able to boot either one of them. Or at leas, that is my experience in the case of Linux distros.a memstick image is not a dvd
I've not used Ventoy so all this is speculation.I did that and it worked. Thank you! Why don't memstick .img files work well in Ventoy?
I'm not sure how it has any relevance here. Ventoy is not some software that is running on top of FreeBSD or any OS for that matter. It's a boot loader kind of like GRUB. The comparison to dd doesn't make sense because dd isn't a boot loader and does not in any way interact with your BIOS/EFI the way Ventoy does.but dd is native on freebsd
But ventoy must be written to a USB device, at least the parts that act as a bootloader, currently it looks like there is only a Linux version and a Windows version. The rest of the "ventoy instally" has userland tools that are used to update the existing "ventoy usb thing".I'm not sure how it has any relevance here. Ventoy is not some software that is running on top of FreeBSD or any OS for that matter. It's a boot loader kind of like GRUB. The comparison to dd doesn't make sense because dd isn't a boot loader and does not in any way interact with your BIOS/EFI the way Ventoy does.
It's just a one-time deal and you don't even need Windows or Linux for it. They provide a standalone live-cd for you to set that up the first time if you prefer to do so, though using Windows or Linux is more convenient. Once you do that one-time setup, you can just use `cp` `rsync` or even a GUI file manager to transfer ISO's to the partition instead of using `dd` and nuking your USB stick everytime you want to boot something different. It's a small price to pay for that flexibility, really.But ventoy must be written to a USB device, at least the parts that act as a bootloader, currently it looks like there is only a Linux version and a Windows version. The rest of the "ventoy instally" has userland tools that are used to update the existing "ventoy usb thing".
The totality is what I'm talking about. You have a USB device, you copy ventoy boot bits to it, then you use other tools to add images to that usb device.
I'm saying using dd to push the entire image to the usb device is native.
I think if I remember correctly, the 15.0 ISO file worked for me. Try that instead of using the img file.I have tried FreeBSD's memstick .img file on Ventoy and it always has the/dev/ufs/FreeBSD_Installdevice fail. Anyone know why this happens? I am using the latest Ventoy version (1.1.17)
Ventoy can handle a bunch of different images at once and you generally just need to copy the relevant images to the disk.Why Ventoy? Why not just follow the instructions in the handbook ? Choosing an image and a dd to a USB stick is easier
That's an entirely different thing, isn't it? It's what I used when I wanted to install FreeBSD 15.0 from scratch, but I think that the release had been out for a while at that point.hedwards
Yes, but the question isn't about its usefulness.
I used to use it for Linux distributions.
For FreeBSD, I prefer the native FreeBSD approach from start to finish:
ISO > USB drive > installation or maintenance.
It's not clear to me what's involved with that, but 15.0 is the last FreeBSD release that is currently listed as tested. Possibly, the easiest thing to do with ventoy is either wait for 15.1 support to be fixed and working or install 15.0 and upgrade from there.Maybe it didn't work because our dvd / img files aren't 'hybrid'.
Many Linux .isos you can dd to a memory stick and they also function. The FreeBSD .img files are pure image files which ventoy possibly doesn't support.