I am trying to dualboot a brand new computer - ASUS ZenBook Flip UX360UAK-BB358R with Intel Core i7 7500U Kaby Lake.
The preinstalled Windows 10 Pro work well. After minor testing of the laptop I shrinked the windows partition do half and intended to install Ubuntu aside so that I have a dualboot.
I tried the following systems - Ubuntu 16.04 LTS, Ubuntu 16.10, Ubuntu 17.04 alpha (daily build from 17.2.2017) and KDE Neon (built on Ubuntu 16.04 LTS). To the last one (neon) I also tried to install kernel 4.9.10.
The problem is always the same with all of the systems.
- I install the system / to the ext4 partition which I create from the free space that windows shrinkage tool left me, leaving 8GB to swap.
- I restart the computer, in grub select Ubuntu (or neon), splashscreen appears and it freezes.
- After ~20min I turn of the computer.
- I try turning it on again and it works.
- [When I log in, I update the whole system, update kernel, disable mounting the windows drives in
- I reboot again and it works or not. About 1/10 boots works. Windows work everytime.
- In 1/2 cases I am able to boot live usb and mount the drive to analyze it.
I also turned off the splashscreen to get this output (sorry for the quality, I don't know how to capture it without using my phone). Sometimes it terminates with kernel panic, sometimes it just freezes like this. Anyway it always passes the grub, starting a splashscreen with a spinner. Then, before log-in screen, the spinner either freezes or runs till infinity of the screen goes black and nothing happens.
I also enclose some common logs (currently running Neon with kernel 4.9.10) but it is very similar in standard ubuntu.
- there is a problem with driving the Kaby Lake cpu
- there are missing some other drivers (however
- there is a problem with having windows installed aside
- it is pretty weird as I tried multiple systems (each multiple-times) and the behavior is still the same
However, all of them contradict the fact that sometimes it boots well. I can't see any pattern when it works and when it doesn't. So far I think it is better chance to boot up if windows were booted before (but it doesn't help always).
I would be very grateful if you could give me some tips on what to do as I am after yestarday 12-hour session pretty desperate. Thanks
Following the Teyras's answer, I tried to debug ACPI (tutorial). My results (if I write "everytime" I mean 5/5 tries):
acpi=off- boots everytime; neither touchap nor touchscreen works
acpi=ht- boots occasionally; if it boots? everything works
pci=noacpi- boots everytime; neither keybord nor touchap nor touchscreen works
acpi=noirq- doesn't boot
pnpacpi=off- doesn't boot
noapic- boots everytime; neither keybord nor touchap nor touchscreen works
nolapic- boots occasionally; if it boots: neither touchap nor touchscreen works
Everything is really weird, sometimes
acpi=off boots to a normal mode where even touchpad etc. works fine.
I came across to this reddit post in which similar problems are discussed. I tried to turn off the wifi and bluetooth in the grub by pressing
fn+F2 as suggested, but the control diode didn't turn on and boot failed, so I guess it doesn't work at all.