Re: Memory replacement
On Friday 11 March 2011, John Watlington wrote: On Mar 9, 2011, at 2:23 PM, Arnd Bergmann wrote: On Wednesday 09 March 2011 17:31:24 Kevin Gordon wrote: go, no-go, spend the extra pennies and get a Class 4/6/8/10 Note that Class 8 does not exist (except fakes) and class 10 is usually not faster than class 6 if you run ext3 on it. Also, a Sandisk card is usually faster than a card from most other manufacturers even if they are one class faster nominally. I'll call BS on that claim. Sandisk cards are all over the map, depending on the controller used internally.Please understand that these manufacturers change controllers all the time --- tests results from nine months ago are invalid. I've tested around a dozen media from them, and while you are true that they use rather different algorithms and NAND chips inside, all of them can write to at least 5 erase blocks before getting into garbage collection, which is really needed for ext3 file systems. Contrast this with Kingston cards, which all use the same algorithm and can only write data linearly to one erase block at a time, resulting in one or two orders of magnitude higher internal write amplification. Most other vendors are somewhere inbetween, and you sometimes get fake cards that don't do what you expect, such a a bunch of Samsung microSDHC cards thaI have I which are labeled Sandisk on the outside. I've also seen some really cheap noname cards outperform similar-spec'd sandisk card, both regarding maximum throughput and the garbage collection algorithms, but you can't rely on that. Arnd ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1 developer key does not work
I am trying to put a permanent developer key on an XO-1. I have been following the steps at http://wiki.laptop.org/go/Activation_and_developer_keys First, I created the key using devkey.html. Then I copied develop.sig to /security on the XO. After rebooting, I still see a wp tag in /ofw/mfg-data. Then I copied develop.sig to /security to a USB drive. Turning the XO on with the drive plugged in makes no difference. If I hold down the tick key while turning on, I get the messages: trying disk:\security\develop.sig Devel key No matching records ... Trying nand:\security\develop.sig Devel key No matching records I tried several FAT32-formatted USB drives, including one that I have used to upgrade to the latest signed firmware. Can anyone help out? Thanks, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 developer key does not work
Posting your machine's serial number as well as then contents of your develop.sig might help; your developer key might be malformed or correspond to a different XO than the one you are trying to use it on. You can also try the collection key method, as one more check on the process by which you are generating the developer key. --Scott On Friday, March 11, 2011, Sridhar Dhanapalan srid...@laptop.org.au wrote: I am trying to put a permanent developer key on an XO-1. I have been following the steps at http://wiki.laptop.org/go/Activation_and_developer_keys First, I created the key using devkey.html. Then I copied develop.sig to /security on the XO. After rebooting, I still see a wp tag in /ofw/mfg-data. Then I copied develop.sig to /security to a USB drive. Turning the XO on with the drive plugged in makes no difference. If I hold down the tick key while turning on, I get the messages: trying disk:\security\develop.sig Devel key No matching records ... Trying nand:\security\develop.sig Devel key No matching records I tried several FAT32-formatted USB drives, including one that I have used to upgrade to the latest signed firmware. Can anyone help out? Thanks, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: os-builder: could we roll a 1.3.1?
On 10 March 2011 23:17, Martin Langhoff martin.langh...@gmail.com wrote: That's completely understood, and I meant to stay the heck away from any risky changes. We're on the same page -- your changes read very sane to me. OK. Pushed all that and the v1.3 branch changes. it just needs testing then we can do a 1.3.1 release. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: [Health] $30 microscope
Love it! Tweeted it! Caryl From: b...@waveplace.org Date: Fri, 11 Mar 2011 13:48:36 -0500 To: cwith...@ekindling.org CC: hea...@lists.laptop.org; devel@lists.laptop.org; cbige...@hotmail.com Subject: Re: [Health] $30 microscope Neat. Cell phone technology? http://www.wired.com/wiredscience/2011/03/diy-cellphone-microscope/ --- Beth Santos Outreach Coordinator Waveplace Foundation Tel: +1 610 797 3100 x 44 Fax: +1 610 797 3199 Cell: +1 603 661 1273 http://www.waveplace.org Waveplace on Facebook Twitter: @waveplace On Fri, Feb 18, 2011 at 10:10 PM, Cherry Withers cwith...@ekindling.org wrote: Finally got my Veho microscope in the mail today (had to cancel the Digimicro order). Followed Kevin's instructions and it just worked auto-magically. Thanks Kevin! So we are good to go for a microscope demo @Scale9x. No dice on the Intel play microscope but not giving up yet. Cheers, Cherry On Jan 20, 2011 3:20 PM, Kevin Gordon kgordon...@gmail.com wrote: Folks: We've been able to get the Veho USB 400x 1.3Mp/2.0Mp interpolated to work on the XO 1 and XO 1.5 under 10.1.3 with 'Cheese'. However, with this high resolution webcam, you just need to make sure it attaches itself to the USB 2.0 bus. If for some reason it comes up and attaches to the 1.1 bus, one gets get what looks like a 1970's color TV test pattern when starting the camera software.. I can't speak to the specifics of the DIgiMicro; we bought a bunch of different microscope samples from various HK based ebay vendors before standardizing on the Veho. It is fully uvc compliant and also works on Ubuntu, Windows and the Mac. On Ubuntu, we use guvcview to control it. Due to the fact we needed to support multi-continent co-curricula, we needed one that ran everywhere on everything. It can cost between $40 and $75 from ebay depending on the day of the week, it seems. Be careful, the one one wants is the '004' product not the '001' or '004'. On the XO, Mikus Grinbergs has since done some magic for us to get guvcview to load on the XO, since guvcview only has an Fc12, 686 RPM. It gets more complicated since some of the dependencies for guvcview need the FC12/686 rpm versions which one has to go out and find manually, while other dependencies need the FC11/586 standard repo versions. For us, we are still in the process of bullet-proofing this so young users can mod their 10.1.3 box to install guvcview. guvcview has way more user-definable parameters than does Cheese. So, for simplicity, one can just install Cheese for now. It works from Sugar if called from the terminal prompt. It wont run properly as root, just stay as default OLPC user., dont know why, dont really care. Personally I run as little as possible as root.A bunch of weird messages come up once invoked from Sugar, but it does eventually come up. It will flash the built-in cafe camera light then proceed over to the USB camera. You can edit the preferences in Cheese to default to the USB camera. If the USB camera isnt seen in teh camera device drop-down, then for some reason it isn't being handled properly at the driver level. In terminal, check the output of the lsusb command, the camera should be seen there with a nice description and USB vendor./eqpt number. Once you are doen in cheese on the the sugar side, unfortunately you have to stop it 'inelegantly'' as it has no sugar activity button. You can use the ctrl-q, or function key back to the activity wheel and kill it from there. However, this seems to leave a little stub up and running, so you may have to reboot to get it going again. On the other hand the successful yum install of cheese puts itself nicely into the graphics submenu on the Gnome side, and behaves nicely there. You can then save your microscope photos ot the fiel system (preferably on an external SD card or a USB stick, then look at the photos from the Sugar side. Just remember INSTALL it as root, but run it as the normal default user. Summary. USB uvc compliant webcams (microscopes) should just plug in and be seen by both the XO 1.0 and XO 1.5. Then yum install cheese, and use the Gnome side to do any 'photos'. All caveats with respect to the snails-pace of the yum install are still in effect ont the 1.0, we do a yum install downloadonly to a stick on a 1.5 (which does yum nicely), then yum localinstall from the stick to all the XO 1.0's to eliminate those install hanging and memory full issues. As an added benefit, Cheese has no other dependencies when installed to 10.1.3. For those who saw our little tech-geek table at the SF summit, this is exactly what we were demoing on the 1.5. Daniel Drake and Paul Fox have since done yeomen effort to bring the uvc, sisusb, and ldusb drivers all back into sync on the 1.0's and 1.5s at 10.1.3 . Have fun, it really is cool stuff. KG O n Thu, Jan 20, 2011 at
11.2.0 development build 13 released
http://wiki.laptop.org/go/11.2.0 http://build.laptop.org/11.2.0/os13 Notable changes: Fedora updates include NetworkManager, avahi, firefox, xulrunner Updated chrome driver fixes rendering bugs Maze updated to v9 Record updated to v89 Stopwatch updated to v6 TamTamEdit updated to v55 TamTamJam updated to v56 TamTamSynthLab updated to v55 Wikipedia updated to v25 WikipediaEN updated to v25 Bugs fixed: #10710 Record: 'i' triggers the description field to hide/show the dialog #10711 olpc-configure: workaround invalid KL #10718 F14: Include rebased xkeyboard patches #10729 Force XO 1.5 Capture audio mixer control to be captured ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 developer key does not work
On 12 March 2011 05:10, C. Scott Ananian csc...@cscott.net wrote: Posting your machine's serial number as well as then contents of your develop.sig might help; your developer key might be malformed or correspond to a different XO than the one you are trying to use it on. You can also try the collection key method, as one more check on the process by which you are generating the developer key. This is a bit strange - I am getting a different result for each method. Printed in the battery compartment is the serial number SHC83102126 /home/.devkey.html contains: SN - SHC8320373E UUID - D5576981-BDA0-4271-ABFE-0183633847D1 /ofw/serial-number contains SHC832038CC laptops.dat (created with a collection key) contains: SHC832038CC C95B2B75-18A6-4860-B834-9AEAC7A4C47F 20110312T034351Z laptops.dat concurs with /ofw/serial-number. I've used the laptop.dat details to request a developer key. The page says that it'll be available in 24 hours. There are three main questions raised by this process: 1. why am I getting different readings for each method? 2. what is the most trustworthy method? 3. why must I wait 24 hours to get the developer key? Thanks, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] XO-1 developer key does not work
why am I getting different readings for each method? My guess is that file /home/.devkey.html was copied in from some other system, and shows the serial number and UUID of the copied-from system. And there is a mis-match between the bottom cover and the motherboard. Since the boot process does NOT look at the label in the battery compartment, the number there does not affect what happens at boot. I myself would trust the collection key values. mikus p.s. When you get file develop.sig (1260 bytes), take a look at the serial number therein (1st record, 2nd token). It should match the serial number printed out by OFW when you boot with the check-button pressed -- if they don't match, that develop.sig will not be recognized. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] XO-1 developer key does not work
On Sat, Mar 12, 2011 at 2:16 AM, Mikus Grinbergs mi...@bga.com wrote: why am I getting different readings for each method? My guess is that file /home/.devkey.html was copied in from some other system, and shows the serial number and UUID of the copied-from system. It would be interesting to investigate how /home/.devkey.html got onto the machine -- ie, what build you used, and how you installed it onto the device -- in order to prevent this problem from recurring. I myself would trust the collection key values. yup. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
