View Full Version : 'Fixed in Fremantle' and Diablo community SSU
Stskeeps
08-04-2009, 01:41 PM
This project is now active and working!:
Read more at http://wiki.maemo.org/Diablo_Community_Project
Original post:
I was thinking a bit about the community SSU to Diablo (http://talk.maemo.org/showpost.php?p=304018&postcount=35)and how to go about it. Obviously we have some community-relevant fixes to the application manager and some other things that can be useful.
But what I'm wondering about - if you had a chance to select one favourite Fixed in Fremantle bug fixed in the open source packages and have this backported to be fixed in a community SSU, which would you take - and why?
EDIT: Please note the bugs.maemo.org bug numbers in question too. :)
zerojay
08-04-2009, 01:42 PM
And the list of 'Fixed in Freemantle' bugs is...where?
sjgadsby
08-04-2009, 01:48 PM
And the list of 'Fixed in Freemantle' bugs is...where?
The size of the list is going to depend upon what exactly you want to lump in under the "Fixed in Fremantle" header, but I have the results of a quick search (https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Maemo+Official+Applications&classification=Maemo+Official+Platform&target_milestone=Fremantle&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&resolution=FIXED&resolution=INVALID&resolution=WORKSFORME&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=enhancement&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=).
(By the way, Zerojay, it's "Fremantle", not "Freemantle". It's a small thing, but the extra "e" you include doesn't jive with your focus on text perfection.)
Stskeeps
08-04-2009, 01:49 PM
And the list of 'Fixed in Freemantle' bugs is...where?
https://bugs.maemo.org/buglist.cgi?target_milestone=Fremantle&resolution=FIXED is also a possibility.
zerojay
08-04-2009, 01:52 PM
(By the way, Zerojay, it's "Fremantle", not "Freemantle". It's a small thing, but the extra "e" you include doesn't jive with your focus on text perfection.)
I blame all the times I've had to use the word "freemasons" over the last two months. ;/
But what I'm wondering about - if you had a chance to select one favourite Fixed in Fremantle bug fixed in the open source packages and have this backported to be fixed in a community SSU, which would you take - and why?
sadly, its not so much a fix as a total rewrite. basically, what irks me the most is that until diablo, one could trigger a network access while in offline mode, say yes on the dialog, and have wifi connect to a saved hotspot automatically...
since diablo, it instead claims that it cant find any saved hotspots, and i have the impression the nokia devs know where the bug is, but as the networking system have been fully replaced for fremantle, there will never be a fix...
sachin007
08-04-2009, 02:03 PM
A2DP please!
Stskeeps
08-04-2009, 02:07 PM
sadly, its not so much a fix as a total rewrite. basically, what irks me the most is that until diablo, one could trigger a network access while in offline mode, say yes on the dialog, and have wifi connect to a saved hotspot automatically...
since diablo, it instead claims that it cant find any saved hotspots, and i have the impression the nokia devs know where the bug is, but as the networking system have been fully replaced for fremantle, there will never be a fix...
AFAIK we're still on icd and libconic. Correct me if I'm wrong.
buurmas
08-04-2009, 02:20 PM
Does upgrading the Flash player count? If so, I think that would get my vote. There are MicroB bugs that bother me, but then I just use Tear instead.
EDIT:
one favourite Fixed in Fremantle bug fixed in the open source packages
Oops -- it probably doesn't count. Apologies.
gazza_d
08-04-2009, 03:07 PM
Even though it's not open, the fix which unbreaks metalayer-crawled since the last SSU would be a good thing to add, especially if we can add an option to start/stop the thing at will.
Otherwise just all the simple stuff which is easy to fix. I would sooner see the efforts put into bringing Mer up to the level where it can replace Maemo, and run all the new versions of apps like Gpodder, and Mauku.
Spending a lot of time fixing diablo, doesn't change the fact that it's now a dead end, and that the majority of new development is understandably going to be for Fremantle.
Being able to provide access to all or most of those apps on the current hardware would seem to me to be the best use of the resources available.
wklink
08-04-2009, 03:11 PM
A2DP please!
+AVRCP. A2DP can be made to work--with limits--but AVRCP doesn't work at all.
Saturn
08-04-2009, 06:47 PM
Lock applets in desktop:
https://bugs.maemo.org/show_bug.cgi?id=2639
Saturn
08-04-2009, 06:49 PM
clock with 12/24h selection!!
https://bugs.maemo.org/show_bug.cgi?id=303
Saturn
08-04-2009, 06:51 PM
more contacts number!! yuppie!
https://bugs.maemo.org/show_bug.cgi?id=1034
Jaffa
08-04-2009, 08:23 PM
#2639 is already included in Mer.
#303 primarily affects Nokia's closed-source Clock application (if it was open source, I'd've fixed it 4 years ago!)
#1034 is - I think - in the closed source UI again.
I always wondered why the camera app didn't come pre-installed.
sjgadsby
08-04-2009, 09:10 PM
I always wondered why the camera app didn't come pre-installed.
/usr/bin/camera
There's just no entry in the application menu out of the box.
Low hanging fruit (stuff that could be packaged right now):
2639 (https://bugs.maemo.org/show_bug.cgi?id=2639) Home view needs to have an option to lock desktop applets into place
3455 (https://bugs.maemo.org/show_bug.cgi?id=3455) telepathy-gabble deadlooping
3951 (https://bugs.maemo.org/show_bug.cgi?id=3951) Incompatible quote handling in Busybox xargs (FEATURE_XARGS_SUPPORT_QUOTES disabled?)
3957 (https://bugs.maemo.org/show_bug.cgi?id=3957) Busybox does not support "ls -Q" which some scripts need
3968 (https://bugs.maemo.org/show_bug.cgi?id=3968) grep -r can output corrupt data in error message if file cannot be read
4079 (https://bugs.maemo.org/show_bug.cgi?id=4079) busybox df does not handle root filesystem on command line
4119 (https://bugs.maemo.org/show_bug.cgi?id=4119) digest-uri omits the serv-name part causing authentication failure when host != serv-name
4174 (https://bugs.maemo.org/show_bug.cgi?id=4174) shell history file is overwritten after every command
4225 (https://bugs.maemo.org/show_bug.cgi?id=4225) The x11vnc does not work on some areas of the screen
4803 (https://bugs.maemo.org/show_bug.cgi?id=4803) Modest sends empty ENABLE command when IMAP server advertises ENABLE but not CONDSTORE or QRESYNC capabilities
Some stuff that needs more investigation:
2863 (https://bugs.maemo.org/show_bug.cgi?id=2863) Allow setting of MTU per access point
3793 (https://bugs.maemo.org/show_bug.cgi?id=3793) Segmentation fault when ossofilemanager access SMB shares
3885 (https://bugs.maemo.org/show_bug.cgi?id=3885) RSS Reader Fails to Read HTTPS RSS Webpages
4248 (https://bugs.maemo.org/show_bug.cgi?id=4248) Enable features in Busybox to increase its tools GNU/Debian compatibility
The most annoying bug for me is the no-flip camera bug on the N800
since diablo, it instead claims that it cant find any saved hotspots
I think there was a bug for that but I can't find it now - IIRC that happens if you restore the access points from a pre-diablo backup.
I think there was a bug for that but I can't find it now - IIRC that happens if you restore the access points from a pre-diablo backup.
clearing house and rebuilding did not make it go away...
https://bugs.maemo.org/show_bug.cgi?id=3310
this looks like the bug, tho i could have sworn it was claimed fixed in fremantle because it had a reworked networking system...
That annoying charging screen that doesn't let me use the device while charging. Of course that doesn't happen in Mer.
That annoying charging screen that doesn't let me use the device while charging. Of course that doesn't happen in Mer.
press power and it should boot to the desktop...
press power and it should boot to the desktop...Alright, I just tested it and it worked, so this problem only happens with powerlunch then. When I had that installed, pressing the power button while charging would only brought up the powerlunch menu.
danramos
08-05-2009, 02:15 AM
Oh God.. this thread is making me VERY, VERY drunk with EVERY mention of 'fixed in Fremantle'
...aw crap, now I did it. (drink!)
Alright, I just tested it and it worked, so this problem only happens with powerlunch then. When I had that installed, pressing the power button while charging would only brought up the powerlunch menu.
may i ask what your using powerlaunch for? And yes, i recall that powerlaunch has such a issue, as i have ranted about it myself at one time...
Oh God.. this thread is making me VERY, VERY drunk with EVERY mention of 'fixed in Fremantle'
...aw crap, now I did it. (drink!)
cheers, campai, and all those other words for the same action ;)
Tomaszd
08-07-2009, 08:22 PM
A2DP with AVRCP for me would be a great addition, but it does require a kernel patch to fix stability issues. This patch, along with a few FiF patches from bugzilla are in Mer currently.
When it comes to bugs... locking the applets in place would be nice.
It would also be great if the microb browser got an update. It's running alpha code.
Snoshrk
08-10-2009, 11:07 AM
When it comes to bugs... locking the applets in place would be nice.
.
Step by step (even for a linux n00b like me) (http://talk.maemo.org/showthread.php?t=30508&highlight=home+lock)
Seems to work as advertised :D
only that it has to be set again on each reboot...
Saturn
08-13-2009, 07:08 PM
only that it has to be set again on each reboot...
Hi, if you use the latest files from Qwerty (see here: http://talk.maemo.org/showpost.php?p=305095&postcount=1046) the setting is persistent.
HIH and sorry for the change of subject.
Hi, if you use the latest files from Qwerty (see here: http://talk.maemo.org/showpost.php?p=305095&postcount=1046) the setting is persistent.
HIH and sorry for the change of subject.
these where not linked in the "howto"-thread then?
Saturn
08-14-2009, 02:20 PM
these where not linked in the "howto"-thread then?
I think not. qwerty is too quick for a thread. ;)
If I remember correctly even the option was a little different. You could check from the screenshots.
Again, sorry to the OP.
so, now that the N900 cat is out of the bag, it would be nice to get a official go ahead from nokia to let the community do SSUs for diablo...
zerojay
08-28-2009, 02:16 PM
so, now that the N900 cat is out of the bag, it would be nice to get a official go ahead from nokia to let the community do SSUs for diablo...
That probably won't ever be happening. Nokia would be scared to death at the thought of something the community does in an SSU killing or forcing a tablet reflash.
allnameswereout
08-28-2009, 02:26 PM
so, now that the N900 cat is out of the bag, it would be nice to get a official go ahead from nokia to let the community do SSUs for diablo...There is big difference between community/3rd party/unofficial support and official support by manufacturer. They shouldn't be mixed.
Diablo going forward with community support vs Fremantle backported to the N8*0 via Mer. Has thre beeen discussion and conclusion about which is the way preferred by the community?
Diablo going forward with community support vs Fremantle backported to the N8*0 via Mer. Has thre beeen discussion and conclusion about which is the way preferred by the community?
Why do you imply they are mutually exclusive? And let's not forget Mer has other goals besides backporting Fremantle to N8x0.
pelago
08-28-2009, 04:42 PM
Diablo going forward with community support vs Fremantle backported to the N8*0 via Mer. Has thre beeen discussion and conclusion about which is the way preferred by the community?
Call me greedy, but it would be nice to have a choice of both. Diablo+community SSUs for those who aren't ready to make the jump to a new UI/platform and 'just' want a fixed Diablo, and Fremantle via Mer for those who want the shiny and like living dangerously.
Sure, it's good to have choices but this implies more work for everybody. A priority list would help at least. :)
Saturn
08-28-2009, 05:53 PM
How about adding support for the Nokia PC Suite? It is already done for the Maemo 5.
Synchronisation with Outlook, SyncML etc have been requested from day 1.
Saturn
08-28-2009, 05:54 PM
Sure, it's good to have choices but this implies more work for everybody. A priority list would help at least. :)
Just wanted to say..
Thanks a lot for listening; Especially now with all things happening..
Edit: I was actually planning to quote your other post (http://talk.maemo.org/showpost.php?p=317512&postcount=38) but it's OK you get the point.
GeneralAntilles
08-29-2009, 12:27 AM
Sure, it's good to have choices but this implies more work for everybody. A priority list would help at least. :)
Both options are being pursued, we just need some people to step up and lead the SSU one.
Any volunteers interested in seeing it happen should hop to it, as the ball isn't in Nokia's court at the moment.
Diablo going forward with community support vs Fremantle backported to the N8*0 via Mer.
As others said, those aren't mutually exclusive. But thanks for asking :-)
Sure, it's good to have choices but this implies more work for everybody. A priority list would help at least. :)
I would vote for giving priority to enabling community Diablo updates first, then moving all available resources to Mer. Rationale: Mer isn't stable/complete enough for end users and probably won't be for a while. On the other hand there's a growing set of Diablo patches sitting in bugzilla which solve real problems and could be packaged and distributed to willing users.
Now, the good news is that there is very little Nokia needs to do to enable the community to go ahead with this (see also Andrew's post here (http://talk.maemo.org/showthread.php?p=304018)).
IMHO the only blocker is the lack of clarity on Nokia's intentions regarding releasing more official Diablo SSUs. We know there are internal fixes for various bugs that have not been released yet (eg bug 3830 (https://bugs.maemo.org/show_bug.cgi?id=3830), about which someone was asking right here (http://talk.maemo.org/showthread.php?t=31151) earlier today or bug 3793 (https://bugs.maemo.org/show_bug.cgi?id=3793) which is a crash/critical bug). It would be nice to have these, but at this point it would seem more productive to declare Diablo officially unsupported and move on. And maybe at some future time Nokia may even publish those updates to the community repository :-)
I of course would like to see the current, fixed OS2008 RTComm Beta pushed into the core of the system, rather than a complex secondary install that involves going to Red Pill mode (!)
there is a reason i have pidgin installed...
buurmas
09-16-2009, 02:36 PM
See also this (http://talk.maemo.org/showthread.php?t=31746).
Both options are being pursued, we just need some people to step up and lead the SSU one.
Any volunteers interested in seeing it happen should hop to it, as the ball isn't in Nokia's court at the moment.Volunteer how? Who is mentor? (did not see it in current Sprint)
GeneralAntilles
09-20-2009, 02:37 PM
Volunteer how? Who is mentor? (did not see it in current Sprint)
Pick it up and run with it. Organize people, talk to Nokia, get the necessary patches gathered up. You could be mentoring if you want this to happen.
At the moment the Maemo Devices team is focused in the Maemo 5 release and any resource available jumps to Harmattan. If you need an official word I can't give it but if a recommendation is enough then I recommend you to organize yourselves and make a list somewhere with the list of things you still need from Nokia.
Who will be our hero, our champion, our SSU-foo master?
SD69, will you shoulder the burden, buckle the armour and lead the troops?
Someone should bring this up at the next sprint. Maybe we can get an eager new council member to help, too.
Who will be our hero, our champion, our SSU-foo master?
SD69, will you shoulder the burden, buckle the armour and lead the troops?
Someone should bring this up at the next sprint. Maybe we can get an eager new council member to help, too.I will volunteer and promote, organize, etc., but I think a developer type should mentor the project. I am not a programmer and didn't even fully understand Jaffa's 5-point plan, but I did catch the part about non-developers being able to help.
Anyone interested in having a BoF session about this at the Summit? Saturday morning looks like a good time and still has two slots open.
Stskeeps
09-26-2009, 09:28 AM
Anyone interested in having a BoF session about this at the Summit? Saturday morning looks like a good time and still has two slots open.
I'm in. Is definately a project worth discussing. Also in terms of community variants of Fremantle.
Anyone interested in having a BoF session about this at the Summit? Saturday morning looks like a good time and still has two slots open.Good idea, especially to get some people invvolved. Unfortunately, I won't be able to attend. But I started a wiki page for Diablo community - and we can add and work on a page for software update and BoF session.
I'm in. Is definately a project worth discussing. Also in terms of community variants of Fremantle.
Thanks :-)
Anyone else? It doesn't look like we have enough critical mass to book a BoF session yet, but let's at least meet "unoficially" during one of the breaks. Shall we say Saturday 13:00 outside N810 (also a good opportunity to grab Jeremiah)?
buurmas
10-06-2009, 02:31 PM
Offshoot thread about opening up more portions of code is here (http://talk.maemo.org/showthread.php?t=32448).
Fontus
10-06-2009, 03:11 PM
BTW, something that I*think has not been said yet...
In my opinion Mer and Diablo are not necessarily two alternatives. I think it should not be difficult to build a version of Mer that includes the old libraries of Diablo and is binary compatible with Diablo and maybe even has the libraries of Fremantle only as an option. The choice Matchmox/Fvwm/whatever can be made after the installation of the OS even without restart of the OS. If the user selects Matchbox, the result would be an improved Diablo with possibility to install the software both for Diablo and Fremantle.
BTW, something that I*think has not been said yet...
In my opinion Mer and Diablo are not necessarily two alternatives. I think it should not be difficult to build a version of Mer that includes the old libraries of Diablo and is binary compatible with Diablo and maybe even has the libraries of Fremantle only as an option. The choice Matchmox/Fvwm/whatever can be made after the installation of the OS even without restart of the OS. If the user selects Matchbox, the result would be an improved Diablo with possibility to install the software both for Diablo and Fremantle.
Although there is overlap, I believe that Mer has already dropped binary compatibility with Diablo.
Read and contribute to:
http://wiki.maemo.org/Diablo_Community_Project
buurmas
10-13-2009, 06:24 PM
My biased list of Diablo bugs that bother me most:
1. Media Player not refreshing (3970 (https://bugs.maemo.org/show_bug.cgi?id=3970)).
2. MicroB certificate problems (349 (https://bugs.maemo.org/show_bug.cgi?id=349), 3792 (https://bugs.maemo.org/show_bug.cgi?id=3792)). It would be nice to use my N810 to access some of my secure company web sites.
A short update on the summit meeting was posted here (http://lists.maemo.org/pipermail/maemo-developers/2009-October/021351.html). Hopefully we will have a repository and be able to start testing soon :-)
In the meantime, I would like to discuss the scope of the community updates project a bit.
In my mind, the updates should be rock-solid. It MUST be safe to tell a non-technical end-user to enable our repository, and when they do that they should get a better Diablo as a result and absolutely no nasty surprises. That means no experimental stuff (that includes things like the forthcoming TI GPU drivers, at least until they're well tested and found good enough), nothing that breaks compatibility with existing apps etc. Tested bug fixes and enhancements belong here, but new/experimental stuff should probably go to Mer.
I'm hopeful that by the time we've cleared the existing backlog this will encourage more contributors to submit patches so the project may continue for a while, but in the long run, Mer is the future and there's little point duplicating effort.
In my mind, the updates should be rock-solid. It MUST be safe to tell a non-technical end-user to enable our repository, and when they do that they should get a better Diablo as a result and absolutely no nasty surprises. That means no experimental stuff (that includes things like the forthcoming TI GPU drivers, at least until they're well tested and found good enough), nothing that breaks compatibility with existing apps etc. Tested bug fixes and enhancements belong here, but new/experimental stuff should probably go to Mer.
I agree.
I'm hopeful that by the time we've cleared the existing backlog this will encourage more contributors to submit patches so the project may continue for a while, but in the long run, Mer is the future and there's little point duplicating effort.We don't have a clear roadmap for Maemo, so the future is uncertain. Plenty of people are satisfied with stylus-based Diablo UI, now and in the future. It's only the HW that will need updating eventually.
buurmas
10-20-2009, 08:01 AM
My appreciation for all who discussed this & are involved. From my perspective, ANY maintenance to Diablo is better than nothing. It doesn't have to be visionary (although I appreciate that that stuff is cool). Each bug that was FiF represents a roadblock to Diablo usability (forcing users to stop using certain features or develop tortured workarounds). Each one that the community fixes is giving users back their tablets! From my perspective, little bug fixes is big stuff.
A small update: we now have a "community-diablo" bugzilla keyword for bugs with patches of interest to the community SSU project. I've marked all the ones I could find, but feel free to update any I might have missed.
buurmas
10-22-2009, 02:20 PM
If you're talking about the "Keywords" field on the bug page (example (https://bugs.maemo.org/show_bug.cgi?id=3970)), when I change it I get this message:
"You tried to change the Keywords field from crash to crash, community-diablo , but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field."
"I've got the power"... not! :) So it looks like only some people can do this.
Oops, I didn't realize that... Plan b: post bug numbers to this thread and I'll have a look at them.
example (https://bugs.maemo.org/show_bug.cgi?id=3970)
Unfortunately that's just a binary attachment for a closed component, so we probably can't re-distribute it.
solarion
10-22-2009, 03:07 PM
Pardon my ignorance, but what's SSU? What happens now that Fremantle is out? Is there a FAQ I can read?
Saturn
10-22-2009, 06:30 PM
Pardon my ignorance, but what's SSU? What happens now that Fremantle is out? Is there a FAQ I can read?
check here:
http://wiki.maemo.org/SSU
buurmas
10-26-2009, 02:11 PM
Unfortunately that's just a binary attachment for a closed component, so we probably can't re-distribute it.
Sorry, I thought I'd done my homework on this, but clearly I was wrong. :( Even with the list of closed components (http://wiki.maemo.org/Why_the_closed_packages), it can be hard to figure this stuff out. (Is metalayer-crawler the same as libmetalayer? Exactly what library contains the bug? Those kinds of questions.)
Unfortunately that's just a binary attachment for a closed component, so we probably can't re-distribute it.
I think we will be able to. Nokia seems open to the idea of the community pushing this SSU, and an SSU certainly can't be composed entirely of open pieces; that would be absurd.
The binary in question was posted in a public place; it's not like anyone would be "stealing" it. And the SSU would only be going out to device owners, anyway.
solarion
10-26-2009, 04:19 PM
could some sort of project leader get the keys to maintain/push the proprietary bits from Nokia?
The binary in question was posted in a public place; it's not like anyone would be "stealing" it. And the SSU would only be going out to device owners, anyway.
There's no explicit or implicit redistribution licence that I can see. The .deb's licence is "Copyright (C) 2006 Nokia Corporation. All rights reserved." and the bugzilla attachment is clearly marked "for testing". So at best it's a gray area, and I don't think we should start taking liberties. It doesn't hurt to ask though, would you like to?
Alternatively, Nokia can push it to the community repo themselves once it's up and running :-)
Alternatively, Nokia can push it to the community repo themselves once it's up and running :-)
I think the time to ask for these closed bits will be when there's somewhere for us to receive them, ie the community repo. I suspect that Nokia will be willing to upload stuff as long as it isn't too much work for them, and maybe let us package stuff that is too much hassle for them to do.
I think the time to ask for these closed bits will be when there's somewhere for us to receive them, ie the community repo.
True. In the meantime, since the creation of the repo etc doesn't seem to be moving forward, could you push for it a bit in the November sprint?
jeremiah
12-29-2009, 08:43 AM
Hi!
I have set up a new repository on the new infrastructure generously provided by Nokia for community SSU packages. The new repo is not yet public but I would like to test it with some packages and get it ready for when it becomes publicly viewable.
If anyone has an SSU to submit, please let me know.
Jeremiah
---
jeremiah@maemo.org
jebba
12-29-2009, 04:37 PM
Can you explain a bit more WTF you mean? Sry, I'm not quite following what packages will be in this repo.
Jeremiah's blog announcement:
http://blog.jeremiahfoster.com/?p=200
SSU = Seamless Software Update:
http://wiki.maemo.org/SSU
This is somewhat similar to `apt-get upgrade`, AFAICT, but just doing individual packages one-at-a-time, ala Hildon Application Manager, instead of all at once like `apt-get upgrade`.
Some further explanation would be helpful. thx :)
jeremiah
12-30-2009, 04:58 PM
Can you explain a bit more WTF you mean?
Sure! :)
Let's say there are lots of people with N810s out there. They want some of the goodies in fremantle, but they don't want to buy a new device.
With the community repo, we can backport stuff, like bug fixes, new libraries, etc. to older devices. By first integrating the software into diablo, testing it, then pushing out a new diablo SSU, we can reach people who want to update their N810 or N800 for example.
All of this done by the community without having to wait for Nokia.
mikkov
12-30-2009, 05:29 PM
aha, title and blog post are missing very important keyword: DIABLO. Without that this doensn't make much sense
fanoush
12-30-2009, 05:32 PM
aha, title and blog post are missing very importantant keyword: DIABLO. Without that this doensn't make much sense
got a bit confused too, additionally this topic is created in "maemo.org > Talk > OS / Platform > Development" so no hint there either :-)
fanoush
12-30-2009, 05:45 PM
If anyone has an SSU to submit, please let me know.
Hmm, is there some testing way for SSU similar to fremantle extras-devel->testing->extras repositories?
What about legal issues like making new initfs image with closed stuff inside?
How's this going? Can I help?
I was reminded recently that I promised to push the community SSU forward as part of my term on council. The crazy months of the N900 release and update, and my own development work, somewhat drowned out this project.
I'm willing to do some testing, and I want to make this happen, so ...
Jeremiah has a repository, so can SD69 and Stskeeps try to pull something together here? Feel free to e-mail me or PM me or whatever to tell me what the problems are.
Jeremiah has a repository, so can SD69 and Stskeeps try to pull something together here? Feel free to e-mail me or PM me or whatever to tell me what the problems are.I sent you a PM
I have set up a new repository on the new infrastructure generously provided by Nokia for community SSU packages. The new repo is not yet public but I would like to test it with some packages and get it ready for when it becomes publicly viewable.
Thanks!
Sorry I disappeared, this month has been mad... I haven't got anything newer than the osso-pdf-viewer package you've already seen, but I'm hoping to have some time to package stuff after FOSDEM.
In the meantime, if anyone feels like having a go here (https://bugs.maemo.org/buglist.cgi?keywords=community-diablo)'s a bunch of patches waiting to be applied.
gerbick
01-29-2010, 10:11 PM
Is it too early to be happy and have hope?
Stskeeps needs to prioritise this. I will have to sit in the lobby of my hotel next week (when I assume the next sprint meeting is happening?) and hassle him. I want a beta-testers version ASAP, and we can begin feeding back to the SSU team.
Stskeeps
01-30-2010, 03:21 AM
Just moving the answer here
I still want to see our Distmaster guide the final bugfix version of Diablo out the door as a community SSU. That acomplishment would put a lot of these angsty threads to rest; people would see that Nokia does help our community support old devices. The next step would be getting Mer into a usable state. Really, it doesn't need to be beautiful or feature packed, but it needs to the basic stuff.
As for all the council quitting bluster -- Whatever. You got a Big Agenda you want to push? Run for council yourself.
Community SSU is TBH, ready to go, we have new servers (finally), a debmaster who is making the repositories, patches to be put into it.
I wasn't doing anything related to this of the sole reason SD69 and lma had taken up the torch of pushing this forward and I'm not for one to take over projects from others. I've been ready for any action items for me to take care of for a long while. But it has all been waiting on new servers and getting actual repository going. The question is then, who's supposed to take leadership of the project?
What I -did- do in the last couple of days was visiting Finland. And discussing several issues related to the community. Such as, how to deal with things legally if we need to drop in a binary package and distribute it, what if I have the shot at patching a closed source package from N8x0 and how to distribute the results. All relevant to community SSU.
As for council quitting bluster, I'm going to assume that was regarding the rucus from the other thread and not based on the quote from my post.
P.S. If anyone wants a exact output of what I've used my 20hours/week on they're more than welcome to ask as I keep track of this.
Community SSU is TBH, ready to go, we have new servers (finally), a debmaster who is making the repositories, patches to be put into it.
Cool :-) I feel that I'm the bottleneck here, but I still very much want this to happen. Apologies, and please bear with me for another week or so.
What I -did- do in the last couple of days was visiting Finland. And discussing several issues related to the community. Such as, how to deal with things legally if we need to drop in a binary package and distribute it, what if I have the shot at patching a closed source package from N8x0 and how to distribute the results. All relevant to community SSU.
Much appreciate thanks :-) A somewhat related question is whether Nokia would be willing to publish fixed-but-not-released packages. But I guess we probably have to prove the community SSU works before we can ask for that :-)
(BTW, if a moderator is reading this can we merge this (http://talk.maemo.org/showthread.php?t=38712) thread?)
Stskeeps, thanks, I'm sorry if I sounded like I doubted that you were doing your job. That didn't cross my mind.
But I believe this Diablo SSU needs to be a top priority here. The Distmaster needs to be the facilitator and help our volunteer leads (lma and SD69) keep the fire lit under this pot. You're the best person for this, you're able to talk to Nokia and get what we need from them to make this a reality...
The comments about the council quitting were related to people insisting that Maemo 6 runs on the N900 and that the council should quit in protest if it doesn't. Complete crazy talk.
(BTW, if a moderator is reading this can we merge this (http://talk.maemo.org/showthread.php?t=38712) thread?)
Done! + 10 chars
Stskeeps
01-30-2010, 05:26 PM
Stskeeps, thanks, I'm sorry if I sounded like I doubted that you were doing your job. That didn't cross my mind.
But I believe this Diablo SSU needs to be a top priority here. The Distmaster needs to be the facilitator and help our volunteer leads (lma and SD69) keep the fire lit under this pot. You're the best person for this, you're able to talk to Nokia and get what we need from them to make this a reality...
The comments about the council quitting were related to people insisting that Maemo 6 runs on the N900 and that the council should quit in protest if it doesn't. Complete crazy talk.
My apologies too - When I say I go with an assumption it doesn't mean I think the intent was malicious, just commenting that I assume it had nothing to do with the quote.
But yes, I agree that SSU should be a priority as this exersise is valuable even on N900 once Nokia gives up on Maemo5 (or at any point in future) and people would like to see continuing fixes.
And I have been taking it as a priority as well. The curse of my role is sometimes the things I do is not visible but will manifest itself in things being easier when we get around to it.
Reason I was pointing out Mer in the other thread was of the sole reason a SSU approach for Maemo6 on N900 probably won't be simple as there is claimed big architectual changes (mentioned at summit)
buurmas
02-05-2010, 02:01 PM
Is it too early to be happy and have hope?
Well, I for one am getting excited!
robers97
02-09-2010, 02:13 PM
[QUOTE=buurmas;345797]My biased list of Diablo bugs that bother me most:
1. Media Player not refreshing (3970 (https://bugs.maemo.org/show_bug.cgi?id=3970)).
2. MicroB certificate problems (349 (https://bugs.maemo.org/show_bug.cgi?id=349), 3792 (https://bugs.maemo.org/show_bug.cgi?id=3792)). It would be nice to use my N810 to access some of my secure company web sites.[/QUOT
I think this is a problem that could be solved with libssl getting a bump. The p12 certificates don't look like they're getting the right treatment even though they are decrypted successfully. This would definitely by my vote. It would be nice to show a vpn of my desktop when I had to go to meetings. I'm sure that would attract a lot of good attention and buzz.
In the meantime, if anyone feels like having a go here (https://bugs.maemo.org/buglist.cgi?keywords=community-diablo)'s a bunch of patches waiting to be applied.
In the interests of avoiding duplicate work: I've applied the patches to osso-pdf-viewer, loudmouth and (mostly, a couple of more tricky ones still pending) busybox and I'll be going after tinymail/modest next.
If anyone wants to help by working on other packages or even just identifying useful patches, by all means feel free :-)
Matan
02-14-2010, 05:42 AM
I wrote a patch for hildon-desktop which makes it send a dbus-signal for every key pressed while the windows list is displayed - description of using this is here: http://talk.maemo.org/showthread.php?t=28004 .
How to get it integrated into the hildon-desktop in new diablo ssu?
Best way to make sure it doesn't get lost: submit it to bugs.maemo.org, making sure the report has the "patch' and "community-diablo" keywords.
Matan
02-14-2010, 06:01 AM
This is a technical answer. There is still a person who maintains hildon-desktop in the community ssu, and it is up to this person to decide if they will include this or not. I do not wish to bother with the technicalities if it is not going to be included.
Stskeeps
02-14-2010, 06:13 AM
This is a technical answer. There is still a person who maintains hildon-desktop in the community ssu, and it is up to this person to decide if they will include this or not. I do not wish to bother with the technicalities if it is not going to be included.
You're assuming there's such a person and that the work won't be structured like wiki work where patches are submitted and added. The idea of bugs.* is that the CSSU people can easily get to the patches that should eventually be merged.
There is still a person who maintains hildon-desktop in the community ssu
Currently there isn't - hey, it could be you :-)
it is up to this person to decide if they will include this or not. I do not wish to bother with the technicalities if it is not going to be included.
Well, the first step to having a patch evaluated is submitting it. I had a quick look and (while I'm probably not the most qualified person to comment) I don't see anything obviously wrong with it apart from the preprocessor conditionals.
any chance one could wrestle a fix for the "no saved networks found" bug out of someone at nokia? or where it never looked at as maemo 5 uses a different system to manage network connections?
maacruz
02-14-2010, 07:34 AM
Just added 3852 (https://bugs.maemo.org/show_bug.cgi?id=3852) to the list.
Ok, I put this off for a while as I didn't have time to respond to questions properly (I still don't actually, so please bear with me) but it's about time we move forward.
So: I've got a temporary signed repository set up, tested it as much as I can on my N800 & N810, and would like to invite some beta testing.
Please only volunteer for this if you accept that these packages come with no warranty and may not be production quality, you have a recent backup and are comfortable reflashing your device.
Note also that this is not the final repository and depending on how testing goes you may have to reflash back to the official 5.2008.43-7 in order to install the "official" community SSU when it arrives (though I will try to avoid that if at all possible).
Unusual configurations (eg bootmenu) and N810W (RX48) owners are particularly welcome, as are people who are willing to review source packages.
If I haven't managed to scare you off yet and you are still reading, PM me and I will reply back tonight with the repository details.
To give you an idea of what to expect (and to avoid repeating the same info in PMs):
Make sure you have not (perhaps unintentionally) removed the appropriate osso-software-version-rxXX package for your device, of if you have re-install it as SSU simply won't work without it.
You will receive the URL of a .install file. Visit it with microb and open it with application manager when prompted. This will install the repository and an enabler package that loads its public key and sets up the package domain with a higher priority than the nokia-system one so that nokia-system packages can be updated.
Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update.
Install the update.
Report any issues here.
Known issue:
If you have -dbg versions of any of the packages in the SSU installed, you will have to uninstall them manually for the update to work. You can re-install updated versions afterwards. Any ideas on how to resolve this are welcome of course.
Changelog:
busybox:
* Fixes: BMO#3917: Missing Large File Support (CONFIG_LFS) in Busybox.
* Fixes: BMO#3951: Incompatible quote handling in Busybox xargs
(FEATURE_XARGS_SUPPORT_QUOTES disabled?)
* Enable FEATURE_XARGS_SUPPORT_ZERO_TERM for consistency with
FEATURE_FIND_PRINT0 (mentioned in BMO#3951/BMO#4248).
* Fixes: BMO#3957: Busybox does not support "ls -Q" which some scripts need.
* Fixes: BMO#3968: grep -r can output corrupt data in error message if file
cannot be read.
* Fixes: BMO#4174: shell history file is overwritten after every command.
* Fixes: BMO#4175: History cross-contamination between concurrently running
shells
* Fixes: BMO#7014: ash saves only 15 lines of history (increased to 100).
* Workaround for BMO#5317: Shell does not save command history / Busybox
doesn't handle SIGHUP properly.
.
loudmouth:
* Fixes: BMO#3455: telepathy-gabble deadlooping
* Fixes: BMO#4119: digest-uri omits the serv-name part causing
authentication failure when host != serv-name
.
modest:
* Fixes: BMO#2553: Please make folder view finger-sized.
* Fixes: BMO#2554: Add "Move to folder" button in main view.
* Fixes: BMO#3004: Modest pops up even when only read messages are in IMAP
inbox.
* Fixes: BMO#3498: Add "Zooming to x%" messages to Modest.
* Fixes: BMO#3941: Signature separator misses trailing space (RFC 3676
violation).
.
tinymail:
* Fixes: BMO#4803: Modest sends empty ENABLE command when IMAP server
advertises ENABLE but not CONDSTORE or QRESYNC capabilities.
.
osso-pdf-viewer:
* Fixes: BMO#2150/NB#76448/NB#120388: PDF Reader doesn't support internal document hyperlinks.
xujun <Jun.Xu@plenware.com>
* Fixes: BMO#2704: PDF Reader needs more zoom levels between 50% and 150%
Sandu Gherbe <pursisimplu2004@yahoo.com>
* Fixes: BMO#2714: Page up should go to Bottom of Previous Page (instead of Top).
yanghua <Hua.Yang@plenware.com>
* Fixes: BMO#4930: PDF Reader doesn't use optimal screen width in fit width mode.
Hauweele Pierre <antegallya@gmail.com>
And of course if anyone feels like packaging some patches not included in the above feel free :-)
gazza_d
03-10-2010, 08:29 AM
LMA Pmed - I'm happy to be a guinea pig on my N800, and if that survives then my N810 may be next....
Thanks for working on this I also would be more than happy to test my n800
maacruz
03-10-2010, 03:49 PM
Please please please, could anybody build a hildon-desktop package with both "lock desktop applets" and the x11vnc patches for the SSU?. Right now, you can have one or another, but not both.
gazza_d
03-10-2010, 05:22 PM
Installed on my N800 without any problems. To be honest I had not noticed or experienced any of the bugs listed the changelog, but "ls -Q" works for starters.
not sure if its a placebo, but after update all seems faster?
Please please please, could anybody build a hildon-desktop package with both "lock desktop applets" and the x11vnc patches for the SSU?.
It will come (in fact it's next on my list), but right now I'm more interested in making sure the update progress works well and there are no surprises so that we can move the SSU to Jeremiah's maemo.org repository and start working on the next one.
not sure if its a placebo, but after update all seems faster?
There are no performance improvements (unless you were affected by the telepathy-gabble deadlooping bug, but that's pathological). If anything I would expect a very slight performance loss due to the updated binaries being a) not prelinked like in the Nokia firmwaer images and b) slightly larger due to the added code. Perhaps it's a side effect of rebooting, if you have for example a desktop or statusbar applet that leaks memory slowly over time. Before I started testing the update process my tablets' uptime was measured in months :-)
maacruz
03-11-2010, 05:31 PM
SSU installed perfectly, in fact, much better than nokia ones in the past, in my quite unusual setup.
Tested busybox ash and osso-pdf-viewer, everything works as expected.
cstryon
03-15-2010, 01:47 AM
Ima, sorry I am not PMing you, i just registered with talk and i think it might not work yet.
I would like to test the community ssu.
This active discussion about furthering the n810 is really exciting. for a short while i got discouraged that i just got this tool and nokia is starting to slow it's support.
Thanks for everyones geeky tendencies!
I would like to test the community ssu.
Thanks. I tried to email you but I'm not sure that was successful (instead of an acklowledgement I was just redirected to the forum home page, but maybe vbulletin is like that). Let me know if you haven't received it.
cstryon
03-15-2010, 11:36 AM
I did get the email Ima. Doing the install now, I will let you know what happens.
I really want to give this a test but I didn't get around to it this weekend... I'll try this week...
lma: I tried it last night on a (nearly) fresh install of whatever the last official Diablo release was (43-7?), and it installed flawlessly. I haven't used my N810 much since then, but I haven't noticed any obvious issues. I'll keep you posted. Should we report problems/bugs here for now?
Also, at some point in the near future, I'll be setting up my normal cloned install with bootmenu on the device, and I'll let you know how that goes if I do it in time.
Cheers
Should we report problems/bugs here for now?
Yes, for now. But since you brought it up, and we briefly discussed this in the bugsquad meeting earlier today: Obviously we want to use bugs.maemo.org, and there are two obvious ways to do it as far as I can see:
Create a new product and handle everything there
Create a new version and use the existing Official platform/Official applications products.
Both approaches have advantages and drawbacks, and I admit I haven't given it much thought yet but what do people think?
pelago
03-17-2010, 06:04 AM
I guess it depends how "official" maemo.org wants to treat this.
Yes, for now. But since you brought it up, and we briefly discussed this in the bugsquad meeting earlier today: Obviously we want to use bugs.maemo.org, and there are two obvious ways to do it as far as I can see:
Create a new product and handle everything there
Create a new version and use the existing Official platform/Official applications products.
Both approaches have advantages and drawbacks, and I admit I haven't given it much thought yet but what do people think?
I haven't been following the community SSU discussion, so I'm not sure about how the hand-over is happening, but if it's listed under the "Official platform/applications" section in the bugtracker, we're essentially redefining "official"; IMO it would be prudent to wait until the community SSU process has all the kinks worked out of it, and then make a proper announcement, before we start referring to it as 5.2008.43-7++. Otherwise we might run the risk of someone "misreading" something and causing another blogospheric incident like we had the other day.
I don't really think option #1 is a viable choice, though, especially in the long term. It would probably cause all manner of confusion - not only in terms of filing bugs, but also confusion over the nature of the community SSU itself - and probably more work for Andre because of that.
Do we (we being the maemo.org team and/or the community at large) have anything currently set up that would work provisionally for bug reporting? I don't mean a full tracker, but a forum thread is a very inefficient and ineffective method for bug reporting. At the very least, why don't we start a new one for testing, and leave this one for discussion?
xopher
03-17-2010, 11:33 AM
I too would like to participate. Sent PM, thanks for your hard work.
EDIT: not fully registered yet, can not PM
buurmas
03-18-2010, 02:16 PM
What version number would we use? My perspective was: Nokia created Diablo, Nokia maintained Diablo, and now Nokia has turned Diablo maintenance over to the community (with some closed-source handcuffs). So I personally would be comfortable with talking about a new Diablo version. For everyone who has it hardwired into their heads that Maemo = Nokia, this could be confusing. But the confusion could be greatly helped by just appending to the version number something like CE for community edition (I like that better than HE). So I like incrementing the Diablo version number and adding something like CE.
Addison
03-18-2010, 04:53 PM
I'm game. :)
Sent you a PM Ima.
What version number would we use? My perspective was: Nokia created Diablo, Nokia maintained Diablo, and now Nokia has turned Diablo maintenance over to the community (with some closed-source handcuffs). So I personally would be comfortable with talking about a new Diablo version. For everyone who has it hardwired into their heads that Maemo = Nokia, this could be confusing. But the confusion could be greatly helped by just appending to the version number something like CE for community edition (I like that better than HE). So I like incrementing the Diablo version number and adding something like CE.
Certainly, I fully agree. I guess I wasn't very clear... What I was trying to say was that taking over the "Maemo Official" Products in BugZilla necessarily means using a bumped version at that time, and that confusion could ensue if uninformed speculation came out of that before the Community SSU was more officially announced. Think of what would be happening right now if Nokia had officially ditched Fremantle, and then a new version number was mentioned somewhere with no prior clarification. That was all I was saying - a matter of timing, not saying it was a bad idea.
if it's listed under the "Official platform/applications" section in the bugtracker, we're essentially redefining "official"
The confusion with the word "Official" could perhaps be avoided by renaming the classifications, but another problem is the QA contacts (which are shared with Fremantle so we can't change them and we don't want to spam Nokia with "our" bugs either).
So, after some consideration I'm leaning towards the separate product option. I propose we create a "community-something" product under Extras, with some pre-defined components based on what patches are currently available, plus a "general" or "other" in case something fresh comes along.
Workflow-wise, should we re-assign the existing bugs to Extras/Community/whatever or clone them?
I don't really think option #1 is a viable choice, though, especially in the long term.
To be honest, I don't see this as a very long term activity. There are only a finite number of contributed patches we can package after all, and I remain hopeful that Mer^2 and/or Meego will provide a more viable distribution for the OMAP2 devices in the long run.
Do we (we being the maemo.org team and/or the community at large) have anything currently set up that would work provisionally for bug reporting? I don't mean a full tracker, but a forum thread is a very inefficient and ineffective method for bug reporting. At the very least, why don't we start a new one for testing, and leave this one for discussion?
You mean something other than bugs.maemo.org? I'd like to avoid that if possible for various reasons (the bugs, discussions and patches are already on bmo, users shouldn't have to create yet another account to file bugs etc).
What version number would we use?
At the moment I'm using the pre-existing versionsing scheme, simply because I didn't want to think too much about it (the testing SSU is '5.2010-09-2" for example, or perhaps it should start with 6?) but it's not cast in stone, ideas welcome. Keep in mind that for all intents and purposes it is a slightly patched Diablo so a radical departure like calling it Elephanta or something would seem misleading/inappropriate.
So I installed the Community SSU Enabler (from the link lma sent me), and it installed cleanly with no fuss into my highly modded multi-boot SD partition.
What do I do now? It isn't clear.
So I installed the Community SSU Enabler (from the link lma sent me), and it installed cleanly with no fuss into my highly modded multi-boot SD partition.
What do I do now? It isn't clear.
The application manager should offer the update after a manual refresh (needed so that it will see the packages with the new priority defined by the enabler package). If it doesn't please clear the log, refresh again and post the contents of the log here (or PM me if you prefer).
I had one report where an SD-booted N800 didn't see the update, but the problem turned out to be that the catalogue.tableteer.nokia.com repositories were configured twice and removing the duplicate repositories fixed it. Not sure why that would happen (both copies had the default 500 priority) or if there's anything that can be done about it.
The confusion with the word "Official" could perhaps be avoided by renaming the classifications, but another problem is the QA contacts (which are shared with Fremantle so we can't change them and we don't want to spam Nokia with "our" bugs either).
So, after some consideration I'm leaning towards the separate product option. I propose we create a "community-something" product under Extras, with some pre-defined components based on what patches are currently available, plus a "general" or "other" in case something fresh comes along.
Your reasoning makes sense.
To be honest, I don't see this as a very long term activity. There are only a finite number of contributed patches we can package after all, and I remain hopeful that Mer^2 and/or Meego will provide a more viable distribution for the OMAP2 devices in the long run.
Okay, I guess I had some misconceptions, then. In that case, you can disregard most of what I said. :P
You mean something other than bugs.maemo.org? I'd like to avoid that if possible for various reasons (the bugs, discussions and patches are already on bmo, users shouldn't have to create yet another account to file bugs etc).
See my previous bit... I was under the assumption that this was longer-term, and that there would be further testing before it was "released" in a larger sense. I thus was just thinking that practically anything would be a better medium for it than a forum. Disregard that too.
Sorry for the confusion.
OK, I figured out my problem. My hacked rotation-enabled (+ fast SD I/O) kernel and xserver-omap are blocking any version of osso-software-version-rx34 from being installed.
Don't suppose you could include those hacks in your version? I do like my rotation...
Addison
03-18-2010, 11:52 PM
Yep. I have the same rotation kernel thingie as qole.
Just go ahead and flash a clean Diablo for this?
You could uninstall (sob! :( ) the beautiful hacked kernel and xserver-omap packages, then install this SSU that will fix the PDF reader. :(
You could then turn around and re-install the hacked kernel, of course.
My hacked rotation-enabled (+ fast SD I/O) kernel and xserver-omap are blocking any version of osso-software-version-rx34 from being installed.
Ah, that would do it :-)
Don't suppose you could include those hacks in your version? I do like my rotation...
Rotation (https://bugs.maemo.org/show_bug.cgi?id=3519) is in the queue (https://bugs.maemo.org/buglist.cgi?keywords=community-diablo). I'm not convinced we should ship the 48MHz SD patch though as that mode isn't officially supported by either TI or Nokia and probably will break things with some cards out there.
But hey, it sounds like you've done the packaging already, can I grab it from somewhere?
Addison
03-19-2010, 12:34 AM
I'll just reflash when I get home later tonight and try out your latest SSU.
Goodbye my sexy looking desktop. Weep. Sob. :(
http://img510.imageshack.us/img510/4966/screenshot2010031900283.png
Oh well, I was thinking of doing a magical Disney theme anyway. :D
Just can't bring myself to hit "Y".
What about an SSU based on the "unlocked" variant of the osso-software-version package?
Millenium-Falcon:~# apt-get install osso-software-version-rx34
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
osso-software-version-rx34: Depends: kernel-diablo-flasher (= 2.6.21-200842maemo1) but 2.6.21-200842maemo1rotationfast is to be installed
Depends: libdb4.2 (= 4.2.52-18osso) but 4.2.52+dfsg-2 is to be installed
Depends: libxcomposite1 (= 1:0.3.1-2) but 1:0.4.0-3 is to be installed
Depends: libxml2 (= 2.6.27.dfsg-1osso4) but 2.6.27.dfsg-1.maemo1 is to be installed
Depends: xserver-xomap (= 1:1.3.99.0~git20070321-0osso20083801) but 1:1.3.99.0~git20070321-0osso20083801rotation is to be installed
E: Broken packages
Millenium-Falcon:~# apt-get install kernel-diablo-flasher=2.6.21-200842maemo1 xserver-xomap=1:1.3.99.0~git20070321-0osso20083801 libdb4.2=4.2.52-18osso libxcomposite1=1:0.3.1-2 libxml2=2.6.27.dfsg-1osso4 osso-software-version-rx34
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
busybox kernel-diablo-flasher libdb4.2 libloudmouth1-0
libmodest-dbus-client libtinymail-1.0-0 libtinymail-camel-1.0-0
libtinymail-gnomevfs-1.0-0 libtinymail-maemo-1.0-0 libtinymailui-1.0-0
libtinymailui-gtk-1.0-0 libxcomposite1 libxml2 modest osso-pdf-viewer
xserver-xomap
Recommended packages:
xml-core
The following packages will be REMOVED
osso-software-version-rx34-unlocked
The following NEW packages will be installed
osso-software-version-rx34
The following packages will be upgraded:
busybox libloudmouth1-0 libmodest-dbus-client libtinymail-1.0-0
libtinymail-camel-1.0-0 libtinymail-gnomevfs-1.0-0 libtinymail-maemo-1.0-0
libtinymailui-1.0-0 libtinymailui-gtk-1.0-0 modest osso-pdf-viewer
The following packages will be DOWNGRADED:
kernel-diablo-flasher libdb4.2 libxcomposite1 libxml2 xserver-xomap
11 upgraded, 1 newly installed, 5 downgraded, 1 to remove and 6 not upgraded.
Need to get 5394kB of archives.
After unpacking 348kB of additional disk space will be used.
Do you want to continue [Y/n]?
lma: I got my kernel stuff from http://outpo.st/rotate
maacruz
03-19-2010, 04:16 AM
Just can't bring myself to hit "Y".
What about an SSU based on the "unlocked" variant of the osso-software-version package?
I think that's a good idea.
What about an SSU based on the "unlocked" variant of the osso-software-version package?
Sounds reasonable. I think all it entails is building osso-software-version-rxXX-unlocked packages (with >= instead of = dependencies), so devices that have an -unlocked variant installed can still update.
It may still break depending on the version numbers of what's installed, and obviously if you have patches that are not in the SSU (eg the fast SD one) you will lose that functionality, but worth doing IMO.
Depends: libdb4.2 (= 4.2.52-18osso) but 4.2.52+dfsg-2 is to be installed
Depends: libxml2 (= 2.6.27.dfsg-1osso4) but 2.6.27.dfsg-1.maemo1 is to be installed
Those come from extras (bad, but at least I think the autobuilder won't let you do that anymore) and are very easy to install accidentally with apt-get upgrade.
Maybe it's worth building a higher-version package just to get rid of the fork.
Depends: libxcomposite1 (= 1:0.3.1-2) but 1:0.4.0-3 is to be installed
That one's interesting, do you know what the differences are from the Nokia version (or at least where it came from)? Just wondering if there's a patch worth packaging there.
lma: I got my kernel stuff from http://outpo.st/rotate
No source package there :-( Oh well, no biggie, there are several other kernel patches to be integrated so it wouldn't save too much work anyway.
rlinfati
03-19-2010, 06:58 AM
the community ssu do not include osso-software-version-rx34-unlocked ?, my system no update
any option before of reflash a fresh diablo ?
nokia800:~# apt-get --reinstall install libdb4.2=4.2.52-18osso libxml2=2.6.27.dfsg-1osso4
[...]
Pacchetti raccomandati:
xml-core
I seguenti pacchetti saranno RETROCESSI (DOWNGRADED):
libdb4.2 libxml2
0 aggiornati, 0 installati, 2 retrocessi (downgraded), 0 da rimuovere e 11 non aggiornati.
[...]
dpkg - warning: downgrading libdb4.2 from 4.2.52+dfsg-2 to 4.2.52-18osso.
[...]
dpkg - warning: downgrading libxml2 from 2.6.27.dfsg-1.maemo1 to 2.6.27.dfsg-1osso4.
[...]
nokia800:~# apt-get install osso-software-version-rx34
[...]
I seguenti pacchetti verranno inoltre installati:
busybox libloudmouth1-0 libmodest-dbus-client libtinymail-1.0-0 libtinymail-camel-1.0-0 libtinymail-gnomevfs-1.0-0 libtinymail-maemo-1.0-0 libtinymailui-1.0-0 libtinymailui-gtk-1.0-0 modest osso-pdf-viewer
I seguenti pacchetti saranno RIMOSSI:
osso-software-version-rx34-unlocked
I seguenti pacchetti NUOVI (NEW) saranno installati:
osso-software-version-rx34
I seguenti pacchetti saranno aggiornati:
busybox libloudmouth1-0 libmodest-dbus-client libtinymail-1.0-0 libtinymail-camel-1.0-0 libtinymail-gnomevfs-1.0-0 libtinymail-maemo-1.0-0 libtinymailui-1.0-0 libtinymailui-gtk-1.0-0 modest osso-pdf-viewer
11 aggiornati, 1 installati, 1 da rimuovere e 2 non aggiornati.
È necessario prendere 2050kB di archivi.
[...]
I'll try (though no promises!) to find some time to create -unlocked packages this weekend.
Depends: libxcomposite1 (= 1:0.3.1-2) but 1:0.4.0-3 is to be installed
That one's interesting, do you know what the differences are from the Nokia version (or at least where it came from)? Just wondering if there's a patch worth packaging there.
That's part of the transparent desktop / random wallpaper experiment. See more about that, including links to the libxcomposite1 package, in this thread (http://talk.maemo.org/showthread.php?t=25452).
I want to try this on my N810. PM me. Thanks
cstryon
03-19-2010, 03:52 PM
I also have a crazy hacked, rotating, external booting, OS. Though I do have an internal flash image that I can boot to instead and test any updates. With my current and preferred method of booting I have noticed no updates. But the enabler was installed with no problems :). Ima, though I have no programing experience, I am happy to let my n810 be a nice crazy config test subject. Let me know if there is anything else I can do to help continue development :).
fixfox
03-19-2010, 04:45 PM
I also have an N810 to test with ..
You can PM me
thanks...
i forgot i have asked before (and cant be assed to go back and look), will the recent improvements to tinymail pop3 support be backported to the community ssu?
will the recent improvements to tinymail pop3 support be backported to the community ssu?
My own brief experiment (https://bugs.maemo.org/show_bug.cgi?id=3387#c54) with using a modern tinymail on Diablo ended in failure, but if you want to point to individual upstream (note: it moved (http://mail.gnome.org/archives/tinymail-devel-list/2010-March/msg00005.html) to http://gitorious.org/tinymail this week) changesets I can have a look. I don't have any real-world POP accounts though so can't do much testing myself.
andoreasu
03-20-2010, 06:35 AM
I also have an n810 here. Would love to test your SSU.
Please pm me.
I can't, and there's no option to contact you by email either. Have you verified your talk.maemo.org account address?
fixfox
03-20-2010, 08:34 AM
I also have an N810 to test with ..
You can PM me
thanks...
Thanks lma..
Community SSU installed without any issues so far.
My own brief experiment (https://bugs.maemo.org/show_bug.cgi?id=3387#c54) with using a modern tinymail on Diablo ended in failure, but if you want to point to individual upstream (note: it moved (http://mail.gnome.org/archives/tinymail-devel-list/2010-March/msg00005.html) to http://gitorious.org/tinymail this week) changesets I can have a look. I don't have any real-world POP accounts though so can't do much testing myself.
sorry, i was just reading the general news for maemo5 updates, and noticed a mention about modest and pop support. Sadly, gitorious do not allow me to search changeset descriptions, or at least i cant find the option at a casual glance, making the job harder then it may need to be.
I was going to suggest using the tinymail.org trac, but it seems the svn repository behind it is now gone. Oh well, when all else fails you can always clone the git repository and search locally :-)
Heads up for testers: I'll be closing access to the repository shortly in order to test some changes (-unlocked variants and a couple of bug fixes) without risking bricking your devices.
fixfox
03-21-2010, 10:15 AM
Heads up for testers: I'll be closing access to the repository shortly in order to test some changes (-unlocked variants and a couple of bug fixes) without risking bricking your devices.
alright.... thanks for the heads-up
It's back now, remember to always take a backup before updating!
fixfox
03-21-2010, 12:07 PM
It's back now, remember to always take a backup before updating!
Completed the update successfully......All settings were retained.
Tested all my usual apps.... No problems so far.
Everything looks good.
cstryon
03-21-2010, 12:42 PM
My Update worked too. Nothing wrong so far. Thanks Ima!
cstryon
03-21-2010, 12:44 PM
Scratch that, everything works fine except Rotate. :/
andoreasu
03-21-2010, 12:53 PM
The application manager should offer the update after a manual refresh (needed so that it will see the packages with the new priority defined by the enabler package).
Sorry, I dont really get the point in reflashing. Is there no other way to enable the SSU?
They are just .deb packages in the repository, right?
Couldnt we just increase the package version to make the package manager update them? :confused:
cstryon
03-21-2010, 12:56 PM
Well, I reinstall xrandr support for Rotate, and that gave rotate back. But now I have "OS2008 community SSU" available to update again. It seems to have replaced the os2008 broken update that I've always had in my app manager after installing Rotate. Update status says "Broken, but able to update".
Saturn
03-21-2010, 01:46 PM
Sorry, I dont really get the point in reflashing. Is there no other way to enable the SSU?
They are just .deb packages in the repository, right?
Couldnt we just increase the package version to make the package manager update them? :confused:
He said refresh not reflash.. could it be that?
BTW, thx LMA for the work you are doing.
andoreasu
03-21-2010, 02:05 PM
He said refresh not reflash.. could it be that?.
:) Yep thats true. I was reading it on my n810 in a hurry. And I totally misread it. :rolleyes:
UPDATE: the graphical update manager can never see updates for me.
but apt-get upgrade lets me upgrade. Although it warns abount unverified packages.
I have to free up some space to do the update though...
But now I have "OS2008 community SSU" available to update again. It seems to have replaced the os2008 broken update that I've always had in my app manager after installing Rotate. Update status says "Broken, but able to update".
the graphical update manager can never see updates for me.
but apt-get upgrade lets me upgrade. Although it warns abount unverified packages.
Application manager logs (Tools -> Log -> Save as) would be appreciated for both cases.
andoreasu
03-21-2010, 06:24 PM
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.
Good to see this:
http://farm5.static.flickr.com/4008/4452852188_da31ae6b8e_o.png (http://http://www.flickr.com/photos/qole2/4452852188/)
maacruz
03-22-2010, 05:19 AM
Upgraded with no problem at all (regullar SSU, not unlocked)
cstryon
03-22-2010, 11:10 AM
sorry about the delay. Here's my log.
8298
Full success updating my very custom OS using the 'Unlocked' variant of the Community SSU!
I AM VERY EXCITED BY THIS.
cstryon
03-22-2010, 10:48 PM
Full success updating my very custom OS using the 'Unlocked' variant of the Community SSU!
I AM VERY EXCITED BY THIS.
Qole, did you have any problems with rotate? Does your OS boot from external?
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.
ok. here is my log - straight from my n810
sorry about the delay. Here's my log.
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?
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.
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.
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.
andoreasu
03-23-2010, 07:16 AM
Um, I posted my log before I updated with apt-get upgrade manually...
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).
Um, I posted my log before I updated with apt-get upgrade manually...
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?
Is this community SSU process going to allow us to re-compile libsdl-mixer1.2 with more features (OGG Vorbis support)
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?
scaler
03-23-2010, 10:44 AM
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 (https://bugs.maemo.org/show_bug.cgi?id=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.
MicroChip123
03-23-2010, 10:54 AM
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?
cstryon
03-23-2010, 10:59 AM
Can you test whether you have any variant of osso-software-version ("dpkg -l | grep osso-software-version") installed?
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.
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.
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"?
fixfox
03-23-2010, 11:15 AM
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?
cstryon
03-23-2010, 11:16 AM
Yes. It's still the same.
Are testers to update ?... is this the one with "rotation support" mentioned a while ago?
No, see post 170 (http://talk.maemo.org/showthread.php?p=578396).
Yes. It's still the same.
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.
cstryon
03-23-2010, 11:34 AM
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."
fixfox
03-23-2010, 11:40 AM
Just did the upgrade ......
can now do..................... " ls -Q "
all is good.
Depends: kernel-diablo-flasher (>= 2.6.21-200842maemo1) but 2.6.21-200835maemo1rotation is installed.
Ah, true: 2.6.21-200835maemo1rotation isn't >= 2.6.21-200842maemo1. Same goes for:
Depends: xserver-xomap (>=1:1.3.99.0~git20070321-osso20083801) but 1:1.3.99.0~git20070321-osso20083101rotation is installed."
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.
cstryon
03-23-2010, 11:59 AM
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?
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?
Try
apt-get install kernel-diablo-flasher xserver-xomap
or, if that doesn't do the trick, with explicit versions:
apt-get install kernel-diablo-flasher=2.6.21-200842maemo1rotationfast xserver-xomap=1:1.3.99.0~git20070321-0osso20083801rotation
(all on one line).
Also, is the newer ones going to uninstall rotation?
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.
andoreasu
03-23-2010, 12:15 PM
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?
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.
cstryon
03-23-2010, 12:32 PM
Lma, that did it. New ssu installed successfully and rotate support is still working. All is well ^_^
It should be a bit faster too (but don't blame me for that) ;-)
cstryon
03-23-2010, 12:39 PM
It should be a bit faster too (but don't blame me for that) ;-)
Rotate is certainly faster. And no more broken packages. Let me know if there is anything else I should test =)
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.
Has anyone tried OHCI (OMAP2 doesn't (http://www.mail-archive.com/linux-omap@vger.kernel.org/msg00975.html) have EHCI), and is it stable? Are there any drawbacks?
xopher
03-23-2010, 02:08 PM
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. :)
...
xopher: will you be selling the puppies?
gerbick
03-23-2010, 05:05 PM
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?
gerbick: it isn't public, you have to PM lma for the details. But he'll gladly send them to you if you ask!
xopher
03-24-2010, 09:40 AM
xopher: will you be selling the puppies?
I tend to be one of them horders you see documentaries about. :)
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?
No arguments against it so far - how do we proceed?
scaler
03-24-2010, 10:04 PM
Has anyone tried OHCI (OMAP2 doesn't (http://www.mail-archive.com/linux-omap@vger.kernel.org/msg00975.html) have EHCI), and is it stable? Are there any drawbacks?
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.
martinsmc
03-25-2010, 12:53 PM
gerbick: it isn't public, you have to PM lma for the details. But he'll gladly send them to you if you ask!
Is possible add bug 3415 ??
Tks
No arguments against it so far - how do we proceed?
I say we go for it. I just emailed Tuomas (and CC'd you, hope that's OK).
Sorry I can't tell you how stable etc. - I'm not that far advanced.
Right. I don't have much time to experiment with this at the moment, but could you add it to the wiki (http://wiki.maemo.org/Diablo_Community_Project) so it doesn't get forgotten? Any links to previous discussions, experiments etc with OHCI would be most welcome.
Is possible add bug 3415 ??
If you mean the workaround from http://wnd.katei.fi/maemo/workaround-3415/ my opinion is no. Reasoning:
the bug affects only a small proportion of devices
the workaround reduces battery life
there's nothing in the community SSU that conflicts with it so N810 owners who want/need it can still have it.
If you mean the workaround from http://wnd.katei.fi/maemo/workaround-3415/ my opinion is no. Reasoning:
the bug affects only a small proportion of devices
the workaround reduces battery life
I fully agree with "no". This workaround helps me to deal with the issue but it's not a fix. In fact, it could be just good old snake oil packed in a pretty Debian package.
martinsmc
03-25-2010, 02:57 PM
If you mean the workaround from http://wnd.katei.fi/maemo/workaround-3415/ my opinion is no. Reasoning:
the bug affects only a small proportion of devices
the workaround reduces battery life
there's nothing in the community SSU that conflicts with it so N810 owners who want/need it can still have it.
Ok,really workaround is not a good solution, tks. I think if any correction to this is Frementale...
My device reboot every day, 2 or 3 times... it is a not good. :(
Tks
rafaelsemx
03-25-2010, 03:33 PM
I installed the community SSU on my N800 yesterday and been testing apps and everything seem to work fine.
scaler
03-26-2010, 05:09 PM
.. could you add it to the wiki (http://wiki.maemo.org/Diablo_Community_Project) so it doesn't get forgotten?
Thank you very much for your willingness to include this in the project. I am not sure that it counts as "low-hanging fruit".
Because of the broken link, I am unable to add the following material to the wiki entry, and I apologize for creating this long post instead. EDIT: Thanks for your guidance on Wiki use in response to this.
In reading Bug 3281 (https://bugs.maemo.org/show_bug.cgi?id=3281) , it is evident that the problem extends beyond cameras to the other devices discussed in http://people.freedesktop.org/~dkukawka/hal-spec-git/0.5.11/hal-spec.html#device-capabilities.
There are standard procedures, described e.g. in http://people.freedesktop.org/~dkukawka/hal-spec-git/0.5.11/hal-spec.html#device-properties-camera, for overcoming the kernel conflicts that arise in desktop distros which have automounting of USB storage devices. These procedures do not work in the MUSB configuration of OS2008, where the drivers for probing endpoint devices are bundled together with automounting drivers in the g_file_storage module.
(The conflicts do not exist in distros without automounting of USB storage.)
gphoto2 runs without problems on the Nokia 770, where USB host mode operates as it does on a desktop computer, through a dedicated host port controlled by OHCI. (It differs from a desktop computer in needing external power for the transceiver, but that is not relevant to the present case.) There is no automounting of USB storage, and therefore no need to configure HAL to recognize the camera as something other than storage.
I suggest that the best hope of resolving Bug 3281 lies in similarly providing an optional OHCI controller that could temporarily replace the MUSB + g_file_storage control in OS2008.
I am not sure that it counts as "low-hanging fruit"
Yeah, it will probably have to wait a while until someone has time to test it.
although I see that someone else has already made wiki entry 2491 (link broken), which describes my reason for making this request.
That's bug 2491 (https://bugs.maemo.org/show_bug.cgi?id=2491), which seems unrelated to USB.
(The cause of the broken links is bug 9736 (https://bugs.maemo.org/show_bug.cgi?id=9736), just replace apps with bugs in the hostname until it's fixed).
I am unable to add the following material to the wiki entry, and I apologize for creating this long post instead.
Feel free to add it to http://wiki.maemo.org/Talk:Diablo_Community_Project
Just pushed another update that includes a patched kernel & xserver. Both my tablets survived it, but you have been warned.
cstryon
03-27-2010, 12:49 PM
updated successfully. no problems. Awesome stuff. what did the patches do?
updated successfully. no problems. Awesome stuff. what did the patches do?
There's a changelog included in the Maemo-Upgrade-Description, but I guess if you've already installed it it's too late to see it so here goes:
kernel-diablo:
* Fixes: BMO#2249: FM Radio frequency not set for use in Japan.
* Fixes: BMO#2491: cant run camera applications with v4l2.
* Fixes: BMO#3123: Patch to kernel to allow DSP framebuffer sharing on N8x0
devices
* Fixes: BMO#3519: Integrate screen rotation patches into stock kernel.
* Changed debian/rules to do a parallel make because Diablo's
dpkg-buildpackage is too old to support -j and I'm lazy.
xserver-xomap:
* Fixes: BMO#3519: Integrate screen rotation patches into stock kernel and X
server.
There are a couple of more kernel patches in the queue (bug 2504 (https://bugs.maemo.org/show_bug.cgi?id=2504) & bug 3243 (https://bugs.maemo.org/show_bug.cgi?id=3243)) but these are not yet integrated as they go into kernel modules and it's pointless to build them until we have some way to update the initfs. I spoke briefly to Stskeeps on IRC earlier this week and it seems (understandably) that a licencing request will not go very far so I'm still pondering how to do it.
The easiest option seems to be to just remount initfs rw temporarily and copy the new modules over the old ones. There's enough free space there on N800/N810 for this to be reasonably safe once or twice, however it's not a good long-term solution and I'm not quite sure about how much free space there is on an N810W. The other option would be to steal the initfs rebuilding stuff from bootmenu to create a fresh jffs2 image and flash it but that's obviously more complicated. If anyone has any other suggestions I'm all ears!
maacruz
03-27-2010, 04:23 PM
The easiest option seems to be to just remount initfs rw temporarily and copy the new modules over the old ones. There's enough free space there on N800/N810 for this to be reasonably safe once or twice, however it's not a good long-term solution and I'm not quite sure about how much free space there is on an N810W. The other option would be to steal the initfs rebuilding stuff from bootmenu to create a fresh jffs2 image and flash it but that's obviously more complicated. If anyone has any other suggestions I'm all ears!
The first option, done carefully, could work fine:
Remount initfs rw
Move the old modules to a backup directory
Check initfs free space
Copy new modules, checking the free space with each, just to be sure.
If there is not enough free space, restore old modules and print error message.
maacruz
03-27-2010, 04:45 PM
If we are going to modify initfs, don't forget this fix https://bugs.maemo.org/show_bug.cgi?id=3852
maacruz
03-27-2010, 06:27 PM
Adding osso-xterm to the wish-list:
I just remembered I have a improved version of osso-xterm. After searching where I found it, I finally arrived to this thread: http://talk.maemo.org/showthread.php?t=23291
The version available in that thread has the transparent vkb hack, but the menu options to enable/disable it aren't checkmenu, so it doesn't shows the current state and I find it too confusing.
I have managed to keep the previous deb package, if the newer is too experimental we could add this one to the SSU. It adds all options but the vkb hack.
Just pushed another update that includes a patched kernel & xserver. Both my tablets survived it, but you have been warned.
After, I installed it I thought that it 12-3 but when I go to the "about" screen l still see 12-1
fixfox
03-27-2010, 08:32 PM
Just pushed another update that includes a patched kernel & xserver. Both my tablets survived it, but you have been warned.
Successfully installed.... Please keep up the good work!
After, I installed it I thought that it 12-3 but when I go to the "about" screen l still see 12-1
Mea culpa (forgot to update the version in /etc/osso_software_version and the post-install script) :-(
I'm now setting those automatically from the package version so it won't happen again.
scaler
03-28-2010, 07:37 AM
That's bug 2491 (https://bugs.maemo.org/show_bug.cgi?id=2491), which seems unrelated to USB.
Sorry about that. I misunderstood "camera apps" to mean "apps involving connection to (external) camera". Turns out it doesn't. Thanks for the working link to Bug 2491, which clarifies that.
Thanks also for instructions on use of Wiki. Sorry again if that was something I was already supposed to know.
cstryon
03-28-2010, 06:52 PM
got the next update. so painless. and i actually read the changelog this time. thanks guys.
I have noticed, and it might just be a placebo, but everything seems...snappier...should it be? I have noticed Rotate is certainly faster, but that may be from the rotate kernal Lma linked me to.
So what are the chance of the os, or maybe just the browser, will be upgrade with the graphics acceleration?
Once again, thanks for all the work and let me know if there is anything specific i should test and report on.
Posted from my N810.
I have noticed, and it might just be a placebo, but everything seems...snappier...should it be?
In your case definitely, since you were running an older kernel & xorg server. There were some significant speedups in 5.2008.43-7 :-)
So what are the chance of the os, or maybe just the browser, will be upgrade with the graphics acceleration?
Not quite ready for end users yet if I'm reading http://talk.maemo.org/showthread.php?t=21697 & http://wiki.maemo.org/MBX_drivers_status right, but maybe someday.
cstryon
03-28-2010, 11:28 PM
I think I found a bug. no particular program I was running. I had it plugged into the charger. It finished charging at some point, wasn't paying attention to the time it finished. when i picked it up I noticed the icons on the left menu were reset to default, icons at the top right were default aswell. advanced power and advanced brightness were gone but the apps were still installed. I'm pretty sure all my apps were still there. There was no rotate icon up in top right, but the power button made it rotate. and rotate settings were still there. Personal launcher and personal menu were gone too. I did a hard reboot and it all went back to my custom setup and nothing was lost. I am attempting to recreate, and will get pictures if it happens again.
when i picked it up I noticed the icons on the left menu were reset to default, icons at the top right were default aswell. advanced power and advanced brightness were gone but the apps were still installed.
That happens when hildon-desktop crashes, usually caused by a misbehaving desktop or statusbar applet. It is restarted automatically, but without any third-party applets loaded to avoid crashing and restarting endlessly.
Which applets were you using? I don't suppose you had syslog or core dumps enabled at the time?
cstryon
03-28-2010, 11:59 PM
I don't know how to enable syslogs or core dumps :/ Can anyone tell me how?. The applets I am running are seqretary, personal launcher, gpecalander, and OMweather.
iirc, the gpecalendar have a history of being unstable. Why two calendars btw?
tho it could also be omweather.
I don't know how to enable syslogs or core dumps :/ Can anyone tell me how?
Sure! For both of these you'll need packages from the tools repository, installation instructions are here (http://maemo.org/development/tools/diablo/#apt-example).
For syslog: "apt-get install sysklogd" (as root). It logs everything to the file /var/log/syslog by default. Standard warning: note that when you don't need syslog, it's best to remove it and rm /var/log/syslog*. Syslog has some log file rotation, but with time it can fill the root filesystem completely. When that's done by a root process, it can become so full that the device fails to boot.
For "rich" core dumps: "apt-get install sp-rich-core" (as root), then "mkdir /media/mmc1/core-dumps". When a program crashes it will generate a "rich core" file in /media/mmc1/core-dumps (which will also include the syslog output if present). See here (http://maemo.org/development/tools/doc/diablo/sp-rich-core/) for more details if you are interested.
If you install these and the crash happens again feel free to send me the rich core dump privately.
The applets I am running are seqretary, personal launcher, gpecalander, and OMweather.
Are you sure that's all? You mentioned at least a couple more previously (advanced backlight & advanced power). One that always crashes for me even on "official" firmware is the desktop version of the statusbar clock applet for instance.
Could you check Control panel-> Panels -> Task navigator, Control panel -> Panels -> Statusbar and Home -> Menu -> Select applets for a complete list?
cstryon
03-29-2010, 11:02 AM
I think I thought applets were the things on the 'desktop', not the status bar, or task navigator. I will see what all applets I am running, and install those apps for syslog and coredump.
I actually haven't done much with seqretary so I can probably just remove that. I should have information for you LMA later today :)
alephito
03-29-2010, 02:39 PM
lma,
I am willing to try the SSU in my N810 booting in a cloned system in a SD card.
Thanks.
alephito
03-29-2010, 04:12 PM
Thanks, Ima.
It installed well (at least that was the message) but how can I verify it? I run ls -Q but It keeps saying "invalid option".
EDIT: I just checked and PDF Reader doesn't show extra zoom levels between 50% and 150% (only 100%).
Then you haven't actually updated, please re-read post #104 (http://talk.maemo.org/showthread.php?p=562413#post562413) carefully.
Another wishlist item from me, which should be easy to fix and will take ~10 kB of extra space (for the joydev.ko file): Joystick Support, so USB joysticks and gamepads can be connected to the Host-mode-having N8x0 devices. Right now, we have to download a binary joydev.ko module from the forums or build the module from source, which is not ideal.
I've created a bug for this and tagged it with "community-diablo": https://bugs.maemo.org/show_bug.cgi?id=9769
Hm, joydev.ko looks to me like something that would be more appropriately packaged in extras: as far as I can tell it's doesn't depend on any other kernel options that are not enabled by default, and nothing else in the "base" distribution depends on it. Feel free to correct me if I'm wrong, of course.
alephito
03-30-2010, 07:51 AM
Then you haven't actually updated, please re-read post #104 (http://talk.maemo.org/showthread.php?p=562413#post562413) carefully.
You were right.
I don't know what was the 'success' message that I got the first time, but now it took me three refreshes to actually see the option to install the SSU. I did it and this time it downloaded the 4.4 Mb and after installing it rebooted my N810.
Everything is working OK. Thanks.
May I suggest to include in the SSU the option to lock the desktop applets? http://talk.maemo.org/showthread.php?p=306950#post306950
Thanks again.
EDIT: I just saw you marked this bug (https://bugs.maemo.org/show_bug.cgi?id=2639). Thanks.
Hm, joydev.ko looks to me like something that would be more appropriately packaged in extras: as far as I can tell it's doesn't depend on any other kernel options that are not enabled by default, and nothing else in the "base" distribution depends on it. Feel free to correct me if I'm wrong, of course.
No, you're right. I'll see what can be done there. Now that you mention it, I've found out that Attila has already created a joydev module for Fremantle, so I'll mail him and ask if he could provide a package for Diablo as well :)
Hey Ima, (if fix available) and you have time please include this very rude bug for N800 owners where popping out camera will not trigger the internet call app and the image will not flip when camera is rotated. Works fine with older maemo versions and for some reason camera behaves normally when booting from mmc?
https://bugs.maemo.org/show_bug.cgi?id=3303
Addison
03-30-2010, 08:17 PM
Hey lma.
Would it be possible to find the reason why Xkbd stopped working correctly under Diablo?
I found a dirty solution, mostly by accident, that you can find in this post.
http://talk.maemo.org/showpost.php?p=408688&postcount=1
The only other bug to mention that I get consistently is always having to slide the volume button just a titch after making or receiving a phone call.
Many others have reported this bug as well.
Thanks for your contributions to Diablo. :)
peremen
03-30-2010, 09:04 PM
ls -Q works, PDF viewer now has 75% and 125% zoom level, control panel's about product points to 5.2010.blahblah, good. I couldn't feel much speedup, though. Firefox Mobile has some second improvement of loading speed.
We may package 3D driver's GPL part into extras if it is usable enough, showing description about non-GPL parts should be manually installed.
Hey Ima, (if fix available) and you have time please include this very rude bug for N800 owners where popping out camera will not trigger the internet call app and the image will not flip when camera is rotated.
Hm, bug 3303 (http://https://bugs.maemo.org/show_bug.cgi?id=3303) seems to be caused by the camera application. Nothing we can do about that, and FWIW it works fine on my N800 running 5.2010.12-4 without camera installed.
Works fine with older maemo versions and for some reason camera behaves normally when booting from mmc?
Do you have the camera app installed on the mmc OS?
alephito
03-31-2010, 09:59 AM
Ima,
I just found out you included the screen rotation hack in the SSU. Thank you very much. I have never been capable of installing it by myself.
rafaelsemx
03-31-2010, 06:49 PM
lma,
I have been testing for the last 3 days the last update with the kernel patches and everything is just great, improvements in PDF and screen rotation are great.
Thanks
I couldn't feel much speedup, though.
Allow me to repeat this for clarity' sake: there are no performance improvements over vanilla 5.2008.43-7. The one person who noticed a speedup was accidentally running a kernel and X server based on an older official release and was missing these optimisations that went into the last Diablo release:
xserver-xomap:
* Add missed part of fb optimisations (fixes: NB#86182).
* fb optimisation by Siarhei (fixes: NB#86182).
* Cherry-pick trapezoid divide-by-zero patch (fixes: NB#87289).
* Add RGB565 Xv support (fixes: NB#86400).
Mgamerz
04-02-2010, 01:53 PM
I know this is a feature request, but is there hope of A2DP for Diablo or must I wait longer for my BT headphones to be useful again?
I installed the latest SSU, so far I notices modest has changed with display for rotation, which works... kind of. It rotates but hildon doesnt like the size and using it is difficult.
Frank Banul
04-02-2010, 02:39 PM
Any chance to add DSP speed tuning? This allows the DSP to be locked to a max frequency of 133 to allow the ARM to stay at 400 when audio is active. This is nice when listening to MP3s and browsing the web.
See here (http://fanoush.wz.cz/maemo/) for details. The kernel is under the section PPTP client and kernel with MPPE support. Then look at N800/810 - IT2008 version 5.2008.43-7 (latest Diablo).
The changes define a tunable, /sys/power/op_dsp, 0 is 400/133, 1 is 330/220.
thanks,
Frank
maacruz
04-02-2010, 07:35 PM
I vote for including the dsp patch
haxality
04-04-2010, 10:51 AM
Thirding the DSP patch. Excellent find, Frank!
Weird; I powered up my second N800, I installed the enabler and then tried to install the unlocked SSU via HAM. It said that all sorts of dependencies were missing. They looked like the contents of the SSU!
So I gained root, did apt-get update and apt-get install osso-software-version-rx34-unlocked so I could send the errors, but everything worked fine... :confused:
cedar
04-05-2010, 12:10 AM
Weird; I powered up my second N800, I installed the enabler and then tried to install the unlocked SSU via HAM. It said that all sorts of dependencies were missing. They looked like the contents of the SSU!
So I gained root, did apt-get update and apt-get install osso-software-version-rx34-unlocked so I could send the errors, but everything worked fine... :confused:
yeah i had to do the same thing to get the community SSU to install on my n810.
not sure whats up with that.
Oh I also had to manually run flash-and-reboot to get the SSU kernel...
Should "about product" report anything different?
Any chance to add DSP speed tuning? This allows the DSP to be locked to a max frequency of 133 to allow the ARM to stay at 400 when audio is active.
No objections to making it tunable, as long as it defaults to the previous behaviour (ie, no surprises to users who don't know/care about it). Anyone feel like isolating that specific patch?
Weird; I powered up my second N800, I installed the enabler and then tried to install the unlocked SSU via HAM. It said that all sorts of dependencies were missing. They looked like the contents of the SSU!
I don't suppose you saved the HAM log?
Oh I also had to manually run flash-and-reboot to get the SSU kernel...
Yeah, that is handled by HAM and won't trigger via an apt-get upgrade.
Should "about product" report anything different?
Just the version number (should start with "5.2010"). /etc/osso_software_version and the output of /usr/bin/osso-product-info should be similarly updated.
I know this is a feature request, but is there hope of A2DP for Diablo or must I wait longer for my BT headphones to be useful again?
What's the current state of the art on this? I don't own such a headset so never paid much attention to the subject and obviously I can't test anything. The only relevant bug seems to be 667 (https://bugs.maemo.org/show_bug.cgi?id=667).
I installed the latest SSU, so far I notices modest has changed with display for rotation, which works... kind of. It rotates but hildon doesnt like the size and using it is difficult.
I'm not sure I understand what you mean, could you provide a screenshot with some explanation perhaps?
vBulletin® v3.8.2, Copyright ©2000-2012, Jelsoft Enterprises Ltd.