Re: error building oob for XO 1.75
On Wed, Mar 13, 2013 at 03:41:17PM +0545, Basanta Shrestha wrote: > Trying to setup build environment for ARM under fedora 14, following > following doc http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu > > getting following error. > > error: internal error process exited while connecting to monitor: > qemu-system-arm: -device lsi,id=scsi0,bus=pci.0,addr=0x4: Bus 'pci.0' not > found > --- See https://bugzilla.redhat.com/show_bug.cgi?id=667345#c1, which points to http://cdot.senecac.on.ca/arm/FEDORA13-WRAPPER-qemu-system-arm. A newer version of libvirt should work too. > > Also, > Getting following error while while configuring selinux > setsebool -P virt_use_execmem 1 > - > > libsemanage.dbase_llist_set: record not found in the database (No such file > or directory). > libsemanage.dbase_llist_set: could not set record value (No such file or > directory). > Could not change boolean virt_use_execmem > Could not change policy booleans > > > > tried disabling the effect of selinux by doing > echo 0 > /selinux/enforce > > > but no luck. Maybe completely disabling selinux (instead of putting it in permissive) works. Either boot with "selinux=0" on the kernel command line or disable in /etc/selinux/config and reboot. Updating to a newer selinux-policy would be an alternative. HTH, Niels > > > > On Wed, Mar 6, 2013 at 4:30 PM, James Cameron wrote: > > > Your builder system should have an ARM processor, but I see from your > > rpm -qa that you have an i686 package installed. This is because > > builder system is not ARM processor? > > > > See http://wiki.laptop.org/go/OS_Builder/Run_on_XO_hardware for how to > > build 11.3.x on XO-1.75 hardware. > > > > On Wed, Mar 06, 2013 at 03:38:37PM +0545, Basanta Shrestha wrote: > > > Hi, > > > I am trying to build oob for my xo 1.75. But I am getting following > > error: > > > Please help. > > > > > > Retrieving http://mock.laptop.org/repos/koji.dist-f14-armv5tel/repodata/ > > > repomd.xml ...OK > > > Retrieving > > http://mock.laptop.org/repos/koji.dist-f14-armv5tel-updates-11.3.0/ > > > repodata/repomd.xml ...OK > > > Retrieving > > > http://mock.laptop.org/repos/local.11.3.0/repodata/repomd.xml...OK > > > Retrieving > > http://mock.laptop.org/repos/local.11.3.0-xo1.75/repodata/repomd.xml > > > ...OK > > > ERROR:root:Error creating Live CD : Failed to find package > > 'openssh-clients' : > > > No package(s) available to install > > > * 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 > > > -- > > > I have following system: > > > -- > > > [root@basanta-dev examples]# pwd > > > /usr/share/doc/olpc-os-builder-4.0.0/example > > > [root@basanta-dev examples]# more /etc/redhat-release > > > Fedora release 14 (Laughlin) > > > [root@basanta-dev examples]# rpm -qa | grep openssh-clients > > > openssh-clients-5.5p1-24.fc14.2.i686 > > > [root@basanta-dev examples]# ls > > /usr/share/doc/olpc-os-builder-4.0.0/examples/ > > > [root@basanta-dev examples]# olpc-os-builder /usr/share/doc/ > > > olpc-os-builder-4.0.0/examples/olpc-os-11.3.0-xo1.75.ini > > > > > > -- > > > Basanta Shrestha > > > OLE Nepal > > > > > > > > ___ > > > Devel mailing list > > > Devel@lists.laptop.org > > > http://lists.laptop.org/listinfo/devel > > > > > > -- > > James Cameron > > http://quozl.linux.org.au/ > > > > > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 release candidate 5 (build 18) released
On 07/11/2012 08:48 PM, Daniel Drake wrote: Hi, We're pleased to announce the next release candidate of our new 12.1.0 software release. Information and installation instructions can be found here: http://wiki.laptop.org/go/Release_notes/12.1.0 Update on this page still lists release 17, it should probably be corrected to "sudo olpc-update 12.1.0c_xo1.75-18" and the like. Thanks, Niels Quick links for those who know which files need to be grabbed and save to USB disks: http://download.laptop.org/xo-1.75/os/candidate/12.1.0-18/ http://download.laptop.org/xo-1.5/os/candidate/12.1.0-18/ http://download.laptop.org/xo-1/os/candidate/12.1.0-18/ This is a signed release candidate that can be installed on all XOs, even those with security enabled. We're looking for testing and feedback on all aspects of the system. Thanks for any help you can offer, and for all the feedback that was received throughout development. We're hoping to release this as soon as possible, pending some final issues being worked on. Please review the "Known problems" section of the release notes. Some documented issues are carried over from previous releases, but others are new and are things that we will aim to fix in the time remaining before release. Compared to 12.1.0 release candidate 4 (build 17), we have fixed and changed: Use of sensors in Measure on XO-1.75 has been fixed (#11996). An occasional hang on shutdown/reboot (commonly seen in runin testing) has been fixed (#11949), and the runin screen on XO-1.5 is no longer black for the first two minutes (#11985). Thanks! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Niels de Vos Software Maintenance Engineer Global Support Services Red Hat ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: kernel-devel package
On Fri, Jun 15, 2012 at 2:59 PM, Gonzalo Odiard wrote: > I am trying to use stap to find the source of a ugly race condition, > can install it in xo-1.75 with os13, but when want execute it, > have the following error: > > bash-4.2# stap --vp 1 -o ./output.log -t sugar.stp 506 > Checking > "/lib/modules/3.0.19_xo1.75-20120606.1504.olpc.8d24ad5/build/.config" failed > with error: No such file or directory > Incorrect version or missing kernel-devel package, use: yum install > kernel-devel-3.0.19_xo1.75-20120606.1504.olpc.8d24ad5.armv7hl > > Trying to install: > > v7hh-4.2# yum install > kernel-devel-3.0.19_xo1.75-20120606.1504.olpc.8d24ad5.arm > updates/metalink | 4.3 kB 00:00 > > updates-testing/metalink | 4.5 kB 00:00 > > No package kernel-devel-3.0.19_xo1.75-20120606.1504.olpc.8d24ad5.armv7h > available. > Error: Nothing to do > > I know we have our custom kernel, but we publish a kernel-devel package too? > Where is it? Here: http://dev.laptop.org/~kernels/public_rpms/f17-xo1.75/ Cheers, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC Engineering] [Techteam] 12.1.0 devel build 5 released, for the XO-1, XO-1.5 and XO-1.75
On Mon, Mar 26, 2012 at 7:49 PM, Chris Ball wrote: > Hi, > > On Mon, Mar 26 2012, Niels de Vos wrote: >> Now, I'd like to have the wireless working somehow. Any hints, or is >> there a ticket open for this already? > > We're not sure why the crashes are happening. If you (or anyone else) > would be willing to help debug, it'd be appreciated. Either of these > two tests would be helpful: > > (1) Try installing the kernel from 11.3.1 build os31 on os5: > > > http://dev.laptop.org/~kernels/public_rpms/f14-xo1.75/kernel-3.0.19_xo1.75-20120320.1540.olpc.7e610e7.armv7l.rpm > > and see if the problem persists. I tried (1) and the problem is not gone with that kernel. What I did was this: 1. boot the kernel 2. switch to console (CTRL+ALT+F2) to prevent locking up in plymouth 3. try to unload the libertas_sdio module (fails with kernel stack dump, but prevents timeout spamming) 4. # systemctl start powerd.service 5. show the systemd-journal to check that powerd has been started 6. wait until powerd kicks in 7. take a picture of the screen: - https://picasaweb.google.com/lh/photo/mM9iK5dMUyz4BC54Wahn5PPU9FZYZ9jHSbJOykEfJc8?feat=directlink This does not tell me a lot. Let me know if you want me to try booting (which kernel?) with 'no_console_suspend' and do some more tests. Unfortunately I do not have a working serial console setup atm (missing the USB-cable). > (2) Try installing the kernel from os5 onto 11.3.1 build os31: > > > http://dev.laptop.org/~kernels/public_rpms/f17-xo1.75/kernel-3.0.19_xo1.75-20120322.1410.olpc.8f384dd.armv7l.rpm > > That'll help work out whether the problem follows the kernel RPM or > the build image. (Make sure that you've checked that you are actually > running the newly-installed kernel, with uname -r.) > > Thanks! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC Engineering] [Techteam] 12.1.0 devel build 5 released, for the XO-1, XO-1.5 and XO-1.75
On Sun, Mar 25, 2012 at 8:45 PM, Chris Ball wrote: > Hi, > > On Sun, Mar 25 2012, Simon Schampijer wrote: >> Yeah, flashed now another 1.75 machine (1C2 4GB) and the first boot >> when I did not sit next to the machine it came up the same as my 1B1 >> with a non usable keyboard and trackpad. I rebooted and directly >> entered a name and could use than the machine. >> >> Things I came across from a first quick look: >> - the trackpad was not as good responsible >> - the neighborhood view had no APs listed >> - Paint did not start due to missing binaries (does start on the 1.5) > > It might have crashed on its way into idle suspend (probably due to the > libertas bugs) leading to an apparant symptom of no keyboard/trackpad. > I stopped powerd straight away to avoid that. These crashes/hangs happen very reliable for me too. Stopping powerd was a nice hint :-) I did the following, in case someone has the same issues: 1. boot 2. switch to a console (CTRL+ALT+F2), as soon as the GUI starts 3. press enter to activate the shell 4. (optional) ignore the timeout errors related to the libertas driver, just keep typing 5. execute 'systemctl stop powerd.service' to stop the currently running daemon 6. execute 'systemctl disable powerd.service' to prevent the daemon from starting on the next boot Now, I'd like to have the wireless working somehow. Any hints, or is there a ticket open for this already? Thanks, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
On Thu, Jan 12, 2012 at 4:07 AM, Dennis Gilmore wrote: > El Sat, 07 Jan 2012 21:24:29 + > Niels de Vos escribió: >> Unfortunately the fedora.repo and fedora-updates.repo are >> non-functional for Fedora 15 on ARM. Instead, I am now using the most >> current builds directly from a repository on the koji infrastructure: >> - >> http://arm.koji.fedoraproject.org/repos/dist-f15-build/latest/armhfp/ >> >> Does it make sense to create tickets for these kind of issues? Or is >> this email sufficient to help others? > > MAke sure that time on your system is close to correct. mirrormanager > uses https by default. if your time is way off the ssl cert wont check > out and things wont work. > > the repos really do work just fine Just tried it again, and it works for me now too. Not sure what has changed on my side, the /var/log/yum.log is empty, nor can I remember updating the time. Oh well, all fine. Thanks for the replies, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
On 01/03/2012 01:03 PM, Peter Robinson wrote: The "This sonic transducer, it is I suppose some kind of audio-vibratory-physio-molecular transport device?" release. THIS IS A DEVELOPMENT RELEASE AIMED AT CORE OS/HW DEVELOPERS This is a hard floating point Franken release for development and testing of the hardfp on the XO 1.75. Its very incomplete and has a number of things that don't work. This is expected and its a release only really intended for people that understandard what hardfp is and the significance of it and wish to test and develop further for this fairly major feature both for upstream Fedora and the XO releases. This isn't a release that shouldn't have bug reports against it. So what are the known issues, and what works? - X works using fbdev. There's an issue with resolution. Fix this by removing the "Virtual" line from /etc/X11/xorg.conf.d/xo1.75.conf - No accelerated X - Sugar and GNOME do work quite well - Networking seems to work OK - Firefox DOESN'T work. Known issue, hopefully should be fixed before long - Midori for GNOME, Surf for Sugar included as browsers. systemd is included (as it is Fedora 15) but does not really work by default. https://bugzilla.redhat.com/show_bug.cgi?id=704783 describes the same problem and points to a solution: - remove /var/run, /var/lock and /media from /etc/rwtab and reboot The change was made on a date after the version of initscripts that is installed was created. There are no Fedora ARM updates yet, but maybe a new version fixes it automatically. I've been working to get this to a reasonable testing state for a while and finally all the bits fell into place. There's quite a bit of change going on in the ARM Fedora 15 world. I would suggest regular "yum update" to get the latest builds. I'm not expecting to do regular builds of this, but will happily cut more builds if people think a new one would be useful. Unfortunately the fedora.repo and fedora-updates.repo are non-functional for Fedora 15 on ARM. Instead, I am now using the most current builds directly from a repository on the koji infrastructure: - http://arm.koji.fedoraproject.org/repos/dist-f15-build/latest/armhfp/ Does it make sense to create tickets for these kind of issues? Or is this email sufficient to help others? Thanks for the release, Niels Download from: http://build.laptop.org/F15-arm/os1/ For those interested in hardfp stuff enjoy :-) Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
On 01/03/2012 01:03 PM, Peter Robinson wrote: The "This sonic transducer, it is I suppose some kind of audio-vibratory-physio-molecular transport device?" release. THIS IS A DEVELOPMENT RELEASE AIMED AT CORE OS/HW DEVELOPERS This is a hard floating point Franken release for development and testing of the hardfp on the XO 1.75. Its very incomplete and has a number of things that don't work. This is expected and its a release only really intended for people that understandard what hardfp is and the significance of it and wish to test and develop further for this fairly major feature both for upstream Fedora and the XO releases. This isn't a release that shouldn't have bug reports against it. So what are the known issues, and what works? - X works using fbdev. There's an issue with resolution. Fix this by removing the "Virtual" line from /etc/X11/xorg.conf.d/xo1.75.conf - No accelerated X - Sugar and GNOME do work quite well - Networking seems to work OK - Firefox DOESN'T work. Known issue, hopefully should be fixed before long - Midori for GNOME, Surf for Sugar included as browsers. systemd is included (as it is Fedora 15) but does not really work by default. https://bugzilla.redhat.com/show_bug.cgi?id=704783 describes the same problem and points to a solution: - remove /var/run, /var/lock and /media from /etc/rwtab and reboot The change was made on a date after the version of initscripts that is installed was created. There are no Fedora ARM updates yet, but maybe a new version fixes it automatically. I've been working to get this to a reasonable testing state for a while and finally all the bits fell into place. There's quite a bit of change going on in the ARM Fedora 15 world. I would suggest regular "yum update" to get the latest builds. I'm not expecting to do regular builds of this, but will happily cut more builds if people think a new one would be useful. Unfortunately the fedora.repo and fedora-updates.repo are non-functional for Fedora 15 on ARM. Instead, I am now using the most current builds directly from a repository on the koji infrastructure: - http://arm.koji.fedoraproject.org/repos/dist-f15-build/latest/armhfp/ Does it make sense to create tickets for these kind of issues? Or is this email sufficient to help others? Thanks for the release, Niels Download from: http://build.laptop.org/F15-arm/os1/ For those interested in hardfp stuff enjoy :-) Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 release candidate 4 (build 883) released
On Tue, Nov 1, 2011 at 11:24 AM, Niels de Vos wrote: > Hi Gary, > > On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin > wrote: > ... >> I've just been testing Telescope-12 on the XO-1.75 running the new 883 >> build, first the good news, the camera is showing up correctly in Record and >> Telescope, fab! :) Now the not so hot: >> - While in Telescope-12, clicking the digital zoom toolbar button completely >> locked up the XO-1.75 (re-testing with an XO-1 the digital zoom works ok). >> - After some waiting and many attempted keyboard shortcuts, I decided to >> power down. Clicking the power hardware button did not trigger the usual >> shut down screen during this particular lockup case; clicking the power >> button twice (assuming it might just be the gfx that had locked-up) had no >> effect; finally I held down the power button for some seconds until the >> power led flashes and then the hard powers off. >> - On reboot the Journal now shows 3 corrupt entries (see attached screen >> shot) with no name and unknown metadata. None of the three entries allow >> invoking the details view or raise their palette so can not be erased via >> the Sugar Journal UI. The three corrupt entries will be an entry for Browse >> where I visited ASLO to download telescope and then quit Browse; the >> downloaded Telescope-12 bundle; and the instance entry for the Telescope >> that was running when the XO locked up. >> Given the nature of the hard power off I understand why some data would not >> have been synched to disk, but just wanted to raise this case here. I guess >> the actionable items might be: >> 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't >> have an XO-1.5 to test but I re-checked on an XO-1 which still worked fine). >> 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver >> related may have borked badly (I do have a serial cable here for un-bricking >> an XO-1.75 but don't know my way around that side of things very well). > > I tried to reproduce with Telescope, and I get an oops/hang as well. > The same oops is already filed as https://dev.laptop.org/ticket/11128. > > Using a serial console for logging may show if it is a panic/crash or > a hang (like a very busy loop). If you unbricked your XO-1.75 with an > other Linux system, you should be able to use minicom to capture a log > in a similar way. > > After starting minicom, press CTRL+a,z (press CTRL+a together, release > them, press 'z') to get in the minicom help/menu. Pressing 'l' will > ask you for a filename, I'd use samething like > xo-1.75-camera-issue.log. After pressing return, everything will be > saved. Now turn on the XO and reproduce the issue. > > When you encounter the panic/hang again, press CTRL+l in minicom to > close the logfile and exit minicom. > > I'll try this as well, but am still running build 882 which may be > differnt than build 883 in this respect. The result I have with build 882 and Telescope: - working nicely - click 'diigital zoom' - Telescope gets unresponsive (no picture anymore) - oops over the serial console - mouse and keyboard are still functioning - Telescope can be (forcefully) stopped - Telescope fails to sart (requires reboot) - no additional oopses recorded The oops is available in #11128. HTH Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 release candidate 4 (build 883) released
Hi Gary, On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin wrote: ... > I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, > first the good news, the camera is showing up correctly in Record and > Telescope, fab! :) Now the not so hot: > - While in Telescope-12, clicking the digital zoom toolbar button completely > locked up the XO-1.75 (re-testing with an XO-1 the digital zoom works ok). > - After some waiting and many attempted keyboard shortcuts, I decided to > power down. Clicking the power hardware button did not trigger the usual shut > down screen during this particular lockup case; clicking the power button > twice (assuming it might just be the gfx that had locked-up) had no effect; > finally I held down the power button for some seconds until the power led > flashes and then the hard powers off. > - On reboot the Journal now shows 3 corrupt entries (see attached screen > shot) with no name and unknown metadata. None of the three entries allow > invoking the details view or raise their palette so can not be erased via the > Sugar Journal UI. The three corrupt entries will be an entry for Browse where > I visited ASLO to download telescope and then quit Browse; the downloaded > Telescope-12 bundle; and the instance entry for the Telescope that was > running when the XO locked up. > Given the nature of the hard power off I understand why some data would not > have been synched to disk, but just wanted to raise this case here. I guess > the actionable items might be: > 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have > an XO-1.5 to test but I re-checked on an XO-1 which still worked fine). > 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver > related may have borked badly (I do have a serial cable here for un-bricking > an XO-1.75 but don't know my way around that side of things very well). I tried to reproduce with Telescope, and I get an oops/hang as well. The same oops is already filed as https://dev.laptop.org/ticket/11128. Using a serial console for logging may show if it is a panic/crash or a hang (like a very busy loop). If you unbricked your XO-1.75 with an other Linux system, you should be able to use minicom to capture a log in a similar way. After starting minicom, press CTRL+a,z (press CTRL+a together, release them, press 'z') to get in the minicom help/menu. Pressing 'l' will ask you for a filename, I'd use samething like xo-1.75-camera-issue.log. After pressing return, everything will be saved. Now turn on the XO and reproduce the issue. When you encounter the panic/hang again, press CTRL+l in minicom to close the logfile and exit minicom. I'll try this as well, but am still running build 882 which may be differnt than build 883 in this respect. Good luck, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F14-arm build os36 - Sugar in sync, device-tree!
On Tue, Aug 9, 2011 at 2:59 PM, Lennert Buytenhek wrote: > On Tue, Aug 09, 2011 at 02:49:42PM +0100, Niels de Vos wrote: > >> > >> = There is a new schedulear/timer patch from Lennert -- mystery >> > >> minutes-long hangs should be gone for real now. >> > > >> > > Do you have any references like a git-commit or discussion on a >> > > mailinglist for this? I'd like to match this with some other ARM >> > > hardware (non/OLPC) issues I have seen. >> > >> > There's a description of our problem at: >> > >> > http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0&id=b8923ed0809f29e53bd246153ca3a9e9367b4c56 >> >> Nice description! As it's mach-mmp dependent, it's unlikely that I can >> apply this for mx51 based systems. The information in the git-commit is >> clear and I'll try to investigate if 'sporadic hangs' could be caused >> due to missing events. (Which sounds sane, as it might happen when >> the system is under high load.) > > Looking at arch/arm/plat-mxc/time.c and its *_set_next_event() functions, > it appears to correctly handle the case where the timeout has already > expired, so it's not likely that mx51 is suffering from the same problem. Wow, thats a swift reply! Thanks for checking :) Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC Engineering] [Techteam] New F14-arm build os36 - Sugar in sync, device-tree!
On Mon, Aug 8, 2011 at 11:22 AM, Lennert Buytenhek wrote: > On Sat, Aug 06, 2011 at 03:44:09PM +0100, Niels de Vos wrote: > >> > = There is a new schedulear/timer patch from Lennert -- mystery >> > minutes-long hangs should be gone for real now. >> >> Do you have any references like a git-commit or discussion on a >> mailinglist for this? I'd like to match this with some other ARM >> hardware (non/OLPC) issues I have seen. > > I submitted it upstream here: > > http://marc.info/?l=linux-arm-kernel&m=131223859020216&w=2 > http://marc.info/?l=linux-arm-kernel&m=131223860820224&w=2 > http://marc.info/?l=linux-arm-kernel&m=131223862820251&w=2 > http://marc.info/?l=linux-arm-kernel&m=131223864920268&w=2 Cool, many thanks for pointing to the exact patches! Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F14-arm build os36 - Sugar in sync, device-tree!
On Sun, Aug 07, 2011 at 12:40:33PM -0400, Chris Ball wrote: > On Sat, Aug 06 2011, Niels de Vos wrote: > >> = We have device-tree! So what used to be in /ofw now appears in > >> /proc/device-tree . Time to port bitfrost, dracut-modules-olpc, sugar > >> control panel, olpc-utils. Thanks Andres, Mitch and Saadia! > > > > Wow, this is quite impressive! You must be one of the first that have this > > in a real distribution for ARM :) > > I think ChromiumOS is using flattened trees, but we're also running Open > Firmware and have it stay resident to be called into. Ah, didn't know ChromiumOS used it too. It may be that OpenFirmware makes it easier (as PPC gathered some initial experience with FDT), it's very cool never the less! > >> = There is a new schedulear/timer patch from Lennert -- mystery > >> minutes-long hangs should be gone for real now. > > > > Do you have any references like a git-commit or discussion on a > > mailinglist for this? I'd like to match this with some other ARM > > hardware (non/OLPC) issues I have seen. > > There's a description of our problem at: > > http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0&id=b8923ed0809f29e53bd246153ca3a9e9367b4c56 Nice description! As it's mach-mmp dependent, it's unlikely that I can apply this for mx51 based systems. The information in the git-commit is clear and I'll try to investigate if 'sporadic hangs' could be caused due to missing events. (Which sounds sane, as it might happen when the system is under high load.) Many thanks for your reply, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F14-arm build os36 - Sugar in sync, device-tree!
On Fri, Aug 05, 2011 at 06:52:56PM -0400, Martin Langhoff wrote: > The "Sugar in sync! device-tree" build. > > Download from: > > http://build.laptop.org/F14-arm/os32/ > > Use with OFW Q4B07 - > http://wiki.laptop.org/go/OLPC_Firmware_q4b07 > > Changes and notes: > > - sugar and sugar-toolkit rpms are at 0.92.4! > > - abiword and libabiword are in, but may have been built without asio > (the network/collaboration side) -- please test collaboration! > > - In kernel land... > > = We have device-tree! So what used to be in /ofw now appears in > /proc/device-tree . Time to port bitfrost, dracut-modules-olpc, sugar > control panel, olpc-utils. Thanks Andres, Mitch and Saadia! Wow, this is quite impressive! You must be one of the first that have this in a real distribution for ARM :) > = There is a new schedulear/timer patch from Lennert -- mystery > minutes-long hangs should be gone for real now. Do you have any references like a git-commit or discussion on a mailinglist for this? I'd like to match this with some other ARM hardware (non/OLPC) issues I have seen. I joined the OLPC mailinglists only a while ago, and I must say that I am really impressed with the work all of you are doing! It really seems that you make progress quickly. Congratulations with yet an other release update :) Cheers, Niels > - Some packages have been downgraded - need to work with Peter on these >-dracut-006-3.fc14.noarch >-dracut-modules-olpc-0.5.3-1.fc14.1.armv5tel >+dracut-006-2.fc14.noarch >+dracut-modules-olpc-0.5.3-1.fc14.armv5tel >-linux-firmware-20100806-4.fc14.noarch >+linux-firmware-20100106-4.fc14.noarch >-olpc-update-2.23-1.fc14.noarch >+olpc-update-2.22-1.fc14.noarch > > > Activity version changes: > > -Colors-15 > -Finance-3 > +Finance-5 > -Jukebox-21 > +Jukebox-22 > -Paint-35 > +Paint-36 > -StopWatch-10 > +stopwatch-11 > -TurtleArt-112 > +TurtleArt-113 > > Using Yum: > > The default yum config - which we include - points to the official > Fedora mirrors, and those don't really support unsupported > architectures like ARM. Surprise! > > Of course it's in my list of things to fix. In the meantime, here's > what you can do > > - edit /etc/yum.repos.d/fedora-update.repo -- look at the first > section, disable it (enabled=0) > > - edit /etc/yum.repos.d/fedora.repo -- look at the first section, > disable gpg checks (gpgcheck=0), comment out the mirrorlist line, and > add > baseurl=http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/ > > You're done! Note that it is a partial repo, and it only has the > packages at the F14 release time versions. Additionally, some packages > are missing or tagged wrong. > > If you want a package that is missing, ping Peter to see if it'll be > available soon. > > If you see a package or dependency bail out complaining about > python(abi)=2.6, let Peter know. The repo is just showing the wrong > package (and the right one is likely there). > > > > > m > -- > mar...@laptop.org -- Software Architect - OLPC > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [fedora-arm] Fedora 14 on armv5tel status update
On Mon, May 30, 2011 at 11:37 PM, Peter Robinson wrote: >> The glibc issue is interesting... it seems its a regression from F-13, >> we had to apply a patch for F-13 but even with all that in place I >> still get some failures. So it seems to be a regression (and we're >> seeing it on the F-15 glibc one as well. I'll do some more testing and >> follow up with the logs etc so that someone more smart than I am might >> be able to comment and assist :-) >> >> All help and feedback welcome :-D I've managed to build the F14 glibc on F13: - https://arm.koji.fedoraproject.org/koji/taskinfo?taskID=96723 If someone finds some time to test, please leave a note in https://bugzilla.redhat.com/show_bug.cgi?id=708452 or on this list. If there are any issues, I'll try to have a look at them. Cheers, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
