Unfortunately I failed in 'modprobe'. FFC3 3.1.0-ffc3mb-00050-g5874787 # pwd /lib/modules/3.1.0-ffc3mb-00050-g5874787 FFC3 3.1.0-ffc3mb-00050-g5874787 # modprobe tun modprobe: can't load module tun (net/tun.ko): invalid module format FFC3 3.1.0-ffc3mb-00050-g5874787 # modinfo net/tun.ko filename: net/tun.ko license: GPL author: (C) 1999-2004 Max Krasnyansky <maxk@xxxxxxxxxxxx> description: Universal TUN/TAP device driver alias: devname:net/tun depends: vermagic: 3.1.0-ffc3mb-00050-g5874787 -ffc3mb-00055-g4c6394f-dirty mod_unload ARMv5 Can you help to give a clue? Thanks in advance! -woody On 30 March 2015 at 17:45, Adam Lee <adam8157@xxxxxxxxx> wrote: > On Mon, Mar 30, 2015 at 05:35:23PM +0800, Woody Wu wrote: >> Thanks and glad to know that. Just be curious, it means, in kernel building, >> select a driver as M or as EMPTY will put no influence on the resulted kernel >> image at all, is it right? > > Not right if that driver depends on some other things. > >> Previously, I always thought, when I choice a >> driver as module, I was not only creating a module itself, but also force the >> kernel create some kind of a stub in it's image. Now it seems my thoughts is >> wrong. > > You were right at the most of times, but it could be inserted at the most > of times too, not that picky. Also you still could extract its > dependencies(if there are) out and compile them as external modules. > > -- > Adam Lee > http://adam8157.info -- Life is the only flaw in an otherwise perfect nonexistence -- Schopenhauer woody public key at http://subkeys.pgp.net:11371 (narkewoody@xxxxxxxxx) _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
