[uClinux-dev] Kernel modules don't work on read-only filesystems ?

[David Wu]

On Wed, 10 Oct 2007 16:59:56 -0400, Josue de Freitas  
<josue.freitas at gmail.com> wrote:

> On 10/10/07, Crane, Matthew <mcrane03 at harris.com> wrote:
>>
>>  Hi,
>>
>> Sounds like your module didn't actually get inserted.  Can you verify it
>> is present with an lsmod?   If it failed to insert, then check your  
>> klog.
>>
>
>
> Yes it is up. It's very strange because it's up but seems not to be  
> running,
> a simple "hello world" module using printk  also don't work, it gets up  
> but
> apparently not run (damn my naivety to think that this will work :p).
>
> The scull module is suppose to create an proc dir entry called scullmem,  
> but
> it's not created.
Did you do a strip on the module? If yes then try not strip.

>
> # lsmod
> Module                  Size  Used by
> scull                  10708   0 (unused)
> #
>
> An also:
>
> # cat /proc/ksyms | grep scull
> 30dd8000
> __insmod_scull_O/lib/modules/2.4.34.5-uc0/kernel/drivers/char/scull/scull.o_M00000000_V-1
> [scull]
> 30dd8060 __insmod_scull_S.text_L9656    [scull]
> 30dda618 __insmod_scull_S.rodata_L38    [scull]
> 30dda640 __insmod_scull_S.data_L512     [scull]
> #
>
>
>
> You can build the module into the kernel statically to verify that it  
> works
>> with the device node.
>>
>
>
> It's a possibility. But to do it I just have to chance de obj-m to obj-y  
> on
> the Makefiles ? I think I must undefine de MODULE directive also, right ?
> Any other hint of how to make it statically ?
>
>
> Matt
>>
>>
>
> Thanks Matthew.
>
> Regards, Josue.



-- 
David
davidwu at arcturusnetworks.com