I did the same tests as in comment #3 and it works for me.
Thanks.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I can't test this 3.13 kernel, as it has multiple other problems.
What I was talking about was the 4.4 Xenial kernel compiled with the
Trusty config / compiler, so my modules will build against:
Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-
protector-strong not supported by c
Thanks a lot. After apw's comment on IRC I expected something in the
next weeks :-)
I can just tell you it boots and seems to work. When I tried to manually
build my hw-support-dkms against the kernel I got:
LANG=C ./r
+ pwd
+ make -C /usr/src/linux-headers-4.4.0-112-generic M=/home/glg/mod
make
Public bug reported:
I'm using an external monitor on my notebook via DisplayPort => DVI
adapter.
After the latest Xenial updates, which included a kernel update to
4.4.0-13.29, I had massive problems, with black screen after reboot to
black screen after suspend with the attached monitor.
xrandr
The reverted radeon patchset didn't help for long. Actually I don't know
why it worked at all, but probably the HW was just breaking down slowly.
What finally helped was replacing my DisplayPort to DVI adapter for a
new one. This doesn't seem to be a software problem, as the latest
kernel works aga
I patched the source from 3.8.0-27.40 (there aren't any changes for the
mei driver in any Ubuntu 3.8 kernels) and just build the module. The
dmesg log still continues to fill with "mei reset" messages.
Since the mei driver has changed a lot since 3.8, I tried to backport
the mei driver from git AK
6 matches
Mail list logo
