On Tue, Sep 13, 2005 at 03:42:39PM +0200, Frans Pop wrote:
> On Tuesday 13 September 2005 12:07, Emmanuel Kasprzyk wrote:
> > I encountered also this problem while migrating from the
> > kernel-image-2.4.19-sun4u (3.0 ) to kernel-image-2.6.8-2-sparc64, on a
> > un ULTRA 10 with a Type5 keyboard. If you do dpkg-reconfigure
> > console-data, and then select "Keep kernel keymap" the keyboard will
> > then work correctly on 2.4 AND 2.6 from your next reboot on. This
> > kernel keymap works fine for type qwerty, I guessed the problem will be
> > still here for azerty.
> >
> > It seems that the keymap definitions loaded when you select keymap from
> > arch list in "dpkg-reconfigure console-data" is broken with kernel 2.6
> > I have no idea if this is a bug from the kernel, or if the keymaps have
> > to be updated somehow.
> 
> This is not a bug, but a result of a change in the kernel's input/output 
> layer. The Sarge release notes [1] have information on this change.
> 
> [1]http://www.debian.org/releases/stable/sparc/release-notes/ch-information.en.html#s-upgrade-to-2.6

Should this bug be closed, or is the originally reported problem
different?

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to