Michael Marsh wrote: To the module.john gennard <[EMAIL PROTECTED]> wrote:I followed O'Reilly - tried 'insmod' and as unsuccessful, built a database with 'depmod -a'. 'modules.dep' showed there were dependencies, so I used 'modprobe' which I understood should find and install the dependencies. O'Reilly says I should use the full path - is this a recent change?The full path to modprobe, or the full path to the module? Using the full path to modprobe is a good idea. I don't know what the history of modprobe's arguments is, but given that it needs to find the appropriate module for a given kernel, you'd always want to leave the path out and let it do the work for you. This advice has solved the problem. '/sbin/modprobe atmel' loads all three modules. Putting 'atmel' into '/etc.modules' and rebooting has loaded them. Now to play with 'iwconfig' and I'm home and dry. Michael, I'm most grateful that you've taken time to help me as you have. Being long retired means not having anyone to discuss things with and also almost all problems are first time ones. Many thanks, John. Yes it was -sorry if I created confusion.I don't get any more detail in the error messages:- modprobe <full path> says file not found. modprobe <atmel> gives no output, merely returns to the promptI assume the second line was actually modprobe atmel (ie, without the angle brackets). If not, try without the brackets. Also try "lsmod", which will show you what's loaded. It might be that you've got the module loaded now, and should be set. You can also give modprobe the "-v" option to make it more verbose. |
- -1 Unknown symbol in module john gennard
- Re: -1 Unknown symbol in module Michael Marsh
- Re: -1 Unknown symbol in module john gennard
- Re: -1 Unknown symbol in module Michael Marsh
- john gennard