BIOS does not see the flash drive, how to fix it?

K

KOLANICH2014-06-04 06:10:13

linux

KOLANICH, 2014-06-04 06:10:13

I uploaded a new image of Ubuntu to one flash drive, and a new image of another distribution kit to the other. In turn.
After updating the Linux image uploaded to the flash drive, the BIOS stopped detecting flash drives as bootable. On both, the boot sector is in place and contains the code - checked by a hex editor and one debugger / disassembler.
As a filling utility, I tried 4 different ones: rufus , unetbootin , yumi and the one that comes with ubuntu - the result is zero. I suppose that the matter may be in the updated kernel or the updated bootloader. Or is there something wrong with the system. Just in case, I changed the BIOS - it did not help (I reset the settings after the update!).
Upd: I tried to use plop boot manager: I created a cd zone on the flash drive (the microcontroller in the flash drive emulates the cd drive, it is necessary in case the computer cannot boot from usb-hdd or usb-zip (mine can, apparently, how- it’s not completely, but sometimes you have to deal with computers that don’t support booting from a USB flash drive at all)), a plop isoshnik was poured into it, and a disk image was filled in for the rest. As expected, plop saw, Linux, as before - no. In the plop I went into the boot from usb. Plop searched, found and ... a black screen with a blinking cursor.

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

S

Soniked, 2014-07-28
@Soniced

Try checking the "Fast BIOS Mode" option or something similar. I myself had a similar problem.

O

oia, 2014-06-04
@oia

Do these flash drives work as bootable on other PCs?

E

Eugene Obrezkov, 2014-06-04
@ghaiklor

Check things like UEFI, USB Legacy, and of course hard drive boot priority. Some distributions are not able to work with UEFI, so it's better to turn it off. If it does not help, then you can also enable / disable USB Legacy.

I

Ilya, 2014-06-04
@11rus

Did you reset the bios to default after updating?

K

KOLANICH, 2014-06-15
@KOLANICH

As expected, it's the new syslinux. The old one works, but the new one doesn't.
Or rather, not with syslinux, but most likely with the motherboard, which for some reason does not want to see the new syslinux. And since it is included in all used utilities, and the result does not depend on the utility.
In short - some kind of crap.