| Author |
Message |
|
shplad
|
 Posted: Thu Jul 21, 2005 3:51 pm |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
Hi all:
Due to my Mythbox being inside an entertainment centre, I've had to bend over to type
on the keyboard, and the result has been strained muscles. So I thought I'd try to relieve
the strain by introducing a wireless keyboard.
I picked up one of these BTC 9019URF models (Very nice)
http://www.pcalchemy.com/product_info.php/pName/btc-9019urf-wireless-multimedia-keyboard-wdual-mode-joystick?osCsid=a412037a929b3797139f5d0365ca0654
and I'm wondering if someone can tell me:
1. Where I could find some examples on how to configure a similar type of USB keyboard
AFTER KnoppMyth has already been installed. (I installed KnoppMyth using a regular PS/2 Keyboard.)
2. What kinds of issues I am likely to encounter trying to get it working, both within Linux, and within X.
Now, before anyone jumps all over me, I HAVE searched the forums, and I have read
some of the posts, including posts on other sites. But most of the posts related to USB
keyboards seem to deal with pre-install, not post-install configuration and issues, so I thought
I'd check to see if I could get this keyboard working. I know this could be a bit of work, but
Trust me, if you had one of these on your lap, you'd want to get it working in Myth. The keyboard
was obviously designed for HTPC use.
Thanks for any help in advance.
shplad
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
 |
|
tjc
|
Posted: Thu Jul 21, 2005 7:05 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
You'll definitely have to fix your XF86Confgi-4 and some other system config file under /etc
... Try this to get a feel for places that might need some love... (Sorry I'm away from the box or might be able to provide more detail.)
Code: find /etc -type f -print0 | xargs -0 grep -i ps2
|
|
| Top |
|
|
|
shplad
|
Posted: Thu Jul 21, 2005 8:17 pm |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
tjc:
Thanks. Here is the output.
Code: root@box:~# find /etc -type f -print0 | xargs -0 grep -i ps2
/etc/X11/xkb/keycodes/powerpcps2:// $XFree86: xc/programs/xkbcomp/keycodes/power
pcps2,v 1.1 2000/09/19 12:46:23 eich Exp $
/etc/X11/xkb/keycodes/powerpcps2:default xkb_keycodes "powerpcps2" {
/etc/X11/xkb/keycodes.dir:-d------ -------- powerpcps2(powerpcps2)
/etc/X11/xkb/rules/xfree86: powerpcps2 = powerpcps2
/etc/X11/xkb/rules/xfree86.xml: <name>powerpcps2</name>
/etc/X11/xkb/rules/xfree86.xml: <description>powerpcps2 - No decripti
on</description>
/etc/X11/xkb/rules/xfree86.xml: <description xml:lang="bg">powerpcps2 - Ð
±ÐµÐ· опиÑание</description>
/etc/Xprint/C/print/attributes/document:# "PS2PDFspooldir-GS" jobs should always
be 600 DPI
/etc/Xprint/C/print/attributes/document:PS2PDFspooldir-GS.default-printer-resolu
tion: 600
/etc/Xprint/C/print/attributes/printer:# Sample entry for the "PS2PDFspooldir-GS
" model
/etc/Xprint/C/print/attributes/printer:# to PDF using "ps2pdf" and files them in
to the "$HOME/Xprintjobs/" directory.
/etc/Xprint/C/print/attributes/printer:# instead of relying on GhostScript/ps2pd
f...
/etc/Xprint/C/print/attributes/printer:xp_pdf_spooldir_HOME_Xprintjobs.xp-model-
identifier: PS2PDFspooldir-GS
/etc/kde3/ksslcalist:x509=MIIFLDCCBBSgAwIBAgIEOU99hzANBgkqhkiG9w0BAQUFADBaMQswCQ
YDVQQGEwJXVzESMBAGA1UEChMJYmVUUlVTVGVkMRswGQYDVQQDExJiZVRSVVNUZWQgUm9vdCBDQXMxGj
AYBgNVBAMTEWJlVFJVU1RlZCBSb290IENBMB4XDTAwMDYyMDE0MjEwNFoXDTEwMDYyMDEzMjEwNFowWj
ELMAkGA1UEBhMCV1cxEjAQBgNVBAoTCWJlVFJVU1RlZDEbMBkGA1UEAxMSYmVUUlVTVGVkIFJvb3QgQ0
FzMRowGAYDVQQDExFiZVRSVVNUZWQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCgg
EBANS0c3oTCjhVAb6JVuGUntS+WutKNHUbYSnE4a0IYCF4SP+00PpeQY1hRIfo7clY+vyTmt9P6j41ff
gzeubx181vSUs9Ty1uDoM6GHh3o8/n9E1z2Jo7Gh2+lVPPIJfCzz4kUmwMjmVZxXH/YgmPqsWPzGCgc0
rXOD8Vcr+il7dw6K/ifhYGTPWqZCZyByWtNfwYsSbX2P8ZDoMbjNx4RWc0PfSvHI3kbWvtILNnmrRhyx
dviTX/507AMhLn7uzf/5cwdO2NR47rtMNE5qdMf1ZD6Li8tr76g5fmu/vEtpO+GRg+jIG5c4gW9JZDnG
dzF5DYCW5jrEq2I8QBoa2k5MUCAwEAAaOCAfgwggH0MA8GA1UdEwEB/wQFMAMBAf8wggFZBgNVHSAEgg
FQMIIBTDCCAUgGCisGAQQBsT4BAAAwggE4MIIBAQYIKwYBBQUHAgIwgfQagfFSZWxpYW5jZSBvbiB0aG
lzIGNlcnRpZmljYXRlIGJ5IGFueSBwYXJ0eSBhc3N1bWVzIGFjY2VwdGFuY2Ugb2YgdGhlIHRoZW4gYX
BwbGljYWJsZSBzdGFuZGFyZCB0ZXJtcyBhbmQgY29uZGl0aW9ucyBvZiB1c2UsIGFuZCBjZXJ0aWZpY2
F0aW9uIHByYWN0aWNlIHN0YXRlbWVudCwgd2hpY2ggY2FuIGJlIGZvdW5kIGF0IGJlVFJVU1RlZCdzIH
dlYiBzaXRlLCBodHRwczovL3d3dy5iZVRSVVNUZWQuY29tL3ZhdWx0L3Rlcm1zMDEGCCsGAQUFBwIBFi
VodHRwczovL3d3dy5iZVRSVVNUZWQuY29tL3ZhdWx0L3Rlcm1zMDQGA1UdHwQtMCswKaAnoCWkIzAhMR
IwEAYDVQQKEwliZVRSVVNUZWQxCzAJBgNVBAYTAldXMB0GA1UdDgQWBBQquZtpLjub2M3eKjEENGvKBx
irZzAfBgNVHSMEGDAWgBQquZtpLjub2M3eKjEENGvKBxirZzAOBgNVHQ8BAf8EBAMCAf4wDQYJKoZIhv
cNAQEFBQADggEBAHlh26Nebhax6nZR+csVm8tpvuaBa58oH2U+3RGFktToQb9+M70j5/Egv6S0phkBxo
yNNXxlpE8JpNbYIxUFE6dDea/bow6be3ga8wSGWsb2jCBHOElQBp1yZzrwmAOtlmdE/D8QDYZN5AA7KX
vOOzuZhmElQITcE2K3+spZ1gMe1lMBzW1MaFVA4e5rxyoAAEiCswoBw2AqDPeCNe5IhpbkdNQ96gFxug
R1QKepfzk5mlWXKWWuGVUlBXJH0+gY3Ljpr0NzARJ0o+FcXxVdJPP55PS2Z2cS52QiivalQaYctmBjRY
oQtLpGEK5BV2VsPyMQPyEQWbfkQN0mDCP2qq4=
/etc/vga/libvga.config:# mouse PS2 # PS/2 mouse
/etc/vga/libvga.config:# mouse IMPS2 # Microsoft IntelliMouse or Logi
tech MouseMan+ on PS/2 port
/etc/vga/libvga.config:# Note that this option has no effect unless the IntelliM
ouse or IMPS2 mouse
root@box:~#
Can you help me understand what that command did, exactly? I'm a semi-newbie.
thanks
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
tjc
|
Posted: Thu Jul 21, 2005 10:06 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
The long asnswer...
Code: man find
man xargs
man grep
The short answer...
The find command searches the directory tree from one or more given starting points (here just /etc) and matches according to the arguments given, (here type is a normal file), finally we have it print the names of the objects that match.
The xargs command reads a list of "words" (here file names) and executes the specified command (here grep) with those words as arguments.
The grep command searches for a given regular expression pattern (here just the simple string "ps2") in the files it gets as arguments and prints any matches it finds.
So what we did in the end was search every normal file under the /etc directory for the string "ps2". There are some fine points that i've glossed over (using find -print0 and xargs -0, and grep -i), and other possible approaches, but this is about the most efficient way to do this.
OBTW - it looks like the only other file of concern under /etc is /etc/vga/libvga.config which means i'm forgetting something... Oh yeah, you may need to fix the link /dev/mouse
|
|
| Top |
|
|
|
shplad
|
Posted: Fri Jul 22, 2005 8:19 am |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
tjc:
Thanks once again. That was a great explanation. I'll try to remember that from now on.
So, in order to get the kbd. working at Linux level, do I just need to fix the /dev/mouse link?
Could you please explain what's wrong with that link.
Somewhat off-topic, I need to completely uninstall lirc and reinstall it. (see my other
thread about lirc not working properly in Myth) I knew to use the whereis or locate commands
to find all files containing the regexp "lirc", but I didn't know how to pass that info.
to a rm command. Based on what you wrote above, would it be okay for me to just:
Code: find / -type f | xargs -0 rm -i lirc*
or is there a better way to remove all traces of lirc?
Thanks again so much.
shplad
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
tjc
|
Posted: Fri Jul 22, 2005 8:45 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
That command won't do what you want. As a matter of fact it would do very bad things. Please read the man page and do some safe experiments first.
|
|
| Top |
|
|
|
linuxvirgin
|
Posted: Fri Jul 22, 2005 9:16 am |
|
|
Joined: Thu Jun 23, 2005 7:09 pm
Posts: 21
|
|
Can't you just slap a USB to PS2 converter on the wireless receiver end, and be done w/ it?
_________________
This is my first time...
|
|
| Top |
|
|
|
Liv2Cod
|
Posted: Fri Jul 22, 2005 10:29 am |
|
|
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location:
Silicon Valley, CA
|
|
The converter might be the best idea. In my case, I found I couldn't boot without a PS2 keyboard and mouse, even after initial installation.
A simple question: Why did you get a USB wireless keyboard when all anecdotal evidence suggests it won't work? Especially if you're not super-comfortable with Linux yet?
_________________ Do you code to live, or live to code? Search LinHES forum through Google
|
|
| Top |
|
|
|
shplad
|
Posted: Fri Jul 22, 2005 3:22 pm |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
|
Hmm..no offense meant guys, but I don't think Hoover Dam would've been built with that attitude.
I can't understand why so many of you guys bash Microsoft, and then turn around and ask
"Why did you buy that XYZ component if it isn't supported out of the box with Linux yet?".
Answer: It's an awesome keyboard. It would be pefect for Myth. Shouldn't someone
be the first to do it? So I may have bit off more than I can chew as a Linux newbie-I'm not sure yet. But someone
has to be the first, right?
As for a PS/2 to USB converter, I've been told that that won't work in this situation.
I'm not sure why. I'll consider it, but really only as a last resort, as my entertainment centre
door already has to stay open because the Mythbox case is so big. Another adapter
would send it right over the edge (literally.)
Anyhow, should we just write off all USB keyboards with Myth because they're not
supported just yet? If it's that difficult, I will find other ways, believe me. But I just refuse
to believe it's all that difficult for someone who knows what to do.
This thread reminds me of that song: "That's just the way it is". If there's reading material
for me to sift through, just send me to that, but I did ask politely at the beginning of this
thread not to simply receive answers like "Why did you buy that keyboard?".
Those answers, if you stop to think about, really aren't that helpful.
Thanks
shplad
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
tjc
|
Posted: Fri Jul 22, 2005 5:21 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Quote: Hmm..no offense meant guys, but I don't think Hoover Dam would've been built with that attitude. The "Six Companies" that built Hoover Dam (aka Boulder Dam, aka Black Canyon Dam) where some of the biggest, most advanced and cutting edge engineering firms of the day, and they had a great deal of existing know how, and plans for how they were going to overcome the various difficulties before construction ever started.
If you are (or aspire to being) a Linux kernel developer who wants to tackle the USB keyboard/mouse problems, I'd say go for it. However most of the folks around here who we help, just want to get something working, and are often loath to do so much as recompile a kernel or driver. As a result the recommendations that we make are conservative, like you'd probably make for an elderly relative who is a mild technophobe, or a neighbor who could never get their VCR clock to stop blinking 12:00 12:00 12:00 12:00 ... when you know that you're going to be providing tech support for them...
|
|
| Top |
|
|
|
shplad
|
Posted: Fri Jul 22, 2005 9:20 pm |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
Point noted. I probably shouldn't have said anything, as I knew it would start some
off-topic argument. I guess I'm just one of those guys who doesn't always like to take
the easiest possible route.
Anyone have any notes or anything they can point me to which might help?
Would it be worth my going back to Knoppix sites to have a look again?
Thanks
shplad
tjc wrote: Quote: Hmm..no offense meant guys, but I don't think Hoover Dam would've been built with that attitude. The "Six Companies" that built Hoover Dam (aka Boulder Dam, aka Black Canyon Dam) where some of the biggest, most advanced and cutting edge engineering firms of the day, and they had a great deal of existing know how, and plans for how they were going to overcome the various difficulties before construction ever started. If you are (or aspire to being) a Linux kernel developer who wants to tackle the USB keyboard/mouse problems, I'd say go for it. However most of the folks around here who we help, just want to get something working, and are often loath to do so much as recompile a kernel or driver. As a result the recommendations that we make are conservative, like you'd probably make for an elderly relative who is a mild technophobe, or a neighbor who could never get their VCR clock to stop blinking 12:00 12:00 12:00 12:00 ... when you know that you're going to be providing tech support for them...
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
Liv2Cod
|
Posted: Sat Jul 23, 2005 3:54 am |
|
|
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location:
Silicon Valley, CA
|
When building a Myth box, like any other great engineering project, it's a good idea to stick with tools, techniques, and materials that are known to work. Yes, you sometimes need to adopt new methods or materials where nothing fulfills you needs, but you minimize those excursions into the unknown.
Having a "cool" keyboard is irrelevant because 99.99% of the time the keyboard is in the bottom drawer. I use my keyboard so little that its batteries will die of shelf-life before they're used up. Your "cool" keyboard is RF. That means you can't use a simple programmable remote to talk to its receiver -- you'll have to add a separate IR receiver and use lirc to control your Myth box over a remote control.
Had you used the keyboard suggested on this forum, you could have programmed a remote to talk directly to the receiver of the keyboard, bypassing both the separate IR receiver AND lirc, which isn't needed because your remote issues the same keyboard commands Myth already understands. Plus, it would have been less than half the cost of your cool keyboard (not even counting your IR receiver) AND its rubber feet would not fall off in the first week. (according to the one review on the site you linked  _________________ Do you code to live, or live to code? Search LinHES forum through Google
|
|
| Top |
|
|
|
shplad
|
Posted: Sat Jul 23, 2005 1:21 pm |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
|
Anyone have any other ideas?
shplad
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
shplad
|
Posted: Sat Jul 23, 2005 10:15 pm |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
|
Okay, I tried just plugging in the keyboard before booting. I also had my normal,
wired keyboard plugged in, as I didn't know if Linux could work with two keyboards.
Apparently, it can.
However, I started having weird problems. When I had the BTC keyboard plugged in,
The Mythbox couldn't get an IP address. When I unplugged the BTC keyboard,
it could obtain one. Is that some kind of resource conflict? Should I just try plugging
in the keyboard after the machine has booted? Should I also try it without
the wired regular keyboard?
Thanks in advance.
shplad
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
ryanpatterson
|
Posted: Tue Aug 30, 2005 7:49 pm |
|
|
Joined: Fri Aug 26, 2005 9:54 pm
Posts: 617
|
shplad wrote: Anyhow, should we just write off all USB keyboards with Myth because they're not supported just yet?
I've been using my USB keyboard with mythtv since I first set it up (okay that is only three or four days). But the point is linux didn't have any problems detecting it. It is an Apple USB keyboard that came with a G4. Durring boot up when knoppmyth initialises the USB controller it says somthing about the keyboard. Let me see if I can find it. . .
excerpt from dmesg | grep USB
Code: usb 3-1.1: new full speed USB device using uhci_hcd and address 3
input: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB Keyboard] on usb-0000:00:1d.2-1.1
input: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB Keyboard] on usb-0000:00:1d.2-1.1
I quickly looked through my XF86Config-4 and cound't find anything that looked like it pertained to a USB keyboard as apposed to a ps/2 keybaord.
Ohh yea and I can access my motherboard's setup with the USB keybaord also.
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register