nouveau.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: dmanye <dmanye@urv.cat>
To: nouveau <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] [INVALID_ARG] mthd 0414
Date: Fri, 19 Nov 2021 13:59:20 +0100	[thread overview]
Message-ID: <f7a8c82c-2fa3-60ed-40e4-ccde4a96b8c6@urv.cat> (raw)
In-Reply-To: <CACO55tsqBSSzyeyJbS-81rO4=JXtdJxz_vOHoc-f7rvVwZdLog@mail.gmail.com>

On 19/11/21 13:31, Karol Herbst wrote:
> yeah.. not quite sure yet. I tried it out with my gk208b gpus, but
> couldn't hit anything. Maybe using VGA makes the difference here. Or
> something else is different. Might also already be fixed in 5.16...
> too many unknowns still. I will do another round of testing with VGA
> and see how that ends.

hello again,

thanks for your effort Karol. i've just found another time the bug and:

1) kept the vga cable in the same place.

2) connected a dvi cable between the same computer and the same monitor.

3) told xrandr to dup the signal through the dvi cable:

DISPLAY=:0.0 xrandr --output DVI-D-1 --mode "1920x1080" --same-as VGA-1

4) voilà! the monitor, all alone, switched to dvi input and there is my 
x session up and running.

5) if i force the monitor to change to vga input it refuses it and 
returns to dvi

so i think the driver does its job but without actually sending anything 
through the vga cable.


thanks.



  reply	other threads:[~2021-11-19 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 13:59 [Nouveau] [INVALID_ARG] mthd 0414 dmanye
2021-11-18 15:13 ` Karol Herbst
2021-11-19  8:10   ` dmanye
2021-11-19 12:31     ` Karol Herbst
2021-11-19 12:59       ` dmanye [this message]
2021-11-19 14:39         ` Karol Herbst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7a8c82c-2fa3-60ed-40e4-ccde4a96b8c6@urv.cat \
    --to=dmanye@urv.cat \
    --cc=nouveau@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).