I did verify that kernel 5.3 was running. Also I'm confident that it isn't
a hardware issue. When I wiggle the top cover there is no change, also I
run windows on the same laptop and I don't have these issues.
On Sun, Aug 11, 2019, 7:35 PM Daniel van Vugt
wrote:
> Also, did you verify that
booting with the parameter intel_idle.max_cstate=4 seems to have solved the
issue, thank you. Is this a permanent fix or will I eventually need to
alter this with a future kernel update? Also I'm curious as to what
intel_idle.max_cstate=4 actually does.
On Thu, Aug 22, 2019 at 8:00 PM Daniel van
No, i915.enable_psr=0 doesn't solve the problem
On Sat, Aug 24, 2019 at 1:40 PM Kai-Heng Feng
wrote:
> Does "i915.enable_psr=0" instead of "intel_idle.max_cstate=4" help?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
I have tested this kernel without having the parameter
intel_idle.max_cstate=4 at boot and I am not having any problems
On Sun, Aug 25, 2019 at 1:15 AM Kai-Heng Feng
wrote:
> Can you please test latest drm-intel kernel here:
>
I'm not sure how to boot with this setting, could I get more
information?
On Wed, Aug 14, 2019 at 2:50 PM Timo Aaltonen
wrote:
> does booting with intel_idle.max_cstate=4 help?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
I have found something that changes the state of the flickering. I tried to
plug in a thunderbolt to hdmi display and while the machine didn't output
to the display, the flickering stopped. I found that if I plugged in the
display while flickering was occurring the flickering would stop and once I
I'm uncertain if this channel is still open, but It seems that the problem
has returned. I'm not quite sure why, I think it might be that I didn't
properly update to boot parameters when I was testing kernel 5.3.0 - 994
but either way, it seems that the new kernel isn't a solution.
On Tue, Sep 3,
Public bug reported:
I am experiencing a large amount of screen tearing flickering and
artifacting. I've tried the common fix that is suggested on
askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel-
graphics.conf and this has not changed anything.
ProblemType: Bug
It's not clear to me how to change the driver to 'modesetting'.
What I did was edit the file /etc/X11/xorg.conf.d/20-intel-graphics.conf
and changed the line:
Driver "intel"
to
Driver "modesetting"
and I didn't see any change.
On Wed, Aug 7, 2019 at 3:03 AM Daniel van Vugt <
Here are two videos:
https://photos.app.goo.gl/mtpHBRNHrY8XvZ3y6
https://photos.app.goo.gl/uV34bkz1ZZsd6msGA
On Wed, Aug 7, 2019 at 2:51 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Also, if you can then please take a video of the issue and attach it
> here.
>
> --
> You received
I'm assuming you want me to send the allpackages.txt to you, so here it
is
On Wed, Aug 7, 2019 at 2:51 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> These lines suggest some graphics-related packages are missing:
>
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
>
I've tried both switching to Ubuntu on wayland and I installed kernel
5.3-rc3 and there hasn't been any change.
I'm not sure what I'm supposed to be seeing in the terminal window when I
run dmesg -w but here is a screenshot of part of the output. Nothing gets
added to the output when the
I'm having the same issue on an ASUS ZenBook S UX391UA in ubuntu 19.10,
kernel version 5.4.2-050402-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641290
Title:
[04f3:0903] Elan
13 matches
Mail list logo
