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

[Crane, Matthew]

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.
 
You can build the module into the kernel statically to verify that it
works with the device node.  

Matt
 
________________________________

From: uclinux-dev-bounces at uclinux.org
[mailto:uclinux-dev-bounces at uclinux.org] On Behalf Of Josue de Freitas
Sent: Wednesday, October 10, 2007 1:53 PM
To: uClinux development list
Subject: [uClinux-dev] Kernel modules don't work on read-only
filesystems ?


Hi people,

I'm trying to build the scull module example from Chapter 3 of Linux
Device Drivers book and it's not working. I create a /dev/scull0 (with
fixed major number, which is also configured on the module source) but
when I stand up the module and try something like "dd if=/dev/zero
of=/dev/scull0" it gives a message "dd: /dev/scull0: No such device".
According to the book a "cat /proc/devices" should show the scull device
when the module is up but nothing about scull is there, nothing changes
on /proc/devices with or without the module loaded. 

So the main question is: dynamic module loading works perfectly on a
read-only filesystem on uClinux ?


If this is not the best place to this kind of question, please tell me
where I can send this doubt. ;) 


Thanks in advance, Josue.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.uclinux.org/pipermail/uclinux-dev/attachments/20071010/cf997118/attachment.html