similar to: [PATCH] drm/nouveau: fix blank LVDS screen regression on pre-nv50 cards

Displaying 20 results from an estimated 100 matches similar to: "[PATCH] drm/nouveau: fix blank LVDS screen regression on pre-nv50 cards"

2009 Aug 16
2
[PATCH] drm/nv04: fix null pointer dereferences of native_mode
Subject: [PATCH] drm/nv04: fix null pointer dereferences of native_mode nv_connector->native_mode is not set when no modes were found for the connector, so its existence can't be assumed. In nv04_dfp_mode_fixup, reject the mode if GPU scaling is enabled but native mode is not known. In nv04_dfp_mode_set, use clock value from nv_encoder->mode instead of nv_connector->native_mode. If
2012 Oct 27
47
[Bug 56461] New: NV11 black screen & kernel hang on loading nouveaufb
https://bugs.freedesktop.org/show_bug.cgi?id=56461 Priority: medium Bug ID: 56461 Assignee: nouveau at lists.freedesktop.org Summary: NV11 black screen & kernel hang on loading nouveaufb QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: chris at
2009 Aug 12
14
[PATCH 00/12] TV-out modesetting kernel patches.
This patch series adds TV-out modesetting support to the KMS implementation. I've tried to test it on all the hardware I've got at hand (that is nv11, nv17, nv34, nv35, nv40, nv4b) with every possible output combination; I believe it has reached a mergeable state, however it depends on some commits from drm-next that haven't got into Linus' tree yet, if you agree to merge this
2009 Aug 13
9
[PATCHv2 01/10] drm/nouveau: Fix a lock up at NVSetOwner with nv11.
It seems it was only locking up in the context of nouveau_hw_save_vga_fonts, when it actually did something (because the console wasn't already in graphics mode). Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_hw.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_hw.c
2011 Oct 29
15
[Bug 42384] New: X fails on NV11 with Error allocating scanout buffer: 0
https://bugs.freedesktop.org/show_bug.cgi?id=42384 Bug #: 42384 Summary: X fails on NV11 with Error allocating scanout buffer: 0 Classification: Unclassified Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium
2009 Dec 13
3
[PATCH] drm/nouveau: use drm debug levels
- Use driver level (0x2) for NV_DEBUG instead of all levels - Create a NV_DEBUG_KMS for KMS level (04) and use them in modesetting code - Remove a few odd NV_TRACE calls and replace with NV_DEBUG_KMS Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_bios.c | 12 +++++----- drivers/gpu/drm/nouveau/nouveau_connector.c | 8 +++---
2009 Oct 08
0
[PATCH] Add an option for Nouveau debugfs output that depends on DEBUG_FS and update help entry for Nouveau KMS
From: Matt Parnell <parwok at gmail.com> drm/nouveau: Add DRM_NOUVEAU_DEBUG option Sometimes we have DEBUG_FS enabled, but don't want output from certain modules. Most modules make this an option, so I figured that Nouveau needed it too. I also made it exlicit that CONSOLE_FRAMEBUFFER is needed for textmode use with KMS. Signed-off-by: Matt Parnell <parwok at gmail.com> ---
2009 Oct 08
2
[PATCH] drm/nouveau: Add DRM_NOUVEAU_DEBUG option
From: Matt Parnell <mparnell at gmail.com> Sometimes we have DEBUG_FS enabled, but don't want output from certain modules. Most modules make this an option, so I figured that Nouveau needed it too. Signed-off-by: Matt Parnell <mparnell at gmail.com> --- drivers/gpu/drm/Kconfig | 11 +++++++++++ drivers/gpu/drm/nouveau/Makefile | 2 +-
2013 Jun 09
4
[Bug 65576] New: [NV11] no EGL with nouveau_vieux_dri - no DRI_IMAGE
https://bugs.freedesktop.org/show_bug.cgi?id=65576 Priority: medium Bug ID: 65576 Assignee: nouveau at lists.freedesktop.org Summary: [NV11] no EGL with nouveau_vieux_dri - no DRI_IMAGE Severity: normal Classification: Unclassified OS: Linux (All) Reporter: chris at edesix.com Hardware: x86 (IA32)
2008 Apr 23
3
[Bug 15666] New: Nouveau error: Unknown LVDS configuration bits
http://bugs.freedesktop.org/show_bug.cgi?id=15666 Summary: Nouveau error: Unknown LVDS configuration bits Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2008 May 05
1
[Bug 15833] New: NV50: Unknown LVDS configuration bits, please report
http://bugs.freedesktop.org/show_bug.cgi?id=15833 Summary: NV50: Unknown LVDS configuration bits, please report Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2008 May 20
0
report : Unknown LVDS configuration bits
Hi, I try to use the "nouveau" (from git today march 20) driver on my laptop : an hp dv9000 that have an 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GS (rev a1) X says : (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found and ask to report : (EE) NOUVEAU(0): Unknown LVDS configuration bits, please report the
2008 Aug 15
2
[Bug 17149] New: Backlight is reduced on LVDS when an external vga monitor is connected
http://bugs.freedesktop.org/show_bug.cgi?id=17149 Summary: Backlight is reduced on LVDS when an external vga monitor is connected Product: xorg Version: 7.3 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: low Component: Driver/nouveau
2008 Aug 29
2
[Bug 17347] New: NV34M (12" powerbook G4) LVDS not supported
http://bugs.freedesktop.org/show_bug.cgi?id=17347 Summary: NV34M (12" powerbook G4) LVDS not supported Product: xorg Version: git Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2010 Feb 24
1
Why report LVDS as disconnected when lid is closed?
What's the motivation behind commit 60821e0 (drm/nouveau: report LVDS as disconnected if lid closed)? The only noticeable effect I can see from it is that if I turn on my laptop and then close the lid, X fails to start as it can't find any screens. In fact, if I close the lid before nouveau initialises, I don't even get a framebuffer console. I know I can just use the ignorelid
2011 Dec 18
1
Why do non-lvds monitors default to dithering these days?
In the past we assumed that external displays did their own dithering if needed. GPU based dithering is only needed for laptop displays if i had to guess. I was almost thinking my monitor was malfunctioning because of strange barely visible flickering. Now it *seems* as if dithering was the problem, although time will have to tell, because it's subtle to see these effects. Ofcource i can try
2019 May 27
0
[PATCH 1/2] drm/nouveau/disp/nv50-: force scaler for any non-default LVDS/eDP modes
On Sun, 26 May 2019 at 08:41, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > Higher layers tend to add a lot of modes not actually in the EDID, such > as the standard DMT modes. Changing this would be extremely intrusive to > everyone, so just force the scaler more often. There are no practical > cases we're aware of where a LVDS/eDP panel has multiple resolutions >
2009 Oct 18
4
[Bug 24603] New: LVDS-0 off after resume, PGRAPH_ERROR in kern.log
http://bugs.freedesktop.org/show_bug.cgi?id=24603 Summary: LVDS-0 off after resume, PGRAPH_ERROR in kern.log Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2016 Feb 16
0
"Unknown LVDS configuration bits, please report"
When booting arch linux on laptop Dell Latitude D800, there is displayed following in one of the first ten lines. "[Nouveau] "Unknown LVDS configuration bits, please report"" [root at arch ~]# dmesg | grep nouveau [ 0.848209] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x028600a2 [ 0.848219] nouveau [ DEVICE][0000:01:00.0] Chipset: NV28 (NV28) [ 0.848223] nouveau [
2007 Jul 05
0
RANDR1.2 and LVDS
Hi! I've written a small amount of code that gets the randr 1.2 branch much closer to working for me on a laptop. Most of the changes are fairly obvious, but a couple of comments: 1) The changes to nv_crtc.c are clearly bogus, but I'm not sure what on earth these registers do. I need to set them to get a moderately sane-looking picture 2) The fp registers poked in nv_output.c