From: Sascha Retzki <lantis@iqranet.info>
To: linux-admin@vger.kernel.org
Subject: Re: Re[10]: Linux Help
Date: Tue, 20 Jul 2004 18:42:44 +0200 [thread overview]
Message-ID: <1090341764.2470.16.camel@linux.local> (raw)
In-Reply-To: <20040720222617.16C3.SAVAGE-GARDEN@hanikamail.com>
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 ;) ... .
>
> -------
> Web Hosting at cheep price, stating at $1 per moth with your own domain, .COM, .NET, .LK, .ORG etc..
> PHP, CGI, Perl, MySQL, Cpanel 9, POP3, POP3s, SMTP, IMAP, FTP,
> http://www.orbitsl.net
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2004-07-20 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040720214345.16B6.SAVAGE-GARDEN@hanikamail.com>
[not found] ` <1090339517.2470.11.camel@linux.local>
2004-07-20 16:27 ` Re[10]: Linux Help Kev
2004-07-20 16:42 ` Sascha Retzki [this message]
2004-07-20 16:46 ` Re[12]: " Kev
2004-07-20 17:05 ` Sascha Retzki
2004-07-20 17:07 ` Sascha Retzki
2004-07-20 17:55 ` Re[14]: " Kev
2004-07-21 1:23 ` chuck gelm
2004-07-20 16:57 ` Re[12]: " Kev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1090341764.2470.16.camel@linux.local \
--to=lantis@iqranet.info \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).