similar to: bad things happened, 4.4-rc3, nve7, virgl test server

Hei, 839ca903f12e (drm/nouveau/kms/nv50: transition to atomic interfaces internally, 2016-11-04) seems to introduce a regression on my machine. Attached dmesg output. Has anyone else seen this on a MacBookPro? Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu -------------- next part -------------- [ 0.000000] microcode: microcode updated early to revision 0x16, date = 2016-04-01 [

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

Hi Everyone! I've been trying to get my Nvidia 9800m GT working with the latest nouveau drivers with no luck so far. First of all I'd like to mention that this is a weird card as it is an SLI in one piece of hardware (not 2 separated cards). It came with my Dell XPS M1730 laptop. I know SLI is not currently supported and _I don't want_ to use SLI, I just would like to use one of

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

For some reason it seems to fail somewhere in either nouveau_display_create or nouveau_display_init. Kernel 3.16 is nearly 2 years old though, and countless changes and fixes have gone into the nouveau kernel driver since then. Does this still happen with a recent kernel? You can try a livecd from https://nouveau.pmoreau.org/ which has all the very latest nouveau-related software. On Wed, Jul 6,

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different

dmesg output: --------------------------------------------------------------------------------------------------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.0-38-generic (buildd at allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #52~14.04.1-Ubuntu

Hello. Minimal testcase for my problem: No X running, just a TTY. Use of the nouveau kernel module as of today (or any older) with an up to date vanilla kernel. Hardware: DELL Vostro 3500 with Geforce 310M. To suspend to ram I use this script, as suggested in Documentation/power/s2ram.txt: #!/bin/sh sync echo 1 > /sys/power/pm_trace echo mem > /sys/power/state When I try to suspend to

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

Hi, I took this issue to the Fedora forum initially, but no-one there has been able to offer any guidance, so I have decided to come to the nouveau community directly. I was running a KDE desktop under Fedora 21 successfully, including the ability to use a direct text login on an older card (GXT 560 Ti) with an entirely stock Fedora, fully updated. I simply replaced the old card with an

Is that an error that prevents anything from working? It's probably expected... On Thu, Jul 7, 2016 at 2:07 PM, abcd <abcdeluxe at web.de> wrote: > Thanks for the quick help! > > Indeed a kernel update resolved the issue, there one problem left > though: I get an error: > > Xorg.0.log: Couldn't load sub module "fb". > > I can't find out what

On Sun, Mar 9, 2014 at 10:51 AM, Marcin Slusarz <marcin.slusarz at gmail.com> wrote: > [ 326.168487] ====================================================== > [ 326.168491] [ INFO: possible circular locking dependency detected ] > [ 326.168496] 3.13.6 #1270 Not tainted > [ 326.168500] ------------------------------------------------------- > [ 326.168504] ldconfig/22297 is

https://bugs.freedesktop.org/show_bug.cgi?id=94725 Bug ID: 94725 Summary: Nouveau driver fails to load on GM204 Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Howdy! I've been doing a lot of troubleshooting, and haven't arrived at a solution yet. Kernel log attached. VBIOS also attached. Ubuntu 19.10 $ uname -a Linux joyful 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l|grep nouveau ii libdrm-nouveau2:amd64 2.4.99-1ubuntu1 amd64

Hellow all, i need help to fix this bug: ACPI BIOS Bug: Error: A valid RSDP was not found (20120711/tbxfroot-219) Because of this first errors i get this after, and it causes don''t work USB ports and some PCI cards on the system: can''t find IRQ for PCI INT A; please try using pci=biosirq Kernel: 3.6.1-xen self compiled (work perfect without xen multiboot) Xen Version: 4.2

Hm, well you can see the messages about failure to set plls, which is why you don't see anything. The only odd thing I see is that you're using vesa, which can definitely mess things up. Try not using that. Also try booting with nouveau.debug=debug drm.debug=0xe which might provide more relevant info. On Jun 12, 2015 8:34 AM, "Andre Campos Rodovalho" <andre.rodovalho at

dmesg output after a resume from a suspend. the device in question was /dev/sdb mounted on /home. after a device failure to resume properly, the link is then reset by the kernel but comes back as /dev/sde. /dev/sdb disappeared entirely, and is now referred to as sde. attempted to remount rw of sde, seemed to succeed, mount/mtab said that it was rw now but i couldn''t write to the volume

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

Am Mittwoch, den 06.05.2020, 10:26 -0400 schrieb Ilia Mirkin: > [please keep list cc'd in your replies] > > On Wed, May 6, 2020 at 10:15 AM Milan Bu?ka <milan.buska at gmail.com> wrote: > > [ 0.000000] Linux version 5.6.10-zotac (root at saux) (gcc version 9.3.0 (SAUX Aarch64)) #1 SMP PREEMPT Tue May 5 22:16:40 CEST 2020 > > [ 0.000000] Machine model: NVIDIA