From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Giuliano Pochini <pochini@shiny.it>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: module is not unloaded when probe fails
Date: Tue, 23 Mar 2004 00:11:11 +0100 [thread overview]
Message-ID: <405F728F.3090004@gmx.net> (raw)
In-Reply-To: <20040322220826.1be9799a.pochini@shiny.it>
Giuliano Pochini wrote:
>
> When I try to load a module and it fails (snd-darla20 in this case) the
> module is not unloaded. IIRC it didn't happen some months ago, but I have no
> idea what is the cause because I changed a lot of stuff in the meantime
> (kernel, compiler, modutils...). Is this the expected behaviour ?
Yes, it's by design. If a module sees it can't drive the available
hardware, it *should* stay loaded so you either can
- add new hardware it can drive or
- tell it via /sys/bus/pci/drivers/tulip/new_id that it should drive dome
hardware with previously unknown pci id.
> [Giu@Jay Giu]$ uname -a
> Linux Jay 2.6.3-ben2 #10 SMP Sun Mar 14 21:46:34 CET 2004 ppc unknown
It's a new 2.6 feature.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
prev parent reply other threads:[~2004-03-22 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 21:08 module is not unloaded when probe fails Giuliano Pochini
2004-03-22 23:11 ` Carl-Daniel Hailfinger [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=405F728F.3090004@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pochini@shiny.it \
/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