Hmm... can you verify that the stuff in .config of the kernel sources
actually matches the stuff in /boot/config-2.6.31* of your XO?
They only differ where I set the Bluetooth stuff.
What does uname -a print?
Linux xo-35-12-ce.localdomain 2.6.31_xo1-20100701.1605.1.olpc.a8f1b26 #1
PREEMPT
Maybe I should try to compile the whole kernel and see if it works?
On Fri, Jan 7, 2011 at 9:41 AM, Emiliano Pastorino
epastor...@plan.ceibal.edu.uy wrote:
Hmm... can you verify that the stuff in .config of the kernel sources
actually matches the stuff in /boot/config-2.6.31* of your XO?
It worked. I had to compile the whole thing and used the resulting
bluetooth.ko
Maybe it's related to that warning about a missing file Module.symvers?
On Fri, Jan 7, 2011 at 9:44 AM, Emiliano Pastorino
epastor...@plan.ceibal.edu.uy wrote:
Maybe I should try to compile the whole kernel and
On Fri, 2011-01-07 at 12:28 -0200, Emiliano Pastorino wrote:
It worked. I had to compile the whole thing and used the resulting
bluetooth.ko
I'm glad it worked! How were you compiling before?
Just make modules SUBDIR=drivers/blah/blah ?
--
// Bernie Innocenti - http://codewiz.org/
\X/
I was doing make M=drivers/bluetooth
Anyways, after compiling the kernel, olpc-configure doesn't recognize some
hardware
and now I have no sound or touchpad. I'll keep my bluetooth modules and
flash my XO.
On Fri, Jan 7, 2011 at 2:46 PM, Bernie Innocenti ber...@codewiz.org wrote:
On Fri,
On Fri, 2011-01-07 at 15:32 -0200, Emiliano Pastorino wrote:
I was doing make M=drivers/bluetooth
Anyways, after compiling the kernel, olpc-configure doesn't recognize
some hardware
and now I have no sound or touchpad. I'll keep my bluetooth modules
and flash my XO.
To ensure that you have
On Fri, Jan 7, 2011 at 6:02 PM, Bernie Innocenti ber...@codewiz.org wrote:
On Fri, 2011-01-07 at 15:32 -0200, Emiliano Pastorino wrote:
I was doing make M=drivers/bluetooth
Anyways, after compiling the kernel, olpc-configure doesn't recognize
some hardware
and now I have no sound or
On Wed, 2011-01-05 at 16:12 -0200, Emiliano Pastorino wrote:
Then, when i execute insmod net/bluetooth/bluetooth.ko, I get:
insmod: error inserting 'net/bluetooth/bluetooth.ko': -1 Invalid
module format
Anything suspicious in the output of dmesg/
vermagic: 2.6.31.6 preempt mod_unload
Anything suspicious in the output of dmesg/
kernel: [ 4892.710548] bluetooth: no symbol version for module_layout
vermagic: 2.6.31.6 preempt mod_unload modversions GEODE 4KSTACKS
Do these things match your running kernel?
I'm running 2.6.31_xo1-20100701.1605.1.olpc.a8f1b26,
On Wed, 2011-01-05 at 17:20 -0200, Emiliano Pastorino wrote:
Anything suspicious in the output of dmesg/
kernel: [ 4892.710548] bluetooth: no symbol version for module_layout
Hmm... can you verify that the stuff in .config of the kernel sources
actually matches the stuff in
On Wed, 2011-01-05 at 14:43 -0600, Mikus Grinbergs wrote:
Each kernel has something I might call a magic handle. [I do not know
how that value is constructed - but I suspect that vermagic is only
*part* of that value.]
When a module needs to be dynamically loaded into the kernel, the (my
Hi,
The version of gcc might take part in computing the magic number.
The idea is to prevent users from causing hard to diagnose bugs
by inadvertently loading modules that aren't 100% ABI compatible
with the running kernel.
It might, but it doesn't -- see
12 matches
Mail list logo
