RE: [SLE] How to make SuSE 9.1 NOT search for a keyboard, but just activate one?
Pieter Hulshoff wrote :
Hello all,
I have a non-standard keyboard (an arcade controller with a keyboard mapper) that doesn't let its presence be known. If I have a keyboard hooked up to it, SuSE 9.1 has no problem activating it, and it stays active even after I disconnect the keyboard from the arcade controller.
If however I don't have a keyboard hooked up to it, the system doesn't respond to any of its keys.
It did work fine in SuSE 8.2 however, which leads me to believe there've been some changes in the boot sequence that stop it from working now (it works neither in X nor in console windows).
A possible source for this problem might be /etc/rc.d/kbd. Does anyone know how I can make SuSE just accept a keyboard in stead of probing for one?
Regards,
Pieter Hulshoff
Hi Pieter, I don't have 9.1. However a similar question was aked last December with regard to 8.1. The answers included: If you want to disable the scan at boot-up, just issue an 'insserv -r hwscan'. And: go to YAST --> SYSTEM --> Runlevel editor and disable "hardware scan" And: Look at script in: /etc/init.d/hwscan. See: http://lists.suse.com/archive/suse-linux-e/2003-Dec/0337.html http://lists.suse.com/archive/suse-linux-e/2003-Dec/0338.html http://lists.suse.com/archive/suse-linux-e/2003-Dec/0339.html Hope this helps, Gar -- PS. Needless to say, you need to include your keyboard definition in /etc/X11/XF86Config or similar. -- __________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp
On Tuesday 11 May 2004 23:56, GarUlbricht7@netscape.net wrote:
A possible source for this problem might be /etc/rc.d/kbd. Does anyone know how I can make SuSE just accept a keyboard in stead of probing for one? If you want to disable the scan at boot-up, just issue an 'insserv -r hwscan'.
The problem wasn't so much in the hwscan as it was in the non-standardness of the keyboardmapper of the arcade controller. I just managed to get it to work late last night by using the i8042.dumbkbd kernel parameter (thanx to a tip on the xmame mailinglist). Regards, Pieter Hulshoff
participants (2)
-
GarUlbricht7@netscape.net
-
Pieter Hulshoff