On Thu, May 6, 2021 at 5:46 PM Rafael J. Wysocki wrote:
>
> On Tue, May 4, 2021 at 10:08 AM Chris Chiu wrote:
> >
> > Hi,
> > We have some Intel laptops (11th generation CPU) with NVIDIA GPU
> > suffering the same GPU falling off the bus problem while exiting
&g
Hi,
We have some Intel laptops (11th generation CPU) with NVIDIA GPU
suffering the same GPU falling off the bus problem while exiting
s2idle with external display connected. These laptops connect the
external display via the HDMI/DisplayPort on a USB Type-C interfaced
dock. If we enter and exit
We found another bug after the fix of
https://gitlab.freedesktop.org/drm/intel/-/issues/2538. The external
monitor is also connected via WD19's HDMI/DisplayPort just as #2538.
However, the display monitor can only be detected and show output at
the very first time we power on the WD19 dock. If we u
We are working with new laptops that have the Ryzen 7 4700U.
It fails to launch X so I can only access via the virtual terminal.
I tried with the latest mainline kernel and kernel from
https://cgit.freedesktop.org/~agd5f/linux but no luck. I also boot
the kernel with parameter amdgpu.exp_hw_suppor
Hi guys,
We have 2 laptops, ASUS Z406MA and Acer TravelMate B118, both
powered by the same Intel N5000 GemniLake CPU. On the Acer laptop, the
panel will blink once during boot which never happens on the ASUS
laptop. It caught my attention and I find the difference between them
but I need help f
On Wed, Oct 30, 2019 at 6:25 PM Chris Chiu wrote:
>
> Hi guys,
> We have 2 laptops, ASUS Z406MA and Acer TravelMate B118, both
> powered by the same Intel N5000 GemniLake CPU. On the Acer laptop, the
> panel will blink once during boot which never happens on the ASUS
> la
On Wed, Sep 19, 2018 at 8:08 PM, Jani Nikula wrote:
> On Wed, 19 Sep 2018, Chris Chiu wrote:
>> I tried to add a slight delay in the hotplug work as follows
>>
>> --- a/drivers/gpu/drm/i915/intel_hotplug.c
>> +++ b/drivers/gpu/drm/i915/intel_hotplug.c
>>
#x27; to reprobe the devices. It would also cause the audio
output path cannot correctly swicth based on the connector status.
This commit kicks off a delayed work when the status remains unchanged
in the first hotplug event handling, which may not be the perfect
timing in some special cases.
Signe
On Tue, Sep 11, 2018 at 6:25 PM, Chris Chiu wrote:
> On Fri, Aug 24, 2018 at 11:04 PM, Jani Nikula wrote:
>> On Wed, 22 Aug 2018, Chris Chiu wrote:
>>> On Fri, Jul 6, 2018 at 2:44 PM, Chris Chiu wrote:
>>>> On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä
>>&
On Fri, Aug 24, 2018 at 11:04 PM, Jani Nikula wrote:
> On Wed, 22 Aug 2018, Chris Chiu wrote:
>> On Fri, Jul 6, 2018 at 2:44 PM, Chris Chiu wrote:
>>> On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä
>>> wrote:
>>>> On Thu, Jul 05, 2018 at 03:58
On Fri, Jul 6, 2018 at 2:44 PM, Chris Chiu wrote:
> On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä
> wrote:
>> On Thu, Jul 05, 2018 at 03:58:36PM +0800, Chris Chiu wrote:
>>> Hi,
>>> We have few ASUS laptops X705FD (The new WiskyLake), X560UD (intel
>>
On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä
wrote:
> On Thu, Jul 05, 2018 at 03:58:36PM +0800, Chris Chiu wrote:
>> Hi,
>> We have few ASUS laptops X705FD (The new WiskyLake), X560UD (intel
>> i5-8250U), X530UN (intel i7-8550U) share the same problem, which is
>>
Hi,
We have few ASUS laptops X705FD (The new WiskyLake), X560UD (intel
i5-8250U), X530UN (intel i7-8550U) share the same problem, which is
the HDMI connector status stays connected even the HDMI cable has been
unplugged. Look into the "/sys/class/drm/card0-HDMI-A-1/status" for
checking the stat
On Thu, Jul 5, 2018 at 9:18 PM, Jani Nikula wrote:
> On Thu, 05 Jul 2018, Chris Chiu wrote:
>> On Thu, Jul 5, 2018 at 5:37 PM, Jani Nikula wrote:
>>> On Thu, 05 Jul 2018, Chris Wilson wrote:
>>>> Quoting Jani Nikula (2018-07-05 09:58:57)
>>>>> On Th
On Thu, Jul 5, 2018 at 5:37 PM, Jani Nikula wrote:
> On Thu, 05 Jul 2018, Chris Wilson wrote:
>> Quoting Jani Nikula (2018-07-05 09:58:57)
>>> On Thu, 05 Jul 2018, Chris Chiu wrote:
>>> > Hi,
>>> > We have few ASUS laptops X705FD (The new WiskyLa
On Thu, Feb 1, 2018 at 9:13 PM, Chris Chiu wrote:
> On Thu, Feb 1, 2018 at 12:08 AM, Harry Wentland
> wrote:
>> On 2018-01-31 09:31 AM, Chris Chiu wrote:
>>> Hi,
>>> We are working with new laptops that have the AMD Ravenl Ridge
>>> chip
On Thu, Feb 1, 2018 at 12:08 AM, Harry Wentland wrote:
> On 2018-01-31 09:31 AM, Chris Chiu wrote:
>> Hi,
>> We are working with new laptops that have the AMD Ravenl Ridge
>> chipset with this `/proc/cpuinfo`
>> https://gist.github.com/mschiu77/b06dba574e89b9a30cf4
Hi,
We are working with new laptops that have the AMD Ravenl Ridge
chipset with this `/proc/cpuinfo`
https://gist.github.com/mschiu77/b06dba574e89b9a30cf4c450eaec49bc
With the latest kernel 4.15, there're lots of different
panics/oops during boot so no chance to get into X. It also happens
We are working with new desktop that have the NVIDIA NV118
chipset.
During boot, the display becomes unusable at the point where the
nouveau driver loads. We have reproduced on 4.8, 4.11 and linux
master (4.12-rc3).
Dmesg log is attached.
Is this a known issue? Anything we can do to help?
Thank
Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it
only gives VGA resolution on screen. Use the same chipset as nv134
then it shows FullHD. This commit copies fields from nv134_chipset
to nv136_chipset for GTX 1060.
Signed-off-by: Chris Chiu
---
drivers/gpu/drm/nouveau/nvkm
20 matches
Mail list logo
