From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ip15.shellworld.net ([64.49.204.174] helo=server2.shellworld.net ident=root) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1Dimh5-0006PU-00 for ; Thu, 16 Jun 2005 01:13:35 -0400 Received: from server2.shellworld.net (ldavis@localhost [127.0.0.1]) by server2.shellworld.net (8.12.10/8.12.8) with ESMTP id j5G5DYVi064851 for ; Thu, 16 Jun 2005 05:13:34 GMT (envelope-from ldavis@shellworld.net) Received: from localhost (ldavis@localhost) by server2.shellworld.net (8.12.10/8.12.8/Submit) with ESMTP id j5G5DYuG064848 for ; Thu, 16 Jun 2005 00:13:34 -0500 (CDT) X-Authentication-Warning: server2.shellworld.net: ldavis owned process doing -bs Date: Thu, 16 Jun 2005 00:13:34 -0500 (CDT) From: Luke Davis To: Speakup@braille.uwo.ca Message-ID: Organization: "Tacticus Communications, Inc." MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Lost Insert After Upgrade X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 05:13:35 -0000 Kernel: 2.4.24 Speakup: 1.5 OS: Debian Woody Stable Linux I recently upgraded about 250 packages, from woody stable, to what is probably mostly sarge. In the middle of my upgrade, using standard debian upgrades and some stuff from backports (which I guess are normalized now), the insert key on the numpad stopped working. The machine had been up for almost 60 days, so I rebooted, thinking it would fix the problem. It didn't, so I set the console-data package to "kernel" keyboard map. Rebooted, and while it still didn't work, I found something interesting: until about half way through the boot process, it did work! I could read rest of screen, move to top of screen, move to far left, etc., until just before the hardware clock update. Can't tell exactly where it stops working, however. I do notice a series of "null symbol found" errors. They do not seem to show up in any logs, and I can't tell where in the boot process they occur (what precedes them scrolls off the screen). If I try to use loadkeys on the map included with speakup, I get errors, and it won't load. Anyone with an idea on how to fix this, before I start trying to fix the keymap manually, if that's even what is wrong? Thanks Luke