Linux mtlb 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:57:17
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux seems to work for me. 2 out of 2
to boot the system smoothly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Taihsiang, as no one seems to be interested in solving this, at least
there is a workaround which worked for me, go with the upstream kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056
The above are logs of my system booting with 4.4.0-75-generic. And the
kern.log shows something related to drm on skylake:
1 May 16 08:26:41 mtlb kernel: [238539.431888] [ cut here
]
LP: #1627670 of comment27 is related to nvm driver. In my case, I saw
hci related (and many other types of) kernel oops with 4.4.0-77-generic.
I can't get in my system with 4.4.0-77-generic so I can't get any log.
Let my have screen shot or something later.
--
You received this bug notification
This issue happens on 4.4.0-77-generic as well and getting worse. I have
rebooted more than five times and never succeeded. I rolled back to
4.4.0-75-generic to boot my system now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The CTRL+ALT+F1 workaround that I mention, it seemed just coincidence. Now I
just reboot and reboot again until it boots, without hitting the keyboard.
The kernel I has now is 4.4.0-66-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think this bug is related with bug 1627670.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627670
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056
Title:
[Asus UX360UA] Unable to boot
I want to ask why this is marked with "medium" importance. We cannot
boot Ubuntu in a normal way, isn't that at least high priority? It is
like, we cannot even enter in our own operating system...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056
Title:
[Asus UX360UA] Unable to boot
To manage notifications
Hi tjiagoM,
I'm sorry but I'm running only windows on it for the moment as I had to use for
work, now is a too busy period to start playing on it again.
As soon as I can I will but it might take a while.
Anyway if you have the exact same laptop (with I5 processor) and latest
upstream is working
I would like to say two things I discovered meanwhile regarding this
issue, with the same laptop that I also have:
- I tested with upstream kernel (4.10 rc7 [1]) and the laptop booted as
a charm. @fireantology can you test with this new kernel, please? I
think you did with 4.9 and there is a new
I have the same laptop with the same problem (not booting after
installing it). I don't know how to get the boot logs that you shown but
for some reason this workaround is working for me:
In the GRUB menu I select the ubuntu as supposed. But then I select it,
immediately when the black screen
12 matches
Mail list logo
