Lost Insert After Upgrade

Lost Insert After Upgrade

[Luke Davis]

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

Re: Lost Insert After Upgrade

[Kenny Hitt]

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

Re: Lost Insert After Upgrade

[Kenny Hitt]

Hi.

Just a followup.  If you didn't use dist-upgrade you should.  Just using
upgrade won't work.

The correct order for now is:

Go read the release notes for Sarge Do this now!!! Do not pass go do not
wait, go read and follow instructions.
After reading, follow there advice on upgrading.  Don't ignore this.
If you do, you can enjoy playing with the pieces. 
Since you appear to not have known this
already, you get to have fun with apt-get, aptitude, and dselect.

If you don't subscribe to any other Debian lists, subscribe to Debian
news, debian security announce, and debian devel announce.  

          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

Re: Lost Insert After Upgrade

[Luke Davis]

On Thu, 16 Jun 2005, Kenny Hitt wrote:

> 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 fact you saw 250 packages upgraded says you were upgraded to Sarge.

Yes, this is what I had assumed, even though my apt sources were still 
pointing to "woody stable" for both debian org, and "woody" on backports.

I recognized that this is what happened, but only after the fact.  It was 
about 250 MB worth of packages, not 250 packages; my mis-typage in the 
previous message.

Thanks

Luke