From owner-freebsd-questions@FreeBSD.ORG Sat Jan 17 15:55:54 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 873B26EE for ; Sat, 17 Jan 2015 15:55:54 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AB568BC for ; Sat, 17 Jan 2015 15:55:54 +0000 (UTC) Received: from moby.local ([91.89.177.101]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LnxxQ-1XWbKA44i0-00g3Ad; Sat, 17 Jan 2015 16:55:43 +0100 Message-ID: <54BA85F7.6000700@gmx.com> Date: Sat, 17 Jan 2015 16:55:35 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Doug Hardie , "freebsd-questions@freebsd.org Questions" Subject: Re: Switching from custom kernel back to generic References: <4DE6D94C-177B-471B-B537-F7853B83115A@lafn.org> In-Reply-To: <4DE6D94C-177B-471B-B537-F7853B83115A@lafn.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:rBInVcc4hbzzilHofXRld4189RR9hLqbZdd6SHYMmG0KoN8ZShA pd5tSPx18tqJeyeVWljCoS3q14AKE/vKY7caMUeiE6SgYfO6gZKTzaKFk1Pi+EqKgvjmGZr 3tHFCNsBDUB86I+uSqHG5RW6eJ2hez31YaLmWPvYqYydSpCCiec3TnHPgUO9VefyXsMlf2t lO8J95D8kx3DYSaDP5hYA== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 15:55:54 -0000 On 01/15/15 10:10, Doug Hardie wrote: > Is there some magic that is needed to switch from a custom kernel to generic? Why would the kernel not find the modules when ls can? Did you reboot the system? Is the running kernel in-sync with the modules in your /boot/kernel/ directory? If the running kernel is not in-sync with the modules, modules cannot be loaded.