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. > [EMAIL PROTECTED] 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 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
