Date: Sat, 27 Aug 2011 17:08:43 +0400 From: Test Rat <ttsestt@gmail.com> To: Chris Rees <utisoft@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: Problem with nvidia-driver and "X" after upgrade Message-ID: <867h5zm278.fsf@gmail.com> References: <BLU0-SMTP4202D6EAD2AD6157E83689D93130@phx.gbl> <20110826172328.67f707d7@cox.net> <BLU0-SMTP272523F17C12EEF65F60A1693130@phx.gbl> <1314402348.13483.6.camel@xenon> <BLU0-SMTP421FE1CB8F2D735D97D6E8393120@phx.gbl> <867h5zt6gd.fsf@gmail.com> <CADLo83-NdNMaCAncRY6W_f8u_KQ36YJxSF86yiNH_5EmHi5dsA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Rees <utisoft@gmail.com> writes: >> >> Carmel <carmel_ny@hotmail.com> writes: >> >> > So, after rebuild World/Kernel and installing same and then >> >> > rebuilding the nvidia-driver, all is well again. >> >> > >> >> > Now, in my not so humble opinion, there should be some sort of >> >> > warning in the driver dialog, or at least in the port description >> >> > that warns of this behavior. It could have save3d me several hours >> >> > of needless searching. Hours that I will never get back. :) [...] > Really, the proper fix would be to make kldload give a more descriptive > error, but IIRC this is much easier said than done... There are a few ports that use SRC_BASE and are *not* kernel modules, e.g. devel/linux_kdump devel/linuxthreads sysutils/lsof > I don't think doing more clever stuff in the port is the solution; It's not > specific to that port. What about bsd.port.mk bailing out early if kernel sources are for different version? It was in the patch you quoted but probably have not read.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867h5zm278.fsf>