Re: XO-1.5 video rendering not always smooth
> The support for the (brand new) video hardware > found in the XO-1.5 is still in teething stages -- this is why the > performance is bad. We've got the appropriate tickets open but it will > take us some time to get there. I searched, but did not find tickets specifically addressing "poor motion" nor "cursor flicker" on XO-1.5. Opened #9921 to make sure. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1.5 video rendering not always smooth
2009/12/20 Mikus Grinbergs : > In the new snow-1.xo Activity, the falling "white spots" are noticeably > jerkier in os64 (XO-1.5) than in os10 (XO-1). > > Also, on os64 the (software?) cursor sometimes "flickers" annoyingly. > It is always noticeable in the google-chrome browser (on Sugar), and for > instance in the new version of the cartoonbuilder-7.xo Activity. In > contrast, the (hardware?) cursor in the Opera browser operates smoothly > in os64 (on Sugar). Thanks for the report. The support for the (brand new) video hardware found in the XO-1.5 is still in teething stages -- this is why the performance is bad. We've got the appropriate tickets open but it will take us some time to get there. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1.5 video rendering not always smooth
In the new snow-1.xo Activity, the falling "white spots" are noticeably jerkier in os64 (XO-1.5) than in os10 (XO-1). Also, on os64 the (software?) cursor sometimes "flickers" annoyingly. It is always noticeable in the google-chrome browser (on Sugar), and for instance in the new version of the cartoonbuilder-7.xo Activity. In contrast, the (hardware?) cursor in the Opera browser operates smoothly in os64 (on Sugar). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XO 1.5 to XS-onXO1 behavior
On Sat, Dec 19, 2009 at 12:14 AM, James Cameron wrote: > On Fri, Dec 18, 2009 at 03:00:44PM -0800, Sameer Verma wrote: >> When the XO1.5 associates with school-mesh-0 (I have to click on it in >> the Neighborhood view) the association happens, but the XO1.5 gets >> 169.254.xxx.xxx address, and beyond that the network is unusable. > > This is http://dev.laptop.org/ticket/9768 and our current plan is > wontfix. Related, but this is a slightly different case from that bug: associating to the "mesh network" that XS-on-XO run. It is equivalent to running an XS with an oldstyle "active antenna". cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - 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
Re: Testing OS64 on XO1.5
On Sun, Dec 20, 2009 at 01:20:37PM -0500, milan zimmermann wrote: > 1) After reboot, or after a brief period of inactivity, the system > sometimes does not connect to network, [...] Deficiency of the B2 hardware, won't be fixed in B2, but will be (is) fixed in the next hardware revision. > 2) In the Record activity, sound does not work - I tried to record > some fairly loud speach, saved it on the bottom, but on replay of the > saved clipping, a very (etremely) low sound - almost no sound, > certainly not distinquishable at all. Speakers were unmute and on max. Thanks, I've reproduced this and raised a new ticket. #9375. http://dev.laptop.org/ticket/9920 > 3) Record activity does not maximize the camera view to the whole > screen (aftger hitting the maximize button) Known problem, ticket #9890. http://dev.laptop.org/ticket/9890 > 4) In Etoys, sound does work reasonably loud, but is very jittery. Known problem, ticket #9375. http://dev.laptop.org/ticket/9375 > 5) With power unplugged, leaving the XO1.5 untouched for 15 minutes > (or so, did not measure exactly), all lights go off, only the power > light flashes. This is OK, but no mouse or keyboard action , only > holding the power button for about 2 seconds, brought the system back > from sleep . Is this normal or expected? It does not seem right.. Intentional. > 6) There is no shell activity. Is that an intention to hide the > filesystem? Intentional, yes. It is only hidden. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Little issue with Midore
Hi, On Thu, Dec 17, 2009 at 20:38, César D. Rodas wrote: > Hello All, > > In the FC-11, The Midore Browser comes as the default browser. It looks > good so far, but it has a little bug, well it is not a proper bug, the > font-size is too big displaying messages. > > As I said before, it is not a proper bug, and I fixed it by setting the > default font size to 6px, in the ~/.config/midori/config, and it looks > better. Is there a way to set this configuration by default?, I think it > could be done in the RPM itself, in a %post stage. Not if this is a per user only setting. Isn't there a system-wide configuration file ? If so, this file could be modified in the RPM. Also, beware that the problem might not appear on a different screen than th XO's. So by fixing this bug for the XO screen, you might be introducing it (i.e. too small fonts) for other screens. > who is takes care of Midore (or perhaps Gnome) packaging? You can find that out using the Fedora PackageDB: https://admin.fedoraproject.org/pkgdb/packages/name/midori In our case, Peter Gordon is the Midori maintainer. If you want to report this issue, bugzilla would be the place to go. -- Mathieu Bridon (bochecha) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XO 1.5 to XS-onXO1 behavior
On Fri, Dec 18, 2009 at 03:00:44PM -0800, Sameer Verma wrote: > When the XO1.5 associates with school-mesh-0 (I have to click on it in > the Neighborhood view) the association happens, but the XO1.5 gets > 169.254.xxx.xxx address, and beyond that the network is unusable. This is http://dev.laptop.org/ticket/9768 and our current plan is wontfix. Other devices, like Mac OS X, try for DHCP before trying link-local. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Testing OS64 on XO1.5
milan wrote: > I was testing latest os (OS64) on XO1.5 with latest firmware (Q3A25) > this weekend. There are some thing that I think may be bugs, but > 5) With power unplugged, leaving the XO1.5 untouched for 15 minutes > (or so, did not measure exactly), all lights go off, only the power > light flashes. This is OK, but no mouse or keyboard action , only > holding the power button for about 2 seconds, brought the system back > from sleep . Is this normal or expected? It does not seem right.. this is normal. first the screen dims, but the laptop is still awake. after short time, the laptop will sleep, leaving the screen on. during this period keyboard/mouse activity will wake it up. 10 minutes later, the laptop will turn off the screen. at this point only the power button or the lid will wake it up. > > 6) There is no shell activity. Is that an intention to hide the filesystem? Terminal is there, it's just not marked as a "favorite" by default. on the home screen go to the list view (click in the far upper right. find Termina. and click in the star to make it a favorite. it will now appear in the ring when you go back to the previous view. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Testing OS64 on XO1.5
Milan - > 1) After reboot, or after a brief period of inactivity, the system > sometimes does not connect to network, or disconnects from the > network, and shows nothing on the network neigborhood screen (many > dots button), only the middle xo symbol, while there are many wireless > networks around - this happened at least five times in 6 hours of > testing, either aftrer reboot or after a brief inactivity. No such > problem on the XO1.0 system tested in parallel. This seems the biggest > issue. Thanks for the testing. All B2 XO-1.5 machines (virtually all of the ones distributed outside of OLPC) cannot resume properly after suspending. The WLAN will disappear and won't come back until you reboot. This sounds exactly like the symptom you're seeing. It's been fixed on later hardware and will be fixed in the production version, but it will never work properly on a B2 machine. If you need WLAN access after suspend/resume (which will indeed occur after a "brief inactivity") use the Sugar Control Panel / Power settings to disable automatic power management - both checkboxes on that panel should be cleared). If you don't need WLAN operation, it is helpful if you don't clear this setting, so suspend/resume operation continues to be tested for more bugs. - Ed ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Testing OS64 on XO1.5
I was testing latest os (OS64) on XO1.5 with latest firmware (Q3A25) this weekend. There are some thing that I think may be bugs, but before reporting it I'd like to see if others experienced similar problems. Everything below applies to Sugar on OS64 on XO1.5 - I did not test gnome. 1) After reboot, or after a brief period of inactivity, the system sometimes does not connect to network, or disconnects from the network, and shows nothing on the network neigborhood screen (many dots button), only the middle xo symbol, while there are many wireless networks around - this happened at least five times in 6 hours of testing, either aftrer reboot or after a brief inactivity. No such problem on the XO1.0 system tested in parallel. This seems the biggest issue. 2) In the Record activity, sound does not work - I tried to record some fairly loud speach, saved it on the bottom, but on replay of the saved clipping, a very (etremely) low sound - almost no sound, certainly not distinquishable at all. Speakers were unmute and on max. 3) Record activity does not maximize the camera view to the whole screen (aftger hitting the maximize button) 4) In Etoys, sound does work reasonably loud, but is very jittery. 5) With power unplugged, leaving the XO1.5 untouched for 15 minutes (or so, did not measure exactly), all lights go off, only the power light flashes. This is OK, but no mouse or keyboard action , only holding the power button for about 2 seconds, brought the system back from sleep . Is this normal or expected? It does not seem right.. 6) There is no shell activity. Is that an intention to hide the filesystem? Milan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
powerd or ohm?
Hi, I think f11 for the XO 1.5 uses ohmd but from a recent message from Paul I think the images for the XO-1 are configured to use powerd or at least doesn't start ohmd by default. Steve, is there any plan on this? Thanks, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XO 1.5 to XS-onXO1 behavior
On Sun, Dec 20, 2009 at 2:41 AM, John Gilmore wrote: > The least common denominator in the XO-1 and XO-2 clients is a > connection to an access point. So making the XS (on any hardware) > provide a standard 802.11 access point would probably be the easiest > path forward. That's right. But Sameer is asking about XO-1 hardware running the "XS" OS. When that happens, we don't require any extra hw, we just use the Libertas device as a mesh gateway. If you read back on this thread, you'll see discussion of hostap drivers too, to make it run as an AP. > As I recall there was some step in the XO-specific school > "provisioning" (antitheft DRM?) that only works over the mesh. Correct. Fixed in the 8.2.2 betas I've been publishing and on the F11 images too. As for the 1.5 running as an XS -- it is squarely on my list. I am talking with the Libertas team on the availability of a thinmac/thinfirm driver+firmware combo that works with hostap. Once that is available, the XO-1.5 can run its wifi as an AP. If you don't want to wait, you can always use a USB-Wifi that is known to work with hostap drivers under linux. Or a USB-ethernet + a conventional AP. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - 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
