Forum
Replies （5）
- You Reply: @pirsen
Thank you for the screenshot and instructions. I was able to finally boot to USB using those Rufus burning settings and following bios steps. I only had one successful boot so far to Linux 16.04, but I have a positive outlook that these same steps will allow me to continue installing and testing different USB bootable images as well.
Thanks!!! - You Reply: Hello,
I have tried just about every option and method I could to get both the 2/32 and 4/64 versions of my LattePanda boards to boot from several different USB flash drives to load different Linux and FreeBSD OS images as disk images in ISO, VGA, Serial, and Nano formats, but I have yet to successful get any OS to boot, run, load, install, etc. Can someone point me in the right direction or help me understand what they have done or know how to do to accomplish this?
I did have to re-image my 4/64 boards when I first received them because they would not originally boot to Windows. That process worked good by following the simple steps shown on the Docs page of this site. But where I usually get stuck on trying to do the above OS installs is in the bios and EFI/UEFI shell terminals. I've spend plenty of time navigating different motherboard bios screens over the years, but I'm new to the EFI shell terminal and how that may affect things. The first problem I typically run into is that the USB drive is never an option in the Boot Priority menu to boot from. It does show as a listed drive under USB Configuration from the six or so different USB drives I tried with, but not in the Boot Priority list. The three options under Boot Priority are usually Windows Manager, UEFI, or none.
Some of the OS images I'm trying to install and use the LattePanda as the hardware/computer for are OPNSense, pfSense, and Sophos. I'm going to add USB to Ethernet adapters I have to increase the NICs. The objective I'm after is to turn these into firewall routers and gateways to different WAN/LAN networks I have setup as additional hardware security measures before a WAN connection hits one of my NICs on my PC Server with a Hyper-V switch and clusters of VMs.
I know there are plenty of other boards on the market that are built for doing exactly what I'm trying to do above and I also have a few of those. But, I'm trying to do it on the LattePanda since it has an Atom processor which is usually the primary piece needed compared to ARM processors for similar embedded board sizes. I also have several other Atom processor based PCs that are primarily Zotac Zbox Pico models.
One final note: I am having the exact same issue in the bios of a few Zotac Zbox Picos. The processor and configuration of those are very similar to the LattePanda boards, minus the GPIO option.
Thanks,
Keith - You Reply: I was able to bypass the error with a fresh install of the WIndows setup file on a USB flash drive. That image is in stalled and currently running stable after a few hours in the Windows 10 environment. More testing will continue, but so far so good. Speed and performance is impressive.
A negative thing is that it looks like both my 4GB/64GB boards that arrived needed to be re-imaged before use. I'm happy that it is not a difficult fix other than taking time to figure it out. - You Reply:
schluej wrote:Take a look her:
Than you for the reply and links. I will run the Windows tests on the downloaded 64-bit image I downloaded and extracted onto the USB drive that is provided on the Docs page. I hope it may be a simple software fix or update as oppose to a hardware or configuration issue on the 4GB/64GB boards. Since the same issue of not being able to load Windows other than getting to the Please Wait a Moment (second screen) after showing the LattePanda logo page when powered on (first screen), I'm a little concerned.
https://technet.microsoft.com/en-us/lib ... 24869.aspx
or
http://answers.microsoft.com/en-us/wind ... c47?auth=1
Interesting could also the DISM.LOG file content...
I have high hopes for the success of these boards though, so I will continue troubleshooting and testing as needed until everything is stable : )
Just in case the question comes up, I have several 5V/2A power supplies on my test bench and multiple Pi/Beagle charges with the same output. I tried a few of them to rule out the bad power supply or low power option. However, do the 4GB/64GB boards maybe need more than 2A to run successfully compared to the 2GB/32GB boards? - You Reply: As a quick follow up, I powered up one the two DFR0418 boards after posting this error message on the DFR4019 boards. The DFR0418 (2GB/32GB) board booted to the Windows install screen like you normally see to begin setting up Windows. So, the 2GB/32GB boards are working good and normally. Unfortunately, neither of my 4GB/64GB boards are working.
Please help.