similar to: "Unknown LVDS configuration bits, please report" - Error

http://bugs.freedesktop.org/show_bug.cgi?id=15502 Summary: Unknown LVDS configuration bits Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: low Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: pee at

http://bugs.freedesktop.org/show_bug.cgi?id=16736 Summary: NVS 135M not supported Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

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 [

Hello Timothy, On 5 January 2016 at 07:55, Timothy Murphy <gayleard at eircom.net> wrote: > When I re-booted my HP MicroServer into CentOS-7.2 > I was given a text console. > When I run "startx" I get the response on screen [edited]: > ===================== > [tim at alfred ~]$ startx > xauth: file /home/tim/.serverauth.21307 does not exist > X.Org X Server

> No error is given in /var/log/Xorg.0.log. > It seems to find an appropriate ATI Radeon driver, > but it has the warnings > (WW) Falling back to old probe method for modesetting > (WW) Falling back to old probe method for fbdev > (WW) Falling back to old probe method for vesa Could you share your whole Xorg.0.log ? Do you use a custom xorg.conf, or custom xorg.conf.d files ?

When I re-booted my HP MicroServer into CentOS-7.2 I was given a text console. When I run "startx" I get the response on screen [edited]: ===================== [tim at alfred ~]$ startx xauth: file /home/tim/.serverauth.21307 does not exist X.Org X Server 1.17.2 Release Date: 2015-06-16 X Protocol Version 11, Revision 0 Build Operating System: 2.6.32-220.17.1.el6.x86_64 ... Build ID:

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

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

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

Commit 2a44e499 ("drm/nouveau/disp: introduce proper init/fini, separate from create/destroy") started to call display init routines on pre-nv50 hardware on module load. But LVDS init code sets driver state in a way which prevents modesetting code from operating properly. nv04_display_init calls nv04_dfp_restore, which sets encoder->last_dpms to NV_DPMS_CLEARED.

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

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=55832 Priority: medium Bug ID: 55832 Assignee: nouveau at lists.freedesktop.org Summary: xf86-video-nouveau-1.0.2 - Xorg crashes once a week : segmentation fault in NVRefreshArea QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

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

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

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 >

http://bugs.freedesktop.org/show_bug.cgi?id=14491 Summary: enabling randr-1.2 support causes LVDS unknown config bits error when starting the X server Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

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

http://bugs.freedesktop.org/show_bug.cgi?id=14567 Summary: Randr 1.2 fails on nv17 lvds in a Dell Inspiron 8100 (continued from 14491) Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau