battery: XO1 vs CL1
Some of my batteries have XO1 on them while some others have CL1. Any difference between the two? cheers, Sameer ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] New XO-1.5 10.2.0 build 125 - control panel
On Sat, May 22, 2010 at 14:11, Bernie Innocenti ber...@codewiz.org wrote: El Fri, 21-05-2010 a las 23:01 -0700, Yioryos Asprobounitis escribió: Simple and quite effective :-) Changing MAX_COLUMNS to 4 in /usr/lib/python2.6/site-packages/jarabe/controlpanel/gui.py did the trick. And still has space for (just) one more control. Yes, but this is not general enough. It only happens to work for the 1200x900 display used by the XO-1 and XO-1.5. It would break even there if we change the font size or translate to a language with longer words. Following the grid system that we should be using for layout, columns would have a size expressed in whole cell units and a fixed number of columns would work everywhere, though for wide screens there would be some waste. http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Sugar_Interface/Layout_Guidelines About text, I'm afraid we cannot do anything else than let them wrap if are too long, and just scroll vertically as needed. Regards, Tomeu -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ 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: How can I recover a bum battery?
On Sat, May 22, 2010 at 6:20 PM, Mikus Grinbergs mi...@bga.com wrote: ok batman-start ok bat-rewrite-life That fixed the second battery - when I plugged in the AC power to the XO, the Battery LED first turned yellow, and after a period of charging turned green. I'm concluding the second battery is o.k. Thanks. Cool. Various values may be incorrect until you go through a full discharge/recharge cycle so don't be surprised if when you run on that battery that it doesn't last as long as you expect. If the rewrite does not fix things look at bat-dump-banks again and verify that the values changed. If they did and its still broke then we will have to look at other things. On the first battery, the values did change - but the Battery LED on the XO still stays dark when the AC power is plugged in. [By the way, I have an XO-1.5 B2, if running batman.fth there would help things.] running batman on it won't make any difference but the 1.5 firmware is going to do a much better job of indicating what its unhappy with. Update the 1.5 with the latest firmware and then put the battery in that machine. If the 1.5 does not do anything then I'll want to see what the state machines are doing. I'm not at a place I can look right now but I believe that I have a bat-debug-log or something like that will log what the state machines are doing to a log file on SD or USB. Do you have a serial port? The first series of things see-bstate does after battery insertion would be useful. [on 1.5] remove the battery. ok see-bstate insert battery. Then copy the 1st 5 or 6 lines after the 0 1 2 's stop repeating. -- Richard A. Smith ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: a Git question
El Sat, 22-05-2010 a las 06:33 -0400, George Hunt escribió: Hi everyone, Bruce Bell-Myers offered to work with me on an activity. I created some code and pushed it to sugarlabs git with the results mentioned in the forwarded message. This morning it occurred to me that I may have created a permissions problem for myself. I created my private key as root, and it is stored under /root on my local machine -- so when I'm wanting to push to sugarlabs I need to become root to do the push. Is it possible that the identity I used during the push is not being masked completely on the server, and I'm encountering root squash-like behavior? Nope. All users access the repositories as user gitorious. Permissions and file ownership are the same regardless of what user did the push. You could create another key for your user account and upload it to gitorious. Then, make a new clone from scratch. Alternatively, you could move /root/.ssh/id_rsa* to ~/.ssh/. You could also move the already checked-out repository to your home. In both cases, make sure you change the ownership of all files. Or maybe there is human intervention that I need to request. Anyone have ideas on how I should proceed? If you still have trouble after following the above tips, come to #sugar on irc.freenode.net for interactive support. Besides me, you can find many others who use git regularly. (be patient, it may take some time for people to notice you and respond). -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: battery: XO1 vs CL1
On Sun, May 23, 2010 at 3:16 AM, Richard Smith smithb...@gmail.com wrote: On Sun, May 23, 2010 at 3:51 AM, Sameer Verma sve...@sfsu.edu wrote: Some of my batteries have XO1 on them while some others have CL1. Any difference between the two? Not sure. Whats the serial number of each battery? Are the labels different colors? -- Richard A. Smith OLPC CL1: S/N: 00401080114110001245 Came with XO 1.5 B2 OLPC XO-1: S/N: 00101071120110055061 Came with XO-1 (Mass Production) I take it that batteries are interchangeable across XO1 and XO 1.5? cheers, Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor, Information Systems Director, Campus Business Solutions San Francisco State University http://verma.sfsu.edu/ http://opensource.sfsu.edu/ http://cbs.sfsu.edu/ http://is.sfsu.edu/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: How can I recover a bum battery?
The first series of things see-bstate does after battery insertion would be useful. [on 1.5] remove the battery. ok see-bstate insert battery. Then copy the 1st 5 or 6 lines after the 0 1 2 's stop repeating. I booted the 1.5 on AC (without the battery). Entered 'see-bstate' at the ok prompt - saw string of '0 3' repeating. Inserted bum battery. The Battery_LED on the 1.5 soon changed to yellow. Took the battery out of the 1.5 and put it into the testing XO-1. Battery_LED still yellow when AC power plugged in. Eventually, Battery_LED turned green. I'm concluding this problem battery is now o.k., too. Thanks. Unfortunately, I did not get a chance to copy the output lines (from 'see-bstate') when I inserted the battery - the battery is on one side of the XO-1.5, and by the time I had turned the 1.5 over and located the ctrl and C keys to stop the output, the first lines (upon insertion of the battery) had already scrolled off the screen. Because I noticed that the Battery_LED was no longer dark, I did not repeat trying to capture those first things 'see-bstate' did after battery insertion. My guess is that the better support in the XO-1.5, plus the procedure of inserting the battery *while* 'see-bstate' was running, was enough to kick-start the shadow ram in the battery (which had previously been reset by running 'bat-rewrite-life' on the XO-1). Update the 1.5 with the latest firmware and then put the battery in that machine. If the 1.5 does not do anything then I'll want to see what the state machines are doing. I've got q3a39b in my XO-1.5. If I remember correctly, just putting the bum battery into the 1.5, then plugging in the AC, did not cause the Battery_LED to light up. I have bat-debug-log that will log what the state machines are doing to a log file on SD or USB. Do you have a serial port? Yes, the 1.5 OFW does have 'bat-debug-log'. Does that command take the name of its output file as a parameter? I did not get around to running that command. I do have a serial port (and have used it) - but at the moment, none of my machines has its back off. Thanks for helping me recover my bum batteries. I did not know that 'bat-rewrite-life' (and 'bat-debug-log') existed. How to use them (and other useful commands) is the kind of information that would be helpful to distribute to places where XOs get repaired. [I looked at the DS2756 data sheet - it's NOT a how to get a battery working again guide!] Thanks again, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] New XO-1.5 10.2.0 build 125 - control panel
On Fri, May 21, 2010 at 08:53:58AM -0400, Bernie Innocenti wrote: I've applied the following patch to my builds. It mitigates the problem, at least on the screen size of the XO-1. Tested on XO-1.5 os125 with Sugar 0.84 and Sugar 0.88. Observation and comment: the icons are not evenly spaced across the screen; they are spaced according to the length of the text under each icon. Therefore the grid system is either inapplicable or the text should be wrapped. Incidentally, there's a search entry box on the top left of the control panel which does not do anything. I agree with a later observation that the control panel could take full screen and behave as an activity. Tested-by: James Cameron qu...@laptop.org -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: battery: XO1 vs CL1
On Sun, May 23, 2010 at 10:47:27AM -0700, Sameer Verma wrote: I take it that batteries are interchangeable across XO1 and XO 1.5? Yes. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] New XO-1.5 10.2.0 build 125 - control panel
El Mon, 24-05-2010 a las 08:36 +1000, James Cameron escribió: Observation and comment: the icons are not evenly spaced across the screen; they are spaced according to the length of the text under each icon. Therefore the grid system is either inapplicable or the text should be wrapped. Works fine on 0.88. Incidentally, there's a search entry box on the top left of the control panel which does not do anything. Also works fine on 0.88. Quick, let's backport also the control panel to 0.84! ;-) I agree with a later observation that the control panel could take full screen and behave as an activity. Indeed. I also think we're abusing the centralized control panel concept for settings that could stay closer to the UI element they refer to. For example: * Network should be available somewhere from the neighbor view. * Modem Configuration could become a menu item of the GSM device * Power could become a single checkbox in the battery menu The control panel should really be for global system-wide settings. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: battery: XO1 vs CL1
On 05/23/2010 01:47 PM, Sameer Verma wrote: OLPC CL1: S/N: 00401080114110001245 Came with XO 1.5 B2 OLPC XO-1: S/N: 00101071120110055061 Came with XO-1 (Mass Production) Your batteries only differ by production dates. The 004 is a later run. CL1 is the Quanta model name for the laptop where as we like to call it XO. The newer Li shipping regulations required the battery to have specific markings on it for Wh capacity. I suspect the change happened in response to them. -- Richard A. Smith rich...@laptop.org One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: How can I recover a bum battery?
On 05/23/2010 02:37 PM, Mikus Grinbergs wrote: I booted the 1.5 on AC (without the battery). Entered 'see-bstate' at the ok prompt - saw string of '0 3' repeating. Inserted bum battery. The Battery_LED on the 1.5 soon changed to yellow. Took the battery out of the 1.5 and put it into the testing XO-1. Battery_LED still yellow when AC power plugged in. Eventually, Battery_LED turned green. I'm concluding this problem battery is now o.k., too. Thanks. Most of the reasons XO-1 firmware would silently ignore the battery were just silly. In my large battery refactor (q3a36) many of those went away. that the Battery_LED was no longer dark, I did not repeat trying to capture those first things 'see-bstate' did after battery insertion. No worries. It would only have been useful if it _didn't_ work. I know what happens when works. :) My guess is that the better support in the XO-1.5, plus the procedure of inserting the battery *while* 'see-bstate' was running, was enough to kick-start the shadow ram in the battery (which had previously been reset by running 'bat-rewrite-life' on the XO-1). see-bstate is merely an observer with no influence. The 1.5 firmware simply does a better job at dealing with unexpected values. I've got q3a39b in my XO-1.5. If I remember correctly, just putting the bum battery into the 1.5, then plugging in the AC, did not cause the Battery_LED to light up. Interesting. I've got your snapshots of what things looked like in the failed case. I'll program a battery with those values and see what it does. Yes, the 1.5 OFW does have 'bat-debug-log'. Does that command take the name of its output file as a parameter? I did not get around to running that command. As James says it creates its own log file on whatever media you have as disk which is USB or SD depending on whats discovered. Thanks for helping me recover my bum batteries. I did not know that 'bat-rewrite-life' (and 'bat-debug-log') existed. Rewriting the values is a sledgehammer fix so I don't recommend it without looking at the values first to see whats up. Prior to the ESD discovery it was a mystery where the corruption was coming from and it happens so infrequently that I wanted to see as many cases of it as possible. How to use them (and other useful commands) is the kind of information that would be helpful to distribute to places where XOs get repaired. Indeed. Perhaps you would like to summarize the email exchange and add it to the troubleshooting guide? It could use some updating. Now that the cause of the corruption is known its less of an issue to just rewrite the values. And with LiFe there is little harm. 95% of the values in that eeprom are for the NiMH chemistry and its complex algorithm. The values are updated real time. So overwriting destroys the current state of the battery. In contrast the LiFe algorithm is trival, only a few locations are used and destroying them doesn't really hurt except that your SOC will be out of whack for a while. -- Richard A. Smith rich...@laptop.org One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] New XO-1.5 10.2.0 build 125 - control panel
On Sun, May 23, 2010 at 07:15:54PM -0400, Bernie Innocenti wrote: El Mon, 24-05-2010 a las 08:36 +1000, James Cameron escribi??: Observation and comment: the icons are not evenly spaced across the screen; they are spaced according to the length of the text under each icon. Therefore the grid system is either inapplicable or the text should be wrapped. Works fine on 0.88. evenly spaced was the wrong phrase, sorry. I've tested again on Sugar 0.88, the icons are not regularly positioned horizontally. That is, their centre to centre distance varies. This looks unpleasant to me. Incidentally, there's a search entry box on the top left of the control panel which does not do anything. Also works fine on 0.88. Agreed. I had only typed a, and there was no response. When I type ab the About Me, About my Computer and Network icons remain sensitive, all others are insensitive. Doesn't work on 0.84. Quick, let's backport also the control panel to 0.84! ;-) Yes, good idea. Actually, we could backport all of 0.88 and call it 0.84. Why stop there, why not backport all of 0.90 and call it 0.82? ;-) I agree with a later observation that the control panel could take full screen and behave as an activity. Indeed. I also think we're abusing the centralized control panel concept for settings that could stay closer to the UI element they refer to. Yes, we have a hammer, every problem is a nail. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] New XO-1.5 10.2.0 build 125 - control panel
El Mon, 24-05-2010 a las 09:57 +1000, James Cameron escribió: evenly spaced was the wrong phrase, sorry. I've tested again on Sugar 0.88, the icons are not regularly positioned horizontally. That is, their centre to centre distance varies. This looks unpleasant to me. Oh, I see. Doesn't disturb me so much, at least with the Spanish labels. Wrapping might cause other kinds of difficulties... Anyway, someone should rework this code at least to compute the number of columns dynamically. Now it goes off-screen even with 4 columns. Quick, let's backport also the control panel to 0.84! ;-) Yes, good idea. Actually, we could backport all of 0.88 and call it 0.84. Why stop there, why not backport all of 0.90 and call it 0.82? ;-) Even better, we should never bump the minor release number and sneak new features along with security updates, like Microsoft and Apple always do. Only, their critical updates sometimes happen to bring in new DRM schemes and stricter license enforcement ;-) -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: How can I recover a bum battery?
I do have a serial port (and have used it) - but at the moment, none of my machines has its back off. For your interest, if you have an open wireless access point or a USB ethernet dongle supported by OFW, then you can capture OFW output using another system. The telnetd command starts a TELNET server on OFW and displays the address that should be used. Hmmm. I don't have wireless. If I type in 'telnetd', OFW scans for OLPCOFW, then for school-mesh channels, then gives up. I do have ethernet - but my XO-1.5's OFW (q3a39b) does not appear to recognize my ethernet dongle (SMC 2208) - its built-in LED never lights up. [But the built-in LED on an USB stick (plugged in alongside the ethernet dongle) *does* light up.] Yes, the 1.5 OFW does have 'bat-debug-log'. Does that command take the name of its output file as a parameter? No, it writes to disk:\batdbug.log Back when I tried that command, it gave me an error message about its output file. I must have failed to have an USB stick plugged in. [I'll assume my permanent SD card does not count as 'disk:'.] Thanks for the ideas, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
