LinHES Forums
http://forum.linhes.org/

System nonresponsive to Keyboard after install and reboot.
http://forum.linhes.org/viewtopic.php?f=11&t=20265
Page 1 of 2

Author:  gatorback [ Sat Aug 29, 2009 3:17 pm ]
Post subject:  System nonresponsive to Keyboard after install and reboot.

Unsure if this is install issue or a configuration issue:

Issue: LINHES (system details in signature) Installation sequence up to reboot and the menu does not respond to mouse \ keyboard (both USB if it makes any difference). No PS2 ports. During the boot, system responded to F2 verbose command.

The clock in the bottom right corner advances properly and there are 6 menu choices

1) General
2) Capture Cards
3) Video Sources
4) input connections
5) Channel Editor
6) Storage Directories.

My forum search for the Optiplex 760 was null. Any constructive advice to diagnose and correct is appreciated.

Author:  mihanson [ Sat Aug 29, 2009 3:38 pm ]
Post subject: 

Try adding this to your /etc/X11/xorg.conf:

Code:
Section "ServerFlags"
      Option "AutoAddDevices" "False"
EndSection

Author:  gatorback [ Sat Aug 29, 2009 4:16 pm ]
Post subject:  What does the line do?

I opened up the xorg.conf file and the first three lines are:

Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection

I was able to SSH into the system from another box, however, the LinHES keyboard is nonresponsive.

LinHES did not detect the USB keyboard \USB Mouse:

Code:
Section "ServerLayout"
        Identifier     "Xorg Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection

Section "ServerFlags"
        Option "AllowMouseOpenFail"  "true"

EndSection



Is there anyway to drill down to root cause of the nonresponsvie behavior? My gut tells me that a change in the Server Layout with regard to the USB Mouse and USB Keyboard will solve the problem, however, I am uncertain of the syntax.

Tried:
Code:
      InputDevice    "USB Keyboard0" "CoreKeyboard"
      InputDevice    "USB Mouse" "CorePointer"
Made things worse: didn't arrive at the menu described above. Reinstalling.

Author:  mihanson [ Sat Aug 29, 2009 6:13 pm ]
Post subject: 

Check here: http://wiki.archlinux.org/index.php/Xorg_input_hotplugging#FAQ.2FTroubleshooting and here: http://wiki.archlinux.org/index.php/Xorg

You can also try to comment out (with #) or remove all lines of the "Server Flags" section to see if that helps.

Author:  bobmyth [ Sun Aug 30, 2009 7:30 pm ]
Post subject: 

I was having a similar problem and added this to my xorg.conf file:
Code:
Section "ServerFlags"
        Option "AllowEmptyInput" "false"
EndSection

Author:  richwine4 [ Sat Sep 05, 2009 3:13 pm ]
Post subject: 

Has anyone solved this problem yet? I'm having a very similar keyboard issue. Had a fully-working dedicated backend and decided to uncheck the "run the frontend" option because I didn't need it.

Then I realized I needed it (to do some archiving to a DVD) so I ran add_service.sh frontend to get it back. (Is this the correct method?)

Since then the keyboard has been entirely unresponsive in X. I tried the server flags the previous posts mentioned, I tried upgrading, I tried running X -configure, I tried different keyboards. Nothing worked.

Any ideas?

Author:  gatorback [ Wed Sep 09, 2009 3:38 pm ]
Post subject: 

@ bobmyth:


I tried:
Code:
Option "AllowEmptyInput" "false"


The key board is nonresponsive. Is there any kind of diagnostic procedure I can perform to provide information that leads to issue resolution?

Author:  bobmyth [ Wed Sep 09, 2009 9:10 pm ]
Post subject: 

Please review your log file (/var/log/Xorg.0.log) or make it available somewhere for review. Please note my file is over 2500 lines so this forum may not be the best place to put it.

Author:  gatorback [ Wed Nov 11, 2009 11:12 am ]
Post subject: 

I psftp-ed Xorg.0.log and posted it here.

I am hoping to gain some insight as to be able to detect the issue, analyze and correct.

Your insight and skill is highly appreciated.

Author:  bpmcgee [ Wed Nov 11, 2009 1:50 pm ]
Post subject: 

Gatorback,

I found the MythVantage X configuration stuff kinda flakey. I used the standard X configuration method (I think Xorg --configure) to create a config file that I used to pirate the bits and pieces I needed to get everything working.

B

Author:  gatorback [ Wed Nov 11, 2009 2:13 pm ]
Post subject: 

bpmcgee wrote:
Gatorback,

I found the MythVantage X configuration stuff kinda flakey. I used the standard X configuration method (I think Xorg --configure) to create a config file that I used to pirate the bits and pieces I needed to get everything working.

B


Please advise path forward to your suggestion. What exactly would I need to do (procedure?). Thanks!

Author:  bpmcgee [ Wed Nov 11, 2009 3:57 pm ]
Post subject: 

I'm sorry, I can't do it from memory, so I can't walk you through an itemized list of steps. Here's what I remember:

1) "xorg" is the X server -- what actually does the window displaying.

2) When you run "xorg -configure" while logged in as root, it attempts to build a configuration file. When it does this, it tells you the name of the file that it's creating. xorg.conf.test or something like that.

3) To test that file, you would run "xorg -config <file name>"

4) If the keyboard and mouse work, you can take the relevant InputDevice sections from xorg.conf.test and paste them into the xorg.conf that was created by MythVantage.

Sorry that's the best that I can do. I'm not a guru, just a grunt who's slogged through this once in the past. I'm sure the other people here will have much more sage advice than me -- advice I recommend you take.

B

Author:  mitmwp [ Mon Nov 23, 2009 11:30 am ]
Post subject: 

I've got the exact same issue. This is a vanilla LinHES install on empty hard drive.

I made a change to xorg.conf, changing from Driver "fbdev" to Driver "xxx" so that X failed on the reboot. I then changed driver back to "fbdev" and did a startx. It started and keyboard input was fine. From the xterm, I ran mythtv-setup and the keyboard is responding (like it should after the initial install).

Not sure what this tells us, however, there is something going on in the default startup scripts. Anyone got any ideas... This seems strange.


GIGABYTE GA-MA785GM-US2H
AMD PH II X2 550 3.1G
CORSAIR MEM 2Gx2
WD SATA2 WD1001FALS (Black)

Author:  mitmwp [ Fri Dec 04, 2009 1:20 pm ]
Post subject: 

Solved my issue.

I had a Hauppauge 1600 in one of the PCI slots. When I removed the card, everything responded normally. After configuring Myth, I reinstalled the 1600 card and everything now works (including both digital and analog sides of the 1600).


GIGABYTE GA-MA785GM-US2H
AMD PH II X2 550 3.1G
CORSAIR MEM 2Gx2
WD SATA2 WD1001FALS (Black)
Hauppauge 1600
Hauppauge 150

Author:  gatorback [ Fri Jan 22, 2010 11:04 am ]
Post subject:  Verified that Hauppauge PVR500 is good & works

Not sure if this is a bug that needs to be reported. Maybe one of the more senior members or even cecil should weigh in.

I put together a new machine this month (see signature). One of my objectives was to determine if the PVR500 card used at the beginning of this thread works.

That being said, I installed R5.5 and was able to verify the PVR500 (it was able to record Cable-TV and I was able to play it back).

Initially, I tried R6 with the hope this problem went away with new hardware, however, no such luck. I installed R6 w/o the PVR500 and then installed the PVR500 only to have the PS2 keyboard freeze up again.

Maybe in the future I will try mitmwp's procedure with R6.

Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/