Dear Nastya,

I think you need to compile your own kernel. As you compile OE
yourself it is even easier. Anyway you can take any kernel version,
apply patches from OE, make all necessary changes to a kernel and get
what you need. I've done this before and it worked for me.

what dmesg prints to your console?

You just need to integrate all USB stuff into your kernel and forget
about modules.

Max

2010/1/28 Анастасия Жирнова <[email protected]>:
>
>
>> Hi!
>>
>> I suggest you to have such string i Xserver
>> ARGS="$ARGS -dpi 10 -rgba bgr -screen 480x640"
>>
>> just remove "-mouse". I don't work with CRT monitors, but at
>> conventional LCD panels (no TS) USB mouses work fine. Furthermore I
>> only tested kernels 2.6.27 and 28.
>>
>> Anyway I think it is good idea to see dmesg, may be there are a lot of
>> errors regarding USB mouse..
>> Just type dmesg in linux console
>>
>> Max
>>
> So, I tried your suggestion. Thank's a lot, but it didn't help me(((
>
> I did the same changes (as I described in the first post) with 
> angstrom-x11-DEMO-image (not built but downloaded from linux4sam.org). And 
> the mouse became to work. But I need mouse to work in MY x11-image built with 
> openembedded. I saw there were many differences between these two images. In 
> DEMO-image there are kernel-module-usbhid and kernel-module-usbmouse. And in 
> my image there aren't such packages. I tried to find them in angstrom feed 
> but I couldn't find them((( Where can I download it???
> The second strange thing is that the task-base-usbhost takes place during 
> building of rootfs image. Mustn't it include usbhid and usbmouse???
>
> Sincerely yours, Nastya.
> Waiting for a reply
>
> _______________________________________________
> Angstrom-distro-users mailing list
> [email protected]
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
>

_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users

Reply via email to