I am sorry to say but is is just one small single instance of many, that is the
big let down with
ubuntu, it always has been and always be.
Debian as in debian lenny for example is ROCK SOLID as with all debian
release's
Ubuntu is fine for the beginner but SHIT for anything more
alex
ps In this
Hello Jirka,
I gave up rebuilding the kernel without the loop module and started
using dm-crypt.
"cryptsetup -c aes-xts-plain -s 512" is similar featurewise to loop-aes.
--
Ákos
--
Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’
https://bugs.launchpad.net/bugs/342902
You recei
hello Jirka,
you are not supposed to make the loop.ko by hand, it is a kernel object and is
part of the kernel build.
so please remove the one you created.
--
Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’
https://bugs.launchpad.net/bugs/342902
You received this bug notificati
Hi,
I'm running Lucid with 2.6.32-24-generic kernel.
I have run into the same issue. I can create loop.ko but it does not
work:
# modprobe loop
FATAL: Error inserting loop (/lib/modules/2.6.32-24-generic/updates/loop.ko):
Invalid module format
Does anybody see the same on Lucid? Is there some
I get a different build error in karmic, but it's essentially the same
problem. An old version of the module was packaged with the new kernel.
The lucid repo has a version that compiles at least. Please upgrade the
version of this module to at least 3.2g.
I'd also like to suggest that someone pu
Beside of the kernel configuration issue (very unpleasant), there is still the
compilation error (the original bug), even in karmic! In order to get loop-aes
to work i need to manually download v3.2h from sourceforge...
I understand that you refuse to fix the kernel configuration thing (or even
the compilation test went ok, but as stated previously (i should have
read closer) the module won't load because of duplicate symbols.
as per comment #10 and 10 seconds boot goal for karmic that change would
need a big sponsor to get done.
I've reopened the Linux task in bug #372781
sorry for th
hmmm, it seems that a pretty similar bug was solved upstream in latest
loop-aes-source available in karmic at this time. So if the reporters
can test the package
loop-aes-source | 3.2f-1 | karmic/universe | all
and this solves the problem, a backport can be requested.
http://bugs.debian.or
According to last comment from notch-1, links and irc log, i must mark
this task as won't fix in the meantime (until loop-aes get's
upstreamed).
However i'm reopening loop-aes-source in order to look a path to compile
this module without a full recompilation.
** Changed in: linux (Ubuntu)
ok, i think i see the real problem now, after the post to the mailing list,
this bug report and a month of unanswered questions on ircnode i finally had
this conversation on #ubuntu-kernel (see attachment).
Their point is that since the loop-aes module is not in the upstream, is not a
problem (a
Looks like the problem is in the kernel configuration rather than in
loop-aes-source. Modifying accordingly now.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: loop-aes-source (Ubuntu)
Status: New => Invalid
--
Build error: ‘struct bio’ has no
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
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:
http://packages.ubuntu.com/jaunty/loop-aes
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’
https://bugs.launchpad.net/
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 ri
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’
https://bugs.launchpad.n
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 pack
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 ‘bi_hw_fron
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
19 matches
Mail list logo
