** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed => Triaged
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-s
** Description changed:
Hi,
since hardy I'm getting the following error while booting:
[63.686712] padlock: VIA Padlock Hash Engine not detected.
modprobe: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
Yes, I can confirm this bug.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Confirmed
Ubuntu Hardy 8.04 beta
swap and /home encrypted. I receive this error after entering the first
passphrase for swap to be mounted. The error comes up, then onto prompting for
the /home passphrase.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-ge
Just curious if you've tried blacklisting the module.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bu
Should blacklisting be something everyone with an encrypted filesystem
installation be doing by default? If this is not needed, then it should
be blacklisted by default.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha
Add the line:
alias sha256 sha256_generic
to /etc/modprobe.d/aliases
This leads to the old (pre-hardy) behaviour, where sha256 is an alias for
sha256_generic and not for padlock-sha
In Gutsy, sha256 was an alias for sha256_generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/l
Blacklisting (as well as assigning sha256 alias to sha256_generic) works
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
http
What are the security implications of this issue (if we don't alias as
described above)? Is it likely that this will be fixed in Hardy soon
anyway?
In case one wonders why I'm asking these questions, I have been curious
since I started using Hardy about what happens when I implement a work-
around
It's not a bug - it's a feature.
Honestly, it just tries to load the module for hardware encryption support of a
VIA Epia - so users of a VIA Epia will have hardware acceleration for
encryption out of the box.
For everyone else, it will fail loading and no harm is done.
--
Warning during boot:
Workaround:
alias sha256 to sha256_generic
padlock-sha is for using the crypto-chip on via epia boards
The problem is:
padlock-sha is aliased to sha256 in hardy.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko):
Hi Sven,
could you please specifiy what you mean with aliasing the module? Just renaming
it?
greets
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You re
Still no solution ? I even tried to delete the module and without success. :/
I never had a Ubuntu version without issues!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
I'm using Ubuntu 8.04 with kernel 2.6.24-19-generic and fully encrypted
hard disk without LVM. For me none of the two workarounds worked!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://b
I confirm it with kernel 2.6.24-19-generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a member of U
Yes, I can confirm this bug too. Aliasing module helps.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a
I am using 8.04 with lvm and fully encrypted hard disk on two machines
and every now and then both error in the way described by the first
poster.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
But when this happens, ubuntu doesnt show the bootsplash anymore. So,
cant say thats a harm, but its a bug anyway.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/
Excuse me:
This happend to me (or I just recognized it) because I tried to setup a
swapfile for hibernation and instead of setting "resume=/dev/sda2" as a kernel
boot option mine was "resume=/swapfile". So, you can ignore my contribution.
--
Warning during boot: WARNING: Error inserting padlock
I confirm this bug on Ubuntu 8.10. I got error messages during boot.
It's not fixed :( . Also I can't find any workaround.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
Making a clean install (I haven't tried with an upgrade, sorry) solved
the problem for me (it happened in Hardy but seems to be solved in
Intrepid, at least in my machine, I use Intrepid 32 bits).
The only thing is that the graphical bootsplash turns to text mode just
after entering my passphrase,
Just because you don't see any relevant changes, does not mean that this
bug don't exist anymore. Sorry but people using 8.04 don't care for
fixes in 8.10 Alpha, they want it to be fixed in 8.04. Specially since
its LTS.
You can't tell somebody to upgrade the whole system to an alpha stage OS
Vers
I confirm this bug on Ubuntu 8.04. It has all worked since I made
recently some updates then I got this error message during boot. This
bug seemed to be reintroduced someway (regression)! Hoping that the
alias workaround will fix this.
--
Warning during boot: WARNING: Error inserting padlock_sha
I have thoroughly read this thread in an effort to find a solution to
this issue for my machine as well. I have discovered something that it
probably obvious to most but clearly wasn't to me. If you are intent on
aliasing sha265 to something like sha256_generic, but sure you do not
blacklist both
I have thoroughly read this thread in an effort to find a solution to
this issue for my machine as well. I have discovered something that it
probably obvious to most but clearly wasn't to me. If you are intent on
aliasing sha265 to something like sha256_generic, but sure you do not
blacklist both
And again the bug was fixed in Debian, sometimes i wonder why I'm still using
Ubuntu...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
ht
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
Importance: Unknown
Status: Unknown
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https:
** Changed in: linux (Debian)
Status: Unknown => Fix Released
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification beca
The Debain report comments this was fixed in cryptsetup=2:1.0.6-1
The current version of cryptsetup for the upcoming Intrepid Ibex release
is 2:1.0.6-2ubuntu7 so it would seem this should be resolved for
Intrepid Ibex 8.10. Regardless I've reassigned this to the cryptsetup
package. If anyone can
when comparing the current ubuntu and debian package, I don't see any
releavant changes in debian/initramfs/cryptroot-script .
I'm therefore closing this bug.
** Changed in: cryptsetup (Ubuntu)
Status: New => Fix Released
--
Warning during boot: WARNING: Error inserting padlock_sha
(/li
I'm using Ubuntu 8.04 with kernel 2.6.24-19-generic and fully encrypted
hard disk without LVM. For me none of the two workarounds worked!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://b
Yes, I can confirm this bug too. Aliasing module helps.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a
Still no solution ? I even tried to delete the module and without success. :/
I never had a Ubuntu version without issues!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
The Debain report comments this was fixed in cryptsetup=2:1.0.6-1
The current version of cryptsetup for the upcoming Intrepid Ibex release
is 2:1.0.6-2ubuntu7 so it would seem this should be resolved for
Intrepid Ibex 8.10. Regardless I've reassigned this to the cryptsetup
package. If anyone can
Just because you don't see any relevant changes, does not mean that this
bug don't exist anymore. Sorry but people using 8.04 don't care for
fixes in 8.10 Alpha, they want it to be fixed in 8.04. Specially since
its LTS.
You can't tell somebody to upgrade the whole system to an alpha stage OS
Vers
I have thoroughly read this thread in an effort to find a solution to
this issue for my machine as well. I have discovered something that it
probably obvious to most but clearly wasn't to me. If you are intent on
aliasing sha265 to something like sha256_generic, but sure you do not
blacklist both
I have thoroughly read this thread in an effort to find a solution to
this issue for my machine as well. I have discovered something that it
probably obvious to most but clearly wasn't to me. If you are intent on
aliasing sha265 to something like sha256_generic, but sure you do not
blacklist both
And again the bug was fixed in Debian, sometimes i wonder why I'm still using
Ubuntu...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
ht
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
Importance: Unknown
Status: Unknown
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https:
** Changed in: linux (Debian)
Status: Unknown => Fix Released
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification beca
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed => Triaged
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-s
Workaround:
alias sha256 to sha256_generic
padlock-sha is for using the crypto-chip on via epia boards
The problem is:
padlock-sha is aliased to sha256 in hardy.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko):
Hi Sven,
could you please specifiy what you mean with aliasing the module? Just renaming
it?
greets
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You re
Add the line:
alias sha256 sha256_generic
to /etc/modprobe.d/aliases
This leads to the old (pre-hardy) behaviour, where sha256 is an alias for
sha256_generic and not for padlock-sha
In Gutsy, sha256 was an alias for sha256_generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/l
Blacklisting (as well as assigning sha256 alias to sha256_generic) works
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
http
What are the security implications of this issue (if we don't alias as
described above)? Is it likely that this will be fixed in Hardy soon
anyway?
In case one wonders why I'm asking these questions, I have been curious
since I started using Hardy about what happens when I implement a work-
around
It's not a bug - it's a feature.
Honestly, it just tries to load the module for hardware encryption support of a
VIA Epia - so users of a VIA Epia will have hardware acceleration for
encryption out of the box.
For everyone else, it will fail loading and no harm is done.
--
Warning during boot:
** Description changed:
Hi,
since hardy I'm getting the following error while booting:
[63.686712] padlock: VIA Padlock Hash Engine not detected.
modprobe: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
Yes, I can confirm this bug.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Confirmed
Ubuntu Hardy 8.04 beta
swap and /home encrypted. I receive this error after entering the first
passphrase for swap to be mounted. The error comes up, then onto prompting for
the /home passphrase.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-ge
Just curious if you've tried blacklisting the module.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bu
Should blacklisting be something everyone with an encrypted filesystem
installation be doing by default? If this is not needed, then it should
be blacklisted by default.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha
I confirm this bug on Ubuntu 8.04. It has all worked since I made
recently some updates then I got this error message during boot. This
bug seemed to be reintroduced someway (regression)! Hoping that the
alias workaround will fix this.
--
Warning during boot: WARNING: Error inserting padlock_sha
when comparing the current ubuntu and debian package, I don't see any
releavant changes in debian/initramfs/cryptroot-script .
I'm therefore closing this bug.
** Changed in: cryptsetup (Ubuntu)
Status: New => Fix Released
--
Warning during boot: WARNING: Error inserting padlock_sha
(/li
I confirm this bug on Ubuntu 8.10. I got error messages during boot.
It's not fixed :( . Also I can't find any workaround.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
Making a clean install (I haven't tried with an upgrade, sorry) solved
the problem for me (it happened in Hardy but seems to be solved in
Intrepid, at least in my machine, I use Intrepid 32 bits).
The only thing is that the graphical bootsplash turns to text mode just
after entering my passphrase,
I am using 8.04 with lvm and fully encrypted hard disk on two machines
and every now and then both error in the way described by the first
poster.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
But when this happens, ubuntu doesnt show the bootsplash anymore. So,
cant say thats a harm, but its a bug anyway.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/
Excuse me:
This happend to me (or I just recognized it) because I tried to setup a
swapfile for hibernation and instead of setting "resume=/dev/sda2" as a kernel
boot option mine was "resume=/swapfile". So, you can ignore my contribution.
--
Warning during boot: WARNING: Error inserting padlock
I confirm it with kernel 2.6.24-19-generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a member of U
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you
Still no solution ? I even tried to delete the module and without success. :/
I never had a Ubuntu version without issues!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
I'm using Ubuntu 8.04 with kernel 2.6.24-19-generic and fully encrypted
hard disk without LVM. For me none of the two workarounds worked!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://b
I have thoroughly read this thread in an effort to find a solution to
this issue for my machine as well. I have discovered something that it
probably obvious to most but clearly wasn't to me. If you are intent on
aliasing sha265 to something like sha256_generic, but sure you do not
blacklist both
I have thoroughly read this thread in an effort to find a solution to
this issue for my machine as well. I have discovered something that it
probably obvious to most but clearly wasn't to me. If you are intent on
aliasing sha265 to something like sha256_generic, but sure you do not
blacklist both
And again the bug was fixed in Debian, sometimes i wonder why I'm still using
Ubuntu...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
ht
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
Importance: Unknown
Status: Unknown
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https:
** Changed in: linux (Debian)
Status: Unknown => Fix Released
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification beca
The Debain report comments this was fixed in cryptsetup=2:1.0.6-1
The current version of cryptsetup for the upcoming Intrepid Ibex release
is 2:1.0.6-2ubuntu7 so it would seem this should be resolved for
Intrepid Ibex 8.10. Regardless I've reassigned this to the cryptsetup
package. If anyone can
It's not a bug - it's a feature.
Honestly, it just tries to load the module for hardware encryption support of a
VIA Epia - so users of a VIA Epia will have hardware acceleration for
encryption out of the box.
For everyone else, it will fail loading and no harm is done.
--
Warning during boot:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed => Triaged
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-s
** Description changed:
Hi,
since hardy I'm getting the following error while booting:
[63.686712] padlock: VIA Padlock Hash Engine not detected.
modprobe: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
Yes, I can confirm this bug.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Confirmed
Ubuntu Hardy 8.04 beta
swap and /home encrypted. I receive this error after entering the first
passphrase for swap to be mounted. The error comes up, then onto prompting for
the /home passphrase.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-ge
Just curious if you've tried blacklisting the module.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bu
Should blacklisting be something everyone with an encrypted filesystem
installation be doing by default? If this is not needed, then it should
be blacklisted by default.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha
Workaround:
alias sha256 to sha256_generic
padlock-sha is for using the crypto-chip on via epia boards
The problem is:
padlock-sha is aliased to sha256 in hardy.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko):
Hi Sven,
could you please specifiy what you mean with aliasing the module? Just renaming
it?
greets
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You re
Add the line:
alias sha256 sha256_generic
to /etc/modprobe.d/aliases
This leads to the old (pre-hardy) behaviour, where sha256 is an alias for
sha256_generic and not for padlock-sha
In Gutsy, sha256 was an alias for sha256_generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/l
Blacklisting (as well as assigning sha256 alias to sha256_generic) works
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
http
What are the security implications of this issue (if we don't alias as
described above)? Is it likely that this will be fixed in Hardy soon
anyway?
In case one wonders why I'm asking these questions, I have been curious
since I started using Hardy about what happens when I implement a work-
around
Just because you don't see any relevant changes, does not mean that this
bug don't exist anymore. Sorry but people using 8.04 don't care for
fixes in 8.10 Alpha, they want it to be fixed in 8.04. Specially since
its LTS.
You can't tell somebody to upgrade the whole system to an alpha stage OS
Vers
I confirm this bug on Ubuntu 8.04. It has all worked since I made
recently some updates then I got this error message during boot. This
bug seemed to be reintroduced someway (regression)! Hoping that the
alias workaround will fix this.
--
Warning during boot: WARNING: Error inserting padlock_sha
when comparing the current ubuntu and debian package, I don't see any
releavant changes in debian/initramfs/cryptroot-script .
I'm therefore closing this bug.
** Changed in: cryptsetup (Ubuntu)
Status: New => Fix Released
--
Warning during boot: WARNING: Error inserting padlock_sha
(/li
Yes, I can confirm this bug too. Aliasing module helps.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a
I confirm it with kernel 2.6.24-19-generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/206129
You received this bug notification because you are a member of U
I am using 8.04 with lvm and fully encrypted hard disk on two machines
and every now and then both error in the way described by the first
poster.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
But when this happens, ubuntu doesnt show the bootsplash anymore. So,
cant say thats a harm, but its a bug anyway.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.net/bugs/
Excuse me:
This happend to me (or I just recognized it) because I tried to setup a
swapfile for hibernation and instead of setting "resume=/dev/sda2" as a kernel
boot option mine was "resume=/swapfile". So, you can ignore my contribution.
--
Warning during boot: WARNING: Error inserting padlock
I confirm this bug on Ubuntu 8.10. I got error messages during boot.
It's not fixed :( . Also I can't find any workaround.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
Making a clean install (I haven't tried with an upgrade, sorry) solved
the problem for me (it happened in Hardy but seems to be solved in
Intrepid, at least in my machine, I use Intrepid 32 bits).
The only thing is that the graphical bootsplash turns to text mode just
after entering my passphrase,
Still no solution ? I even tried to delete the module and without success. :/
I never had a Ubuntu version without issues!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
Still no solution ? I even tried to delete the module and without success. :/
I never had a Ubuntu version without issues!
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
https://bugs.launchpad.n
Just because you don't see any relevant changes, does not mean that this
bug don't exist anymore. Sorry but people using 8.04 don't care for
fixes in 8.10 Alpha, they want it to be fixed in 8.04. Specially since
its LTS.
You can't tell somebody to upgrade the whole system to an alpha stage OS
Vers
I confirm this bug on Ubuntu 8.04. It has all worked since I made
recently some updates then I got this error message during boot. This
bug seemed to be reintroduced someway (regression)! Hoping that the
alias workaround will fix this.
--
Warning during boot: WARNING: Error inserting padlock_sha
It's not a bug - it's a feature.
Honestly, it just tries to load the module for hardware encryption support of a
VIA Epia - so users of a VIA Epia will have hardware acceleration for
encryption out of the box.
For everyone else, it will fail loading and no harm is done.
--
Warning during boot:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed => Triaged
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-s
** Description changed:
Hi,
since hardy I'm getting the following error while booting:
[63.686712] padlock: VIA Padlock Hash Engine not detected.
modprobe: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
1 - 100 of 186 matches
Mail list logo
