Re: New kernel branch for XO-1 and XO-1.5 development
On Thu, 2009-07-09 at 19:13 -0700, S Page wrote: On Thu, Jul 9, 2009 at 5:59 PM, Paul Foxp...@laptop.org wrote: plus, no immediate release for the XO-1 is even on the drawing board. D'oh! I would have thought OLPC deployments would want one software release for XO-1 and XO-1.5. Is a single image simply impossible for technical reasons -- different firmware, different NAND flash capacity, different file systems? Yes, impossible. I understand OLPC has extremely limited resources. Maybe you could provide the raw materials for builds together with scripts that let more expert users turn them into what they need. Given the XO-1.5 packages, an XO-1 kernel, the geode driver, the build scripts and a ton more l33t skillz would I be able to make my own XO-1 image? Everything is in the fedora-xo git repository in the xo-1.5 branch. I recently backported all of my XO-1.5 work to XO-1 (the kickstart changes really are only the handful that you mention) and it only took about an hour. I am looking to find some community members to do this as an ongoing process and publish the resultant builds. Adam found a couple of interested people but they have not yet made an appearance. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO-1 Camera in F11?
Has anyone seen the XO-1 camera working (or even just detected) in Record or Cheese with F11? I'm using the latest kernels with this change, so I don't think it's (just) that: http://lists.laptop.org/pipermail/devel/2009-May/024363.html Martin pgprjohfE4XhF.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 Camera in F11?
On Fri, Jul 10, 2009 at 11:43, Martin Denglermar...@martindengler.com wrote: Has anyone seen the XO-1 camera working (or even just detected) in Record or Cheese with F11? I'm using the latest kernels with this change, so I don't think it's (just) that: http://lists.laptop.org/pipermail/devel/2009-May/024363.html This is the relevant ticket in fedora's bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=498900 May be good to keep it updated. I'm adding fedora-olpc to cc in case someone there can help debugging this. Thanks, Tomeu Martin ___ 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: XO-1 Camera in F11?
On Fri, Jul 10, 2009 at 10:57 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Fri, Jul 10, 2009 at 11:43, Martin Denglermar...@martindengler.com wrote: Has anyone seen the XO-1 camera working (or even just detected) in Record or Cheese with F11? I'm using the latest kernels with this change, so I don't think it's (just) that: http://lists.laptop.org/pipermail/devel/2009-May/024363.html This is the relevant ticket in fedora's bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=498900 May be good to keep it updated. I'm adding fedora-olpc to cc in case someone there can help debugging this. The last time I tried it didn't work, its been on my todo list to retest a vanilla F11 on the XO for a while. Has the one line patch been pushed upstream yet? Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New kernel branch for XO-1 and XO-1.5 development
plus, no immediate release for the XO-1 is even on the drawing board. D'oh! I would have thought OLPC deployments would want one software release for XO-1 and XO-1.5. Is a single image simply impossible for technical reasons -- different firmware, different NAND flash capacity, different file systems? Yes, impossible. I understand OLPC has extremely limited resources. Maybe you could provide the raw materials for builds together with scripts that let more expert users turn them into what they need. Given the XO-1.5 packages, an XO-1 kernel, the geode driver, the build scripts and a ton more l33t skillz would I be able to make my own XO-1 image? Everything is in the fedora-xo git repository in the xo-1.5 branch. I recently backported all of my XO-1.5 work to XO-1 (the kickstart changes really are only the handful that you mention) and it only took about an hour. I am looking to find some community members to do this as an ongoing process and publish the resultant builds. Adam found a couple of interested people but they have not yet made an appearance. I discussed at Fudcon with Sebastian, Scott etc about resurrecting the Sugar Spin in Fedora which would allow us to have automated builds and make use of the new autoqa stuff. I can assist in this stuff as well if you like although at the moment I don't know how the laptop.org build stuff works or have access. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 Camera in F11?
On Fri, 2009-07-10 at 10:43 +0100, Martin Dengler wrote: Has anyone seen the XO-1 camera working (or even just detected) in Record or Cheese with F11? I'm using the latest kernels with this change, so I don't think it's (just) that: http://lists.laptop.org/pipermail/devel/2009-May/024363.html Is there a new error message or is it still the same one? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New kernel branch for XO-1 and XO-1.5 development
On Fri, 2009-07-10 at 11:12 +0100, Peter Robinson wrote: I discussed at Fudcon with Sebastian, Scott etc about resurrecting the Sugar Spin in Fedora which would allow us to have automated builds and make use of the new autoqa stuff. I can assist in this stuff as well if you like although at the moment I don't know how the laptop.org build stuff works or have access. I'd say that a Sugar spin isn't what you want here -- a Sugar spin should aim to be generic and be useful for more widespread testing of Sugar. For the XO, at this point, we still need special customization, including the kernel, some out-of-tree deployment technologies, etc. We also want it as slim as possible, and just with a few lines in a kickstart file you can do a lot better than a standard fedora install. The builds we're doing are just kickstart wrapped in a makefile and another script to turn a .iso into an appropriate image format. All the code is here: http://dev.laptop.org/git/projects/fedora-xo/ The xo-1.5 branch is where we're working. xo-1 is where I did a backport a few weeks ago. master is unused. The task at hand is simply syncing all changes from xo-1.5 to xo-1 on a continual basis, running make foo.img, publishing foo.img, and trying to act on user feedback as much as possible. (right now you will have to build and set up your own kernel repo for XO-1, but hopefully chris will have that automated soon: http://dev.laptop.org/ticket/9402) Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 Camera in F11?
On Fri, Jul 10, 2009 at 11:16:19AM +0100, Daniel Drake wrote: On Fri, 2009-07-10 at 10:43 +0100, Martin Dengler wrote: Has anyone seen the XO-1 camera working (or even just detected) in Record or Cheese with F11? I'm using the latest kernels with this change, so I don't think it's (just) that: http://lists.laptop.org/pipermail/devel/2009-May/024363.html Is there a new error message or is it still the same one? Can't find an error message now. kernel reports the chip was detected, as opposed to before: cafe1000-ccic :00:0c.2: enabling device ( - 0002) ov7670 1-0042: chip found @ 0x84 (cafe_ccic) Daniel Martin pgpNKyWXdhLWp.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New kernel branch for XO-1 and XO-1.5 development
On Fri, Jul 10, 2009 at 11:22:45AM +0100, Daniel Drake wrote: On Fri, 2009-07-10 at 11:12 +0100, Peter Robinson wrote: I discussed at Fudcon with Sebastian, Scott etc about resurrecting the Sugar Spin in Fedora which would allow us to have automated builds and make use of the new autoqa stuff. I can assist in this stuff as well if you like although at the moment I don't know how the laptop.org build stuff works or have access. I'd say that a Sugar spin isn't what you want here -- a Sugar spin should aim to be generic and be useful for more widespread testing of Sugar. From discussing with Peter last week, you're both talking about the same thing (different words, etc.). The task at hand is simply syncing all changes from xo-1.5 to xo-1 on a continual basis, running make foo.img, publishing foo.img, and trying to act on user feedback as much as possible. One also needs good bandwidth between the build machine and download site, which is all I'm lacking now or I'd be happy to do it...the problem is that I'd want to test the build before pushing, and I'd want to be able to distribute what I test. (right now you will have to build and set up your own kernel repo for XO-1, but hopefully chris will have that automated soon: http://dev.laptop.org/ticket/9402) One could also use http://dev.laptop.org/~mdengler/xo-1 Daniel Martin pgpoX0Uohpjhr.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 Camera in F11?
On Fri, Jul 10, 2009 at 11:02:48AM +0100, Peter Robinson wrote: On Fri, Jul 10, 2009 at 10:57 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Fri, Jul 10, 2009 at 11:43, Martin Denglermar...@martindengler.com wrote: Has anyone seen the XO-1 camera working (or even just detected) in Record or Cheese with F11? Has the one line patch been pushed upstream yet? I'm using the latest kernels with this change Yup. Peter Martin pgpTYjEE29vG2.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New kernel branch for XO-1 and XO-1.5 development
I discussed at Fudcon with Sebastian, Scott etc about resurrecting the Sugar Spin in Fedora which would allow us to have automated builds and make use of the new autoqa stuff. I can assist in this stuff as well if you like although at the moment I don't know how the laptop.org build stuff works or have access. I'd say that a Sugar spin isn't what you want here -- a Sugar spin should aim to be generic and be useful for more widespread testing of Sugar. From discussing with Peter last week, you're both talking about the same thing (different words, etc.). The task at hand is simply syncing all changes from xo-1.5 to xo-1 on a continual basis, running make foo.img, publishing foo.img, and trying to act on user feedback as much as possible. One also needs good bandwidth between the build machine and download site, which is all I'm lacking now or I'd be happy to do it...the problem is that I'd want to test the build before pushing, and I'd want to be able to distribute what I test. I have a server in france with a 100 meg link which I'm happy to run it on. Or can do so on dev.laptop.org if there's a procedure to get an account. (right now you will have to build and set up your own kernel repo for XO-1, but hopefully chris will have that automated soon: http://dev.laptop.org/ticket/9402) One could also use http://dev.laptop.org/~mdengler/xo-1 Daniel Martin Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New kernel branch for XO-1 and XO-1.5 development
On Fri, 2009-07-10 at 12:07 +0100, Martin Dengler wrote: One also needs good bandwidth between the build machine and download site, which is all I'm lacking now or I'd be happy to do it...the problem is that I'd want to test the build before pushing, and I'd want to be able to distribute what I test. I'm sure we could get you a machine at OLPC to do that. It would probably make sense to do it from the same one as XO-1.5 builds. Also I wouldn't worry about testing before publishing. We don't do it for XO-1.5 builds, never did it for joyride, etc. That's what users are for! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
recent olpc-update changes
Hi Martin, Thanks for your recent work on olpc-update. I'd like to propose a few changes though: 1. I think that checking for new leases every 15 minutes when expiry is near is too much. It will simply put too much load on any server that has to handle a lot of laptops when there are no new leases on it (for whatever reason). For a 4000 laptop deployment you're looking at 16,000 requests per hour or more. Remember that some of these servers may be internet-based, in which case it takes several seconds of socket tear-up/tear-down. All deployments using this security will need an alternative lease delivery mechanism anyway for the times when a laptop is reinstalled, or when it has not been turned on for a week, etc. This should not be too common, but it will not be overly uncommon either, and it's one of the things that even if it only happens occasionally in a deployment scenario, it's so so painful that you're going to need a solid system to fix it. Also, the statistics code does work well. I did quite a bit of testing of this in Paraguay. If the server has said that laptops should checks for updates every day, and you leave your laptop off for 2 days, next time you turn it on it's very likely to check immediately for a new lease. And if that doesn't happen, it's even more likely to do so 15 minutes later, etc. Instead, I would like to go back to the mechanism in my patch where the probability is modestly raised as lease expiry approaches. If deployments wish to make checks a lot more frequent, their OATS server can specify this. Realistically, even my probability increase will not be needed - if we assume kids use their laptops once per week, and that deployments will offer new leases on the server at least 1 week in advance of expiry, then the existing code will do a very fine job of phoning home as soon as the laptop is turned on. 2. Why did you rip out my parse the leases properly code (for determining the lease expiry date) and replace it with something uglier? :) I plan to reimplement this, exposing a proper interface from the bitfrost modules rather than just exposing the internals like I did before. 3. For time setting, the more sensible option is to set the system clock using date and then sync it to hardware using hwclock. Or is there a reason that you did it the other way around? The rest looks great :) Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
user-space XO hardware detection
It's getting more and more important to be able to detect XO hardware from userspace. One can no longer assume that Sugar implies XO because Sugar runs elsewhere and because non-Sugar is getting common on the XO. Considering the 1.5 hardware, assuming that Geode implies XO is not going to be reasonable either. I suppose the real needs are: 1. detect that the screen has XO-like blur 2. detect that the keyboard has XO-style keys 2a. detect that there is a multiply/divide key If possible I'd like to do this as a regular user, without X server help, in both Sugar and non-Sugar situations, despite any Bitfrost. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: recent olpc-update changes
On Sat, Jul 11, 2009 at 12:17 AM, Daniel Draked...@laptop.org wrote: Thanks for your recent work on olpc-update. I'd like to propose a few changes though: Thanks for the review! 1. I think that checking for new leases every 15 minutes when expiry is near is too much. It will simply put too much load on any server that has to handle a lot of laptops when there are no new leases on it (for Hmmm. I considered it carefully. My reasoning is as follows: - as soon as the server gives the lease, or answers 'STOLEN' it stops, so it won't insist... - in security-disabled scenarios this won't trigger (if you think it will, let's fix that bug) - if the lease _does_ expire, two bad things happen: - user gets a scary, different process - the get a lease from secure initrd code workflow _only works wirelessly with Active Antennas_, not with Access Points. So in 99.% of deployments it _does not work_; hence the try really hard stance. whatever reason). For a 4000 laptop deployment you're looking at 16,000 requests per hour or more. Remember that some of these servers may be internet-based, in which case it takes several seconds of socket tear-up/tear-down. 16K/ph requests isn't much for a webserver. And if it's an internet-based webserver (the central antitheft server) it _will_ know what to answer (new lease or 'stolen') so it's just 4K requests. And if it's the local XS, the traffic is much smaller... and it should know what to answer to local XOs. All deployments using this security will need an alternative lease delivery mechanism anyway for the times when a laptop is reinstalled, or when it has not been turned on for a week, etc. This should not be too common, but it will not be overly uncommon either, and it's one of the things that even if it only happens occasionally in a deployment scenario, it's so so painful that you're going to need a solid system to fix it. Agreed. I am attacking this two ways: - Fix initrd to work with APs. It's a bit out of my comfort zone but I'll eventually get it done. Help definitely welcome, and once we get it done we can ease off on the extreme eagerness you criticize above... - Make it easy to make a recovery leases.sig that has leases for all the relevant machines, valid for a day or two (good enough to get the machine to boot, and to get a lease via wireless). The Moodle side is done (so good for XS-delegated leases). Now, this will generate a large leases.sig which we fail to parse, so I am working on that. Also, the statistics code does work well. That's good to know! Instead, I would like to go back to the mechanism in my patch where the As I mentioned, that's more realistic once the initrd can associate to an AP-based wireless and get its lease there. 2. Why did you rip out my parse the leases properly code (for determining the lease expiry date) and replace it with something uglier? :) There is a proper parser for sig01 and sig02 in the bitfrost libs. Refactoring the correct parser to expose a parse it and just tell me expiry is a bit of a mission. I didn't see a clear way to get your parser to deal with sig01 and sig02 elegantly. All we need is a quick parser. We're after a simple value, not validation. The sig there has already been validated. The regex I implemented is fairly precise (no chance of mismatch with sig01/sig02 formats), and very efficient in programmer and cpu time. I plan to reimplement this, exposing a proper interface from the bitfrost modules rather than just exposing the internals like I did before. If you have the time, fantastic. If you're refactoring the bitfrostparser, btw, it'd be interesting to doublecheck that using -O doesn't make the code vulnerable. All those asserts do get bypassed with -O, and I'm not sure if the code still ensures correctness without them. 3. For time setting, the more sensible option is to set the system clock using date and then sync it to hardware using hwclock. Or is there a reason that you did it the other way around? I tried several ways. I settled on that order because - We care mainly about setting the hwclock - if we crash / restart right there, the truth is in the hwclock :-) - For consistency with the initrd code (activate.py) I wanted to do it in a way that busybox and standard hwclock/date could handle. The busybox version is quite a bit more limited, and IIRC there was a problem setting hwclock from system date, something about hwclock getting confused about the date format it got when reading the system time. You could read that second reason the other way around: I first got it running in the initrd (in activate.py) which took a bit of fiddling. Then I checked that standard hwclock acted consistent with busybox and copied the code verbatim. The rest looks great :) Thanks! (is there a rest? maybe the whitespace I trimmed? ;-) ) Let's get lease-requests working on an AP-controlled network. Once that works, then we can relax the request
Re: recent olpc-update changes
On Sat, 2009-07-11 at 04:12 +1200, Martin Langhoff wrote: As I mentioned, that's more realistic once the initrd can associate to an AP-based wireless and get its lease there. OK, so would you change your mind if that was the case? :) I already wrote that code and it is deployed in Paraguay. 2. Why did you rip out my parse the leases properly code (for determining the lease expiry date) and replace it with something uglier? :) There is a proper parser for sig01 and sig02 in the bitfrost libs. Refactoring the correct parser to expose a parse it and just tell me expiry is a bit of a mission. I didn't see a clear way to get your parser to deal with sig01 and sig02 elegantly. OK, will see if there is anything that can be done easily. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
2PM Boston Time TODAY/Thurs: Brief Contributors Program Mtg (#olpc-meeting)
Please join us (right now!) reviewing the latest OLPC/Sugar community projects over IRC Live Chat, 2PM EDT Boston Time Friday, right here right now :) http://forum.laptop.org/chat Then type at bottom: /join #olpc-meeting AGENDA: * New Libraries Coming! http://wiki.laptop.org/go/Projects#XO_Laptop_Lending_Libraries * Which projects might you enjoy Mentoring?! http://wiki.laptop.org/go/Projects http://rt.laptop.org/Search/Results.html?Query=Queue=%27contributors%27 * Fast Review of the 10 latest (greatest!) HW/Project Proposals -- please join us advocating for and/or reviewing shortcomings of these proposals: 1. Small Solutions Big Ideas - MASSACHUSETTS, USA http://rt.laptop.org/Ticket/Display.html?id=43314 http://smallsolutionsbigideas.org Requests 8 XO's for 2 months Project Objectives: Immediate objective is to raise awareness in Newburyport in order to raise money to set up a pilot project in a Kenyan village. 2. Nunnery Education, experimental model - NEPAL http://rt.laptop.org/Ticket/Display.html?id=43434 Requests 3-4 XO's indefinitely Project Objectives: The objectives of this project may seem ambitious. Jennifer desires to teach 60 nuns ages 6-15 basic computer skills, show them how to use the XOs, and integrate the XO education programs into the nunnery's existing curriculum in 6 weeks. Most likely, a follow-up volunteer will continue the work that Jennifer has started as it will be difficult to teach so many children these skills to the fullest with only a few XOs. However, if the project succeeds and both the nuns and full time teachers are receptive to the technology's integration into the curriculum, we may ask for more computers in the future. Depending on the effectiveness of existing programs, Jennifer may try to develop specific Nepali ESL programs for the purposes of this project, and if this occurs, she will definitely share the data with OLPC. 3. Moroccan Model XO Lending Library - MOROCCO / UK http://rt.laptop.org/Ticket/Display.html?id=43486 http://lists.laptop.org/pipermail/olpc-uk/2009-July/000336.html Requests 10 XO's initially? Project Objectives: Full proposal not yet written (British Moroccan Society) OLPC UK is offering them 1 XO to explore/refine their idea. 4. Journal for Sugar 0.86 - RUSSIA http://rt.laptop.org/Ticket/Display.html?id=43584 http://git.sugarlabs.org/users/alsroot http://wiki.sugarlabs.org/go/User:Alsroot#Todo Requests 1 XO for 24+ months Project Objectives: Support several projects http://git.sugarlabs.org/users/alsroot including core parts of sugar for example Journal for 0.86 release cycle Run activities in native XO environment, check performance and other XO related issues. 5. GreenThumb - PHILIPPINES http://rt.laptop.org/Ticket/Display.html?id=43621 http://thegreenthumb.blogspot.com Requests 2 XO's for 10 months Project Objectives: Generally, this project aims to develop a Sugar activity that can provide teachers an alternative way for demonstrating fundamental genetic concepts. This project also aims to inculcate, within the child, the importance of the environment, how relationships and interactions between plants, animals and humans can change (harm or make better) the world. Specifically, the project focuses on achieving the following: 1. To devise a game design incorporating mesh networking to achieve a mechanism for sharing of ideas, discussion and collaborative learning. 2. To design a system architecture for efficient use of memory in implementing simulation processes. 3. To develop a simple, easy-to-use, adaptable and fail-soft User Interface encouraging creative exploration among its users. 6. Using the XO Laptop to Teach Agriculture and Science - KENYA http://rt.laptop.org/Ticket/Display.html?id=43607 Requests 10 XO's Project Objectives: 1.To teach abstract concepts using illustrations from the XO laptop 2.To teach the children about different farming methods and tools using the XO laptop. 3.To develop XO videos showing different livestock breeds and crops. 4.To develop a weather chart using the XO for children to help teach them how to monitor the weather. 7. Using XO Technology Awareness on HIV/AIDS among children ages 4 – 16 - KENYA http://rt.laptop.org/Ticket/Display.html?id=43608 Requests 10 XO's 1.Develop a curriculum to address the absence of good HIV/AIDS in Kenyan education by using the XO interactive and individualized learning environment . 2.By the end of the program children should be able to know the nature of HIV/AIDS and various ways of contracting the disease; describe the negative effects; evaluate and make decisions about the ways to prevent the spreading of HIV/AIDS 3.Students will discuss and learn what it means to live with HIV/AIDS or have parents who are ill. 4.Identify support groups and organizations 8.
Re: recent olpc-update changes
martin.langh...@gmail.com said: As I mentioned, that's more realistic once the initrd can associate to an AP-based wireless and get its lease there. Let's get lease-requests working on an AP-controlled network. Once that works, then we can relax the request eagerness if desired. And hell, maybe even time to refactor bitfrost. What's the current status of the NetworkManager tangle? The old/released stuff (802) wasn't very happy with APs. -- 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: FIltering out languages via kickstart
I'm completely ignorant regarding how translations work even in plain Fedora and even more so for the OLPC systems, but pray tell, why can't these translations be shipped as regular Fedora updates? /abo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: recent olpc-update changes
On Fri, 2009-07-10 at 12:43 -0700, Hal Murray wrote: What's the current status of the NetworkManager tangle? The old/released stuff (802) wasn't very happy with APs. This is unrelated, we're talking about the initramfs. Feel free to start another topic with a more detailed report of your issues... Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1.5 microphone testing
Hi Dan, I have a board with the microphone ECO now. 2. In alsamixer, under Playback leave all PortX Jack controls as their defaults. Turn Master all the way up. Under Capture, you'll see a choice of 8 inputs. Go through them one by one while making some noise. Which one represents the internal microphone? Mic_C is external. Mic_B is internal. Mic_F is both off. 3. Once you know which of the 8 inputs represents the internal microphone, select it and experiment with the Analog Mic Boost/DMIC Mic Boost controls. Which one has effect? Of the one that has effect, which gain values are sensible? Analog Mic Boost has effect, DMIC Mic Boost does not. I think I like Capture volume at 80, Digital volume at 80, and Analog Mic Boost at 20dB, optimizing for clarity vs. volume of background noise. 4. Pick a sensible gain value and go back to Playback. Set the jack options for PortD and PortE to off. Make some noise, can you still hear it? I think PortD and PortE do absolutely nothing on our hardware so I want to harcode them to be permanently off. Confirmed, they do nothing here. 5. Experiment with PortB and PortC. Which one affects the internal microphone? Does 50% or 80% bias sound better? At this point you can hopefully reach a configuration where one port is set to Mic with a certain bias level, and the other 3 ports are Off, and you can still record and play audio, right? PortC affects the internal microphone. 50% and 80% sound identical to me, so perhaps we prefer 50%. 6. Select a good bias level and go back to capture. Experiment with the Digital volume control, what effect does this have? It has very similar effect to the main Capture control; 100 capture and 60 digital sounds identical to 80 Capture and 80 Digital to me. 7. Close alsamixer and start watching kernel debug messages. Plug in external microphone. Which new kernel messages appear? [ 974.423246] ALSA sound/pci/hda/patch_conexant.c:2268: CXT5066: unsol event e1a1 (38) [ 974.423299] ALSA sound/pci/hda/patch_conexant.c:2218: CXT5066: PortB automic present=8000 [ 974.423316] ALSA sound/pci/hda/patch_conexant.c:2149: CXT5066: select capture source 3 8. Open alsamixer again and repeat the above experiment. Note that when you plugged in the microphone, some settings may have been automatically changed. (it may have changed the PortX settings, and it will certainly have selected a microphone input under Capture although possibly the wrong one). Please also blow lightly into the internal microphone once you've found a good configuration for the external microphone, confirming that the internal one is muted. It correctly switched from internal mic over to external mic. Mic_B is active now and Mic_C isn't. The port settings are both on 50%, unchanged from before I plugged in the external mic. Speaker automuting seems to be working too; external mic is correctly routed to internal speakers once I unplug the external speakers. 9. please send full kernel logs of the whole session Attached. Thanks! - Chris. [0.00] Linux version 2.6.30-20090703.1.olpc.0517950 (d...@polyethylene) (gcc version 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 PREEMPT Fri Jul 3 18:52:37 BST 2009 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e801: - 0009f000 (usable) [0.00] BIOS-e801: 0010 - 3af53400 (usable) [0.00] DMI 2.1 present. [0.00] last_pfn = 0x3af53 max_arch_pfn = 0x10 [0.00] Warning only 895MB will be used. [0.00] Use a HIGHMEM enabled kernel. [0.00] init_memory_mapping: -37fa8000 [0.00] 00 - 40 page 4k [0.00] 40 - 0037c0 page 2M [0.00] 0037c0 - 0037fa8000 page 4k [0.00] kernel direct mapping tables up to 37fa8000 @ 7000-c000 [0.00] RAMDISK: 3af53600 - 3bdfd000 [0.00] Allocated new RAMDISK: 00939000 - 017e2a00 [0.00] Move RAMDISK from 3af53600 - 3bdfcfff to 00939000 - 017e29ff [0.00] ACPI: RSDP 000e 00024 (v02 OLPC ) [0.00] ACPI: RSDT 000e0040 00034 (v01 OLPC OLPC_000 30303030 OLPC 30303030) [0.00] ACPI: FACP 000e0080 00084 (v02 OLPC OLPC_000 30303030 OLPC 30303030) [0.00] ACPI: DSDT 000fc000 0270C (v01 OLPC XO-1.5 0001 INTL 20061109) [0.00] ACPI: FACS 000e0180 00040 [0.00] ACPI: DSDT 000fc000 0270C (v01 OLPC XO-1.5 0001 INTL 20061109) [0.00] ACPI: APIC
Re: FIltering out languages via kickstart
fre 2009-07-10 klockan 21:08 +0100 skrev Daniel Drake: OLPC has historically done releases every 6 months, and usually as it happens, the deployments receive the releases before creating a sufficiently sized translator team, so the translations come later. And in the past, only OLPC could make and sign builds. Now deployments can do this too, but it remains to be seen how realistic this is in the field. Unfortunately, a lot of deployments do not have the resources or know-how in order to do this. I see, thanks for the explanation. I wish I could suggest a pretty solution, but I know it's not that simple. :) /abo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: user-space XO hardware detection
On Fri, Jul 10, 2009 at 8:50 PM, Albert Cahalanacaha...@gmail.com wrote: It's getting more and more important to be able to detect XO hardware from userspace. One can no longer assume that Sugar implies XO because Sugar runs elsewhere and because non-Sugar is getting common on the XO. Considering the 1.5 hardware, assuming that Geode implies XO is not going to be reasonable either. I suppose the real needs are: 1. detect that the screen has XO-like blur 2. detect that the keyboard has XO-style keys 2a. detect that there is a multiply/divide key If possible I'd like to do this as a regular user, without X server help, in both Sugar and non-Sugar situations, despite any Bitfrost. You can probably poke HAL. http://pastebin.be/19650 will give you the vendor name (which should be OLPC). Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: FIltering out languages via kickstart
On Fri, 2009-07-10 at 21:58 +0200, Alexander Boström wrote: I'm completely ignorant regarding how translations work even in plain Fedora and even more so for the OLPC systems, but pray tell, why can't these translations be shipped as regular Fedora updates? Because we have no way of distributing such updates that is suitable for deployments. Also, for various reasons, many deployments run software that is no longer maintained. All of the XO deployments run sugar-0.82 on Fedora 9 but nobody is doing releases of that any more. OLPC has historically done releases every 6 months, and usually as it happens, the deployments receive the releases before creating a sufficiently sized translator team, so the translations come later. And in the past, only OLPC could make and sign builds. Now deployments can do this too, but it remains to be seen how realistic this is in the field. Unfortunately, a lot of deployments do not have the resources or know-how in order to do this. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: FIltering out languages via kickstart
Hi, 2009/7/11 Alexander Boström a...@root.snowtree.se: I'm completely ignorant regarding how translations work even in plain Fedora and even more so for the OLPC systems, but pray tell, why can't these translations be shipped as regular Fedora updates? There are quite a few reasons. For example, our official, stable build (version 8.2.1) is based on Fedora 9 (which has been officially end-of-lifed recently), and runs Sugar 0.82, which has not seen any package upgrade in at least the 6 months (I'm not blaming the Sugar devs here, they are resource-starved, and need to prioritize accordingly). I don't see the official build changing before the last quarter of this year, and I know for sure, that at least one large scale pilot (1000 machines) is going to be deployed for the first time a certain region (translations for at least one of the languages to be enabled in that pilot did not exist a few months back). Doing new package releases is not feasible in this scenario. Even when we have an up to date system (eg F11 based), translation is usually typically done in many cases via a set of translation sprints at the very last moment. Submitting those translations upstream, then chasing down each and every package maintainer (upstream as well as distro) to do new releases within a very short timeframe is not something that is realistically possible. Hence the need for decoupling our translation process from the release and packaging process. Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: user-space XO hardware detection
On Fri, Jul 10, 2009 at 11:20 AM, Albert Cahalanacaha...@gmail.com wrote: It's getting more and more important to be able to detect XO hardware from userspace. One can no longer assume that Sugar implies XO because Sugar runs elsewhere and because non-Sugar is getting common on the XO. Considering the 1.5 hardware, assuming that Geode implies XO is not going to be reasonable either. I suppose the real needs are: 1. detect that the screen has XO-like blur 2. detect that the keyboard has XO-style keys 2a. detect that there is a multiply/divide key Many of the XO-1 machines do not have a multiply/divide key. It is the language key on non-Latin alphabets. -walter If possible I'd like to do this as a regular user, without X server help, in both Sugar and non-Sugar situations, despite any Bitfrost. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: user-space XO hardware detection
On Fri, 2009-07-10 at 11:20 -0400, Albert Cahalan wrote: It's getting more and more important to be able to detect XO hardware from userspace. One can no longer assume that Sugar implies XO because Sugar runs elsewhere and because non-Sugar is getting common on the XO. Considering the 1.5 hardware, assuming that Geode implies XO is not going to be reasonable either. In the XO-1.5 builds, and the latest XO-1 builds that I have made locally based on the 1.5 work, we have enabled the smbios and are now using DMI for detecting XO-1 vs XO-1.5 vs other computers. You can read the info from /sys/class/dmi or from HAL. On XO-1 you need setup-smbios in boot.fth at the moment. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: user-space XO hardware detection
2009/7/10 Sayamindu Dasgupta sayami...@gmail.com: You can probably poke HAL. http://pastebin.be/19650 will give you the vendor name (which should be OLPC). Be careful. In current builds, that only works for XOs with ALPS touchpads. This will be fixed as we move to DMI-based detection. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO with no radio...
On Thu, Jul 09, 2009 at 11:10:58PM -0500, Sameer Verma wrote: lsmod shows usb8xxx and libertas missing. modprobe ing usb8xxx shows the modules via lsmod, but sitll no LED or other activity. I've a unit that does this. The wireless device also does not appear in lsusb or equivalent. I've not investigated it fully yet. -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: FIltering out languages via kickstart
Sayamindu, I like your answer but I think that it leaves some important goals unstated -- most notably, click2trans, horizontal distribution of translations, and translation undo. See http://cscott.net/Publications/OLPC/fudcon-i18n.pdf and http://lists.laptop.org/pipermail/devel/2008-June/015838.html for the writeups and http://dev.laptop.org/git/users/cscott/click2trans for the prototype code. Thoughts? Regards, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New kernel branch for XO-1 and XO-1.5 development
the problem is that I'd want to test the build before pushing, and I'd want to be able to distribute what I test. Also I wouldn't worry about testing before publishing. We don't do it for XO-1.5 builds, never did it for joyride, etc. That's what users are for! I'm someone who doesn't mind booting new builds to see what they would/would_not do. But please - I'd like *something* I can boot. As far as I can tell, the most recent build meant for an XO-1 was 'devxo-1' on 6/16/09. [Strawberry (6/22/09) was available as a general applicability .iso -- but on my XO-1 it had less capability than 'devxo-1' !] And I don't have any XO-1.5 motherboard to test XO-1.5 builds on. That's what users are for! -- not all those users have the resources to compile (then test) new builds/kernels themselves. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO with no radio...
This is the classic loss of WLAN problem with the XOs. We happen to still be looking for additional examples of those. Please send me the motherboards and I will send out replacement laptops (send mailing address.) There is nothing on the motherboard between the southbridge and the WLAN module. The solder connections to the WLAN module are generally very good. The general problem appears to be failure of either the 88W8388 itself or bad solder connections. I am trying to gather a second batch of samples concentrating on no WLAN. Cheers, wad On Jul 10, 2009, at 7:29 PM, James Cameron wrote: On Thu, Jul 09, 2009 at 11:10:58PM -0500, Sameer Verma wrote: lsmod shows usb8xxx and libertas missing. modprobe ing usb8xxx shows the modules via lsmod, but sitll no LED or other activity. I've a unit that does this. The wireless device also does not appear in lsusb or equivalent. I've not investigated it fully yet. -- James Cameronmailto:qu...@us.netrek.org http:// quozl.netrek.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: user-space XO hardware detection
On Fri, Jul 10, 2009 at 4:10 PM, Walter Benderwalter.ben...@gmail.com wrote: On Fri, Jul 10, 2009 at 11:20 AM, Albert Cahalanacaha...@gmail.com wrote: I suppose the real needs are: 1. detect that the screen has XO-like blur 2. detect that the keyboard has XO-style keys 2a. detect that there is a multiply/divide key Many of the XO-1 machines do not have a multiply/divide key. It is the language key on non-Latin alphabets. This is why I specifically mention it. Right now I'm facing a hack: if the screen is 1200x900, then we assume it's an XO. (both screen and keyboard) A hardcoded locale list is then consulted to determine if multiply/divide exists. Ew. Save me from this. BTW, last I looked it was painful to deal with D-BUS. I'd like to do things with as few libraries as possible, in plain C. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO with no radio...
On Fri, Jul 10, 2009 at 10:25 PM, John Watlington w...@laptop.org wrote: This is the classic loss of WLAN problem with the XOs. We happen to still be looking for additional examples of those. Please send me the motherboards and I will send out replacement laptops (send mailing address.) OK. Will do. I'm in Jamaica right now, leaving for San Francisco tomorrow. The broken XO is local. I'll swap mine (good one) with theirs and bring it across. I'll send you the motherboard from SF. Thanks everybody for sending out diagnostics. Sameer There is nothing on the motherboard between the southbridge and the WLAN module. The solder connections to the WLAN module are generally very good. The general problem appears to be failure of either the 88W8388 itself or bad solder connections. I am trying to gather a second batch of samples concentrating on no WLAN. Cheers, wad On Jul 10, 2009, at 7:29 PM, James Cameron wrote: On Thu, Jul 09, 2009 at 11:10:58PM -0500, Sameer Verma wrote: lsmod shows usb8xxx and libertas missing. modprobe ing usb8xxx shows the modules via lsmod, but sitll no LED or other activity. I've a unit that does this. The wireless device also does not appear in lsusb or equivalent. I've not investigated it fully yet. -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.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
