Trying to install the driver for my main GPU,the Intel UHD Graphics 630.(i915)

marietto

I'm going to do that again.

netbsd-marietto# git clone https://github.com/riastradh/netbsd-src

Cloning into 'netbsd-src'...
remote: Enumerating objects: 5915052, done.
remote: Counting objects: 100% (144/144), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 5915052 (delta 80), reused 107 (delta 67), pack-reused 5914908
Receiving objects: 100% (5915052/5915052), 2.14 GiB | 4.91 MiB/s, done.
Resolving deltas: 100% (4107989/4107989), done.
Updating files: 100% (200812/200812), done.

netbsd-marietto# cd netbsd-src

netbsd-marietto# git checkout reredrm56

Updating files: 100% (180844/180844), done.
Branch 'reredrm56' set up to track remote branch 'reredrm56' from 'origin'.
Switched to a new branch 'reredrm56'

netbsd-marietto# mkdir -p /home/mario/Desktop/Dati/obj
netbsd-marietto# mkdir -p /home/mario/Desktop/Dati/tools

netbsd-marietto# pwd
/home/mario/Desktop/Dati/netbsd-src

netbsd-marietto# ./build.sh -U -u -j14 -m amd64 -O /home/mario/Desktop/Dati/obj -T /home/mario/Desktop/Dati/tools tools

===> Tools built to /home/mario/Desktop/Dati/tools
===> build.sh ended: Thu Sep 23 16:38:53 CEST 2021
===> Summary of results:
build.sh command: ./build.sh -U -u -j14 -m amd64 -O /home/mario/Desktop/Dati/obj -T /home/mario/Desktop/Dati/tools tools
build.sh started: Thu Sep 23 16:34:46 CEST 2021
NetBSD version: 9.99.82
MACHINE: amd64
MACHINE_ARCH: x86_64
Build platform: NetBSD 8.99.22 amd64
HOST_SH: /bin/sh
No $TOOLDIR/bin/nbmake, needs building.
Bootstrapping nbmake
MAKECONF file: /etc/mk.conf
TOOLDIR path: /home/mario/Desktop/Dati/tools
DESTDIR path: /home/mario/Desktop/Dati/obj/destdir.amd64
RELEASEDIR path: /home/mario/Desktop/Dati/obj/releasedir
Created /home/mario/Desktop/Dati/tools/bin/nbmake
Updated makewrapper: /home/mario/Desktop/Dati/tools/bin/nbmake-amd64
Tools built to /home/mario/Desktop/Dati/tools
build.sh ended: Thu Sep 23 16:38:53 CEST 2021
===> .

netbsd-marietto# ./build.sh -U -u -j14 -m amd64 -O /home/mario/Desktop/Dati/obj -T /home/mario/Desktop/Dati/tools kernel=GENERIC

link GENERIC/netbsd

/home/mario/Desktop/Dati/tools/bin/x86_64--netbsd-ld -Map netbsd.map --cref -T netbsd.ldscript -Ttext 0xffffffff80200000 -e start -z max-page-size=0x200000 -X -o netbsd ${SYSTEM_OBJ:[@]:Nswapnetbsd.o} ${EXTRA_OBJ} vers.o swapnetbsd.o
NetBSD 9.99.82 (GENERIC) #0: Thu Sep 23 16:44:13 CEST 2021
text data bss dec hex filename
21476444 727136 1368064 23571644 167acbc netbsd
mv -f netbsd netbsd.gdb
/home/mario/Desktop/Dati/tools/bin/x86_64--netbsd-strip -g -o netbsd netbsd.gdb
===> Kernels built from GENERIC:
/home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC/netbsd
===> build.sh ended: Thu Sep 23 16:44:28 CEST 2021
===> Summary of results:
build.sh command: ./build.sh -U -u -j14 -m amd64 -O /home/mario/Desktop/Dati/obj -T /home/mario/Desktop/Dati/tools kernel=GENERIC
build.sh started: Thu Sep 23 16:42:23 CEST 2021
NetBSD version: 9.99.82
MACHINE: amd64
MACHINE_ARCH: x86_64
Build platform: NetBSD 8.99.22 amd64
HOST_SH: /bin/sh
MAKECONF file: /etc/mk.conf
TOOLDIR path: /home/mario/Desktop/Dati/tools
DESTDIR path: /home/mario/Desktop/Dati/obj/destdir.amd64
RELEASEDIR path: /home/mario/Desktop/Dati/obj/releasedir
Updated makewrapper: /home/mario/Desktop/Dati/tools/bin/nbmake-amd64
Building kernel without building new tools
Building kernel: GENERIC
Build directory: /home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC
Kernels built from GENERIC:
/home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC/netbsd
build.sh ended: Thu Sep 23 16:44:28 CEST 2021
===> .

netbsd-marietto# cp -r /home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC/netbsd /

rvp

marietto

cp -r /home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC/netbsd /

Please don't use the -r flag to copy single files--too easy to make mistakes.

When you include text output in your posts, can you enclose them within code tags:

```text
output of commands
blah blah
blah
```

It makes things much easier to read.

marietto I have specified in /etc/xorg.conf.d/xorg.conf

That location is wrong. The correct locations are given here

marietto Since I want that the primary card is the intel igpu,that I've placed as primary on the BIOS,

Correct.

marietto I have disabled the nouveau driver.

Correct.

marietto Not sure if I should disable also the i915drmkms driver.

You should not (unless the Intel DRM driver doesn't work).

marietto At a certain point of the netbsd booting my monitor turns off and it says : "no signal"

Disable the i915drmkms driver temporarily, boot back into NetBSD and recompile only the kernel after uncommenting these lines in sys/arch/amd64/conf/GENERIC:

options        DRM_MAX_RESOLUTION_HORIZONTAL=1920      # Limit DRM size in horizontal dimension
options        DRM_MAX_RESOLUTION_VERTICAL=1080        # Limit DRM size in vertical dimension

Re-create the drm devices (they're lost if the modesetting driver fails to run) as Step 2 in post #3; then comment out the userconf=disable i915drmkms* in /boot.cfg; reboot and try the newly-built kernel.

marietto

Rebooted and I have specified in /etc/xorg.conf.d/xorg.conf,the following

Section "Device"
Identifier "Card0"
Driver "modesetting"
EndSection

It didn't work. You can read the logs here

https://pastebin.ubuntu.com/p/Y3H7hScvTK/

and here

https://pastebin.ubuntu.com/p/HhTrbMPz8t/

marietto

I forgot to mention that I'm using this boot.cfg file :

menu=Boot normally:rndseed /var/db/entropy-file;gop 4;boot
#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
userconf=disable nouveau*
userconf=disable i915drmkms*
default=1
timeout=5
clear=1

Since I want that the primary card is the intel igpu,that I've placed as primary on the BIOS,I have disabled the nouveau driver. Not sure if I should disable also the i915drmkms driver.

marietto

UPDATE :

this is what I did,before to boot NetBSD,mounting the NetBSD partition from FreeBSD :

nano /boot.cfg :

menu=Boot normally:rndseed /var/db/entropy-file;gop 4;boot
#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
userconf=disable nouveau*
#userconf=disable i915drmkms*
default=1
timeout=5
clear=1

nano /mnt/ada1p2/etc/X11/xorg.conf.d/xorg.conf

Section "Device"
Identifier "Card0"
Driver "modesetting"
EndSection

At a certain point of the netbsd booting my monitor turns off and it says : "no signal" and I cannot do anything anymore"....

marietto

rvp

-) That location is wrong. The correct locations are given here.

Please don't give me the man pages. They are too full of informations that I'm not able to filter,because my low technical knowledge. give me clearly what's the proper path. very thanks.

-) You should not (unless the Intel DRM driver doesn't work).

The screen is turned off if enabling or disabling nouveau and / or i915drmkms. Inside xorg.conf is not accepted intel and modesetting.

-) Disable the i915drmkms driver temporarily....

I will do this.

JuvenalUrbino

marietto Please don't give me the man pages. They are too full of informations that I'm not able to filter,because my low technical knowledge. give me clearly what's the proper path. very thanks.

From a user standpoint, there's really no practical advantage in preferring BSD over a user-friendly Linux distro in day to day usage, be it desktop or server. The main reason you see people using BSD here, is that they got interested in these systems at some point, appreciated some of their features, their design choices, their development model or their community and decided they wanted to dig deeper into them, learn them.

While personally I started using FreeBSD before Linux, I would have never considered installing BSD weren't it for a true interest in learning, understanding and having fun with a system which wouldn't have hidden what was going on beneath the surface.

Man pages are possibly the best maintained and the most reliable source of information on BSDs, and it's really hard to imaging leaving without. Not seldom will they provide the provide the proper answer to any question and it's safe to assume every BSD user will have to look up man pages sooner or later, so the sooner one starts the easier will dealing with BSD in everyday life turn out.

Do not get me wrong, the fact you're just getting started with this is pretty understandable; everything seems a little bit alien and keeping track of all the info you're given is not a easy task. And while it's not hard to relate (everybody has gone through it at a certain point), I still recommend you to try to be a little bit keener to cooperate and look up official documentation.

Worth noticing this forum is populated by non technical users who work outside of IT.

marietto The screen is turned off if enabling or disabling nouveau and / or i915drmkms

so none of the four possible combinations apparently leads to a working console?

rvp

marietto give me clearly what's the proper path

Already given in post #17

marietto if a) netbsd is able to boot,but when I do : startx,xorg does not start.

Of course this won't start: In this configuration you've disabled both your DRM drivers and then you're asking to run the modesetting X display driver which needs DRM kernel drivers. modesetting won't work on genfb. The only X display driver which will work on genfb is wsfb

marietto if b) the monitor turns off and I can't use netbsd anymore

Multiple reasons could account for this:

The new kernel doesn't have the MAX_RESOLUTION changes because you compiled the kernel with -u.
Solution: compile only the kernel again, this time, omit the -u flag to do a full rebuild of the kernel.
(Really, -u is for developers. Users should just rebuild the whole kernel from scratch.)
You've specified a serial console and/or are running in a VM.
Solution: Run on the regular console and actual HW. Also without -s (single-user mode)
You've made the Intel card the primary in BIOS, but, have disabled i915drmkms and this confuses NetBSD nouveau DRM driver.
Solution: If the Intel card is selected in BIOS, then nouveau should be disabled. And vice versa.
In both cases, the Xorg display driver should be modesetting. Make sure you re-create the DRM devices in /dev before starting X.

Q: Is it possible to disable the unwanted graphic adapters completely in your BIOS instead of only selecting which one to make primary?

Your GPU HW or HW combination is not supported yet.
Solution: report with full dmesg/Xorg.log on the Github issues page.

marietto Below u can read the logs file attached.

These logs don't help at all. Here, you've disabled both the Intel and Nvidia DRM drivers--after which the safe genfb framebuffer driver takes over (which we already know works), and then you're trying to run the modesetting X driver on genfb (which is invalid--modesettingonly works if the kernel DRM drivers are enabled).

Since we want to make DRM work, enable the Intel DRM driver (first), then boot into it.
Set up sshd (instead of using a serial console) so that you can log into the system to shut it down safely in case the display becomes unusable.

marietto

JuvenalUrbino
I think that you should take much care of my point of view,not of the point of view of a generic "user" ; As a psychologyst I can tell you that the way the concepts are shown, the way they are aggregated, the way they are related to each other, makes the difference in the ability to absorb or skim them. The man pages are up to date and full of information for sure, but from my point of view they get lost in too much detail and do not go straight to the point. The form in which concepts are shown on the man pages are not tailored for learning how things should be done, but more for showing what you can do. Consequently, they aren't useful for me, because they do not help me to focus my attention on what I really need, because I do not have the skills to understand completely what I really need, since my job is different. I am someone who tries to get by and tries to cross the advices that I get from the various forums and thanks to the intuition and the trial and errors method,usually I can solve a problem,if this is not much complicated. I'm a psychologist. That's why I can't use them but I look for much more targeted tutorials. Your point of view is the one of a systems engineer, an experienced IT technician, mine is that of someone who like to play with operatying systems as apprentice and hobbyist, but above all it is the point of view of a psychologist who studies the learning processes of the human mind.

----> so none of the four possible combinations apparently leads to a working console?

exactly. In addition,below u can see that as soon as NetBSD try to boot,it switches to VESA mode...

maybe because on the boot.cfg I have disabled the nouveau driver and the i915drmkms driver ?

marietto

So,I tried the suggestions of "rvp" ; I mean I did this 😀

1) I've recompiled the kernel after uncommenting these lines in sys/arch/amd64/conf/GENERIC:

options DRM_MAX_RESOLUTION_HORIZONTAL=1920 # Limit DRM size in horizontal dimension
options DRM_MAX_RESOLUTION_VERTICAL=1080 # Limit DRM size in vertical dimension

2) I've recreated the drm devices ;

3) I've tried to boot netbsd using two different versions of boot.cfg 😀

menu=Boot normally:rndseed /var/db/entropy-file;gop 4;boot
#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
userconf=disable nouveau*
#userconf=disable i915drmkms*
default=1
timeout=5
clear=1
consdev com1

AND this content inside /etc/X11/xorg.conf.d/xorg.conf

Section "Device"
Identifier "Card0"
Driver "modesetting"
EndSection

if b) the monitor turns off and I can't use netbsd anymore

if a) netbsd is able to boot,but when I do : startx,xorg does not start. Below u can read the logs file attached.

dmesg : https://pastebin.ubuntu.com/p/TB4f88ZYzm/

xorg.log : https://pastebin.ubuntu.com/p/7FqGdQNjbW/

marietto

Ok. I did everything like you have suggested. But maybe I did some mistake. So,I want to make a recap :

0) I've used the phisycal installation of netBSD to do everything

1) I have uncommented these lines in sys/arch/amd64/conf/GENERIC:

options DRM_MAX_RESOLUTION_HORIZONTAL=1920 # Limit DRM size in horizontal dimension
options DRM_MAX_RESOLUTION_VERTICAL=1080 # Limit DRM size in vertical dimension

2) I've recreated the drm devices with :

cd /dev
sh ./MAKEDEV drm0 drm1 drm2

3) recompiled tools and kernel with the following commands :

./build.sh -U -j14 -m amd64 -O /home/mario/Desktop/Dati/obj -T /home/mario/Desktop/Dati/tools tools
./build.sh -U -j14 -m amd64 -O /home/mario/Desktop/Dati/obj -T /home/mario/Desktop/Dati/tools kernel=GENERIC

3.1) copied the netbsd kernel from /home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC/netbsd to / with the following command 😀

cp /home/mario/Desktop/Dati/obj/sys/arch/amd64/compile/GENERIC/netbsd /

4) I've edited the file boot.cfg like this 😀

nano /boot.cfg


menu=Boot normally:rndseed /var/db/entropy-file;gop 4;boot
menu=Boot single user:rndseed /var/db/entropy-file;boot -s
menu=Drop to boot prompt:prompt
userconf=disable nouveau* 
#userconf=disable i915drmkms*
default=1
timeout=5
clear=1

5.1) I don't know if it useful,but I did an additional try,trying to boot netBSD with bhyve and trying to capture the early boot messages because I wanted to know what's happened as soon as netbsd booted,to understand the reason why the screen turns off and I've captured the messages that u see on the picture below

6) I've used this xorg.conf file,saved on : /etc/X11/xorg.conf.d

Section "Device"
Identifier "Card0"
Driver "modesetting"
EndSection

what else ? nothing is changed. At some point the screen turns off and I can't use netBSD anymore.

rvp

marietto 1) I have uncommented these lines in sys/arch/amd64/conf/GENERIC

Correct.

marietto 2) I've recreated the drm devices with

Correct. Not normally needed, but, if there are errors when starting the modesetting driver, then those devices are removed--for some reason.

marietto 3) recompiled tools and kernel with the following commands

Correct. However, in your case, you don't need to build tools. The kernel alone is sufficient.

marietto 3.1) copied the netbsd kernel

Correct.

marietto 4) I've edited the file boot.cfg like this

First: just remove that gop 4 directive.

As I mentioned before, it's only useful with the genfb/wsfb combo., since the wsfb Xorg driver doesn't switch resolutions on its own--it just uses whatever the bootloader/kernel set-up. The DRM drivers usually switch to the highest possible resolution, but sometimes, what's chosen can exceed what the monitor is capable of (turning the display off). Which is why we're constraining the max resolution to 1920x1080.

And, I don't understand why you've disabled the i915drmkms driver when you want your Intel card to be used. This might be a problem if you've made the Intel card the primary in BIOS and then the nouveau driver takes over.

Look, this is very simple: If the Intel card is primary, then disable the nouveau driver in /boot.cfg.
If one of the Nvidia cards is primary, then the i915drmkms driver has to be disabled.

I would suggest either:
a) completely disabling the unwanted video card in BIOS (if possible), or
b) physically removing the unneeded cards (if possible).

marietto 5.1) I don't know if it useful,but I did an additional try,trying to boot netBSD with bhyve and trying to capture the early boot messages

bhyve screenshots are not useful as they're not real HW. You can make a more useful screenshot like this:
Use your phone to make a short movie (at the highest possible resolution) of the screen. Then, step through the ending frames one-by-one and post the frame just before the screen blanks.

Even more useful would be combining that with the dmesg and Xorg.log files from the machine. If you enable sshd, then you just login--even if the screen is off--and collect those files.

marietto 6) I've used this xorg.conf file,saved on : /etc/X11/xorg.conf.d

Correct.

marietto

3) I tried to compile the kernel alone without the tools,but an error came up,telling that it wants the tools to build the kernel

4) going to try

4.1) I haven't disabled the i915drmkms driver from boot.cfg,because I used the hashtag before the command,like this : #userconf=disable i915drmkms* ; maybe you didn't see it

5) my BIOS doesn't allow to disable a graphic card. I can only select which card I want as primary or secondary

6) I can't remove physically a graphic card

rvp

marietto The error message is : failed to load dmc firmware i915/kbl_dmc_ver1_04.bin
but I'm not sure. I'm not able to see it clearly...

That looks about right, but, I can't make out clearly either. (Atleast hold the camera sideways, mate.)
Looks like either:
a) you'll have to bring in the Linux firmware blobs--see this post, or
b) it's a driver bug and you'll have to report it.

marietto I used the hashtag before the command,like this : #userconf=disable i915drmkms* ; maybe you didn't see it

My mistake, I thought the nouveau was commented out.

marietto

I made new experiments :

1) I have disabled the gop 4 directive,but the screen turned off again

2) I've installed ssh in NetBSD and I've been able to connect to the ssh server using ssh client on Windows. It means that the NetBSD kernel does not crash

3) I've recorded a video because I wanted to capture the latest boot message displayed on the screen just before the monitor turns off. Do you want to give it a look ? it is here

https://drive.google.com/file/d/1H8uKrzirCqtd1IQ1JrW_HXNl6Rm3hNnn/view?usp=sharing

The error message is : failed to load dmc firmware i915/kbl_dmc_ver1_04.bin

but I'm not sure. I'm not able to see it clearly...

marietto

I've tried to follow this tutorial,but at some point it didn't work :

https://www.unitedbsd.com/d/253-intel-hd-graphics-on-nuc6cayh/46


netbsd-marietto# git clone https://git.kernel.org/.../git/firmware/linux-firmware.git

netbsd-marietto# mkdir /libdata/firmware/i915drmkms

netbsd-marietto# mv linux-firmware/i915 /libdata/firmware/i915drmkms/

netbsd-marietto# rm -rf linux-firmware

netbsd-marietto# ftp http://defert.com/netbsd/intel_csr.c.patch

netbsd-marietto# patch /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_csr.c intel_csr.c.patch
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- intel_csr.c.orig   2020-02-14 15:34:58.000000000 +0100
|+++ intel_csr.c        2021-04-04 12:41:15.467350912 +0200
--------------------------
patch: **** can't find /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_csr.c

netbsd-marietto# cp -r /home/mario/Desktop/Dati/netbsd-src/sys/external/bsd/drm2/dist/drm/i915 /usr/src/sys/external/bsd/drm2/dist/drm

netbsd-marietto# patch /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_csr.c intel_csr.c.patch
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- intel_csr.c.orig   2020-02-14 15:34:58.000000000 +0100
|+++ intel_csr.c        2021-04-04 12:41:15.467350912 +0200
--------------------------
Patching file /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_csr.c using Plan A...
Hunk #1 failed at 49.
Hunk #2 failed at 205.
Hunk #3 failed at 338.
3 out of 3 hunks failed--saving rejects to /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_csr.c.rej
done

rvp

marietto at some point it didn't work

Only the firmware needs to be installed, mate. The patching and compiling stuff is for getting his Intel card to work. You don't need it.

And, you've overwritten the 9.2 intel_csr.c with the same file from 9.99.82. (Why?)

Remove the intel_csr.c.rej
Rename the intel_csr.c.orig file saved (in the same dir.) by patch back over intel_csr.c

marietto

done. what should I do now ?

marietto

$ cd /usr/src/sys/arch/amd64/conf
$ config GENERIC
$ cd ../compile/GENERIC
$ make
$ mv /netbsd /netbsd.old
$ cp netbsd /
$ cd /dev
$ sh ./MAKEDEV drm0 drm1 drm2
$ cd /etc/X11/xorg.conf.d
$ mv xorg-intel.conf xorg.intel.conf_
$ mv xorg-modesetting.conf_ xorg-modesetting.conf

kern info [drm] failed to find VBIOS tables (VBT)
i915drmkms0 : interrupting at ms19 vec0

rvp

marietto

kern info [drm] failed to find VBIOS tables (VBT)
i915drmkms0 : interrupting at ms19 vec0

Those are standard messages. They're fine. The next message is more important:

[drm] finished loading DMC firmware ...

This means that the right firmware was copied to the correct location. If the screen is blanking even after this, then its a driver bug and you should report it on Github. BTW, I just tried the new DRM drivers on my own 10-year-old integrated Intel card, and while the driver didn't blank the screen, the results of running X were either:

a) locked-up the system (with glamor acceleration--only on -HEAD; 9.2 doesn't have it), or
b) a completely unusable display woth glamor disabled.

Can you:

Post the dmesg output?
Try this experiment: After the screen goes blank, wait a few minutes; then blindly type-in (on the console) your username, password, and then startx
I want to see if running X produces a display. Post the Xorg.log file.
(You can check if X is running by logging in via ssh.)
Disable your Intel driver, and see if the new Nvidia DRM drivers work better.

rvp

marietto

$ cd /usr/src/sys/arch/amd64/conf
$ config GENERIC
$ cd ../compile/GENERIC
$ make
$ mv /netbsd /netbsd.old
$ cp netbsd /

I don't know what all this is, but, you don't need to do it. If you want to compile the kernel use build.sh as you've already done.

« Previous Page Next Page »