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