legousbtower kernel module

[Paul Fox]

bert wrote:
 > On 07.05.2012, at 19:05, Paul Fox <pgf at laptop.org> wrote:
 > 
 > > bert wrote:
 > >> 
 > >> On 07.05.2012, at 18:19, Paul Fox wrote:
 > >> 
 > >>> bert wrote:
 > >>>> Hi,
 > >>>> 
 > >>>> I'm trying to connect a LEGO RCX via the RCX 2.0 USB Tower. When plugging it 
 > >>>> in, it gets listed with name and vendor in the messages log. 
 > >>>> 
 > >>>> However, /dev/usb/lego0 is not created. The corresponding udev rule is 
 > >>>> installed by Fedora's "nqc" rpm, but it relies on the "legousbtower" kernel 
 > >>>> module.
 > >>>> 
 > >>>> AFAICT, it does not work because legousbtower.ko is missing.
 > >>>> 
 > >>>> This is both on an XO-1.5 (11.3.0) and a 1.75 (11.3.1). The latter at least 
 > >>>> creates an entry in /dev while plugged in, but it's a generic usb one. On 
 > >> the 
 > >>>> former I don't see any dev node created when plugging in.
 > >>>> 
 > >>>> Am I doing something wrong, or is it really just that the OLPC kernel is 
 > >>>> missing that module? If so, where can I get it? Or do I have to try 
 > >> compiling 
 > >>>> myself?
 > >>> 
 > >>> i think the kernel is really missing that module.  i'd never heard
 > >>> of it until just now.
 > >>> 
 > >>> i'll see if we can get an rpm built for 11.3.0 and 11.3.1.  (and 12.1.0)
 > >>> 
 > >>> paul
 > >> 
 > >> Awesome! But the driver is in the regular kernel sources, right? Just not 
 > >> configured to be built?
 > > 
 > > yes.
 > > 
 > > paul
 > > =---------------------
 > > paul fox, pgf at laptop.org
 > 
 > I installed (rpm -Uvh) this kernel on top of 883:
 > 
 > http://rpmdropbox.laptop.org/f14-xo1.5/kernel-2.6.35.13_xo1.5-20120508.1139.olpc.eb0c7a8.i586.rpm
 > 
 > It booted fine, but the touchpad does not work, keyboard does, network does not, lego tower does not. 
 > 
 > Should I have done this differently? Any advice how to diagnose this, and get the machine working correctly again?
 > 
 > Thanks!

did you "cp -a /boot/* /bootpart/boot/" ?   our kernel rpms still
have this "feature" where not quite all the right pieces are put
in place.  that might nor might not be the entire problem -- i hope
so.

(you might try "uname -a" and see if the kernel you ended up booting
matches the above rpm.)

i won't be able to test myself until monday, so you if you simply
want a working machine, go to /bootpart/boot and redirect the vmlinuz
symlink back to the original kernel, and reboot.

paul
=---------------------
 paul fox, pgf at laptop.org