SamyGO

Hey guys!

What a cool feature in combination with Netsurf.
Since the first posting of this thread states, that the Mouse an Keyboard extension can be used by Content Library Software, I suppose that there is no way to get those extensions started automatically by SamyGo.sh and being used by the youtube widget. Am I right?

I have a some generic USB hub which ID is
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
and works with this TV. I think you can use most of USB hubs with it.

Hi all,

@lmax69: I just bought myself an el-cheapo hub (Sitecom, 4-port micro USB hub). Works out-of-the-box, as most hubs do and fits neatly behind the rim of the TV screen (on my UE40B7020 at least), so you can't see it.

The reason I bought it is because my wife and kids discovered the possibility to use the TV as web browser. I demonstrated the NetSurf app yesterday night, stupid me, so this morning we had to go and buy a wireless mouse and keyboard (and the hub). And that's where the problems arise right now.

The keyboard works fine, but the mouse doesn't. It is a logitech M505 with unified connection. I manually installed usbhid.ko and evdev.ko, both from arris's samyGO extension pack for T-CHU7DEUC. I copied part of the startup scripts to make the device special files. mouse0, mouse1, mice, hiddev0 hiddev1 and hidraw0, hidraw1, and an awful lot of event0 ---31 files.

Attached to my laptop (fedora 14) both devices do their job, so it's no DOA).

(oh btw, the reason I didn't use the extension pack as is is because (flash)memory is quite tight on my TV. I want to keep the installation as lean as possible.)

This is the message I get in dmesg:
I don't trust the last line: looks like I miss hiddev.ko or some device special file.

My questions:

Are driver modules usbhid.ko and evdev.ko enough to drive a mouse? In the hiddev_init script there is mention of the insertion of hiddev.ko, but this module is not available in the extension pack.

The /dev directory is read-only. I put all device special files in /dtv according to arris's scripts. Where do I tell the module loader to look for modules elsewhere, or what environment variable do I need to set to point to the device special file directory?

grtz, and thanks for any comments,

marcelru

marcelru wrote: ...
My questions:

Are driver modules usbhid.ko and evdev.ko enough to drive a mouse? ...

marcelru

first load evdev and than usbhid

hth
arris

Hi arris69,

The reversal of insmodding the modules didn't work.

I just tested the extensions pack (00 3.6) from USB stick, so far no success either.
For now I will test my new hardware on another linux box, maybe there are some issues with it that I haven't noticed so far.
(On an old linux desktop (FC14) that I have, the mouse works and the keyboard doesn't ....)

Anyway, thanks for your response, I'll stop here and when I need more help, I will continue in the support section. This is not the right thread for it.

have a nice new years eve,

marcelru