From: Takashi Iwai <tiwai@suse.de>
To: Nikola Knezevic <nikkne@gmx.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re[2]: PROBLEM: ALSA requests module to early, before / is mounted
Date: Tue, 30 Sep 2003 13:03:46 +0200 [thread overview]
Message-ID: <s5hbrt2bkrx.wl@alsa2.suse.de> (raw)
In-Reply-To: <6510599647.20030929171409@gmx.ch>
At Mon, 29 Sep 2003 17:14:09 +0200,
Nikola Knezevic wrote:
>
> Hello Takashi,
> Monday, September 29, 2003, 12:50:00 PM, you wrote:
> >> >> Hi, I'm really annoyed to see 'No soundcards found.' in logs:)
> >> TI> you didn't build in emu10k1 driver. so, at that stage, there is
> >> TI> really no available card :)
> >>
> >> But I build one. modprobe snd-emu10k1 loads it.
>
> TI> did you put this module into initrd?
> TI> otherwise there is NO way to load the MODULE at that time (before
> TI> mounting the root).
>
> No I haven't. How can I do that?
RTFM :)
you can find it in Documentation directory.
if you're using mkinitrd, it's even easier.
> >> TI> yep, this should be avoided before root is mounted.
> >> But for the time being, it isn't...
> TI> right. but it's harmless anyway. just annoying.
>
> Yes, really annoying.
i thought you're annoyed by the message "no soundcards found".
it cannot be solved until you build the emu10k1 into kernel.
> >> >> There is no call for modprobe snd-emu10k1 in
> >> >> rc.modules, so after booting I have to call it manually. Yes, I could
> >> >> put that call in rc.modules, but isn't it supposed to be called by ALSA?
> >> TI> yes, but only if you set up /etc/modprobe.conf correctly to load the
> >> TI> modules automatically.
> >> TI> at least, you have to specify which card is the first one
> >> TI> (snd-card-0).
> >> Did that long time ago, problem remains. Also, I'm using devfs.
> TI> perhaps that's the problem.
>
> I can't see why it should be. If I type:
> modprobe snd-card-0
> it works OK.
> There are some issues about devfs using old modprobe format, and new
> kernel requires module-init-tools 0.9.xx, which have a lighter
> modprobe.conf. As it seems to me, problem is about calling modules
> before / is mounted.
no.
> And I haven't put it in initrd, so it can't be
> loaded. I suppose that call couldn't be done sometime later?
of course, the module could be requested later.
the ALSA core routine calls request_module("snd-card-0"), if the
entry is not present.
basically, you can safely ignore the message "no soundcards found"
at the boot time, because it shows only the built-in drivers.
the modules can be loaded dynamically if you set up the configuration
correctly.
i've never used devfs by myself, so i cannot tell exactly whether it's
a devfs problem. but the fact that you can load snd-card-0 module
manually implies that the problem lies on auto-loading mechanism.
--
Takashi Iwai <tiwai dot suse.de> ALSA Developer - www.alsa-project.org
prev parent reply other threads:[~2003-09-30 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 13:16 PROBLEM: ALSA requests module to early, before / is mounted Nikola Knezevic
2003-09-26 13:37 ` Takashi Iwai
2003-09-26 20:04 ` Nikola Knezevic
2003-09-29 15:32 ` Takashi Iwai
2003-09-30 19:53 ` Nikola Knezevic
[not found] ` <1723482591.20030926200802@gmx.ch>
[not found] ` <s5hzngn6f8n.wl@alsa2.suse.de>
[not found] ` <6510599647.20030929171409@gmx.ch>
2003-09-30 11:03 ` Takashi Iwai [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=s5hbrt2bkrx.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nikkne@gmx.ch \
/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