NVIDIA 14.3 AGAIN

Total novice installed HBSD and tried to get NVIDIA working!
I have ended to create nvidia-drm nvidia-driver ,... at /usr/ports

Told hardened that it load linux as insecure kernel module,....
.... but most likely I should build linux as welL?? version mitcmatch,..


Solutions:

a) is there way to use NVIDIA drivers whitout it uses linux ???

b) easy way to get back packages, note hardenedbsd at top,
and installation works???

c) build linux.ko linux64.ko from sources,... where its hide?

d) install FreeBSD

e) go back Ubuntu 22.04

Select one or more solutions you like and
give some code!

Problem purely due folks do hate nvidia and do like have
to have nvidia chain NOT working at FreeBSD.

This is not hightech problem, packing and suply chain problem.
It dessapeared from Ubunut time ago,.. but same troubles.

ps. IF YOU THINK WRITEING WORD NOVICE OR YOU THINK TO
SAY "look handbook" your identity will be marked as AI automatic
answering machine you are banned by administration. Be clewer.


joni
 
And you cannot use graphics/nvidia-drm-*-kmod[-devel], as they require corresponding graphics/drm-*-kmod, and they actually mandate LinuxKPI, which requires Linuxulator-related kernel modules.

So don't expect Wayland to work sanely if completely disabling Linux supports.

As far as I understand, Wayland wants DRM interface with KMS.

On the other hand, xorg would work without Linux support as SirDice already noted.
 
I haven't used Wayland for awhile, but did find out today that it's not working with my machine that has an Nvidia card.. That machine does run the linux service. It's not something I use much, so I'm not bothering to troubleshoot. As has been said above, Xorg is working without problems.
 
they actually mandate LinuxKPI, which requires Linuxulator-related kernel modules.
I always understood LinuxKPI is completely separate from linux(4). But you probably know a lot more about the NVidia (DRM) drivers than I do.
 
I always understood LinuxKPI is completely separate from linux(4). But you probably know a lot more about the NVidia (DRM) drivers than I do.
Apart from nvidia, kmods from graphics/drm-*-kmod (which graphics/nvidia-drm-*-kmod[-devel] require to run) automatically pulls in linux[64].ko.
 
hi,
Build x11/nvidia-kmod from ports and turn off "LINUX". It's not required for the driver to actually work, it's for the Linux compatibility so it's usable from there.
This ain't help,
what are cprrect settings /boot/loader.conf and /etc/rc.conf ?

Iám not telling what i have tried out, those ain´t work out !

Yes, if possible, whitout linux !
 
And you cannot use graphics/nvidia-drm-*-kmod[-devel], as they require corresponding graphics/drm-*-kmod, and they actually mandate LinuxKPI, which requires Linuxulator-related kernel modules.

So don't expect Wayland to work sanely if completely disabling Linux supports.

As far as I understand, Wayland wants DRM interface with KMS.

On the other hand, xorg would work without Linux support as SirDice already noted.
No Iám not intrested wauland,..... X11 is ok and it can be started from commandline when needed?
 
X11 is ok and it can be started from commandline when needed?
Yes.
I'm logging into FreeBSD via historical login prompt, then, startx when I need X11.
I don't like graphical logins unless it is developed in conjunction with computer systems that it is intended to run on "as a whole supported product", like (already ancient) EWS.
 
I have liked graphical system at Ubuntu,... after ZFS was messed and "unsuported" latest version
I desided to give possibility to FreeDSB. I'am trying to get two two screen systems to work,..
due freebsd has not easyly cuda available still need to have ubuntu machine for calculation
works. Due everyday tasks can be handeled by NextCloud,... there is variety devices that
can www UI to nextcloud! No need to too far WayLand.

Out of box I got graphics system that has messed screens whit difrent colours and visible text
but mouse was floating,... after many changes I have ended situation where i do have
nvidia, nvidia-drivers from ports all others uninstalled, upploading at rc.conf,... dose not
load driver, "can not attach",... it took time to learn powerfull disable-module command
that is needed to boot whitout nvidia,... disable-module nvidia !

I have used so much time whit all combinations that time expense is such high that
not getting it work is great loss! It had been good idea to leave earlyer.

There is all ways better to do, HandBook should give bullet proof installation guidance
and whit NVIDIA it fails, all threads about subject do not give bullet proof recepy.

I have not tried to install nvidia-drivers directly from nvidia,... but whit ubuntu decade
ago it ended to mess whit every update/upgrade so that's not solution for easy way
to keep system update.

Also dose all work if I do pkg lock to ports ? If I get idea how to get it work.

Combitronix of case:

2x /boot/loader.conf /etc/rc.conf
3x pkg , ports, native from nvidia
3x nvidia-drm, nvidia, nvidia-modeset
2x linux, no linux
2x xorg.conf, no xorg

2x3x3x2x2 = 72

If forget something at combitronix please add!
Whats positive is that I have learnt much
about FreeBSD sosciety, software structure,...

so plans:
rc.conf
ports
nvidia
no linux
xorg.conf (? no drm ?)

is this ok? :



/usr/ports/x11/nvidia-kmod
pkg reinstall

/usr/ports/x11/nvidia-driver
pkg reinstall

/boot/loader.conf = hw.nvidiadrm.modeset=1
/etc/rc.conf: kld_list = "nvidia-modeset nvidia"

It dose not work out!
 
Could it be that graphics card needs older version
even based it type its listed at compatible whit newer!


Combitronix of case:

2x /boot/loader.conf /etc/rc.conf
3x pkg , ports, native from nvidia
3x nvidia-drm, nvidia, nvidia-modeset
2x linux, no linux
2x xorg.conf, no xorg
3x nvidia-320 390 580

2x3x3x2x2x3 = 210

I have to try this idea !!!!
 
/boot/loader.conf = hw.nvidiadrm.modeset=1
Replying only one thing, though, this is for /boot/module/nvidia-drm.ko, which is installed by any single one of graphics/nvidia-drm-*-kmod[-devel] ports.

Even if you don't install any of them manually, would be installed if you install graphics/nvidia-drm-kmod (which is a metaport to choose which variant to be installed depending on base FreeBSD version, and pull in x11/nvidia-driver for Xorg / Wayland side of driver and libraries, too).

And x11/nvidia-driver* pulls in corresponding x11/nvidia-kmod* automatically. So you don't manually install x11/nvidia-kmod*.

Note that you shouldn't mix-up versions between x11/nvidia-driver* and x11/nvidia-kmod* (if you want Linux compatibility libraries, x11/linux-nvidia-libs*, too).
 
So you don't manually install x11/nvidia-kmod*.
3x nvidia-drm, nvidia, nvidia-modeset:

I have understood that if I use nvidia-drm-kmod it will automatically sellect all stuff, unfortunately
automatically select items have not worked together due supply chain failures to have homogenous versions.
And I have understood that I do not this automation, it dose not just work, its basically programming over programming.

I have understood that I can install directly forexample 390 drivers, nvidia-driver-390-,...

And it should be clear that if I wanna have linux, i do have Ubuntu then, its native linux!

I like to have FreeBSD ( hardened?) at this case.
==============================
N O L I N U X
 
3x nvidia-drm, nvidia, nvidia-modeset:
Maybe a good news for you.
nvidia-drm.ko doesn't support -304, -340, -390 and -470 variants of nvidia-modeset.ko, as thesed don't have mandatory codes for nvidia-drm.ko.

And nvidia.ko and nvidia-modeset.ko are built from exactly the same upstream tarball as any of single x11/nvidia-kmod* ports.
So if you don't intentionally mangle these 2 kmods from different versions, you can consider these two as "single bundle".
 
Yes, what I have now learnt, 8 years ago someone corrected code so that
if not booted UEFI screen mode will such it will mixed maxed, at vesa driver !

So to get ctrl+alt+1 work you must set /boot/loder.conf:

kern.vty=sc

Then screen works while you switch between screens !
And at startup screen is ok!

Still I have problems whit xfce,...... um, when i do startx
X starts cursor invisible, other problem is that windows has
no topic line so I can move those, forexample Thunder bird,....

Hardened BSD is FreeBSD whit balls,... this question is purely FreeBSD
problem, https://forums.freebsd.org/threads/how-to-set-up-nvidia-graphics-card-on-freebsd-11-1.63456/page-3

This same problem is nasty when graphics drivers are setup at loder.conf due
then you get MIXMAX SCREEN instead login: prompt. This bug says
stay away FreeBSD.
 
when graphics drivers are setup at loder.conf
It is STRONGLY DISCOURAGED (almost prohibited), especially nvidia drivers and recent drm drivers. This is because these drivers are tooooooooo large to load via /boot/loader.conf. The staging area loader allocates to load kernel and all kernel modules, buffers specified in /boot/loader.conf is limited.

Load GPU-related drivers via kld_list variable in /etc/rc.conf[.local] instead.
This is the NORMAL way for years.
 
  • Like
Reactions: mer
ctrl+alt+1
This shouldn't work. From X11 sessions, ctrl-alt-<f1..8>, not numeric "1".."8".
From vtys, alt-<f1..8>, without ctrl works, but not with ctrl.

kern.vty=sc
Usually, it shouldn't work for UEFI firnwares but legacy BIOSes.

But some irregular UEFI firnware allows it if booted with UEFI mode with CSM activated (usually disallowed configuration, but abnormal firmware could allow it). So do NOT depend on it.
 
And solution to get mouse back, windows topics was:

delete .config !

Still codepage is wrong whit sc,...., have to find out how
to change ascii code page to right one at startuo,..



Yes, legacy boot could workout from package if one bug fixed
8 years ago will be reversed. If i undesrtood corectly that can
not be done due that could insult person who did that deeply!
Hope this is nor true,....,
 
Back
Top