Date: Sat, 27 Aug 2011 06:52:44 -0400 From: Carmel <carmel_ny@hotmail.com> To: freebsd-ports@freebsd.org Subject: Re: Problem with nvidia-driver and "X" after upgrade Message-ID: <BLU0-SMTP421FE1CB8F2D735D97D6E8393120@phx.gbl> In-Reply-To: <1314402348.13483.6.camel@xenon> References: <BLU0-SMTP4202D6EAD2AD6157E83689D93130@phx.gbl> <20110826172328.67f707d7@cox.net> <BLU0-SMTP272523F17C12EEF65F60A1693130@phx.gbl> <1314402348.13483.6.camel@xenon>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/TO7a/6hdwd.C48XWQ6zrxfv Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 27 Aug 2011 01:45:48 +0200 Michal Varga articulated: > On Fri, 2011-08-26 at 18:51 -0400, Carmel wrote: >=20 > > I found the problem. I had downloaded the source files for BSD a few > > days ago; however, I never rebuild the kernel or world. When the > > nvidia driver got rebuild it was evidently using those new files. I > > got the answer while Googling. When trying to manually load the > > driver, I received this error message: > >=20 > > kldload: can't load nvidia: Exec format error > >=20 > > Evidently, this is a known phenomena with the nvidia-driver. >=20 > This is a known phenomena with everything when having your OS sources > and your live OS out of sync. Define "everything" Obviously, not everything suffers from this problem. In fact, lacking proof otherwise, I would tend to believe that this is a niche problem. > > So, after rebuild World/Kernel and installing same and then > > rebuilding the nvidia-driver, all is well again. > >=20 > > 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. :) > >=20 >=20 > Nvdia-driver is a driver, a kernel module so to say. You built the > driver against kernel sources that are different from your live > kernel. You got a driver that will work with kernel corresponding to > those sources. What kind of "warning" would you be expecting there > and what purpose would it serve? This is the first time I have seen this phenomena occur. A warning when the drive starts, or should I say tries to start, that there is a mismatch would have been nice. I was not aware that the driver had been rebuild and therefore wasted valuable time tracking down the problem. Even the warning that I received when manually attempting to load the driver was not displayed when booting up, unless it flew past the screen faster than I could view it, nor was it listed in the system log. The Xorg log simply stated it couldn't load the module, which is in itself a start. I am assuming that if the module cannot give a proper reason for its failure to load then the Xorg log really has nothing to log. That is just an unproven assumption though. --=20 Carmel =E2=9C=8C carmel_ny@hotmail.com --Sig_/TO7a/6hdwd.C48XWQ6zrxfv Content-Type: application/pgp-signature; name="signature.asc" Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBAgAGBQJOWMyGAAoJEE2VKrk/3DQmJGwH/RjbhOEKoT7KzgPtseoQJl4A ZLCArmRnZHhSxhZ26MljopJ3Zj7G+53F9r5SnbLNuNIUYY7zff2cnQWC4PDFxtl5 2lM2ZRpdP+SPEDhxvh0dp+GR9x8JQrzG9ijD8ejZPRWv4wPUDRXV3+Rs/3Ledjbf s7gihl12WpnSfyyNx1eAiwd1uCLd53UxlsPMU945AYsj5hxWPlq2giH4xDBf2iIe H3L+q8ZA1BvvJaDPP+p5j7NCIgvIJyCGCHiN5HFrloAnrxPcbpuT2Hv3wnUeZ9ku rC5SC1oscB9XYBjw1csSJ5F+7Zccjl5eCN5b6J5XCAqAzOZFt2zbZWIcJ/sjONs= =YW/F -----END PGP SIGNATURE----- --Sig_/TO7a/6hdwd.C48XWQ6zrxfv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU0-SMTP421FE1CB8F2D735D97D6E8393120>