From: "张 勇顺" <biosedit2000@yahoo.com.cn>
To: gentoo-user@lists.gentoo.org
Subject: 回复: [gentoo-user] Re: 回复: Re: [gentoo-user] install gentoo 2005.0
Date: Fri, 7 Oct 2005 20:14:23 +0800 (CST) [thread overview]
Message-ID: <20051007121423.29792.qmail@web15010.mail.cnb.yahoo.com> (raw)
In-Reply-To: <4346528F.4000403@planet.nl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312, Size: 4868 bytes --]
i
--- Holly Bostick <motub@planet.nl>дµÀ:
> å¼ å顺 schreef:
> > --- Heinz Sporn <heinz.sporn@sporn-it.com>åé:
> >
> >> Am Freitag, den 07.10.2005, 14:05 +0800 schrieb
> å¯\x7f éå¬ã\x7f:
> >>
> >>> hi yestoday to today i am spend two days to
> install
> >>> gentoo 2005.0 and see the hand man but when i am
> install it i am
> >>> see what modules were load with lsmod but i
> can't see anyting is
> >>> modules and i ues modprobe lsmod can't see
> somemodules i don't
> >>> know how to do that
> >>
> >> lsmod will not show modules that have been
> compiled into the
> >> kernel. Is it that you are looking for?
> >>
> >>> if i must rc-update add ....?or other i am uses
> logitech USB
> >>> mouse and uses well in debian starge but
> >>> can't driverd in gentoo i am try to uses the
> same driver with
> >>> starge and ues "auto" but can't driverd
> >>> mouse ether i am emerge fvwm and x.org
> >>
> >> I am not quite sure what exactly your problem is
> - so sorry for
> >> guessing:
> >>
> >> For any USB input device you'll just need kernel
> support. Look into
> >> /Drivers/USB Support. You'll propably want
> support for EHCI, OHCI
> >> and UHCI.
> >> <snip>
> >
> > now i am went to gentoo and modprobe ehci-hcd nwo
> can uses mouse and
> > install discover rc-update add modules default
> but always can't load
> > any modules when system starting and lsmod can't
> see any modules
>
> How did you compile your kernel? It would seem that
> your problem is
> related to the fact that some of your needed drivers
> are compiled as
> modules and some are not.
>
> As Heinz said, 'drivers' compiled statically into
> the kernel will *not*
> be visible via lsmod (only 'drivers' compiled as
> loadable modules are
> visible).
>
> I have many questions about your setup:
>
> 1) why do you have rc-update modules default (rather
> than rc-update
> modules boot)? I would suspect that the default
> runlevel may be too late
> in the boot process for the modules you're trying to
> load,.
>
> 2) 'always can't load any modules when system
> starting'-- how precisely
> are you trying to load said modules? Are they in
> fact modules (or
> statically compiled)? What do you have in
> /etc/modules.autoload.d/kernel-2.6 (I assume you're
> using a 2.6-series
> kernel)? At least ehci-hcd should be listed there in
> order to load it
> during boot (or you could just statically compile it
> into the kernel, to
> avoid this).
>
> 3) just because modules are not listed in lsmod,
> does not mean they are
> not loaded and working. As said previously, modules
> that are statically
> compiled into the kernel do not appear in lsmod, but
> if the hardware
> requiring said modules is detected during the
> hardware detection phase
> of the boot process, the module will be loaded to
> support it. My USB
> mouse works fine this way (ehci-hcd is compiled into
> the kernel, when
> the usb mouse is detected, the kernel module is
> loaded), although I
> cannot see the module in lsmod (because the module
> is not loadable).
> Other than the mouse, which we've solved (add
> ehci-hcd to
> /etc/modules.autoload.d/kernel-2.6), what other
> kernel modules are not
> working as you expect (*not* whether you see them in
> lsmod or not, what
> actually *does not work*)?
>
> Once you have determined what modules are not
> loading, you can then
> check your kernel config to see whether they are
> loadable modules or
> statically compiled, and if loadable, add them to
> /etc/modules.autoload.d/kernel-2.6, which should
> load them automatically
> for you at boot. If statically compiled, but not
> loading at boot, there
> are two possibilities I can think of:
>
> 1) wrong module for the hardware;
>
> 2) you do not have 'Automatic kernel module loading'
> set in your kernel
> (Loadable Module Support => Automatic kernel module
> loading= Y)
>
> HTH,
> Holly
> --
> gentoo-user@gentoo.org mailing list
>
>
I am compile kernel three times and uses "make
defconfig make menuconfig make make modules_install"
that i did't reduce any "M" OR "Y" but i
am add some thing
"requiring said modules is detected during the
hardware detection phase"
you said that but i uses usb mouse the modules is not
load ?
if i am uses "modprobe " the mouse is work well i
think anyone harve compile driver in kernel
some of them must is modules
one time i think to know if i compile all of them in
kernel , what is the condition ?
i am try to compile all the driver in kernel that is
very bad
___________________________________________________________
ÑÅ»¢Ãâ·ÑGÓÊÏä£ÖйúµÚÒ»¾øÎÞÀ¬»øÓʼþɧÈų¬´óÓÊÏä
http://cn.mail.yahoo.com
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-10-07 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 6:05 [gentoo-user] install gentoo 2005.0 张 勇顺
2005-10-07 7:03 ` Heinz Sporn
2005-10-07 9:25 ` 回复: " 张 勇顺
2005-10-07 10:48 ` [gentoo-user] " Holly Bostick
2005-10-07 12:14 ` 张 勇顺 [this message]
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=20051007121423.29792.qmail@web15010.mail.cnb.yahoo.com \
--to=biosedit2000@yahoo.com.cn \
--cc=gentoo-user@lists.gentoo.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