Re: Topic in http://wiki.laptop.org/go/Talk:How_to_Damage_a_FLASH_Storage_Device
On 07/26/2013 08:53 PM, peasth...@shaw.ca wrote: If anyone can have a look and give some feedback It would be useful to extend the table to describe even larger capacity cards - prices of large-capacity cards keep coming down. (However, I don't lnow if any XO model would support the latest SD technologies.) mikus p.s. I wrote the example on the main page four years ago. For my XOs, since that time I've formatted more than three dozen SD cards (of different manufacturers) according to that example. All worked well. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Exist any Activity cache that ones must be aware while code/deployment/test cycle an Activity?
On 05/20/2013 09:01 AM, Frank Cancio wrote: or I must do anything else to make sure that the new .py files get execute and not the code inside the files I delete? I myself always delete any created .pyo or .pyc files, as well. [Python creates these from .py files, to speed up execution.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: wifi power on/off
On 04/05/2013 07:55 AM, Paul Fox wrote: someday the card should power down with "ifconfig eth0 down" If the system were to use several (static) self-assigned addresses, and "ifconfig eth0 down" was the way to terminate the use of the current IP address so that the next IP address could be activated - would it be desirable to have the hardware power off on "ifconfig down" ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 13.2.0 development build 2 released
On 03/27/2013 12:32 AM, Hal Murray wrote: On my XO-1, keys F1, F2, F3, and F4 don't do anything. Same for me. Is there any way to get to someplace where I can feed it my WiFi password? More to the point - is there any way to get to get to the 'Home' screen when F3 does not work (neither does the 'Frame' key) ? (I'm thinking there ought to be a CLI command) mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 and 13.1.0 provide absurdly small temporary space
I was unable to reproduce on 13.1.0. My apologies - I wrote without realizing that I haven't experience this with recent 13.1.0 builds (but I do remember it on 13.1.0 - maybe it was on the initial builds). I definitely do currently experience the too-small-tmp-size with my (customized) 12.1.0 build 21. My bypass is to issue 'umount -l /tmp' followed by 'mount -a' - that restores /tmp to the size I have in my fstab. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
12.1.0 and 13.1.0 provide absurdly small temporary space
Since the recent discussion of which release is most reliable for remote deployments, I've started actually putting 12.1.0 to use in place of 11.3.1. One thing I notice is that (despite me customizing /etc/fstab with entries having reasonable "size=" values), on both 12.1.0 and 13.1.0 'df' shows sizes of 1 MB for /tmp and for /var/tmp Apparently *something* (on 12.1.0 and 13.1.0) remounts /tmp and /var/tmp after /etc/fstab gets processed. I tried (on 12.1.0) copying a large file into /tmp - and got the error ""No space left on device". Perhaps this situation contributes to difficulties seen with 12.1.0 mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Auckland Testing Summary 15 November 2012
On 12/15/2012 07:15 PM, Tom Parker wrote: I generally only raise tickets if I have a reproducible problem to report. That said, we should probably raise a ticket complaining about the whole "failed to start" problem, where that message appears even though the activity has started. I've never made any sense of this, it happens quite frequently but I have no reliable steps to reproduce. (I looked at the tracker has many failed to start tickets, but I didn't find one that describes this problem.) I believe the symptom has to do with the presence of multiple windows by an Activity. Sugar starts the initial window - if in time certain things do not happen in that window, the "failed to start" message eventually gets displayed. But if in the meantime the Activity is proceeding in ANOTHER window (e.g., screen) , the eventual message in the initial window is misleading. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 development build 17 released
I have a "permanent" SD card in my XO-1.5 Installed os17 via olpc-update. When it first booted, I issued 'umount /dev/mmcblk0p1'. X restarted. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 development build 8 released
Disclaimer: I am not asking for help; I am sharing my experiences I'm not writing a ticket because I may have affected something by when I did my customizations, but -- XO-1.5 Used 'olpc-update' to go from os7 to os8. Even after third reboot, 'ifconfig' shows the radio has been assigned interface 'wlan0'. mikus p.s. [I do have an ethernet adapter plugged in - but I have a rule in /etc/udev/rules.d/ to designate 'eth1' as the interface for that adapter - and it duly shows up as 'eth1' in 'ifconfig'.] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 build 6 released
Build 6 does not have 'Software update' in 'My Settings' mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Regarding temporary "pauses", perhaps due to using an SD card with an XO
Lately there has been discussion about using an SD card to expand the "storage" capability of the XO. [For instance, discussion of when an XO functions as a server, having it keep its database on an SD card.] What I want to mention is that I experience occasional "pauses" on my XO systems (each has a "permanent" SD card, on which I keep Activities, Linux executables, etc.). I do not know what causes these "pauses", but my best guess is the following (particularly since "pauses" often occur during a CLI command that is "massively" accessing the SD card). My guess: SD cards have an "embedded chip" which is responsible for "wear levelling" the electronic components used to keep the data. It does this by internally 'rearranging' "which data block is physically kept where". I think this 'rearranging' action by the "embedded chip" gets launched (when some 'internal' SD card thresholds are met) during an I/O access by the (XO) host -- and this "rearranging" results in that host's I/O access being DELAYED until the "embedded chip" is done. I have not compared the "performance" (from the user's point of view) of running an Activity "from the SD card" vs. running it "from the XO". But I do have the impression that the duration of the occasional "pauses" which I as a user notice while running "with the SD card" have gotten LONGER as my XOs have migrated to using ever-larger SD cards. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Xo1.5 crashes
On 10/07/2012 03:22 PM, Andres Aguirre wrote: In the case that alan is describing with the XO 1.5 the arduino was connected to the power supply. See if interposing a __powered__ hub between the XO-1.5 and the arduino will make a difference. WARNING: I have encountered powered USB hubs that have VIOLATED the USB specification - they can emit power on the SMALL socket that normally is used for the USB cable that connects to the computer. It is my understanding that only the LARGE sockets are supposed to be able to supply power to the connected device. [I do not know what kind of USB socket the arduino has.] IIRC, Richard warned about connecting an XO's USB socket to any USB device where that devices's USB socket can emit power (that sets up a condition where a non-XO device can try to send power to the XO -- which is a no_no). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Xo1.5 crashes
Since I don't own a cell phone, I've never tried charging from an XO. My external USB storage devices are all self-powered; and my other USB devices (adapters, microscopes, keyboards, etc.) are all low-power devices. In about four years of using XO-1.5s, I haven't ever had the XO-1.5 crash when I dynamically plugged any USB device in. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Completely disable buildt-in WLAN
In 11.3.0 there still was file /sys/power/wlan-enabled, whose content if set to '0' was supposed to disable wireless. Has that function gone the way of the dodo ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Filesystem sizes on XO-1.5 with 12.1.0
DISCLAIMER: I am not asking for help -- I'm sharing ny experiences I often perform 'yum upgrade' - just to pick up the latest fixes from Fedora. But with 12.1.0 on an XO-1.5, I am encountering 'cpio' errors when the upgrade tries to unpack certain packages (e.g., gnome-keyring-3.4.1-3). Since there is no sign of their owners rushing to "fix" such packages, I figure the problem lies at my end. One thing I have noticed with recent (on my XO-1.5) 12.1.0 builds is that filesystems /tmp and /var/tmp are absurdly small. I don't know if this is due to some customization I have applied, or if they come that way with 12.1.0. Anyway, I wonder if "running out of temporary space" might explain the 'cpio' failures (inside 'rpm') I'm seeing. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Shipping bigger fonts by default for greater glyph coverage
Something to watch out for is the content of /usr/lib/locale. Having been caught several time in the past with "C" as the only language recognized, I now pay attention to the content of that directory. [For instance, allowing a Fedora "upgrade" of the package 'glibc-common' could add an extra 80 MB into that directory. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Removing duplication in /boot - affects kernel development
On 09/05/2012 04:46 PM, Daniel Drake wrote:
Installing a new kernel RPM to test a new kernel/initramfs before
it gets shipped in a build (with rpm -Uvh kernel-foo.rpm).
This will continue to install the new kernel as /boot/vmlinuz and the
initramfs as/boot/{actrd,initrd}.img.
The olpc.fth shipped as part of this change will look for the presence
of /boot/vmlinuz, and, if found, will boot directly from that rather
than looking in the zip files and executing the secure boot code as
outlined above.
I'm a user, not a developer. As long as I can upgrade a kernel with
yum/rpm (plus copy), what you've proposed is fine with me.
mikus
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Announcing Q3C09 for XO-1.5
On 08/31/2012 05:14 PM, James Cameron wrote: To eliminate that possibility, please get to the ok prompt, type p2 and describe for me the output At the ok prompt the lights on the USB-ethernet adapter are not lit ok p2 USB2 devices: /pci/usb@10,4/hub@0,0 /pci/usb@10,4/hid@3,1 /pci/usb@10,4/keyboard@3,0 /pci/usb@10,4/mouse@2,0 USB1 devices: /pci/usb@10/device@1,0 ok type boot and press enter. Watch carefully to make sure it says "Loading ramdisk image from" Yes "Loading ramdisk image from pci/sd@c/disk@3:\boot\initrd.img ..." The above is when I have pressed the 'check' button (and boot works) Without 'check', the boot stalls -- just before the panic message is: Please append a correct "root=" boot option; here are the available partitions: b300 7761920 mmcblk0 driver: mmcblk b301 7233536 mmcblk0p1 ---- b302 524288 mmcblk0p2 ---- b308 3872256 mmcblk1 driver: mmcblk b309 65538 mmcblk1p1 ---- b30a 3802624 mmcblk1p2 ---- NOTE: At least once, the last three lines above were omitted. mikus p.s. By the way, you used the phrase "a hub that is incompatible". I have other Belkin hubs (of the same model, and of a different model). They all work with OFW. So believe the phrase ought to be "an individual hub with interesting timings" rather than "a hub that is incompatible". The adjacent XO-1.5, with the same configuration (and the same model Belkin hub) produces the same output from 'p2' and 'boot' - but does not stall without 'check'. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing Q3C09 for XO-1.5
On 08/31/2012 04:03 PM, Samuel Greenfeld wrote: So this a problem with the USB hub and not the network adapter? The hub works fine. With many devices plugged in, including this hub, OFW does not work as I expect. The build DOES work as I expect. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing Q3C09 for XO-1.5
Edit after having written up the text below the divider: Have swapped XO-1.5s, adapters, hubs. The "no root device" kernel panic shows up with q3c09 wherever a particular Belkin F5U 234 (Rev 3) external USB hub is plugged in. [With other hubs, of the same or different models, the problem does not show up.] On 08/31/2012 09:09 AM, Samuel Greenfeld wrote: Open Firmware knows how to use certain types of USB Ethernet adapters in addition to the internal Wifi adapter, and supports accessing files via many network protocols in addition to local means. You can tell OFW to "fs-updatehttp:\\download.laptop.org\xo-1.5\os\candidate\12.1.0-21\21021o1.zd" (with the slashes intentionally backwards) and it would try to get on a network and install the build that way. Does your network provide network-based boot services ? In this instance I was merely attempting to __boot__ the XO-1.5, and had not specified any URLs to the firmware (had not stopped at the ok prompt; had not typed in anything). My assumption is that if I do not explicitly tell the firmware to access an external resource, it will __not__ go looking for one. Is my assumption wrong? Yes, I do have a wireless AP active, which would perform DHCP assignment if contacted. I was relying upon information from the __build__ (once the XO got initialized) -- 'ifconfig' does not show any wireless connection. Are you saying that when I power up, OFW will search for radio signals even when I have not told it to do so ?? The XO is using whatever /bootpart contents os21 installs - including that build's original '/bootpart/boot-versions/21/olpc.fth' file. My assumption is that OFW isn't attempting any "fully network boot". [Besides - how would OFW know the passphrase for the wireless network ?] mikus p.s. By the way, my XO-1.5 configuration is : External SD card plugged in at bottom of XO Contains one data partition (ext2) and one swap partition USB hub plugged in at left side of XO Keyboard plugged in to USB hub Mouse plugged in to USB hub USB ethernet adapter plugged in at right side of XO ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing Q3C09 for XO-1.5
On 08/30/2012 11:53 AM, Samuel Greenfeld wrote: what version of Open Firmware are you using that you are replying to the Q3C09 thread? q3c09 The reason I posted to this thread is -- I did NOT have the described kernel panic when booting os21 on the XO-1.5 with q3c08 What make and model of USB Ethernet adapter are you using? SMC2208 Do you think this matters? I have been using these USB ethernet adapters for four years now, and have never had any problems using them (on XO-1 and XO-1.5) with any build. [In the past I sometimes have had firmware failures (particularly with q2b firmware - which sometimes would "hang" in the firmware when I was trying to boot (unless the USB ethernet adapter was unplugged from the XO before the XO was booted).] I could not hang a XO-1.5 with os21 & Q3C07 (included in the build) I flash new firmware as it becomes available, independent of the build. [Note that os21 boots fine on the XO-1.5 with q3c09 if I press the front panel 'check' button -- it only gets the panic message if do NOT press any front panel buttons.] Does your network provide network-based boot services ? No. When I am using an ethernet-based LAN, that network provides __NO__ services - not even DHCP. But I think this question is irrelevant - the described panic occurred while trying to load kernel software -- long before the build would get around to attempting any initialization of network services. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing Q3C09 for XO-1.5
With my setup I can only boot os21 on an XO-1.5 with the front panel 'check' button pressed. If I try to boot without pressing any buttons, the boot process gets a kernel panic: "Unable to mount root fs on unknown-block(0.0)". [There is also a message "RAMDISK: Couldn't find valid RAM disk image starting at 0."] If I unplug my USB-ethernet adapter from the XO-1.5 before booting, the boot process runs correctly even when I do not press any panel buttons. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] long-press touch actions in Sugar
Sridhar wrote: It appears that long-press is becoming part of the Sugar user experience on touchscreens: In my opinion the XO product is notably limited in that its front panel "buttons" will only register a 'press'. The opportunities for use of the XO in e-book configuration would be greatly enhanced if those front panel "buttons" were able to register 'long press' as well as 'press'. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Migrating XO-1.75 to device tree - upgrade considerations
I do not have an XO-1.75. But with other XO models, I update firmware INDEPENDENTLY of updating the distribution, and update the kernel INDEPENDENTLY of updating the firmware or the distribution. Surely I am not alone in the world in doing so. If stable (old) kernels will not boot with development (new) firmware, I suggest adding two warnings to the new firmware: 1. Whenever the new firmware is flashed INDEPENDENTLY of the distribution, somehow insert a new "emit" step into the installation process, to emit the following message: "WARNING: This ROM q4z00 will not allow 12.0.0 or earlier releases to boot". Then the person doing the install will at least have been warned. 2. Add a new flag to every distribution that requires the new firmware. Whenever the new firmware is used to flash a distribution, if that distribution does not have that flag, refuse to perform that install, and have the new firmware emit: "ERROR: Install of File 21099o2 not supported." 3. Whenever a new distribution (requiring the new firmware) is flashed INDEPENDENTLY with the old firmware, the person doing the install would be left to recover on his own. The release notes for the new distribution should document what the person doing the installer would see (given such a situation) when he tries to boot the system - and should explain that the new firmware must be installed. Optionally the new distribution could have code added to it, so that when the boot process fails for lack of the DT - to tell the person doing the install that a new firmware must be installed in order to run that distribution. [If you are adding code to the new distribution, you might instead include a "basic" DT to allow the new distribution to boot anyway.] 4. Whenever someone installs a new kernel INDEPENDENTLY of the firmware and of the distribution, and the system subsequently does not boot -- TOO BAD. [The new release notes should warn that a "mismatch" __WILL__ render the system non-bootable.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 release candidate 6 (build 19) released
On an XO-1 system with wireless working on os19 (but customized with additional rpms) -- after each reboot I find /etc/resolv.conf to have been reset to dummy (nonworking) content (even though the wireless link itself had been automatically reconnected). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 release candidate 6 (build 19) released
I'm surprised that os19 omits 130+ updates that have been made to Fedora 17 in the last month. Did you do a lot of regression testing with os18 that you do not want to repeat ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: compiled to .XO
We are also able to run the binary, but I am unclear about
how we would package this into a .xo activity. Any pointers?
Am attaching an copy of an email I sent earlier to someone with a
question similar to yours. IMHO that email provides a concise how-to
guide to fashioning a bare-bones .xo package.
[Obviously, your 'exec' line must be appropriate to your binary.]
[The example had a library which was explicitly linked-to from within
that binary. If your binary does not need any special library, just
leave out the library part from the attached instructions.]
[If your binary *does* need to be supplied with a specific library, move
that library into (for example) the subdirectory itself, then add this
line (without the >) before your 'exec' line
> export LD_LIBRARY_PATH=$SUGAR_BUNDLE_PATH/your-library-name
to indicate *where* that library can be accessed.]
To produce the .xo file, just 'pack' the subdirectory you created.
mikus
Here is one way to package your stuff so it can be launched from an icon
in the XO's Home View:
DISCLAIMER: To set this up, I used my templates from 2009 (for
"sugarizing" a Linux executable). I have __NOT__ referenced (nor
incorporated) any SugarLabs advances from any intervening years.
1) Create a directory (either in /home/olpc/Activities, or linked-to
from there). Mine was called "Evil.activity".
In 'Evil.activity', create subdirectories 'activity' and 'bin'
2) Move your binary into 'Evil.activity/' [I called it 'evil.eng'}
Move your 'id1' directory into 'Evil activity/'
Note: 'Evil.activity' now contains:
activity{a directory}
evil.eng{a binary}
bin {a directory}
id1 {a directory}
Move your 'icon.svg' into 'Evil.activity/activity/'
3) Add file 'Evil.activity/activity/activity.info' with content:
> [Activity]
> name = Evil
> service_name = com.atphalix.evil
> exec = runevil
> icon = icon
> activity_version = 1
> host_version = 1
[Note: This is how it was in 2009. I have not looked at whether
"activity.info" lines have been added/removed since then.]
[In the above, you get to choose "name" and "service name"]
'runevil' is the name of the script in 'Evil.activity/bin/'
4) Copy 'libsugarize.so' into 'Evil.activity/bin/'
Add file 'Evil.activity/bin/runevil' with content:
> #!/bin/bash
> while [ -n "$2" ] ; do
> echo "OO:" $1 $2
> case "$1" in
> -b | --bundle-id) export SUGAR_BUNDLE_ID="$2" ;;
> -a | --activity-id) export SUGAR_ACTIVITY_ID="$2" ;;
> -o | --object-id) export SUGAR_OBJECT_ID="$2" ;;
> -u | --uri) export SUGAR_URI="$2" ;;
> *) echo unknown argument $1 $2 ;;
> esac
> shift;shift
> done
> export LD_PRELOAD="$SUGAR_BUNDLE_PATH/bin/libsugarize.so"
> export NET_WM_NAME="Evil"
> exec ./evil.eng -mem 64 -width 1200 -height 900 +map start
> exit
Obviously, the names/locations specified in this script must
correspond to what is in your "Evil.activity" directory.
[And when you create the two files whose content is shown above,
please leave off the "> " (they're for clarity in the printout).]
For me, the above worked. [With an old libsugarize.so, there might be a
redundant launch screen (with error message) left over. It's harmless,
and can eventually be closed.]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: XO battery/performance
DISCLAIMER: I am not asking for help; I'm merely sharing my experiences I have an XO-1 which with recent q2f roms might boot up with the power light green, or might boot up with the power light blinking red (and the battery icon in Frame claiming "not connected"). The last time it booted up with a blinking red power light, I kept on using that XO-1 "as is". After 100+ hours of operation (it *was* connected to A/C all the time) the behavior of that XO-1 was perfectly NORMAL (except for the blinking red power light). I have since twice booted that XO-1 -- both times the power light came up green (as it should). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Outdoor Light Sensor
Please also take into account the possible influence of the user's "hand position". I've seen tablets where the display illumination changes as the user shifts how he holds the unit. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Recent XO-1 OFW had difficulty reading USB stick
I'm curious, why do you have security enabled? Because that's the way they were shipped to me from the factory (or from whoever I purchased the unit from). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Recent XO-1 OFW had difficulty reading USB stick
DISCLAIMER: I am not asking for help; I'm just sharing my experiences.
With q2f11.rom on one of my vintage-1997 XO-1s, I could __not__ install
('copy-nand') os12 (12.1.0) from an USB stick -- sooner or later OFW
always stopped on a "file read error". I finally flashed q2f05.rom to
that XO-1. Then the 'copy-nand' ran flawlessly (same USB stick).
mikus
p.s. I also tried q2f11jb.rom - and nearly bricked the XO-1 (I do not
have security deactivated). Turns out q2f11jb would __not__ read my
"permanent" SD card (which has file develop.sig on it). And the
previous (failed) install attempt had erased develop.sig from nand.
Lots of fun trying to replace the q2f11jb rom with a rom that would stop
at the ok prompt.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
XO-1 SD card access during boot-up
DISCLAIMER: I am not asking for help; I'm sharing my experiences. Encountered an interesting situation on one XO-1 with os11 (12.1.0): On completely random occasions, the boot-up sequence stops because of i/o errors on device mmcblk0. Without making any changes whatsoever, the very next boot-up runs fine. [EDIT: I've now put os12 on that system. Problem has not re-occurred.] [I've discussed with Kevin the question of "when during boot-up is it a good time to mount an SD card?" In my case, I need Sugar to find resources located on that card -- so I need that card to be already accessible when Sugar is starting up.] For three years now, as part of my XO customization I've had an initialization script in /etc/rc.d/init.d/ that issues an explicit 'mount' of my "permanent" SD card -- and that script has always worked well. [For historical reasons, my mount point is to a subdirectory in /media.] Now I'm starting to see these random errors after that script is installed. [I've reinstalled os11 on that system several times from scratch -- since the problem keeps coming back it is NOT due to an operator mistake while installing.] The closest I have to a clue is that /media appears to be empty. I'm speculating that after my initialization script tests for the existence of my mount point subdirectory (and creates that subdirectory if need be), something is wiping /media. And that the 'mount' command (or a subsequent bash 'test -f' command) is getting errors because the inode it looks for is not present. [I don't think the errors occur before my initialization script gets run. If the system were accessing the SD card, it would do so whether my script was there or not. Yet the errors only show up after my script has been installed - so its presence must have an influence.] So far, I've put os11 on only a couple of XO-1s. This is the only system on which I'm having this problem. I'm guessing that there is some sort of a race condition - such that ordinarily my mount point subdirectory gets left alone after my initialization script has created it. But on random occasions with this particular system, something seems to be happening WHILE my initialization script is running -- and that interference results in my customized boot-up sequence now seeing i/o errors with device mmcblk0. mikus p.s. [If this problem persists, I'll experiment with allocating my mount point elsewhere. But that means changing a number of scripts -- I don't want to make such modifications unless absolutely m=necessary.] pps. This is one of the XO-1 systems on which I can get randomly occurring "Bad read of .img file" messages while using 'OFW to copy-nand' a build image from an USB stick. The same USB stick works well with "non-sensitive" XOs. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Booting XO-1 with SD card occasionally hangs on I/O timeouts
Is this an interesting problem? It only happens occasionally, say 1 out of 100 times. Over the years, I've always had a "permanent" SD card in all my XO systems (many dozens of SD cards in all). The SD cards have one ext2-formatted data partition, plus a swap partition. I can NEVER recall any incident where I could attribute "failure to boot" to the SD card. [Note that if an XO fails to boot, I normally don't get to see the /var/log/messages from that boot attempt.] My experience with "failures to boot (after getting past OFW)" is that they occur 10 out of 10 times (not 1 out of 100). I've had a handful of incidents where the SD card became "dead" - (electrically unresponsive) - but the XO would still boot - it would just not "see" the SD card. In general, an XO with a corrupted SD card would boot - but accesses to one or more directories would time out (and 'ls -l' would show question marks). Nowadays I always 'synch' after explicitly writing onto an SD card, and run 'fsck' whenever I have an SD card removed from its XO. My suggestion would be to try "repairing" (fsck?) the SD card. Though you may not have the time to try this, you might check if the same SD card on a different XO-1 still has this problem, and if a different SD card in the original XO-1 still has this problem. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Checking filesystems periodically
On Fri, May 4, 2012 at 2:55 AM, Anish Mangal wrote: I am curious to know why we are not periodically checking file systems after every N boots on the XO laptop. I think the question is: "Should functions which affect the 'system' be performed automatically, or should they be explicitly invoked ?" The currently-existing OLPC precedent is the 'Software updates' facility -- which gets invoked manually to check whether the system's Activities are up-to-date. My suggestion is to package the required software (fsck?) into a new 'Check system' facility - and add an icon for that new facility to the 'My Settings' panel - then the user who invokes it will know why his XO is "tied up" for a while. [The local XO-laptop distributing organization can publish guidelines as to how often such a 'Check system' facility ought to be used.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend
Another comment from the unwashed: Years back, I used only ethernet to connect my XOs. Nowadays, I'm using both wired and wireless to connect between XOs. [By the way, I normally run my XOs with suspend disabled - so I have not paid much attention to problems associated with 'resume'.] For about the last year, Network Manager has become "super bossy": It used to be that if I had an XO on ethernet, Network Manager might intervene after some 10+ hours - breaking that ethernet connection. I did not mind occasionally having to "reconnect" the ethernet (I just invoke a script that re-issues the necessary commands). But the current Network Manager intervenes in less than ten SECONDS - it breaks the connection on the ethernet (eth1) interface - presumably to set up the wireless (eth0) interface (to listen for radio signals). Bottom line - these days, in order to use ethernet on an XO, I need to __disable__ Network Manager. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Switching to randomly generated hostnames
On 05/01/2012 10:29 AM, Daniel Drake wrote: As far as I can see, the hostname is not really of relevance to anything except avahi. But from avahi is how the other XO users identify who is online. I can never remember which system has which XO-icon color -- but the name (as shown on hover in Neighborhood View, and by sugar-xos) instantly tells me who's who. [As part of my customization, I specify the XO hostname to match the nickname I entered at first boot upon install.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Determining whether we are doing pretty boot -- in olpc-configure - 12.1.0
On 04/27/2012 10:17 AM, Kevin Gordon wrote: Also, please let me know if 12.1.0 is ready for my battery of external USB device testing on all three platforms. I see no reason why you should hold off testing with 12.1.0 (please use os8 or following). [Note: I usually plug in USB storage devices only after the XO has booted. All too often, OFW stalls if I have too many USB devices plugged in at the time when I power on.] Do please note that as of Fedora 17, automounts are __NOT__ to directory /media Instead, on the XO they now are to directory /run/media/olpc/ mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] Announcing Q3C05 for XO-1.5
FYI. I apply extensive customizations to the builds I install. In my case, both the customization scripts and the packages-to-be-installed reside on the "permanent" SD card I place into each XO. But there is no reason why in your case they could not reside on a "non-permanent" USB stick used only during the customization procedure. My customizations (and the run-time scripts I have added to my systems) depend upon certain environmental variables. When I first boot a new build, I enter these by hand. But as soon as my customization scripts run, they insert commands into the appropriate places in /etc to set these values on boot (so every session has them). I also substitute my own /home/olpc/.bashrc, which extends $PATH to access all the scripts (particularly for run-time) that I have added. I manually run (at first boot) all my customization scripts (currently 10 or so) from the Terminal Activity (after doing 'su' to get into root, but keeping the environmental variables set up for user olpc). The steps performed by those initialization scripts are (roughly): *) Set up "well-known" filenames (I use /home as the location) to provide pointers to things like the installed python version and to provide values for things like the net address of the ethernet. *) Install additional RPMs ( for instance, those needed by Linux applications I will be running -- those applications themselves reside on my "permanent" SD card ). *) Customize certain files in /etc *) Link up my Activities (they reside on the "permanent" SD card) *) Add pointers into the system for resources kept on the "permanent" SD card -- such as Java, additional fonts, Adobe, Chrome, etc. *) Customize certain files in Sugar As new releases of Fedora and Sugar come out, I need to update my customization scripts to accomodate any changes. But how I have structured the customizations application process has served me well -- all the way from Fedora 9 to Fedora 17, and from Sugar 0.82 to Sugar 0.96. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 6 released, for the XO-1, XO-1.5 and XO-1.75
In the case of the /etc/fstab if it's a file system required to boot it will bork I don't mind it borking. But the system offered me the choice of "continue". When I took that choice, the system returned to the SAME bork. I would have preferred it if "continue" had meant "skip this". You mentioned you'd already created a ticket for this, do you have the number of the ticket? I wrote ticket # 11719 for a different problem - which appears to exist in all XO-1 12.1.0 builds (I believe I saw it before os3; it definitely exists in os5 and os6). [Whereas the "no device for the XO-1 SD card (beneath the display) problem only showed up with XO-1 build os6.] Ticket # 11719 says that for XO-1 12.1.0 builds, nothing exists in the /dev tree which can be used in a 'mount' command to access the files which OFW uses to boot the XO-1. [These files exist in a separate partition on NAND; when things work correctly that partition gets mounted onto /bootpart -- then those files can be accessed/manipulated (e.g., via manual commands) from the running XO-1 system.] My own interest is in customizing the olpc.fth file that OFW uses when it boots the XO-1. But the same problem arises if the user performs 'yum upgrade kernel' (assuming that a newer kernel version has been placed in the olpc-f17-xo1 repo). With the # 11719 problem present in XO-1 12.1.0, the output of the 'yum upgrade' (which got placed into /boot) CAN'T be copied onto /bootpart (because there is no filesystem mounted on /bootpart). The result is that the XO-1 12.1.0 system ignores attempts to upgrade its boot process, and continues to use those "boot files" which were created when the XO-1 12.1.0 build was originally compiled. mikus p.s. Please let me repeat: It is not clear to me what the "we need detailed reports" are that would allow you to discover whether such a problem exists on the XO-1 you use. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 6 released, for the XO-1, XO-1.5 and XO-1.75
I don't disagree but ultimately if there's not appropriate bug reports with all the information needed we can't fix the problems. So ultimately I appreciate his bug reports but with a non standard configuration we need detailed reports to have that information be useful for those people that actually have to deal with the information and fix the problem. I've already stopped writing bug reports against Fedora - I've concluded their requirement that the submitter describe "how to reproduce the bug" is to me not worth my time and effort. Fedora is *their* product - what does it matter to me whether it retains bugs ? You would like "all the information needed". I thought I posted to the effect that when an XO-1 with 12.1.0 build os6 is booted, nothing gets defined in the /dev tree against which a 'mount' command could be issued in order to access the content of a partition on the SD card plugged into the XO-1 external slot (beneath the screen). It is not clear to me what the "we need detailed reports" are that would allow you to discover whether such a problem exists on the XO-1 you use. Note that for my purposes I was able to bypass this problem. What I was not able to ignore was the os6 (on XO-1) reaction to having an entry in /etc/fstab referencing this undefined (on os6) storage device. But I agree that having such an entry in /etc/fstab is "non-standard" -- from now on, I will make sure to NEVER for 12.1.0 to mention any problems I have with whatever I do that is "non-standard". mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 6 released, for the XO-1, XO-1.5 and XO-1.75
Peter wrote We're glad of the testing but ultimately if you need a perfectly stable platform I suggest you stick with 11.3 for the moment. I'm a volunteer. I have no __need__ to post here (nor to use the XO). Which would you prefer - to have me keep quiet about what I encounter - or may I share my experiences without being lectured about __need__ ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 6 released, for the XO-1, XO-1.5 and XO-1.75
Edit: BTW - when I left the entry (which my customization had placed there) in /etc/fstab for my "permanent" SD card, os6 would not boot ON THE XO-1 -- it would go into the prompt for emergency mode, then when I ctl-D would after a while again go into the prompt for emergency mode, etc., etc. [I have no problems with 12.1.0 booting on the XO-1.5 (not even with os6). XO-1.5 /dev/mmcblk0 and /dev/mmcblk1 get defined correctly.] mikus ___ olpc mailing list o...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 6 released, for the XO-1, XO-1.5 and XO-1.75
I've already written a ticket saying that on the XO-1, 12.1.0 does not define any /dev/mmcblk0 (or anything) whose partition could be mounted onto /bootpart. Well, on the XO-1, 12.1.0 build os6 goes one step further -- it does not define any /dev/mmcblk1 (or anything) whose partition I could mount as my "permanent" SD card. I had to remove my SD card from the "external" (bottom of screen) socket on the XO-1, and plug it into an external USB reader, for me to be able to mount it on os6 as my "permanent" storage device. [At least, on the XO-1 os5 *would* define a device for the SD card that was inserted into the "external" (bottom of screen) socket on the XO-1.] BTW - when I left the entry (which my customization had placed there) in /etc/fstab for my "permanent" SD card, os6 would not boot -- it would go into the prompt for emergency mode, then when I ctl-D would after a while again go into the prompt for emergency mode, etc., etc. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OLPC RPM Repository Access
Did 'yum list olpc-powerd'. On one XO the latest version listed was 46 -- on another XO the latest version listed was 47. Turns out the the XO with the more-up-to-date answer had recently done 'yum clean all'. [My XOs normally run 24/7 - reboots are rare.] There is supposed to be a repository-refresh-countdown, which when it expires causes yum to automatically re-download the repository index (as it exists now). It appears that for the olpc-f14 repository entry (at least in os31) this "the previously downloaded repository index content has become obsolete" moment had not occurred recently. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.1 development build 31 for XO-1 and XO-1.5
On 03/27/2012 03:41 PM, Martin Langhoff wrote: The software update sees the base url and the OS version, and tries http://wiki.laptop.org/go/Activities/G1G1/11.3.1 http://wiki.laptop.org/go/Activities/G1G1/11.3 http://wiki.laptop.org/go/Activities/G1G1/11 First one to have content wins, and the software update stops searching. Thank you. I thought I had looked in wiki.laptop.org/go/Activities/G1G1/11.3.1, and not seen what I was looking for. But they *are* there. Sorry - must have made a mistake when looking. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.1 development build 31 for XO-1 and XO-1.5
The XO-1.5 build 31 came with Read-92.2 and Terminal 35.1. I am unable to locate the (raw) .xo files for these two Activities. [They are __NOT__ referenced by http://wiki.laptop.org/go/Activities/G1G1/ -- which is the "activity group" URL listed by My Settings -> Software update -> Modify activity groups. WHERE in laptop.org is the "official" URL for Activities contained in 11.3.1 ?? Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 5 released, for the XO-1, XO-1.5 and XO-1.75
FYI - odd: I have an (ext2) USB stick. On Linux, or on pre-12.1.0 XO1/XO1.5, -- that stick gets automounted as /media/CAVE On 12.1.0.- os5 - XO 1.5 -- that stick gets automounted as /run/media/olpc/CAVE mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New boot animation for 12.1.0
On 03/26/2012 07:33 AM, Peter Robinson wrote: Hitting escape on at least one of the XO-1/1.5/1.75 worked for me in my testing, I don't remember exactly which one(s) it was but it was certainly working in base testing (ie no modifications, no extra HW). My setup *does* have extra HW. I have an USB hub (with a keyboard and a mouse plugged into it) plus an USB-ethernet adapter plugged directly into the XO-1.5. If I unplug either the USB Hub or the USB-ethernet adapter before powering up, then "pretty boot" completes normally (system up and running). It is only when BOTH are plugged in to the XO-1.5 that the "pretty boot" stalls at the single dot. mikus p.s. Reminder - non-"pretty boot" works correctly. Pressing escape once the "pretty boot" has stalled does nothing. pps. Richard - when the "pretty boot" appears to stall, I do not think booting has gotten very far. Without both USB devices plugged in, "pretty boot" eventually activates the camera LED (presumably while initializing the camera). But when "pretty boot" stalls (with both USB devices plugged in), I did not see the camera LED ever being activated. [BTW, whenever booting completes and the system is up. powerd *is* running.] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO1/os31 update-nand issues
Don't use update-nand on XO-1 against a non-partitioned image. Once a signed build becomes available, the instructions should be changed to using the four-game-key method of starting the process, without any typing required. I myself keep several "build versions" on one (large) USB stick, so I do need to type - to indicate which "build version" I'm installing. I've been going by the filename-extension -- using 'copy-nand' for .img and using 'update-nand' for .onu -- but I was surprised to have to use 'copy-nand' with the 12.1.0 os5 for XO-1 -- 'update-nand' told me the file length was incorrect. mikus p.s. James - I have a "weak" XO-1, on which I often needed to redo an attempted install (because fetching the data off the USB stick happened to experience a file read error). Mitch Bradley came up with a timing change in q2e46a.rom which in my testing made 'copy-nand' run smoothly on that "weak" XO-1. I noticed that with one of this year's q2f roms that I again had to redo 'copy-nand' on that "weak" XO-1. Did the q2e46a change ever make it into the q2f roms ? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New boot animation for 12.1.0
I do not think the two-step progression from one dot to three dots is very useful. Particularly since on an XO with 21005xx1 with both an USB hub and an USB-ethernet adapter plugged in, "pretty boot" stalls with the one dot showing. [No change after 30 minutes; no clue as to what the user should do now.] Note - the same setup with pressing the check button (_no_ pretty boot) will boot correctly to completion.> > Hit escape and you'll get the output and you can see what it's doing. That just brings me into "non-pretty" boot -- which I already know will work. Besides, hitting escape has to be precisely timed -- AFTER it would cause a pause at the ok prompt, but BEFORE the boot process stalls. [Once booting has paused at the single dot, pressing escape does nothing.] If I wanted to run non-pretty boot -- much simpler to press the check button as the XO-1,5 powers on. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New boot animation for 12.1.0
I do not think the two-step progression from one dot to three dots is very useful. Particularly since on an XO with 21005xx1 with both an USB hub and an USB-ethernet adapter plugged in, "pretty boot" stalls with the one dot showing. [No change after 30 minutes; no clue as to what the user should do now.] Note - the same setup with pressing the check button (_no_ pretty boot) will boot correctly to completion. Please consider replacing the dots with a constantly-moving indicator (perhaps like in Object Chooser), but which STOPS when booting stalls. Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New boot animation for 12.1.0
What I think is important is for the user to be given visual ASSURANCE that the boot process has not gotten "stuck" (e.g., the line of periods emitted by long-running processes). If the indication can track fraction_completed - so much the better - but I do not expect the user to leave the room if the boot process takes longer than he expects. Seeing "only 25% to go" is ; the is knowing "no problems thus far". mikus (BTW, I haven't seen the new animation) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Multi-laptop naming scheme for build files
Based on this and previous discussions I think we could go with something like: 1. single-character ID for product type. 'a' for XO-1, 'b' for XO-1.5, 'c' for XO-1.75, ... 2. build number 3. a "." 4. extension Thoughts/other ideas? I suggest you should allocate at least one additional character for "originating organization" (or geographical location of issuer). Today we have au___ from Australia, ca___ from Canada, ___dx for Dextrose (South America), etc. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Unannounced 12.1.0 devel build 4 does not boot on XO-1
Used 'update-nand' to write os4 onto XO-1. With Q2F07 I get: | Boot device: /nandflash:\boot\olpc.fth Arguments: | Boot device: /pci/nandflash@c\boot\vmlinuz Arguments: | :88: | Can't open boot device With os3 (and Q2F07) the two "Boot device" lines are followed by ! Loading ramdisk image ... mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Kernel
I'm just installing onto a jffs2 XO-1, no building, just an install, so I did the basics: an install then the copy. Did I miss something in the install that left the old files around? Kevin - I've for years been removing the old files manually. What I do after the 'uname -r' is 'rpm -q kernel'. That gives me the full name of the kernel that is not running. Then I do 'rpm -e ...', specifying that obsolete kernel_full_name. I begin to finish up with 'find / -name ...' (where ... is a unique string extracted from the full name of the deleted kernel). Typically there will be leftover files within /versions/pristine/883 . I manually delete those. [In my opinion, the principal nand-space user is the leftover /lib/modules/,,, from the previous running system.] Of course, if the new kernel you installed did not come from a fully-functional rpm, then little things (like drivers) might stop working. If you wanted to no longer use the new kernel, but had deleted the previous kernel, you couldn't go back (e.g., by manually changing the pointers in the /boot directory ) -- you would need to do a complete re-install. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Removing duplication in /boot - affects kernel development
Our builds will always ship the kernel and initramfs *only* in their actos/runos/actrd/runrd zip forms. I'm an user who always runs 'yum upgrade kernel' whenever a newer version of the kernel appears in the olpc rpm repositories. I know how to copy the output of 'yum upgrade kernel' to where today's XO-1 and XO-1.5 kernels are actually being loaded from. If you change to this new packaging, __PLEASE__ publish a script (or instructions) that will allow an user to (manually) rebuild a newer kernel version into the appropriate actos/runos/actrd/runrd forms. Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Impacts of disabling Automatic Power Management
We shouldn't need to check whether there is network traffic when desiring to suspend. If no process has run in N milliseconds, the kernel should autosuspend. N should be tuned to avoid constantly suspending and then immediately reawakening, e.g. between packets in an active HTTP connection. Aren't there situations where network traffic occurs without significant "process" involvement? I remember a couple of years back, when my XO-1 (if so enabled) would suspend while I had a 100 MB ethernet transfer ongoing - I needed to periodically press something on the keyboard to keep that XO-1 awake. 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]
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: 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]
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: 12.1.0 devel build 3 released, for XO-1.5 and XO-1
On an XO-1, build os3 was quite unusable until I disabled power management. All too soon after initial boot-up, the XO-1 would lock up -- it would not accept keystrokes (even though the Power LED was not blinking); after a couple of seconds it would not perform cursor movement either. I am no longer nimble - it felt to me that I had to really *rush* to My Settings to deactivate suspend/resume before their effect was to lock me out. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Browse-130 fails to launch on XO-1 with os2 (F17)
I do not know enough python to figure out for line 23 in __init__.py --
what is being imported, or from where -- but I interpret the cause for
the error message from that line as "could not find" (since the line in
webactivity.py DOES look like what the error message says it should be).
mikus
Traceback (most recent call last):
File "/usr/bin/sugar-activity", line 21, in
main.main()
File "/usr/lib/python2.7/site-packages/sugar/activity/main.py", line 121, in main
module = __import__(module_name)
File "/home/olpc/Activities/Browse.activity/webactivity.py", line 24, in
from gi.repository import GObject
File "/usr/lib/python2.7/site-packages/gi/__init__.py", line 23, in
from ._gi import _API, Repository
ImportError: could not import gobject (error was: ImportError('When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject".',))
1324736391.516371 DEBUG root: _cleanup_temp_files
Exited with status 1, pid 1054 data (None, ', mode 'w' at 0x950f758>, 'f88fbfbb3a10cf8f6a0eeb4199f6e72513b4f70c')
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 2 released, for XO-1.5 and XO-1
On XO-1 with os2, suspend (as enabled during boot-up) gives me trouble.. Disclaimer: I am not asking for help -- just sharing my experiences. When running os2 on the XO-1, sometimes "function stoppages" happened: * my swap partition got detached, so I couldn't run huge apps. * the "permanent" SD card which I mounted got silently unmounted * the wireless connection (to an AP) got broken There seemed to be somewhat of a correlation between these incidents and the 'power button' having gone into blink mode (and me having to press a key on the native keyboard to get the XO going again). So I updated my /etc/init.d customization script to inhibit suspend -- and since then the first two "function stoppages" haven't recurred. mikus p.s Midori (webkit-based) on the XO-1 performs in the same ballpark as with F14. So do Mozilla, Opera, and Chrome. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 2 released, for XO-1.5 and XO-1
Object Chooser sugar 0.95-2 (on XO-1.5 screen) Selecting 'OLPC root' icon appears to give the same view as selecting 'Journal' icon. Also a human factors difficulty - when there are more entries in Object Chooser than will fit on one screen, the scroll bar at the right edge is much too narrow. I tried to 'click' within the scrollbar (to scroll one page's worth), but accidentally mispositioned the cursor (off the narrow scrollbar image) and my 'click' got interpreted as selecting the entry where the cursor had strayed. mikus p.s. The above-described incident illustrates the lack within Object Chooser (i.e., within Sugar) of a "No I didn't want that!" facility [i.e., "BACK"].. To return to where I had been when I made the accidental click, I had to exit the Activity (which had acted upon the unwanted entry); and restart that Activity; and in Object Chooser to indicate the (in this case external) device I wanted to access -- and then wait for Object Chooser to again present its listing of that device's objects. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 2 released, for XO-1.5 and XO-1
Known issues: - Browse doesn't work - Read doesn't work The reason Browse doesn't work is that the OLPC-customized? hulahop package is not included in the build. [Neither is xulrunner.] The reason Read doesn't work is that python is unable to import 'evince' (perhaps because gnome-python2-evince isn't in F17). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-3 competitor?
Low-cost Aakash tablet: http://venturebeat.com/2011/10/26/aakash-android-tablet-exclusive/?utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Feed:+Venturebeat+(VentureBeat) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 1 released, for XO-1.5 and XO-1
My mistake - apologies. Turned out it was the SD card that had given up the ghost (and was non-responsive). When I inserted a different "external" SD card, it was correctly recognized by os1. Sorry, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 1 released, for XO-1.5 and XO-1
Disclaimer: I'm not asking for help; I'm sharing my observations.
os1 (on XO-1.5) does not recognize the second ("external") SD card --
I'll need to set up an USB stick with the resources that I normally
access via my "permanent" (second) SD card.
mikus
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Interesting aspect of signed build
Disclaimer: I am not asking for help. I'm just telling what I found. Was running os883 on an XO-1 (which had a developer key). I applied some modifications (part of which was a yum upgrade of the kernel and a change to /boot/olpc.fth (to set the CPU speed)). When I rebooted, I found that NONE of the changes to /boot were effective - the system still used the previous kernel and disregarded the changed olpc.fth. On investigating, I saw that I had accidentally replaced the develop.sig on the XO-1 with the file from another system. When I put in the correct develop.sig, that XO-1 now booted into the desired kernel (and had processed the desired /boot/olpc.fth change). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New XO-1 testing firmware q2f04rd
Running XO-1 (os883) with q2f04rd. Appears to work well -- same behavior as with q2e48. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 can have difficulties with wired ethernet adapter
Re: eth0 assigned to ethernet Can you explain how we can reproduce this? At which point do you connect the ethernet adapter? My setup has (before I power up the XO) its own USB hub plugged in to that XO, with keyboard and mouse plugged in to the hub. I perform a "non-pretty" boot. I encountered this problem when I happened to insert the adapter into the XO-1.5 socket as the boot-process information lines were scrolling by on the (dark background) screen. I must have accidentally inserted the ethernet-USB adapter at exactly the right instant to produce the interface-assignment mixup. I tried to reproduce the problem using an XO-1 (os883, Q2e48.rom) but could not -- if I inserted the adapter AFTER the lines for the USB hub scrolled by, the ethernet was correctly assigned to 'eth1'. If I inserted the adapter just a bit earlier, the booting process hung (tail end of a trace showing - I suspect from a program check in the pegasus code - but the initial lines of the trace had already scrolled off the screen). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
11.3.0 can have difficulties with wired ethernet adapter
Using os883 with q3b22.rom on an XO-1.5. On first-time boot-up with a build, which interface gets assigned to the ethernet depends upon when the ethernet-USB adapter gets plugged in to the XO. [If plugged in too soon, the wired ethernet gets assigned the 'eth0' interface -- which causes conflicts trying to use wireless.] Further, with the ethernet-USB adapter plugged in, shutdown usually takes about a minute (while displaying the U/L warnings screen). It appears that something regarding the ethernet is being timed out. [Also, since this summer the Fedora 14 NetworkManager has gotten aggressive -- it periodically simply disconnects my ethernet connection (so that it can scan for wireless signals ??). My bypass is to stop the NetworkManager before connecting the XO to the internet using the wired ethernet rather than connecting the XO through a wireless AP.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: EC corruption by q2f04rc firmware
To date I have one 2007-vintage XO-1 with q2f04rd (and os882). It worked normally (and never lost charge while plugged in to AC) until I closed the lid (thereby putting it into suspend). Upon opening the lid and pressing power, the power light changed to red, and the native XO green keyboard no longer worked. [I then used an external USB keyboard.] The XO-1 continued to function normally (except for no native keyboard), except that the power light continued to remain red. I removed AC and let the XO-1 continue until it shut down when it had exhausted its battery. I then plugged the AC back in (power light showed orange) and let it recharge until the power light was green, then rebooted. That XO-1 is now functioning normally. Closing the lid puts it into suspend, but after opening the lid and pressing power it resumes properly (power light is green) and (WITH THE AC PLUGGED IN) functions normally. With AC removed, shutting the lid then opening the lid and pressing power caused the power light to go red - but the XO-1 continued to function normally (did not check keyboard - was using external USB). (With AC removed) repeated closing the lid then reopening and pressing power caused the system to halt with the "EC problem - disconnect ... " message. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] reflashing an XO-1
Mitch wrote on 10/11 This weekend I discovered a race condition in the OFW USB driver that might possibly be related to the problem you report. http://dev.laptop.org/~wmb/q2e46a.rom has a fix for the problem I found. My "weakest" XO-1 runs 'copy-nand' to completion with this rom, whereas from other roms it very often gets "file read errors" (on the file on that same USB stick) while performing 'copy-nand'. I've now adopted the procedure with that "weakest" XO-1 to first flash q2e46a.rom; then use it to install whatever the new os__.img is; then flash that XO-1 to another rom if I want to boot with that other rom. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: EC corruption by q2f04rc firmware
It may be that my setup is different from yours. I installed os882 on an XO-1 and booted; then installed q2f04rc.rom and booted. So far, the various logs from powerd are all reporting 'Full' (the XO-1 is plugged in to A/C). I will wait and see if the battery charge goes down with time. By the way, on a different XO-1 which first had q2e48.rom installed, then had os882 installed -- (without a prior EC reset having been done by pulling the battery) -- at the ok prompt the green native keyboard was unresponsive (nothing typed in showed up; nor was it recognized). I had to reboot with an external USB keyboard plugged in -- then I could enter text at the ok prompt from the external keyboard. [This XO_1 never had q2f04rc applied.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 build 4 released, for *XO-1.75*, XO-1.5 and XO-1
I think we're wasting the first two characters of the name. On the I agree -- keeping the scheme we have, and given the constraints, the leading 2 chars are the most viable option. The leading 2 chars ARE really useful to distinguish Australian builds from South American builds from North American builds. As Kevin suggested (regarding the trailing 3 chars) -- if we already have 'zd2' and 'zd4' and 'zd8' -- why not 'yd_' (or suchlike). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Help testing Sugar 0.93.x
Fedora 16 Sugar (and Soas) no longer have a working Browser: I will load os3 in my XO-1 and XO-1.5 and test ... Except for missing the fix from Ticket #10699, Browse-125 works adequately on os3 on the XO-1 and on the XO-1.5 mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar and GTK updates
had nowhere near the configurability of G2 Whether you intended to or not, you've just joined forces with those who criticise the fallback mode without actually saying whats wrong with it. What functionality were you missing? If you were someone working to improve the fallback mode, I would consider my time well spent to explain my comment. But to inform those not directly involved, please read what I _DID_ already say regarding what I dislike: "had nowhere near the configurability of G2". mikus p.s. For example, in the panels G2 gives me a LOT of function via LMB -- icon move and delete, panel resize and add, etc. G3 fallback mode (out of the box) has taken all those configurability facilities away. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar and GTK updates
At the moment, the fallback environment is working well on XO-1 in my testing. It's really not that different from before - nothing has ... - keeping G3 "fallback" desktop, hmm, well tested, in current and future Fedoras Some comments (NOT based on the XO): Been running Fedora 15 on a desktop. Was disappointed in G3 "fallback" -- it looked like G2, but had nowhere near the configurability of G2. [I may be wrong, but I got the impression that G3 "fallback" was a temporary expedient (to be dropped in future Fedora releases).] It is likely that computer neophytes will find G3 (or "fallback") acceptable -- but G3 itself as originally packaged in Fedora 15 has raised such a firestorm among long-time Linux users to in my opinion warrant being omitted from mention as a future direction for the XO. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Avoid losing your screws
I've found that inverted side bumpers make nice little holding containers for your screws. If you have a bit more room on your workbench, I've always found that an empty egg carton is a convenient way to hold screws segregated. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing OLPC OS 11.2.0 for XO-1 and XO-1.5
when I tried to boot back up into Sugar, I got a blank screen. The culprit is olpc-kbdshim.i686 0:18-1.fc14. When you did 'yum -y update', it got picked up. You should have done 'yum -y update --exclude=olpc-kbdshim' One bypass might be to download olpc-kbdshim.i686 0:17-1.fc14, then at the blank screen get into a text console (ctl-alt-F2) and issue 'rpm --force -Uvh olpc-kbdshim.i686 0:17-1.fc14' mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.2.0 release candidate 5 (build 874) released
Looking at the version numbers of some packages in build 874 -- The XO-1 has kernel-2.6.35.13_xo1-20110619.0933.olpc.218154b.i586, The XO-1,5 has kernel-2.6.35.13_xo1.5-20110707.0809.olpc.da7074b.i586 Build 874 has olpc-utils-1.2.12-1.fc14.i686, which has not yet appeared in the principal RPM repositories for F14. Build 874 still has xkeyboard-config-1.9-9.fc14.olpc.noarch My Settings -> About my Computer -> Sugar: says 0.92.2, whereas 'rpm -q sugar' says sugar-0.92.3.4.g50b9373-1.fc14.olpc.noarch mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OGG file testing
http://wiki.laptop.org/go/File:OGG_tests.zip It would be very helpful if these could be tested on both XO-1 and XO-1.5 hardware. It is a judgement call balancing between file size and sound quality. Any feedback would be appreciated. My comments (highly subjective): [os872 XO-1.5 XO-1 audio_decoder: ffmpeg audio_codec: ffvorbis] * The .ogx files did NOT provide any noticeable improvement in the audio quality over the 16000 files. Because of their much larger size, I recommend the .ogx files be excluded from consideration. * In every case, the 08000 files were perfectly understandable. But they sounded less natural than the 11025 files. My suggestion - leave the 08000 files in last place when considering sound quality. * I thought the 11025 and 16000 files to be equivalent in listen- ability. If others also think their audio quality similar, I would give preference to the 11025 files because of their smaller size. * I personally preferred the 'plain' files to the 'eng' files. The whole audio is quite long - by starting with the Preamble the 'eng' files induced me to think that I was listening to "pontificating". * I am not a Spanish speaker. For me, the speech in all the 'spa' files was too rapid and too quiet. Because in the female voice the higher frequencies are more important, I thought the 'spa' 16000 file had better listen-ability than the 'spa' 11025 file. * I realize that "attribution" is extending common courtesy. The stuff at the beginning really sounded to me like an advertisement. mikus p.s. I consider it HYPOCRITICAL for an U.S. organization to distribute this to non-U.S. countries. For *most* of the rights in this declaration, I can think of examples of incidents where that right was not respected within the U.S. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: *.laptop.org issues
should be fixed now, providing your DNS says: % host download.laptop.org download.laptop.org is an alias for owl.laptop.org. owl.laptop.org has address 18.85.2.163 11:00 am Jul 7 U.S.Central Time I now works, as above. Thanks mikus traceroute download.laptop.org traceroute to download.laptop.org (18.85.2.163), 30 hops max, 40 byte packets using UDP 1 192.168.1.254 (192.168.1.254) 0.214 ms 1.269 ms 0.155 ms 2 ppp-70-253-79-254.dsl.austtx.swbell.net (70.253.79.254) 8.519 ms 7.866 ms 8.875 ms 3 99.171.168.130 (99.171.168.130) 7.734 ms 8.733 ms 8.790 ms 4 12.83.48.216 (12.83.48.216) 144.996 ms 144.983 ms 144.403 ms 5 ggr6.dlstx.ip.att.net (12.122.138.113) 19.638 ms 18.275 ms 19.071 ms 6 192.205.36.182 (192.205.36.182) 18.211 ms 19.263 ms 17.861 ms 7 te2-4.ccr02.dfw01.atlas.cogentco.com (154.54.6.61) 57.382 ms 55.387 ms 54.606 ms 8 te0-3-0-2.ccr21.mci01.atlas.cogentco.com (154.54.5.222) 29.703 ms 28.595 ms 30.810 ms 9 te0-5-0-4.ccr21.ord01.atlas.cogentco.com (154.54.45.146) 41.262 ms te0-3-0-2.ccr21.ord01.atlas.cogentco.com (154.54.2.190) 43.321 ms te0-1-0-2.ccr21.ord01.atlas.cogentco.com (154.54.25.82) 42.554 ms 10 te0-3-0-6.ccr22.bos01.atlas.cogentco.com (154.54.43.198) 67.170 ms te0-2-0-2.ccr22.bos01.atlas.cogentco.com (154.54.43.194) 65.751 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com (154.54.42.254) 66.842 ms 11 * * * 12 B24-RTR-3-BACKBONE-2.MIT.EDU (18.168.1.26) 66.101 ms 66.780 ms 65.690 ms 13 passport-7-4.media.mit.edu (18.85.0.2) 67.698 ms 66.341 ms 67.621 ms 14 owl.laptop.org (18.85.2.163) 66.062 ms 67.354 ms 65.501 ms ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: *.laptop.org issues
traceroute to lists.laptop.org (18.85.2.148), 30 hops max, 40 byte Thanks. That's the old IP; looks like DNS is being slow to update. Eventually it should resolve to 18.85.2.166 for you, and start working. 07:20 am Jul 7 U.S. Central Time I can now correctly access lists.laptop.org, which resolves to 18.85.2.166 But download.laptop.org still resolves to 18.85.2.148 - which I cannot access. mikus traceroute download.laptop.org traceroute to download.laptop.org (18.85.2.148), 30 hops max, 40 byte packets using UDP 1 192.168.1.254 (192.168.1.254) 0.275 ms 0.192 ms 1.227 ms 2 ppp-70-253-79-254.dsl.austtx.swbell.net (70.253.79.254) 7.754 ms 8.898 ms 7.753 ms 3 99.171.168.33 (99.171.168.33) 9.297 ms 8.420 ms 8.010 ms 4 bb1-g0-0.aus2tx.sbcglobal.net (151.164.188.145) 7.954 ms 10.436 ms 9.786 ms 5 ggr6.dlstx.ip.att.net (12.122.138.113) 19.993 ms 18.599 ms 19.159 ms 6 * 192.205.36.178 (192.205.36.178) 18.061 ms * 7 * * * ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: *.laptop.org issues
Can't reach lists.laptop.org. Taken at 17:30 Jul 6, U.S. Central time: daina:/home/mikus/fetch # traceroute lists.laptop.org traceroute to lists.laptop.org (18.85.2.148), 30 hops max, 40 byte packets using UDP 1 192.168.1.254 (192.168.1.254) 1.273 ms 1.268 ms 0.156 ms 2 ppp-70-253-79-254.dsl.austtx.swbell.net (70.253.79.254) 8.768 ms 9.029 ms 9.510 ms 3 99.171.168.33 (99.171.168.33) 7.935 ms 8.707 ms 9.187 ms 4 bb1-g0-0.aus2tx.sbcglobal.net (151.164.188.145) 9.163 ms 9.241 ms 10.904 ms 5 ggr6.dlstx.ip.att.net (12.122.138.113) 19.164 ms 19.917 ms 18.568 ms 6 192.205.36.178 (192.205.36.178) 206.277 ms * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * daina:/home/mikus/fetch # traceroute build.laptop.org traceroute to build.laptop.org (18.85.2.147), 30 hops max, 40 byte packets using UDP 1 192.168.1.254 (192.168.1.254) 0.242 ms 0.210 ms 1.239 ms 2 ppp-70-253-79-254.dsl.austtx.swbell.net (70.253.79.254) 7.689 ms 10.188 ms 9.105 ms 3 99.171.168.130 (99.171.168.130) 9.670 ms 8.292 ms 9.822 ms 4 bb2-g0-0.aus2tx.sbcglobal.net (151.164.243.247) 9.358 ms 10.519 ms 10.266 ms 5 ggr6.dlstx.ip.att.net (12.122.138.105) 21.128 ms 18.415 ms 18.848 ms 6 192.205.36.182 (192.205.36.182) 19.852 ms 21.337 ms 19.915 ms 7 te4-8.ccr02.dfw01.atlas.cogentco.com (154.54.1.253) 22.837 ms 20.843 ms 22.403 ms 8 te0-2-0-1.ccr21.mci01.atlas.cogentco.com (154.54.2.114) 30.290 ms 28.636 ms 29.861 ms 9 te0-4-0-3.ccr21.ord01.atlas.cogentco.com (154.54.6.157) 41.354 ms te0-2-0-3.ccr21.ord01.atlas.cogentco.com (154.54.7.186) 42.154 ms te0-5-0-4.ccr21.ord01.atlas.cogentco.com (154.54.45.146) 41.068 ms 10 te0-4-0-6.ccr22.bos01.atlas.cogentco.com (154.54.45.218) 67.318 ms te0-1-0-1.ccr22.bos01.atlas.cogentco.com (154.54.6.21) 65.558 ms te0-4-0-6.ccr22.bos01.atlas.cogentco.com (154.54.45.218) 66.695 ms 11 * * * 12 B24-RTR-3-BACKBONE-2.MIT.EDU (18.168.1.26) 66.512 ms 68.441 ms 66.914 ms 13 passport-7-4.media.mit.edu (18.85.0.2) 118.112 ms 116.103 ms 115.333 ms 14 crank.laptop.org (18.85.2.147) 67.641 ms 66.023 ms 67.359 ms daina:/home/mikus/fetch # mikus (my DSL provider is AT&T) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OFW and aging hardware ?
Perhaps it is because I am using XO-1s manufactured in 2007, but all too often when when I'm running 'copy-nand u:\osxx.img' (from q2e45), the screen gets more than halfway filled with green, then stops with 'Error reading .img file'. [I've done md5sum against the .img file on the USB stick, and its value matches osxx.img.md5] My bypass is to try the copy-nand again (sometimes switching USB sockets at the XO-1) - usually the retry completes. Is there something I can type in at the ok prompt that would make OFW more tolerant - so that my copy-nand would not stop in the middle ? Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build 871
I still cant connect to the candidates on download.laptop.org. > Works fine from here. I have tried several times over the past 24 hours > and the connection worked ok each time. > I've been trying (browser, wget) on Jul 1 and Jul 2 and Jul 3 -- the attempted connection (ping tells me it's to pedal.laptop.org < 18.85.2.148 >) ALWAYS times out. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.2.0 development build 23 released
On 6/10/2011, my most up-to-date os22 system had: (taken (then) from xs-dev.laptop.org/~dsd/repos/f14/) sugar-0.92.2-1.fc14.noarch sugar-toolkit-0.92.2-1.fc14.i686 Os23, as released 6/15/2011, has: (so does (now) xs-dev.laptop.org/~dsd/repos/f14/) sugar-0.92.1.7.ge37bb32-1.fc14.olpc.noarch sugar-toolkit-0.92.1.6.g4e847e7-1.fc14.olpc.i686 The sugar-0.92.2 appears to have been withdrawn. Was it premature ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] [Dextrose] Support for Firefox 3.5 is ending
> Does that mean that with FF4 installed, Browse is still working > because it is (equivalently) using FF3.6 as the backend? > > Would that mean that if we were to upgrade to FF4, we would have a > disparity in rendering between GNOME and Sugar? A note from a sometimes_bleeding_edge user: Ever since FF4 beta was available, I've been running it on all my XOs. It has its own subset of "xulrunner functions" - so does not conflict with whatever xulrunner package version has been installed in the XO. Browse has not been affected by my upleveling of FF. mikus p.s. Activities such as "Karma" appear to have packaged-in an entire copy of the then-current xulrunner function. pps. With FF 5 beta now available - that's what I am currently running in all my F11/F14 XOs. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Get serial number or XO name from command line or python
> Is there a simple way to get the XO serial number and/or the XO name You have to define "serial number", and you have to define "name". Further, the answer depends upon the software version in the XO : Start with (this is from a bash script) > if [ -e /ofw/serial-number ]; then > echo "Serial: "`cat /ofw/serial-number` > fi and > echo "Nick : "`hostname` also try (all one line) > gconftool-2 --get --direct --config-source=xml:readwrite:/home/olpc/.gconf > /desktop/sugar/user/nick and then there are the addresses shown by 'ifconfig eth0' mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.2.0 development build 19 released
> The visual representation is nice ??? I myself (and perhaps others) am used to the entire matrix being visually filled with green. [It already was a shock on the XO-1 when with F14 some blue intruded upon the first couple green lines.] Now the green leaves glaring gaps. The user is being forced to TRUST that such gaps will not affect the running of the installed system. NOT a reassuring visual presentation. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.2.0 development build 19 released
I'm getting a download speed of 3 KB / sec !!! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Great Contributor's Project: Undercover Land Mine Game Update and Download
> on the sources of activity should be placed in the file version > activity.info activity that is designed so that other users who want > toexperience can see the compatibility of the activity in different flavors > :-) I believe that is not necessary. __ALL__ the software files in this package are written in Python -- so anyone who unzips the package has access to all the source code. [There are some data files in binary format - but I don't expect you to try to reverse-engineer those.] > the question is where build of sugar was tested this activity? Since the event.block() problem occurred from a file in the olpcgames subdirectory -- it is likely that the activity's author picked up that ENTIRE subdirectory from a now superseded version of Sugar. I do not know HOW SugarLabs does version control of the resources made available to Activity authors - but I am unaware of such information being packaged within the released Activity's bundle itself. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [DESIGN] XO1 | Same hardware, slower internet
> Hmm, it'd be interesting to see how much of a performance improvement > webkit offers. It's no big deal to run webkit-based browsers on the XO. For instance, all of my XO-1s have Midori installed. The question is - what is this "performance improvement" that you are looking for? I believe that in practice, it is the "usability" of a browser that is noticed the most, not the "performance". What Midori has is a smaller footprint - what it does not have is a richer experience than Firefox - the result is that I myself prefer using Firefox on the XO-1 to using Midori on the XO-1. [In my opinion, the "performance" of the two is roughly equivalent (e.g., in showing YouTube videos).] It is worth noting that the Google Chrome browser, which *does* have the reputation (in the general public) of better performance, does not stand out on the XO (perhaps because its footprint is large). > should we consider loading mobile versions of websites Regarding creating websites suited to web clients without much computational power -- why should the typical internet website owner bother? I'm going to assume there might be 100 users in the worldwide audience who are looking for "glitz" for every one user who is looking for "fast rendition" -- just look at the size of the images transmitted by the typical internet website -- in my opinion any image greater than 40KB will "slow down" a web client which does not have considerable computational power -- yet monster images abound. Regarding a project providing web transmissions specifically aimed at a classroom - the phrase "mobile versions of websites" is often applied to video information formatted to be displayed on phones - yet if there are XOs in the classroom, they have a significantly larger screen than phones. I expect what you are looking for is video information formatted to be displayed on *tablets* - it will come, but I don't know if it is available just yet. What is definitely useful is an aimed-at-classroom setup, where a teacher's (or lab experimenter's) mobile system broadcasts to multiple (pupils') XO *clients* in that classroom. [Think of it as a website aimed at XOs.] This setup ideally would use an XO for the system from which the video transmissions originate. The simplest way to provide such functionality appears to be a slimmed-down web *server*. [I've seen descriptions of such, but at the moment can't remember the name of that software (might have been proprietary).] Since such a "website" would be viewed at XOs, the webpages created for that site definitely need to take into account the limited computational power of the XO. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1.75 RAM
> Might 1GB of RAM become a performance bottleneck? I myself am skeptical of efforts to use the OLPC where a desktop system might be more effective. I've run various large applications on an XO-1.5 system, and have not myself experienced "memory shortage". Unless the RAM chips on the XO-1.75 are socketed (and thus easily replaceable), it seems to me that it would be easier to add swap space (rather than RAM) to those systems used to run particularly memory-hungry applications (such as video editing). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1 OFW occasionally has difficulty reading from my "permanent" SD card
It may well be the quality of the non-high-priced SD cards I use, but with q2e42 and later OFW versions, when several specific XO-1s are booted, OFW will occasionally (but not consistently) time out when trying to read the developer key from the SD card. My usual bypass is to unplug all external USB cables and reboot - that appears to get rid of the timeout. Is there some incantation that I can type in at the ok prompt which would tell OFW to not time out so promptly ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Memory replacement
> The tests have also helped expose other issues with things like sudden
> power off. In one case a SPO during a write would corrupt the card so
> badly it became useless. You could only recover them via a super secret
> tool from the manufacturer.
Is there any "sledgehammer" process available to users without a super
secret tool ?
I've encountered SD cards which will be recognized as a device when
plugged in to a running XO-1 (though 'ls' of a filesystem on that SD
card is corrupt) -- but 'fdisk' is ineffective when I want to write a
new partition table (and 'fsck' appears to loop). Since otherwise I'd
just have to throw the card away, I'd be willing to apply EXTREME
measures to get such a card into a reusable ("blank slate") condition.
mikus
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Discovering the XOs local timezone in a bash script
Well, 'My Settings' -> 'Date & Time' allows the user to specify the local timezone (I always do this) - but I'm not sure which routines actually make use of that setting. It can be extracted by (all on one line): gconftool-2 --direct --config-source=xml:readwrite:/home/olpc/.gconf/desktop/sugar/date --get /timezone but then you have to decode that string ( e.g., America/Chicago ). mikus ___ 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
