Bug#781475: Jessie Installation-reports
On Sun, Mar 29, 2015 at 08:42:41PM +0100, A. J. Trim wrote:
> Package: installation-reports
>
> Boot method: DVD-RW
> Image version:
> https://www.debian.org/devel/debian-installer/News/2015/20150126
> (This was Jessie, RC1.)
> Date: Some time last week. (It is now Sun 29-Mar-2015.)
>
> Machine: Dell Inspiron 3000 (i.e. the current model) but with a
> second 1 TByte hard disk added. Installation attempt was onto this
> second disk.
> Processor: Intel Core i5-4460 CPU @ 3.20 GHz x 4.
> Memory: 7.8 GiByte
> Partitions: As set up automatically by the installer, using the
> encrypted LVM option.
>
> Output of lspci -knn (or lspci -nn): ???
>
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Initial boot: [O]
> Detect network card: [O]
> Configure network: [O]
> Detect CD: [O]
> Load installer modules: [O]
> Detect hard drives: [O]
> Partition hard drives: [O]
> Install base system: [O]
> Clock/timezone setup: [O]
> User/password setup: [O]
> Install tasks: [O]
> Install boot loader: [O] but not sure where. This is a UEFI boot
> system. Secure Boot had been disabled.
> Overall install: [O]
>
> Comments/Problems:
>
> System booted to a graphical grub menu. Windows 8.1 booted from here
> OK ( /dev/sda ).
> Linux started to boot ( /dev/sdb ).
> It asked for the LVM encryption password using command-line
> interface. The USB keyboard and USB mouse are "dead" at this point,
> so I was unable to enter the password. No progress was possible.
> I installed Linux Mint 17.1 at this point. This asks for the LVM
> encryption password via Plymouth GUI with keyboard and mouse "live".
> This works OK. This works with Secure Boot switched on.
>
> I recommend holding the release of Jessie until "live" keyboard and
> mouse can be provided at the time of the encryption password
> request.
Well I have no issue with USB keyboard input for the disk encryption
password with the jessie install I did a few weeks ago using the daily
build of the installer. So it is not broken for USB in general, perhaps
just in some specific cases.
Perhaps RC1 being so old had some bugs that are not present anymore
(my installer image was much newer than RC1).
--
Len Sorensen
Reply to: