Processing control commands:
> tag -1 wheezy wontfix
Bug #689851 [initramfs-tools] initramfs-tools: Wrong keymap at boot while
prompting for the passphrase
Added tag(s) wheezy and wontfix.
> affects -1 console-tools
Bug #689851 [initramfs-tools] initramfs-tools: Wrong keymap at boot while
prompt
Control: tag -1 wheezy wontfix
Control: affects -1 console-tools
Control: notfound -1 0.107
Control: found -1 0.108
On Thu, 28 Nov 2013 11:37:54 +0100 Ondřej Vodáček
wrote:
> Hello,
>
> I have upgraded initramfs-tools to version 0.115 and it looks like
its fixed. Same keyboard layout like in ver
Hello,
I have upgraded initramfs-tools to version 0.115 and it looks like its fixed.
Same keyboard layout like in version 0.107.
Regards
Ondřej Vodáček
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
On Wed, Oct 10, 2012 at 09:32:21AM +0200, Ondřej Vodáček wrote:
>
> >Please try the command
> >
> >loadkeys /etc/boottime.kmap.gz
>
> the output is:
> /bin/sh: loadkeys: not found
Good! It seems we've found the culprit.
Anton Zinoviev
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.de
Dne 10.10.2012 08:16, Anton Zinoviev napsal(a):
On Tue, Oct 09, 2012, Jean-Luc Coulon wrote:
Please send us the file /tmp/i/etc/boottime.kmap.gz
Attached
Thanks. Well, as far as I can see this is a correct keymap. Se we have
to figure out for what reason it hasn't been activated. It is
On Tue, Oct 09, 2012, Jean-Luc Coulon wrote:
>
> > Please send us the file /tmp/i/etc/boottime.kmap.gz
>
> Attached
Thanks. Well, as far as I can see this is a correct keymap. Se we have
to figure out for what reason it hasn't been activated. It is not an
Unicode keymap, it is for ISO 8859-1
Hello,
I have encountered the same problem after upgrading from 0.107 to 0.108. I have
my root and home partitions on lvm on an encrypted device. It is definitely a
keymap problem. After 3 unsuccessfully tries typing the passphrase a shell
(busybox?) appeared and I was able to figure out, that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 08/10/2012 17:06, Anton Zinoviev a écrit :
> On Mon, Oct 08, 2012 at 02:59:17PM +0200, Michael Prokop wrote:
>> [Cc-ing Anton as being maintainer of setupcon]
>>
>>> Calling hook keymap
>>> Adding binary /bin/loadkeys
>>> Adding library /lib/libcfon
On Mon, Oct 08, 2012 at 02:59:17PM +0200, Michael Prokop wrote:
> [Cc-ing Anton as being maintainer of setupcon]
>
> > Calling hook keymap
> > Adding binary /bin/loadkeys
> > Adding library /lib/libcfont.so.0
> > Adding library /lib/libctutils.so.0
> > Adding library /lib/libconsole.so.0
> > WARNI
[Cc-ing Anton as being maintainer of setupcon]
* Jean-Luc Coulon [Mon Oct 08, 2012 at 01:50:31PM +0200]:
> Le 08/10/2012 08:15, Michael Prokop a écrit :
> > Please provide output of:
> > update-initramfs -u -k $(uname -r) -v
> Output attached
[...]
> Calling hook keymap
> Adding binary /bin/lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 08/10/2012 08:15, Michael Prokop a écrit :
> Please provide output of:
> update-initramfs -u -k $(uname -r) -v
Output attached
Regards
Jean-Luc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla
* Jean-Luc Coulon (f5ibh) [Sun Oct 07, 2012 at 09:55:54AM +0200]:
> I've some encrypted filesystems over lvm.
> After upgrading from 0.107 to 0.108, it refuses my passphrase at boot.
> I suppose it is related to the keymap.
> I've reverted to 0.107 at that fixed the problem.
> I've then upgraded
Package: initramfs-tools
Version: 0.107
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've some encrypted filesystems over lvm.
After upgrading from 0.107 to 0.108, it refuses my passphrase at boot.
I suppose it is related to the keymap.
I've reverted to 0.107 at that fixed
13 matches
Mail list logo
