Hello I'm currently running NetBSD 9.2 stable: ``` # uname -a NetBSD localhost 9.2_STABLE NetBSD 9.2_STABLE (GENERIC) #0: Wed Apr 27 16:54:20 UTC 2022 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 ``` and I've been having some issues getting my graphics card to work. I'm currently trying to get an nvidia GTX 770 to work with nouveau, and it seems like it should be supported: [https://man.netbsd.org/NetBSD-9.2-STABLE/nouveau.4](https://man.netbsd.org/NetBSD-9.2-STABLE/nouveau.4) However, once the boot process is done, even if I have xdm=NO on /etc/rc.conf, I get a blank (black) screen. The machine is not crashed, as I can ssh into it. The blank screen does not happen if I disable the nouveau driver on the boot manager with `userconf disable nouveau`. Several debug outputs: dmesg: https://termbin.com/dlx4 dmesg.boot https://termbin.com/0wfq lspci -vnn https://termbin.com/p60z Xorg.0.log (after running startx) https://termbin.com/8bac modstat https://termbin.com/5zb5 Any help would be appreciated, thanks!

@"tse"#p11595 Those `autoconfiguration` errors are from the kernel driver, and will need a fix there. Try the [latest](https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/) -HEAD image. The newer DRM drivers in that might work.

> @"tse"#p11595 [](https://termbin.com/0wfq) > > lspci -vnn Next time, better to run `pcictl pci0 list -N` on NetBSD, since that will print also the attached driver (similarly to `lspci -k`), useful to get an idea of what is supposedly working and what not. To print all PCI devices names and ids, you can do: [code] /usr/sbin/pcictl pci0 list \ | awk -F: '{print "pcictl pci0 dump -b "$1" -d "$2}' \ | sort -u| sh | grep -i 'device name' | cut -d ':' -f 2 [/code]

> @"tse"#p11595 Several debug outputs: > dmesg: > [https://termbin.com/dlx4](https://termbin.com/dlx4) At first glance it seems like a regression [introduced](https://bugzilla.kernel.org/show_bug.cgi?id=201847) somewhere in 2017 (many reports like this one upon web search), and probably now [fixed](https://www.spinics.net/lists/kernel/msg3773355.html) upstream. I fear that the graphic stack implemented in -current, which comes from Linux 5.6, would still be affected.

@"rvp"#p11603 Hello, Thank you for the replies. If I try the latest HEAD kernel (https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/binary/kernel/netbsd-GENERIC.gz - MD5 (/netbsd-HEAD) = 0dd1f8ed7828c36b11281cd780f0cf20) I do not get a blank screen, however my console becomes completely unresponsive. I can still ssh into the box. ``` # uname -a NetBSD localhost 9.99.96 NetBSD 9.99.96 (GENERIC) #0: Mon May 2 10:50:02 UTC 2022 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 ``` ``` # cat boot.cfg menu=Boot HEAD:rndseed /var/db/entropy-file;boot netbsd-HEAD menu=Boot normally:rndseed /var/db/entropy-file;boot menu=Boot single user:rndseed /var/db/entropy-file;boot -s menu=Drop to boot prompt:prompt default=1 timeout=5 clear=1 ``` ``` # pcictl pci0 list -N 000:00:0: Intel Haswell Host Bridge, DRAM (host bridge, revision 0x06) [pchb0] 000:01:0: Intel Haswell PCI-E x16 Controller (PCI bridge, revision 0x06) [ppb0] 000:20:0: Intel 9 Series USB xHCI (USB serial bus, xHCI) [xhci0] 000:22:0: Intel 9 Series MEI Controller (miscellaneous communications) 000:26:0: Intel 9 Series USB EHCI (USB serial bus, EHCI) [ehci0] 000:27:0: Intel 9 Series HD Audio (mixed mode multimedia, HD Audio 1.0) [hdaudio1] 000:28:0: Intel 9 Series PCIe (PCI bridge, revision 0xd0) [ppb1] 000:28:3: Intel 9 Series PCIe (PCI bridge, revision 0xd0) [ppb2] 000:29:0: Intel 9 Series USB EHCI (USB serial bus, EHCI) [ehci1] 000:31:0: Intel Z97 LPC (ISA bridge) [ichlpcib0] 000:31:2: Intel 9 Series SATA Controller (AHCI) (SATA mass storage, AHCI 1.0) [ahcisata0] 000:31:3: Intel 9 Series SMBus Controller (SMBus serial bus) [ichsmb0] 001:00:0: NVIDIA product 1184 (VGA display, revision 0xa1) [nouveau0] 001:00:1: NVIDIA product 0e0a (mixed mode multimedia, HD Audio 1.0, revision 0xa1) [hdaudio0] 003:00:0: Attansic Technologies Killer E2200 (ethernet network, revision 0x13) [alc0] ``` dmesg (before startx) https://termbin.com/xrbi dmesg (after startx) https://termbin.com/cwvj dmesg.boot https://termbin.com/lx3i Xorg.0.log: https://termbin.com/6o6n

@"tse"#p11614 Please file a [PR](https://www.netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd) about this. This is a driver issue.

@"rvp"#p11615 Will do. As for the NetBSD release, should I report it as -CURRENT, -HEAD, or NetBSD 9.2-STABLE?

@"tse"#p11617 -CURRENT and -HEAD can be used interchangeably, so either will do. File it against that. Bugs get fixed in -HEAD, then back-ported to the still-supported releases.

@"rvp"#p11618 PR submitted (kern/56813). I hope it has all the required information. In the meantime, is there any alternative that would allow me to use my system with its native resolution (2560x1440), preferably that would allow me to watch videos on firefox? :) (preferably if I could do it with 9.2-STABLE). Thank you very much for all the help.

> @"tse"#p11621 is there any alternative that would allow me to use my system with its native resolution (2560x1440), preferably that would allow me to watch videos on firefox? 🙂 (preferably if I could do it with 9.2-STABLE). You can disable/unplug the NVidia card and use embedded graphics in your Intel chip. Since it's a 4th gen Intel Core we're talking about, it should be supported by i915drmkms even on 9.2. This would be imho the recommended workaround for the time being. Otherwise you can use the generic framebuffer driver (can't say if it supports 2K res), wsfb(4). See [How to use Xorg's wsfb display driver with a UEFI/BIOS framebuffer, and change its resolution](https://wiki.netbsd.org/tutorials/x11/how_to_use_wsfb_uefi_bios_framebuffer/). Have also a look at [this thread](http://daemonforums.org/showthread.php?t=11852) on DaemonForums in case.

> @"JuvenalUrbino"#p11622 You can disable/unplug the NVidia card and use embedded graphics in your Intel chip. According to his `pcictl` output, OP doesn't have an integrated Intel graphics card. But, `wsfb` can be made to work at the native resolution using `gop` in `/boot.cfg`

nvidia / nouveau problems on 9.2

tse

there have been some developments - I'm quite new at this, so surely I'm to blame to some extent.
I have recompiled the kernel (did a git checkout today), and I also compiled the modules, and put them in /stand which I had not done before.

If I do not disable nouveau* I end up with a very messed up framebuffer (a jumble of tiny green patches is the best I can describe it as), and a non working system, as I cannot ssh into it.

Later today I'll also post an update on my PR.

(I am a bit confused about this development however, since there are no nouveau files under /stand)

rvp

tse I end up with a very messed up framebuffer (a jumble of tiny green patches is the best I can describe it as)

On older Intel integrated GPUs, newdrm has a few issues, one of which is not retrieving the correct EDID. The result is a severely messed up console and a hard-lockup as soon as you start X. The messed-up screen I managed to work around. The lockup I've still to figure out. Can't say if it is a similar issue or something else without looking at the dmesg output. (And without access to the HW, I'll not even attempt a fix 😁 .)

Are you sure that gop lists only those 2 modes? Hmm. OK, let's see if we can "persuade" your BIOS to accept the panel's native resolution (this is for genfb only, mind) by sending it a patched EDID. I'll send you something this weekend. (Will need to hack the bootloader as well...)

tse

rvp

😮 oh wow this sounds like a terrible amount of work! I cannot in good conscience "ask" you to do this. I was hoping for a fix to land before 10 comes around... is that not a realistic expectation? :x

rvp

tse this sounds like a terrible amount of work!

Nah, the bootloader should be easy to patch. For the EDID-stuff however, I'll have to chew through its specs.

tse I was hoping for a fix to land before 10 comes around... is that not a realistic expectation?

You'll have to ask the official folks this. I don't move in such rarefied circles...

Edit: does the gop output differ if you connected your monitor to the integrated Intel GPU?

tse

rvp Edit: does the gop output differ if you connected your monitor to the integrated Intel GPU?

I do not know since my monitor does not have a DVI port, and I don't have at my disposal a way of going from DVI to HDMI (the integrated gpu only has VGA and DVI outputs).

JuvenalUrbino

I encountered the same problem on a GTX 1060, using the latest 9.99.96 HEAD snapshot. Bug reported https://mail-index.netbsd.org/netbsd-bugs/2022/05/19/msg075056.html

JuvenalUrbino

Updates on my PR:

https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=56847
https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53126

« Previous Page