similar to: [PATCH] vga16fb: refuse to load in face of other driver controlling primary card

let vga16fb claim 0xA0000+0x10000 region as its aperture; drm drivers don't use it, so we have to detect it and kick vga16fb manually - but only if drm is driving the primary card Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: James Simmons <jsimmons at infradead.org> Cc: Dave Airlie <airlied at redhat.com> Cc: Ben Skeggs <bskeggs at redhat.com> --- no

It simplifies nouveau code by removal of detection which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc:

fb_do_apertures_overlap is returning wrong value when one aperture is completely whithin the other. Add generic ranges_overlap macro (probably kernel.h candidate) and use it here. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc: Andrew Morton <akpm at linux-foundation.org> ---

This series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc

This series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc

Hello I have an active-active DRBD cluster using OCFS2 as the filesystem on the drbd devices. I started getting a "general protection fault error" when trying to mount any one of the ocfs2 volumes I have, even when running mount on a single node, with no mounted FSs on the other node. The kernel trace follows at the bottom of this message. Does anyone know what could have been

https://bugs.freedesktop.org/show_bug.cgi?id=27706 Summary: Blank screen and "Error referencing VRAM ctxdma: -12" on NV44A with ubuntu lucid beta 2 (worked in alpha 3) Product: xorg Version: 7.5 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority:

https://bugs.freedesktop.org/show_bug.cgi?id=30158 Summary: nouveau fails to display on external monitor Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

Hi everyone I have a Digium card TE110P and after plug it, turn on the computer and configure, the LEDs don't light up in spite of what Digium FAQ says about the LEDs: When will the LED's light up on my TDM400P/TE110P/TE2XXP/TE4XXP? ... The TE110P LED's will light up RED when the span is configured and kernel module is loaded. If configured correctly and a circuit or channel bank is

I'm trying to run Total Annihilation but this error comes up: wine totala.exe fixme:system:SystemParametersInfoW Unimplemented action: 94 (SPI_GETMOUSETRAILS) fixme:system:SystemParametersInfoW Unimplemented action: 93 (SPI_SETMOUSETRAILS) X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 1 (X_CreateWindow) Serial number of failed

Hi Everyone! I've been trying to rediscover the lost art of appliance-ification. SystemD is actually pretty amenable to masking tty1 and spawning a program instead of login which makes a config console a rather easy thing to do (mostly). Have that bit done, no problem. Happily spawning a rather locked down program. However, you seem to be limited in terms of color palette, creating a new

Almost all PCI drivers using remove_conflicting_framebuffers() wrap it with the same code. --- v2: add kerneldoc for DRM helper v3: propagate remove_conflicting_framebuffers() return value + move kerneldoc to where function is implemented Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- drivers/video/fbdev/core/fbmem.c | 35 ++++++++++++++++++++++++++++++++

Hi, all. I''m trying to track down some stability issues with my Xen system, and in the course of doing so, I''ve found a few things that are probably unrelated, but things I''d like to clean up nonetheless. I have a Xen guest instance running my Xen0 kernel. When it boots I get: Jul 29 01:31:37 loki kernel: fb0: VGA16 VGA frame buffer device Jul 29 01:31:37 loki

I don't know enough about it to know whether this is a known problem (I couldn't make much sense of what I found on Google), but it seems to be a journal-related issue. Is it likely that data has been corrupted? Do I need to take any action? 2.6.12-9-amd64-k8-smp, Ubuntu 5.10, dual opteron 2GB Jan 23 03:08:22 infinity kernel: [24686.841032] Unable to handle kernel NULL pointer

On Thu, Aug 06, 2020 at 03:46:23AM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 47ec5303 Merge git://git.kernel.org/pub/scm/linux/kernel/g.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=16fe1dea900000 > kernel config: https://syzkaller.appspot.com/x/.config?x=7c06047f622c5724 >

Trying to create a 32 bit domU is unsuccessful. I also tried some of the older builds from http://people.debian.org/~joeyh/d-i/images and found similar problems Can someone point me to an installer kernel that will work? dom0: Linux dom0test 2.6.18-6-xen-amd64 #1 SMP Tue Aug 19 06:15:09 UTC 2008 x86_64 GNU/Linux Hardware: Intel Pentium D 960 with EMT64 /etc/xen# xm create -c xm-debtest1.cfg

My log says suddenly: Dec 14 02:35:16 hp1 kernel: [1492482.232822] o2net: no longer connected to node hp2 (num 1) at 192.168.1.2:7777 Dec 14 02:35:18 hp1 kernel: [1492483.960150] BUG: soft lockup - CPU#1 stuck for 61s! [kvm:32398] I have no idea what happens here and why - but the result are a lot of problems with virtual machines. Viele Gr??e Andreas Rittershofer -- Hier k?nnte keine

https://bugs.freedesktop.org/show_bug.cgi?id=61731 Priority: medium Bug ID: 61731 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau not working on second monitor QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rvhbox-freedesktop at

Since upgrading from Ubuntu 10.10 I have had problems with graphics. The problems started after I initially upgraded to Ubuntu 11.04 but then installed xubuntu-desktop over it, but I have had the same problem all my fresh installs of Xubuntu 11.04 too. FPS previously averaging about 30 or 35 FPS while playing an OpenGL game with WINE now starts at 20 FPS for 2 or 3 minutes and then slows down to

Currently vesafb/efifb/... is kicked when hardware driver is registering framebuffer. To do it hardware must be fully functional, so there's a short window between start of initialisation and framebuffer registration when two drivers touch the hardware. Unfortunately sometimes it breaks nouveau initialisation. Fix it by kicking firmware driver(s) before we start touching the hardware.