Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
Re: [SLE] Linux and cary keyboards
Here is the InputDevice sections from our "xorg.conf" file for what it's worth:
Section "InputDevice"
Driver "kbd"
Identifier "Keyboard[0]"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "pc104"
Option "XkbRules" "xfree86"
EndSection


Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "5"
Option "Device" "/dev/input/mice"
Option "Name" "ImPS/2 Generic Wheel Mouse"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection

We've played around with the device assignment trying "/dev/null" and "/dev/input/mouse0" among other things we've tried. So far with no success.

There is also this section:

Section "ServerFlags"
Option "AllowMouseOpenFail"
EndSection

We did a google on AllowMouseOpenFail and found lots of hits indicating that this caused the exact problem we are seeing in XFree86. The postings all said to add "true" to the end of the option line. That did nothing. Not surprising since we are running xorg and not XFree86.

This problem is causing us to order a bunch of mice just in case there is no other solution! Any help will be much appreciated!

Rick Schaeffer(rschaeff@xxxxxxxxxxx)

----- Original Message ----- From: "Art Fore" <art.fore@xxxxxxxxxxx>
To: <suse-linux-e@xxxxxxxx>
Sent: Thursday, April 13, 2006 6:40 PM
Subject: Re: [SLE] Linux and cary keyboards


On Thu, 2006-04-13 at 14:17 -0700, Rick Schaeffer wrote:
I work for a local theme park. We are converting all of the park's POS systems to linux and have run into an unexpected snag. The pos application runs under X-windows and seemed to work fine until we powered up a system with a "Cary" keyboard attached (this is a special retail keyboard with a large membrane keypad that can be programmed so that each membrane key returns a unique key sequence). The odd thing is that the OS starts up fine but when the application (in X-windows) starts up, the keyboard is not functional unless a mouse is attached to the computer. No keystrokes reach the application at all. If we boot up with a mouse attached, the keyboard works fine. If we boot up with no mouse but with the standard windows keyboard attached, the keyboard works fine! It's only if we come up with no mouse and a Cary keyboard attached that we run into the problem. Is there a solution to this problem? Perhaps something we need to do at start-up time to get the keyboard t
o work?

The Cary keyboard is programmable and has ports to which you can connect other peripherals. For instance, a cash drawer is one peripheral for the keyboard. We discovered that we had to change the keyboard's software to NOT access the port for anything except the cash drawer in order to get it to work at all. Once we got past that problem, the keyboard seemed to work fine. As I mentioned above, the problem only occurs when the system boots up WITHOUT a mouse attached and WITH a Cary keyboard attached.

This keyboard is particularly important at the fast-food outlets in the park where the membrane keys are programmed for the different food items sold (ie: 1 button for "Hamburger", another for "Fries" and-so-on). We are in contact with NRT (Cary's parent company) but are rapidly running out of time (the park opens for the season at the end of this month). Please respond directly to rschaeff@xxxxxxxxxxx if you have any experience with this type of keyboard. I will check the newsgroup but a direct reply is quicker.

Rick Schaeffer (rschaeff@xxxxxxxxxxx)

What does the /etc/X11/XF86config (or xorg.conf, depending on version of
linux) have for the "InputDevice" section for the "mouse" driver look
like? Maybe just need to remark it out.

Why not post the above mentioned file so someone can look at it?

Art


--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx






< Previous Next >