similar to: [Bug 85742] New: GF117M Can *not* use nouveau at all

Displaying 20 results from an estimated 8000 matches similar to: "[Bug 85742] New: GF117M Can *not* use nouveau at all"

2015 Nov 09
4
[Bug 92870] New: GF117M nvkm_pmu_pgob fault
https://bugs.freedesktop.org/show_bug.cgi?id=92870 Bug ID: 92870 Summary: GF117M nvkm_pmu_pgob fault Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at
2017 Jan 08
2
Erros and warning using kernel 4.10-rc2
Hi guys, I don't know if it is useful to just post some random kernel warnings/errors, but here they are: [marcos at xfiles ~]$ journalctl -b -p 3 | grep nouveau Jan 08 15:37:05 xfiles kernel: nouveau 0000:04:00.0: volt: couldn't find speedo value, volting not possible Jan 08 15:37:05 xfiles kernel: nouveau 0000:04:00.0: bus: MMIO write of ffff981f FAULT at 6013d4 [ IBUS ] Jan 08
2015 Aug 12
2
[PATCH] Revert "drm/nouveau/fifo/gk104: kick channels when deactivating them"
On Wed, Aug 12, 2015 at 3:00 PM, Afzal Mohammed <afzal.mohd.ma at gmail.com> wrote: > Hi, > > On Wed, Aug 12, 2015 at 01:17:38PM +0900, Alexandre Courbot wrote: >> This reverts commit 1addc1264852 >> >> This commit seems to cause crashes in gk104_fifo_intr_runlist() by >> returning 0xbad0da00 when register 0x2a00 is read. Since this commit was >>
2013 Oct 09
2
Panic in nouveau on resume after 5addcf0a
After 5addcf0a (nouveau: add runtime PM support (v0.9)) I'm getting kernel panics immediately after resuming from suspend. Unfortunately it happens so early that I don't get any more info than the blinking keyboard lights... The nouveau tree still panics up to 2fb9d6c, which fails before I can test it. Any ideas? Martin $ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core
2010 Jun 11
1
[BUG ?] Nouveau driver on 330M GT
Hi, I tested Nouveau with 2.6.34, and now with 2.6.35-rc2 and It does not work with my laptop (chip NVIDIA GeForce 330M GT). (I give more information of the nvidia chip below). I've seen an error message related to my nvidia chip that may also be related to my problem : pci 0000:01:00.0: no compatible bridge window for [mem 0xfff80000-0xffffffff pref] Thanks in advance for your response.
2013 Aug 30
5
[PATCH 1/2] drm/nouveau/bios/therm: handle vbioses with duplicate entries (mostly nva5)
From: Martin Peres <martin.peres at labri.fr> Some vbioses have extra useless entries after "the end" of the table. This is problematic since all of the vbios I found with this issue redefine the pwm freq divider to insane levels (52750 Hz instead of 2500), thus breaking fan management. The first solution to solve this mess would be to change the length of the table. The solution
2010 Mar 13
10
[Bug 27064] New: Nouveau fails to start X. This is a Nvidia G210m, the laptop is an asus UL50vt
http://bugs.freedesktop.org/show_bug.cgi?id=27064 Summary: Nouveau fails to start X. This is a Nvidia G210m, the laptop is an asus UL50vt Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau
2013 Aug 31
2
[PATCH] drm/nouveau/therm: ack any pending IRQ at init v2
From: Martin Peres <martin.peres at labri.fr> This is safe because ptherm hasn't been configured yet and will be a little further down the initialization path. Ptherm should be safe regarding to runtime reconfiguration. v2: - do not limit this patch to nv84-a3 and make it nv84+ Signed-off-by: Martin Peres <martin.peres at labri.fr> ---
2014 Jul 10
1
Warnings in dmesg and results of mmiotrace 10de:1140 Geforce620m Optimus Laptop Acer E1-531G
Hello in dmesg I always have these informations (I tested several kernels between 3.7 and 3.16-rc3): [ 13.742006] nouveau E[ DRM] Pointer to TMDS table invalid [ 13.742036] nouveau [ DRM] DCB version 4.0 [ 13.742038] nouveau E[ DRM] Pointer to flat panel table invalid [ 13.742079] nouveau [ DRM] ACPI backlight interface available, not registering our own [ 13.742082]
2015 Jun 16
3
Progress on nv46 vblank bug
Hi All, So I've been working~w banging my head against the nv46 vblank bug again and I've been finding out some interesting things. This is all using the latest kernel + ddx + mesa code. All of this was tested with *cold* (power removed from wall outlet for 20 seconds) boots in between the scenarios because this is really weird, all boots where into text mode. Scenario 1: a) startx
2013 Sep 08
3
[PATCH 1/2] drm/nouveau/therm: ack any pending IRQ at init
From: Martin Peres <martin.peres at labri.fr> This is safe because ptherm hasn't been configured yet and will be a little further down the initialization path. Ptherm should be safe regarding to runtime reconfiguration. v2: - do not limit this patch to nv84-a3 and make it nv84+ v3: - move the ack to fini() - disable IRQs on fini() - silently ignore un-requested IRQs
2014 Oct 25
4
linux kernel 3.17, freeze on resume
This may not be the proper place to raise this question but I've had little luck elsewhere. After trying again, unsuccessfully this time, to install the proprietary NVIDIA driver, I've decided to focus my efforts on the open source Nouveau driver. I've seen video drivers blamed for varying degrees of "freeze on resume" but I'm not certain that's what I'm up
2013 Jul 24
11
[Bug 67255] New: black screen after resuming from Hibernate
https://bugs.freedesktop.org/show_bug.cgi?id=67255 Priority: medium Bug ID: 67255 Assignee: nouveau at lists.freedesktop.org Summary: black screen after resuming from Hibernate QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: michele.cane at
2014 Jun 17
1
[REGRESSION] drm/g94/i2c: add aux channel interrupt driver
Hey, This patch causes a regression on my display-less nvd7. Commenting out the aux, aux_stat and aux_mask members in nvd0_i2c_oclass fixes boot, and makes things work normally again. broken dmesg: [ 40.314470] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 40.314729] ACPI Warning: \_SB_.PCI0.GFX0._DSM:
2017 Jan 09
0
Erros and warning using kernel 4.10-rc2
could you grab the vbios from /sys/kernel/debug/dri/1/vbios.rom and maybe also do a mmiotrace with the nvidia driver (using bumblebee or second X server by hand or so)? thanks 2017-01-08 19:22 GMT+01:00 Marcos Paulo de Souza <marcos.souza.org at gmail.com>: > Hi guys, > > I don't know if it is useful to just post some random kernel warnings/errors, but here they are: > >
2018 Dec 08
18
[Bug 108980] New: GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
https://bugs.freedesktop.org/show_bug.cgi?id=108980 Bug ID: 108980 Summary: GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2013 Apr 04
28
[Bug 63135] New: [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS
https://bugs.freedesktop.org/show_bug.cgi?id=63135 Priority: medium Bug ID: 63135 Assignee: nouveau at lists.freedesktop.org Summary: [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)
2013 Oct 10
97
[Bug 70354] New: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M)
https://bugs.freedesktop.org/show_bug.cgi?id=70354 Priority: medium Bug ID: 70354 Assignee: nouveau at lists.freedesktop.org Summary: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:
2014 Apr 01
3
CH7007A (AKA CH7006) TV OUT Support for NV11 (NVidia GeForce2 Go Dell I8K Laptop)
> On Tue, Apr 01, 2014 at 02:53:02PM -0400, Ilia Mirkin wrote: >I believe that ch7006 is the only external encoder that's supposed to >work, so you're in luck. It sounds like it passes the nv04_tv_identify >stage of nv04_tv_create -- perhaps it fails later? Although based on >the prints, it's even doing dpms stuff (but it hits _detect a second >time... odd). Try
2016 Apr 11
4
Problems with scsi-target-utils when hosted on dom0 centos 7 xen box
Hello We were attempting to use scsi-target-utils, hosted on a xen dom0 vm using localhost, and running into some problems. I was not able to reproduce this on a centos 7.2 server using the default kernel. (From dmesg) Apr 4 11:18:42 funk kernel: [ 596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv