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

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

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

Hello, guys. First apologize my flaws, I am not a native English speaker and thus am prone to stupid errors. My box is an ASUSTek Notebook with Optimus capability (no, this is NOT about Optimus, I don't try to use Optimus yet, so please don't switch off here) with a running Gentoo. The first GPU is an Haswell-based Intel chip, the second one is a nVidia GeForce GTX 850M, the chip is a

Hi, I have just passed through my NVIDIA Geforce GTX 560 to CentOS 6.3 x86-64 HVM domU. I am wondering whether the Xen VGA Passthrough is successful. The following information is obtained from inside CentOS 6.3 x86-64 HVM domU: 00:05.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device 3527

Hi, I have just passed through my NVIDIA Geforce GTX 560 to CentOS 6.3 x86-64 HVM domU. I am wondering whether the Xen VGA Passthrough is successful. The following information is obtained from inside CentOS 6.3 x86-64 HVM domU: 00:05.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device 3527

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

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

On Thu, Apr 10, 2014 at 6:08 PM, ~Stack~ <i.am.stack at gmail.com> wrote: >> 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: > [snip] >>> Can you test with a fresh kernel (e.g. some >>> distro's livecd) rather than one based on a 5-year old release? > > Greetings, >

https://bugs.freedesktop.org/show_bug.cgi?id=110714 Bug ID: 110714 Summary: Xorg crashes randomly because of memory leak Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau

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

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

On 09/03/2013 09:45 PM, Ben Skeggs wrote: > On Fri, Aug 30, 2013 at 5:11 PM, Lucas Stach <dev at lynxeye.de> wrote: >> Am Freitag, den 30.08.2013, 15:36 +1000 schrieb Ben Skeggs: >>> On Fri, Aug 30, 2013 at 12:01 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>>> On Thu, Aug 29, 2013 at 9:58 PM, Ben Skeggs <skeggsb at gmail.com> wrote:

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

@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

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:

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