Ocassionaly (every few days), after shutting down Windows, or Linux, Udoo Bolt does not boot any more till hardware reset of bios. It boots until B4/A0 phase (right lower corner of screen) then hangs. It's not possible to boot. It's not possible to enter bios either (sic!) If I do bios manual reset using switch on the board ( BIOS default recovery switch), the udoo boots properly, without ANY changes to windows/linux/disk mechanism. I suspect this is some kind of bug in the firmware interpreting UEFI values. I tested this behaviour on three different firmwares: * orginall * rc 1.05 * rc 1.06 RC6 (from 22 November) -> this one I use currently.
I am having this same issue, and it's driving me crazy. It happens for me almost every time Windows shuts down. I was having issues with the Linux boot (after a Windows shutdown) which was solved by putting Ubuntu boot before Windows boot. I didn't know about the BIOS recovery switch, so my solution has been to remove all of my storage devices (both M.2 slots, this gets really annoying...) which allows me to boot into BIOS menu. Then I can put the storage back and boot normally again. I've been using the the original firmware I believe. (I think you should not hide the fact that there is a BIOS firmware update under the 'Advanced Topics' page...)
Yeah, it does not allow me to put my bolt in case, and drives me crazy too. Currently I'm observing it hang on A0 phase: * on every windows crash (which happens occasionaly during heavy gaming) * on almost every normal restart I do through windows menu * ocassioinally on linux shutdowns. @evaloverde Could you please ask one of the engineers to look into it? I'd happily provide any technical input/diagnose into this bug.
I'm having exactly the same problem as this. I just leave mine on 24/7 and it does not boot afterward until the mini BIOS switch is toggled. What is the solution to this?
Unfortunately this problem appears in a hit or miss fassion. Your only solution is to wait to bios update from udoo, and in the meantime you can file ticket to them, to help them debug the problem at https://ticket.udoo.org/
Udoo support is in contact with me, as they try to investigate it. If you can post here detailed technical steps to reproduce the problem, starting from the full hardware bios reset, it can help. Please post also your disk setup (which connectors, partitions, OS installed).
M.2 2280 is a Crucial P1 1TB SSD M.2 2260 is a Trancend 128GB SSD The last M2 is an intel Wifi/BT chip. Memory is Crucial 2x16GB Ubuntu 20.04LTS Only the first SSD is actual used. EFI is the first 50MB of that. Not sure the rest are really important. Neither the EMMC or the 128GB SSD are in use. Reproducing is easy. Reboot. Every single time, never fails. Gets to A0 and hangs.
THanks, thats helpful. Could you please: 1. confirm that i happens if you disconnect 128GB ssd 2. confirm that EMMC is empty (no partition table at all) 3. paste output of 'lsblk -f'
1) No change - I've tried reinstalling everything without that drive installed and it didn't matter. 2) gparted shows no partition on the EMMC, contents unknown. 3) $ lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT loop0 squashfs 0 100% /snap/core18/1705 loop1 squashfs 0 100% /snap/gnome-3-34-1804/24 loop2 squashfs 0 100% /snap/snapd/7264 loop3 squashfs 0 100% /snap/snap-store/433 loop4 squashfs 0 100% /snap/gtk-common-themes/1506 loop5 squashfs 0 100% /snap/core18/1754 loop6 squashfs 0 100% /snap/snap-store/454 loop7 squashfs 0 100% /snap/gnome-3-34-1804/33 sda mmcblk0 mmcblk0boot0 mmcblk0boot1 nvme0n1 ├─nvme0n1p1 vfat 9BD2-158A 38.5M 17% /boot/efi ├─nvme0n1p2 ext4 8ce9952a-a08e-4cdc-96ae-7a67f3badb5b 83.5G 3% /usr/local ├─nvme0n1p3 ext4 ca3120e7-0951-44ad-966e-a24e50e56e85 86.2G 0% /opt ├─nvme0n1p4 swap c386ef95-5c48-4a2c-9013-77702bcf327e [SWAP] ├─nvme0n1p5 ext4 c89e3b63-df09-4b0c-ad40-12ed68a56e39 188.6G 12% /data ├─nvme0n1p6 ext4 f124a589-1299-4b72-8b9c-6bfa46c72f39 125.1G 3% /abi ├─nvme0n1p7 ext4 31120260-015d-42f3-a13a-f45c2d8fac51 169.1G 2% /home └─nvme0n1p8 ext4 909032aa-7b6c-4f94-8d7b-dff83fda7ff8 110.5G 6% /
I am seeing the same issue. Reset the bios, boot up, and Ubuntu starts successfully. Reboot and I see error A0. Reset the bios, it boots up correctly and a reboot never gets passed A0. Ad nauseum.
My hardware: Intel 600P SSD Intel 3168NGW (from Udoo store) 2x16gb sticks of Crucial memory. I have tried removing the memory, swapping memory slots according to the troubleshooting guide etc with no result.
I having the exact same issue even since day one, even with the latest BIOS 1.08. I run Windows 10 off a Crucial 1TB NVMe M.2 SSD (CT1000P1SSD8). Runs extremely well EXCEPT everytime I lose power accidentally and Windows doesn't shut down properly it can't boot back to Windows or even to BIOS. All I get is the Udoo logo in the middle and the code A0 B4 bottom right. Everytime I have to open the case, remove the SSD, reboot to BIOS, turn off, reconnect SSD and then it reboots to Windows I also noticed that it boots successfully I get B4 A2 in the corner before Windows starts. Any help would be appreciated
I actually have the exact same SSD and just ran into the same issue. I also used the Crucial tool to update the firmware hoping it would resolve the issue but no luck there. I believe this stems back to the original BIOS release. I'm curious if having it as the Boot device causes the issues but haven't got around to fully testing. Are you running Windows off the NVMe or the eMMC?
I've got Windows on NVMe. I've tried to install it on eMMC when I first got my Bolt but gave up. I feel a bit dumb but I've just discovered the tiny reset switch on the side. So I don't need to open the whole case anymore and remove the SSD... Just flick the switch, press the power button, wait few seconds, flick the reset switch back and Windows starts straight away. I've opened a ticket with Udoo 3 weeks ago. They said they'll get back to me eventually. I'll update this post if I get something interesting to share.
