MacBook Pro 11,3 Nvidia Drivers

[Hartmann, O.]

On Tue, 06 Sep 2016 06:39:03 +0000
blubee blubeeme <gurenchan at gmail.com> wrote:

> I just did a full portmaster -Da and updated all my packages. Which
> are listed here: http://paste2.org/EcM8s3gH
> 
> When I add nvidia_load to boot/loader.conf and I log in, nvidia
> drivers are loaded but running startx gives me garbled screen.
> 
> If I try to add nvidia-modest_load to my boot/loader.conf then no
> nvidia drivers are loaded.

Shouldn't it be nvidia-modeset_load="YES"? Check for a typo, please.

> 
> Trying sudo kldload nvidia-modest returns kldload can't load
> nvidia-modest no such for our directory.
> Here is the xorg log: http://paste2.org/37fpmnYL

See above, this could probably be due to the type, it is
nvidia-modeset.ko, not nvidia-modest.ko (the name of the kernel object
module).

> 
> I have the nvidia Gt 750m Mac edition and I have the nvidia driver
> 367.44 which I think is the latest one.
> 
> Is there anything else that I could try to do to fix this?

Well, I'd prefere to wait for your next response due to the possible
typo. If it is a typo, no further help is needed :-) 


> 
> On Tue, Sep 6, 2016, 13:09 Hartmann, O.
> <ohartman at mail.zedat.fu-berlin.de> wrote:
> 
> > On Mon, 5 Sep 2016 20:53:34 -0700
> > Conrad Meyer <cem at freebsd.org> wrote:
> >  
> > > Hi,
> > >
> > > Have you tried changing 'nvidia_load="YES"' to
> > > 'nvidia-modeset_load="YES"'?  It's documented in UPDATING and
> > > pkg-message, but I understand this is a surprising change.  At
> > > least one other user has reported a garbled screen on 367.44, but
> > > I don't know what hardware they had.
> > >
> > > Best,
> > > Conrad
> > >
> > > On Mon, Sep 5, 2016 at 8:39 PM, blubee blubeeme
> > > <gurenchan at gmail.com> wrote:  
> > > > I seem to be having issues recently when I build nvidia-driver
> > > > from ports.
> > > >
> > > > Installing 346.44 from pkg works fine but If I go and install
> > > > 367.44 from ports then my screen gets garbled and the nvidia
> > > > driver doesn't seem to get loaded, even though
> > > > nvidia_load="YES" is still in /boot/loader.con but if I revert
> > > > back to 346.44 then things work again.
> > > >
> > > > Is this a known issue? How can I fix/ avoid this?
> > > >
> > > > _______________________________________________
> > > > freebsd-x11 at freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> > > > To unsubscribe, send any mail to
> > > > "freebsd-x11-unsubscribe at freebsd.org"  
> > > _______________________________________________
> > > freebsd-x11 at freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> > > To unsubscribe, send any mail to
> > > "freebsd-x11-unsubscribe at freebsd.org"  
> >
> > Prior to 367.35, I also ran into an garbled screen issue once with
> > the new modeset driver. This happened on all nVidia Quadro based
> > cards we have around here, at least that built into my workstation,
> > a Quadro NV315, one of the low-end Quadros nVidia offers. But that
> > has gone with the most recent series of divers.
> >
> > The garbled console is still with consumer GPUs (GTX 960, GTX 560Ti)
> > when using UEFI with required vt() console driver. The above
> > mentioned Quadro boards have a black console - no garbled, no
> > distorted screen so far but black. This goes away immediately after
> > unloading the nvidia_modeset.ko kernel module.
> >
> > Kind regards,
> >
> > Oliver
> >