similar to: PROBLEM: new kernel 3.15.0-rc8 hangs completely with CONFIG_DRM_NOUVEAU enabled

Yes, you are right - the Intel-chip is connected to the display, it just offloads 3D work to do to the nVidia-chip, which isn't even to tell how to get the EDID. I just wanted to try it out, simply for two reasons: 1. I heard that nouveau now "supports" the chip, and since I got the hardware, I wanted to try it out - just for the fun of it. :) 2. As far as I am informed, a way to

First off, the current state of support for Maxwell (GM107/NV110) is not very useful to end-users. It's especially not useful if it's a 3d accelerator card without outputs (as yours appears to be), since acceleration is not supported in 3.15 out of the box. You'd have to figure out how to extract the context switching firmware from the blob driver and load it in nouveau. I'm told

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

https://bugs.freedesktop.org/show_bug.cgi?id=99841 Bug ID: 99841 Summary: Switching to VT freezes X only on a dual screen Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

@bjorn: any further ideas? Otherwise I'd like to just go ahead and fix this issue inside Nouveau and leave it there until we have a better understanding or non Nouveau cases of this issue. On Tue, May 21, 2019 at 7:48 PM Karol Herbst <kherbst at redhat.com> wrote: > > doing the same on the bridge controller with my workarounds applied: > > please note some differences: >

was able to get the lspci prints via ssh. Machine rebooted automatically each time though. relevant dmesg: kernel: nouveau 0000:01:00.0: Refused to change power state, currently in D3 kernel: nouveau 0000:01:00.0: Refused to change power state, currently in D3 kernel: nouveau 0000:01:00.0: Refused to change power state, currently in D3 kernel: nouveau 0000:01:00.0: tmr: stalled at

Hi Bjorn, I was playing around with some older information again (write into the PCI config to put the card into d3 state). And there is something which made me very curious: If I put the card manually into any other state besides D0 via the 0x64 pci config register, the card just dies and pci core seems to expect this to not happen. pci_raw_set_power_state has this

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Greetings, I am resending this as it doesn't appear in the archives and no one responded...maybe it got routed to /dev/null or something :-) I have asked this question the Scientific Linux mailing list (a few months ago) and got the suggestion I talk to the kernel guys. I pinged a kernel guy I know, and his suggestion was to ask the Nouveau list. So here I am. :-) I have had my work laptop

Hi, any pointer on how to debug this: [ 19.741005] nouveau 0000:01:00.0: enabling device (0541 -> 0543) [ 19.741095] nouveau 0000:01:00.0: Using 32-bit DMA via iommu [ 19.741165] nouveau 0000:01:00.0: NVIDIA GP108 (138000a1) [ 19.752562] tg3 0004:01:00.0 enP4p1s0f0: renamed from eth0 [ 19.832879] [drm] Initialized ast 0.1.0 20120228 for 0005:02:00.0 on minor 0 [ 19.856391] nouveau

Hi List, I have an ASUS G73S laptop with our favorite OS installed and all up-to-date. Sound has always "just worked" When I use the Preferences>Sound app I can setup the hardware, input, output and was overall very impressed. One can check each speaker and the laptop has a front left and right and also has a bass speaker which seems to be connected to the left rear. The various

https://bugs.freedesktop.org/show_bug.cgi?id=107959 Bug ID: 107959 Summary: System hangs up when loading nouveau for NVIDIA MX150 card Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

doing the same on the bridge controller with my workarounds applied: please note some differences: LnkSta: Speed 8GT/s (ok) vs Speed 2.5GT/s (downgraded) SltSta: PresDet+ vs PresDet- LnkSta2: Equalization stuff Virtual channel: NegoPending- vs NegoPending+ both times I executed lspci while the GPU was still suspended. 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core

On Mon, Jun 03, 2019 at 03:18:56PM +0200, Karol Herbst wrote: > @bjorn: any further ideas? Otherwise I'd like to just go ahead and fix > this issue inside Nouveau and leave it there until we have a better > understanding or non Nouveau cases of this issue. Nope, I have no more ideas. > On Tue, May 21, 2019 at 7:48 PM Karol Herbst <kherbst at redhat.com> wrote: > >

ohh nvm. It was a mistake on my end. Sorry for the noise On Wed, Jun 19, 2019 at 2:07 PM Karol Herbst <kherbst at redhat.com> wrote: > > Hi Bjorn, > > I was playing around with some older information again (write into the > PCI config to put the card into d3 state). And there is something > which made me very curious: > If I put the card manually into any other state

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]

Ack! This slipped through my email. I am terribly sorry. Thank you so much for responding. On 04/06/2014 08:43 PM, Ilia Mirkin wrote: > On Sun, Apr 6, 2014 at 7:16 PM, ~Stack~ <i.am.stack at gmail.com> wrote: >> Greetings, [snip] >> My working kernel is: 2.6.32-358.23.2.el6.x86_64 (and anything before). >> >> The problem kernel is: 2.6.32-431.1.2.el6.x86_64 and

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: > >

On Tue, May 21, 2019 at 03:28:48PM +0200, Karol Herbst wrote: > On Tue, May 21, 2019 at 3:11 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > On Tue, May 21, 2019 at 12:30:38AM +0200, Karol Herbst wrote: > > > On Mon, May 20, 2019 at 11:20 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > > > On Tue, May 07, 2019 at 10:12:45PM +0200, Karol Herbst