← Back to team overview

kernel-packages team mailing list archive

[Bug 1502055] Re: Crypt password screen not responding

 

Piotr Piwonski, as per
http://www.toshiba.co.uk/innovation/download_bios.jsp?service=UK an
update to your computer's buggy and outdated BIOS is available (3.20).
If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the
information above is provided, then please mark this report Status
Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-3.20

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502055

Title:
  Crypt password screen not responding

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  During booting of system when the password screen for a encrypted device is presented there is no response.
  The screen is not accepting any input.
  I can switch to another screen using ctrl+alt+F# key and see blinking cursor.
  Switching back to ctrl+alt+F7 is showing message and all entered keys on screen.

  Rebooting by ctrl+alt+del or power button causes that the system boots
  to a text version of that screen where I can enter the password and
  system boots to OS.

  Not sure what could be gathered during this event to assist in
  identifying the problem since I have no possibility to get any logs
  and decrypt the disk :(

  Regards,
  Peter

  
  Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: 
  starting version 219

  The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible
  --- 
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ppiwonsk   1929 F.... pulseaudio
   /dev/snd/controlC1:  ppiwonsk   1929 F.... pulseaudio
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-06-03 (122 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: TOSHIBA TECRA Z40-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware                             1.143.3
  Tags:  vivid
  Uname: Linux 3.19.0-30-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.1A
  dmi.board.asset.tag: 0000000000
  dmi.board.name: TECRA Z40-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 0000000000
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z40-B
  dmi.product.version: PT45GE-06S03C0V
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+subscriptions