From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 21:42:32 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D8271065673 for ; Thu, 28 Feb 2008 21:42:32 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 017EC8FC20 for ; Thu, 28 Feb 2008 21:42:31 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 25253 invoked from network); 28 Feb 2008 21:42:31 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 28 Feb 2008 21:42:31 -0000 Message-ID: <47C7294E.9000804@chuckr.org> Date: Thu, 28 Feb 2008 16:36:14 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: FreeBSD-Hackers X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: problem with ldconfig X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 21:42:32 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I had a problem with my raid array, and during a fix, I noticed that a thing I'd gotten very used to during my time running Linux was a really bad thing for FreeBSD (the usage of a /boot partition for booting only, to store the kernel, but nothing else). Well, after I had reloaded my raid, and fixed the /boot to be one nice big parition, I have a several very weird things that have cropped up. First one, I'd kept a 100G IDE disk hanging around just in case I hadn't installed the raid right, so I could use it for backup, and this saved me, but now, it no longer boots right. I used to either hit F1 (to boot the 100G IDE, called ad1, ad0 being a cdrom), or I would hit F5 then F1, to boot from the raid, called da0. Well, now, no matter what Function key I hit, it boots from ad1 regardless, and the only way I can boot the raid is the use the #6 option of the beastie menu (to catch the ld cli) and set currdev to disk2s1a, unload, load, then boot. This works fine, but howcome I can't just get it to boot without all this intervention? I have already tried reloading the boot manager into both ad1s1 and da0s1, no change. Well, the other thing that's come up, I can't get my nvidia driver to work along with xorg. It used to show it's arrival both in kldstat, AND also because, in /dev, a file named nvidiactl would show up. This has stopped happening. I had been using the old version 100.14.19, and when I checked the nvidia website, it seems a couple of newer versions had appeared, so I downloaded and built version 169.12. Don't ask me why the crazy version numbering, I looked around for something like a changelog, but had no luck. Anyhow, updating to the newer version wasn't too hard, but didn't show any change. Consulting the /var/log/Xorg.0.log file, even though kldstat says that nvidia.ko is loaded, it never shows a /dev/nvidiactl, and the log file says clearly that it never finds the Nvidia kernel module. Using it with Vesa lets me limp, so I do that, but howcome? OK, I'm not giving my ldconfig problem to you folks, its quite likely its a FreeBSD-current problem, so let those folks handle that one. Boy, I feel like the little boy who cried wolf! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHxylOz62J6PPcoOkRAudcAJ9ex65oZUoh+0gf/7WcpNi6KhwsxwCgje63 m4GwVJZrkoU3McfHK1NAArk= =wLpy -----END PGP SIGNATURE-----