The particular card is nvidial gtx 1050 on PCIe bus (no kernel agp mod needed).
Did my xorg.conf.new and edited. Ran "X loglevel 5 & xterm & twm ". /var/log/Xorg.log gives me some error (NO EDID) and says "640x480 mode only" in the nvidia loading/logging section (which seemed to go very well minus the monitor part). I get:
* black screen with large mouse cursor and one large keyboard cursor (both which are frozen) (aka black screen)
* re-editing and trying "vesa" driver did work - but monitor is wrong size, doesn't look great, acceleration not good, video mode for native resolution is wrong ... messed UP but 1/2 usable.
I ran xrandr thinking "ok nvidia didn't sense the monitor i will use xrandr to fix it". xrandr refuses to resize the monitor.
That seems expected (xrandr's refusal) until we say "but xrandr works when vesa is loaded instead of nvidia" (but xrandr still refuses to give my monitor's correct sizes, uses a size about 1/2 of what the LED's native size).
* one suspicious thing i see is nvidia us loading of "fb" (frame buffer) module(s). i mention that because i had a linux laptop intel graphics i setup for "fb" once. i remember it's complicated you have to have "fb" setup and boot to a graphics terminal (on linux, once linux starts the standard text console fb won't work: you have to have the kernel boot to graphics mode with text - at which point either fb or vesa works, but fb commands are touchy you have to give and take control when entering/leaving X or die if you get the comands wrong). i have no idea if any of that applies to freebsd.
_____________________
I did not compile nvidia I used the port (which should be preferred - by someone who knows). It didn't install the /compat/linux/lib but some of the libs in the list are on the system. nvidia-xconfig and nvidia-settings also were no where to be found - whoever ported it deleted those.
____________________
I've had many problems installing. 1st the "parition" didn't want to work (installing to 2nd hd with linux gpt already smack in middle after 2nd attempt). Then Win10 re-install wrote over my freebsd-boot (i reinstalled, which failed to create boot, finally figured how to make my own CAREFULLY as i didn't need the linux damaged). The Handbook has allot of outdated advice (ie, stating partition command to do something for non-GPT and i have no idea that's the case being new to freebsd). Using vesa worked (no sound yet) but xfce is highly broken: mouse cursor is "big X", often invisible, xterm has no frame wrapper (cannot move it around) and firefox - if you click on options - it closes the menu as soon as you move the mouse toward preferences. However TWM works fine except the DPI is wrong (poor fonts but not totally bad either - better than bitmap default scaled up i'm sure). Also I have to boot from USB or go into bios every time i reboot (it's one of those damn dual boot PC - can't afford a second PC). Also note i'm not gaming around this is for work and win10 won't let me work either - though i consider unix a hobby I have an app to run which is broken in win10 (likely intentionally).
Did my xorg.conf.new and edited. Ran "X loglevel 5 & xterm & twm ". /var/log/Xorg.log gives me some error (NO EDID) and says "640x480 mode only" in the nvidia loading/logging section (which seemed to go very well minus the monitor part). I get:
* black screen with large mouse cursor and one large keyboard cursor (both which are frozen) (aka black screen)
* re-editing and trying "vesa" driver did work - but monitor is wrong size, doesn't look great, acceleration not good, video mode for native resolution is wrong ... messed UP but 1/2 usable.
I ran xrandr thinking "ok nvidia didn't sense the monitor i will use xrandr to fix it". xrandr refuses to resize the monitor.
That seems expected (xrandr's refusal) until we say "but xrandr works when vesa is loaded instead of nvidia" (but xrandr still refuses to give my monitor's correct sizes, uses a size about 1/2 of what the LED's native size).
* one suspicious thing i see is nvidia us loading of "fb" (frame buffer) module(s). i mention that because i had a linux laptop intel graphics i setup for "fb" once. i remember it's complicated you have to have "fb" setup and boot to a graphics terminal (on linux, once linux starts the standard text console fb won't work: you have to have the kernel boot to graphics mode with text - at which point either fb or vesa works, but fb commands are touchy you have to give and take control when entering/leaving X or die if you get the comands wrong). i have no idea if any of that applies to freebsd.
_____________________
I did not compile nvidia I used the port (which should be preferred - by someone who knows). It didn't install the /compat/linux/lib but some of the libs in the list are on the system. nvidia-xconfig and nvidia-settings also were no where to be found - whoever ported it deleted those.
____________________
I've had many problems installing. 1st the "parition" didn't want to work (installing to 2nd hd with linux gpt already smack in middle after 2nd attempt). Then Win10 re-install wrote over my freebsd-boot (i reinstalled, which failed to create boot, finally figured how to make my own CAREFULLY as i didn't need the linux damaged). The Handbook has allot of outdated advice (ie, stating partition command to do something for non-GPT and i have no idea that's the case being new to freebsd). Using vesa worked (no sound yet) but xfce is highly broken: mouse cursor is "big X", often invisible, xterm has no frame wrapper (cannot move it around) and firefox - if you click on options - it closes the menu as soon as you move the mouse toward preferences. However TWM works fine except the DPI is wrong (poor fonts but not totally bad either - better than bitmap default scaled up i'm sure). Also I have to boot from USB or go into bios every time i reboot (it's one of those damn dual boot PC - can't afford a second PC). Also note i'm not gaming around this is for work and win10 won't let me work either - though i consider unix a hobby I have an app to run which is broken in win10 (likely intentionally).
