Re: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
On 01/23/2012 04:20 PM, Mikus Grinbergs wrote: Please (I'm trying to ask nicely!), can you all tell me what I need to tweak to make "customizing the olpc.fth" (plus run 'rpm -U kernel...') be effective on 12.1.0. [ I know how to make them work on 11.3.0. ] Ah.. I misunderstood you. When you said "device" I thought you were referring a to an OFW device tree device, like the device that lets you do MSR access. I didn't realize you were talking about access to the boot partition. I could help you with a firmware issue but I'm afraid I can't help much with 12.1.0. The boot partition is supposed to be accessible via /bootpart/boot or /boot if its not then its just a bug that will get fixed up later. 12.1.0 is still in its infancy. I wouldn't expect much to work for quit a few more builds. Like Martin's e-mail suggested you can open 'olpc.fth' in a small editor under OFW. You can edit the file there and make your changes. No Linux involved. Although I'm not sure if that version of firmware can edit files on the bootpart correctly. There have recently been a bunch of fixes for OFW ext2/3/4 support. Alternatively you could decompress the os image file on a desktop machine, edit the file and then re-compress it. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: fresh Gnash rpms for OLPC XO 1.75
On 01/23/12 15:17, Martin Langhoff wrote: > Without ffmpeg, what is a good test of current gnash? What is a > reasonable expectation of what it can deliver? I start with testing from source, ala "make check". The Gnash testsuite requires many dependences, many of which are not available in Fedora or rpmfusion. A short list is haxe, mtasc, swfmill, and swftools. Then I test with a few SWF files, followed by going to YouTube to make sure it works acceptably. Gnash has decent support for up to swf v9 with AVM1, your mileage may vary... > what's the right way of doing things? and what's a reasonable > expectation of what a lightspark+gnash install can / cannot do? I > didn't find a how-to nor a summary of the state of play... If Lightspark sees an AVM1 (swf versions 5-9), it hands those off to Gnash. That's about all it does. I've looked into Gnash handing off AVM2 (swf v9+) content to Lightspark, but after conversation with the Lightspark developers, that was abandoned as unworkable. We had another ide for integration, but that would be alot of work, and nobody has volunteered to do it. Lightspark uses LLVM and a pile of other stuff, it's got a pretty big footprint. I haven't tried it on the ARM. It does work with YouTube, but I believe support for generic SWF files is a work in progress still. - rob - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
Access to the jffs2 boot partition of the XO-1 NAND Flash is required for any kernel upgrade ... so having it missing should be breaking olpc-update. I expect this will need to be fixed during development of 12.1.0, and when it is fixed your access to the boot partition should be easier. It isn't a matter of hunting down a correct block device. I don't think there should be any block devices for the XO-1 NAND Flash ... they will be mtd or character devices. We did have mtdblock by mistake once, fixed in #11234. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
On Mon, Jan 23, 2012 at 6:03 PM, Mikus Grinbergs wrote: > I will liken "finding out OFW capabilities (and commands)" to "pulling hen's > teeth". When I inquired in 2008, the answer was "read the code". Still > haven't gotten around to doing that. And then January 2012 came, and some lunatic gave you an exact command to type! Man, that's so different! Maybe it even works -- now that'd be a change! ;-) m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
if you don't feel like hunting down the correct
block device on the linux side
But there __is__ no block device defined by the 12.1.0 operating system
when running on the XO-1. { Raw /dev/ubi0, whose partition contains the
root file system, is defined as a character device. } I don't want to
get into making my own major and minor inode numbers, etc., etc.
[ I normally don't run Gnome. When I now switched over to Gnome -- it
saw the same devices (and only those devices) as when running Sugar. ]
you can probably edit it from OFW
I will liken "finding out OFW capabilities (and commands)" to "pulling
hen's teeth". When I inquired in 2008, the answer was "read the code".
Still haven't gotten around to doing that.
Thank you for responding, mikus
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: fresh Gnash rpms for OLPC XO 1.75
Hi Rob, THANKS! I have been personally flat out for the last 2 months or so with 1.75 stuff, hence my high latency. On Sun, Jan 15, 2012 at 11:04 AM, Rob Savoye wrote: > On 10/20/11 03:59, Martin Langhoff wrote: > >> That's really good news! Rob, we can ship you a few more B1 units, if >> that helps make bricking less of an issue :-) > > I just put new rpms for the XO 1.75 in the Gnash repository at > getgnash.org, for anyone that wants to play with a pre-release snapshot. > I assume these will also work on the XO 3.0, although I'd need to do > some work for Gnash to run on the newer version of Android. > >> We are looking into a (partial?) rebuild of the rpmfusion repo to see >> how it works with ffmpeg in. Might take some time... > > I've found the performance better with ffmpeg than gstreamer on the XO > 1.75. I understand the redistribution issues... Any progress on the > rpmfusion repo ? Hopefully we'll soon see ffmpeg rpms to test this in tandem with your rpms. Without ffmpeg, what is a good test of current gnash? What is a reasonable expectation of what it can deliver? Also, I've played with lightspark, which you guys are promoting as a solution for the newer flash formats that gnash won't handle. But in my (brief) expeiment, lightspark didn't "take" -- it didn't install anything runnable in the plugins dir. What's the right way of doing things? and what's a reasonable expectation of what a lightspark+gnash install can / cannot do? I didn't find a how-to nor a summary of the state of play... m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
On Mon, Jan 23, 2012 at 4:20 PM, Mikus Grinbergs wrote: > Please (I'm trying to ask nicely!), can you all tell me what I need to tweak > to make "customizing the olpc.fth" (plus run 'rpm -U kernel...') be > effective on 12.1.0. [ I know how to make them work on 11.3.0. ] As a quick answer -- if you don't feel like hunting down the correct block device on the linux side, you can probably edit it from OFW. Try ok emacs int:\boot\boot.fth Hope the lack of vi does not hurt sensibilities :-) m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
If you ask nicely and give us the necessary failure info I'm sure we can tell you what you need to tweak to make it work again. The problem is that earlier versions had a separate partition on the built-in nand where the olpc.fth script (used by OFW) resided. That partition was defined by the running operating system as _block_ device mmcblk1p1 (on raw device /dev/mmcblk1 - and was mounted (or could be manually mounted) to /bootpart. With 12.1.0 builds, the running system does NOT see any raw device /dev/mmcblk1 (nor any block partition on that device). It does see several raw _character_ devices /dev/mtdx, but I don't know how to access the corresponding partitions (assuming that's what they are). One bypass would be to boot with an USB stick plugged in to the XO-1, which provides a /boot directory with the appropriate olpc.fth in it. Another bypass (which I haven't had time to explore) would be to boot the XO-1 from an USB stick which has an older system version on it, then update the XO-1 nand when mounted within THAT operating system. [By the way, I have not found instructions on how to use the 'tree. tar.lzma' file to fashion an XO bootable (self-contained) USB stick.] Please (I'm trying to ask nicely!), can you all tell me what I need to tweak to make "customizing the olpc.fth" (plus run 'rpm -U kernel...') be effective on 12.1.0. [ I know how to make them work on 11.3.0. ] Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
On 01/23/2012 01:56 PM, Mikus Grinbergs wrote: Although in some cases you can increase the clock frequency a bit and have it still function the system is designed to run at the specified frequency. We didn't use parts that were rated for 1Ghz and then dial it down. We used the highest speed parts that we could get in our cost range and designed for that operating frequency. One data point: Ever since I learned that Mavrothal operated his XO-1s in overclock mode, I've been running all my XO-1s at 460 MHz. [ I run the "heavy CPU load" application 'Timidity' on my systems. That extra 30 MHz noticeably cuts down on the number of dropped notes. ] In three years of running some twenty XO-1s always at 460 MHz (many of those are powered-on 24/7), I have __NEVER__ had any one of them fail. Sure. It will probably work fine in your limited environment but its not guaranteed to do so. Thats the difference. The full range specification for the XO is 0 to 50 degrees C. Our timings are guaranteed to work across that entire range. Again there's no harm in increasing that frequency until you find where it fails and corrupts your data. You can't damage the hardware. p.s. I'm now having difficulty overclocking the XO-1 for 12.1.0, since those builds "hide" the script used by OFW to boot the XO-1 system. The addition of 1.5 and 1.75 into the firmware build trees came with a fair amount of restructuring and refactoring out common things for all XO generations and the arch specific items. I can assure you it was not "hidden" intentionally. If you ask nicely and give us the necessary failure info I'm sure we can tell you what you need to tweak to make it work again. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
Although in some cases you can increase the clock frequency a bit and have it still function the system is designed to run at the specified frequency. We didn't use parts that were rated for 1Ghz and then dial it down. We used the highest speed parts that we could get in our cost range and designed for that operating frequency. One data point: Ever since I learned that Mavrothal operated his XO-1s in overclock mode, I've been running all my XO-1s at 460 MHz. [ I run the "heavy CPU load" application 'Timidity' on my systems. That extra 30 MHz noticeably cuts down on the number of dropped notes. ] In three years of running some twenty XO-1s always at 460 MHz (many of those are powered-on 24/7), I have __NEVER__ had any one of them fail. mikus p.s. I'm now having difficulty overclocking the XO-1 for 12.1.0, since those builds "hide" the script used by OFW to boot the XO-1 system. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Run OFW heat spreader test
On Mon, Jan 23, 2012 at 7:54 AM, Richard A. Smith wrote: > Hmmm... Something else is the problem here. You can't damage the processor > via thermal overload because it has an automatic clock back off. If you > have motherboards that are failing its not due to a bad heat spreader. At > worst all you would get would be hangs. Agreed with Richard -- Sridhar, if you are seeing permanent mb failures, let's get SNs of those motherboards into Reuben's hands for more in-depth diagnostics. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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: Run OFW heat spreader test
Richard (et al.) - Please keep in mind that early ramp units of XO-1.5 were sent to Australia, and they are different (specifically with respect to the heat spreader) than all the production units that follow. - Ed On Jan 23, 2012, at 7:54 AM, Richard A. Smith wrote: > On 01/23/2012 01:32 AM, Sridhar Dhanapalan wrote: > >> On 23 January 2012 17:20, James Cameron wrote: >>> I thought you were doing this test to detect early units that may have >>> a failed heat spreader, and you were doing it at the time of reflashing >>> because that's when you had some control. >> >> Yes, that's the primary reason. Our initial batch of XO-1.5s have an >> inefficient heat spreader. They've been burning out, and replacing the >> motherboards is getting expensive and time consuming. We'd like to >> detect potentially faulty units early, and recommend a heat spreader >> change for them. > > Hmmm... Something else is the problem here. You can't damage the processor > via thermal overload because it has an automatic clock back off. If you have > motherboards that are failing its not due to a bad heat spreader. At worst > all you would get would be hangs. > > Can you acquire the serial number of the failed motherboards or is that not > lost? > > -- > Richard A. Smith > One Laptop per Child > ___ > 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: XO-1 cpu temperature [Devel Digest, Vol 71, Issue 43]
On 01/23/2012 02:56 AM, Yioryos Asprobounitis wrote: The thing is that XO-1.5 has about twice the XO-1 processing power and is quite usable. So getting another 50%+ out of the XO-1 (albeit with risks) may keep it in stride with the new software versions a bit longer. Of course I do realize that this should have nothing to do with OLPC, thus the vague questions ;) It won't work that way. Although in some cases you can increase the clock frequency a bit and have it still function the system is designed to run at the specified frequency. We didn't use parts that were rated for 1Ghz and then dial it down. We used the highest speed parts that we could get in our cost range and designed for that operating frequency. But may be all this is irrelevant now as pushing the XO-1 to 600MHz (extrapolating from "these guys") results in kernel panics and/or errors. If this is because of the protection mechanisms I would appreciate if someone lets me know off-list (I promise not to tell) of a possible way around it. Its not a protection mechanism. Its because one of the system buses is corrupted because its being forced to operate above its design rating. A thermal shutdown will be a hang since the clock to the CPU is stopped. The thermal shutdown is not configurable and you can't bypass it. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Run OFW heat spreader test
On 01/23/2012 01:32 AM, Sridhar Dhanapalan wrote: On 23 January 2012 17:20, James Cameron wrote: I thought you were doing this test to detect early units that may have a failed heat spreader, and you were doing it at the time of reflashing because that's when you had some control. Yes, that's the primary reason. Our initial batch of XO-1.5s have an inefficient heat spreader. They've been burning out, and replacing the motherboards is getting expensive and time consuming. We'd like to detect potentially faulty units early, and recommend a heat spreader change for them. Hmmm... Something else is the problem here. You can't damage the processor via thermal overload because it has an automatic clock back off. If you have motherboards that are failing its not due to a bad heat spreader. At worst all you would get would be hangs. Can you acquire the serial number of the failed motherboards or is that not lost? -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
