Re: [Sugar-devel] XO4 touch stopped working (SOLVED)
Serial number for the XO is SHC31100189 I'll keep using it for a few days to check if the repair lasts... - Juan On 10/25/2013 04:37 PM, James Cameron wrote: We are aware of a manufacturing process problem that caused what you observed, but it was fixed some time ago. We know exactly when it was fixed. When you give us the serial number, I can check if the laptop was made before the fix or after. The change you've made sounds reasonable, but it may not last. Keep monitoring the situation. p.s. use the devel@lists.laptop.org mailing list for posts related to XO-4 and unrelated to Sugar. I've intentionally retained all of thread below. On Fri, Oct 25, 2013 at 03:19:52PM -0600, Juan Cubillo wrote: Tried the test /touchscreen and this message appeared: missing IR PCB failed to boot Tried the command again and a whole lot of code appeared (can't find my serial dongle so I can't copy it here) Tried the test for a third time and the message now was: missing IR PCB No touchscreen present I opened the screen and found that the conector for the ZIF cable was damaged and required some pressure to make proper contact. I just inserted some folded tape to keep it pressured and it's now working. No damage or mishandling was given to the laptop on my part so if there are any other reports of touch not working OLPC should stay aware in case the conector might be damaged from factory. Anyway... it's now working just fine :) Thanks for the info! Juan Adrián Cubillo Director de Tecnología | Fundación Quirós Tanzi Web: http://fundacionqt.org FB:Fundación Tel: (506) 2293-2460 ext211 | Cel: (506) 8832-1824 On 10/25/2013 01:39 PM, Gonzalo Odiard wrote: You can check the touchscreen from the bios: * Start the xo * While the startup sound is played, press ESC key You will see a ok prompt. * Type: test /touchscreen and press enter. The screen will turn black and you can test it with until 4 fingers. Gonzalo On Fri, Oct 25, 2013 at 4:32 PM, Juan Cubillo jcubi...@fundacionqt.org wrote: Hello, I recently received an XO4 touch to test. As far as I know, it came with the default 13.2 Sugar image. Last night I updated the system with yum update just because. The touch option stopped working but I just assumed it was due to the update which might have broken some package or library. This morning, I flashed the XO with OLPC's stable sugar build to restore the XO and the touch option is still not working. Is there any chance the update I made last night might have updated something that broke the touch option? Some firmware maybe? Also, is there any way to test if the XO is able to correctly detect the touch hardware and test it? I tried to search the mailing list and wiki for this but found no info available. - Juan ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OOB not working on 1.75XO. Can't download package tracker.
On 07/19/2013 05:59 PM, James Cameron wrote: Try a VPN or a different service provider? Some service providers may block URLs with tracker in them so that they reduce the impact of torrent file sharing. If you find this is the cause, work with your service provider to have the block removed for your account, or refined so that RPMs are allowed. This is exactly what was happening. I'm now going around the blockers and everything is working fine. Thank you for the advice! - Juan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OOB not working on 1.75XO. Can't download package tracker.
Hello, I'm trying to build a custom image based on the newer 13.1.0 release. An XO was installed fresh with the 13.1.0 stable image and olpc-os-builder installed via yum. When trying to build the 1.75XO example ini file it always ends with this error: Retrieving http://mock.laptop.org/repos/local.13.1.0-xo1.75/repodata/repomd.xml ...OK ERROR:root:Error creating Live CD : Unable to download from repo : Package Header tracker-0.14.2-4.fc18.armv7hl: RPM Cannot open INFO:root:Unmounting directory /var/tmp/olpc-os-builder/imgcreate-0HsYBZ/install_root INFO:root:Losetup remove /dev/loop0 * Caught error, cleanup and then bail out. * Running part cleanup base cleanup.50.cleanup.sh... * Running part cleanup buildnr_from_file cleanup.50.write_buildnr.sh... ERROR: Failure in BuildStage: module base, part build.40.imagecreate.py, error code 1 bash-4.2# I tried to download tracker on the host system with yum but it is not currently available. It seems the repositories locations are broken: bash-4.2# yum -y install tracker Resolving Dependencies -- Running transaction check --- Package tracker.armv7hl 0:0.14.2-4.fc18 will be updated --- Package tracker.armv7hl 0:0.14.4-1.fc18 will be an update -- Finished Dependency Resolution Dependencies Resolved === Package Arch Version Repository Size === Updating: tracker armv7hl 0.14.4-1.fc18 fedora 1.2 M Transaction Summary === Upgrade 1 Package Total download size: 1.2 M Downloading Packages: tracker-0.14.4-1.fc18.armv7hl. FAILED http://mirrors.rit.edu/fedora-secondary/releases/18/Everything/armhfp/os/Packages/t/tracker-0.14.4-1.fc18.armv7hl.rpm: [Errno 14] curl#56 - Network error recv() Trying other mirror. tracker-0.14.4-1.fc18.armv7hl. FAILED http://dl.fedoraproject.org/pub/fedora-secondary/releases/18/Everything/armhfp/os/Packages/t/tracker-0.14.4-1.fc18.armv7hl.rpm: [Errno 14] curl#56 - Network error recv() Trying other mirror. tracker-0.14.4-1.fc18.armv7hl. FAILED http://mirrors.kernel.org/fedora-secondary/releases/18/Everything/armhfp/os/Packages/t/tracker-0.14.4-1.fc18.armv7hl.rpm: [Errno 14] curl#56 - Network error recv() Trying other mirror. Error Downloading Packages: tracker-0.14.4-1.fc18.armv7hl: [Errno 256] No more mirrors to try. tracker-0.14.4-1.fc18.armv7hl: Downloaded package tracker-0.14.4-1.fc18.armv7hl, from fedora, but it was invalid. bash-4.2# I can add some other repo to the host system, but is there any way to add another download option for this package to OOB? Regards, - Juan Cubillo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Different boot sound on XO1.75
Hello, Quick question I have two 1.75XO that make a beep beep sound while booting instead of the usual XO booting sound. Why is this so? Can this be changed? - Juan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Different boot sound on XO1.75
That might be an option, but not in my case. Both XOs have Build 13.0.1 and Firmware Q4D28. I'll wait for James to wake up :) - Juan On 06/20/2013 09:45 AM, Daniel Drake wrote: On Thu, Jun 20, 2013 at 9:28 AM, Juan Cubillo jcubi...@fundacionqt.org wrote: Hello, Quick question I have two 1.75XO that make a beep beep sound while booting instead of the usual XO booting sound. Why is this so? Can this be changed? This likely means that you are running a new firmware on an old OS release. Downgrading the firmware to the version that was intended for that release should restore the bootup sound. (or, alternatively, upgrade the OS to match the firmware) I imagine James will provide a full explanation when he wakes up later on :) If you are mixing versions on purpose, do note http://dev.laptop.org/ticket/12637 Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Different boot sound on XO1.75
Just downgraded do Q4D20 and the original sound has been restored :) I had no idea that certain OS versions had to be matched to certain Firmware versions... I always tried to keep up with the latest on my test machines. - Juan On 06/20/2013 11:41 AM, Daniel Drake wrote: On Thu, Jun 20, 2013 at 11:36 AM, Juan Cubillo jcubi...@fundacionqt.org wrote: That might be an option, but not in my case. Both XOs have Build 13.0.1 and Firmware Q4D28. I'll wait for James to wake up :) In the mean time maybe you can explain why changing firmware version and/or OS version is not an option. It might help us give good advice. Thanks Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OOB V6.0 does not installs example ini files
Hello, I just flashed a 1.75XO with the stable 13.1.0 image from OLPC. Then, I installed OOB via yum install olpc-os-builder I wanted to build a test image but no example files were installed in /usr/share/docs/ Any ideas what may be wrong? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OOB V6.0 does not installs example ini files (SOLVED)
Thank you for the info! Yeah the ../docs/... was a typo... I was looking inside ../doc/ I also always wondered why the wiki instructions didn't used yum to install the software... another mystery solved! - Juan On 06/12/2013 04:37 PM, James Cameron wrote: Yes, that happened to me. Edit the file /etc/rpm/macros.imgcreate and delete the line %_excludedocs 1 Then reinstall the olpc-os-builder: yum remove olpc-os-builder yum install olpc-os-builder Our instructions at http://wiki.laptop.org/go/OS_Builder/Run_on_XO_hardware and http://wiki.laptop.org/go/OS_Builder/Development avoid this problem by using git to obtain the olpc-os-builder software. Oh, and as Peter points out, look in /usr/share/doc not /usr/share/docs for the files. On Wed, Jun 12, 2013 at 12:39:22PM -0600, Juan Cubillo wrote: Hello, I just flashed a 1.75XO with the stable 13.1.0 image from OLPC. Then, I installed OOB via yum install olpc-os-builder I wanted to build a test image but no example files were installed in /usr/share/docs/ Any ideas what may be wrong? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Problem compiling bios-crypto in XO1.75 hardware
Hello, I'm creating xo1.75 OS images on a 1.75 XO since that's the only ARM hardware I have around. In order to sign the images I need to compile bios-crypto following the instructions from the wiki: http://wiki.laptop.org/go/OS_Builder#Signing_preparation make is not finishing correctly and ends with the following error message: bash-4.2# make echo Building in the 'build' subdirectory Building in the 'build' subdirectory make -C build make[1]: Entering directory `/home/root/bios-crypto/build' ld -Ttext 0xc -Tbss 0xd --defsym _start=verify_data bios_verify.o stack_alloc.o bios_string.o ../depends/libtomcrypt.a ../depends/libtfm.a arm_libs.o /usr/lib/gcc/armv7hl-redhat-linux-gnueabi/4.7.2/libgcc.a -o bios_verify.elf /usr/lib/gcc/armv7hl-redhat-linux-gnueabi/4.7.2/libgcc.a(bpabi.o):(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr1' make[1]: *** [bios_verify.elf] Error 1 make[1]: Leaving directory `/home/root/bios-crypto/build' make: *** [all] Error 2 bash-4.2# Has anyone been able to get bios-crypto working on ARM architecture? How could I solve this issue? - Juan Cubillo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem compiling bios-crypto in XO1.75 hardware
On 04/01/2013 10:56 AM, Daniel Drake wrote: On Mon, Apr 1, 2013 at 10:51 AM, Juan Cubillo jcubi...@fundacionqt.org wrote: Hello, I'm creating xo1.75 OS images on a 1.75 XO since that's the only ARM hardware I have around. In order to sign the images I need to compile bios-crypto following the instructions from the wiki: http://wiki.laptop.org/go/OS_Builder#Signing_preparation make is not finishing correctly and ends with the following error message: bash-4.2# make Have you tried using the exact instructions given at http://wiki.laptop.org/go/OS_Builder#Signing_preparation $ cd bios-crypto/build $ make cli Thanks Daniel Yes, I cloned the git repo, changed directory and issued the make command but I get the error described. I'm running this on the latest stable image for the xo1.75. From your reply I assume that this error is not normal. Should the make work with no issues on arm hardware? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem compiling bios-crypto in XO1.75 hardware
Just noticed that mistake. I was missing the cli parameter for the make command. It's now built and I'll include the crypto module in the oob ini file to test it. Thank you for the help - Juan On Mon, Apr 1, 2013 at 11:34 AM, Daniel Drake d...@laptop.org wrote: On Mon, Apr 1, 2013 at 11:12 AM, Juan Cubillo jcubi...@fundacionqt.org wrote: Yes, I cloned the git repo, changed directory and issued the make command but I get the error described. I'm running this on the latest stable image for the xo1.75. From your reply I assume that this error is not normal. Should the make work with no issues on arm hardware? In your mail you seem to be in the bios-crypto root directory, and you ran make. However following the instructions you should be in the bios-crypto/build directory and the command is make cli. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problem downloading a lease.sig file on an XO
mime type has been correctly set to application/octet-stream and wget confirms the change. But Sugar is still downloading it as text/plain type and now adds a .txt extension at the end of the file making it lease.sig.txt . It seems my guide will now have to add the extra step of log into Gnome so that kids may download the file and unlock XOs. Nothing to worry about. Thanks for all the help! - Juan El 13/09/12 14:15, Martin Langhoff escribió: On Wed, Sep 12, 2012 at 9:22 PM, Samuel Greenfeld greenf...@laptop.org wrote: 1. Is there a security problem/concern with having our project's lease.sig file publicly available? (we only generate activations for non-stolen XOs) Should be ok, as long as you're comfortable with the validity period (ie: not too long!). 2. Why is the XO adding this .asc extension or how can it be avoided? As Sam mentions, it is MIME-Types. Perhaps this helps: set the mime types in your webserver so that .sig files are served as application/octet-stream (something that I believe sugar will not mess with). You can check what mimetype is being set on a transfer with wget -- during download, it'll print a message about Length, that same line shows the mime-type. If that doesn't help, let us know. cheers, m ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problem downloading a lease.sig file on an XO
I agree that this is not the best behavior, especially if Browse can potentially determine the original extension while downloading. If your XO images have the GNOME desktop in them, using the web browser included for GNOME (Firefox or Epiphany) to download the file to USB should not alter the file name. Just make sure the kids know how to eject the USB stick when they are done. This is probably what I'm going to do. The idea was to have kids use Browse in Sugar but telling them to go to Gnome as an extra step seems easy enough for a simple unlocking guide. Thanks for the help! - Juan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
