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.
First of all some information about my current setup:
Kernel configuration:
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT is not set
CONFIG_DEVFS_DEBUG=y
Boot options:
devfs=mount,dmod,dreg,dunreg,dimknod,dilookup
devfsd version:
1.3.11
devfs configuration:
I used the devfsd.conf that came with devfsd 1.3.11.
I only added these two lines in order to change the rights of the audio
devices after the ALSA modules have been loaded:
REGISTER sound/.* PERMISSIONS root.audio 660
REGISTER snd/.* PERMISSIONS root.audio 660
I did not change anything else. The line
LOOKUP .* MODLOAD
is present !
devfsd is started with "/dev" as the only option.
So let's see what happens if I try to access my first SCSI CD-ROM device
(/dev/sr0).
With plain kernel 2.4.5 / devfs 176, the sr_mod module was loaded
automatically, and the devices were created. No problem at all.
With version 177 / 178, it seems like nothing happens. The sr_mod module is
not loaded automatically, and the applications complain about the missing
/dev/sr0 device file.
Here are the syslog messages I get with the debugging options mentioned
above:
devfs: lookup(sr0): dentry: c1761440 by: "mount"
devfs: lookup(sr0): dentry: c1761440 by: "mount"
If i start devfsd with "-d -t 0", it tells me the following:
Entry: "/sr0"(len=4) lookup mode: 0 uid: 0 gid: 100
Entry: "/sr0"(len=4) lookup mode: 0 uid: 0 gid: 100
Of course everything works when I insert the sr_mod kernel module manually:
syslog:
devfs: devfs_mk_dir(cdroms): de: c1dac860 new
devfs: devfs_register(cd): de: c1dacd60 new
devfs: devfs_do_symlink(cdrom0)
devfs: lookup(sr0): dentry: c0397860 by: "devfsd"
devfs: devfs_do_symlink(sr0)
devfs: lookup(sr): dentry: c03978e0 by: "devfsd
devfs: lookup(sr): dentry: c03978e0 by: "devfsd"
devfs: lookup(c0b0t5u0): dentry: c0397960 by: "devfsd"
devfs: devfs_do_symlink(c0b0t5u0)
devfsd:
Entry: "scsi/host0/bus0/target5/lun0/cd"(len=31) registered mode:
60666 uid: 0 gid: 0
Entry: "cdroms/cdrom0"(len=13) registered mode: 120555 uid: 0 gid: 0
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.
Any ideas ?
PS:
I am not subscribed to the list, but there is no need to answer me
directly.
Just post to the list ... I will check out the archives regulary.
|