What you see is what I expect. If you check the properties of /lib/modules/2.6.33.2/modules.alias, you should see that the "modified" date is the time you ran depmod. Depmod simply examines all of the modules in /lib/modules/2.6.33.2 and lists the alias lines for each, in modules.alias, to establish the appropriate module for each device hardware ID. So, that needs to be run any time the mix of modules is changed. That would be the case if you use a regular-lupu pupsave with lupuplus*. Now, try your test on the "depmodded" pupsave setup.(On my desktop) I've just typed "depmod" in a ROX terminal, and absolutely nothing happens.
Quote:
sh-4.1# depmod
sh-4.1#
About those warnings: I infer from them that either the module 8192cu contains the duplicate entries or that there are multiple copies of it in different places within the /lib/modules/2.6.33.2 directory.
If the depmod does not solve the problem, please look at /initrd/pup_rw/lib/modules/2.6.33.2 for any "8192" modules that might interfere with the lupuplus modules. If you find any, please delete them or move them outside of /lib/modules/2.6.33.2/.
Beyond those thoughts, I think I am out of ideas. I am not going to try to keep up with the drive-swapping activities.
Richard