From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sun, 25 Jul 2004 11:31:02 +0300 From: Michael Shigorin To: community-en@altlinux.org Subject: Re: [Comm-en] ALT Linux's Junior 2.2 Keyboard Lockup Message-ID: <20040725083102.GA31335@osdn.org.ua> Mail-Followup-To: community-en@altlinux.org References: <20040724180703.810224BDA8@ws1-1.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040724180703.810224BDA8@ws1-1.us4.outblaze.com> User-Agent: Mutt/1.4.2.1i X-BeenThere: community-en@altlinux.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: community-en@altlinux.org List-Id: "Mailing list for ALT Linux users \(in English only\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 08:31:04 -0000 Archived-At: List-Archive: List-Post: On Sat, Jul 24, 2004 at 11:07:03AM -0700, Matthew Cuddy wrote: > The mouse still worked, allowing me to select a user, but the > keyboard didn't work, so I couldn't log in. Seen the message that gpm may cause such behaviour facing mouse problems. While I can't recall objective reasons for that other than serial mouse and a PS/2 keyboard _with_ a faulty PS/2 controller which will freeze the keyboard when trying to access absent PS/2 mouse (it's not uncommon hardware glitch), this may help: * boot into single mode (add "single" to "linux-up" line in bootloader) * after logging in with your root password, enter: chkconfig gpm off or even (if you don't use mouse in console mode): rpm -e gpm * type "exit" to get into normal runlevel. -- ---- WBR, Michael Shigorin ------ Linux.Kiev http://www.linux.kiev.ua/