Re: Notes from an impromptu 8.2.1 Release Mtg.
2009/2/6 S Page i...@skierpage.com: In Sugar control panel Language, Swedish (Sweden) was highlighted! Sure enough, in the bash shell, LANG is set to sv_SE.utf8. I'm pretty sure I never chose that, and other settings like Date Time were unchanged. Has anyone else noticed Language changing? If you did olpc-update then you can hold a game key to boot back into your 8.2.0 build and see if things were the same there. (if so, it makes sense for that preference to have been copied) Why didn't Software update install the newer Browse (v.101 ?) that according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes addresses ticket #9112 Enable Browse to embed PDF files in itself Because it is a bit of a hack, aimed at deployments only. I don't think it will be presented as an update until the feature is properly implemented in sugar. Feel free to brush up the release notes. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
Why didn't Software update install the newer Browse (v.101 ?) that according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes addresses ticket #9112 Enable Browse to embed PDF files in itself Because it is a bit of a hack, aimed at deployments only. I don't think it will be presented as an update until the feature is properly implemented in sugar. Feel free to brush up the release notes. I see. Something which is a SUBSTANTIAL improvement (being able to view .pdf files without fetching them to Journal and separately launching Read) will be available only to deployments which explicitly ask for it - and not to general 8.2.1 users. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
2009/2/6 Mikus Grinbergs mi...@bga.com: I see. Something which is a SUBSTANTIAL improvement (being able to view .pdf files without fetching them to Journal and separately launching Read) will be available only to deployments which explicitly ask for it - and not to general 8.2.1 users. It's available to everyone, just not through the software update mechanism. Feel free to start a new thread if you think this should be proposed as an automatic 8.2 update - I don't have a strong argument against it. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
I updated from 8.2.0 build 767 to staging-27 with `sudo -v -v -v olpc-update staging-27` and it all went very smoothly! IMO, the expired http://wiki.laptop.org/go/Friends_in_testing/banner should be updated to staging-27 from staging-25 Good stuff -- * Restart from Home view worked (sometimes I have to go into a console and press keys to complete shutdown, but not this time) * Two startup chimes (I assume one was installing the new firmware) * By the time I allowed Software update to run I was connected to my wireless access point (with WEP security). * Software update offered no new activities (I had ran it the day before on build 767). Build : 27 Firmware : CL1 Q2E30 Q2E Libertas : 5.110.22.p23 Medium serious bugs --- Build '27' is confusing, especially when About my XO doesn't show your release or stream (Trac 8260). I updated the What release am I running? wiki page to mention this stream. In Sugar control panel Language, Swedish (Sweden) was highlighted! Sure enough, in the bash shell, LANG is set to sv_SE.utf8. I'm pretty sure I never chose that, and other settings like Date Time were unchanged. Has anyone else noticed Language changing? Why didn't Software update install the newer Browse (v.101 ?) that according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes addresses ticket #9112 Enable Browse to embed PDF files in itself A few minor things -- I see a [Discard network history] button in the Network panel, I didn't notice this before but I think it was in 8.2.0. The 8.2.0 manual http://www.laptop.org/8.2.0/manual/XO_Troubleshooting.html should mention this. In the Home view ring view, when I hide the frame (by moving away from a corner or pressing the Frame key), the very edge of the frame flickers white a few times. I didn't notice this before. Please please create Trac version Build 767 (8.2.0) (Trac bug 8904). Cheers, -- =S Page ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
2009/1/31 Hal Murray hmur...@megapathdsl.net: Probably best to upload somewhere and put a link here. http://www.megapathdsl.net/~hmurray/tmp/messages.11 It also contains the info from when I poked my icon and it worked. That starts at 08:49. I inserted a few blank lines at that point to separate it from the booting stuff. Thanks. This is very odd -- it appears that association and WPA handshake completes, but it receives no response to DHCP. I have finally got my hands on some APs which work reliably with WPA/WPA2 and reproduced this bug. I posted my results in a new thread titled 8.2.1 wireless testing results #2 Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
2009/1/30 Hal Murray hmur...@megapathdsl.net: It created a new version of /home/olpc/.sugar/default/nm/networks.cfg which differs from the old one only in time stamps and in having the bssids field filled in. Sounds like a pretty critical difference. I would recommend not using wpa.sh, or at least, not using it when discussing bugs about wireless. OLPC and the community can't support random scripts outside of the normal way of doing things. As far as I can tell, it's just like it was when I used Wpa.sh: The icon for my AP has a little star. It doesn't connect automatically on boot. I can see the icon blinking for a while. I assume that is when it is trying. It works when I poke the icon. That's after waiting for everything to stop blinking. OK. Next thing for you to try. Delete networks.cfg again, per Martin's instructions. Reboot, note that your AP has a padlock. Enter password until connected successfully. Then reboot, wait 5 minutes (regardless of whether it connects to your AP or not), and then send us /var/log/messages. And check that the AP icon now has a star, even if it doesn't autoconnect. One more question.. are you saying that build 9 works fine and later builds do not? That would be very odd because there have been no changes since build 9 that would affect this. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
OK. Next thing for you to try. Delete networks.cfg again, per Martin's instructions. Reboot, note that your AP has a padlock. Enter password until connected successfully. That's the state I'm currently in. networks.cfg was generated by typing in a password. Then reboot, wait 5 minutes (regardless of whether it connects to your AP or not), and then send us /var/log/ messages. And check that the AP icon now has a star, even if it doesn't autoconnect. Yes, the icon for my AP has a star. /var/log/messages is 63K. 644 lines, 328 from NetworkManager. Should I send it as email or put it someplace or ??? One more question.. are you saying that build 9 works fine and later builds do not? That would be very odd because there have been no changes since build 9 that would affect this. os759 automatically connected on startup. Build 9 is the first new software that I tried since then. It had the same symptoms as build 25. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Wifi is fine and dandy now that I updated to build staging-25 and firmware Q2E30. Weird seeing 'pretty boot' again. Sorry I never filed a ticketI'm ashamed to not know if my AP is WEP or WPA, (it's a cable modem-router-thingy SMC model SMC8014WG-SI)...how can I find out? For myself, I wanted to connect a staging-21 system to a wireless AP, but *could not* - no matter what I tried. [When I tried build 767 with the identical hardware and setup, it connected easily.] Ticket #9222 has been written about the WEP problem. I wrote -- View this message in context: http://n2.nabble.com/Notes-from-an-impromptu-8.2.1-Release-Mtg.-tp2201059p2251197.html Sent from the Software development mailing list archive at Nabble.com. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
2009/1/31 Hal Murray hmur...@megapathdsl.net: /var/log/messages is 63K. 644 lines, 328 from NetworkManager. Should I send it as email or put it someplace or ??? Probably best to upload somewhere and put a link here. Bear in mind that it is lost every reboot, so if you did not already take a copy, you should repeat the experiment before capturing again. Thanks! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
Probably best to upload somewhere and put a link here. http://www.megapathdsl.net/~hmurray/tmp/messages.11 It also contains the info from when I poked my icon and it worked. That starts at 08:49. I inserted a few blank lines at that point to separate it from the booting stuff. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
Hi Hal, I'm having trouble comprehending your mail 2009/1/30 Hal Murray hmur...@megapathdsl.net: [Context is WAP connection not getting set via NetworkManager] I expected this to get fixed in build 24. I grabbed build 25 since that announcement came by before I started pulling things over. I expected it to fix the startup problem (#9222), but it doesn't seem to be working for me. #9222 is unrelated to startup problems. It represents a total inability to connect to WEP networks at any point in time. Are you using a WEP network? I've rebooted a half-dozen times. It has never connected automatically. It works if I poke the icon. I don't think I could tell the difference between this one and 1352. What is 1352? joyride-1352? Ticket 1352? Have you ever connected to the network successfully (using staging-25)? If not, it will not attempt to connect on further boots. If yes, did you wait sufficiently long enough (perhaps as long as 5 minutes) for the XO to check mesh channels for school servers before consulting the history of infrastructure networks? If you did, then here are some diagnostics you can do: Firstly, you can check if the AP is marked as a favourite when it appears on the network view. It should have a star against the circular icon. Secondly, you can check that it is correctly represented in /home/olpc/.sugar/default/nm/networks.cfg Thirdly, you can share /var/log/messages. It is possible that during boot, you hit the bug (#8104) where a successful connection to your AP is established, but an internal failure in communications means that NM mistakenly believes the connection failed. This results in the XO trying other network connections (e.g. going back to meshing). I just attempted to reproduce on 2 laptops through this procedure: 1. Install staging-25 2. Boot, enter name and choose colour 3. Connect to our office infrastructure network 4. Reboot 5. A couple of minutes after booting, confirm that it has reconnected to the same infrastructure network. No problems found. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
I'm having trouble comprehending your mail Sorry if I wasn't clear. (If it was simple we wouldn't be having this discussion.) [I'm running with a B3 board in a B2 chassis, so there is a slight chance that this is confusing things. I doubt it, but standard disclaimer...] With old software, when I did a Restart from the GUI, or a fresh power up, my system would automatically connect via my Linksys AP. With the new software, that doesn't work. I thought build 24 was going to correct/restore this action, but maybe that fix referred to WEP vs WPA. (Or maybe I'm confused) Bottom line is that a setup that I assume will be common for G1G1 doesn't work for me when it did with (slightly?) older software. What is 1352? joyride-1352? Ticket 1352? Sorry, I didn't keep good notes. The real filename was very long so I renamed it to something reasonable, or at least it seemed reasonable at the time. It's joyride or whatever rather than a ticket. I think it came from a URL in a recent message to devel, probably early in this subject/thread. My quick attempts at tracking it down didn't get anywhere. I've got the MD5 file so we should be able to find it if it's worth the effort. Sorry. (It seemed obvious at the time.) Have you ever connected to the network successfully (using staging-25)? If not, it will not attempt to connect on further boots. If yes, did you wait sufficiently long enough (perhaps as long as 5 minutes) for the XO to check mesh channels for school servers before consulting the history of infrastructure networks? My current setup works if I wait a while after booting, then poke the icon for my AP. (There is a Connect choice, but no others. Just poking the icon without waiting for the menu does the right thing.) That's after running Wpa.sh which I got (ages ago) from ??? which writes some stuff to /home/olpc/.sugar/default/nm/networks.cfg It might be something like the magic info is passed via some environment variable which is different from background/NetworkManager and GUI/screem. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
2009/1/30 Hal Murray hmur...@megapathdsl.net: What is 1352? joyride-1352? Ticket 1352? Sorry, I didn't keep good notes. The real filename was very long so I renamed it to something reasonable, or at least it seemed reasonable at the time. It's joyride or whatever rather than a ticket. I think it came from a URL in a recent message to devel, probably early in this subject/thread. My quick attempts at tracking it down didn't get anywhere. I've got the MD5 file so we should be able to find it if it's worth the effort. I still don't understand which version you are comparing to. Can't you just go to the control panel and check? My current setup works if I wait a while after booting, then poke the icon for my AP. (There is a Connect choice, but no others. Just poking the icon without waiting for the menu does the right thing.) That's after running Wpa.sh which I got (ages ago) from ??? which writes some stuff to /home/olpc/.sugar/default/nm/networks.cfg What is wpa.sh and why do you have to use it? You do know that the OS supports WPA out-of-the-box (although unreliable with some APs), right? Other questions that it would be useful to know the answer to: Did you wait sufficiently long enough (perhaps as long as 5 minutes) for the XO to check mesh channels for school servers before consulting the history of infrastructure networks? Is the AP is marked as a favourite when it appears on the network view? It should have a star against the circular icon. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
I still don't understand which version you are comparing to. Can't you just go to the control panel and check? That only gets me the currently installed version. It takes a while to switch back to older versions. Let me try again. I'm using WPA, version 2 on a Linksys WRT54GL running their stock firmware. In the past few weeks, I've had 3 versions of software on my XO. I started with os759 from last Sept. I think that is what was released. Most of the time, when I power up or Restart, it connects automatically. I have to reboot a dozen times to get a case that fails. I could time the reboot process by starting a ping to my XO, rebooting the XO, stopping the ping, and computing the lost packets. There was no human activity in that process. A while ago, I tried the software that was announced in the message that started this thread. That's what I called 1352. It came from: http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build9/devel_jffs2 That directory contains: xo-1-olpc-stream-staging-build-9-20090106_1352-devel_jffs2.img which is what I installed. That web page says: OLPC Build staging-9 (devel_jffs2) Looks like I should have called it build 9. Sorry for the confusion. I've never seen that connect automatically. Most of the time, it worked when I poke the icon. A few days ago, I tried build 25. For me, it acts just the same as build 9 (1352) What is wpa.sh and why do you have to use it? You do know that the OS supports WPA out-of-the-box (although unreliable with some APs), right? It's a shell script that sets up the crypto stuff. I think it was announced on devel ages ago. My copy is dated Dec 2007. It writes to: conf=/home/olpc/.sugar/default/nm/networks.cfg It is option 4 from: http://wiki.laptop.org/go/WPA_Manual_Setting I use it because I have a big long password. It's much easier to select/stuff than type in. Is this the problem? Does the new/current NetworkManager and/or Sugar need some info in some other location? Somebody recognizes my AP since it has star on the icon and I don't need to enter a password when I poke the icon. Did you wait sufficiently long enough (perhaps as long as 5 minutes) for the XO to check mesh channels for school servers before consulting the history of infrastructure networks? I wait until the icons stop blinking. I haven't carefully reverse engineered the pattern and/or I'm not sure it's always the same, but it's something like scan the mesh channels, try my AP, then scan the mesh channels again. That takes a while, but it's less than 5 minutes. I have waited more than 5 minutes a few times when I got distracted doing something else. That didn't work. Is the AP is marked as a favourite when it appears on the network view? It should have a star against the circular icon. Yes the icon for my AP has the little star. (That's after running Wpa.sh I don't remember looking before running Wpa.sh) The star is how I find the icon to poke. There are several other APs within range, usually 2 to 4. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
On Sat, Jan 31, 2009 at 1:25 PM, Hal Murray hmur...@megapathdsl.net wrote: OLPC Build staging-9 (devel_jffs2) Looks like I should have called it build 9. Sorry for the confusion. I've never seen that connect automatically. Most of the time, it worked when I poke the icon. dsd is suggesting you wait, as it does a little dance before trying to reconnect. Can you try build 9 and/or 25, waiting? (and _not_ using wpa.sh - see notes below) What is wpa.sh and why do you have to use it? You do know that the OS supports WPA out-of-the-box (although unreliable with some APs), right? It's a shell script that sets up the crypto stuff. I think it was announced on devel ages ago. My copy is dated Dec 2007. It writes to: conf=/home/olpc/.sugar/default/nm/networks.cfg Try _deleting_ that file (with nm not running, as it'll recreate it), rebooting, connecting for the first time -- a dialog window will come up asking for the wpa passkey, provide it, and _then_ see if future reboots reconnect (after waiting, as dsd suggests). 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] Notes from an impromptu 8.2.1 Release Mtg.
Try _deleting_ that file (with nm not running, as it'll recreate it), rebooting, connecting for the first time -- a dialog window will come up asking for the wpa passkey, provide it, and _then_ see if future reboots reconnect (after waiting, as dsd suggests). I deleted the file and pulled the power plug (no battery) then powered up again. As expected, it didn't connect and my icon had a lock rather than a star. I poked connect and it asked for a password. The first try didn't take, maybe because I didn't get the password right. Trying again worked. It created a new version of /home/olpc/.sugar/default/nm/networks.cfg which differs from the old one only in time stamps and in having the bssids field filled in. As far as I can tell, it's just like it was when I used Wpa.sh: The icon for my AP has a little star. It doesn't connect automatically on boot. I can see the icon blinking for a while. I assume that is when it is trying. It works when I poke the icon. That's after waiting for everything to stop blinking. I've tried Restart-ing ~4 times by now. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
2009/1/29 Mikus Grinbergs mi...@bga.com: Remember - in addition to new function being tested, there ought to be regression testing (especially of vital things like wireless). I've been doing a lot of wireless testing with no problems. However, I only have one AP available to me. It would be useful if affected parties could file tickets for regressions. This is the way that developers prefer to attack problems. We had the first one filed yesterday (#9222), thanks! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
[Context is WAP connection not getting set via NetworkManager] I expected this to get fixed in build 24. I grabbed build 25 since that announcement came by before I started pulling things over. I expected it to fix the startup problem (#9222), but it doesn't seem to be working for me. I've rebooted a half-dozen times. It has never connected automatically. It works if I poke the icon. I don't think I could tell the difference between this one and 1352. Did I get confused, or is there another bug lurking here? About XO says Build 25 Sugar 0.82.1 Firmware Q2E30 uname -a says Linux xo-02-33-FF.localdomain 2.6.25-20090129.1.olpc.a3e1b6fe884eb2d #1 PREEMPT Thu Jan 29 09:07:09 EST 2009 i586 i586 i386 GNU/Linux -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Hal Murray wrote: For me, the new wireless is a step backwards. My setup used to fail occasionally. Now it connects occasionally. genesee wrote: wifi has been broken in staging-9 and 11 Pia Waugh added: I had a similar problem. I'm on a WEP network which worked fine on 8.2.0, but we simply can't connect on 8.2.1. The AP is a Billion brand. I can see the network, and am prompted for the password, but no joy! I've also booted three times and each time the two freshly imaged 8.2.1 laptops don't see each other. I had previously tried just installing the kernel rpm associated with ticket #9048, and noticed the same issue, so it might be a problem with that package, which is a new kernel :) For myself, I wanted to connect a staging-21 system to a wireless AP, but *could not* - no matter what I tried. [When I tried build 767 with the identical hardware and setup, it connected easily.] Ticket #9222 has been written about the WEP problem. I wrote #9223 (which might be a duplicate of #9222). Remember - in addition to new function being tested, there ought to be regression testing (especially of vital things like wireless). mikus p.s. Neighborhood View shows only one icon per XO, regardless of what IP address that XO might have. I have two XOs with 8.2.1 at home. If both are connected to the ethernet, both see each other (presumably through the respective ethernet IP addresses). If at least one of them is not connected to the ethernet, they still see each other (presumably through the respective mesh IP addresses). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
On Thu, Jan 29, 2009 at 01:26:45AM -0500, Mikus Grinbergs wrote: I had a similar problem. I'm on a WEP network which worked fine on 8.2.0, but we simply can't connect on 8.2.1. The AP is a Billion brand. I can see the network, and am prompted for the password, but no joy! I've also booted three times and each time the two freshly imaged 8.2.1 laptops don't see each other. I had previously tried just installing the kernel rpm associated with ticket #9048, and noticed the same issue, so it might be a problem with that package, which is a new kernel :) For myself, I wanted to connect a staging-21 system to a wireless AP, but *could not* - no matter what I tried. [When I tried build 767 with the identical hardware and setup, it connected easily.] Ticket #9222 has been written about the WEP problem. I wrote #9223 (which might be a duplicate of #9222). I just performed some more testing of this for Pia. When connecting through the GUI I can't connect to the AP at all using WEP. It simply keeps asking for the encryption key. However I can connect fine from the command line by doing iwconfig eth0 essid blah iwconfig eth0 mode Managed iwconfig eth0 key 1235... dhclient If I run iwconfig while the GUI is trying to connect I never see the encryption key set. So maybe network-manager isn't successfully setting the WEP key on the interface? Cheers, John -- John Bloghttp://www.inodes.org/blog OLPC Friends http://olpcfriends.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
2009/1/27 S Page i...@skierpage.com: `sudo olpc-update staging-9` gives I don't think the requested build number exists. I get the same for staging-11, I guess we have to use the full .img (or olpc-update --usb) for now: http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build11/devel_jffs2/ Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
We are definitely recommending that they stop using MPP mode (at least an automatic one.) On Jan 23, 2009, at 7:11 AM, Martin Langhoff wrote: On Thu, Jan 22, 2009 at 8:44 PM, Michael Stone mich...@laptop.org wrote: http://dev.laptop.org/report/38 A quick side-note here - reviewing the bugs listed there, I see we have a fix for dnsmasq in MPP mode, presumably for Uy. Are we recommending Uy that they stop using MPP mode? I think that there is fairly good consensus on that matter -- the reports of very bad RF saturation have been diagnosed to be cause by _all_ the laptops being in MPP mode. The RF saturation problems block any connectivity that you could hope to extend via MPP... cheers, martin -- 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Hal Murray wrote: please-help-test-this messages but I could easily have missed one. The latest version is Q2E28. I'm reasonably sure that it didn't get much testing since I just fixed a typo on the wiki page in the URL to download the bits. Anyway, most of the testing below was done with Q2E24. I've updated to Q2E28 and a quick test didn't show any changes. Right now e28 is what you should be testing. When the next f series release comes out (RSN) then that will be the new series going forward. Even when it isn't a total disaster, the cursor is still very hard to use. The problem seems to happen when I lift my finger off the pad so I can move it over and set it down to continue a long move. Yes, I could be being sloppy and moving before I lift, but I've been working/playing with it enough that I don't think it's me, or if it is, other normal users will be totally frustrated. Sometimes it jumps to the lower left corner. Again, this is a B2 chasis with a B3 board. If the cursor pad stuff has changed I apologize for the noise. In a B2 chassis you are going to see worse performance than later chassis as we added metal in the B3. And why do not have a MP (C2)? Mail me your shipping address and I'll see that you get a new machine. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Right now e28 is what you should be testing. When the next f series release comes out (RSN) then that will be the new series going forward. I just ran a half-dozen Restart cycles with e28. None of them connected automatically. All of them connected when I poked Connect. (One may have taken a second try.) I can see my icon blinking when the automatic stuff tries to connect. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Hal Murray wrote: Right now e28 is what you should be testing. When the next f series release comes out (RSN) then that will be the new series going forward. I just ran a half-dozen Restart cycles with e28. None of them connected automatically. All of them connected when I poked Connect. (One may have taken a second try.) I can see my icon blinking when the automatic stuff tries to connect. Thats expected. You should not see any behavior change in the wlan by changing the system firmware. The copy of the wlan firmware in the laptop system firmware is completely different than the copy of the wlan firmware that is in the OS build. The system firmware has zero influence on how the wlan device operates wrt to association. The only area where they interact at all is during suspend/resume and if you put the wlan into reset. Its confusing since there are 3 different firmwares on the XO and the wlan is duplicated in both the system firmware and the build. Often the wlan firmware in the system firmware is a different version than whats in the build. The build will normally be the latest with the copy in the system firmware getting upgraded as necessary. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Michael Stone wrote: ... how to push 8.2.1 a few inches closer to release. The main conclusion that we reached after we updated http://dev.laptop.org/report/38 was that staging-9 [1] needs some testing! http://wiki.laptop.org/go/Friends_in_testing still points to staging-7 and says The 8.2.1 build is currently identical to 8.2.0. ??! The instructions in Friends in testing say Clean-install the #Build under test, but I tried olpc-update from 8.2.0 anyway. `sudo olpc-update staging-9` gives I don't think the requested build number exists. `sudo olpc-update -v -v -v -v -v --latest=staging` gives Querying http://antitheft.laptop.org/antitheft/1/; (that's all) Is olpc-update possible, or are the instructions correct? :) -- =S Page ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
The main conclusion that we reached after we updated http://dev.laptop.org/report/38 was that staging-9 [1] needs some testing! In particular, it's got long-awaited new wireless firmware and wifi kernel drivers which means that we need to know whether it still associates with your crazy encrypted access points. :) [1]: (http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build9/devel_jffs2) That's Build 9, 1352 from 6-Jan. What firmware should we be testing? I'm using Q2E24. There are several later versions, but I didn't see anything that looks interesting in the web pages. I don't remember any please-help-test-this messages but I could easily have missed one. The latest version is Q2E28. I'm reasonably sure that it didn't get much testing since I just fixed a typo on the wiki page in the URL to download the bits. Anyway, most of the testing below was done with Q2E24. I've updated to Q2E28 and a quick test didn't show any changes. I have an early B3 board in a B2 chassis. So any or all of this may be a wild goose chase. It used to work reasonably well. I think It was the last major release. From the bits on my hard drive, that looks like 759. -- Several quirks: 1) During setup, I normally ssh in via an USB Ethernet dongle so I can run Wpa.sh. (I have a long password so select/stuff is much more convenient than typing it in.) DHCP didn't work automagically like I expected it to. I didn't investigate. ifconfig by hand worked. 2) For me, the new wireless is a step backwards. My setup used to fail occasionally. Now it connects occasionally. After it connects it seems to work OK. I'm using WPA version 2 on a Linksys WRT54GL There are usually 2 to 4 other systems visible. There are no other XOs nearby. (At least none that I know of.) I realize that occasionally isn't very precise. I don't have hard numbers. With the old system, roughly 9 out of 10 reboots automatically connected. I had to go looking for one that failed. (Normally, I don't reboot very often.) With the new code, I've rebooted 10 times so far, but I haven't see any of them connect automatically. I have seen the icon blinking while it tries. Usually it works when I manually poke connect. I got a bit frustrated the second reboot when 3 pokes in a row didn't work. At least once, the blinking icon stuff got confused. Maybe because the underlying control code was confused. I saw Mesh-11 blinking for a long time after I did a manual connect... Is there anything I can do to collect useful debugging info? 3) I have now seen to the crazy-cursor symptoms that have been discussed here quite a bit. It's possible that it's been there all along and I just haven't noticed it before or I didn't use the cursor pad enough to tickle it. This time, I discovered the Implode activity and I have been playing with it. It uses the cursor a lot. I've seen one time where it was nasty enough to make the cursor totally unusable. The cursor just kept jumping to the upper right corner. I tried rebooting. That didn't fix it. A power cycle did. That could be a wild goose chase. Even when it isn't a total disaster, the cursor is still very hard to use. The problem seems to happen when I lift my finger off the pad so I can move it over and set it down to continue a long move. Yes, I could be being sloppy and moving before I lift, but I've been working/playing with it enough that I don't think it's me, or if it is, other normal users will be totally frustrated. Sometimes it jumps to the lower left corner. Again, this is a B2 chasis with a B3 board. If the cursor pad stuff has changed I apologize for the noise. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
On Thu, Jan 22, 2009 at 8:44 PM, Michael Stone mich...@laptop.org wrote: http://dev.laptop.org/report/38 A quick side-note here - reviewing the bugs listed there, I see we have a fix for dnsmasq in MPP mode, presumably for Uy. Are we recommending Uy that they stop using MPP mode? I think that there is fairly good consensus on that matter -- the reports of very bad RF saturation have been diagnosed to be cause by _all_ the laptops being in MPP mode. The RF saturation problems block any connectivity that you could hope to extend via MPP... cheers, martin -- 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
Notes from an impromptu 8.2.1 Release Mtg.
Hi folks, Kim Quirk kindly stopped by #olpc-meeting this evening and precipitated an impromptu discussion between herself, me, cjb, edmcnierney, mchua, and garycmartin on how to push 8.2.1 a few inches closer to release. The main conclusion that we reached after we updated http://dev.laptop.org/report/38 was that staging-9 [1] needs some testing! In particular, it's got long-awaited new wireless firmware and wifi kernel drivers which means that we need to know whether it still associates with your crazy encrypted access points. :) At any rate, the bottom line is that YOU can personally help 100k kids in Uruguay get access to 8.2.* faster by helping to test this build. (Guadalupe and Emiliano in Uruguay have already helped to test fixes for some of the issues they found in 8.2.0 but more (your!) testing help is still needed!) So, on that note, thanks very much in advance for any help that you can provide. Voluntarily yours, Michael P.S. - Bryan -- would you please update FiT with instructions for staging-9 wifi-testing? P.P.S. - I'd like to host a test party at 1cc sometime in the next two weeks to try to do some large-scale collaboration and wifi testing such as was requested by dsd [2] in preparation for his trip to Paraguay tomorrow [3]. Would interested people who might be in Boston in the next two weeks please mail me to let me know good days and times for them to come help test? P.P.P.S. - The major coding work left before we can wrap up 8.2.1 is currently resting on Mitch Bradley's capable shoulders [4]. I'm looking forward to receiving a new OFW snapshot from him for testing in the not-too-distant future. [1]: (http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build9/devel_jffs2) [2]: http://wiki.laptop.org/go/Profiles/DanielDrake -- dsd, update you profile! [3]: http://wiki.laptop.org/go/Deployment_meetings/20090120#Summary [4]: http://wiki.laptop.org/go/Profiles/wmb ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
