• NetBSD
  • nvidia / nouveau problems on 9.2

rvp According to his pcictl output, OP doesn't have an integrated Intel graphics card

I'm skeptic about this since Intel Core processors usually have integrated graphics (Xeon do not) and a 4th gen Intel Core should come with Intel HD 4600 graphics embedded. Is it possibile that it's being disabled at BIOS level due to the connected NVidia card ?

  • rvp replied to this.
  • rvp likes this.

    JuvenalUrbino (Xeon do not)

    It might be a Xeon. From OP's lspci output:

    00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode])

    But, a cpuctl identify would be a more definitive confirmation...

    sorry I've been busy and I haven't been able to get back to this. The cpu is not a xeon, and I believe I have the integrated graphics card disabled in the bios. Later today, if I get the chance I'll try out the integrated graphics and report back 🙂

    edit: the motherboard only has vga and dvi outputs, so I cannot test it. I tried the gop option as suggested, but neither the HDMI nor the DisplayPort outputs list my native resolution.

    I guess I can still ssh into the machine and /pray very hard for a fix 🙂

    • rvp replied to this.
    • Jay likes this.

      tse I tried the gop option as suggested, but neither the HDMI nor the DisplayPort outputs list my native resolution.

      The gop command queries the UEFI firmware for the resolutions it supports. On laptops, UEFI is almost sure to return the highest resolution the panel supports (otherwise, users will want their money back, right?). For HDMI or DP-connected monitors, UEFI may (or may not) query the monitor for EDID data. Or, it may simply return some standard resolutions: 1920x1080, 1024x768, etc.

      Does your external monitor support your card's best resolution?

      • tse replied to this.

        tse Can you show what resolutions the gop command outputs (and in the same order)?
        Also a hexdump of the monitor's EDID data.
        Describe your HW setup too.

          rvp Also a hexdump of the monitor's EDID data.

          Forget this--I got the EDID from your Xorg.0.log

          rvp sorry for the late reply. I'll do this tomorrow if I get the chance!

          rvp

          the gop command outputs

          *0: 800x600 BGRR pitch 800 bpp 32
           1: 1024x768 BGRR pitch 1024 bpp 32

          as far as hardware goes, that hasn't been mentioned before, I have an
          Acer Predator XB271HUA (a 2k monitor with gsync), which is connected to the netbsd computer via HDMI (displayport is being used to connect it to a windows machine).
          The motherboard is an MSI Z97 Gaming 5, and the only setting I can think of as being relevant here is:

          Settings\Advanced\Integrated Graphics Configuration\Initiate Graphic Adapter -> PEG

          The CPU is an Intel i5-4690K @ 3.5 GHz.

          The memory is two 8gb sticks: DDR3 SDRAM - Kingston KHX1866C10D3/8G

          Did I miss something important?

          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 replied to this.

            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 replied to this.

              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 replied to this.

                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 replied to this.

                  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).

                  8 days later