Re: #9642 NORM 1.5-F11: OS37 -FW Q3A15: Gnome window movement crash
Effectively this happens only if I hit the left edge of the screen. Same issue. Thank you. 2009/11/10 Zarro Boogs per Child bugtrac...@laptop.org #9642: OS37 -FW Q3A15: Gnome window movement crash +--- Reporter: fmiceli | Owner: Type: defect| Status: closed Priority: normal| Milestone: 1.5-F11 Component: not assigned | Version: 1.5-B2 Resolution: duplicate |Keywords: os37 os36 q3a15i q3a15 gnome window crash Next_action: never set |Verified: 0 Deployment_affected:| Blockedby: Blocking:| +--- Changes (by Quozl): * status: new = closed * resolution: = duplicate Comment: almost certainly this is #9565, closing #9642 as a duplicate, please re- open if you have data that challenges this belief. -- Ticket URL: http://dev.laptop.org/ticket/9642#comment:4 One Laptop Per Child http://laptop.org/ OLPC bug tracking system ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO 1.5 - CONTENTION WINDOW
Hi, Looking for the reasons for low throughput on the XO 1.5 I've come across with the contention window's registers. I've found that there are like eight queues and that for all of them the CWmax and min are set as follows: CWmin = 7 slots CWmax = 31 slots As I see it this would make for a decrease in performance in situations with a high number of customers connected to the same AP. Can someone explain to me why these registers have been set to such values? Is this a mistake or it is something done for some reason in particular? Thanks. Franco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO 1.5 - CONTENTION WINDOW
What I was expecting was to have CWmax closer to 1024. What I think happens when you set CWmax to 31 is that -as you have more and more machines trying to compete for the medium- you could be having more colisions -since they would wait less time slots to tx and collisions would be more likely to happen. When you set CWmax to a higher value you prevent this situation. Of course this is for a higher number of machines using the medium. Maybe I'm wrong but this might be optimized for a certain number of machines. If so, could you tell me for what number? (not exactly just an estimate). Thanks Martin. Franco 2009/12/2 Martin Langhoff martin.langh...@gmail.com On Tue, Dec 1, 2009 at 5:43 PM, Franco Miceli fmic...@plan.ceibal.edu.uy wrote: Can someone explain to me why these registers have been set to such values? Is this a mistake or it is something done for some reason in particular? Hi Franco, What values are you expecting, and why? 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: XO 1.5 - CONTENTION WINDOW
Sure, I'm looking directly at the registers in the XO 1.5 B2 laptop. The process I follow is the following one: # mount -t debugfs null /mnt # cd /mnt/lbs_wireless/eth0/ To read register 0x # echo 0x rdmac ; cat rdmac MAC[0x0] = 0x0033fa05 I've read the following registers: 0xA0A0 - CWMin queue 0 0xA0A4 - CWMax queue 0 0xA0A8 - CWMin queue 1 0xA0AC - CWMax queue 1 0xA0B0 - CWMin queue 2 0xA0B4 - CWMax queue 2 0xA0B8 - CWMin queue 3 0xA0BC - CWMax queue 3 Now, this are the four queues I've read, and they have the values: CWmax = 31 CWmin = 7 The eight registers that follow this ones have the exact same pattern (7 31 7 31). That's why I mentioned eight queues (but I might be wrong and those other queues could be backups of the first ones). Thanks, Franco 2009/12/2 Daniel Drake d...@laptop.org On Wed, 2009-12-02 at 09:33 -0200, Franco Miceli wrote: What I was expecting was to have CWmax closer to 1024. What I think happens when you set CWmax to 31 is that -as you have more and more machines trying to compete for the medium- you could be having more colisions -since they would wait less time slots to tx and collisions would be more likely to happen. When you set CWmax to a higher value you prevent this situation. Of course this is for a higher number of machines using the medium. Could you directly reference the code that you are referring to, and the register documentation that you are looking at? Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO 1.5 - CONTENTION WINDOW
Daniel, I've not got such documentation, could you tell me where can I get it? Also - what does the firmware on the card do with that? Could it be overwritten by a DCW algorythm? -Martin Martin, No idea if that happens, I've only read such parameters since they were used also by the XO1.0 and assumed that they remained there for the XO 1.5. If I can get a copy of the documentation I may be able to understand a little bit more about this. Thanks, Franco 2009/12/2 Daniel Drake d...@laptop.org On Wed, 2009-12-02 at 10:06 -0200, Franco Miceli wrote: Now, this are the four queues I've read, and they have the values: CWmax = 31 CWmin = 7 The eight registers that follow this ones have the exact same pattern (7 31 7 31). That's why I mentioned eight queues (but I might be wrong and those other queues could be backups of the first ones). Ok, and what about the documentation? Are you sure that a value of 31 actually means 31 slots? On other wireless hardware I have worked with, this was not the case. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F11 for XO-1.5 build 61
Hi, I'm running OS61 with ofw q3a24. I've found that with the automatic power management option the XO puts the network down and then I can't reactivate it via the cli. Deactivating this option has fixed this issue for me in two XO 1.5. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Devel Digest, Vol 53, Issue 56
HI, I was wondering if there was a way to have a different resolution on the screen of the XO 1.5. I know that due to the DCON chip the res cannot be changed to other value that 1200x900, and have been told about Xephyr ( http://dev.laptop.org/ticket/10210). Does anyone have any thoughts/experiences on this? Thanks. Cheers Franco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Changing screen resolution XO 1.5
Sorry, Re: field corrected. Cheers 2010/7/30 Franco Miceli fmic...@plan.ceibal.edu.uy HI, I was wondering if there was a way to have a different resolution on the screen of the XO 1.5. I know that due to the DCON chip the res cannot be changed to other value that 1200x900, and have been told about Xephyr ( http://dev.laptop.org/ticket/10210). Does anyone have any thoughts/experiences on this? Thanks. Cheers Franco -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Changing screen resolution XO 1.5
Smaller. Actually the reason I want to change it is to test an app that was designed using a lower resolution. It's just for testing, so there's no intention of making the resolution change permanent. i just wanted to know if there was a way to modify it just to test the app. Cheers 2010/8/2 John Watlington w...@laptop.org The display resolution of the XO is fixed at 1200 x 900 on XO-1 and XO-1.5. We are considering a change to 1280 x 720 for XO-1.75, but it too would be fixed. Are you interested in a larger or smaller resolution ? Cheers, wad On Jul 30, 2010, at 7:45 AM, Franco Miceli wrote: Sorry, Re: field corrected. Cheers 2010/7/30 Franco Miceli fmic...@plan.ceibal.edu.uy HI, I was wondering if there was a way to have a different resolution on the screen of the XO 1.5. I know that due to the DCON chip the res cannot be changed to other value that 1200x900, and have been told about Xephyr ( http://dev.laptop.org/ticket/10210). Does anyone have any thoughts/experiences on this? Thanks. Cheers Franco -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Sugar and NetworkManager
Hi, I'm trying to improve the autoconnection algorithm NetworkManager uses to select the best AP to connect to -in the XO with F11-. I've succeeded in modifying the algorithm so that it connects to the known AP with best strength. The problem I'm having is that the XO's initial scans are poor in results and don't let NM autoconnection feature make a confident decision as to what AP to connect to. This is important for network planning issues in deployments. What I wanted to do was to execute a few scans before NM tries to autoconnect to any AP. That's why I have a question about how wireless interfaces get started in Sugar. I was under the impression that I could ask for the scans by editing the code where sugar starts the network interfaces. Sadly I'm not familiar with the code and don't know where to start. That's why I'm asking if anyone could point me in some direction (what .py/s to look for, where the interfaces get started) in order to accomplish what I want to do. I look forward to any tips anyone can provide. Thanks much for the help. Cheers, -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Possible bug between Sugar and NetworkManager F11
, and besides the time cost of checking the firmware version is higher than the time cost of just trying to receive the broadcast. The procedure is optimised for mass deployment, not mass upgrade. -- James Cameron http://quozl.linux.org.au/ -- Message: 10 Date: Thu, 2 Sep 2010 10:06:39 +1000 From: James Cameron qu...@laptop.org Subject: Re: Assignment of Network Interface Names To: Mikus Grinbergs mi...@bga.com Cc: OLPC Devel devel@lists.laptop.org,fedora-olpc-list fedora-olpc-l...@redhat.com Message-ID: 20100902000639.gu4...@us.netrek.org Content-Type: text/plain; charset=us-ascii On Wed, Sep 01, 2010 at 02:03:40PM -0500, Mikus Grinbergs wrote: The F14 developers' build assigns the radio as interface 'wlan0'. Thereby, it is my ethernet that gets assigned interface name 'eth0'. Yes, irritating isn't it? -- James Cameron http://quozl.linux.org.au/ -- Message: 11 Date: Thu, 2 Sep 2010 11:40:25 +0800 From: Huang, FrankR frankr.hu...@amd.com Subject: Question on Fedora 13 LiveCD install on hard disk? To: devel@lists.laptop.org Cc: fedora-olpc-l...@redhat.com Message-ID: dd1cc71b621b004fa76856e5129d6b170334d...@sbjgexmb1.amd.com Content-Type: text/plain; charset=us-ascii Hi, all I create a Fedora 13 Live CD and it can boot using CD-ROM. When I click the Install to Hard Disk in Menu, I got the error DBusException: org.freedesktop.DBus.Error.AccessDenied: Interface org.freedesktop.NetworkManager. I check this error, it has been reported on https://bugzilla.redhat.com/show_bug.cgi?id=626780. Is there some solution to this issue? Thanks, Frank -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel End of Devel Digest, Vol 55, Issue 3 -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Possible bug between Sugar and NetworkManager F11
Strange. But worth fixing. I doubt it is correct. Should I report it somewhere else so it can be worked on, or is it just here ok? I can't see in the code where this might be happening, but I can tell you where to look: I'll look to see if I can find the issue, bout I'm pretty new to this, and it could take me a long while to do. p.s. you sent back to the mailing list the whole digest message you received. Yes, sorry...Won't happen next time. Thanks so much for your answers. Cheers -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC wireless startup at boot time
I do not know if this things are related but there's a bug that I have reported to NM's bugzilla (*629661*https://bugzilla.gnome.org/show_bug.cgi?id=629661). The problem on the XO seems to be that while ListConnections on sugar reports all favourites to NM, when the XO starts NM only sees one favourite or none of them. This is a problem of NM, but also as you mention there's a problem with the scans, as debugging has shown a delay greater than 20s, and also that ListConnections reports everything and NM (using other methods: nm_manager_get_connections) does not get them all at the same time. If you see this NM debugging log ( https://bugzilla.gnome.org/attachment.cgi?id=171290) you can see that ListConnections -on NM Policy I think- reports all favourite user connections, while afterwards nm_get_connections does not find any of them. Later it does but it starts picking them up by stages -first one, then another one, etc.-. This is an issue since -at startup- NM does not get all the data it needs to make a (good) decision in order to connect to an AP. -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Jabber 2.1.5 on Debian6 and OS885
I've been trying to get ejabberd 2.1.5 to work with some XOs with OLPC OS855 image. I have followed the instructions on http://wiki.laptop.org/go/Installing_ejabberd/deb, configured the DN on the XOs but they keep talking salut (olpc-netstatus). Is Jabber still supported on the F14 builds (with ejabberd version 2.1.5)? Has anyone encountered this problem? Thanks in advance. -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
