similar to: 6.2 Radeon HDMI audio gotcha

Hi all, I have installed a centos 6.2 x86_64 box to use as a multimedia center. All works ok, except sound over hdmi using nvidia graphics card. My lspci output: 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge

Hello, I'm looking for help figuring out why I am having problems with shutting down a machine. I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and both power down without issues. I added acpi.debug_level=1 to the grub boot as it was suggested to see more info about ACPI in the logs I found the following ACPI Errors in the /var/log/messages Oct 11

On Thu, 4 May 2023 16:32:16 -0700 Marc MERLIN <marc_nouveau at merlins.org> wrote: > Hi again, I just saw a bunch of commits from all of you (thanks), but > still can't find info if my thinkpad P73 with Quadro RTX 4000 > Mobile/TU104 is meant to be supported, or not, and if so, how I can > best report issues beyond what I've already sent. > > The intel graphics

On Fri, May 05, 2023 at 01:56:50PM -0500, Steven Kucharzyk wrote: > Nvidia does great support (on-line chat) don't remember if you need to > sign-up for free account or not but I say first hand that your talking > with an engineer who will answer *any* type question. I've been buying > Nvidia for twenty yrs. or more and have actually been to the site. > They're very

To the noueau devs: Is there an appropriate list/forum to get support for nouveau, or is this the list? The nvidia support forums seem to be for the binary nvidia driver which I'm not running. On Mon, May 08, 2023 at 05:38:38PM -0500, Steven Kucharzyk wrote: > I understand parts of your motivation in how you want to deal with > Nvidia. Without knowing what you have or have not done in

Hello, This's my first ever post to CentOS lists. Sorry if I made any mistakes. My family is familiar with this RealPlayer Gold 11 and hesitate to use VLC or others. I googled a lot and tried different settings to no avail. Could you please tell me what I need to edit in order to slow down the audio/video playback of this old player? All other apps - even some older than Realplayer can play

HDMI 3D mode support, round two. Revisions include no longer dealing with audio InfoFrames, passing infoframe data to NVKM as bags of bytes rather than as data pre-packed for the hardware, more-normal return value checking for drm_hdmi_*_infoframe_from_display_mode() results, Frame-Packing mode support, more-principled logic for enabling stereo mode support on a connector, and support for all

On Wed, Mar 29, 2017 at 8:02 AM, Ville Syrjälä < ville.syrjala at linux.intel.com> wrote: > > On Mon, Mar 27, 2017 at 05:57:57PM -0400, Alastair Bridgewater wrote: > > And the tenth patch enables stereo mode support... on HDMI and DPort > > connectors on nv50+ hardware. HDMI connectors because obvious. DPort > > connectors because of DPort to HDMI adaptors. >

HDMI 3D mode support, round three. Rebased to drm-next as it was on Sunday morning. Overall structure is the same as v2. Substantially rewrote the first patch (nv50_head_atomic_check_mode()) since a recent change to the calculation of m->v.blankus caused a merge conflict and problems with frame-packed and interlaced 3D modes, and I found a much saner model for how the timing parameters work

On Mon, Mar 27, 2017 at 05:57:57PM -0400, Alastair Bridgewater wrote: > HDMI 3D mode support, round two. Revisions include no longer dealing > with audio InfoFrames, passing infoframe data to NVKM as bags of bytes > rather than as data pre-packed for the hardware, more-normal return > value checking for drm_hdmi_*_infoframe_from_display_mode() results, > Frame-Packing mode support,

On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater <alastair.bridgewater at gmail.com> wrote: > Enable stereoscopic output for HDMI and DisplayPort connectors on > NV50+ (G80+) hardware. We do not enable stereoscopy on older > hardware in case there is some older board that still has HDMI > output but for which we have no logic for setting the Vendor > InfoFrame. > >

v2: clean up left over comments don't overwrite hdmimhz parameter cap to 297MHz Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/dispnv50/disp.c | 5 +++++ drm/nouveau/nouveau_connector.c | 15 ++++++++++----- drm/nouveau/nouveau_encoder.h | 4 ++++ 3 files changed, 19 insertions(+), 5 deletions(-) diff --git a/drm/nouveau/dispnv50/disp.c

> > OK, so I think that these are not the HDMI/DP outputs connected to > your secondary device. They are the ones connected to your primary > device (might not be pinned out, or might only be available via an > optional dock). Normally there'd be an extra -1- in the name of such > outputs. But who knows with modesetting - perhaps it doesn't stick > that in and sticks

The hdmi device is required for runtime pm. However it is not available on many esp older devices, which were all seeing these error messages. Take this opportunity to also convert to nv_debug instead of the DRM_* messages, like the rest of nouveau does. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/nouveau_drm.c | 11 +++++------ 1 file changed, 5

https://bugs.freedesktop.org/show_bug.cgi?id=58735 Priority: medium Bug ID: 58735 Assignee: nouveau at lists.freedesktop.org Summary: GeForce 680, HDMI output no good after passing through HDMI-to-DVI converter QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:

On Fri, Aug 3, 2018 at 4:08 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Fri, Aug 3, 2018 at 8:19 AM, Karol Herbst <kherbst at redhat.com> wrote: >> v2: clean up left over comments >> don't overwrite hdmimhz parameter >> cap to 297MHz >> >> Signed-off-by: Karol Herbst <kherbst at redhat.com> >> --- >>

On Fri, Jan 13, 2017 at 10:11 AM, Sylvain Fabre <sylvain at lahiette.com> wrote: > xrandr --setprovideroutputsource 1 0 seems to do nothing, either with a > monitor connected to HDMI-1 or not. The second monitor is detected and > available in the screen configuration tool of KDE, but it remains black, no > window, nothing. > > With a monitor conected in HDMI-1, here are the

Now that the plane code takes the underscan setup into account, we can safely attach the underscan props to the HDMI connector. We also take care of filling AVI infoframes correctly to expose the top/botton/left/right bar. Note that these underscan props match pretty well the overscan_{left,right,top,bottom} properties defined in config.txt and parsed by the VC4 firmware. Signed-off-by: Boris

Now that the plane code takes the underscan setup into account, we can safely attach the underscan props to the HDMI connector. We also take care of filling AVI infoframes correctly to expose the top/botton/left/right bar. Note that these underscan props match pretty well the overscan_{left,right,top,bottom} properties defined in config.txt and parsed by the VC4 firmware. Signed-off-by: Boris

Op 24-07-13 09:13, Dave Airlie schreef: > After a full device powerdown via the optimus power switch, we seem > to lose the HDMI device completely on power on, this keep track of > whether we had a hdmi audio sub function device at power on, and > pokes a magic register to make it reappear after the optimus power > switch is thrown. > > This at least works on my NVC4 machine,