qwerty12 is my first tester of the easy-chroot stuff in Fremantle, and he noticed the missing dm-loop.

I would like someone to upload the dm-loop kernel modules to Extras for both Diablo and Fremantle. It really isn't right that I'm packaging this as part of my easy-chroot package; my package should depend on this package.

At the end of September, Attila77 graciously offered to get the Diablo dmloop package into the repositories for me... He wrote to me:

"Just to let you know, I got the module built, but there is a bit of a snag, the i386 part of the autobuilder process dies a horrible death as it can't really deal with the arm kernel stuff and thus marks the whole package as failed. I already wrote Jeremiah about this, so hopefully with a little help I'll have this in extras shortly."

Here's a link to his package (currently in my repository, doesn't seem to be in Extras yet).

So this looks like it will be quite a challenge for anyone willing to try it for Fremantle... And can anyone help getting the package to build for Diablo?

If it means something, I can 'fake' the i386 part, so only the ARM module gets built. Not pretty, but it would work with extras until Jeremiah gets some time to play with it.

BTW I though you said 'simple' loop is good enough in Fremantle ?

Well, setting the Architecture field in debian/control to armel ensures that it only gets built for ARM; no "faking" required. TBH, I don't see why the modules would be needed in an I386 Scratchbox anyway; Scratchbox insists on reporting your hosts' kernel version when running "uname -a" so I doubt they're gonna work either way.

P.S. I'd say that the modules are needed for Fremantle. "apt-get install nokia-binaries nokia-apps" completed when I woke up in the morning...

I know about (and set) that field, but the autobuilder DOES make (or rather, tries to make) something in i386, and that's where it blows up (complains about the cross-compiler, but the actual error is not there, it shouldn't get that far in the first place)

Seeing as you will have already once uploaded it to the autobuilder, would it be too much trouble to ask for the source package so I can look at it (not to upload with my name as the Maintainer ), please?

Thanks guys.

It's because of you and this stuff that you do that I love this place.

<warm fuzzies>

Sent. I believe the thing is quite self-explanatory, I just extract the kernel source, patch the dmloop stuff, compile, and that's about it. It's probably failing because of something trivial (=me not seeing something 'cause my eyes get in the way). Under a VM on my ancient hardware, every attempt was ~30 minutes so I lost interest in the trial and error method real quick, especially as I had my armel.deb You are very welcome to become maintainer

PS The architecture is 'all' in the archive, which is wrong, I know, I was just trying to figure out a few arch related things and it remained that way in the last package.

PPS Also, Matan showed some interest in packaging modules, so if you figure out what I was missing, post here so anyone trying to add a separate deb module can work it out.

https://garage.maemo.org/pipermail/e...er/010773.html =)

qwerty12 for president !

Hi guys,

I've finally had a chance to look at the package that you built. It has the kernel modules, but now we need the dmsetup package in Extras too (see first post in the thread).

The dmsetup package should additionally have a symbolic link made (in postinst), /sbin/dmlosetup, which points to /sbin/dmsetup.

As soon as these things appear in the repositories, I can start depending on them for my package instead of providing them.