@guiverc, @sudodus I need to note that we should use software which writes ISO to the flash-drive on the binary level (this means without any custom boot- loaders on top of included into ISO).
I have used GNOME Disks (`gnome-disks`, *Restore Disk Image*) and `ddrescue` (with command link `sudo ddrescue groovy-desktop-amd64.iso /dev/sdZ --force`) to write latest Ubuntu MATE ISO to the flash-drive. Below are the current results for todays 20200714 build ( http://cdimage.ubuntu.com/ubuntu-mate/daily-live/20200714/groovy-desktop-amd64.iso , http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/217010/testcases/1303/results ) : * ThinkPad SL500, legacy only, boot and operate normally; * VAIO F13, legacy only, boot and operate normally; * Asustek UX32A, EFI, boot and operate normally; * Asustek UX32A, legacy, boot and operate normally; * desktop AsRock G41M-VS2, Core2Duo Q9400 - legacy only, boot and operate normally. So my systems boot normally with ISOs newer than 20200709. You can check full history for Ubuntu MATE at http://iso.qa.ubuntu.com/qatracker/milestones/413/history . --- What is really strange here is that Rufus is a recommended way for Windows - https://ubuntu.com/tutorials/create-a-usb-stick-on-windows . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
