problem with infrared usb stick ?

frenchn00b · 09-27-2007, 02:15 PM

Problem with irda infrared usb stick:
i have that :
http://www.pcmegastore.nl/catalog/im...ustRC-2400.jpg
http://www.trust.com/products/default.aspx?item=15254
i remove it and plug, it says:

Code:

usb 1-1: USB disconnect, address 5
usb 1-2: USB disconnect, address 4
usb 1-2: new low speed USB device using uhci_hcd and address 6
usb 1-2: configuration #1 chosen from 1 choice
usb 1-2: USB disconnect, address 6
usb 1-2: new low speed USB device using uhci_hcd and address 7
usb 1-2: configuration #1 chosen from 1 choice

Code:

lsusb
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 008: ID 147a:e017 Formosa Industrial Computing, Inc.
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 005: ID 045e:0084 Microsoft Corp.
Bus 003 Device 004: ID 046d:0928 Logitech, Inc. Quickcam Express
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 003: ID 0556:0001 Asahi Kasei Microsystems Co., Ltd AK5370 I/F A/D Converter
Bus 004 Device 001: ID 0000:0000

and :

Quote:

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 8 Spd=1.5 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=147a ProdID=e017 Rev= 1.10
S: Manufacturer=Formosa21
S: Product=SnowflakeEmulation
S: SerialNumber=C0000CA7
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
E: Ad=02(O) Atr=03(Int.) MxPS= 8 Ivl=10ms

but there is nothing in devices:

Quote:

cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=0084 Version=0110
N: Name="Microsoft Basic Optical Mouse"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input3
U: Uniq=
H: Handlers=kbd event2
B: EV=40001
B: SND=6

I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=button_power/button/input0
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=100000 0 0 0

HELP, what should I DO ??

frenchn00b · 09-27-2007, 02:21 PM

and this, what does it mean ?

Code:

AS FAR AS I KNOW YOU MUST DO ALL OF THE FOLLOWING!
--------------------------------------------------

Kernel:
  Disable USB HID event layer support in the kernel (CONFIG_USB_HIDINPUT)
  Enable USB Human Interface Device (full HID) support (CONFIG_USB_HID)
  Enable /dev/hiddev raw HID device support (CONFIG_USB_HIDDEV)
  Recompile, copy to the appropriate boot location, reboot.

Set up HID devices:
    cd /dev/usb
    mkdir -p /dev/usb/hid
    mknod /dev/usb/hiddev0 c 180 96  
    mknod /dev/usb/hiddev1 c 180 97
    mknod /dev/usb/hiddev2 c 180 98
    mknod /dev/usb/hiddev3 c 180 99
    mknod /dev/usb/hiddev4 c 180 100

Set up virtual IR501 mouse support:
  cd /dev/usb
  mknod fauxmouse p

frenchn00b · 09-27-2007, 04:52 PM

I found that for formosa devices irda ./...

http://www.undergroundcircus.net/ben/ir501d.html

I get this unfrotuenately:

Code:

ir501d-0.1# ./compile
ir501d.c: In function 'read_config':
ir501d.c:68: warning: incompatible implicit declaration of built-in function 'strcpy'
ir501d.c:82: warning: incompatible implicit declaration of built-in function 'strcpy'
Read the install file for remaining instructions.

zlin50 · 10-12-2007, 11:22 AM

Hi,

it seems to me that I have a similar problem
(me with the i/r-remote of a terratec cinergy xs usb dvb-t receiver)

Our (first) problem is here: :-( :-)

Quote:

Originally Posted by frenchn00b

Problem with irda infrared usb stick:

S: Manufacturer=Formosa21
S: Product=SnowflakeEmulation
S: SerialNumber=C0000CA7
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

HELP, what should I DO ??

I assume, this was the output of
$ cat /proc/bus/usb/devices

There is no driver loaded for your device, therefore, you can't find it in /proc/bus/input/devices.

Greetings,
Markus

frenchn00b · 10-12-2007, 01:03 PM

Quote:

Originally Posted by zlin50

Hi,

it seems to me that I have a similar problem
(me with the i/r-remote of a terratec cinergy xs usb dvb-t receiver)

Our (first) problem is here: :-( :-)

I assume, this was the output of
$ cat /proc/bus/usb/devices

There is no driver loaded for your device, therefore, you can't find it in /proc/bus/input/devices.

Greetings,
Markus

Hi

I am very glad that I am not alone with that problem
could we exchange the email address?

I just found this http://web.mat.bham.ac.uk/R.W.Kaye/s...e/rc102remote/
looks very interesting for our problem

I hope we can make it work !

--
btw would you know anything about that http://www.linuxquestions.org/questi...3/#post2922364 ?

frenchn00b · 10-13-2007, 04:36 PM

I think we could modify this one : 147a:e019, sligthly http://www.qbik.ch/usb/devices/showdev.php?id=3863

so that we can read through udp the : 147a:e017 (how to insatll the 147a:e017, it is easy: http://braithwaite.dk/wikka/ZolidIrRemote)
it should not be that much changes normally, I would say ...

has someone more info how to adapt the http://www.qbik.ch/usb/devices/showdev.php?id=3863 to our device

thanks !!

frenchn00b · 10-14-2007, 10:38 AM

RC-2400 Trust, Working on it with assistance. Sounds very promising, the results ... You will soon have it working too. Nice info. nope ?

zlin50 · 10-15-2007, 12:35 PM

Hi,

yesterday I had another try with the current kernel (2.6.23.1) - same results as before.

I will abandon. :-(

frenchn00b · 10-15-2007, 12:59 PM

Quote:

Originally Posted by zlin50

Hi,

yesterday I had another try with the current kernel (2.6.23.1) - same results as before.

I will abandon. :-(

Nope it is already fairly well working

hehe :-)

Can you wait few days for a driver release ?

frenchn00b · 10-23-2007, 03:04 PM

We have now the driver working for the Trust, RC 2400 !!
lsusb:
Bus 001 Device 005: ID 147a:e017 Formosa Industrial Computing, Inc.

Released & ready to be retrived for linux!

If anyone has a rc2400.conf, please do not hesitate to post it in this thread too !
Thx to the Linux Opensource community

frenchn00b · 10-23-2007, 04:26 PM

I am encountering difficulties with the irrecord...

it is quite hell with that:
Now hold down button "more".
Sorry, something went wrong.
Try again.
Sorry, something went wrong.
Try again.
Sorry, something went wrong.
Try again.
Sorry, something went wrong.
Try again.
Sorry, something went wrong.
Try again.
Sorry, something went wrong.
Try again.
Got it.
Signal length is 67

Jadedjay · 11-05-2007, 10:10 AM

Hi there

Did you manage to get your remote going?

I have just bought an ELECOM remote in Japan which appears to have the same Vender and Product id as your remote.
"http://www.akihabaranews.com/en/news-13834-RC-MV01%2C+the+Media+Center+remote.html"
I was in the process of trying to get it working with the lirc_mceusb2 driver as I thought it was a MCE remote. But no luck yet.

How are your attempts working out? Im hoping that by the sounds of it you have almost solved all the problems with this remote?

frenchn00b · 11-05-2007, 05:30 PM

Quote:

Originally Posted by Jadedjay

Hi there

Did you manage to get your remote going?

I have just bought an ELECOM remote in Japan which appears to have the same Vender and Product id as your remote.
"http://www.akihabaranews.com/en/news-13834-RC-MV01%2C+the+Media+Center+remote.html"
I was in the process of trying to get it working with the lirc_mceusb2 driver as I thought it was a MCE remote. But no luck yet.

How are your attempts working out? Im hoping that by the sounds of it you have almost solved all the problems with this remote?

The driver developer has already made a great great job !! the driver is "partially" and could be said as working.

Hence, I am working on a alternative to lirc. It is working with alternative program I wrote to lirc. it is up to development for the moment. You can code ? I PM you ...

edit : PMing you is not working (?)

Jadedjay · 11-05-2007, 09:28 PM

Quote:

Originally Posted by frenchn00b

The driver developer has already made a great great job !! the driver is "partially" and could be said as working.

Hence, I am working on a alternative to lirc. It is working with alternative program I wrote to lirc. it is up to development for the moment. You can code ? I PM you ...

edit : PMing you is not working (?)

Hi
I think PM should be working now as I changed my profile options.

Now I understand more clearly, thanks.

I can code, but I have never coded a driver before. I may be able to help.

zlin50 · 11-11-2007, 02:02 PM

Quote:

Originally Posted by zlin50

Hi,

yesterday I had another try with the current kernel (2.6.23.1) - same results as before.

I will abandon. :-(

News:

I was able to make the i/r-receiver visible to the input layer (/dev/bus/input/...) by compiling "usbkbd" into the kernel.

I'm mentioning it here, since the kernel says:
"CONFIG_USB_KBD
Say Y here only if you are absolutely sure that you don't want
to use the generic HID driver for your USB keyboard and prefer
to use the keyboard in its limited Boot Protocol mode instead.

This is almost certainly not what you want.

This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usbkbd.o. If you want to compile it as a
module, say M here and read <file

ocumentation/modules.txt>."

Next step: trying to get the remote control running with vdr.