what's the scenario within I should produce those files ? choose from below the right comtinabion 
1) with Intel and Nouveau DRM drivers disabled in boot.cfg
2) with Nouveau disabled in boot.cfg
3) with intel disabled in boot.cfg
4) with intel and nouveau enabled in boot.cfg
I tried with intel and nouveau driver disabled....also tried with nouveau disabled and intel enabled. nothing to do.
I changed the monitor. I'm using a very old monitor,Samsung syncMaster 740N. It is a VGA only monitor. So,the cable is VGA behind and it became HDMI on the intel graphic card port,thanks to a hardware signal converter. It works like the AOC. Same errors and it turns off with the intel driver enabled. So,it does not depend on my monitor. I suspect that only some specific monitors will work. But it's hard to determine in advance which monitors are ok.
marietto what's the scenario within I should produce those files ?
Don't bother. This is a kernel issue. I get the same error with my old integrated Intel card where the console display is OK (but X doesn't work as I mentioned above).
If you want to get the EDID data, then you'll have to put back the GENERIC kernel and run the program on that. (Though I don't see, now, what use that would be as the 5.6 DRM drivers are still very much a WIP... I had hoped the issue was your monitor sending slightly non-standard EDID data, and that we could work around it by applying some known workarounds.)
so ? is there anything that I can do ? This item can help me ? ----> https://www.amazon.it/LogiLink-hd0105-HDMI-EDID-emulatore-Nero/dp/B07F2N9ZTS/ref=sr_1_6?__mk_it_IT=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=Hdmi+Edid+Emulator&qid=1634161069&sr=8-6
marietto is there anything that I can do ?
Wait and keep an eye on the Github page; and if there are changes to the reredrm56 branch, do a git pull in the netbsd-src directory, then recompile the new kernel sources. Until then, run genfb/wsfb. We know that works.
marietto This item can help me ?
Very unlikely as this is a NetBSD driver issue... I wouldn't spend any lire on this.
Do u know why Taylor R. Campbell doesn't reply at all on his github account ? I mean,here : https://github.com/riastradh/netbsd-src/issues/36 ; the bug that I've reported is 18 days old now.
--> run genfb/wsfb. We know that works.
yes it works,but my goal was to try to passthrough the RTX 2080 ti from host to guest using qemu and nvmm. I can't make more tests if netbsd chooses it as primary card. ok. then. I will change os for the moment. I will remove netbsd and I will assign the empty space to Open Indiana and I will do the same using bhyve in this case. Maybe in the future I will come back.
I've removed the GTX 1060 from my PC and I've moved the 2080 ti to the PCI slot 2 because I've thought that the previous problem could be caused by the fact that I had two nvidia graphic cards installed and netbsd could have been confused. Previously I had saved an image of the previous installation done with dd and today I've restored that backup file. Unfortunately it won't boot. It gives the error : can't open root device. Can you help me to fix this error ? I suspect that I could also fix the graphic driver error that we know. thanks.
marietto Previously I had saved an image of the previous installation done with dd and today I've restored that backup file. Unfortunately it won't boot.
Now you know why dd isn't a good backup solution (aside from being horribly wasteful of space): If the restoration is off by even 1 sector from where it was read, you'll make a hash of things.
I've restored the backup using this procedure :
ntfs-3g /dev/da0p2 /mnt/da0p2 # G-DRIVE USB (where is saved the netbsd img file that contains the old installation of netbsd)
cd /mnt/da0p2/Backups/img/BSD/NetBSD
efi-netbsd92-no.img efi-netbsd92.img netbsd92.img
mdconfig -a -t vnode -f netbsd92.img -u 0
mount -t ufs /dev/md0 /mnt/netbsd
mount -t ufs /dev/ada0s1 /mnt/ada0s1
cd /mnt/netbsd
rsync -avxHAX * --exclude 'etc/fstab' /mnt/ada0s1The method that I've used worked. Netbsd has been able to boot,but,unfortunately I had the same graphic card problem as before.
yes,I tried to mount the netbsd partition in Ubuntu,but it refuses to mount it in rw (using ufstype=ufs2,instead 44bsd it is not recognized at all),so I went on FreeBSD and it did it. Anyway,in another post you tried to mount the netbsd partition on linux using the parameter 44bsd,but it does not work at all. Instead,ufs2 works,even if only in ro.
UPDATE :
I've installed OS108,based on :
localhost# uname -a
NetBSD localhost 9.1_STABLE NetBSD 9.1_STABLE (GENERIC) #1: Sun Nov 8 03:50:47 IST 2020 root@unitedbsd.com:/usr/srcNEW/objNEW/sys/arch/amd64/compile/GENERIC amd64and now I can use the screen at a good resolution (1920x1080),but without using my intel gpu neither my nvidia geforce RTX 2080 ti gpu. If I remember correctly some time ago I was not able to do that using netbsd 9.2. I'm not using any xorg.conf file and I have modified only the boot.cfg file like this :
banner=Welcome to OS108
banner=================
banner=
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
default=1
timeout=10
clear=1So,now I would like to know why with OS108 / netbsd 9.1-Stable I can do this but I can't do it with the 9.2. And more important,what happens if I make the upgrade of the 9.1-Stable to the 9.2. Will it stop working ?
marietto So,now I would like to know why with OS108 / netbsd 9.1-Stable I can do this but I can't do it with the 9.2.
I don't understand this: gop 4 is what you used last year with 9.2, right? And gop 4 with genfb/wsfb has always worked for you, as far as I can tell. Post /var/run/dmesg.boot and /var/log/Xorg.0.log.
Try, out the latest NetBSD images. There have been a lot of fixes, and your Intel and nVidia cards may now be supported (may even be accelerated now!)