similar to: [Bug 54512] New: xrandr does not detect screen

https://bugs.freedesktop.org/show_bug.cgi?id=103351 Bug ID: 103351 Summary: Nouveau fails when booting with a screen connected to displayport since 13a86519202c5d119d83640d6f781f3181205d2c Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

https://bugs.freedesktop.org/show_bug.cgi?id=90682 Bug ID: 90682 Summary: failed to idle channel 0xcccc0001 then crash Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee:

Op 4/12/2023 om 15:11 schreef Timur Tabi: > On Mon, 2023-12-04 at 09:51 +0100, Gert Vanhaerents wrote: >> OK? i will report it to nvidia. But with the nouveau drivers it's also not >> working. Are you sure it's not a kernel problem? >> Because according to systemd it would be a kernel problem.? (personaly i am >> also thinking it's a driver problem) >

> > No, that line is actually expected (just means accel won't work, since > NVIDIA hw now requires signed firmware, but they won't release the > ctxsw fw). Are you absolutely sure that you're seeing the outputs in > xrandr? Could you provide the output of xrandr as well as an Xorg log? > > Thanks, > > -ilia Many thanks for you help. All data below :

dmesg -t | grep -i nvidia nouveau 0000:02:00.0: NVIDIA G98 (098200a2) input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input6 input: HDA NVidia Front Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input7 input: HDA NVidia Line as /devices/pci0000:00/0000:00:07.0/sound/card0/input8 input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:07.0/sound/card0/input9

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

Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only

Hi, I am having problems with the nouveau driver from Debian. Can I get help here? Cheers

https://bugs.freedesktop.org/show_bug.cgi?id=76818 Priority: medium Bug ID: 76818 Assignee: nouveau at lists.freedesktop.org Summary: Xorg EQ overflowing lock up QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: max.snow at 4mation.com.au

https://bugs.freedesktop.org/show_bug.cgi?id=110993 Bug ID: 110993 Summary: GP107GLM [Quadro P1000 Mobile]: frequent failure to initialize displays on Thunderbolt dock Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority:

https://bugs.freedesktop.org/show_bug.cgi?id=34430 Summary: nouveau driver does not return VGA connector status breaking upower Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

On Thu, Nov 30, 2023 at 11:48:24AM +0100, Gert Vanhaerents wrote: > Hi Kernel list, > I'm the IT person of a school, earlier we used multiseatcomputers for the > school, i have maded with a XGL implementation and it works fine but not so > fantastic. The school wants that i build new computers but the XGL project > is too outdated so i can't use it anymore. > > How

Hello Andy, The CentOS 6.9 kernel we are using is 2.6.32-696.el6.x86_64. Regards, Mark Woolfson MW Consultancy Ltd Leeds United Kingdom Tel: +44 113 259 1204 Mob: +44 786 065 2778 -----Original Message----- From: Andreas Benzler Sent: Wednesday, May 31, 2017 9:54 AM To: CentOS mailing list Subject: Re: [CentOS] CentOS 6.9 Skylake soft error Hello Mark, which kernel you use? Sometimes it is

https://bugs.freedesktop.org/show_bug.cgi?id=111044 Bug ID: 111044 Summary: Resume up from suspend sometimes freezes system (Optimus/Nouveau) Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

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,

On Wed, 16 Aug 2017 12:46:46 -0700, H. Peter Anvin via Syslinux wrote: >Is that true for vesamenu only, or even for text mode syslinux? Hi, I'm using menu.c32 (text mode only), this is the complete config: [root at archlinux ~]# cat /boot/syslinux/syslinux.cfg # http://syslinux.zytor.com/wiki/index.php/Doc/menu PROMPT 0 TIMEOUT 600 UI menu.c32 MENU HIDDEN MENU CLEAR MENU COLOR screen

https://bugs.freedesktop.org/show_bug.cgi?id=64774 Priority: medium Bug ID: 64774 Assignee: nouveau at lists.freedesktop.org Summary: nouveau GF108 kernel crash in optimus mode when enabling external display output QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified

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

https://bugs.freedesktop.org/show_bug.cgi?id=54537 Bug #: 54537 Summary: native mode, forcing panel scaling Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

> > OK, so I think that these are not the HDMI/DP outputs connected to > your secondary device. They are the ones connected to your primary > device (might not be pinned out, or might only be available via an > optional dock). Normally there'd be an extra -1- in the name of such > outputs. But who knows with modesetting - perhaps it doesn't stick > that in and sticks