Re: Power LED not switching to green even when fully charged
> Hi all, > > I just noticed that even after a night of charging an XO-1.5 the power LED > is still orange and hasn't switched to green (as it did with the XO-1 when > the battery was fully charged). > > I know this is only a tiny detail but I was wondering whether this happens > on purpose or if this might point to some low-level fault or something? Its certainly not on purpose and does not happen on my 1.5's. One of the changes we made to help prevent charge balance was to adjust the "Full" condition to by a taper charge of near 100mA . ( I think the exact number is 116mA) I've noticed a few in some of my power testing runs that some laptops take quite a bit longer to reach full. (This is XO-1 q2e41). I've seen one or 2 take 3 hours. And in at least 1 case I've seen symptoms similar to yours, although I didn't leave it over night. I think the setting might be a bit too low. To check if this is whats happening please grab the latest olpc-pwr-log from http://dev.laptop.org/~rsmith and run it while charging to see what the current is. If its less than 120mA then the next step would be to use bat-debug from OFW in the latest firmware to look at whats going on with some of the EC variables. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OFW RPM packaging
> From memory when I've looked at this in the past it was packaged > within OLPC from the binary download. I've had on my list at one point > being able to follow the instructions to recompile it from source so > it could be included explicitly upstream in Fedora You mean just including the source? Unless you include a build for every machine and every arch I don't see how the binary will be useful in fedora. Building is easy as long as you have a 32 bit machine to compile it on. I have just few very simple scripts that do all the work. > but have never got > around to investigating it further due to time constraints. I think > the KVM people use a OFW release as well so it might be worth looking > at how they compile their version of it. I also wasn't sure what the > signing requirements were of a XO OFW build would be. The .rom file is signed outside of any .rpm stuff. .rpms are just for installing it in the filesystem builds. The signed firmware is just a zip file of the .rom and a signature file. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] GSM/CDMA Modems support (part II)
2009/11/26 Martin Abente > Hello again everyone! > > As I mentioned in my last email to devel@lists.laptop.org, there is a real > need for a GSM/CDMA usb modem support in our region since thats the most > common/available service in rural locations. > > Have you looked at the project RapidSMS, developed with support from Unicef? [1] "RapidSMS is designed to run on any standard computer paired with a standard GPRS modem or certain models of cell phones."[2] I have been lurking on their lists for a while, with my interest in the Sahana Disaster Management System[3], but have gathered that at its core is a python library, pyGSM [4]. I don't know if there is a PyGTK front end. Best of luck! @timClicks [1] http://rapidsms.org/ [2] http://www.rapidsms.org/getting-started/tech-basics/ [3] http://sahana.lk/ [4] http://www.rapidsms.org/code/libraries/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1.5 boot options
Sending out the latest boot options chart. The change is that MEM_ID0 is now used to indicate whether the memory chips used require CL3 or CL4 timing. Regards, wad BootOptions.pdf Description: Adobe PDF document ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: updates.laptop.org now serves F11-for-XO1.5 builds
Hi Christoph, > I assume what it's trying to do is stopping suspend while the > updater is working and not being to do that on the current builds > for one reason or another.) Anyone else seeing that behaviour? That's right -- it tries to inhibit suspend, and OHM isn't running because we haven't turned it on yet. A task for next week. - Chris. -- Chris Ball One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Power LED not switching to green even when fully charged
It is a bug. Please trac it. On Nov 25, 2009, at 7:18 AM, Christoph Derndorfer wrote: > Hi all, > > I just noticed that even after a night of charging an XO-1.5 the > power LED is still orange and hasn't switched to green (as it did > with the XO-1 when the battery was fully charged). > > I know this is only a tiny detail but I was wondering whether this > happens on purpose or if this might point to some low-level fault > or something? > > Thanks, > Christoph > > -- > Christoph Derndorfer > co-editor, olpcnews > url: www.olpcnews.com > e-mail: christ...@olpcnews.com > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: updates.laptop.org now serves F11-for-XO1.5 builds
On Tue, Nov 24, 2009 at 5:45 PM, Daniel Drake wrote: > >From that point, you can upgrade to os46 and onwards using e.g. >olpc-update f11_xo1.5-46 > The command seems to work fine as I'm looking at a "Downloading contents of build f11_xo1.5-46" message right now. However above that one there's another message saying "Error setting OHM inhibit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ohm was not provided by any .service files". (I assume what it's trying to do is stopping suspend while the updater is working and not being to do that on the current builds for one reason or another.) Anyone else seeing that behaviour? Christoph -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: The "missing" olpc-util patches -- review / apply?
On 25/11/2009, at 9:42 PM, Martin Langhoff wrote: > Look at the 4 patches following right after v0.88 here: > http://dev.laptop.org/git/projects/olpc-utils/log/?h=8.2-fixes Reviewed. 3eb8b7e1dc10b00f4125957700a6c51e84313e22 (diskspace fixes from the mysterious v0.89) is already present in os45, and looks fine, the change to sys.exit is expected, and the threshold change looks like tuning. If it was what was shipped, let's keep it. 85d1235147974def0c831f698ebc8a6505d4e2be (Make olpc-session launch a dbus-session before running sugar.) is absent from os45, looks fine, I vaguely recall discussion about it when it was needed. This might also relate to our regression where sugar-xos doesn't run properly on console? 4f68ff11b3c2185710e0924d607e8d5c35c8f922 (Workaround/hack for US(Intl) keyboards in Peru (dlo #9126)) is absent from os45, also looks fine, I don't think we'd want to break upgrades for that small group of laptops. What does Sayamindu think? 8c9f7f196fb270b183a762212894d58f78129f22 (Enable the X Input Method module for Nepali (dlo #9220)), is absent from os45, but looks fine too, same comment as above. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.x, touchpads and papercuts
> On Wed, Nov 25, 2009 at 9:24 PM, Richard A. Smith wrote: > = CL1A "New touchpad" users I've not had the opportunity to do a lot of testing on a bank of CL1A machines but based on all the work I've been doing on 1.5 I suspect that CL1A users are going to run into the "no keyboard" (trac #9453). The difference is that in Gen 1 we don't force the EC to reboot every shutdown so the frequency of this bug may be a lot lower. Fixing will requires back porting my Gen 1.5 code into Gen 1. The port is not hard but testing is. For both CL1 and CL1A firmwares are you interested in the auto power up manufacturing tag? -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OFW RPM packaging
> Hi, > > How did RPM packaging of OpenFirmware work in previous OLPC OS release > cycles? > > Who did it, and how? The person who build/releases the firmware (me or mitch) would modify the spec files we have for the firmware and then build the rpm. Editing the spec file is manual but I have some scripts that automate making and releasing the rpms. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.x, touchpads and papercuts
On Wed, Nov 25, 2009 at 9:24 PM, Richard A. Smith wrote: > I assert that in the absence of controlled regression testing there are no > "low-risk" changes. We are both trolling. Now - changing to productive topics... give me some things we can do on a 8.2.2 release for the 2 groups of users I mention: = CL1 Alps users - better kmod? - pgf proposed an xset command to tweak responsiveness? = CL1A "New touchpad" users - split off psmouse kmod? - kmod or xorg option to disable tapping? m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.x, touchpads and papercuts
> Last time I mentioned I was looking at a simple, low risk 8.2.x > release, Richard and Paul jumped on me with "gotta recompile that > kernel!". Clearly, they are men of mystery, fast cars, women and in > their book, yeah, changing the kernel, low risk mate :-) I assert that in the absence of controlled regression testing there are no "low-risk" changes. My position is based on ROI for this change and not a risk metric. The touchpad issue is a very common problem and not having the driver as a module is a significant barrier to both testing and implementing any attempts we have at fixing the problem. If we go to the trouble of doing a release it seems silly not to make this change. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F11 for the XO-1 Build 9
> Today I have released build 9 for the XO-1. Thanks. I just tried it. The UI hangs in the startup sequence showing the whole little man with one dot below him. It works if I hold down the check-key when booting. Has anybody else noticed this quirk? It's just the UI that's stuck. I can ssh in. What can I do to collect more info? I've seen this on a XO-1 b3 and c2. os8 worked. -- The F9 and F10 keys (dim/un-dim the backlight) don't do anything. - Another quirk: from /var/log/messages Nov 25 01:36:23 xo-02-33-ff powerd: starting Nov 25 01:36:23 xo-02-33-ff powerd: configuring from /etc/powerd/powerd.conf Nov 25 01:36:23 xo-02-33-ff powerd: configured to never shutdown while plugged in Nov 25 01:36:23 xo-02-33-ff olpc-kbdshim-hal[1591]: idle timers set to 120 130 240 Nov 25 01:36:23 xo-02-33-ff powerd: dim in 120 seconds, sleep in 130, blank in 240, then shutdown after 3600 Nov 25 01:38:25 xo-02-33-ff init: powerd main process (1783) terminated with status 1 Nov 25 01:38:25 xo-02-33-ff init: powerd main process ended, respawning That repeats every 2 minutes. After a while, the picture gets blanked but the backlight stays on. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OFW RPM packaging
Hi Daniel, >From memory when I've looked at this in the past it was packaged within OLPC from the binary download. I've had on my list at one point being able to follow the instructions to recompile it from source so it could be included explicitly upstream in Fedora but have never got around to investigating it further due to time constraints. I think the KVM people use a OFW release as well so it might be worth looking at how they compile their version of it. I also wasn't sure what the signing requirements were of a XO OFW build would be. Peter On 11/25/09, Daniel Drake wrote: > Hi, > > How did RPM packaging of OpenFirmware work in previous OLPC OS release > cycles? > > Who did it, and how? > > We need to restart this process for > http://dev.laptop.org/ticket/9573 > http://dev.laptop.org/ticket/9628 > > I'm happy to help out, but knowing what happened previously would be > useful. > > Daniel > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] GSM/CDMA Modems support (part II)
Hi On Wed, Nov 25, 2009 at 1:02 PM, Martin Abente wrote: > On Wed, 25 Nov 2009 17:13:41 +0100, Martin Langhoff > wrote: >> On Wed, Nov 25, 2009 at 3:36 PM, Martin Abente >> wrote: >>> As I mentioned in my last email to devel@lists.laptop.org, there is a >>> real >>> need for a GSM/CDMA usb modem support in our region since thats the most >>> common/available service in rural locations. >> >> Hola Martin, >> >> question: are you planning on giving a GSM/CDMA card to each child >> with an XO? > > No, but teachers and parents has been asking us about this in every > meeting we attended so far > since they only got Internet access at schools. > >> Or to configure the local XS to have a GSM/CDMA connection >> that provides the "upstream" connection which is then shared by all XO >> users that connect to the XS? >> >> If you want to set things up on the XS, we can probably come up with >> scripts that get it online as soon as you plug the modem into the XS. >> (So: unplug to disconnect). >> > > Thats not our case, all our school servers are working with WiMax > connections, which it's infrastructure > requirements are fine for a school. > > But in countries like Paraguay with a high rate of cellphone usage and > coverage (which is an interesting phenomena, > considering our country reality), gsm/cdma modems are by far the most > common and acquirable service. This is also truth for Colombia, satellite internet is very expensive although in some places is offered by the government, and there are GSM/CDMA modems with a broad use and cheaper fares and wider coverage, although with some problems of wideness of the communication band and re-use of the channel. > > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] GSM/CDMA Modems support (part II)
On Wed, 25 Nov 2009 17:13:41 +0100, Martin Langhoff wrote: > On Wed, Nov 25, 2009 at 3:36 PM, Martin Abente > wrote: >> As I mentioned in my last email to devel@lists.laptop.org, there is a >> real >> need for a GSM/CDMA usb modem support in our region since thats the most >> common/available service in rural locations. > > Hola Martin, > > question: are you planning on giving a GSM/CDMA card to each child > with an XO? No, but teachers and parents has been asking us about this in every meeting we attended so far since they only got Internet access at schools. > Or to configure the local XS to have a GSM/CDMA connection > that provides the "upstream" connection which is then shared by all XO > users that connect to the XS? > > If you want to set things up on the XS, we can probably come up with > scripts that get it online as soon as you plug the modem into the XS. > (So: unplug to disconnect). > Thats not our case, all our school servers are working with WiMax connections, which it's infrastructure requirements are fine for a school. But in countries like Paraguay with a high rate of cellphone usage and coverage (which is an interesting phenomena, considering our country reality), gsm/cdma modems are by far the most common and acquirable service. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc-update server selection
On Wed, Nov 25, 2009 at 5:21 PM, Daniel Drake wrote: > So what happens with the default XS if it is contacted over OATS? ... > As far as I can see it will return a valid response with basically no > information, which will cause the current olpc-update code to not check > the other URL. Correct. So my suggestion is to make olpc-update-query check for empty responses in the loop, and keep looping. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc-update server selection
Another approach that I think would work for everyone: Build the URL list with up to 3 URLs, in this order. 1. Value from ANTITHEFT_SERVER_FILE if it exists 2. schoolserver 3. antitheft.laptop.org Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc-update server selection
On Wed, 2009-11-25 at 17:09 +0100, Martin Langhoff wrote: > Ummm. Reading the current code in query(), both in master and in > 8.2-fixes, it will try the local XS and the configured OATS server -- > in that order. If the request to the local XS errors out or returns an > invalid response (non 200) it attempts the next one. So what happens with the default XS if it is contacted over OATS? The laptops are registered and so on, and leases may or may not be available through xs-activation-server, but no key material has been loaded on the XS and it cannot generate leases. As far as I can see it will return a valid response with basically no information, which will cause the current olpc-update code to not check the other URL. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc-update server selection
On Wed, Nov 25, 2009 at 4:10 PM, Daniel Drake wrote: > Going back to recent olpc-update changes... Good timing. I am about to look into olpc-update (to wrap up for 8.2.x). > The current logic of choosing which server(s) to query is not really > suitable for places where the OATS server is not the school server, but > there are school servers online too. Ummm. Reading the current code in query(), both in master and in 8.2-fixes, it will try the local XS and the configured OATS server -- in that order. If the request to the local XS errors out or returns an invalid response (non 200) it attempts the next one. > In these situations there will be a responsive OATS server on the > schoolserver, but the one we want them to contact is at a different > address. With the current logic, the fact that the school server > responds means that the other one is not try. What case are you thinking of? Situations where the local server doesn't know the XO? Or is not running an OATS (in that case, the XS returns 404... and is no prob)? > I propose we change the logic to this: > > - If a server can be read from ANTITHEFT_SERVER_FILE then use it. > (this file will not be shipped in our builds, but deployments can add > it) > - Otherwise default to http://schoolserver > > Then the out-of-the-box configuration will still talk to the school > server, and deployments can override that by creating the > ANTITHEFT_SERVER_FILE when necessary. I prefer to - Try the local XS, and maybe be more eager to retry to the global OATS server if the response is not satisfactory. Trying local first saves bandwidth, and if it errors out, it errors out faster too :-) - Try the antitheft server (if it is configured) of the XS doesn't respond, as we may be at a non-school connection. We want that to happen because it's an important chance to tell a stolen XO that is... stolen. > antitheft.laptop.org drops out of the picture Yep, removing the fallback to antitheft.l.o ok with me. A bit. I am ambivalent about it actually. We lose the ability to help small deployments mark an XO as stolen. I know there is a lot of talk of "getting out of that business", but it _is_ am important aspect of what we do, and our small/midsize deployments care enough about it that some part of OLPC needs to provide some infra for that. (IOWs: there aren't enough Daniels in this world for all of them). Anyway - we'll probably end up making as spin that re-adds 'antitheft.laptop.org' as a configured value. Ah, progress ;-) m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] GSM/CDMA Modems support (part II)
On Wed, Nov 25, 2009 at 3:36 PM, Martin Abente wrote: > As I mentioned in my last email to devel@lists.laptop.org, there is a real > need for a GSM/CDMA usb modem support in our region since thats the most > common/available service in rural locations. Hola Martin, question: are you planning on giving a GSM/CDMA card to each child with an XO? Or to configure the local XS to have a GSM/CDMA connection that provides the "upstream" connection which is then shared by all XO users that connect to the XS? If you want to set things up on the XS, we can probably come up with scripts that get it online as soon as you plug the modem into the XS. (So: unplug to disconnect). cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New F11 for XO-1.5 build 46
http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os46 Compressed image size: 410.31mb (+4.33mb since build 45) Description of changes in this build: * remove SD debugging from the kernel, now that #9702 is root-caused. Package changes since build 45: -kernel-2.6.31_xo1.5-20091123.2010.1.olpc.cf78794.i586 +kernel-2.6.31_xo1.5-20091125.0040.1.olpc.aa06eb3.i586 -kernel-firmware-2.6.31_xo1.5-20091123.2010.1.olpc.cf78794.i586 +kernel-firmware-2.6.31_xo1.5-20091125.0040.1.olpc.aa06eb3.i586 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Recent olpc-utils fixes
On Wed, Nov 25, 2009 at 3:31 PM, Daniel Drake wrote: > Thanks for looking at olpc-utils. 2 comments: > olpc-configure: use /etc/olpc-configure/devkey.html as template if > exists (dlo#9731) > > Just curious, why is a .tmp file used here? Atomicity. echo foo > final_path has some nasty results if yoir process dies or errors out for any reason. Writing to a tmpfile ensures that you only overwrite a potentially existing file once you've completed writing to it. Not that I think _this_ codepath is specially vulnerable. But I am changing this block of code and the added atomicity is a good thing. (Note: for real failsafe atomicity in the face of POSIX, I should add a call to sync. But after the ext4 fallout, rationality is prevailing and the semantics of data=ordered are here to stay.) > olpc-configure: separate upg from firstboot, trigger activity upg > (#9747) > > To fix #9747 I was planning just to remove that code altogether and not > pop up a dialog. It was added in anticipation of G1G1 but (IMO) was > never useful even for those users. For deployment users its just > confusing, and we aren't preparing this OS release for anyone else. I thought of removing it too, but looking at _why_ it was put in place, the rationale behind having it in the first place (#7495) does hold water: if you are managing a large deployment with OATS-triggered upgrade ran by olpc-update, the activities in ~/Activities will need an upgrade. And olpc-configure is the only bit of code that can differentiate a first install vs an upgrade. After it's run This 'fix' is a step in the right direction. If you think of the workflow for deployments there are things we could improve in the rest of the machinery: - olpc-update should be able to include Activities as well. Maybe just .xo files in a directory that are picked up, installed and purged on first boot. - The trigger to update should wait until we are connected to a network - The trigger to update should just get the job done -- if we are on a network and an activity server is available, block the UI and get the job done. but we have what we have. One fix at a time. > Other things in that commit look a bit suspicious. > I think it will reintroduce the problems with SSH files because > update_home_permissions_to_v6 is run after set_home_permissions Ugh, you're right. Fix coming. > And this seems contradictory: > > + if [ -z "$olpc_home_version" ]; then > + ### upgrades only Of course -- I actually fixed that to be -n on the XO where I was testing and then forgot to copy it back to the git repo copy. ID10T error. Fix coming. *Thanks* for the review. > My vote would be to just remove the .sugar-update creation I hope I can convince you that the need behind it exists :-) It was just implemented a bit too broad. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
olpc-update server selection
Hi Martin, Going back to recent olpc-update changes... The current logic of choosing which server(s) to query is not really suitable for places where the OATS server is not the school server, but there are school servers online too. In these situations there will be a responsive OATS server on the schoolserver, but the one we want them to contact is at a different address. With the current logic, the fact that the school server responds means that the other one is not try. I propose we change the logic to this: - If a server can be read from ANTITHEFT_SERVER_FILE then use it. (this file will not be shipped in our builds, but deployments can add it) - Otherwise default to http://schoolserver Then the out-of-the-box configuration will still talk to the school server, and deployments can override that by creating the ANTITHEFT_SERVER_FILE when necessary. antitheft.laptop.org drops out of the picture, but that is not used by any deployment, and if we did want to use it for providing updates info to any possible future G1G1 customers then we could just ship the relevant ANTITHEFT_SERVER_FILE in a G1G1 build. Thoughts? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
GSM/CDMA Modems support (part II)
Hello again everyone! As I mentioned in my last email to devel@lists.laptop.org, there is a real need for a GSM/CDMA usb modem support in our region since thats the most common/available service in rural locations. In my last email I proposed to the OLPC guys to include the "option" module to their builds, _but_ theres another problem concerning sugar connections management. Currently it is not allowed to manage non-802.11 connections. I checked the code at jarabe/model/network.py and I think it needs the proper extensions/changes to at least be able to store other connections types. Would a patch that extends the allowed connection types be accepted in the 0.84 branch (that will be shipped with F11) ? I say "at least" because this would allow other applications that interact with NM (ie via Dbus) to configure/set this device letting us postpone the need to extend the Sugar UI itself. I already wrote a prototype app for this that is actually working on the Gnome environment [1]. What do you guys think? Saludos, Martin Abente (tch) [1] http://trac.paraguayeduca.org/browser/nmbridge ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] GSM/CDMA Modems support (part II)
On Wed, 2009-11-25 at 09:36 -0500, Martin Abente wrote: > Would a patch that extends the allowed connection types be accepted in the > 0.84 branch (that will be shipped with F11) ? Depends on the patch, but in general one requirement I've been putting on patches for OLPCs 0.84 fork is that the patches must already be in sugar master. So this should be your first port of call... Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Recent olpc-utils fixes
Hi Martin, Thanks for looking at olpc-utils. 2 comments: olpc-configure: use /etc/olpc-configure/devkey.html as template if exists (dlo#9731) Just curious, why is a .tmp file used here? olpc-configure: separate upg from firstboot, trigger activity upg (#9747) To fix #9747 I was planning just to remove that code altogether and not pop up a dialog. It was added in anticipation of G1G1 but (IMO) was never useful even for those users. For deployment users its just confusing, and we aren't preparing this OS release for anyone else. Other things in that commit look a bit suspicious. I think it will reintroduce the problems with SSH files because update_home_permissions_to_v6 is run after set_home_permissions And this seems contradictory: + if [ -z "$olpc_home_version" ]; then + ### upgrades only Surely $olpc_home_version would be set on an upgrade? My vote would be to just remove the .sugar-update creation, which I was already planning to do (pending a quick run-by-Chris). As for the rest of your changes in this commit, could you explain exactly what you're trying to achieve? Thanks! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Power LED not switching to green even when fully charged
Hi all, I just noticed that even after a night of charging an XO-1.5 the power LED is still orange and hasn't switched to green (as it did with the XO-1 when the battery was fully charged). I know this is only a tiny detail but I was wondering whether this happens on purpose or if this might point to some low-level fault or something? Thanks, Christoph -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Problem with dracut-modules-olpc-0.2.8 (was: Problem with dracut-modules-olpc-0.2.4)
When I try boot the XO using signed initrd and kernel, initrd doesn't mount the filesystem. The screen displays the message "mouont: you must specify the filesystem type" several times and then shows Can't mount root filesystem Boot has failed, sleeping forever . 2009/11/19 Esteban Bordón > I conected a serial console and XO started normally. > On XO the image is not deleted... > > 2009/11/19 Daniel Drake > >> On Thu, 2009-11-19 at 14:31 -0200, Esteban Bordón wrote: >> >> > >> > Is it this image? >> > >> http://dev.laptop.org/git/users/dsd/olpc-bootanim/plain/images/frame00.png >> > NO >> > >> > >> > Or does the XO man still have his legs? >> > >> > Correct! >> >> OK, then I think you are hitting #9100. A serial console would confirm. >> >> Daniel >> >> >> >> ___ >> Devel mailing list >> Devel@lists.laptop.org >> http://lists.laptop.org/listinfo/devel >> > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
8.2.x, touchpads and papercuts
Last time I mentioned I was looking at a simple, low risk 8.2.x release, Richard and Paul jumped on me with "gotta recompile that kernel!". Clearly, they are men of mystery, fast cars, women and in their book, yeah, changing the kernel, low risk mate :-) Anyway - I am finishing with other aspects of the build and want to see what can we do for: = CL1 Alps users - better kmod? - pgf proposed an xset command to tweak responsiveness? = CL1A "New touchpad" users - split off psmouse kmod? - kmod or xorg option to disable tapping? If we end up changing the kernel, I'll probably issue 2 testing images, one with the old kernel, another with the new kernel, and ask for reports. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
The "missing" olpc-util patches -- review / apply?
Paul, Sayamindu, 8.2.1 released with olpc-util-0.89, which was never in any public git repo and carried 3 patches in the SRPM. Daniel tracked down the .88 to .89 delta a while ago, and yesterday I spotted the 3 patches tucked into the SRPM. Look at the 4 patches following right after v0.88 here: http://dev.laptop.org/git/projects/olpc-utils/log/?h=8.2-fixes This is out of my area of expertise so hoping for hints on wether they're interesting on the F11 track. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OFW RPM packaging
Hi, How did RPM packaging of OpenFirmware work in previous OLPC OS release cycles? Who did it, and how? We need to restart this process for http://dev.laptop.org/ticket/9573 http://dev.laptop.org/ticket/9628 I'm happy to help out, but knowing what happened previously would be useful. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
olpc-configure and upgrades: What to do about ~/isolation? Skipping 802?
Looking at /etc/init.d/olpc-configure -- which handles fixups after upgrades -- questions come to mind: - We are not using Rainbow on our F11 images. If we rm -fr ~/isolation some state will be lost -- for example browser cookies & cache. What other persistent data gets saved there & how important is it? Is it feasible to migrate it with a script? - There is some very unhappy code to handle upgrades from early releases to 802. I'd love to rip it out, but we may want to support deployments that skip 802. We sure have some deployments that are likely skip 802 in some hard-to-reach locations. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Quick guide to ftrace
On 25.11.2009, at 06:52, Chris Ball wrote: > > cjb's quick guide to kernel tracing with ftrace, as used today to > track down #9702: > > mkdir /debug > mount -t debugfs debugfs /debug > cd /debug/tracing > echo function > current_tracer > echo "mmc_*" > set_ftrace_filter > echo "sdhci*" >> set_ftrace_filter > echo "sdio*" >> set_ftrace_filter > echo 1 > tracing_on > echo mem > /sys/power/state > [resume] > echo 0 > tracing_on > cat trace > /root/trace-output Thanks :) I'm slightly embarrassed to admit reading the ticket log was highly entertaining to me. Mysterious from the onset, great buildup to the story, a few suspects, powers lost and regained, a crash of the protagonist, some racy bits thrown in, but in the end the innocuously looking C253 is found guilty. Onward to the happy end ... Great job all, and priceless at the same time! - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
