Re: [Dextrose] Problems compiling bluetooth module
On Fri, Jan 7, 2011 at 6:02 PM, Bernie Innocenti 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 touchpad. I'll keep my bluetooth modules >> and flash my XO. > > To ensure that you have all options set correctly, you may want to copy > the configuration file of the OLPC kernel from /boot/config-2.6.xx and > copy it to .config in the root dir of the kernel tree. Then, you have to > issue a "make oldconfig" or equivalent to regenerate the include files. Sorry to be lagging on this conversation. I do this constantly and will write up my own secret sauce recipe for it tomorrow. Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 all options set correctly, you may want to copy the configuration file of the OLPC kernel from /boot/config-2.6.xx and copy it to .config in the root dir of the kernel tree. Then, you have to issue a "make oldconfig" or equivalent to regenerate the include files. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 wrote: > 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/ Sugar Labs - http://sugarlabs.org/ > > -- Ing. Emiliano Pastorino Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598) 2 601 5773 int.: 2232 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 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? >> >> >> 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 Thu Jul 1 16:08:10 EDT 2010 i586 i586 i386 GNU/Linux >> >> >> On Wed, Jan 5, 2011 at 9:11 PM, Chris Ball wrote: >> >>> 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 include/linux/vermagic.h's >>> VERMAGIC_STRING. >>> >>> - Chris. >>> -- >>> Chris Ball >>> One Laptop Per Child >>> ___ >>> Dextrose mailing list >>> dextr...@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/dextrose >>> >> >> >> >> -- >> Ing. Emiliano Pastorino >> Plan Ceibal >> Av. Italia 6201 CP: 11500, Montevideo, Uruguay >> Tel: (598) 2 601 5773 int.: 2232 >> > > > > -- > Ing. Emiliano Pastorino > Plan Ceibal > Av. Italia 6201 CP: 11500, Montevideo, Uruguay > Tel: (598) 2 601 5773 int.: 2232 > -- Ing. Emiliano Pastorino Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598) 2 601 5773 int.: 2232 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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? > > > 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 Thu Jul 1 16:08:10 EDT 2010 i586 i586 i386 GNU/Linux > > > On Wed, Jan 5, 2011 at 9:11 PM, Chris Ball wrote: > >> 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 include/linux/vermagic.h's >> VERMAGIC_STRING. >> >> - Chris. >> -- >> Chris Ball >> One Laptop Per Child >> ___ >> Dextrose mailing list >> dextr...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/dextrose >> > > > > -- > Ing. Emiliano Pastorino > Plan Ceibal > Av. Italia 6201 CP: 11500, Montevideo, Uruguay > Tel: (598) 2 601 5773 int.: 2232 > -- Ing. Emiliano Pastorino Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598) 2 601 5773 int.: 2232 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
> > 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 Thu Jul 1 16:08:10 EDT 2010 i586 i586 i386 GNU/Linux On Wed, Jan 5, 2011 at 9:11 PM, Chris Ball wrote: > 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 include/linux/vermagic.h's VERMAGIC_STRING. > > - Chris. > -- > Chris Ball > One Laptop Per Child > ___ > Dextrose mailing list > dextr...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/dextrose > -- Ing. Emiliano Pastorino Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598) 2 601 5773 int.: 2232 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 include/linux/vermagic.h's VERMAGIC_STRING. - Chris. -- Chris Ball One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 > name) "magic handle" for the include libraries with which that module > was compiled must match the "magic handle" of the running kernel. If > they don't - the result is the "Invalid module format" message. > > Some months ago I tried my best to compile a driver and add it to the > os852 build - but no matter how careful I was - I could NOT satisfy that > "magic handle" comparison when it came time to load that driver. [I > ended up recompiling the whole kernel (now having the missing driver > specified as part of the configuration for this kernel's compile).] 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. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 /boot/config-2.6.31* of your XO? > > 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, that's all I > know What does "uname -a" print? You might be running a newer or older kernel, or a kernel configured differently. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
> > 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, that's all I know > -- > // Bernie Innocenti - http://codewiz.org/ > \X/ Sugar Labs - http://sugarlabs.org/ > > -- Ing. Emiliano Pastorino Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598) 2 601 5773 int.: 2232 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problems compiling bluetooth module
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 modversions GEODE 4KSTACKS > Do these things match your running kernel? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
