I don't think the issue is directly related to PM, but when we released the source, PM functionally was limited.
Since I'm not able to recreate, I want to rule out any possible relation, even the slightest chance, regardless for now we really would like everyone to run without PM ( i.e. PM disabled).
Thanks,
Seif
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of dann frazier
Sent: Tuesday, May 22, 2012 10:52 PM
To: Seif Mazareeb
Subject: [Bug 940025] Re: [public] armadaxp net installer fails to properly encrypt disks (dm-crypt)
This certainly looks like a userspace issue to me - I wouldn't expect power management to affect this (unless Seif has a reason to believe otherwise). From what I can tell, it looks like plymouthd maybe prompting for a password on tty7 instead of ttyS0. What I don't understand is why this would happen on armadaxp and not on x86. A plymouth expert might be helpful here.
--
You received this bug notification because you are a member of The Eilt team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/940025
Title:
[public] armadaxp net installer fails to properly encrypt disks (dm-
crypt)
Status in The Eilt project:
Confirmed
Status in “debian-installer-netboot-images” package in Ubuntu:
Confirmed
Summary: armadaxp net installer fails to properly encrypt disks (dm-
crypt)
Steps to Reproduce:
1a) run net installer
1b) choose Guided - use entire disk and setup encrypted LVM
1c) complete crypt setup and password and reboot
2a) run net installer
2b) choose Manual partitioning
2c) configure an encrypted partition (physical volume for encryption)
2d) choose configure encrypted volumes and then activate encrypted volumes
Expected result: system boots and requests unlock passphrase
Actual result: 1) after install, boot hangs after udev, 2) during
install, activate encrypted volumes fails claiming no dm-crypt devices
found
All,
I don't think the issue is directly related to PM, but when we released the source, PM functionally was limited.
Since I'm not able to recreate, I want to rule out any possible relation, even the slightest chance, regardless for now we really would like everyone to run without PM ( i.e. PM disabled).
Thanks,
Seif
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of dann frazier
Sent: Tuesday, May 22, 2012 10:52 PM
To: Seif Mazareeb
Subject: [Bug 940025] Re: [public] armadaxp net installer fails to properly encrypt disks (dm-crypt)
This certainly looks like a userspace issue to me - I wouldn't expect power management to affect this (unless Seif has a reason to believe otherwise). From what I can tell, it looks like plymouthd maybe prompting for a password on tty7 instead of ttyS0. What I don't understand is why this would happen on armadaxp and not on x86. A plymouth expert might be helpful here.
-- /bugs.launchpad .net/bugs/ 940025
You received this bug notification because you are a member of The Eilt team, which is subscribed to the bug report.
https:/
Title:
[public] armadaxp net installer fails to properly encrypt disks (dm-
crypt)
Status in The Eilt project: installer- netboot- images” package in Ubuntu:
Confirmed
Status in “debian-
Confirmed
Bug description: ports.ubuntu. com/ubuntu- ports/dists/ precise/ main/installer- armhf/20101020u buntu113/ images/ armadaxp/ uInitrd (with 1500.3 uImage)
Build Version/Date: http://
Environment used for testing: armadaxp1
Summary: armadaxp net installer fails to properly encrypt disks (dm-
crypt)
Steps to Reproduce:
1a) run net installer
1b) choose Guided - use entire disk and setup encrypted LVM
1c) complete crypt setup and password and reboot
2a) run net installer
2b) choose Manual partitioning
2c) configure an encrypted partition (physical volume for encryption)
2d) choose configure encrypted volumes and then activate encrypted volumes
Expected result: system boots and requests unlock passphrase
Actual result: 1) after install, boot hangs after udev, 2) during
install, activate encrypted volumes fails claiming no dm-crypt devices
found
To manage notifications about this bug go to: /bugs.launchpad .net/eilt/ +bug/940025/ +subscriptions
https:/