-5 assembly which is luks encrypted. It contains an lvm pv/vg
with all my filesystems (mostly xfs) in it.
I'm not sure how much pursuing this is worth the effort. Perhaps recording the workaround
(load the modules in dracut) in case someone else hits the problem is sufficient.
Dick
--
D
On 5/20/22 11:38 PM, Thomas Lange wrote:
Can you please provide the output of
# lsinitrd /boot/initrd.img-..
on the old and new system?
PLease also create a new temp initrd on the new system to see the log
of the creation process:
# dracut -v /tmp/tempfile
I attach tar archive:
1) co
On 5/18/22 8:43 AM, Thomas Lange wrote:
Which dracut version are you using?
051-1 according to aptitude.
[ I realised after I'd posted this report that the issue was probably with dracut rather
than the kernel. Apologies for any annoyance caused. ]
--
Dick Middleton d...@lingbrae.com
Package: linux-image-amd64
Version: 5.10.106-1
Severity: serious
Justification: 4
Dear Maintainer,
Upgrading Stable to Bullseye no longer can access encrypted root file system.
Prevents booting.
Needed to add crypto modules ecb and ccm (although I'm not sure which or both
were needed) to init
I think this might be because libgpgme11 v1.2 depended on gnupg whereas
libgpgme11 v1.4 depends on gnupg2.
mandos-client depends on gnupg.
In initrd only gnupg files are included whereas at console both gnupg and
gnupg2 files are available.
Needs to be proved!
Dick
--
Dick Middleton
d
Package: motion
Version: 3.2.12-3.2
Severity: serious
Justification: 4
Dear Maintainer,
* What led up to the situation?
upgrade from squeeze to wheezy
* What exactly did you do (or not do) that was effective (or
ineffective)?
no longer connects to mysql
reports unknown config opti
FWIW I get these exact symptoms with 0.7.1-2 on my eeePC BUT only with
plain encrypt=y. With RSA encryption it works OK.
kernel 2.6.26-8
Dick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
But it doesn't segfault if -d or -u options are set. It's that damn duck!
It says memory usage is 66% - duck is near top - perhaps about to go
upside-down. If I reduce memory usage then it starts OK and doesn't seem to die
when I increase memory use again. Not very consistent so hard to be s
Package: wmbubble
Version: 1.46-1+b1
Severity: grave
Justification: renders package unusable
Upgrade [UPGRADE] wmbubble 1.46-1 -> 1.46-1+b1
was OK now segfaults shortly after starting.
No other info I can find.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT poli
9 matches
Mail list logo
