Re: 'Fixed in Fremantle' and Diablo community SSU
 

ok. here is my log - straight from my n810

UPDATE: After posting the log, I did the update with apt-get upgrade. Everything seems to be fine after the update with your SSU packages.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Good to see this:

http://farm5.static.flickr.com/4008/...31ae6b8e_o.png

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Upgraded with no problem at all (regullar SSU, not unlocked)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

sorry about the delay. Here's my log.
Attachment 8298

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Full success updating my very custom OS using the 'Unlocked' variant of the Community SSU!

I AM VERY EXCITED BY THIS.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Qole, did you have any problems with rotate? Does your OS boot from external?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Yes, after installing the SSU, rotation continues to work.
Yes, I installed it to a cloned OS on an external SD card.
If only Nokia's SSUs had been so painless.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Thanks for the logs guys, but I guess I needed logs from before the update was applied in order to see what the problem was :-/

Can you test whether you have any variant of osso-software-version ("dpkg -l | grep osso-software-version") installed?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

To be fair, this is a tiny update that doesn't touch too many things and uses exactly the same mechanisms as the Nokia SSUs. Rotation still works because both the kernel and X server were left alone :-)

I think the next step should be to push an updated kernel (might as well do the full rotate support though) to make sure updating that also works. It probably won't happen for a few days, but feel free to disable the SSU repository now if that makes you nervous and you wish to opt out.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Gah, I managed to screw up the last osso-software-version package (claim to fix an ls -Q bug but actually depend on the previous busybox version). Pushed an updated one, feel free to skip 1:5.2010-12-2 if you are running the -unlocked variant (which would have installed the fixed busybox anyway) and save yourselves a reboot.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Um, I posted my log before I updated with apt-get upgrade manually...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Is this community SSU process going to allow us to re-compile libsdl-mixer1.2 with more features (OGG Vorbis support) and provide it to the broader community as part of this update? If so, where do I go to propose such an update? I've got the package sources ready (patched from Diablo source).

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Interesting, I don't see anything related to the community-SSU reporitory in your log. Can you double-check that you do have some variant of osso-software-version installed?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

That's a very interesting question!

It's not just a simple matter of rebuilding as it pulls in libvorbis etc dependencies. That's not too much "bloat" (~1MB) but it does mean we'll have to package & distribute those as well, and be careful to avoid conflicts with extras (at the very least some coordination with Tuomas Kulve would be necessary).

Personally I wouldn't mind at all having Ogg support out of the box (it's one of the first things I install anyway), anyone have any good arguments against it?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

The thing I would most like to see in an updated Diablo is a way of optionally running USB host mode with OHCI and EHCI controllers in place of the currently built-in MUSB.

This looks like the best hope for overcoming Bug 3281. The bug isn't "Fixed in Fremantle", but it is a serious limitation on N8x0's usefulness. With that fixed, I might be able to leave my 770 at home when travelling.

For end users, there would have to be some indication that the USB operation is host-only when this option is active.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I Have a n810 i would also happy to test.

If there is something wrong and it does stop working.
Am i right in saying the worst that could happen is that i would have to reflash it?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I'm not sure I am running the command right to check osso software version. I can tell you I see the new update you pushed. but it too says broken but able to update.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Is the application manager log still the same? Ie, does it still only mention ignoring xserver-xomap, kernel-diablo-flasher and libelfg0 as "from wrong domain"?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I've just noticed a new version--- (OS2008 Community SSU) 5.2010-12-2

Are testers to update ?... is this the one with "rotation support" mentioned a while ago?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Yes. It's still the same.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

No, see post 170.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Thanks. I've no idea why it thinks it's broken then :-( Can you run an "apt-get upgrade" and check what it proposes? You don't have to actually do the upgrade, just see what it thinks it's going to do.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

It says "you might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies 'osso-software-version-rx44-unlocked: Depends: kernel-diablo-flasher (>= 2.6.21-200842maemo1) but 2.6.21-200835maemo1rotation is installed.

Depends: xserver-xomap (>=1:1.3.99.0~git20070321-osso20083801) but 1:1.3.99.0~git20070321-osso20083101rotation is installed."

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Just did the upgrade ......
can now do..................... " ls -Q "

all is good.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Ah, true: 2.6.21-200835maemo1rotation isn't >= 2.6.21-200842maemo1. Same goes for:

So your kernel & xserver are out of date even relative to 5.2008.43-7, but according to the application manager log there are newer ones available. Try installing those first.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

In the app manager I only have the option to instll update "os2008 Community SSU (unlocked)" That one says Broken. Is there another way I can install the newer ones? Also, is the newer ones going to uninstall rotation?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Try

or, if that doesn't do the trick, with explicit versions:

(all on one line).

I can't say with 100% certainty as they're not my packages, but judging from their version names most likely not. The kernel looks like it also has the 48MHz SD patch applied so do test that your card(s) work correctly with it, and make a backup of their contents just in case.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I didnt have the package installed.
Now I did apt-get install osso-software-unlocked.
After that, the update manager shows me an upgrade
"OS200 Community SSU (unlocked)" :)
(Of course it didnt really update anything except the meta package because I already installed everything with apt-get upgrade)

Sorry I got the tablet from a friend and unfortunately did not do a reflash after that, I dont know if it was in a strange state.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Lma, that did it. New ssu installed successfully and rotate support is still working. All is well ^_^

Re: 'Fixed in Fremantle' and Diablo community SSU
 

It should be a bit faster too (but don't blame me for that) ;-)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Rotate is certainly faster. And no more broken packages. Let me know if there is anything else I should test =)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Has anyone tried OHCI (OMAP2 doesn't have EHCI), and is it stable? Are there any drawbacks?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Hate to clutter the thread with garbage but I can not get the email to fully register to my address..I'll only be a second and take up little screen space

@lma - can you please re-email the link to me. I accidentally deleted your email in group deletion and had been busy over the weekend I'll have to read the thread seems there's a bit of progress; cool! On a side note I'm picking up an 810 to breed with my 800. :)

...

Re: 'Fixed in Fremantle' and Diablo community SSU
 

xopher: will you be selling the puppies?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Wow. There's a lot of stuff going on... and I need to catch up with 10+ pages. So indulge me for a moment... this isn't public yet, right?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

gerbick: it isn't public, you have to PM lma for the details. But he'll gladly send them to you if you ask!

Re: 'Fixed in Fremantle' and Diablo community SSU
 

I tend to be one of them horders you see documentaries about. :)

Re: 'Fixed in Fremantle' and Diablo community SSU
 

No arguments against it so far - how do we proceed?

Re: 'Fixed in Fremantle' and Diablo community SSU
 

OHCI would be good for me. I put in the EHCI suggestion in case other members complain that OHCI is too slow and too old. Sorry I can't tell you how stable etc. - I'm not that far advanced.

Presumably anyone choosing this option would know how to mount storage devices, and there would therefore be no need to include auto-mounting of those. The main reason for taking this option would (presumably) be to make it possible to disable auto-mounting. (This doesn't work with MUSB, because of MUSB's dependence on g_file_storage to see all the way to end-point interface devices.) If auto-mounting is left out, there will be no need for special HAL configuration to suppress it for cameras etc.

Re: 'Fixed in Fremantle' and Diablo community SSU
 

Is possible add bug 3415 ??

Tks