Re: What do we know about Diablo (Maemo 4.1) ?
 

No. The "cease and desist" or takedown order comes before lawsuit.

NOTE: that is not an official corporate statement!!!!

Re: What do we know about Diablo (Maemo 4.1) ?
 

I thought about that but decided it wouldn't work.

initfs flasher grabs initfs from the already flashed initfs. Defeats point when you cant flash image to rip...

Also, loop device doesn't exist on n800 afaik and the modules to emulate an mtd are not available for n800.

Re: What do we know about Diablo (Maemo 4.1) ?
 

Well, I got /dev/loop[0-7] here... BTW, thanks for that kernel info! I grabbed Fanoush's.

Re: What do we know about Diablo (Maemo 4.1) ?
 

I don't see no losetup ;)

Besides, you need modules to emulate an mtd device too. Like nokia, I don't see the point in compiling them. I compiled mtd-utils thanks to fanoush's source so you can remake the image at least on the device.
(actually, initfs flasher has tool needed too)

No problems :)

Re: What do we know about Diablo (Maemo 4.1) ?
 

I'm running diablo, but I'm running it with chinook's kernel and initfs. When I flash diablo's kernel my N810 won't boot, it just shows the NOKIA image for a while and then it dies (no progressbar or anything).. Also, "About product" in Control Panel shows <unknown> version. If someone would point me in the right direction to get diablo's kernel and initfs working, I'd be very grateful. :)

Re: What do we know about Diablo (Maemo 4.1) ?
 

Hmm... Funny; it looks like mount -o loop used to work (OS2007, PB used it for XFCE at least), but doesn't now. I even tried chrooting to an extracted initfs. Still no good. I'm not sure if mount -o loop uses losetup, or if something else is wrong (perhaps pertaining to mtd emulation; I had thought that was an alternative, not a corequisite). Oh, well, I'll look at it more when I get irritated enough ;). (Maybe it works from Debian... but I probably still need to compile the mtd stuff.)

Be nice if you could post a tar of the initial contents of the Diablo initfs, but I suppose Reggie and Qim would rather you didn't...

You need to get hold of a tar of the Diablo initfs. You can do that any of three general ways:

• With a Glock (to threaten or barter, your call.)
• On the device, like I was trying. It seems rather troublesome, but you will be lauded as a hero if you can post kernel modules that let us all tear Diablo initfses to pieces and build them back up our own ways.
• Or you could do it on a desktop, as Faheem outlined.

Once you got that, it's pretty straightforward; read through the initfs_flash script and you'll see what it's doing. Modify that procedure as needed...
Or do the stripping, bundling and even flashing, if you like, from the desktop.

Dunno about the kernel; the new kernel, I'd have thought, would just work...

Re: What do we know about Diablo (Maemo 4.1) ?
 

Loopback was the first thing I tried, but I got the same results you did - no dice. It probably needs losetup, which (as qwerty12 observed) is not on the device.

I also tried Fanoush's initfs_flasher stuff, but ran into the same problems qwerty12 mentioned - it operates directly on the device's initfs partition, probably to get around the loopback problem. So that would require flashing the image onto the initfs partition, which (of course) is the whole problem in the first place.

I considered dd'ing the jffs2 file to one of the other partitions (like a memory card), and we'd be able to rip files out (either manually or with a modified initfs_flasher), but then we'd still need mkjffs2 in order to re-jffs2 the contents into a size small enough to fit onto the N8x0's initfs partition.

In the end, it's probably easier to just do it all on the desktop.

Re: What do we know about Diablo (Maemo 4.1) ?
 

How hard is it to re-partition the device's internal flash to give the initfs partition enough space to hold the larger jffs2 image? It's only around 300k too large; I don't mind sacrificing it. Anybody know how to do that? Do we need an entire Fiasco image for that to work?

Re: What do we know about Diablo (Maemo 4.1) ?
 

Well, if you've got initfs_flasher, it's got mkfs.jffs2 and what-not. That idea of slamming it on a mmc partition... yeah! (I think you solved it.)

(For me, doing it on a desktop's not easier, because my Linux desktop is unfortunately deprived of internet access (and ~50 miles away). LiveCDs aren't fun for that kinda work, in my experience.)

Re: What do we know about Diablo (Maemo 4.1) ?
 

Remember, you probably still need something to emulate the mtd device unles mount -o jffs2 /dev/mmcetc works straight.

mtdram is out. johnx with 1gb ram couldn't mount diablo initfs, i could with 2gb ram.
mtd2block sounds like it would work.

fanoush posted me a bug which made his partition start location later but he had to compile custom kernel to point to new place and never fixed it afaik :p