5 BTC BOUNTY --- BAMT boot issue.

[mc_lovin]

did you try this?

[1714736349]

1714736349

[1714736349]

1714736349

[1714736349]

1714736349

[1714736349]

1714736349

[cmg5461]

You may have a bad copy on your flash drive.  I'd say, rewrite it :/

[phr0stbyt3]

What model is your motherboard? Or did I miss that 

Anyway I had a hell of a time using my Gigabyte motherboard until I flashed the BIOS.

These motherboards are currently reported to have issues with BAMT according to their HCL:
Gigabyte 890FXA-UD5 - Unable to boot from .img (BAMT and Debian Live image tested)
Gigabyte 990fxa-UD3 rev 1.0 - Unable to boot images with paritions? Doesn't work.

-http://bamter.org/redmine/projects/bamt/wiki/Hardware_Compatibility_List

[flatronw]

You may find a "interim fix" for this problem but it will alway come again in some other manifestation to make your life difficult. The only way you will never finally solve it is to go to each machine that has a Gigabyte M/board. Remove the board, go to an open window and throw the FFFing board as far away as you can!!!!!

Posted by a Gigabyte owner, dont want the Bounty, happy to help another sufferer

[Danijel Habek]

Don't throw that board if it's capable for mining.
For the sake of your sanity and speed, why not use an 2.5" HDD you must have lying around your workbench collecting dust. Considering it's small power draw, at least you will be mining pronto. Just use dd and image BAMT on that hdd and mine away. Imo, this is much better solution than reverting back to windows, as far as there is BAMT available.

[gotobed]

I had exact same issues with kingston 4gb and managed to fix it by doing two things:

1 - I wrote the bamt img file to usb using dd from command line. making sure that the write speed was not too fast for the usb -  these Kingstons seem to have a pretty crap write speed. You do this by making sure NOT to specify any BS= parameter at the end of the dd command


2 - I had been plugging the Kingston into a usb 3.0 port and this also did not work. It must be a usb 2.0 port

These combined fixed it for me.