Re: Installing Trixie netinst iso on ASUS motherboard - solution
On Mon, 1 Sep 2025 19:27:17 +0800
jeremy ardley <jeremy.ardley@gmail.com> wrote:
> I have a new ASUS motherboard with a Ryzen 7 processor and downloaded
> the Trixie netinst iso
>
> I assumed simple dd of the iso to a USB drive would work. I was wrong.
How about showing us exactly what you typed and what results you got?
As in copy and paste the terminal session into your email.
>
> The problem is the ASUS BIOS expects a FAT-32 formatted install from
> a USB drive. dd of an iso does not produce the correct format.
I can dd the netinst ISO to a USB device and get a result that works on
various computers I have here. But I doubt I have exactly the same
motherboard and firmware version you have.
>
> After a great deal of experimentation, including linux tools such as
> Balena Etcher and Ventoy, I had to go to Windows to write the media.
>
> The solution is rufus on windows that was able to format the target
> drive correctly and then copy all the files from the iso image. The
> ASUS BIOS recognised this and I was able to do the netinst install.
>
> There may be some linux way of doing this but I haven't found it yet.
>
I suspect that the firmware on the motherboard expects an EFI
partition. That is exactly what the netinst image provides:
root@hawk:/crc/isos/debian# fdisk -l 13.x/debian-13.0.0-amd64-netinst.iso
Disk 13.x/debian-13.0.0-amd64-netinst.iso: 754 MiB, 790626304 bytes, 1544192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4f2c5af7
Device Boot Start End Sectors Size Id Type
13.x/debian-13.0.0-amd64-netinst.iso1 * 0 1544191 1544192 754M 0 Empty
13.x/debian-13.0.0-amd64-netinst.iso2 4108 11307 7200 3.5M ef EFI (FAT-12/16/32)
root@hawk:/crc/isos/debian#
Have you checked for firmware updates for the motherboard?
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: