Discussion:
Nvidia issue with CURRENT
(too old to reply)
Mariusz Zaborski
2018-04-22 10:42:37 UTC
Permalink
Hello,

I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
stop working.
I tried also nvidia-driver-390.25 without luck as well.

I have loaded nvidia-modeset.ko .

While I'm rebooting my machine its also core dumping:
Loading Image... .
I'm attaching also Xorg log.

Is this a known issue?

Thanks,
Mariusz
Tommi Pernila
2018-04-22 12:24:32 UTC
Permalink
Hi,

are you running which version of CURRENT?
E.g. Some snapshot or did you compile from source?

-Tommi
Post by Mariusz Zaborski
Hello,
I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
stop working.
I tried also nvidia-driver-390.25 without luck as well.
I have loaded nvidia-modeset.ko .
https://people.freebsd.org/~oshogbo/nvidia-mail.png .
I'm attaching also Xorg log.
Is this a known issue?
Thanks,
Mariusz
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
Mariusz Zaborski
2018-04-22 12:38:55 UTC
Permalink
Hi,

Normally I build my CURRENT by myself from Xorg - r332861.
But I also tried latest SNAPSHOT.

Thanks,
Mariusz
Post by Tommi Pernila
Hi,
are you running which version of CURRENT?
E.g. Some snapshot or did you compile from source?
-Tommi
Post by Mariusz Zaborski
Hello,
I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
stop working.
I tried also nvidia-driver-390.25 without luck as well.
I have loaded nvidia-modeset.ko .
https://people.freebsd.org/~oshogbo/nvidia-mail.png .
I'm attaching also Xorg log.
Is this a known issue?
Thanks,
Mariusz
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
O. Hartmann
2018-04-23 07:00:33 UTC
Permalink
On Sun, 22 Apr 2018 14:38:55 +0200
Post by Mariusz Zaborski
Hi,
Normally I build my CURRENT by myself from Xorg - r332861.
But I also tried latest SNAPSHOT.
Thanks,
Mariusz
All my boxes running with nVidia hardware running most recent CURRENT (compiled
this morning on an almost daily basis) and I'm using the lates official driver
available from nVidia, 390.48.

It happens to be as a natural byproduct of CURRENT that very often the kernel
module of the nVidia driver is out of sync so i made it a habit to recompile
the module from sources whenever I recompile/install a kernel.

In /etc/src.conf , therefore you should add something similar to (like I added
to mine):

PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod

This is one of the great advantages of having an operating system which you can
compile yourself.

Regards,

oh
Post by Mariusz Zaborski
Post by Tommi Pernila
Hi,
are you running which version of CURRENT?
E.g. Some snapshot or did you compile from source?
-Tommi
Post by Mariusz Zaborski
Hello,
I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
stop working.
I tried also nvidia-driver-390.25 without luck as well.
I have loaded nvidia-modeset.ko .
https://people.freebsd.org/~oshogbo/nvidia-mail.png .
I'm attaching also Xorg log.
Is this a known issue?
Thanks,
Mariusz
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
Greg 'groggy' Lehey
2018-04-23 07:51:01 UTC
Permalink
Post by O. Hartmann
On Sun, 22 Apr 2018 14:38:55 +0200
Post by Mariusz Zaborski
Hi,
Normally I build my CURRENT by myself from Xorg - r332861.
But I also tried latest SNAPSHOT.
All my boxes running with nVidia hardware running most recent CURRENT (compiled
this morning on an almost daily basis) and I'm using the lates official driver
available from nVidia, 390.48.
It happens to be as a natural byproduct of CURRENT that very often
the kernel module of the nVidia driver is out of sync so i made it a
habit to recompile the module from sources whenever I
recompile/install a kernel.
As I commented, I've had this on -STABLE as well.

My guess is that this is GPU dependent. I'm using an old card:

[ 32.251] Current Operating System: FreeBSD teevee.lemis.com 11.1-STABLE FreeBSD 11.1-STABLE #2 r327971: Mon Jan 15 1
0:55:53 AEDT 2018 ***@teevee.lemis.com:/home/obj/eureka/home/src/FreeBSD/svn/stable/11/sys/GENERIC amd64
...
[ 32.763] (II) NVIDIA dlloader X Driver 390.25 Wed Jan 24 19:00:20 PST 2018
...
[ 33.785] (II) NVIDIA(0): NVIDIA GPU GeForce GT 710 (GK208) at PCI:1:0:0 (GPU-0)
[ 33.785] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 33.785] (--) NVIDIA(0): VideoBIOS: 80.28.b8.00.45
[ 33.785] (II) NVIDIA(0): Detected PCI Express Link width: 8X
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to (like I added
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod
This is one of the great advantages of having an operating system which you can
compile yourself.
Yes, but this has nothing to do with the bug. Clearly Marisuz and I
have the configuration correct, but something has changed in the last
few months.

Marisuz, as I commented, your log wasn't appended to the message I
received. What is your hardware?

Greg
--
Sent from my desktop computer.
Finger ***@FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
Mariusz Zaborski
2018-04-23 07:55:40 UTC
Permalink
Post by Greg 'groggy' Lehey
Post by O. Hartmann
On Sun, 22 Apr 2018 14:38:55 +0200
Post by Mariusz Zaborski
Hi,
Normally I build my CURRENT by myself from Xorg - r332861.
But I also tried latest SNAPSHOT.
All my boxes running with nVidia hardware running most recent CURRENT (compiled
this morning on an almost daily basis) and I'm using the lates official driver
available from nVidia, 390.48.
It happens to be as a natural byproduct of CURRENT that very often
the kernel module of the nVidia driver is out of sync so i made it a
habit to recompile the module from sources whenever I
recompile/install a kernel.
As I commented, I've had this on -STABLE as well.
[ 32.251] Current Operating System: FreeBSD teevee.lemis.com 11.1-STABLE FreeBSD 11.1-STABLE #2 r327971: Mon Jan 15 1
...
[ 32.763] (II) NVIDIA dlloader X Driver 390.25 Wed Jan 24 19:00:20 PST 2018
...
[ 33.785] (II) NVIDIA(0): NVIDIA GPU GeForce GT 710 (GK208) at PCI:1:0:0 (GPU-0)
[ 33.785] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 33.785] (--) NVIDIA(0): VideoBIOS: 80.28.b8.00.45
[ 33.785] (II) NVIDIA(0): Detected PCI Express Link width: 8X
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to (like I added
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod
This is one of the great advantages of having an operating system which you can
compile yourself.
Yes, but this has nothing to do with the bug. Clearly Marisuz and I
have the configuration correct, but something has changed in the last
few months.
Yea this is a known issue so I rebuild nvidia-driver.
I'm just not sure if this is a problem with kernel or with the driver itself.
Post by Greg 'groggy' Lehey
Marisuz, as I commented, your log wasn't appended to the message I
received. What is your hardware?
https://people.freebsd.org/~oshogbo/Xorg.0.log

NVIDIA GPU GeForce GTX 1050 Ti

Thanks,
--
Mariusz Zaborski
oshogbo//vx | http://oshogbo.vexillium.org
FreeBSD commiter | https://freebsd.org
Software developer | http://wheelsystems.com
If it's not broken, let's fix it till it is!!1
Greg 'groggy' Lehey
2018-04-23 08:17:42 UTC
Permalink
Post by Mariusz Zaborski
Post by Greg 'groggy' Lehey
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to (like I added
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod
This is one of the great advantages of having an operating system which you can
compile yourself.
Yes, but this has nothing to do with the bug. Clearly Marisuz and I
have the configuration correct, but something has changed in the last
few months.
Yea this is a known issue so I rebuild nvidia-driver.
I'm just not sure if this is a problem with kernel or with the
driver itself.
Almost by definition, it's a driver issue. Something in the kernel
has changed which makes it no longer work.
Post by Mariusz Zaborski
Post by Greg 'groggy' Lehey
Marisuz, as I commented, your log wasn't appended to the message I
received. What is your hardware?
https://people.freebsd.org/~oshogbo/Xorg.0.log
A brief scan doesn't show anything very similar to my issues. I'll
look again tomorrow when I have time.

Did you try the most recent driver?

Greg
--
Sent from my desktop computer.
Finger ***@FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
Mariusz Zaborski
2018-04-23 12:21:27 UTC
Permalink
Post by Greg 'groggy' Lehey
Post by Mariusz Zaborski
Post by Greg 'groggy' Lehey
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to (like I added
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod
This is one of the great advantages of having an operating system which you can
compile yourself.
Yes, but this has nothing to do with the bug. Clearly Marisuz and I
have the configuration correct, but something has changed in the last
few months.
Yea this is a known issue so I rebuild nvidia-driver.
I'm just not sure if this is a problem with kernel or with the driver itself.
Almost by definition, it's a driver issue. Something in the kernel
has changed which makes it no longer work.
Post by Mariusz Zaborski
Post by Greg 'groggy' Lehey
Marisuz, as I commented, your log wasn't appended to the message I
received. What is your hardware?
https://people.freebsd.org/~oshogbo/Xorg.0.log
A brief scan doesn't show anything very similar to my issues. I'll
look again tomorrow when I have time.
Did you try the most recent driver?
If you mean the 390.48, then yes.
I didn't see any newer then that.

Thanks,
--
Mariusz Zaborski
oshogbo//vx | http://oshogbo.vexillium.org
FreeBSD commiter | https://freebsd.org
Software developer | http://wheelsystems.com
If it's not broken, let's fix it till it is!!1
Mateusz Piotrowski
2018-04-23 08:53:26 UTC
Permalink
On Mon, 23 Apr 2018 09:00:33 +0200
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to (like
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod
Shouldn't it go into make.conf(5)? That's what the manual suggests.
Kevin Oberman
2018-04-23 15:19:25 UTC
Permalink
Post by Mateusz Piotrowski
On Mon, 23 Apr 2018 09:00:33 +0200
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to (like
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+= emulators/virtualbox-ose-kmod
Shouldn't it go into make.conf(5)? That's what the manual suggests.
Ans the man page should be fixed. By putting it into make.conf, it pollutes
the environment of ever make(1) run on the system. (Yes, unlikely to ever
cause a problem,)

In src.conf it only impacts the builds of the system and ports. This is why
src.conf was created a few years ago. In fact, it was originally supposed
to only impact the build of the system, but the ports Mk files were
modified to pull it in, to, much to my annoyance. I liked being able to
modify compile options just for the system without them breaking ports
builds.

Simple rule... any definition used by make(1) only for system builds
belongs in /etc/sec.conf.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: ***@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Mateusz Piotrowski
2018-04-23 22:54:07 UTC
Permalink
On Mon, 23 Apr 2018 08:19:25 -0700
Post by Kevin Oberman
Post by Mateusz Piotrowski
On Mon, 23 Apr 2018 09:00:33 +0200
Post by O. Hartmann
In /etc/src.conf , therefore you should add something similar to
PORTS_MODULES=
PORTS_MODULES+= x11/nvidia-driver
PORTS_MODULES+=
emulators/virtualbox-ose-kmod
Shouldn't it go into make.conf(5)? That's what the manual suggests.
Ans the man page should be fixed. By putting it into make.conf, it
pollutes the environment of ever make(1) run on the system. (Yes,
unlikely to ever cause a problem,)
In src.conf it only impacts the builds of the system and ports. This
is why src.conf was created a few years ago. In fact, it was
originally supposed to only impact the build of the system, but the
ports Mk files were modified to pull it in, to, much to my annoyance.
I liked being able to modify compile options just for the system
without them breaking ports builds.
Simple rule... any definition used by make(1) only for system builds
belongs in /etc/sec.conf.
Done, I've added this information to make.conf(5). Now it's waiting for
a review.

https://reviews.freebsd.org/D15177

Thanks!

Mateusz

Greg 'groggy' Lehey
2018-04-23 01:40:30 UTC
Permalink
Post by Mariusz Zaborski
Hello,
I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
stop working.
I tried also nvidia-driver-390.25 without luck as well.
Yes, I've had this trouble as well with -STABLE. It happened some
time in the February/March time frame. See
http://www.lemis.com/grog/diary-mar2018.php#D-20180324-031830. I
haven't reported it yet because I had intended to try the latest
version of the driver. At the time that was 390.42, but now it's
390.48. You might like to try that (see
http://www.nvidia.com/object/unix.html).
Post by Mariusz Zaborski
I'm attaching also Xorg log.
This seems to have got lost.

Greg
--
Sent from my desktop computer.
Finger ***@FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
Kevin Oberman
2018-04-23 03:21:51 UTC
Permalink
Post by Greg 'groggy' Lehey
Post by Mariusz Zaborski
I'm attaching also Xorg log.
This seems to have got lost.
Greg
Please be sure that attachments are typed "text/plain". I believe all other
MIME type are removed for security reasons. I also believe that text/SOME
CHARACTER-SET will also be removed as they can be abused.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: ***@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Continue reading on narkive:
Loading...