also take a look here
http://archives.free.net.ph/message/20090524.121638.72482e0d.en.html
--
Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’
https://bugs.launchpad.net/bugs/342902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As of today the problem still exists.
On fresh install of ubuntu 9.04 with network upgrade, 'module-assistant
auto-install loop-aes ' fails with the same build error.
linux-headers-2.6.28-11-generic
--
Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’
with CONFIG_BLK_DEV_LOOP=y does not even make sense to compile loop-aes with
module assistant: if the loop module is compiled inside the kernel we can't
replace it with an external one...
So the description of the loop-aes-source package is just wrong:
i totally agree with peter_22, i'm running with an encrypted root
filesystem and is already a problem that i have to re-run m-a to rebuild
the loop-aes module every kernel update, and now with
CONFIG_BLK_DEV_LOOP=y i will have to recompile the whole kernel, it's
not so human... i'm stuck at 8.10
May someone inform the ubuntu kernel team to re-set CONFIG_BLK_DEV_LOOP=m in
the kernel-configuration file?
Who is responsible for this mess? I know no sane reason to put loop inside the
kernel-image.
--
Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’
I've just had the same pair of problems, which I worked around as
follows:
* Build a custom kernel with CONFIG_BLK_DEV_LOOP=m as the only change
(following the instructions at
https://help.ubuntu.com/community/Kernel/Compile more or less).
* Install the custom linux-image and linux-headers
Yes, module-assistant loop-aes used to work in Intrepid. The change
from CONFIG_BLK_DEV_LOOP=m to CONFIG_BLK_DEV_LOOP=y is new in the Jaunty
kernel. Not sure why.
https://lists.ubuntu.com/archives/kernel-team/2008-December/003880.html
--
Build error: ‘struct bio’ has no member named
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for
modprobe loop I get Invalid module format (dmesg shows loop: exports
duplicate symbol loop_unregister_transfer (owned by kernel).
I guess this happens as the jaunty kernel has CONFIG_BLK_DEV_LOOP=y whereas
the
