From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Lost Insert After Upgrade
Date: Thu, 16 Jun 2005 08:35:11 -0500 [thread overview]
Message-ID: <20050616133511.GB24002@blackbox> (raw)
In-Reply-To: <Pine.BSF.4.63.0506160004000.35011@freire2.furyyjbeyq.arg>
Hi.
First: Sarge is now stable It went stable last week. If you did a
dist-upgrade after an apt-get update, you should have been upgraded to
Sarge.
The Sarge speakup kernel is now 2.4.27. It uses a version of speakup
2.0 from CVS. You might consider upgrading to the new kernel. Several
changes in speakup 2.0 are worth the upgrade. One in particular is how
speakup handles keymaps. I would upgrade the kernel-image package
before doing anything else.
The fact you saw 250 packages upgraded says you were upgraded to Sarge.
Hope this helps.
Kenny
On Thu, Jun 16, 2005 at 12:13:34AM -0500, Luke Davis wrote:
> 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
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Luke Davis
` Kenny Hitt [this message]
` Luke Davis
` Kenny Hitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050616133511.GB24002@blackbox \
--to=kenny@hittsjunk.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).