LongTermUser
Member
I have already reported this bug to NeoSmart support, but i think its important to make sure it get notice by the users of NeoSmart.
I recently bought Easy Recovery for recovery of my Win10 OS, but wasn't able to boot due to kernel bug in the live iso (booting from flashed usb stick)
Old CPU AMD A10-6800K APU
Per bios settings i have disabled the internal GPU on this cpu and i am using Nvidia pci express video card.
During boot process freeBSD just got to kernel error and step into the kdb debugger.
I assume freeBSD can't handle properly the disable state of GPU on mentioned CPU.
Its a blocker for me , because it cannot start X server even in vesa mode , which cant start the recovery Wizzard of NeoSmart.
Is there a console application for windows recovery?
The "old" terminal seems to be working , but the keyboard was wrongly setup, when i switch to german layout , then i was able to work in console mode.
I recently bought Easy Recovery for recovery of my Win10 OS, but wasn't able to boot due to kernel bug in the live iso (booting from flashed usb stick)
Old CPU AMD A10-6800K APU
Per bios settings i have disabled the internal GPU on this cpu and i am using Nvidia pci express video card.
During boot process freeBSD just got to kernel error and step into the kdb debugger.
I assume freeBSD can't handle properly the disable state of GPU on mentioned CPU.
Its a blocker for me , because it cannot start X server even in vesa mode , which cant start the recovery Wizzard of NeoSmart.
Is there a console application for windows recovery?
The "old" terminal seems to be working , but the keyboard was wrongly setup, when i switch to german layout , then i was able to work in console mode.
