similar to: Extend reserved memory on 0xfc000000

Hi This patch correct on usb keyboard acces on number when enter via Ctrl + Alt + F12 on vt after Xorg running.Without this patch when enter on vt vas unable to use numbers from NumLock an only numbers from main keyboard. nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046f00a3 nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) nouveau [ DEVICE][0000:01:00.0] Family : NV40 nouveau [

Hello, I'd like to recommend backporting this commit: commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 Author: Hans de Goede <hdegoede at redhat.com> Date: Thu Jul 23 17:20:12 2015 +0200 drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c This disables MSI by default on G72 (NV46) devices where it's apparently a bit buggy. We have a later patch which turns MSI back

Hi, On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: > I'd like to recommend backporting this commit: > > commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 > Author: Hans de Goede <hdegoede at redhat.com> > Date: Thu Jul 23 17:20:12 2015 +0200 > > drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c > > This disables MSI by default on G72 (NV46)

https://bugs.freedesktop.org/show_bug.cgi?id=78441 Priority: medium Bug ID: 78441 Assignee: nouveau at lists.freedesktop.org Summary: X does not start under kernel 3.13.x QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: aebenjam at opentext.com

On Tue, Jan 19, 2016 at 5:22 AM, Jiri Slaby <jslaby at suse.cz> wrote: > Hi, > > On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: >> I'd like to recommend backporting this commit: >> >> commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 >> Author: Hans de Goede <hdegoede at redhat.com> >> Date: Thu Jul 23 17:20:12 2015 +0200 >> >>

https://bugs.freedesktop.org/show_bug.cgi?id=95095 Bug ID: 95095 Summary: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

On Thu, Feb 13, 2014 at 2:15 AM, Kui Zhang <kuizhang at gmail.com> wrote: > Hello, > > When CONFIG_DRM_NOUVEAU=y, I get following error. Blank screen after initrd. > > This was in the dmesg. > > [ 0.282559] [drm] hdmi device not found 1 0 1 > [ 0.282688] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046800a3 > [ 0.282693] nouveau [ DEVICE][0000:01:00.0]

https://bugs.freedesktop.org/show_bug.cgi?id=83168 Priority: medium Bug ID: 83168 Assignee: nouveau at lists.freedesktop.org Summary: No display after suspend to RAM QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: nsajko at gmail.com

https://bugs.freedesktop.org/show_bug.cgi?id=89775 Bug ID: 89775 Summary: Grpahics card G72 [GeForce 7200 GS / 7300 SE] 3d does not work Product: Mesa Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

On Mon, Aug 25, 2014 at 2:58 PM, Christian Costa <titan.costa at gmail.com> wrote: > --- > nvbios/info.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/nvbios/info.c b/nvbios/info.c > index 87a33d8..6b8d209 100644 > --- a/nvbios/info.c > +++ b/nvbios/info.c > @@ -119,6 +119,10 @@ int envy_bios_parse_bit_i (struct envy_bios *bios, struct

https://bugs.freedesktop.org/show_bug.cgi?id=73342 Priority: medium Bug ID: 73342 Assignee: nouveau at lists.freedesktop.org Summary: nouveau not working with yuy2 overlay QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: fbs777 at gmail.com

https://nouveau.freedesktop.org/wiki/CodeNames/ > If you're running a recent version nouveau, you can find your chipset by doing dmesg | grep -i chipset. This will always be correct, whereas the lists below are approximate. # dmesg | grep -i chipset # Not true anymore I guess. What is the 'GP' in 'GP107' if 'NV...' are the code names? # dmesg | grep -i nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=89571 Bug ID: 89571 Summary: XFX 7300 GS - Black screen with DVI when KMS(nouveau) starts - VGA working Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: blocker Priority: medium

Hello list, I have always though codec translation table is dircetly connected to system speed, utill i came across this: in my lab, i have 2 boxes, First box is an Intel Celeron 1.7 GHZ with 256M RAM: show translation Translation times between formats (in milliseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw

Hi, On 24-07-15 04:32, Ben Skeggs wrote: > On 24 July 2015 at 01:20, Hans de Goede <hdegoede at redhat.com> wrote: >> MSI interrupts appear to not work for nv46 based cards. Change the mc >> subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is >> identical to the nv44 mc code except that it does not use msi >> (it does not define a msi_rearm

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #9 from aebenjam at opentext.com --- #dmesg | grep -i chipset [ 1.887251] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) Reproduction: You can fire up an xterm with -vb to request the visual bell. You can also use control + middle-mouse-button to bring up a menu which allows you to enable/disable the visual bell. Let me

MSI interrupts appear to not work for nv46 based cards. Change the mc subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is identical to the nv44 mc code except that it does not use msi (it does not define a msi_rearm callback). BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=90435 Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

Hi, On 30-07-15 16:09, Ilia Mirkin wrote: > FWIW this is a fail on nv50+ as well. See for example > https://bugs.freedesktop.org/show_bug.cgi?id=91445 > > My suspicion is that this is due to the lack of PUSH_KICK in the *Done > exa handlers -- works fine with DRI2, but DRI3 has no synchronization > and so the commands never get flushed out. Easily verified by sticking >

On Sun, Dec 9, 2018 at 12:24 AM James <bjlockie at lockie.ca> wrote: > > https://nouveau.freedesktop.org/wiki/CodeNames/ > > > If you're running a recent version nouveau, you can find your chipset by doing dmesg | grep -i chipset. This will always be correct, whereas the lists below are approximate. > > # dmesg | grep -i chipset > # > > Not true anymore I

The value of struct drm_device.ttm.type_vram can become -1 for unknown types of memory (see nouveau_ttm_init()). This leads to an out-of-bounds error when accessing struct nvif_mmu.type[]: [ 18.304116] ================================================================== [ 18.311649] BUG: KASAN: slab-out-of-bounds in nouveau_ttm_io_mem_reserve+0x17a/0x7e0 [nouveau] [ 18.320415] Read of