I've decided to stop waiting for v0013 and just run with v0012 for now because all my 1000-series rigs are now stable (
thanks, @fullzero and all the contributors!) and my six Radeon RX470s were sitting idle (boo!
BOO!)
But I'm running into a snag. On First Boot with the v0012 build after imaging (with the same solution I successfully use for imaging nvOC), the rig falls into BusyBox, as shown in the top screen, here:
Second boot goes into Grub, which allows me to start Ubuntu, but goes into the second image in the image above, reporting some sort of corruption and need for fsck.
I've scratched and re-imaged the USB key (same model used with nvOC), I've removed all video cards but the one in the primary X16 slot, I've pre-edited the oneBash file and dropped it into various folders for First Boot, but no joy.
It's on an Asus Z170-AR mobo - which worked fine in Win 10 for mining 6 cards after BIOS update. I have Above 4G enabled.
Any suggestions or direction for troubleshooting? I'm happy to provide whatever info anyone needs to assist. (Warning: I am still getting my bearings in Ubuntuland.)
I'm currently set up with a single video card in the primary X16 slot, connected via USB riser. On First Boot, I briefly get the purple Ubunu desktop background before the screen goes black and it drops into BusyBox.
If necessary, I'll pull the mobo out so that I can do a first boot with a card directly in the slot - that's something I've found necessary for Windows builds, but which I have not found to be necessary for nvOS builds.
Thanks, in advance!
Update:
Figured out that I can run fsck manually with the following:
fsck /dev/sda2
Afterwards, CTRL-ALT-DEL gets Ubuntu to start, but no GUI... just a login.
Will continue trying to troubleshoot and look through the thread again to see how to start the GUI...
OK, mined ETH all night!
Looking forwards to next version, but meanwhile, thanks for all you've done for us!
Next job: upgrade Claymore to 10.0 and tweak OC...
I have spent a few hours messing around with the new driver and have a version I am using as a sort of stopgap to test the new driver. With most GPUs it does have better Ethash peformance, but Equihash seems the same in my tests so far.