Re: Nvidia issue with CURRENT

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Tommi Pernila-2
Hi,

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

-Tommi

On Sun, 22 Apr 2018 at 13.47, Mariusz Zaborski <[hidden email]> wrote:

> 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:
> https://people.freebsd.org/~oshogbo/nvidia-mail.png .
> I'm attaching also Xorg log.
>
> Is this a known issue?
>
> Thanks,
> Mariusz
> _______________________________________________
> [hidden email] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"
>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-desktop
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Mariusz Zaborski
Hi,

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

Thanks,
Mariusz

On 22 April 2018 at 14:24, Tommi Pernila <[hidden email]> wrote:

> Hi,
>
> are you running which version of CURRENT?
> E.g. Some snapshot or did you compile from source?
>
> -Tommi
>
> On Sun, 22 Apr 2018 at 13.47, Mariusz Zaborski <[hidden email]> wrote:
>>
>> 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:
>> https://people.freebsd.org/~oshogbo/nvidia-mail.png .
>> I'm attaching also Xorg log.
>>
>> Is this a known issue?
>>
>> Thanks,
>> Mariusz
>> _______________________________________________
>> [hidden email] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-desktop
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Greg 'groggy' Lehey-3
In reply to this post by Tommi Pernila-2
On Sunday, 22 April 2018 at 12:42:37 +0200, Mariusz Zaborski wrote:
> 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).

> I'm attaching also Xorg log.

This seems to have got lost.

Greg
--
Sent from my desktop computer.
Finger [hidden email] 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

signature.asc (169 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

O. Hartmann-5
In reply to this post by Mariusz Zaborski
On Sun, 22 Apr 2018 14:38:55 +0200
Mariusz Zaborski <[hidden email]> wrote:

> 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

 

>
> On 22 April 2018 at 14:24, Tommi Pernila <[hidden email]> wrote:
> > Hi,
> >
> > are you running which version of CURRENT?
> > E.g. Some snapshot or did you compile from source?
> >
> > -Tommi
> >
> > On Sun, 22 Apr 2018 at 13.47, Mariusz Zaborski <[hidden email]>
> > wrote:  
> >>
> >> 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:
> >> https://people.freebsd.org/~oshogbo/nvidia-mail.png .
> >> I'm attaching also Xorg log.
> >>
> >> Is this a known issue?
> >>
> >> Thanks,
> >> Mariusz
> >> _______________________________________________
> >> [hidden email] mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to
> >> "[hidden email]"  
> _______________________________________________
> [hidden email] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-desktop
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Greg 'groggy' Lehey-3
On Monday, 23 April 2018 at  9:00:33 +0200, O. Hartmann wrote:

> On Sun, 22 Apr 2018 14:38:55 +0200
> Mariusz Zaborski <[hidden email]> wrote:
>
>> 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     [hidden email]:/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

> 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.

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 [hidden email] 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

signature.asc (169 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Mariusz Zaborski
On Mon, Apr 23, 2018 at 05:51:01PM +1000, Greg 'groggy' Lehey wrote:

> On Monday, 23 April 2018 at  9:00:33 +0200, O. Hartmann wrote:
> > On Sun, 22 Apr 2018 14:38:55 +0200
> > Mariusz Zaborski <[hidden email]> wrote:
> >
> >> 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     [hidden email]:/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
>
> > 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.
>
> 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.

> 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

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Greg 'groggy' Lehey-3
On Monday, 23 April 2018 at  9:55:40 +0200, Mariusz Zaborski wrote:

> On Mon, Apr 23, 2018 at 05:51:01PM +1000, Greg 'groggy' Lehey wrote:
>> On Monday, 23 April 2018 at  9:00:33 +0200, O. Hartmann wrote:
>>> On Sun, 22 Apr 2018 14:38:55 +0200  Mariusz Zaborski <[hidden email]> wrote:
>>> 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.
>>
>> 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.

>> 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 [hidden email] 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

signature.asc (169 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Mateusz Piotrowski
In reply to this post by O. Hartmann-5
On Mon, 23 Apr 2018 09:00:33 +0200
"O. Hartmann" <[hidden email]> wrote:

>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

Shouldn't it go into make.conf(5)? That's what the manual suggests.

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-desktop
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Mariusz Zaborski
In reply to this post by Greg 'groggy' Lehey-3
On Mon, Apr 23, 2018 at 06:17:42PM +1000, Greg 'groggy' Lehey wrote:

> On Monday, 23 April 2018 at  9:55:40 +0200, Mariusz Zaborski wrote:
> > On Mon, Apr 23, 2018 at 05:51:01PM +1000, Greg 'groggy' Lehey wrote:
> >> On Monday, 23 April 2018 at  9:00:33 +0200, O. Hartmann wrote:
> >>> On Sun, 22 Apr 2018 14:38:55 +0200  Mariusz Zaborski <[hidden email]> wrote:
> >>> 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.
> >>
> >> 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.
>
> >> 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
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-desktop
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Nvidia issue with CURRENT

Mateusz Piotrowski
In reply to this post by Mateusz Piotrowski
On Mon, 23 Apr 2018 08:19:25 -0700
Kevin Oberman <[hidden email]> wrote:

>On Mon, Apr 23, 2018 at 1:53 AM, Mateusz Piotrowski <[hidden email]>
>wrote:
>
>> On Mon, 23 Apr 2018 09:00:33 +0200
>> "O. Hartmann" <[hidden email]> wrote:
>>  
>> >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  
>>
>> 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
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-desktop
To unsubscribe, send any mail to "[hidden email]"