deskmini a300 boot problem

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Regarding virtualization problem: This is a known issue due to the buggy AGESA/Modules in the the last 2 BIOS updates that added ONLY the initial support for Zen+ (3x00G APU's).

So far, support in my tickets have stated that there are no plans to update the AGESA/Modules for this model, despite the fact that they literally have forum's full of people with issues.

That said, create a ticket to suppport, maybe it will get them to at least change the tone to "we will update it to the latest when we have time" (and actually do it) which is even more acceptable then "nope, let it die with its KNOWN bugs"... 
BTW, they did release a 3.53 beta which fixed the issues (shocker, updated modules!) only to revert with 3.60... maybe you can get them to link you to it!

It is what it is and I am responsible for 20+ of these in one way or another and ASRock has made my life a living hell...

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Hammerfest Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 05 Jun 2020 Status: Offline Points: 21	Post Options Post Reply Quote Hammerfest Report Post Thanks(0) Quote Reply Posted: 30 Jun 2020 at 9:06am
	Regarding virtualization problem: This is a known issue due to the buggy AGESA/Modules in the the last 2 BIOS updates that added ONLY the initial support for Zen+ (3x00G APU's). So far, support in my tickets have stated that there are no plans to update the AGESA/Modules for this model, despite the fact that they literally have forum's full of people with issues. That said, create a ticket to suppport, maybe it will get them to at least change the tone to "we will update it to the latest when we have time" (and actually do it) which is even more acceptable then "nope, let it die with its KNOWN bugs"... BTW, they did release a 3.53 beta which fixed the issues (shocker, updated modules!) only to revert with 3.60... maybe you can get them to link you to it! It is what it is and I am responsible for 20+ of these in one way or another and ASRock has made my life a living hell...

3735943886 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 29 Jun 2020 Status: Offline Points: 22	Post Options Post Reply Quote 3735943886 Report Post Thanks(0) Quote Reply Posted: 29 Jun 2020 at 12:57pm
	The problem is probably d/t virtualization. I don't know why but when I enable SVM and hyperV, the box won't boot.

linuxrocks Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Jun 2020 Status: Offline Points: 1	Post Options Post Reply Quote linuxrocks Report Post Thanks(0) Quote Reply Posted: 27 Jun 2020 at 12:37am
	I too have this problem. After clearing CMOS I get one boot. A reboot will just cause a black screen.

MotorPsico Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 17 Jun 2020 Status: Offline Points: 1	Post Options Post Reply Quote MotorPsico Report Post Thanks(0) Quote Reply Posted: 17 Jun 2020 at 2:31am
	Same problem here. Have just bought an A300, installed with Athlon 3000G, Noctua cooler, 2x4gb Crucial Sodimm and 2x1tb Crucial P1 NVMe SSD. Installed Ubuntu 20.04 to an USB, and after rebooting from the install I get a blank screen, no Bios access, no booting. The only solution was to clear the cmos, then I was able to enter the bios, boot and Ubuntu was working, thought I was some glitch, installed and configured things in Ubuntu, restarted and again, blank screen after rebooting. Once again I cleared the cmos, and I was able to enter the Bios, the version of the bios was 3.5 so I updated it to 3.6. I then installed FreeNAS to give it a try, installed and restarted without a problem, I tried couple of times so I thought the problem was solved. I wasn?�t happy with FreeNAS, so I decided to go back to Ubuntu, now I installed Ubuntu but in one of the NVMe disks, installation run without any problem, and at the time of restarting, again blank screen, no bios access no booting, nothing. I will have to clear the cmos AGAIN in order to be able to do something. This is really annoying, Asrock should give us a solution really fast. I have this very clear, this is solved within a week or the case is going back and I will give very bad opinions about A300 setup. Could it be a UEFI problem? Read about this kind of problems in Ubuntu forums.

Hammerfest Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 05 Jun 2020 Status: Offline Points: 21	Post Options Post Reply Quote Hammerfest Report Post Thanks(0) Quote Reply Posted: 05 Jun 2020 at 5:08am
	sucks that so many of us having issues and fix forthcoming everyone with the issue should make a support ticket

jameswilddev2 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 03 Jun 2020 Status: Offline Points: 5	Post Options Post Reply Quote jameswilddev2 Report Post Thanks(0) Quote Reply Posted: 03 Jun 2020 at 10:03pm
	I'm seeing the same problems as you with just one NVME - I get one boot per CMOS clear - ASRock did not indicate to me that fixed firmware is on the way. Perhaps if we make enough noise they will fix this bug.

nasenag Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 Jun 2020 Status: Offline Points: 1	Post Options Post Reply Quote nasenag Report Post Thanks(0) Quote Reply Posted: 02 Jun 2020 at 4:12am
	I have been running A300 with AMD 2400G With 3.6 Bios ( this is my sub machine for testing) with Windows 10. Updated to Windows 10 2004 Update and stop booting Cleared CMOS - Boot Once and Stop Everytime I clear CMOS it boots but when I Reboot it stop Same goes with Ubuntu 20.04 - so I don?�t think there is any issue with the OS it self. I have two SSD and One M.2 NVME I been reading many forum does this mean the power issue when two SSD is connected ?? Can AsRock confirm that it is power issue for having two SSD ? ( will try out with one SSD later today and post an update )

michischo Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Mar 2020 Status: Offline Points: 5	Post Options Post Reply Quote michischo Report Post Thanks(0) Quote Reply Posted: 31 Mar 2020 at 8:19pm
	The system is running fine with just one ssd being installed on sata 1 port. I have checked that ssd with both sata cables provided and had also hooked it up to the other port; it was functioning fine with either cable and port. therefore i don't think that the cable is the problem. If the problem does not relate to the hdd-s having been used and worn-out before, it might be that the system is "overwhelmed" when 2 drives are connected. Perhaps the power needs of the additional are too much?

ASRock_TSD Members Profile Send Private Message Find Members Posts Add to Buddy List ASRock_Official Joined: 20 Mar 2015 Status: Offline Points: 8727	Post Options Post Reply Quote ASRock_TSD Report Post Thanks(0) Quote Reply Posted: 31 Mar 2020 at 7:44pm
	Dear Michischo, Regarding your case, please help to check if the problem relates to SATA port or SATA cable. If possible, please change another SSD to try. Thank you! Yours truly, ASRock TSD

michischo Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Mar 2020 Status: Offline Points: 5	Post Options Post Reply Quote michischo Report Post Thanks(0) Quote Reply Posted: 27 Mar 2020 at 7:38pm
	Following a hint from Asrock-Support, I detached the disks and was able to boot to bios (uefi). Turned out that one of the two sata disks i had installed was bad. After tearing that disk out (it was a preused one, installed in sata 2) the system came back. Nevertheless i updated the Bios, everything continued to work fine. However, after adding another spare (preused) disk to sata 2, that disk also failed after a short time. Again, the system is fine after removal of that disk. Like the disk before, the drive is no longer accessible on another system. This makes me wonder whether maybe the A300 killed both disks. Has anybody had similar problems? Right now, i am using just one disk in sata 1.