1 |
Hi Alan! |
2 |
Solved it!!! |
3 |
|
4 |
I recompiled the kernel, and unchecked the builtin option |
5 |
NET_WAN_ROUTER, which was previously set in the kernel config. |
6 |
|
7 |
After then, I rebuilt wanpipe from the scratch again, and then VOILAAA, |
8 |
IT WORKED!!!! |
9 |
|
10 |
|
11 |
|
12 |
Tamer |
13 |
|
14 |
|
15 |
Am 08.03.2013 14:09, schrieb Alan McKinnon: |
16 |
> On 08/03/2013 13:52, Tamer Higazi wrote: |
17 |
>> Hi Alan, |
18 |
>> insmod wanrouter.ko tells me in dmesg: |
19 |
>> |
20 |
>> |
21 |
>> wanrouter: exports duplicate symbol register_wan_device (owned by kernel) |
22 |
> |
23 |
> |
24 |
> It means your module is buggy and you can't use it. |
25 |
> |
26 |
> |
27 |
>> |
28 |
>> |
29 |
>> what does this message mean here ??? |
30 |
>> |
31 |
>> |
32 |
>> Tamer |
33 |
>> |
34 |
>> |
35 |
>> Am 07.03.2013 21:57, schrieb Alan McKinnon: |
36 |
>>> On 07/03/2013 22:53, Daniel Frey wrote: |
37 |
>>>> On 03/07/2013 09:23 AM, Tamer Higazi wrote: |
38 |
>>>>> Hi people! |
39 |
>>>>> I have tried to install the latest release of wanpipe through the |
40 |
>>>>> freeswitch overlay, which I did so far successfully. Shortly I have |
41 |
>>>>> realised, that the "wanrouter" module is not loadable. When I try to |
42 |
>>>>> load it I get the following error: |
43 |
>>>>> |
44 |
>>>>> office / # modprobe wanrouter |
45 |
>>>>> modprobe: ERROR: could not insert 'wanrouter': Exec format error |
46 |
>>>>> |
47 |
>>>>> |
48 |
>>>>> What could it be?! |
49 |
>>>>> |
50 |
>>>> |
51 |
>>>> It sounds like the kernel doesn't know how to run the binary. I don't |
52 |
>>>> have experience with this particular error, but maybe running |
53 |
>>>> |
54 |
>>>> `file wanrouter.ko` |
55 |
>>>> |
56 |
>>>> and checking to see what it says may be of help. |
57 |
>>>> |
58 |
>>>> It should tell you what executable format it is using, then you'd need |
59 |
>>>> to cross-reference in the kernel .config to make sure you have support |
60 |
>>>> for that executable format compiled in. |
61 |
>>>> |
62 |
>>>> Dan |
63 |
>>>> |
64 |
>>> |
65 |
>>> He should also check what dmesg says when modprobing the module, that |
66 |
>>> usually gives a clue. |
67 |
>>> |
68 |
>>> An elementary Google search reveals that it's usually obvious things |
69 |
>>> like trying to load a module built for a different kernel version, or |
70 |
>>> trying to load a module that is not compatible with another one already |
71 |
>>> loaded. |
72 |
>>> |
73 |
>> |
74 |
>> |
75 |
> |
76 |
> |