On 7/3/19 9:31 AM, Bennett Piater wrote:
> I was talking about external monitors not working, you are talking about wifi
> cards.
You're right sorry - I replied to wrong email - meant to be to this.
It should have been a new thread as different topic.
On 7/2/19 12:25 PM, Stanislav N. aka pztr
On Wednesday, July 3, 2019 2:59:01 PM CEST Genes Lists via arch-general wrote:
> On 7/3/19 3:58 AM, Bennett Piater wrote:
> > To clarify: I did not find an upstream bug, and I don't know that this
> > is an upstream issue.
>
> It is an upstream bug - peraps my previous email didn't get through -
>
On 7/3/19 3:58 AM, Bennett Piater wrote:
>
>
> To clarify: I did not find an upstream bug, and I don't know that this
> is an upstream issue.
It is an upstream bug - peraps my previous email didn't get through -
will quote it again - sorry if its a dup:
---
On 7/2/19 1:48 PM, Genes Lists via
On 2019-07-03 10:24, Ralf Mardorf via arch-general wrote:
Hi,
since I didn't follow this thread close enough, I don't know if this
is an Arch or upstream related issue. However, it's crass if you
consider it to be most likely an upstream bug and you think somebody
else should do your job.
"O
On Wed, 03 Jul 2019 09:58:48 +0200, Bennett Piater wrote:
>On 2019-07-03 09:51, Ralf Mardorf via arch-general wrote:
>> On Wed, 03 Jul 2019 09:25:46 +0200, Bennett Piater wrote:
>>> I opened an Arch bug so we can track it:
>>> https://bugs.archlinux.org/task/63079
>>>
>>> The maintainers can rep
On 2019-07-03 09:51, Ralf Mardorf via arch-general wrote:
On Wed, 03 Jul 2019 09:25:46 +0200, Bennett Piater wrote:
I opened an Arch bug so we can track it:
https://bugs.archlinux.org/task/63079
The maintainers can report it further upstream, they know where -
that's what they are for :)
H
On Wed, 03 Jul 2019 09:25:46 +0200, Bennett Piater wrote:
>I opened an Arch bug so we can track it:
>https://bugs.archlinux.org/task/63079
>
>The maintainers can report it further upstream, they know where -
>that's what they are for :)
Hi,
since I didn't follow this thread close enough, I don't
On Wednesday, 3 July 2019, 09:25:46 CEST you wrote:
> I opened an Arch bug so we can track it:
> https://bugs.archlinux.org/task/63079
>
> The maintainers can report it further upstream, they know where - that's
> what they are for :)
Thanks, well done, Bennett!
And I took that tracking URL to my
On 2019-07-03 06:38, Oliver Jaksch via arch-general wrote:
Glad that this (4.19 in your case) works for you, too.
Good idea in general. But where? Seems that this is Intels' thing again
and
their list of open bugs is already extensive :(
I opened an Arch bug so we can track it:
https://bu
On Tuesday, 2 July 2019, 17:16:45 CEST you wrote:
> On Tuesday, July 2, 2019 9:59:57 AM CEST Oliver Jaksch via arch-general
wrote:
> > There are *some* issues with intel gpu's and recent kernels. I can't use
> > multiple monitors in most of the cases as the i915 module misinterpret
> > possible re
> Not only GPUs, but also WiFi cards. Got 8265 on Thinkpad T480 and 5G
> speeds are awful. When you're trying to download via 5G network
> something big - connection interrupts and won't come back until
> NetworkManager is restarted, also there are plenty of errors in dmesg.
> All fine on 5.0.x
02.07.2019 12:59, Oliver Jaksch via arch-general пишет:
> On Tuesday, 2 July 2019, 09:46:02 CEST you wrote:
>> On 07/02/2019 01:01 AM, Bennett Piater wrote:
>>> Hi,
>>> I'm using a Thinkpad T450s with Intel graphics.
>>>
>>> Yesterday, I could no longer connect external monitors via miniDP.
>>> The
On Tuesday, July 2, 2019 9:59:57 AM CEST Oliver Jaksch via arch-general wrote:
> There are *some* issues with intel gpu's and recent kernels. I can't use
> multiple monitors in most of the cases as the i915 module misinterpret
> possible resolutions, for example.
>
> https://bbs.archlinux.org/view
>>> There are *some* issues with intel gpu's and recent kernels. I can't use
>>> multiple monitors in most of the cases as the i915 module misinterpret
>>> possible resolutions, for example.
> Also, I remember some issue with external monitors on this list not long ago:
> https://lists.archlinux
Regarding kernel versions: I also had noticed instabilities (more errors than
usual in dmesg from drm and i915, weird GL/compositing glitches) on my HD4400
Intel with one external monitor and laptop display starting with 5.1.x.
I've so far remained on 5.0.3 and have not debugged in depth due to
There are *some* issues with intel gpu's and recent kernels. I can't use
multiple monitors in most of the cases as the i915 module misinterpret
possible resolutions, for example.
Also, I remember some issue with external monitors on this list not long
ago:
https://lists.archlinux.org/pipermai
Have you checked the troubleshooting options on
https://wiki.archlinux.org/index.php/Intel_graphics. I also recall an
intel
issue with recent kernels, but can't put my hand on a link. The
problems
experienced with some are listed in the wiki.
There are *some* issues with intel gpu's and recen
On Tuesday, 2 July 2019, 09:46:02 CEST you wrote:
> On 07/02/2019 01:01 AM, Bennett Piater wrote:
> > Hi,
> > I'm using a Thinkpad T450s with Intel graphics.
> >
> > Yesterday, I could no longer connect external monitors via miniDP.
> > They were not detected at all, either by xrandr in i3 or by s
On 07/02/2019 01:01 AM, Bennett Piater wrote:
> Hi,
> I'm using a Thinkpad T450s with Intel graphics.
>
> Yesterday, I could no longer connect external monitors via miniDP.
> They were not detected at all, either by xrandr in i3 or by sway (wayland).
> I didn't have time to dig out a VGA cable and
Hi,
I'm using a Thinkpad T450s with Intel graphics.
Yesterday, I could no longer connect external monitors via miniDP.
They were not detected at all, either by xrandr in i3 or by sway
(wayland).
I didn't have time to dig out a VGA cable and try that, so I cannot rule
out physical damage yet - I
20 matches
Mail list logo
