From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HApMe-0000SA-ME for garchives@archives.gentoo.org; Sat, 27 Jan 2007 15:21:13 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0RFIsVG006538; Sat, 27 Jan 2007 15:18:54 GMT Received: from a.mx.pulsewidth.org.uk (a.mx.pulsewidth.org.uk [194.150.121.11]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l0RFIsPi006532 for ; Sat, 27 Jan 2007 15:18:54 GMT X-Virus-Scanned: amavisd-new at pulsewidth.org.uk Received: from actium.local.pulsewidth.org.uk (unknown [87.127.58.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a.mx.pulsewidth.org.uk (Postfix) with ESMTP id CB0DBC123 for ; Sat, 27 Jan 2007 15:18:45 +0000 (GMT) Date: Sat, 27 Jan 2007 15:18:44 +0000 From: Adam James To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] upgraded system, usb_storage won't autoload Message-ID: <20070127151844.3452d48f@actium.local.pulsewidth.org.uk> In-Reply-To: <20070127140441.GA4182@brego.pewamo.office> References: <20070126030238.GA28900@brego.pewamo.office> <20070126150936.GB80050@sgi.com> <20070127140441.GA4182@brego.pewamo.office> X-Mailer: Claws Mail 2.7.1 (GTK+ 2.10.6; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 514123fd-2f8e-4f6d-8e07-2846109279ba X-Archives-Hash: 80f820194d19e7dfa7d5b3ad3859482b On Sat, 27 Jan 2007 09:04:41 -0500 Michael George wrote: > On Fri, Jan 26, 2007 at 07:09:36AM -0800, Bob Sanders wrote: > > Michael George, mused, then expounded: > > > > > > What do I need to do so that usb_storage will autoload as needed? > > > > > > > Add it /etc/modules.autoload.d/kernel-2.6 > > > > Or simply compile into the kernel and be done with the problem. > > Ha, well, the brute force solution *would* work, but I want to know > *why* it didn't work as it should! :) Is your kernel compiled with 'CONFIG_KMOD=y'? -atj -- gentoo-amd64@gentoo.org mailing list