Chmouel, your comments? [...] > > Would you mind showing /etc/modprobe.conf? > > > See the attachment for this. >
ok, that is an obvious nonsense. I guess I will make modprobe to include modprobe.default automatically instead of relying on including it out of modporbe.conf. generating it this way is WRONG. some modules have changed, some pre/postinstall scripts have changed or not needed any more. module-init-tools supplies modprobe.default that accounts for these changes (tries to). So as suggested, remove module-init-tools, remove modprobe.conf, reinstall module-init-tools and check the difference. It will be more clean and easy to maintain. > > Module seems to exist but I have no idea if it even compiles. > > Try CONFIG_PCNET32 (surprise :) If it compiles and works, tell > > Olivier to include it in its package. > > > You mean re-compile the 2.6 kernel and set this parameter so the module > gets generated? > yep. so far you have alias for eth0 it should work. Apparently just module is missing. BTW compiling 21.6 is much more pleasant and more fast than 2.4 :) And new make xconfig is quite nice. [...] > > I guess the reason I asked about a "how-to" was just to give people a > basic understanding of what to expect from the 2.6Test2 kernel in Cooker > and how to use it (in very basic terms). In order to get more people > testing it, it should be as easy to install and use like the 2.4 kernel > series. > you are right, at least some words about module-init-tools and "generate-modprobe.conf is evil" seem to be needed. Or at least generate-modprobe.conf should be changed to not include standard aliases/config by default (as it does during module-init-tools install). > Thanks for your quick feedback - Let me know if you want to take this > discussion offline . . . > if you still have problems after compiling pcnet32 - send me as much information as you can privately. first check if it loads (and works) using modprobe pcnet32 , then modprobe eth0 then try to find out why it does not load automatically.
