From mboxrd@z Thu Jan 1 00:00:00 1970 From: chuck gelm Subject: Re: Linux Help Date: Tue, 20 Jul 2004 21:23:40 -0400 Sender: linux-admin-owner@vger.kernel.org Message-ID: <40FDC59C.6070908@gelm.net> References: <20040720222617.16C3.SAVAGE-GARDEN@hanikamail.com> <1090341764.2470.16.camel@linux.local> <20040720224526.16CE.SAVAGE-GARDEN@hanikamail.com> Reply-To: chuck@gelm.net Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040720224526.16CE.SAVAGE-GARDEN@hanikamail.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Kev Cc: linux-admin@vger.kernel.org Uh, I like bottom posting and removing unnecessary lines. Kev wrote: > I have installed Debina with out my LAN cards (Realtec) i did add the > cards after the Denian installation, now i cant seem to get Debian to > detect them :( What did you do and how did it fail? Rheorical: How does hardware detection fall into administration? I would have posted this topic on linux-newbie. > On Tue, 20 Jul 2004 18:42:44 +0200 > Sascha Retzki wrote: >>--> Am Di, 2004-07-20 um 18.27 schrieb Kev: >>--> > how can you make Debian Detect hardware after the installation ? >>--> >>--> This question is ( among many other debian-specific questions ) covered >>--> by their documentations, but ok :) >>--> "detect" hardware .. hm .. first of, /etc/modules is a >>--> one-modulename-per-line file is loaded at boottime, so this is the place >>--> where you put the module-names in ( without the path or the .o ). The >>--> detection is imho manually done with debian. Tip is to use modprobe >>--> instead of isnmod to load dependencies of modules, use lspci -v to find >>--> out all pci/Isa/... adapters and chipnames in your computer ... . Linux >>--> module-names are named after chipsetname, not that what the vendor tries >>--> to tell you on the cage ;) ... . modprobe 8139too HTH, Chuck