Re: Update.1 690 very slow on B2-7 XO
The main problem with B2 is memory, not CPU speed. You can speed up your B2 machine by using the swap as the missing memory: * Plug a USB2 storage device * mkswap the device (mkswap /dev/sda1) * Activate the swap (swapon /dev/sda1) Technically, you can update fstab for automatic swap. Practically it's more complicated, and failed to automate the swap this way. Cheers, Zvi Jim Gettys wrote: On Wed, 2008-02-06 at 10:42 -0500, Stephen Bannasch wrote: We'ved ordered 2 of the G1G1 XOs for development at Concord Consortium but since they haven't arrived yet I installed Update.1 690 on one of our B2-7 XOs. The install completed and the system works but it is extremely slow -- many minutes to start applications or switch contexts (presumably because it only has 128MB of ram). Questions: * Is there anything we can do to speed up the B2-7 XO? No, we do not plan to support the B2's further. Every day, more MP systems get built than the sum of developer prototypes; it just doesn't make sense. Some things will eventually help B2's but we can't afford the testing time, so I expect things will stop working. I'm suprised you were able to install 690 on a B2 in the first place. * Are there any older services or configurations which need to be deleted or modified? * Is it possible to add more RAM? No. I did receive the G1G1 XO I ordered personally and both Eliza (9-yr old daughter) and I are very impressed. I'm looking forward to digging into the system. Glad you like it. - Jim ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preparing the XOs for next week's test
Kim, You can see the diffs here: http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html http://dev.laptop.org/%7Erwh/announcer/joyride_vs_update1.html You will see that there are plenty of new stuff in joyride than just a telepathy-salut update. One thing we can do is use 693 and install the specific package, or make a new Update.1 build that includes it. But we should test it individually before putting it in the update.1 build. One thing we can do is have half the XOs with 1721 in one channel, and the other half with 693 in another channel. Also, how about using B4s? Is there any effect in the performance except suspend/resume? I remember Ricardo saying there were hardware changes related to 4470. Ricardo, can you confirm this? If we decide on the build by tonight, I can have all the XOs updated and ready by tomorrow. On Sat, Feb 23, 2008 at 5:08 PM, Kim Quirk [EMAIL PROTECTED] wrote: Agreed that Read sharing is the highest priority application. My concern is if there are a lot of other things in joyride, then it will take us a long time to get a release out based on joyride. If we pull the fix for Read back into update.1, (and other things that we find next week), then we won't waste time on testing or finding bugs in joyride. Does anyone have a good feel for the differences between today's Update.1and joyride 1721 -- or can someone list the diffs so we can make a decision? Kim On Sat, Feb 23, 2008 at 8:13 AM, Walter Bender [EMAIL PROTECTED] wrote: Read sharing is a critical feature. Please do test it. -walter On 2/23/08, Morgan Collett [EMAIL PROTECTED] wrote: Giannis Galanis wrote: 2. I will try to update all of them with the build we will agree to initially test with. This would be 693/D13? There is a new version of telepathy-salut in 1721, which apparently only fixes smth related to stream tube flush(which i dont know what it is). I dont believe it important to our test. Other than that Update.1 i think should be ok. As I said in reply to Chris's mail, the salut fix is for Read in #6483. If you are going to test sharing PDFs in Read, please use Joyride-1721 otherwise there is a high chance it won't work at all under any conditions. Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender One Laptop per Child http://laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Sugar problems
I'm having a problem running Sugar on an amd64 linux computer. I downloaded and built Sugar using sugar-jhbuild, and using a hardlinked python in ~/bin. It built with no sugar-jhbuild warnings or errors (plenty of compiler warnings, nothing serious). I had a problem where it would say AttributeError: 'DeviceView' object has no attribute 'get_icon', but I fixed that fairly quickly by commenting out the lines that had the problem. A hackish fix, to be sure, but so far it seems to have worked. Now, I have a different problem. It says IOError: [Errno 2] No such file or directory: '/home/user/.sugar/default/datastore'. When I go mkdir -p ~/.sugar/default/datastore, I get a different error: (full error dump) Traceback (most recent call last): File /home/user/sugar/sugar-jhbuild/build/share/sugar/shell/view/Shell.py, line 93, in _start_journal_idle DBUS_PYTHON_TIMEOUT_UNITS_PER_SECOND) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/sugar/datastore/datastore.py, line 311, in mount return dbus_helpers.mount(uri, options, timeout=timeout) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/sugar/datastore/dbus_helpers.py, line 86, in mount return _get_data_store().mount(uri, options, timeout=timeout) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/sugar/datastore/dbus_helpers.py, line 39, in _get_data_store DS_DBUS_PATH), File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/bus.py, line 244, in get_object follow_name_owner_changes=follow_name_owner_changes) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/proxies.py, line 237, in __init__ self._named_service = conn.activate_name_owner(bus_name) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/bus.py, line 183, in activate_name_owner self.start_service_by_name(bus_name) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/bus.py, line 281, in start_service_by_name 'su', (bus_name, flags))) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/connection.py, line 607, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /home/user/sugar/sugar-jhbuild/build/bin/datastore-service exited with status 1 I rebuilt the datastore module, to no avail. I get the same problem. It seems to be that datastore is not running or something, or is timing out on dbus. Any suggestions? I'm running a 2.6.23-amd64 kernel on a Centrino Dual-core with Debian Lenny (testing), updated yesterday. Thanks. KAWK ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preparing the XOs for next week's test
Thanks Yani. I think we need to start with Update.1 and add the required fix(es) to that until we can get the next build together. Who can help with that? Ricardo, if you think there is anything else different with B4s in regards to network performance, please tell us. I'm not aware of anything in hardware. Dennis, Can you be prepared to quickly pull some builds together early next week? Thanks, Kim On Sun, Feb 24, 2008 at 4:39 PM, Giannis Galanis [EMAIL PROTECTED] wrote: Kim, You can see the diffs here: http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html http://dev.laptop.org/%7Erwh/announcer/joyride_vs_update1.html You will see that there are plenty of new stuff in joyride than just a telepathy-salut update. One thing we can do is use 693 and install the specific package, or make a new Update.1 build that includes it. But we should test it individually before putting it in the update.1 build. One thing we can do is have half the XOs with 1721 in one channel, and the other half with 693 in another channel. Also, how about using B4s? Is there any effect in the performance except suspend/resume? I remember Ricardo saying there were hardware changes related to 4470. Ricardo, can you confirm this? If we decide on the build by tonight, I can have all the XOs updated and ready by tomorrow. On Sat, Feb 23, 2008 at 5:08 PM, Kim Quirk [EMAIL PROTECTED] wrote: Agreed that Read sharing is the highest priority application. My concern is if there are a lot of other things in joyride, then it will take us a long time to get a release out based on joyride. If we pull the fix for Read back into update.1, (and other things that we find next week), then we won't waste time on testing or finding bugs in joyride. Does anyone have a good feel for the differences between today's Update.1 and joyride 1721 -- or can someone list the diffs so we can make a decision? Kim On Sat, Feb 23, 2008 at 8:13 AM, Walter Bender [EMAIL PROTECTED] wrote: Read sharing is a critical feature. Please do test it. -walter On 2/23/08, Morgan Collett [EMAIL PROTECTED] wrote: Giannis Galanis wrote: 2. I will try to update all of them with the build we will agree to initially test with. This would be 693/D13? There is a new version of telepathy-salut in 1721, which apparently only fixes smth related to stream tube flush(which i dont know what it is). I dont believe it important to our test. Other than that Update.1 i think should be ok. As I said in reply to Chris's mail, the salut fix is for Read in #6483. If you are going to test sharing PDFs in Read, please use Joyride-1721 otherwise there is a high chance it won't work at all under any conditions. Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender One Laptop per Child http://laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preparing the XOs for next week's test
Ricardo, if you think there is anything else different with B4s in regards to network performance, please tell us. I'm not aware of anything in hardware. They don't suspend. So if MP's have networking trouble that happens when a laptop suspends, the trouble won't happen on a B4. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preparing the XOs for next week's test
Right. But the suspend and resume problems we've seen with the mesh and sharing can be recreated on a relatively small number of laptops (10). So we will either fix the problems, or turn off suspend in order to test for scaling issues above 50. We have 50 MPs for next weeks testing. So we should be ok. Kim On Sun, Feb 24, 2008 at 10:12 PM, John Gilmore [EMAIL PROTECTED] wrote: Ricardo, if you think there is anything else different with B4s in regards to network performance, please tell us. I'm not aware of anything in hardware. They don't suspend. So if MP's have networking trouble that happens when a laptop suspends, the trouble won't happen on a B4. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preparing the XOs for next week's test
Kim, The suspend/resume problems will show even with 2 XOs. This cannot be fixed at the moment. As Michalis mentioned in another email, testing S/R and mesh scalability will just break the test. We have to test them invidually. On Sun, Feb 24, 2008 at 10:35 PM, Kim Quirk [EMAIL PROTECTED] wrote: Right. But the suspend and resume problems we've seen with the mesh and sharing can be recreated on a relatively small number of laptops (10). So we will either fix the problems, or turn off suspend in order to test for scaling issues above 50. We have 50 MPs for next weeks testing. So we should be ok. Kim On Sun, Feb 24, 2008 at 10:12 PM, John Gilmore [EMAIL PROTECTED] wrote: Ricardo, if you think there is anything else different with B4s in regards to network performance, please tell us. I'm not aware of anything in hardware. They don't suspend. So if MP's have networking trouble that happens when a laptop suspends, the trouble won't happen on a B4. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
