06-27-2016, 05:02 PM
I actually had the opposite problem on a friends big custom built 64bit Asus with a 1T SSD, after installing LL2.8 64. Windows 8.1 which was the original system loaded to its boot screen, hung, and then black screened. I had to restore the r-m path for it to load. AMI had no other solution at the time, though since Windows10 the problem does not exist. The board supported BIOS booting, but would not fully boot windows 8.1 after installing LL2.8, even though grub installed properly and recognized the windows system. I have heard several reasons for the problem, none of which proved to be correct. It now works perfectly with Windows10, LL 2.8, and LXDE Posh all installed. I've never had this issue with Windows7 or 10. So many of these problems are OEM and MS related especially with low end laptops. Your problem may be being caused by a logging function in the Windows8 EFI version. EFI Logs do not clean from the BIOS boot, so you must boot from windows EFI occasionally to empty them. Again this does not exist with Windows10. I think the Windows 8 solution to log overrun was a patch. Newer systems have dispensed with the logs altogether. Just a guess. BIOS are going to be disappearing on new laptops, and secure boot for Windows is here to stay, though it's only real purpose is to protect windows systems. These issues are going to continue for Debian based distros until Debian catches up to them. It's like breaking a dozen same colored glasses into a box, and then trying to reassemble each one correctly.
Trinidad
Trinidad
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.