Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

That's most likely unrelated. It means the file system is corrupted (when the kernel detects that it remounts it read-only as a precaution to avoid damaging it further).

There are many ways this can happen, like mounting on another computer via USB and unplugging without unmounting cleanly, unclean shutdown (removing the battery, or running out of battery suddenly) and so on. It may also be bug 2940 if you're one of the unlucky first buyers (though you would probably have noticed years ago), so check for that first.

Otherwise you should unmount the filesystem and repair it with dosfsck, it should be fine after that.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

Wow, I'm speechless (well, not really).
In spite of what the marketing says about the openness of maemo they won't even disclose the build flags.
Cannot say I'm really surprised.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

DEB_BUILD_OPTIONS="maemo-launcher,thumb,vfp,parallel=4"

should be the right ones, I mean, autobuilder uses same..

And then CFLAGS="-Wall -g -O2 -mfpu=vfp -mfloat-abi=softfp -mcpu=arm1136jf-s -mtune=arm1136jf-s" if not indicated already.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

Wow, thanks, that's exactly the info I was looking for!

Using the above I get exactly the same Xomap binary as before, so if there is a bug it's not due to build flags at least, good to know.

I hadn't seen "maemo-launcher" as an option before, but that explains some other differences I noticed in GUI apps. Unfortunately the deb tools in scratchbox are too old to handle "parallel", but a few packages deal with it on their own in debian/rules. I'll probably adapt others to do the same for sanity's sake.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

okey, I rebooted, then deleted swap.
next:
umount /media/mmc2
fsck.vfat -a -d /media/mmc2/ -u /media/mmc2/
mount /dev/mmcblk0p1 /media/mmc2
reboot


Now it works perfect, but I still don't know what it was. Btw, bug 2940 is not for me, 'cause I own my n810 more than 1 year.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

@Ima, See my update to thread #18.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

libssl0.9.7 is not working after installing this SSU and I am using the stable version, when i try to install gizmo, it says that, and when i used -apt get, it said it installed, but when I tried gizmo again, it said missing libssl0.9.7 again, is this just me or other people too?

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

Gizmo may be gone because Google bought it.
Don't trust me though, I did no research.

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

They did, and I have an account that I use and my friend uses and we chat video from time to time

Re: [Announce] First "stable" Diablo community SSU released and call for participation
 

iirc, existing accounts are still working but new ones can't be created.