Kodi Community Forum

Full Version: iMON Pad - Need Reliable Info
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5
I'm looking for some reliable info for a linux semi-noob to help me setup my iMON Pad remote that come with my Silverstone CW03 case. I've read so many posts here and other places and I've been unable to get it working as others have described.

I'm running XBMCbuntu Eden (updated it this morning to the release)

I have some buttons that work like the directional pad, mouse buttons, esc, volume up and down and a few others but thats it.

If by chance you also have a good link or info to help me get the 7" LCD working it would be great but right now I'm really wanting to get the remote working better.

Thanks!
There were some *.imo files posted on Soundgraph's forums that add nessecary functionality to control XBMC with this remote. I have an iMon display but i'm currently using an MCE remote with it as I find the directional pad way too sensitive for my liking. Also, i'm not aware of what support there is for the iMon manager under linux, but assuming there is a version, I would suspect an IMO file would enable all the buttons on the iMon remote to function in XBMC and give you what you need.

Sorry I can't be more specific, but I don't have the links to the file to hand.
Actually... I also find the D-Pad to be to sensitive to the point of being ridiculous and to hard to use. My main desire to use that remote is so I do not need an extra IR receiver laying around on my media center. I'm curious if the MCE remote I have would work with the iMON IR receiver. If I could find instructions on how to make that work I would just go that route.
UGH! I'm at my wits end... I've tried everything I can to the point that now I have buttons on my remote that did work that no longer work....

/cry

I just want this stoopid thing to work... Sad
(2012-03-28, 02:11)TwiztedIndian Wrote: [ -> ]UGH! I'm at my wits end... I've tried everything I can to the point that now I have buttons on my remote that did work that no longer work....

/cry

I just want this stoopid thing to work... Sad

If you run:

cat /proc/bus/input/devices

Look for something on one of the N: lines that includes "iMon Panel" and show me what's on the I: lines above those. There are two different types of iMon receivers. One 'old' and one 'new' and they are both handled differently in XBMCuntu as compared to previous versions.
I´ve got nearly the same Problem with a Silverstone LC20m Case with a soundgraph Imon-Pad VFD/IR Reciever.

The only thing that works is tu turn power on and off.

dpkg-reconfigure lirc

taking the imon-pad an no transmitter

restart lirc an then start "irw" shows no reaction.

I´ve got a remote that looks like this

Image

I have the same probleme here, too.
Before I removed and install LIRC the irw command did not work.

The strange thing is, that my remote is working althouh I removed LIRC with all config files.
Now, after installing LIRC again, irw is working but shows no keypress in the shell, but the remote is still working.
Got the same prob.

I don't think eden uses lirc but a kernel built in version by default. This is configured completely differently, I personally have rolled back to Dharma as everything was working as it should. All the wiki's and forums will need time to catch up as there are lots of post regarding this issue.

(2012-03-30, 10:30)Steve122 Wrote: [ -> ]I have the same probleme here, too.
Before I removed and install LIRC the irw command did not work.

The strange thing is, that my remote is working althouh I removed LIRC with all config files.
Now, after installing LIRC again, irw is working but shows no keypress in the shell, but the remote is still working.

That's because it uses the built-in kernel drivers now to drive the remote.

Pictures of the remote do not help though, you need to know which type of receiver you're using hence the whole cat /proc/bus/input/devices thing, it'll tell you which model receiver you're using. Installing ir-keytable (apt-get install ir-keytable) and then running ir-keytable -r will tell you the current mapping. Running ir-keytable -t will show you what each button sends as it comes through.
No Problem....tell me what you need Wink

This is the cat....

cat /proc/bus/input/devices

Code:
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c05b Version=0111
N: Name="Logitech USB Optical Mouse"
P: Phys=usb-0000:00:06.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.0/input/input3
U: Uniq=
H: Handlers=mouse0 event3
B: PROP=0
B: EV=17
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=143
B: MSC=10

I: Bus=0003 Vendor=15c2 Product=ffdc Version=0000
N: Name="iMON Panel, Knob and Mouse(15c2:ffdc)"
P: Phys=usb-0000:00:04.0-6/input1
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb3/3-6/3-6:1.0/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4
B: PROP=0
B: EV=100007
B: KEY=10800320 2000002 0 0 30000 4 110000 4110 801 e1680 0 0 10000002
B: REL=103

I: Bus=0003 Vendor=15c2 Product=ffdc Version=0000
N: Name="iMON Remote (15c2:ffdc)"
P: Phys=usb-0000:00:04.0-6/input0
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb3/3-6/3-6:1.0/rc/rc0/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=100013
B: KEY=fff 0 0 0 108fc326 2176041 0 0 0 4 118000 4180 1 9e9680 0 0 10000000
B: MSC=10

I hope it may help

The type of the receiver is a "Soundgraph iMon-Pad VFD/IR"

And if you need....

Code:
[email protected]:/etc/lirc$ cat /etc/lirc/hardware.conf
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Soundgraph iMON PAD IR/VFD"
REMOTE_MODULES="lirc_dev lirc_imon"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_LIRCD_CONF="imon/lircd.conf.imon-pad"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""
REMOTE_SOCKET=""
TRANSMITTER_SOCKET=""

Greetings
(2012-03-30, 15:32)David1977 Wrote: [ -> ]No Problem....tell me what you need Wink

This is the cat....

cat /proc/bus/input/devices


I hope it may help

The type of the receiver is a "Soundgraph iMon-Pad VFD/IR"

And if you need....

Greetings

Your receiver is the 'old' receiver.

I: Bus=0003 Vendor=15c2 Product=ffdc Version=0000
N: Name="iMON Panel, Knob and Mouse(15c2:ffdc)"

The FFDC portion is how you tell. You no longer need lirc to manage this. Run apt-get install ir-keytable, and then run ir-keytable you should see an output similar to this:

Code:
Found /sys/class/rc/rc0/ (/dev/input/event4) with:
        Driver imon, table rc-imon-pad
        Supported protocols: RC-6 other
        Enabled protocols:
        Extra capabilities: <access denied>

That tells me that I am using the rc-imon-pad key configuration from /lib/udev/rc_keymaps (the file is named imon_pad) inside of there it's pretty similar to an lirc configuration file. e.g.:

Code:
# table imon_pad, type: OTHER
0x2a8195b7 KEY_REWIND
0x298315b7 KEY_REWIND
0x2b8115b7 KEY_FASTFORWARD
0x2b8315b7 KEY_FASTFORWARD
0x2b9115b7 KEY_PREVIOUS
0x298195b7 KEY_NEXT
0x2a8115b7 KEY_PLAY
0x2a8315b7 KEY_PLAY
0x2a9115b7 KEY_PAUSE
0x2b9715b7 KEY_STOP
0x298115b7 KEY_RECORD

Running ir-keytable -t should display something for each button that you hit
Running ir-keytable -r should display the current keymapping for each key.

I'm still working on fixing both of mine (I have both the 'old' and the 'new' receivers and each is being a colossal pain in the ass)
Okay....

I installed ir-keytable .... everything's ok

running ir-keytable gives an output like you said:

Code:
[email protected]:~$ ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
        Driver imon, table rc-imon-mce
        Supported protocols: RC-6
        Enabled protocols:
        Extra capabilities: <access denied>

That means to me, that I'm using the imon-mce file in /lib/udev/rc-keymaps, right?


ir-keymaps -t doesn't show anything while I hit a button on my remote
ir-keymaps -r displays the mapping like you've said

Code:
^[email protected]:/dev/input$ sudo ir-keytable -r
scancode 0x200001e = KEY_NUMERIC_1 (0x201)
scancode 0x200001f = KEY_NUMERIC_2 (0x202)
scancode 0x2000020 = KEY_NUMERIC_3 (0x203)
scancode 0x2000021 = KEY_NUMERIC_4 (0x204)
scancode 0x2000022 = KEY_NUMERIC_5 (0x205)
scancode 0x2000023 = KEY_NUMERIC_6 (0x206)
scancode 0x2000024 = KEY_NUMERIC_7 (0x207)
scancode 0x2000025 = KEY_NUMERIC_8 (0x208)
scancode 0x2000026 = KEY_NUMERIC_9 (0x209)
scancode 0x2000027 = KEY_NUMERIC_0 (0x200)
scancode 0x2000028 = KEY_ENTER (0x1c)
scancode 0x2000029 = KEY_DELETE (0x6f)
scancode 0x200002a = KEY_EXIT (0xae)
scancode 0x200004f = KEY_RIGHT (0x6a)
scancode 0x2000050 = KEY_LEFT (0x69)
scancode 0x2000051 = KEY_DOWN (0x6c)
scancode 0x2000052 = KEY_UP (0x67)
scancode 0x2200020 = KEY_NUMERIC_POUND (0x20b)
scancode 0x2200025 = KEY_NUMERIC_STAR (0x20a)
scancode 0x800ff400 = KEY_NUMERIC_0 (0x200)
scancode 0x800ff401 = KEY_NUMERIC_1 (0x201)
scancode 0x800ff402 = KEY_NUMERIC_2 (0x202)
scancode 0x800ff403 = KEY_NUMERIC_3 (0x203)
scancode 0x800ff404 = KEY_NUMERIC_4 (0x204)
scancode 0x800ff405 = KEY_NUMERIC_5 (0x205)
scancode 0x800ff406 = KEY_NUMERIC_6 (0x206)
scancode 0x800ff407 = KEY_NUMERIC_7 (0x207)
scancode 0x800ff408 = KEY_NUMERIC_8 (0x208)
scancode 0x800ff409 = KEY_NUMERIC_9 (0x209)
scancode 0x800ff40a = KEY_DELETE (0x6f)
scancode 0x800ff40b = KEY_ENTER (0x1c)
scancode 0x800ff40c = KEY_POWER (0x74)
scancode 0x800ff40d = KEY_MEDIA (0xe2)
scancode 0x800ff40e = KEY_MUTE (0x71)
scancode 0x800ff40f = KEY_INFO (0x166)
scancode 0x800ff410 = KEY_VOLUMEUP (0x73)
scancode 0x800ff411 = KEY_VOLUMEDOWN (0x72)
scancode 0x800ff412 = KEY_CHANNELUP (0x192)
scancode 0x800ff413 = KEY_CHANNELDOWN (0x193)
scancode 0x800ff414 = KEY_FASTFORWARD (0xd0)
scancode 0x800ff415 = KEY_REWIND (0xa8)
scancode 0x800ff416 = KEY_PLAY (0xcf)
scancode 0x800ff417 = KEY_RECORD (0xa7)
scancode 0x800ff418 = KEY_PAUSE (0x77)
scancode 0x800ff419 = KEY_STOP (0x80)
scancode 0x800ff41a = KEY_NEXT (0x197)
scancode 0x800ff41b = KEY_PREVIOUS (0x19c)
scancode 0x800ff41c = KEY_NUMERIC_POUND (0x20b)
scancode 0x800ff41d = KEY_NUMERIC_STAR (0x20a)
scancode 0x800ff41e = KEY_UP (0x67)
scancode 0x800ff41f = KEY_DOWN (0x6c)
scancode 0x800ff420 = KEY_LEFT (0x69)
scancode 0x800ff421 = KEY_RIGHT (0x6a)
scancode 0x800ff422 = KEY_OK (0x160)
scancode 0x800ff423 = KEY_EXIT (0xae)
scancode 0x800ff424 = KEY_DVD (0x185)
scancode 0x800ff425 = KEY_TUNER (0x182)
scancode 0x800ff426 = KEY_EPG (0x16d)
scancode 0x800ff427 = KEY_ZOOM (0x174)
scancode 0x800ff446 = KEY_TV (0x179)
scancode 0x800ff447 = KEY_AUDIO (0x188)
scancode 0x800ff448 = KEY_PVR (0x16e)
scancode 0x800ff449 = KEY_CAMERA (0xd4)
scancode 0x800ff44a = KEY_VIDEO (0x189)
scancode 0x800ff44c = KEY_LANGUAGE (0x170)
scancode 0x800ff44d = KEY_TITLE (0x171)
scancode 0x800ff450 = KEY_RADIO (0x181)
scancode 0x800ff45a = KEY_SUBTITLE (0x172)
scancode 0x800ff45b = KEY_RED (0x18e)
scancode 0x800ff45c = KEY_GREEN (0x18f)
scancode 0x800ff45d = KEY_YELLOW (0x190)
scancode 0x800ff45e = KEY_BLUE (0x191)
scancode 0x800ff466 = KEY_RED (0x18e)
scancode 0x800ff468 = KEY_YELLOW (0x190)
Enabled protocols:

Did I do something wrong or what is the fault because ir-keymaps -t won't display anything?
(2012-03-30, 19:10)David1977 Wrote: [ -> ]Okay....

I installed ir-keytable .... everything's ok

running ir-keytable gives an output like you said:

Code:
[email protected]:~$ ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
        Driver imon, table rc-imon-mce

That means to me, that I'm using the imon-mce file in /lib/udev/rc-keymaps, right?


ir-keymaps -t doesn't show anything while I hit a button on my remote
ir-keymaps -r displays the mapping like you've said

Did I do something wrong or what is the fault because ir-keymaps -t won't display anything?

yes, you are using the imon-mce config file in /lib/udev/rc-keymaps which from what I can tell is wrong. I have that exact setup, here's what I did to fix it (mostly):

dpkg-reconfigure lirc
Select Linux input layer (/dev/input/eventX)
Select None (unless you have a remote extender for a satellite dish or something)
In the next list, it's going to give you a complete listing of /dev/input/ you're looking for the one that ends in usb-15c2_ffdc-even-if00
There will actually be 3 of them, one ends in mouse, another ends in something else. You want the one that ends in if00

Once that is completed, it will start lirc using the drivers from the kernel rather than lirc drivers.

Now, I created my own configuration file in /etc/rc_keymaps named imon-pad so...
nano /etc/rc_keymaps/imon-pad

Code:
0x288195b7 KEY_EXIT
0x289115b7 KEY_POWER
0x298115b7 KEY_RECORD
0x2a8115b7 KEY_PLAY
0x29b195b7 KEY_EJECTCD
0x2a8195b7 KEY_REWIND
0x2a9115b7 KEY_PAUSE
0x2b8115b7 KEY_FASTFORWARD
0x2b9115b7 KEY_PREVIOUS
0x2b9715b7 KEY_STOP
0x28a115b7 KEY_ESC
0x2a9315b7 KEY_SPACE
0x28b715b7 KEY_COMPOSE
0x688481b7 BTN_RIGHT
0x28a195b7 KEY_ENTER
0x688301b7 BTN_MOUSE
0x2b8195b7 KEY_CONTEXT_MENU
0x1008000 KEY_UP
0x100007f KEY_RIGHT
0x1007f00 KEY_DOWN
0x1000080 KEY_LEFT
0x2bb715b7 KEY_ESC
0x29b715b7 KEY_DASHBOARD
0x2ab195b7 KEY_MEDIA
0x299395b7 KEY_EJECTCLOSECD
0x2a9395b7 KEY_CYCLEWINDOWS
0x2b9595b7 KEY_MUTE
0x28a395b7 KEY_VOLUMEUP
0x28a595b7 KEY_VOLUMEDOWN
0x289395b7 KEY_CHANNELUP
0x288795b7 KEY_CHANNELDOWN
0x2b8395b7 KEY_TIME
0x28b595b7 KEY_NUMERIC_1
0x2bb195b7 KEY_NUMERIC_2
0x28b195b7 KEY_NUMERIC_3
0x2a8595b7 KEY_NUMERIC_4
0x299595b7 KEY_NUMERIC_5
0x2aa595b7 KEY_NUMERIC_6
0x2b9395b7 KEY_NUMERIC_7
0x2a8515b7 KEY_NUMERIC_8
0x2aa115b7 KEY_NUMERIC_9
0x28b515b7 KEY_NUMERIC_STAR
0x2ba595b7 KEY_NUMERIC_0
0x29a115b7 KEY_NUMERIC_POUND
0x2b8515b7 KEY_RED
0x299195b7 KEY_GREEN
0x2ba115b7 KEY_BLUE
0x28a515b7 KEY_YELLOW
0x288515b7 KEY_BOOKMARKS
0x2ab715b7 KEY_CAMERA
0x29a595b7 KEY_ZOOM
0x2aa395b7 KEY_SCREEN
0x29a395b7 KEY_DVD
0x2ba395b7 KEY_MENU
0x298595b7 KEY_SUBTITLE
0x2b8595b7 KEY_LANGUAGE

Paste all that into it and save it

then run ir-keytable -w /etc/rc_keymaps/imon-pad
that will write the configuration to the keytable, and if you run irw or ir-keytable -t pressing a button on the remote should cause something to appear on screen.

Note ... this is still a work in progress for me ... as not all the remote buttons work as they used to, but I figure helping you get to the point I'm at is better than nothing Smile
You don´t know how correct this is Wink...better than nothing!!!

I´m gonna check this later or maybe tomorrow morning and tell if I´ve got luck Wink

thx for your help!
I have the same problems, tyring to get MCE remote via Soundgraph imon to work with EDEN. My config is this:

Code:
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0003 Vendor=04fc Product=05d8 Version=0100
N: Name="MLK HAMA Black combo set"
P: Phys=usb-0000:00:06.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=04fc Product=05d8 Version=0100
N: Name="MLK HAMA Black combo set"
P: Phys=usb-0000:00:06.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=1f
B: KEY=4837fff 72ff32d bf544446 0 0 1f0001 20f90 8b17c000 677bfa d941dfed 9ed680 4400 0 10000002
B: REL=1c3
B: ABS=1 0
B: MSC=10

I: Bus=0003 Vendor=15c2 Product=0038 Version=0002
N: Name="iMON Panel, Knob and Mouse(15c2:0038)"
P: Phys=usb-0000:00:06.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4
B: PROP=0
B: EV=100007
B: KEY=10800320 2000002 0 0 30000 4 110000 4110 801 e1680 0 0 10000002
B: REL=103

I: Bus=0001 Vendor=13c2 Product=101a Version=0001
N: Name="Budget-CI dvb ir receiver saa7146 (0)"
P: Phys=pci-0000:01:05.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:09.0/0000:01:05.0/rc/rc0/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=100013
B: KEY=40fc010 202061 0 0 0 0 8000 4180 80002001 9e1680 0 0 ffc
B: MSC=10

I: Bus=0003 Vendor=15c2 Product=0038 Version=0002
N: Name="iMON Remote (15c2:0038)"
P: Phys=usb-0000:00:06.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/rc/rc1/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=100013
B: KEY=fff 0 0 0 108fc322 2176041 0 0 0 4 118000 4180 1 9e9680 0 0 10000000
B: MSC=10

I have the same hardware.conf as dave with the exception that I use lircd.conf.imon-mceusb".
Also before in Dharma to get any keys recognized I had to create a lirc_imon.conf file in /etc/modprobe.d containing just one line:
options lirc_imon ir_protocol=1
So dave, you could try this but I guess then you can't start the lirc daemon cause that's what's happening to me now. First I got unrecognized option then I got broken configuration, check hardware.conf.

Everything worked fine under Dharma where I also had to configure quite a few things, but now it seems hopeless. Mythbuntu forum users are talking about some broken lirc_imon drivers/modules in newer linux kernels, I hope that's not the case with xbmcbunte but my best guess is now that in fact it is the problem we are experiencing right now Sad
See also http://forum.xbmc.org/showthread.php?tid=127098 . There were three steps mentioned to somehow downgrade to the good old working lirc_imon, but I don't know how to exactly do the mentioned steps to test if it works.

BTW I tried the way with inputlirc, too, but that's not really bearable for me. I got all the old problems with buttons responding kind of sluggish or too quick etc. , that's why I bought a MCE remote in the first place and put the imon remote in the dumpster.

Well, if nothing else comes up I guess we have to downgrade and wait till some linux experts figure out a way...if ever. I hope there are enough experienced users with the soundgraph IR product else we will all end up like me with a certain WLAN USB stick that will never EVER work under linux because no one cares. I really like the whole concept of linux and OpenSource in general but sometimes it gets frustrating. Well, shouldn't complain really because it's all for free. Wink
Pages: 1 2 3 4 5