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

[David Wu]

On Thu, 11 Oct 2007 09:30:26 -0400, Josue de Freitas  
<josue.freitas at gmail.com> wrote:

> On 10/10/07, David Wu <davidwu at arcturusnetworks.com> wrote:
>>
>> 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.
>
>
>
> I never wonder if this have any influence... but it's not-stripped:
>
> # file scull.o
> scull.o: ELF 32-bit MSB relocatable, version 1 (SYSV), not stripped
This doesn't show if it is stripped. try list the size of your module in  
the kernel tree and on the target.
BTW. what do you have in /proc/sys/kernel/printk ?
>
> thanks David.
>
> Regards, Josue.



-- 
David
davidwu at arcturusnetworks.com