devfs
[Top] [All Lists]

Re: module autoloading problem with 177 / 178

To: ude@xxxxxxxxxxxx
Subject: Re: module autoloading problem with 177 / 178
From: Richard Gooch <rgooch@xxxxxxxxxxxxx>
Date: Sat, 2 Jun 2001 10:23:31 -0600
Cc: devfs@xxxxxxxxxxx
In-reply-to: <20010602064928.EF66296D3C@xxxxxxxxxxxxx>
References: <20010602064928.EF66296D3C@xxxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
Sebastian Ude writes:
> 
> 
> 
> Sebastian Ude wrote:
> 
> >I applied the devfs 178 patch (which was released today), and now
> >module autoloading does not work for me at all (it worked before with
> >the vanilla 2.4.5 Kernel / devfs 176).
> 
> >I also tried the 177 patch, and I got the same behaviour.
> 
> [...]
> 
> >Of course everything works when I insert the sr_mod kernel module
> >manually:
> 
> [...]
> 
> >As i said it worked with the same setup and devfs 176.
> >And the problem is not limited to the sr driver !
> >As I said above, module autoloading does not work at all ... For
> >example, I have the same problem with my ALSA sound modules since
> >the upgrade.
> 
> I found a solution for the problem.
> 
> I had to change my aliases in the modules.conf, for example "/dev/snd" to
> "/dev//snd" and it worked again.
> Yep, this is no typo, I had to use two // instead of one.
> 
> Strange thing ... can somebody please explain this to me ?
> Why does it only work with "alias /dev//[devname]" but not with "alias
> /dev/[devname" with 177 / 178 ???

Yeah, I know. It's a bug in the devfs code that I introduced. I'll be
putting out a new patch to fix this. Probably not until after the
weekend, when we get power back in our building at work.

                                Regards,

                                        Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current:   rgooch@xxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>