From pbrobinson at gmail.com Wed Apr 1 11:28:49 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 1 Apr 2009 12:28:49 +0100 Subject: rawhide builds Message-ID: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> Hey Chris, What's the status of the rawhide builds? I haven't seen one for a while. It would be good to get one based on F11Beta as it would provide a good point for testing from. Cheers, Peter From cjb at laptop.org Wed Apr 1 18:24:16 2009 From: cjb at laptop.org (Chris Ball) Date: Wed, 01 Apr 2009 14:24:16 -0400 Subject: rawhide builds In-Reply-To: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> (Peter Robinson's message of "Wed, 1 Apr 2009 12:28:49 +0100") References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> Message-ID: Hi Peter, > What's the status of the rawhide builds? I haven't seen one for a > while. It would be good to get one based on F11Beta as it would > provide a good point for testing from. Yeah! I'm interested in three things at the moment: * a standard live image for the beta with overlay, for USB and SD. * an "installed" image for the beta that can be flashed to NAND, and avoids the live image overhead. Sebastian's been working on making images like this using ImageCreator. * an image with the OLPC kernel rather than the Fedora one, so that people have a way to use suspend/resume with F11. This one is a little controversial, since our goal is to upstream everything rather than rely on our custom kernel -- it's clear that we aren't going to get suspend/resume upstream and back in time for F11, though, so I'd like to try out an image like this all the same. Help very welcome on any of these. :) - Chris. -- Chris Ball From pbrobinson at gmail.com Wed Apr 1 18:29:57 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 1 Apr 2009 19:29:57 +0100 Subject: rawhide builds In-Reply-To: References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> Message-ID: <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> Hi Chris, > ? > What's the status of the rawhide builds? I haven't seen one for a > ? > while. It would be good to get one based on F11Beta as it would > ? > provide a good point for testing from. > > Yeah! ?I'm interested in three things at the moment: > > * a standard live image for the beta with overlay, for USB and SD. > > * an "installed" image for the beta that can be flashed to NAND, > ?and avoids the live image overhead. ?Sebastian's been working > ?on making images like this using ImageCreator. > > * an image with the OLPC kernel rather than the Fedora one, so > ?that people have a way to use suspend/resume with F11. ?This > ?one is a little controversial, since our goal is to upstream > ?everything rather than rely on our custom kernel -- it's clear > ?that we aren't going to get suspend/resume upstream and back > ?in time for F11, though, so I'd like to try out an image like > ?this all the same. I've been meaning to ask about that.... what's the current difference between the standard Fedora kernel and the OLPC one. I've got a src rpm of it but haven't had time yet to unpack and investigate. I know of the dcon driver, and obv something that makes the suspend/resume work. What's stopping these from being upsteamed? Even if in the case of the dcon driver its in the staging area of the kernel? At a guess there's also something for rainbow, but I have no idea what else there would be. > Help very welcome on any of these. ?:) Happy to help, let me know where I can be helpful :-) Cheers, Peter From cjb at laptop.org Wed Apr 1 18:37:25 2009 From: cjb at laptop.org (Chris Ball) Date: Wed, 01 Apr 2009 14:37:25 -0400 Subject: rawhide builds In-Reply-To: <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> (Peter Robinson's message of "Wed, 1 Apr 2009 19:29:57 +0100") References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> Message-ID: Hi Peter, > I've been meaning to ask about that.... what's the current > difference between the standard Fedora kernel and the OLPC > one. As far as I know, it's: * open firmware interface (arch/x86/kernel/ofw.[ch]) * geode GPIO driver (used by DCON and suspend/resume) * dcon driver (drivers/video/olpc_dcon.[ch]) * suspend/resume code (arch/x86/kernel/olpc_pm.*) > What's stopping these from being upsteamed? Just the work of submitting them and responding to criticism, which is hard to find time for; OLPC doesn't employ any kernel hackers at the moment. Going with staging first does sound like a decent idea. Thanks, - Chris. -- Chris Ball From pbrobinson at gmail.com Wed Apr 1 18:47:48 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 1 Apr 2009 19:47:48 +0100 Subject: rawhide builds In-Reply-To: References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> Message-ID: <5256d0b0904011147q56b4f403r963605e9ec5db6a5@mail.gmail.com> Hi Chris, > ? > I've been meaning to ask about that.... what's the current > ? > difference between the standard Fedora kernel and the OLPC > ? > one. > > As far as I know, it's: > > * open firmware interface (arch/x86/kernel/ofw.[ch]) > * geode GPIO driver (used by DCON and suspend/resume) > * dcon driver (drivers/video/olpc_dcon.[ch]) > * suspend/resume code (arch/x86/kernel/olpc_pm.*) > > ? > What's stopping these from being upsteamed? > > Just the work of submitting them and responding to criticism, which is > hard to find time for; OLPC doesn't employ any kernel hackers at the > moment. ?Going with staging first does sound like a decent idea. By the sound of it getting that into staging would be a good way of getting it upstreamed, it would allow more feedback and testing without having to afaict do the full review and also get more eyes on it which would ultimately help get it mainline with some help from all of the kernel community. I think that fedora is enabling some features that are self contained in the staging part of the tree as well which would also allow us to use the main Fedora kernel. Peter From katzj at redhat.com Wed Apr 1 19:11:34 2009 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 1 Apr 2009 15:11:34 -0400 Subject: rawhide builds In-Reply-To: References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> Message-ID: <20090401191133.GB2854@redhat.com> On Wednesday, April 01 2009, Chris Ball said: > > What's stopping these from being upsteamed? > > Just the work of submitting them and responding to criticism, which is > hard to find time for; OLPC doesn't employ any kernel hackers at the > moment. Going with staging first does sound like a decent idea. staging is essentially a giant dumping ground of abandonware -- if you're going to put in the effort, please do it right. The whole "what's the fastest point from A->B" is why we're *in* this mess where there's a huge pile of not-upstreamed kernel code to begin with Jeremy From katzj at redhat.com Wed Apr 1 19:13:23 2009 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 1 Apr 2009 15:13:23 -0400 Subject: rawhide builds In-Reply-To: <5256d0b0904011147q56b4f403r963605e9ec5db6a5@mail.gmail.com> References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> <5256d0b0904011147q56b4f403r963605e9ec5db6a5@mail.gmail.com> Message-ID: <20090401191323.GC2854@redhat.com> On Wednesday, April 01 2009, Peter Robinson said: > > ? > I've been meaning to ask about that.... what's the current > > ? > difference between the standard Fedora kernel and the OLPC > > ? > one. > > > > As far as I know, it's: > > > > * open firmware interface (arch/x86/kernel/ofw.[ch]) > > * geode GPIO driver (used by DCON and suspend/resume) > > * dcon driver (drivers/video/olpc_dcon.[ch]) > > * suspend/resume code (arch/x86/kernel/olpc_pm.*) > > > > ? > What's stopping these from being upsteamed? > > > > Just the work of submitting them and responding to criticism, which is > > hard to find time for; OLPC doesn't employ any kernel hackers at the > > moment. ?Going with staging first does sound like a decent idea. > > By the sound of it getting that into staging would be a good way of > getting it upstreamed, it would allow more feedback and testing > without having to afaict do the full review and also get more eyes on > it which would ultimately help get it mainline with some help from all > of the kernel community. I think that fedora is enabling some features > that are self contained in the staging part of the tree as well which > would also allow us to use the main Fedora kernel. Fedora isn't enabling things from staging because they tend to be things which are poorly maintained and don't have a real path to upstream. Also, most of the pieces in question aren't drivers and thus couldn't go into staging anyway. And the one piece that is a driver (the dcon) ends up depending on some of the pieces which aren't. Jeremy From pgf at laptop.org Wed Apr 1 19:17:40 2009 From: pgf at laptop.org (pgf at laptop.org) Date: Wed, 01 Apr 2009 15:17:40 -0400 Subject: rawhide builds In-Reply-To: References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> Message-ID: <19078.1238613460@foxharp.boston.ma.us> chris wrote: > Hi Peter, > > > I've been meaning to ask about that.... what's the current > > difference between the standard Fedora kernel and the OLPC > > one. > > As far as I know, it's: > > * open firmware interface (arch/x86/kernel/ofw.[ch]) > * geode GPIO driver (used by DCON and suspend/resume) > * dcon driver (drivers/video/olpc_dcon.[ch]) > * suspend/resume code (arch/x86/kernel/olpc_pm.*) also parts of the HGPK touchpad: drivers/input/mouse/olpc.c i believe it's been upstreamed, but there are outstanding patches that need reworking before resubmission. paul =--------------------- paul fox, pgf at laptop.org From pbrobinson at gmail.com Wed Apr 1 19:18:25 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 1 Apr 2009 20:18:25 +0100 Subject: rawhide builds In-Reply-To: <20090401191323.GC2854@redhat.com> References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> <5256d0b0904011147q56b4f403r963605e9ec5db6a5@mail.gmail.com> <20090401191323.GC2854@redhat.com> Message-ID: <5256d0b0904011218o1e88b73ap5b4d1bb19eeedf7d@mail.gmail.com> >> > * open firmware interface (arch/x86/kernel/ofw.[ch]) >> > * geode GPIO driver (used by DCON and suspend/resume) >> > * dcon driver (drivers/video/olpc_dcon.[ch]) >> > * suspend/resume code (arch/x86/kernel/olpc_pm.*) >> > >> > ? > What's stopping these from being upsteamed? >> > >> > Just the work of submitting them and responding to criticism, which is >> > hard to find time for; OLPC doesn't employ any kernel hackers at the >> > moment. ?Going with staging first does sound like a decent idea. >> >> By the sound of it getting that into staging would be a good way of >> getting it upstreamed, it would allow more feedback and testing >> without having to afaict do the full review and also get more eyes on >> it which would ultimately help get it mainline with some help from all >> of the kernel community. I think that fedora is enabling some features >> that are self contained in the staging part of the tree as well which >> would also allow us to use the main Fedora kernel. > > Fedora isn't enabling things from staging because they tend to be things > which are poorly maintained and don't have a real path to upstream. > > Also, most of the pieces in question aren't drivers and thus couldn't go > into staging anyway. ?And the one piece that is a driver (the dcon) ends > up depending on some of the pieces which aren't. OK, wasn't aware staging was such a mess. Do you have any other suggestions as to the best way to get this stuff upstream? I'm not a kernel developer so its not something I see that I can take on effectively. Peter From skierpage at gmail.com Thu Apr 2 01:13:23 2009 From: skierpage at gmail.com (S Page) Date: Wed, 1 Apr 2009 18:13:23 -0700 Subject: rawhide builds In-Reply-To: References: <5256d0b0904010428s2f88952ap8b43abf3c0f90656@mail.gmail.com> <5256d0b0904011129r7a7690a8y94ddf0bff029e909@mail.gmail.com> Message-ID: <6509bebe0904011813h6a2176b7hc7166db67f2e67cc@mail.gmail.com> Scott Douglass in "using the stock OLPC kernel in F11/Rawhide" mentioned sound also: > It is possible to use the stock OLPC kernel which includes power > management, DCON and working audio drivers (at the least) with the > F11/Rawhide images that CJB is generating. Chris Ball wrote: > * open firmware interface (arch/x86/kernel/ofw.[ch]) > * geode GPIO driver (used by DCON and suspend/resume) > * dcon driver (drivers/video/olpc_dcon.[ch]) > * suspend/resume code (arch/x86/kernel/olpc_pm.*) pgf added > also parts of the HGPK touchpad: drivers/input/mouse/olpc.c > i believe it's been upstreamed, but there are outstanding patches that > need reworking before resubmission. (also I added a these in a kernel section to http://wiki.laptop.org/go/Rawhide-XO#Known_issues From cjb at laptop.org Fri Apr 3 19:51:59 2009 From: cjb at laptop.org (Chris Ball) Date: Fri, 03 Apr 2009 15:51:59 -0400 Subject: Announcing Fedora 11 Beta for XO Message-ID: Hi, Here's a build of the F11 beta release for XO: http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. Enjoy, - Chris, with thanks to the SoaS and Fedora teams. -- Chris Ball From pbrobinson at gmail.com Fri Apr 3 20:04:54 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Fri, 3 Apr 2009 21:04:54 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: References: Message-ID: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> The Fedora F11 beta announcement is here http://www.redhat.com/archives/fedora-devel-list/2009-March/msg02103.html Peter On Fri, Apr 3, 2009 at 9:01 PM, Carol Farlow Lerche wrote: > Chris, are there release notes somewhere? > > On Fri, Apr 3, 2009 at 12:51 PM, Chris Ball wrote: >> >> Hi, >> >> Here's a build of the F11 beta release for XO: >> >> ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ >> >> Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. >> >> Enjoy, >> >> - Chris, with thanks to the SoaS and Fedora teams. >> -- >> Chris Ball ? >> _______________________________________________ >> Devel mailing list >> Devel at lists.laptop.org >> http://lists.laptop.org/listinfo/devel > > > > -- > "It is difficult to get a man to understand something, when his salary > depends upon his not understanding it." -- Upton Sinclair > > _______________________________________________ > Devel mailing list > Devel at lists.laptop.org > http://lists.laptop.org/listinfo/devel > > From pbrobinson at gmail.com Fri Apr 3 20:24:14 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Fri, 3 Apr 2009 21:24:14 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: References: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> Message-ID: <5256d0b0904031324t577c9719ibd2319e6f6ce2296@mail.gmail.com> It is as far as I'm aware plain rawhide which means it will be sugar 0.84 with default Fedora power stuff using the new devicekit [1]. All the hardware should work as expected and if it doesn't please report it, either here or in the Fedora Bugzilla. Cheers, Peter [1] https://fedoraproject.org/wiki/Features/DeviceKit On Fri, Apr 3, 2009 at 9:15 PM, Carol Farlow Lerche wrote: > That is somewhat helpful, but I suppose I was hoping for the XO-specific > parts.? E.g. power management?? Does all the hardware work (leaving aside > the stylus area, of course)?? Is sugar installed and if so what version? > Does wifi definition work in the sugar gui?? That stuff. > > On Fri, Apr 3, 2009 at 1:04 PM, Peter Robinson wrote: >> >> The Fedora F11 beta announcement is here >> >> http://www.redhat.com/archives/fedora-devel-list/2009-March/msg02103.html >> >> Peter >> >> On Fri, Apr 3, 2009 at 9:01 PM, Carol Farlow Lerche >> wrote: >> > Chris, are there release notes somewhere? >> > >> > On Fri, Apr 3, 2009 at 12:51 PM, Chris Ball wrote: >> >> >> >> Hi, >> >> >> >> Here's a build of the F11 beta release for XO: >> >> >> >> ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ >> >> >> >> Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. >> >> >> >> Enjoy, >> >> >> >> - Chris, with thanks to the SoaS and Fedora teams. >> >> -- >> >> Chris Ball ? >> >> _______________________________________________ >> >> Devel mailing list >> >> Devel at lists.laptop.org >> >> http://lists.laptop.org/listinfo/devel >> > >> > >> > >> > -- >> > "It is difficult to get a man to understand something, when his salary >> > depends upon his not understanding it." -- Upton Sinclair >> > >> > _______________________________________________ >> > Devel mailing list >> > Devel at lists.laptop.org >> > http://lists.laptop.org/listinfo/devel >> > >> > > > > > -- > "It is difficult to get a man to understand something, when his salary > depends upon his not understanding it." -- Upton Sinclair > From cjb at laptop.org Fri Apr 3 20:27:31 2009 From: cjb at laptop.org (Chris Ball) Date: Fri, 03 Apr 2009 16:27:31 -0400 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: (Carol Farlow Lerche's message of "Fri, 3 Apr 2009 13:15:40 -0700") References: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> Message-ID: Hi Carol, > That is somewhat helpful, but I suppose I was hoping for the > XO-specific parts. E.g. power management? This build is pure Fedora, so there are many XO-specific things that do not work, but the build is still quite generally usable, and contains Sugar 0.84. We're looking at making a variant of this build including the XO kernel, which will go most of the way towards XO-specific hardware working. (But this isn't a long-term solution; we need to get our kernel stuff into the upstream kernel for that.) - Chris. -- Chris Ball From pgf at laptop.org Fri Apr 3 20:29:29 2009 From: pgf at laptop.org (pgf at laptop.org) Date: Fri, 03 Apr 2009 16:29:29 -0400 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <5256d0b0904031324t577c9719ibd2319e6f6ce2296@mail.gmail.com> References: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> <5256d0b0904031324t577c9719ibd2319e6f6ce2296@mail.gmail.com> Message-ID: <22758.1238790569@foxharp.boston.ma.us> peter wrote: > It is as far as I'm aware plain rawhide which means it will be sugar > 0.84 with default Fedora power stuff using the new devicekit [1]. All > the hardware should work as expected and if it doesn't please report > it, either here or in the Fedora Bugzilla. i don't understand. wasn't there just a thread yesterday or the day before about how there are major XO-specific pieces (e.g. suspend/resume, the dcon driver) missing from the fedora kernel? what do you mean by "hardware should work as expected"? paul > > Cheers, > Peter > > [1] https://fedoraproject.org/wiki/Features/DeviceKit > > On Fri, Apr 3, 2009 at 9:15 PM, Carol Farlow Lerche wrote: > > That is somewhat helpful, but I suppose I was hoping for the XO-specific > > parts.? E.g. power management?? Does all the hardware work (leaving aside > > the stylus area, of course)?? Is sugar installed and if so what version? > > Does wifi definition work in the sugar gui?? That stuff. > > > > On Fri, Apr 3, 2009 at 1:04 PM, Peter Robinson wrote: > >> > >> The Fedora F11 beta announcement is here > >> > >> http://www.redhat.com/archives/fedora-devel-list/2009-March/msg02103.html > >> > >> Peter > >> > >> On Fri, Apr 3, 2009 at 9:01 PM, Carol Farlow Lerche > >> wrote: > >> > Chris, are there release notes somewhere? > >> > > >> > On Fri, Apr 3, 2009 at 12:51 PM, Chris Ball wrote: > >> >> > >> >> Hi, > >> >> > >> >> Here's a build of the F11 beta release for XO: > >> >> > >> >> ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > >> >> > >> >> Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. > >> >> > >> >> Enjoy, > >> >> > >> >> - Chris, with thanks to the SoaS and Fedora teams. > >> >> -- > >> >> Chris Ball ? > >> >> _______________________________________________ > >> >> Devel mailing list > >> >> Devel at lists.laptop.org > >> >> http://lists.laptop.org/listinfo/devel > >> > > >> > > >> > > >> > -- > >> > "It is difficult to get a man to understand something, when his salary > >> > depends upon his not understanding it." -- Upton Sinclair > >> > > >> > _______________________________________________ > >> > Devel mailing list > >> > Devel at lists.laptop.org > >> > http://lists.laptop.org/listinfo/devel > >> > > >> > > > > > > > > > -- > > "It is difficult to get a man to understand something, when his salary > > depends upon his not understanding it." -- Upton Sinclair > > > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list =--------------------- paul fox, pgf at laptop.org From pbrobinson at gmail.com Fri Apr 3 20:36:05 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Fri, 3 Apr 2009 21:36:05 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <22758.1238790569@foxharp.boston.ma.us> References: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> <5256d0b0904031324t577c9719ibd2319e6f6ce2296@mail.gmail.com> <22758.1238790569@foxharp.boston.ma.us> Message-ID: <5256d0b0904031336t4c618733oe0e149f349a18bac@mail.gmail.com> > ?> It is as far as I'm aware plain rawhide which means it will be sugar > ?> 0.84 with default Fedora power stuff using the new devicekit [1]. All > ?> the hardware should work as expected and if it doesn't please report > ?> it, either here or in the Fedora Bugzilla. > > i don't understand. ?wasn't there just a thread yesterday or the > day before about how there are major XO-specific pieces (e.g. > suspend/resume, the dcon driver) missing from the fedora kernel? > what do you mean by "hardware should work as expected"? Yes. This isn't a joyride style build though. Its a Fedora build with sugar for the OLPC. See chris's follow up post. Peter From pgf at laptop.org Fri Apr 3 20:58:22 2009 From: pgf at laptop.org (pgf at laptop.org) Date: Fri, 03 Apr 2009 16:58:22 -0400 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <5256d0b0904031336t4c618733oe0e149f349a18bac@mail.gmail.com> References: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> <5256d0b0904031324t577c9719ibd2319e6f6ce2296@mail.gmail.com> <22758.1238790569@foxharp.boston.ma.us> <5256d0b0904031336t4c618733oe0e149f349a18bac@mail.gmail.com> Message-ID: <24848.1238792302@foxharp.boston.ma.us> peter wrote: > > ?> It is as far as I'm aware plain rawhide which means it will be sugar > > ?> 0.84 with default Fedora power stuff using the new devicekit [1]. All > > ?> the hardware should work as expected and if it doesn't please report > > ?> it, either here or in the Fedora Bugzilla. > > > > i don't understand. ?wasn't there just a thread yesterday or the > > day before about how there are major XO-specific pieces (e.g. > > suspend/resume, the dcon driver) missing from the fedora kernel? > > what do you mean by "hardware should work as expected"? > > Yes. This isn't a joyride style build though. Its a Fedora build with > sugar for the OLPC. See chris's follow up post. right. joyride or not, it's simply not the case that "hardware should work as expected". :-) paul =--------------------- paul fox, pgf at laptop.org From pbrobinson at gmail.com Fri Apr 3 21:11:37 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Fri, 3 Apr 2009 22:11:37 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <24848.1238792302@foxharp.boston.ma.us> References: <5256d0b0904031304w5d800a0flc5d8cc684757afda@mail.gmail.com> <5256d0b0904031324t577c9719ibd2319e6f6ce2296@mail.gmail.com> <22758.1238790569@foxharp.boston.ma.us> <5256d0b0904031336t4c618733oe0e149f349a18bac@mail.gmail.com> <24848.1238792302@foxharp.boston.ma.us> Message-ID: <5256d0b0904031411i20236c91o72ebaa47079ee1cf@mail.gmail.com> > ?> > i don't understand. ?wasn't there just a thread yesterday or the > ?> > day before about how there are major XO-specific pieces (e.g. > ?> > suspend/resume, the dcon driver) missing from the fedora kernel? > ?> > what do you mean by "hardware should work as expected"? > ?> > ?> Yes. This isn't a joyride style build though. Its a Fedora build with > ?> sugar for the OLPC. See chris's follow up post. > > right. ?joyride or not, it's simply not the case that "hardware > should work as expected". ?:-) Well if that's the case I look forwards to seeing all your bug reports :-D Pete From mikus at bga.com Fri Apr 3 21:28:00 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Fri, 03 Apr 2009 17:28:00 -0400 Subject: Announcing Fedora 11 Beta for XO Message-ID: <49D67F60.4030109@bga.com> Something doesn't match up. Have http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/20090403.img on my XO. When I do 'yum check-update', it lists some 200 packages which are at a lower version level that what is in the f11 repositories. mikus From rms at 1407.org Fri Apr 3 23:24:29 2009 From: rms at 1407.org (Rui Miguel Silva Seabra) Date: Sat, 4 Apr 2009 00:24:29 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: References: Message-ID: <20090403232429.GA7107@roque.1407.org> On Fri, Apr 03, 2009 at 03:51:59PM -0400, Chris Ball wrote: > Hi, > > Here's a build of the F11 beta release for XO: > > http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > > Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. Would love to, but it doesn't seem to boot for me, it just shows the child logo and doesn't move on :( Rui -- You are what you see. Today is Prickle-Prickle, the 21st day of Discord in the YOLD 3175 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? From rms at 1407.org Fri Apr 3 23:33:11 2009 From: rms at 1407.org (Rui Miguel Silva Seabra) Date: Sat, 4 Apr 2009 00:33:11 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090403232429.GA7107@roque.1407.org> References: <20090403232429.GA7107@roque.1407.org> Message-ID: <20090403233311.GB7107@roque.1407.org> On Sat, Apr 04, 2009 at 12:24:29AM +0100, Rui Miguel Silva Seabra wrote: > On Fri, Apr 03, 2009 at 03:51:59PM -0400, Chris Ball wrote: > > Hi, > > > > Here's a build of the F11 beta release for XO: > > > > http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > > > > Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. > > Would love to, but it doesn't seem to boot for me, it just shows the child > logo and doesn't move on :( Using and SD cart and the "bootable" image with zcat bla.gz | dd of=/dev/sdb bs=1m Either with the SD in the built-in slot or in the USB por with a card reader, the result is the same :( Rui -- Or is it? Today is Prickle-Prickle, the 21st day of Discord in the YOLD 3175 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? From cjb at laptop.org Sat Apr 4 05:05:19 2009 From: cjb at laptop.org (Chris Ball) Date: Sat, 04 Apr 2009 01:05:19 -0400 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090403232429.GA7107@roque.1407.org> (Rui Miguel Silva Seabra's message of "Sat, 4 Apr 2009 00:24:29 +0100") References: <20090403232429.GA7107@roque.1407.org> Message-ID: Hi Rui, > Would love to, but it doesn't seem to boot for me, it just shows > the child logo and doesn't move on :( * try holding down the check game-key as you turn on the XO * try upgrading to the newest OFW Does either help? - Chris. -- Chris Ball From martin.langhoff at gmail.com Sat Apr 4 11:05:39 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Sat, 4 Apr 2009 13:05:39 +0200 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: References: Message-ID: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> On Fri, Apr 3, 2009 at 9:51 PM, Chris Ball wrote: > Here's a build of the F11 beta release for XO: > > ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > > Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. How does this relate to the recent SoaS builds? I am trying to organise a test effort on Thursday, and was planning to target the latest SoaS on XO hw. Is this newer? Older? More XO-specific fixes? Less? cheers, m -- martin.langhoff at gmail.com martin at 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 From pbrobinson at gmail.com Sat Apr 4 11:13:36 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Sat, 4 Apr 2009 12:13:36 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> Message-ID: <5256d0b0904040413o45b08f73if3d845a043113ca6@mail.gmail.com> >> Here's a build of the F11 beta release for XO: >> >> ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ >> >> Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. > > How does this relate to the recent SoaS builds? > > I am trying to organise a test effort on Thursday, and was planning to > target the latest SoaS on XO hw. Is this newer? Older? More > XO-specific fixes? Less? I'm not sure what release of Fedora SoaS is based on. From the Fedora perspective this is the latest beta release, essentially a snapshot of rawhide on the way to F11. It has all the latest Sugar stuff in it but has no specific XO fixes in it. EG it doesn't have the XO specific kernel patches in it which I assume SoaS does. Its part of the process of getting all the XO/OLPC changes upstream into Fedora so that there isn't extra maintenance required by the OLPC/sugar/XO teams and they can concentrate on the more important things like sugar development rather than having to build packages for gstreamer or xulrunner or whatever. It would be great to get some testing done on it if possible to see what the issues are with it. I've been meaning on taking a look at SoaS to see what the differences are between that and rawhide but I just haven't had the time to do so yet. Peter From martin at martindengler.com Sat Apr 4 12:48:25 2009 From: martin at martindengler.com (Martin Dengler) Date: Sat, 4 Apr 2009 13:48:25 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <5256d0b0904040413o45b08f73if3d845a043113ca6@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <5256d0b0904040413o45b08f73if3d845a043113ca6@mail.gmail.com> Message-ID: <20090404124825.GN30746@ops-13.xades.com> On Sat, Apr 04, 2009 at 12:13:36PM +0100, Peter Robinson wrote: > >> Here's a build of the F11 beta release for XO: > >> > >> ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > >> > >> Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. > > > > How does this relate to the recent SoaS builds? > > > > I am trying to organise a test effort on Thursday, and was planning to > > target the latest SoaS on XO hw. Is this newer? Older? More > > XO-specific fixes? Less? > > I'm not sure what release of Fedora SoaS is based on. F11/rawhide. > From the Fedora perspective this is the latest beta release Is this statement meant to be equivalent to "this is the latest F11 beta"? > It has all the latest Sugar stuff in it but > has no specific XO fixes in it. EG it doesn't have the XO specific > kernel patches in it which I assume SoaS does. Soas does not, nor does http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ . I can't speak for the intentions of either "distro"s in the future. Please recall Soas is targeted at more than XOs...I would assume that the OLPC distro is more likely to include XO-specific bits than the Soas distro. But now we're both assuming, rather than asking. > It would be great to get some testing done on it if possible to see > what the issues are with it. I've been meaning on taking a look at > SoaS to see what the differences are between that and rawhide but I > just haven't had the time to do so yet. They're essentially the same right now apart from the choice of desktop environment. > Peter Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pbrobinson at gmail.com Sat Apr 4 13:07:53 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Sat, 4 Apr 2009 14:07:53 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090404124825.GN30746@ops-13.xades.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <5256d0b0904040413o45b08f73if3d845a043113ca6@mail.gmail.com> <20090404124825.GN30746@ops-13.xades.com> Message-ID: <5256d0b0904040607h44584e1tf7839392cacd045d@mail.gmail.com> >> From the Fedora perspective this is the latest beta release > > Is this statement meant to be equivalent to "this is the latest F11 > beta"? Now I read it, a fairly pointless statement.... should have coffee _BEFORE_ replying to emails in the morning. >> It has all the latest Sugar stuff in it but >> has no specific XO fixes in it. EG it doesn't have the XO specific >> kernel patches in it which I assume SoaS does. > > Soas does not, nor does > http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ . ?I can't speak for > the intentions of either "distro"s in the future. > > Please recall Soas is targeted at more than XOs...I would assume that > the OLPC distro is more likely to include XO-specific bits than the > Soas distro. ?But now we're both assuming, rather than asking. > >> It would be great to get some testing done on it if possible to see >> what the issues are with it. I've been meaning on taking a look at >> SoaS to see what the differences are between that and rawhide but I >> just haven't had the time to do so yet. > > They're essentially the same right now apart from the choice of > desktop environment. Yea, it seems that its basically very similar. Peter From martin at martindengler.com Sat Apr 4 13:10:50 2009 From: martin at martindengler.com (Martin Dengler) Date: Sat, 4 Apr 2009 14:10:50 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> Message-ID: <20090404131050.GQ30746@ops-13.xades.com> On Sat, Apr 04, 2009 at 01:05:39PM +0200, Martin Langhoff wrote: > On Fri, Apr 3, 2009 at 9:51 PM, Chris Ball wrote: > > Here's a build of the F11 beta release for XO: > > > > ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > > > > Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. > > How does this relate to the recent SoaS builds? > > I am trying to organise a test effort on Thursday, and was planning to I'd test Soas-2 (what I'm running on my XO now). Just a personal opinion. > Is this newer? Older? Only if rawhide / beta has changed > More XO-specific fixes? Less? The same. > cheers, > m Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From martin.langhoff at gmail.com Sat Apr 4 16:39:53 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Sat, 4 Apr 2009 18:39:53 +0200 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090404131050.GQ30746@ops-13.xades.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> Message-ID: <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> On Sat, Apr 4, 2009 at 3:10 PM, Martin Dengler wrote: > I'd test Soas-2 (what I'm running on my XO now). ?Just a personal > opinion. Yeah, that's what I am thinking of doing. Is there stuff that is known to be 'broken' on the XO? IIRC, the NM there can't handle the mesh devices, so no "under a tree" automagic mesh or ad-hoc networking is present. So not expecting that to work. Anything else? Sound? Sleep? Screen rotate? 'Game keys'? cheers, m -- martin.langhoff at gmail.com martin at 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 From cjb at laptop.org Sat Apr 4 16:51:47 2009 From: cjb at laptop.org (Chris Ball) Date: Sat, 04 Apr 2009 12:51:47 -0400 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> (Martin Langhoff's message of "Sat, 4 Apr 2009 13:05:39 +0200") References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> Message-ID: Hi Martin, > How does this relate to the recent SoaS builds? They're very similar, indeed. The rawhide-xo builds have both GNOME and Sugar for you to choose between, and we can imagine putting an OLPC kernel on to the XO builds to get better support, but otherwise they're pretty identical. - Chris. -- Chris Ball From pbrobinson at gmail.com Sat Apr 4 19:18:50 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Sat, 4 Apr 2009 20:18:50 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: References: Message-ID: <5256d0b0904041218m4084ef97w1a64705c8bbf4ba@mail.gmail.com> Hi Chris, Out of interest does OFW support ext4? I've tried today to get a SD card to boot using your image with no luck, but shoved a usb key in that has the standard F11 beta on it and the kernel booted straight up but got no further. Peter On Fri, Apr 3, 2009 at 8:51 PM, Chris Ball wrote: > Hi, > > Here's a build of the F11 beta release for XO: > > ? http://dev.laptop.org/~cjb/rawhide-xo/f11-beta/ > > Instructions on flashing are at http://dev.laptop.org/~cjb/rawhide-xo/. > > Enjoy, > > - Chris, with thanks to the SoaS and Fedora teams. > -- > Chris Ball ? > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > From martin at martindengler.com Sun Apr 5 12:25:40 2009 From: martin at martindengler.com (Martin Dengler) Date: Sun, 5 Apr 2009 13:25:40 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <5256d0b0904041218m4084ef97w1a64705c8bbf4ba@mail.gmail.com> References: <5256d0b0904041218m4084ef97w1a64705c8bbf4ba@mail.gmail.com> Message-ID: <20090405122540.GS30746@ops-13.xades.com> On Sat, Apr 04, 2009 at 08:18:50PM +0100, Peter Robinson wrote: > Out of interest does OFW support ext4? I've tried today to get a SD > card to boot using your image with no luck, but shoved a usb key in > that has the standard F11 beta on it and the kernel booted straight up > but got no further. If you got to the kernel and didn't see any initrd errors then OFW's job (finding the kernel and initrd) was done. I've noticed that if OFW can load the kernel but not the initrd it's hard to see that error - the failure message gets cleared away by the kernel loading messages. > Peter Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From martin at martindengler.com Sun Apr 5 12:43:07 2009 From: martin at martindengler.com (Martin Dengler) Date: Sun, 5 Apr 2009 13:43:07 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> Message-ID: <20090405124307.GT30746@ops-13.xades.com> On Sat, Apr 04, 2009 at 06:39:53PM +0200, Martin Langhoff wrote: > On Sat, Apr 4, 2009 at 3:10 PM, Martin Dengler wrote: > > I'd test Soas-2 (what I'm running on my XO now). ?Just a personal > > opinion. > > Yeah, that's what I am thinking of doing. Is there stuff that is known > to be 'broken' on the XO? > > IIRC, the NM there can't handle the mesh devices, so no "under a tree" > automagic mesh or ad-hoc networking is present. So not expecting that > to work. Indeed, mesh doesn't work. > Sound? Not sure (I thought it worked but haven't checked recently). > Sleep? Nope > Screen rotate? Nope > 'Game keys'? Nope Other things OTTOMH: - Most / all of the XO-specific keys don't work. The keymap isn't set to an OLPC one at boot (these are two seperate problems). - DCON driver isn't available - so forget about coming out of pretty boot (use the check key when starting to avoid pretty boot) - or changing the backlight level, etc.) - /ofw doesn't exist - network frame icon still blank (I think for the same reason as http://dev.sugarlabs.org/ticket/307 ) - some WPA (1) networks unable to be associated with (not sure why, could be #307 again) > cheers, > m Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From fab at fedoraproject.org Sun Apr 5 13:25:22 2009 From: fab at fedoraproject.org (Fabian Affolter) Date: Sun, 05 Apr 2009 15:25:22 +0200 Subject: Pippy Message-ID: <49D8B142.4090509@fedoraproject.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, At the moment I'm trying to update the RPM package of Pippy to 31. But now I have some rpmlint errors. Two of them are: sugar-pippy.i386: E: arch-dependent-file-in-usr-share /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux64/_Box2D2.so sugar-pippy.i386: E: arch-dependent-file-in-usr-share /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux32/_Box2D2.so Any inputs for the proceeding? Thanks in advance. Fabian - -- Fingerprint: 2F6C 930F D3C4 7E38 6AFA 4EB4 E23C D2DD 36A4 397F Fedora always leads and never follows. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAknYsUAACgkQ4jzS3TakOX+AbACfUX4NjqdBNKa3JDQbmVMcE08t aPIAn35b8WLoUjwgg+DwFWpjuiiUI1Sh =YkEp -----END PGP SIGNATURE----- From fab at fedoraproject.org Sun Apr 5 13:37:57 2009 From: fab at fedoraproject.org (Fabian Affolter) Date: Sun, 05 Apr 2009 15:37:57 +0200 Subject: Help activity In-Reply-To: <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> Message-ID: <49D8B435.6080305@fedoraproject.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, In the repos (the one at sugarlabs.org and dev.laptop.org) is Version 7 of 'help' available but there is a new image (Version 10) mentioned on the wiki page [1]. Where is the new source? Or is this just a mistake? BTW, does anybody know where the source tarball of help could be found? Kind regards, Fabian [1] http://wiki.laptop.org/go/Help_(activity) - -- Fingerprint: 2F6C 930F D3C4 7E38 6AFA 4EB4 E23C D2DD 36A4 397F Fedora always leads and never follows. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAknYtDQACgkQ4jzS3TakOX+TxQCfb+tCwgI0ggnZYFzW5xNN29N6 CZ8AnjKHE9rZklDB6djTxv8v5tDAM1pY =skhG -----END PGP SIGNATURE----- From martin at martindengler.com Sun Apr 5 13:53:36 2009 From: martin at martindengler.com (Martin Dengler) Date: Sun, 5 Apr 2009 14:53:36 +0100 Subject: F11 kernel for XO-1 Message-ID: <20090405135336.GU30746@ops-13.xades.com> Hi, I've rebuilt a patched F11 kernel for my XO-1 in order to: 1) get it booting without an initrd and with compcache/ramzswap patch 2) get the olpc-specific patches merged into an F11-based kernel (for my personal use and testing, others' use/testing, and any help it could provide in upstreaming the OLPC-specific patches) 3) convince myself it could be done by mere mortal - note an issue I ran into in step #10 of the process I document below The benefits of this kernel are: 1) it boots on the XO-1 without an initrd (I've compiled in jffs2) 2) it does not use an extra ~22MB of memory like the current F11/SoaS kernels 3) compcache/ramzswap is compiled in This kernel is for XOs. It, like past OLPC kernels, lacks some of the more general (esoteric?) modules that get built by default. The packages are available here: http://www.martindengler.com/proj/soas/kernel-2.6.29-16soas.fc10.i586.rpm http://www.martindengler.com/proj/soas/kernel-headers-2.6.29-16soas.fc10.i586.rpm http://www.martindengler.com/proj/soas/kernel-devel-2.6.29-16soas.fc10.i586.rpm They were built using these config and .spec files: http://www.martindengler.com/proj/soas/config-i586.2.6.29.soas http://www.martindengler.com/proj/soas/kernel.spec-2.6.29-16soas If anyone has the OLPC-specific patches lying around I would be very happy to apply them and build a new kernel. Martin Steps to prepare a F11 kernel for XOs following the instructions at: https://fedoraproject.org/wiki/Building_a_custom_kernel#Copy_the_Source_Tree_and_Generate_a_Patch 0) Find a F10 box. Install rpm build tools and directories: su -c 'yum install yum-utils rpmdevtools' rpmdev-setuptree 1) download kernel src rpm from koji: page: http://koji.fedoraproject.org/koji/buildinfo?buildID=95660 srpm: http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29/16.fc11/src/kernel-2.6.29-16.fc11.src.rpm 2) install it as non-root user: su -c 'yum-builddep kernel-2.6.29-16.fc11.src.rpm' rpm -Uvh kernel-2.6.29-16.fc11.src.rpm 3) extract pristine sources: cd ~/rpmbuild/SPECS rpmbuild -bp --target=i386 kernel.spec 4) creat pristine copy: export ver=29 export arch=i386 cp -r ~/rpmbuild/BUILD/kernel-2.6.$ver/linux-2.6.$ver.$arch ~/rpmbuild/BUILD/kernel-2.6.$ver.orig cp -al ~/rpmbuild/BUILD/kernel-2.6.$ver.orig ~/rpmbuild/BUILD/kernel-2.6.$ver.new 5) patch in compcache / ramzswap: cd ~/rpmbuild/SOURCES wget http://compcache.googlecode.com/files/ramzswap_patch_2.6.29_take4.diff cd ~/rpmbuild/BUILD/kernel-2.6.$ver.new patch -p1 < ../../SOURCES/ramzswap_patch_2.6.29_take4.diff cd ~/rpmbuild/BUILD diff -uNrp kernel-2.6.$ver.orig kernel-2.6.$ver.new > ../SOURCES/linux-2.6-ramzswap_patch_2.6.29_take4 6) patch in the sugarlabs logo: cd ~/rpmbuild/SOURCES wget http://www.martindengler.com/proj/soas/linux-2.6-soas-sugarlabs-logo.patch This patch was prepared by: cd ~/rpmbuild/BUILD/kernel-2.6.$ver.new/drivers/video/logo rm logo_linux_clut224.ppm wget http://www.martindengler.com/proj/soas/Logo_black_02-indexed-ascii.ppm logo_linux_clut224.ppm cd ~/rpmbuild/BUILD diff -uNrp kernel-2.6.$ver.orig kernel-2.6.$ver.new > ../SOURCES/linux-2.6-soas-sugarlabs-logo.patch ...and the Logo_black_02-indexed-ascii.ppm is just http://wiki.sugarlabs.org/go/Image:Logo_black_02.svg opened in the GIMP and saved as indexed (223 colours) ASCII. 7) configure the kernel cd ~/rpmbuild/BUILD/kernel-2.6.$ver/linux-2.6.$ver.$arch/ wget http://www.martindengler.com/proj/soas/config-i586.2.6.29.soas cp config-i586.2.6.29.soas .config setarch $arch make silentoldconfig 8) add the buildarch-comment that rpmbuild expects (note we don't use $arch) echo "# i586" > .config.rpm cat .config >> .config.rpm mv .config.rpm .config 9) copy the config to SOURCES (note we don't use $arch): cp .config ~/rpmbuild/SOURCES/config-i586 10) update the build files: cd ~/rpmbuild/SPECS sed -e 's/#% define buildid .local/%define buildid soas/' < kernel.spec > kernel.spec.soas && mv kernel.spec.soas kernel.spec # add the two sets of lines for Patch9900/Patch9901 and ApplyPatch: $ diff -uw kernel.spec~ kernel.spec --- kernel.spec~ 2009-04-05 12:51:29.000000000 +0100 +++ kernel.spec 2009-04-05 12:55:07.000000000 +0100 @@ -697,6 +697,12 @@ # fix locking in ipsec (#489764) Patch9101: linux-2.6-net-xfrm-fix-spin-unlock.patch +# add ramzswap +Patch9900: linux-2.6-ramzswap_patch_2.6.29_take4 + +# add SoaS splash for non-pretty-boot prettiness +Patch9901: linux-2.6-soas-sugarlabs-logo.patch + %endif BuildRoot: %{_tmppath}/kernel-%{KVERREL}-root @@ -1249,6 +1255,9 @@ ApplyPatch linux-2.6-net-fix-gro-bug.patch ApplyPatch linux-2.6-net-xfrm-fix-spin-unlock.patch +ApplyPatch linux-2.6-ramzswap_patch_2.6.29_take4 +ApplyPatch linux-2.6-soas-sugarlabs-logo.patch + # END OF PATCH APPLICATIONS %endif 11) you'll need to hack out the conflation of i386, i586, and i686 because it breaks the make oldconfig part of the redhat kernel spec file. Do this by adding: %ifarch i586 %define all_arch_configs kernel-%{version}-i586*.config %endif ...to kernel.spec at around line 282, right after the "%ifarch %{all_x86}" section ends. You need to do this if you get an error like this when you build the kernel (the next step): + mv kernel-2.6.29-i686-PAE.config .config ++ head -1 .config ++ cut -b 3- + Arch=i386 + make ARCH=i386 nonint_oldconfig CONFIG_BLK_DEV_RAMZSWAP make[1]: *** [nonint_oldconfig] Error 1 make: *** [nonint_oldconfig] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.hHU6u8 (%prep) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.hHU6u8 (%prep) 12) build the kernel (note this is not $arch) setarch $arch rpmbuild -bb --with baseonly --without debuginfo --target=i586 kernel.spec -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mikus at bga.com Sun Apr 5 13:55:15 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Sun, 05 Apr 2009 09:55:15 -0400 Subject: Announcing Fedora 11 Beta for XO Message-ID: <49D8B843.5020000@bga.com> > Is there stuff that is known to be 'broken' on the XO? Let's not forget broken sound, also broken moving pictures. mikus From ivazqueznet at gmail.com Sun Apr 5 14:59:53 2009 From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams) Date: Sun, 05 Apr 2009 10:59:53 -0400 Subject: Pippy In-Reply-To: <49D8B142.4090509@fedoraproject.org> References: <49D8B142.4090509@fedoraproject.org> Message-ID: <1238943593.3841.43.camel@ignacio.lan> On Sun, 2009-04-05 at 15:25 +0200, Fabian Affolter wrote: > Hi all, > > At the moment I'm trying to update the RPM package of Pippy to 31. But > now I have some rpmlint errors. Two of them are: > > sugar-pippy.i386: E: arch-dependent-file-in-usr-share > /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux64/_Box2D2.so > sugar-pippy.i386: E: arch-dependent-file-in-usr-share > /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux32/_Box2D2.so > > Any inputs for the proceeding? O_o Are these SOs in the tarball itself, or do they get built at runtime? -- Ignacio Vazquez-Abrams PLEASE don't CC me; I'm already subscribed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From pbrobinson at gmail.com Sun Apr 5 15:06:49 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Sun, 5 Apr 2009 16:06:49 +0100 Subject: Pippy In-Reply-To: <49D8B142.4090509@fedoraproject.org> References: <49D8B142.4090509@fedoraproject.org> Message-ID: <5256d0b0904050806s6fa74a0du4497a4dbc67a62a3@mail.gmail.com> > Hi all, > > At the moment I'm trying to update the RPM package of Pippy to 31. But > now I have some rpmlint errors. ?Two of them are: > > sugar-pippy.i386: E: arch-dependent-file-in-usr-share > /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux64/_Box2D2.so > sugar-pippy.i386: E: arch-dependent-file-in-usr-share > /usr/share/sugar/activities/Pippy.activity/library/pippy/physics/box2d/box2d_linux32/_Box2D2.so > > Any inputs for the proceeding? Its presumable being built as a noarch rpm. a .so is a shared library which means it is architecture dependent. If the shared libs are required by the package you have no choice but to remove the "BuildArch: noarch" entry and make it arch dependant. Peter From sebastian at when.com Sun Apr 5 22:37:42 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Mon, 06 Apr 2009 00:37:42 +0200 Subject: [SoaS] Deadlines for upcoming FOSSVT Release Message-ID: <49D932B6.4080109@when.com> Hi all, as you'll have noticed, we're currently readying Sugar on a Stick for release, which is scheduled for April 10th. The roadmap is located here: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap So here's a quick heads-up for activity packagers and maintainers! I know, it's quite of short notice... * SoaS will be frozen as of April 7th. The final image will be already composed on that date, as it takes some time to get everything together for FOSSVT. * Sugar 0.84.2 is the version scheduled for inclusion. * If you want to get your latest bits included, please get them ready as soon as possible! We really need to get this done within the next two days, as we can spend only tomorrow on testing. If your package belongs to sucrose, you might need to get it build in koji, as well. Please ping or e-mail me, if you've any concerns. Again, this is urgent! Thanks and let's make this an awesome release, --Your SoaS Team From scott at swdouglass.com Mon Apr 6 00:36:33 2009 From: scott at swdouglass.com (Scott Douglass) Date: Sun, 5 Apr 2009 20:36:33 -0400 Subject: F11 kernel for XO-1 In-Reply-To: <20090405135336.GU30746@ops-13.xades.com> References: <20090405135336.GU30746@ops-13.xades.com> Message-ID: Great! You might want to play with the patches I've created for adding in olpc-pm, dcon and other stuff to the kernel source RPM. git://dev.laptop.org/git/users/scott/fedora-kernel/patch/2.6.29 I have not put in compcache or the OLPC logo, that was on my list. How about we merge our work together somewhere? I'm traveling in China until April 28, so I will not be able to work on this. I'm glad to see your progress! ShanghaiScott On Apr 5, 2009, at 9:53 AM, Martin Dengler wrote: > Hi, > > I've rebuilt a patched F11 kernel for my XO-1 in order to: > > 1) get it booting without an initrd and with compcache/ramzswap patch > > 2) get the olpc-specific patches merged into an F11-based kernel (for > my personal use and testing, others' use/testing, and any help it > could provide in upstreaming the OLPC-specific patches) > > 3) convince myself it could be done by mere mortal - note an issue I > ran into in step #10 of the process I document below > > The benefits of this kernel are: > > 1) it boots on the XO-1 without an initrd (I've compiled in jffs2) > > 2) it does not use an extra ~22MB of memory like the current F11/SoaS > kernels > > 3) compcache/ramzswap is compiled in > > This kernel is for XOs. It, like past OLPC kernels, lacks some of the > more general (esoteric?) modules that get built by default. > > The packages are available here: > > http://www.martindengler.com/proj/soas/kernel-2.6.29-16soas.fc10.i586.rpm > http://www.martindengler.com/proj/soas/kernel-headers-2.6.29-16soas.fc10.i586.rpm > http://www.martindengler.com/proj/soas/kernel-devel-2.6.29-16soas.fc10.i586.rpm > > They were built using these config and .spec files: > > http://www.martindengler.com/proj/soas/config-i586.2.6.29.soas > http://www.martindengler.com/proj/soas/kernel.spec-2.6.29-16soas > > If anyone has the OLPC-specific patches lying around I would be very > happy to apply them and build a new kernel. > > Martin > > > > Steps to prepare a F11 kernel for XOs following the instructions at: > https://fedoraproject.org/wiki/ > Building_a_custom_kernel#Copy_the_Source_Tree_and_Generate_a_Patch > > 0) Find a F10 box. Install rpm build tools and directories: > su -c 'yum install yum-utils rpmdevtools' > rpmdev-setuptree > > > 1) download kernel src rpm from koji: > page: http://koji.fedoraproject.org/koji/buildinfo?buildID=95660 > srpm: http://kojipkgs.fedoraproject.org/packages/kernel/2.6.29/16.fc11/src/kernel-2.6.29-16.fc11.src.rpm > > > 2) install it as non-root user: > su -c 'yum-builddep kernel-2.6.29-16.fc11.src.rpm' > rpm -Uvh kernel-2.6.29-16.fc11.src.rpm > > > 3) extract pristine sources: > cd ~/rpmbuild/SPECS > rpmbuild -bp --target=i386 kernel.spec > > > 4) creat pristine copy: > export ver=29 > export arch=i386 > cp -r ~/rpmbuild/BUILD/kernel-2.6.$ver/linux-2.6.$ver.$arch ~/ > rpmbuild/BUILD/kernel-2.6.$ver.orig > cp -al ~/rpmbuild/BUILD/kernel-2.6.$ver.orig ~/rpmbuild/BUILD/ > kernel-2.6.$ver.new > > > 5) patch in compcache / ramzswap: > > cd ~/rpmbuild/SOURCES > wget http://compcache.googlecode.com/files/ramzswap_patch_2.6.29_take4.diff > cd ~/rpmbuild/BUILD/kernel-2.6.$ver.new > patch -p1 < ../../SOURCES/ramzswap_patch_2.6.29_take4.diff > cd ~/rpmbuild/BUILD > diff -uNrp kernel-2.6.$ver.orig kernel-2.6.$ver.new > ../SOURCES/ > linux-2.6-ramzswap_patch_2.6.29_take4 > > > 6) patch in the sugarlabs logo: > cd ~/rpmbuild/SOURCES > wget http://www.martindengler.com/proj/soas/linux-2.6-soas-sugarlabs-logo.patch > > This patch was prepared by: > cd ~/rpmbuild/BUILD/kernel-2.6.$ver.new/drivers/video/logo > rm logo_linux_clut224.ppm > wget http://www.martindengler.com/proj/soas/Logo_black_02-indexed-ascii.ppm > logo_linux_clut224.ppm > cd ~/rpmbuild/BUILD > diff -uNrp kernel-2.6.$ver.orig kernel-2.6.$ver.new > ../SOURCES/ > linux-2.6-soas-sugarlabs-logo.patch > > ...and the Logo_black_02-indexed-ascii.ppm is just http://wiki.sugarlabs.org/go/Image:Logo_black_02.svg > opened in the GIMP and saved as indexed (223 colours) ASCII. > > > 7) configure the kernel > cd ~/rpmbuild/BUILD/kernel-2.6.$ver/linux-2.6.$ver.$arch/ > wget http://www.martindengler.com/proj/soas/config-i586.2.6.29.soas > cp config-i586.2.6.29.soas .config > setarch $arch make silentoldconfig > > > 8) add the buildarch-comment that rpmbuild expects (note we don't > use $arch) > echo "# i586" > .config.rpm > cat .config >> .config.rpm > mv .config.rpm .config > > > 9) copy the config to SOURCES (note we don't use $arch): > cp .config ~/rpmbuild/SOURCES/config-i586 > > > 10) update the build files: > cd ~/rpmbuild/SPECS > sed -e 's/#% define buildid .local/%define buildid soas/' < > kernel.spec > kernel.spec.soas && mv kernel.spec.soas kernel.spec > # add the two sets of lines for Patch9900/Patch9901 and ApplyPatch: > $ diff -uw kernel.spec~ kernel.spec > --- kernel.spec~ 2009-04-05 12:51:29.000000000 +0100 > +++ kernel.spec 2009-04-05 12:55:07.000000000 +0100 > @@ -697,6 +697,12 @@ > # fix locking in ipsec (#489764) > Patch9101: linux-2.6-net-xfrm-fix-spin-unlock.patch > > +# add ramzswap > +Patch9900: linux-2.6-ramzswap_patch_2.6.29_take4 > + > +# add SoaS splash for non-pretty-boot prettiness > +Patch9901: linux-2.6-soas-sugarlabs-logo.patch > + > %endif > > BuildRoot: %{_tmppath}/kernel-%{KVERREL}-root > @@ -1249,6 +1255,9 @@ > ApplyPatch linux-2.6-net-fix-gro-bug.patch > ApplyPatch linux-2.6-net-xfrm-fix-spin-unlock.patch > > +ApplyPatch linux-2.6-ramzswap_patch_2.6.29_take4 > +ApplyPatch linux-2.6-soas-sugarlabs-logo.patch > + > # END OF PATCH APPLICATIONS > > %endif > > > 11) you'll need to hack out the conflation of i386, i586, and i686 > because it breaks the make oldconfig part of the redhat kernel spec > file. Do this by adding: > > %ifarch i586 > %define all_arch_configs kernel-%{version}-i586*.config > %endif > > ...to kernel.spec at around line 282, right after the "%ifarch % > {all_x86}" section ends. You need to do this if you get an error > like this when you build the kernel (the next step): > > + mv kernel-2.6.29-i686-PAE.config .config > ++ head -1 .config > ++ cut -b 3- > + Arch=i386 > + make ARCH=i386 nonint_oldconfig > CONFIG_BLK_DEV_RAMZSWAP > make[1]: *** [nonint_oldconfig] Error 1 > make: *** [nonint_oldconfig] Error 2 > error: Bad exit status from /var/tmp/rpm-tmp.hHU6u8 (%prep) > > > RPM build errors: > Bad exit status from /var/tmp/rpm-tmp.hHU6u8 (%prep) > > > 12) build the kernel (note this is not $arch) > setarch $arch rpmbuild -bb --with baseonly --without debuginfo -- > target=i586 kernel.spec > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list From martin at martindengler.com Mon Apr 6 10:54:08 2009 From: martin at martindengler.com (Martin Dengler) Date: Mon, 6 Apr 2009 11:54:08 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090405124307.GT30746@ops-13.xades.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> <20090405124307.GT30746@ops-13.xades.com> Message-ID: <20090406105408.GB26864@ops-13.xades.com> On Sun, Apr 05, 2009 at 01:43:07PM +0100, Martin Dengler wrote: > - network frame icon still blank (I think for the same reason as > http://dev.sugarlabs.org/ticket/307 ) > > - some WPA (1) networks unable to be associated with (not sure why, > could be #307 again) I just rebuilt a Soas2-based image and these two issues are solved. Awesome. > > cheers, > > m > > Martin Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pbrobinson at gmail.com Mon Apr 6 10:57:14 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Mon, 6 Apr 2009 11:57:14 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090406105408.GB26864@ops-13.xades.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> <20090405124307.GT30746@ops-13.xades.com> <20090406105408.GB26864@ops-13.xades.com> Message-ID: <5256d0b0904060357u4c91084k8ee45a62ebf9213c@mail.gmail.com> On Mon, Apr 6, 2009 at 11:54 AM, Martin Dengler wrote: > On Sun, Apr 05, 2009 at 01:43:07PM +0100, Martin Dengler wrote: >> - network frame icon still blank (I think for the same reason as >> ? http://dev.sugarlabs.org/ticket/307 ) >> >> - some WPA (1) networks unable to be associated with (not sure why, >> ? could be #307 again) > > I just rebuilt a Soas2-based image and these two issues are solved. > Awesome. >From rawhide, or with the custom kernel that was mentioned? Peter From simon at schampijer.de Mon Apr 6 10:57:30 2009 From: simon at schampijer.de (Simon Schampijer) Date: Mon, 06 Apr 2009 12:57:30 +0200 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <20090406105408.GB26864@ops-13.xades.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> <20090405124307.GT30746@ops-13.xades.com> <20090406105408.GB26864@ops-13.xades.com> Message-ID: <49D9E01A.2060606@schampijer.de> Martin Dengler wrote: > On Sun, Apr 05, 2009 at 01:43:07PM +0100, Martin Dengler wrote: >> - network frame icon still blank (I think for the same reason as >> http://dev.sugarlabs.org/ticket/307 ) >> >> - some WPA (1) networks unable to be associated with (not sure why, >> could be #307 again) > > I just rebuilt a Soas2-based image and these two issues are solved. > Awesome. I fixed another WPA related thing lately #575 - could be that as well. Happy it is working now. Cheers, Simon From martin at martindengler.com Mon Apr 6 11:34:03 2009 From: martin at martindengler.com (Martin Dengler) Date: Mon, 6 Apr 2009 12:34:03 +0100 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <5256d0b0904060357u4c91084k8ee45a62ebf9213c@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> <20090405124307.GT30746@ops-13.xades.com> <20090406105408.GB26864@ops-13.xades.com> <5256d0b0904060357u4c91084k8ee45a62ebf9213c@mail.gmail.com> Message-ID: <20090406113403.GC26864@ops-13.xades.com> On Mon, Apr 06, 2009 at 11:57:14AM +0100, Peter Robinson wrote: > On Mon, Apr 6, 2009 at 11:54 AM, Martin Dengler > wrote: > > On Sun, Apr 05, 2009 at 01:43:07PM +0100, Martin Dengler wrote: > >> - network frame icon still blank (I think for the same reason as > >> ? http://dev.sugarlabs.org/ticket/307 ) > >> > >> - some WPA (1) networks unable to be associated with (not sure why, > >> ? could be #307 again) > > > > I just rebuilt a Soas2-based image and these two issues are solved. > > Awesome. > > >From rawhide, or with the custom kernel that was mentioned? Rawhide. Though the custom kernel shouldn't directly affect those two problems IIUC. > Peter Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pbrobinson at gmail.com Tue Apr 7 09:39:31 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 10:39:31 +0100 Subject: move to rawhide update Message-ID: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> Hi All, I thought now that we're getting closer to the Fedora 11 freeze it would be a good time for everyone to where they're at as we move towards F-11/9.1.0/olpc-next. I've been keeping the wiki page up to date as I go along and filling in more details as I find out about them. The fixed list is slowly growing shorter. If there are updates that aren't on the list at the moment please add them, or reply with details so I can add it. https://fedoraproject.org/wiki/OLPC/Packages_for_F11 There is also a tracking page for issues with rawhide on w.l.o. It would be nice if as issues are added the appropriate track/BZ number is added to it so its easy to find out the current status of them. http://wiki.laptop.org/go/Rawhide-XO The main and probably most major issues outstanding are the kernel/boot process - so kernel/initscripts/olpcrd/initscripts/upstart/rainbow collection of stuff.... of which I have no real idea about. Updates? The remaining issues are mostly either package deps or getting them into Fedora. There's a couple of reviews of which I've had no response from the submitter. These are 2 fonts packages (and I'm not sure of the state of the other 2 'orphaned' ones but they're not listed as such in the packageDB) as sugar-record. olpcsound should disappear as soon as csound is updated to > 5.08 and I've done most of the ground work on this (RHBZ 493107) pygtk support for numpy finally landed in trunk this morning.... awaiting the date for a release and will then organise to get it into Fedora and dependant packages updated from numeric to numpy if they support it. The final few things are the likes of abiword (which will have most issues fixed for the next major release) and stuff which needs people to submit review requests. Cheers, Peter From bochecha at fedoraproject.org Tue Apr 7 09:55:47 2009 From: bochecha at fedoraproject.org (Mathieu Bridon (bochecha)) Date: Tue, 7 Apr 2009 11:55:47 +0200 Subject: move to rawhide update In-Reply-To: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> Message-ID: <2d319b780904070255v3167346enf0181262a7eeef53@mail.gmail.com> > These are 2 fonts packages (and I'm not sure of the state > of the other 2 'orphaned' ones but they're not listed as such in the > packageDB) as sugar-record. I suppose you're talking about abyssinica-fonts and nafees-web-naskh-fonts. They were orphaned and I took ownership of those 2 packages. The packages were updated to conform the new packaging guidelines by their previous maintainer (Bernie) before he orphaned them, so they are in good shape. I only didn't put them in the "fixed" list on the wiki page as I still didn't have time to look at the fontconfig rules and how to add them to the packages. I'll do that as it's the Right Thing as soon as I find the time to, but it's not necessary AFAIK so the issues with those packages (they are orphaned) are fixed. There's also a comment about renaming the abyssinica-fonts package, but Bernie couldn't help me on that and there was no bug opened asking for it (as was the case with issues with new font packaging guidelines). So, as far as OLPC on F11 goes, I'd say those 2 are "fixed". ---------- Mathieu Bridon (bochecha) From pbrobinson at gmail.com Tue Apr 7 10:02:06 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 11:02:06 +0100 Subject: move to rawhide update In-Reply-To: <2d319b780904070255v3167346enf0181262a7eeef53@mail.gmail.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <2d319b780904070255v3167346enf0181262a7eeef53@mail.gmail.com> Message-ID: <5256d0b0904070302p73514afeud053c6552399fa6a@mail.gmail.com> >> These are 2 fonts packages (and I'm not sure of the state >> of the other 2 'orphaned' ones but they're not listed as such in the >> packageDB) as sugar-record. > > I suppose you're talking about abyssinica-fonts and nafees-web-naskh-fonts. > > They were orphaned and I took ownership of those 2 packages. > > The packages were updated to conform the new packaging guidelines by > their previous maintainer (Bernie) before he orphaned them, so they > are in good shape. > > I only didn't put them in the "fixed" list on the wiki page as I still > didn't have time to look at the fontconfig rules and how to add them > to the packages. I'll do that as it's the Right Thing as soon as I > find the time to, but it's not necessary AFAIK so the issues with > those packages (they are orphaned) are fixed. > > There's also a comment about renaming the abyssinica-fonts package, > but Bernie couldn't help me on that and there was no bug opened asking > for it (as was the case with issues with new font packaging > guidelines). > > So, as far as OLPC on F11 goes, I'd say those 2 are "fixed". Excellent! That's great news. I knew the old owners name started with B but that was it so I couldn't tell if the maintainer listed in pkgdb was him or someone else :-) You don't want to take over the review for the other two font packages by chance (I'm not sure if there's a procedure for this but can look to find out), I'm happy to do the review side of things for them. Cheers, Peter From bochecha at fedoraproject.org Tue Apr 7 10:13:29 2009 From: bochecha at fedoraproject.org (Mathieu Bridon (bochecha)) Date: Tue, 7 Apr 2009 12:13:29 +0200 Subject: move to rawhide update In-Reply-To: <5256d0b0904070302p73514afeud053c6552399fa6a@mail.gmail.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <2d319b780904070255v3167346enf0181262a7eeef53@mail.gmail.com> <5256d0b0904070302p73514afeud053c6552399fa6a@mail.gmail.com> Message-ID: <2d319b780904070313i53c906a1gea53882e58c4a26b@mail.gmail.com> > You don't want to take over the review for the other two font packages > by chance (I'm not sure if there's a procedure for this but can look > to find out), I'm happy to do the review side of things for them. No, sorry. I already have so little time for the huge amount of packages I maintain (yeah, I know, 4 is a lot ^^'), I'd rather act responsibly for those and take more only when I feel I'll be able to do so. Regards, ---------- Mathieu Bridon (bochecha) From martin at martindengler.com Tue Apr 7 14:06:39 2009 From: martin at martindengler.com (Martin Dengler) Date: Tue, 7 Apr 2009 15:06:39 +0100 Subject: F11 kernel for XO-1 In-Reply-To: References: <20090405135336.GU30746@ops-13.xades.com> Message-ID: <20090407140639.GK26864@ops-13.xades.com> On Sun, Apr 05, 2009 at 08:36:33PM -0400, Scott Douglass wrote: > Great! > > You might want to play with the patches I've created for adding in > olpc-pm, dcon and other stuff to the kernel source RPM. > > git://dev.laptop.org/git/users/scott/fedora-kernel/patch/2.6.29 Thanks for pointing those out! The olpc-drivers-video.patch applies and builds fine, however I get "olpc-dcon: no DCON found on SMBus" and "olpc-dcon: Invalid I2C bus (0 not 262155)" messages in /var/log/messages, and no /sys/class/backlight "files". The big olpc-arch-x86-kernel.patch applies OK but then I get this error when rpmbuild'ing: WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' arch/x86/kernel/built-in.o: In function `wakeup_start': /home/martin/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.i586/arch/x86/kernel/olpc-wakeup.S:30: undefined reference to `swsusp_pg_dir' make: *** [.tmp_vmlinux1] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.0aCUOt (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.0aCUOt (%build) I'm not sure if the section mismatch warning is related or not. > I have not put in compcache or the OLPC logo, that was on my list. How > about we merge our work together somewhere? Sure - I'm happy to generate patches to your git repo if you'd prefer, or any other way you/OLPC/SL would like. > ShanghaiScott Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mikus at bga.com Tue Apr 7 15:09:49 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 07 Apr 2009 11:09:49 -0400 Subject: move to rawhide update Message-ID: <49DB6CBD.6090902@bga.com> > I thought now that we're getting closer to the Fedora 11 freeze it > would be a good time for everyone to where they're at as we move > towards F-11/9.1.0/olpc-next. My biggest current question is: When on my XO I enter 'yum check-update' (using either the latest SoaS2 .iso or the latest ~cjb/rawhide-xo .img), it tells me that there are more than 220 packages at the rawhide repositories that are at a more recent version level than those provided by the system on my XO. Why don't the SoaS/~cjb distributions contain the latest rawhide packages ? > The main and probably most major issues outstanding are the > kernel/boot process - so > kernel/initscripts/olpcrd/initscripts/upstart/rainbow collection of > stuff.... of which I have no real idea about. Updates? > > The remaining issues are mostly either package deps or getting them > into Fedora. If we are talking about 9.1.0, it would be nice if 'sound' and 'moving pictures' worked in F-11 on the XO. Currently they don't. I agree that 'suspend' (or even power-off on 'shutdown') would improve the usability of F-11 on the XO. mikus From pbrobinson at gmail.com Tue Apr 7 16:17:09 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 17:17:09 +0100 Subject: move to rawhide update In-Reply-To: <49DB6CBD.6090902@bga.com> References: <49DB6CBD.6090902@bga.com> Message-ID: <5256d0b0904070917t480d5abbo6a47ddd99980c55c@mail.gmail.com> > ?My biggest current question is: ?When on my XO I enter 'yum check-update' > (using either the latest SoaS2 .iso or the latest ~cjb/rawhide-xo .img), it > tells me that there are more than 220 packages at the rawhide repositories > that are at a more recent version level than those provided by the system on > my XO. > > ?Why don't the SoaS/~cjb distributions contain the latest rawhide packages ? Because rawhide is a daily moving development target. If there's a large update (like when rawhide was blocked for the creation of F11-Beta) there could 100s of updates in a day. See the daily rawhide report on the fedora-devel list for a general overview. >> The main and probably most major issues outstanding are the >> kernel/boot process - so >> kernel/initscripts/olpcrd/initscripts/upstart/rainbow collection of >> stuff.... of which I have no real idea about. Updates? >> >> The remaining issues are mostly either package deps or getting them >> into Fedora. > > ?If we are talking about 9.1.0, it would be nice if 'sound' and 'moving > pictures' worked in F-11 on the XO. ?Currently they don't. Are there bugzilla reports for these? What do you mean by 'moving pictures', do you mean recording video or playing video? > ?I agree that 'suspend' (or even power-off on 'shutdown') would improve the > usability of F-11 on the XO. I believe this is being worked on. Peter From pbrobinson at gmail.com Tue Apr 7 16:31:36 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 17:31:36 +0100 Subject: move to rawhide update In-Reply-To: <20090407162807.GL26864@ops-13.xades.com> References: <49DB6CBD.6090902@bga.com> <5256d0b0904070917t480d5abbo6a47ddd99980c55c@mail.gmail.com> <20090407162807.GL26864@ops-13.xades.com> Message-ID: <5256d0b0904070931o30b28fd7v9a809be25ce1f2db@mail.gmail.com> >> > ?Why don't the SoaS/~cjb distributions contain the latest rawhide packages ? >> >> Because rawhide is a daily moving development target. > > Aren't you both right? ?The builds contain the latest rawhide packages > as of the image creation date, right? ?Thus if it's no longer the > instant the image was created, rawhide packages may have been updated. Yes. that is correct. The image is built from the current rawhide at the time of build. But if the image was based on rawhide from a couple of days ago (or the F-11 beta) it wouldn't be surprising that there was 210 package updates. Peter From mikus at bga.com Tue Apr 7 17:25:15 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 07 Apr 2009 13:25:15 -0400 Subject: move to rawhide update Message-ID: <49DB8C7B.7020707@bga.com> >> If we are talking about 9.1.0, it would be nice if 'sound' and >> 'moving pictures' worked in F-11 on the XO. Currently they don't. > > Are there bugzilla reports for these? I. - I haven't figured out how to do an exhaustive search on bugzilla. 'OLPC' picks up some; 'XO' picks up some; '461806' picks up some. But let me emphasize once again - bugzilla appears to be aimed at the problems of developers (and isn't optimal for users). II. - What for me is an inhibitor is the bugzilla section "tell us how to reproduce the problem". I have no desire whatsoever to try to describe how to obtain the Fluendo mp3 codec for an XO, nor how to follow its instructions for seeing if it works. I have even less desire to describe where I obtained a static-linked Mplayer, nor how I have set up my XO for playing movies. [Both the mp3 codec and the Mplayer application work fine in 8.2.1.] What good would it do for me to enter a bugzilla report? A dozen people would ask me for more information, and for more "try this and try that". I have better things to do with my time. > What do you mean by 'moving > pictures', do you mean recording video or playing video? I don't try to record video - so I have no idea if it works or not (see what I mean about being asked questions which I don't know how to answer?). The 'Record' activity does not show me a picture of what the XO camera is supposed to be seeing. The 'watch&listen' activity gives me neither 'sound' nor 'moving pictures'. [IIRC, it can close prematurely.] Mplayer runs, but gives me neither 'sound' nor anything except a blank screen. mikus From pbrobinson at gmail.com Tue Apr 7 18:41:03 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 19:41:03 +0100 Subject: move to rawhide update In-Reply-To: <49DB8C7B.7020707@bga.com> References: <49DB8C7B.7020707@bga.com> Message-ID: <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> >> Are there bugzilla reports for these? > > ?I. - I haven't figured out how to do an exhaustive search on bugzilla. > ?'OLPC' picks up some; 'XO' picks up some; '461806' picks up some. ?But let > me emphasize once again - bugzilla appears to be aimed at the problems of > developers (and isn't optimal for users). You don't need to do an exhaustive search on bugzilla. You just need to search against the component that's causing issues. eg totem media player. Generally most components will have < 10 bugs so its easy to see if its an issue for the component. > ?II. - What for me is an inhibitor is the bugzilla section "tell us how to > reproduce the problem". ?I have no desire whatsoever to try to describe how > to obtain the Fluendo mp3 codec for an XO, nor how to follow its > instructions for seeing if it works. ?I have even less desire to describe > where I obtained a static-linked Mplayer, nor how I have set up my XO for > playing movies. ?[Both the mp3 codec and the Mplayer application work fine > in 8.2.1.] ?What good would it do for me to enter a bugzilla report? ?A > dozen people would ask me for more information, and for more "try this and > try that". ?I have better things to do with my time. Well, firstly if they're statically compiled applications that aren't shipped in Fedora there's no point filing bugs in Fedora about them as they aren't supported. But if your going to have an attitude of its a waste of your time, I won't waste my time trying to get them to work for you. >> What do you mean by 'moving >> pictures', do you mean recording video or playing video? > > I don't try to record video - so I have no idea if it works or not (see what > I mean about being asked questions which I don't know how to answer?). ?The > 'Record' activity does not show me a picture of what the XO camera is > supposed to be seeing. ?The 'watch&listen' activity gives me neither 'sound' > nor 'moving pictures'. ?[IIRC, it can close prematurely.] ?Mplayer runs, but > gives me neither 'sound' nor anything except a blank screen. I can check the record activity but as mentioned before issues with mplayer and mp3 codecs will need to be reported to where ever you get them from. Peter From pgf at laptop.org Tue Apr 7 19:01:53 2009 From: pgf at laptop.org (pgf at laptop.org) Date: Tue, 07 Apr 2009 15:01:53 -0400 Subject: move to rawhide update In-Reply-To: <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> References: <49DB8C7B.7020707@bga.com> <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> Message-ID: <11576.1239130913@foxharp.boston.ma.us> peter wrote: > > ?II. - What for me is an inhibitor is the bugzilla section "tell us how to > > reproduce the problem". ?I have no desire whatsoever to try to describe how > > to obtain the Fluendo mp3 codec for an XO, nor how to follow its > > instructions for seeing if it works. ?I have even less desire to describe > > where I obtained a static-linked Mplayer, nor how I have set up my XO for > > playing movies. ?[Both the mp3 codec and the Mplayer application work fine > > in 8.2.1.] ?What good would it do for me to enter a bugzilla report? ?A > > dozen people would ask me for more information, and for more "try this and > > try that". ?I have better things to do with my time. > > Well, firstly if they're statically compiled applications that aren't > shipped in Fedora there's no point filing bugs in Fedora about them as > they aren't supported. but surely the APIs that they use _are_ supported, no? > But if your going to have an attitude of its a > waste of your time, I won't waste my time trying to get them to work > for you. if mikus is having these problems, children with laptops will too. i'm sorry to hear someone who has done a _lot_ of very patient bug reporting and testing (and documentation, i believe) being dismissed like this. "no point in filing bugs"? let's all pack it in and go home. send the bug reports straight to nicholas. that being said, as a developer, i understand that a bug report with missing background information is difficult to deal with. mikus -- even attaching the static mplayer binary to the bug report, with an explanation that it used to work on 8.2, and now it doesn't, would be better than nothing. > > >> What do you mean by 'moving > >> pictures', do you mean recording video or playing video? > > > > I don't try to record video - so I have no idea if it works or not (see what > > I mean about being asked questions which I don't know how to answer?). ?The > > 'Record' activity does not show me a picture of what the XO camera is > > supposed to be seeing. ?The 'watch&listen' activity gives me neither 'sound' > > nor 'moving pictures'. ?[IIRC, it can close prematurely.] ?Mplayer runs, but > > gives me neither 'sound' nor anything except a blank screen. > > I can check the record activity but as mentioned before issues with > mplayer and mp3 codecs will need to be reported to where ever you get > them from. as mikus said, his applications all worked before. this is a regression, plain an simple, *with respect to the previous XO releases*. now, to the extent that fedora doesn't really care about any specific piece of hardware, especially one which wasn't running fedora when these things last worked, then i suppose it's appropriate to ignore the issues. i think this, and the fact that no one is sure what's broken in the current fedora-on-XO releases, points to huge holes in the OLPC plan of record for ongoing support of this product. unless some energetic entity is willing to own the actual XO distribution(s), and be responsible for maintaining a bug list, and issuing even minimal release notes, i fear for the project. (or, rather, i fear that the project will be running 8.2 until the laptops die. which wouldn't be the worst possible outcome, i suppose... :-/ ) paul =--------------------- paul fox, pgf at laptop.org From gdk at redhat.com Tue Apr 7 19:26:14 2009 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Tue, 7 Apr 2009 15:26:14 -0400 (EDT) Subject: move to rawhide update In-Reply-To: <11576.1239130913@foxharp.boston.ma.us> References: <49DB8C7B.7020707@bga.com> <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> <11576.1239130913@foxharp.boston.ma.us> Message-ID: On Tue, 7 Apr 2009, pgf at laptop.org wrote: > as mikus said, his applications all worked before. this is a > regression, plain an simple, *with respect to the previous XO releases*. > now, to the extent that fedora doesn't really care about any specific > piece of hardware, especially one which wasn't running fedora when these > things last worked, then i suppose it's appropriate to ignore the > issues. > > i think this, and the fact that no one is sure what's broken in the > current fedora-on-XO releases, points to huge holes in the OLPC plan of > record for ongoing support of this product. unless some energetic > entity is willing to own the actual XO distribution(s), and be > responsible for maintaining a bug list, and issuing even minimal release > notes, i fear for the project. (or, rather, i fear that the project will > be running 8.2 until the laptops die. which wouldn't be the worst > possible outcome, i suppose... :-/ ) This is what happens when the 95% of the developers working on the project get canned. The unenviable choice becomes: * Get a community to work from an 8.2 branch that will become more and more outdated over time; or * Get a community to work from a moving target that has a greater chance of supporting new features once they're integrated, but is inherently less stable for large chunks of the development cycle. Whichever way you go, strong leadership, patience, and many hands are required to fight through the problems. If the community cares enough and develops the necessary leadership, the project moves forward. But it's never easy. It is my hope that people continue to use the tracking bug here, and align bugs to it, and use it to assess fitness of the current release: https://bugzilla.redhat.com/showdependencytree.cgi?id=461806&hide_resolved=1 It may not be the perfect tool, but it's the best we have. --g -- Got an XO that you're not using? Loan it to a needy developer! [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] From pbrobinson at gmail.com Tue Apr 7 19:43:57 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 20:43:57 +0100 Subject: move to rawhide update In-Reply-To: <11576.1239130913@foxharp.boston.ma.us> References: <49DB8C7B.7020707@bga.com> <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> <11576.1239130913@foxharp.boston.ma.us> Message-ID: <5256d0b0904071243t29a6f438pe79a8a9a82b0003a@mail.gmail.com> > ?> > ?II. - What for me is an inhibitor is the bugzilla section "tell us how to > ?> > reproduce the problem". ?I have no desire whatsoever to try to describe how > ?> > to obtain the Fluendo mp3 codec for an XO, nor how to follow its > ?> > instructions for seeing if it works. ?I have even less desire to describe > ?> > where I obtained a static-linked Mplayer, nor how I have set up my XO for > ?> > playing movies. ?[Both the mp3 codec and the Mplayer application work fine > ?> > in 8.2.1.] ?What good would it do for me to enter a bugzilla report? ?A > ?> > dozen people would ask me for more information, and for more "try this and > ?> > try that". ?I have better things to do with my time. > ?> > ?> Well, firstly if they're statically compiled applications that aren't > ?> shipped in Fedora there's no point filing bugs in Fedora about them as > ?> they aren't supported. > > but surely the APIs that they use _are_ supported, no? Yes. > ?> But if your going to have an attitude of its a > ?> waste of your time, I won't waste my time trying to get them to work > ?> for you. > > if mikus is having these problems, children with laptops will > too. ?i'm sorry to hear someone who has done a _lot_ of very > patient bug reporting and testing (and documentation, i believe) > being dismissed like this. I'm not dismissing him. I'm quite prepared to help him if he'll provide the information. I'm someone who has done a _lot_ of very patient bug testing and trying to get all the OLPC changes to Fedora upstream so that we have the best release possible. As for children having these problems, most children will use the built in video player (totem, not sure of the sugar application), and then from there there will be local support teams and it will then move upstream (I believe). I doubt they will be reporting the bugs direct to the olpc-devel mailing lists. > "no point in filing bugs"? ?let's all pack it in and go home. > send the bug reports straight to nicholas. By no point filing bugs I meant that 80% of fedora package maintainers will close the bug straight up because its not a package in Fedora and will ask a bug to be filed with the upstream. Those that don't close the bug will expect details and ask questions which mikus clearly stated he couldn't be bothered providing. There's not a lot that can be done unless he at least states what application it is. He original stated "'sound' and 'moving pictures'", how am I or anyone else suppose to work out what that means without asking for details such as the application, what version/build it is and if its not in Fedora where he got it from. Even Microsoft don't support 3rd party applications. That's why Fedora refuses to ship binary drivers for graphics chips and binary applications, it causes alot of problems..... go and search the ubuntu forums or google about video driver problems. > that being said, as a developer, i understand that a bug report > with missing background information is difficult to deal with. > mikus -- even attaching the static mplayer binary to the bug > report, with an explanation that it used to work on 8.2, and now > it doesn't, would be better than nothing. its not difficult, its impossible. > ?> >> What do you mean by 'moving > ?> >> pictures', do you mean recording video or playing video? > ?> > > ?> > I don't try to record video - so I have no idea if it works or not (see what > ?> > I mean about being asked questions which I don't know how to answer?). ?The > ?> > 'Record' activity does not show me a picture of what the XO camera is > ?> > supposed to be seeing. ?The 'watch&listen' activity gives me neither 'sound' > ?> > nor 'moving pictures'. ?[IIRC, it can close prematurely.] ?Mplayer runs, but > ?> > gives me neither 'sound' nor anything except a blank screen. > ?> > ?> I can check the record activity but as mentioned before issues with > ?> mplayer and mp3 codecs will need ?to be reported to where ever you get > ?> them from. > > as mikus said, his applications all worked before. ?this is a > regression, plain an simple, *with respect to the previous XO releases*. > now, to the extent that fedora doesn't really care about any > specific piece of hardware, especially one which wasn't running > fedora when these things last worked, then i suppose it's > appropriate to ignore the issues. Yes, it may well be a regression but if he's using rpms or binary tarballs compiled against older versions of Fedora that could be the issue. It could be as simple as directing him to a repository that contains the best version of mplayer to use on F11 but he's provided nothing. I'm trying to help but I'm not god, I'm one person and if the person that wants help isn't prepared to do some legwork why should I. I do this in my free time and I due to the lack of people on the project I could spend every spare second of waking time on it and still not have every done. > i think this, and the fact that no one is sure what's broken in > the current fedora-on-XO releases, points to huge holes in the > OLPC plan of record for ongoing support of this product. ?unless > some energetic entity is willing to own the actual XO > distribution(s), and be responsible for maintaining a bug list, > and issuing even minimal release notes, i fear for the project. > (or, rather, i fear that the project will be running 8.2 until > the laptops die. ?which wouldn't be the worst possible outcome, i > suppose... ?:-/ ) I'm trying to be an energetic entity to help move forward the Fedora XO distro, but I am just one person. We need to aim to support the core distro because of the lack of people to work on it. If in the process I can help with codecs and applications that aren't part of the core OLPC distro I will when I can, but if someone has the attitude of 'sound' and 'moving pictures' are broken fix them and not prepared to report any more than that I don't have the time to do any more. Peter From pgf at laptop.org Tue Apr 7 20:30:31 2009 From: pgf at laptop.org (pgf at laptop.org) Date: Tue, 07 Apr 2009 16:30:31 -0400 Subject: move to rawhide update In-Reply-To: References: <49DB8C7B.7020707@bga.com> <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> <11576.1239130913@foxharp.boston.ma.us> Message-ID: <15631.1239136231@foxharp.boston.ma.us> peter, and greg -- greg wrote: > Whichever way you go, strong leadership, patience, and many hands are > required to fight through the problems. If the community cares enough and > develops the necessary leadership, the project moves forward. But it's > never easy. > > It is my hope that people continue to use the tracking bug here, and > align bugs to it, and use it to assess fitness of the current release: > > https://bugzilla.redhat.com/showdependencytree.cgi?id=461806&hide_resolved=1 of course. but the whole thing feels a lot like telling someone that their local dealership has closed, and they should write to the car's manufacturer for information about oil changes. the scale of the solution doesn't match the needs of the problem. (the analogy is shaky, i agree.) but as an example -- if bugs filed against the XO will be summarily closed by the developers because "it's not our problem, file it upstream", the larger OLPC community will be ill-served. users of the XO are not typical open-source enthusiasts, and they're not the audience that current linux distributions are used to targeting. the XO isn't a general purpose laptop, and was never intended to be. it's better considered a "device", with special needs, and as such i think it will be under-served by the new generic release and support scheme. while i agree that the current plan is probably the best we can come up with, i remain frustrated. thanks. and sorry for the non-technical venting... believe me, the real target of my rant is not the folks like you two who are continuing the mission. paul =--------------------- paul fox, pgf at laptop.org From gdk at redhat.com Tue Apr 7 21:08:13 2009 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Tue, 7 Apr 2009 17:08:13 -0400 (EDT) Subject: move to rawhide update In-Reply-To: <15631.1239136231@foxharp.boston.ma.us> References: <49DB8C7B.7020707@bga.com> <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> <11576.1239130913@foxharp.boston.ma.us> <15631.1239136231@foxharp.boston.ma.us> Message-ID: On Tue, 7 Apr 2009, pgf at laptop.org wrote: > peter, and greg -- > > greg wrote: > > Whichever way you go, strong leadership, patience, and many hands are > > required to fight through the problems. If the community cares enough and > > develops the necessary leadership, the project moves forward. But it's > > never easy. > > > > It is my hope that people continue to use the tracking bug here, and > > align bugs to it, and use it to assess fitness of the current release: > > > > https://bugzilla.redhat.com/showdependencytree.cgi?id=461806&hide_resolved=1 > > of course. but the whole thing feels a lot like telling someone that > their local dealership has closed, and they should write to the car's > manufacturer for information about oil changes. the scale of the > solution doesn't match the needs of the problem. (the analogy is shaky, > i agree.) > > but as an example -- if bugs filed against the XO will be summarily > closed by the developers because "it's not our problem, file it > upstream", the larger OLPC community will be ill-served. s/larger OLPC community/larger open source community/ Because, of course, this is not a problem experienced only by OLPC. This painful problem is central to every distro provider. The answer is a comprehensive ecosystem-wide mechanism for distributed defect tracking, and we are years away from that solution, I suspect. > users of the XO are not typical open-source enthusiasts, and they're not > the audience that current linux distributions are used to targeting. > the XO isn't a general purpose laptop, and was never intended to be. > it's better considered a "device", with special needs, and as such i > think it will be under-served by the new generic release and support > scheme. while i agree that the current plan is probably the best we can > come up with, i remain frustrated. Yeah, me too. The hope continues to be that we can stabilize and maintain the base, and then focus on the deltas that set the device apart. But it's a hard problem, made harder by a lack of resources. > thanks. and sorry for the non-technical venting... believe me, > the real target of my rant is not the folks like you two who are > continuing the mission. I know, dude. It's okay. If you have any suggestions, believe me, I'm happy to hear them. :) --g -- Got an XO that you're not using? Loan it to a needy developer! [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] From gnu at toad.com Tue Apr 7 21:20:49 2009 From: gnu at toad.com (John Gilmore) Date: Tue, 07 Apr 2009 14:20:49 -0700 Subject: move to rawhide update In-Reply-To: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> Message-ID: <200904072120.n37LKn3S028702@new.toad.com> > The main and probably most major issues outstanding are the > kernel/boot process - so > kernel/initscripts/olpcrd/initscripts/upstart/rainbow collection of > stuff.... of which I have no real idea about. Updates? It's pretty trivial to disable Rainbow, whereas it's not trivial to get maintainers of half a dozen packages to adopt patches that let them deal with Rainbow. So if you want F11 to work on OLPC, disabling Rainbow's UID fiddling in the version of Sugar that ships in F11 is the obvious short-term cure. Some of the initscript changes related to the bizarre idea of running the "anti-theft" process as pid 1 so it couldn't be killed by root. This required changing "init" so it didn't run as pid 1. This is trivial to fix by running the anti-theft process (which is a no-op loop on most OLPCs anyway, and should in a sane world merely exit) on some other pid, and running init where it belongs. It looks like perhaps the kernel changes have slipped right through the F11 schedule. Is it seriously likely that the F11 kernel maintainers would adopt a pile of OLPC patches that aren't in the upstream kernel, between the Beta and the Final F11 releases? Had these changes been adopted (by Fedora or by the Linux kernel) early in the release cycle, they could've been well tested to make sure they don't introduce any problems into non-OLPC hardware. But now, it appears that F11 won't be able to suspend on OLPC, which makes it almost useless for laptop use (as opposed to developer use when the laptop is sitting on a desk with permanent AC power). Such is the price of firing all of your kernel developers. Even the bug report that tracks the kernel power management changes has fallen into disarray (the Fedora "Bug Zapper" zapped it in November and nobody has bothered to fix it since): https://bugzilla.redhat.com/show_bug.cgi?id=465284 John From pgf at laptop.org Tue Apr 7 21:32:15 2009 From: pgf at laptop.org (pgf at laptop.org) Date: Tue, 07 Apr 2009 17:32:15 -0400 Subject: move to rawhide update In-Reply-To: <200904072120.n37LKn3S028702@new.toad.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> Message-ID: <20579.1239139935@foxharp.boston.ma.us> john wrote: > It looks like perhaps the kernel changes have slipped right through > the F11 schedule. Is it seriously likely that the F11 kernel for the record, this was a conscious decision. everyone knew there wouldn't be time to get XO-specific changes upstream, and back to fedora, before F11. as you say, it was the cost of going broke. the challenge is now to get those changes upstream in time for F12. > maintainers would adopt a pile of OLPC patches that aren't in the > upstream kernel, between the Beta and the Final F11 releases? Had > these changes been adopted (by Fedora or by the Linux kernel) early in > the release cycle, they could've been well tested to make sure they > don't introduce any problems into non-OLPC hardware. But now, it > appears that F11 won't be able to suspend on OLPC, which makes it > almost useless for laptop use (as opposed to developer use when the > laptop is sitting on a desk with permanent AC power). Such is the i think the plan is to make an OLPC-patched kernel available for the distribution creators. paul > price of firing all of your kernel developers. > > Even the bug report that tracks the kernel power management changes > has fallen into disarray (the Fedora "Bug Zapper" zapped it in November > and nobody has bothered to fix it since): > > https://bugzilla.redhat.com/show_bug.cgi?id=465284 > > John > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list =--------------------- paul fox, pgf at laptop.org From cjb at laptop.org Tue Apr 7 21:32:54 2009 From: cjb at laptop.org (Chris Ball) Date: Tue, 07 Apr 2009 17:32:54 -0400 Subject: move to rawhide update In-Reply-To: <200904072120.n37LKn3S028702@new.toad.com> (John Gilmore's message of "Tue, 07 Apr 2009 14:20:49 -0700") References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> Message-ID: Hi John, > It's pretty trivial to disable Rainbow, whereas it's not trivial to > get maintainers of half a dozen packages to adopt patches that let > them deal with Rainbow. Yes, we aren't using rainbow in the F11 builds. > Some of the initscript changes related to the bizarre idea of > running the "anti-theft" process as pid 1 so it couldn't be killed > by root. Or this. > But now, it appears that F11 won't be able to suspend on OLPC, > which makes it almost useless for laptop use (as opposed to > developer use when the laptop is sitting on a desk with permanent > AC power). Sure, but you can install a different kernel on your F11 image, such as OLPC's custom kernel (this has already been tested working), or just the minimum set of patches to the F11 kernel that add suspend/resume support, as Scott Douglass and Martin Dengler have been looking at recently. I hope we can get some power management patches (even if they're basic patches rather than everything we have) upstream and back for F12. We started the F11 project with the knowledge that we wouldn't be able to get much of what we need upstream and back in time for its release. Thanks, - Chris. -- Chris Ball From kevin at sonney.com Tue Apr 7 21:35:40 2009 From: kevin at sonney.com (Kevin Sonney) Date: Tue, 7 Apr 2009 17:35:40 -0400 Subject: move to rawhide update In-Reply-To: <200904072120.n37LKn3S028702@new.toad.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> Message-ID: Given everything discussed so far, is it worth considering an F11-OLPC branch, with the intent of merging with F12? -- Kevin Sonney -- kevin at sonney.com ?Around here, however, we don?t look backwards for very long. We keep moving forward, opening up new doors and doing new things? and curiosity keeps leading us down new paths.? ?Walt Disney I check email a couple times daily; to reach me sooner, click here: http://awayfind.com/ksonney From pbrobinson at gmail.com Tue Apr 7 21:42:44 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 22:42:44 +0100 Subject: move to rawhide update In-Reply-To: <15631.1239136231@foxharp.boston.ma.us> References: <49DB8C7B.7020707@bga.com> <5256d0b0904071141s579da4f4g2867756379f26ac@mail.gmail.com> <11576.1239130913@foxharp.boston.ma.us> <15631.1239136231@foxharp.boston.ma.us> Message-ID: <5256d0b0904071442u43d04365i45903b9a80a47449@mail.gmail.com> Paul, > ?> Whichever way you go, strong leadership, patience, and many hands are > ?> required to fight through the problems. ?If the community cares enough and > ?> develops the necessary leadership, the project moves forward. ?But it's > ?> never easy. > ?> > ?> It is my hope that people continue to use the tracking bug here, and > ?> align bugs to it, and use it to assess fitness of the current release: > ?> > ?> https://bugzilla.redhat.com/showdependencytree.cgi?id=461806&hide_resolved=1 > > of course. ?but the whole thing feels a lot like telling someone > that their local dealership has closed, and they should write to > the car's manufacturer for information about oil changes. ?the > scale of the solution doesn't match the needs of the problem. > (the analogy is shaky, i agree.) I agree with you here to a degree, but also by getting the Fedora community involved you also get 1000s of extra bug testers, coders, and community which I think in time will have much more of a positive effect than negative. Unfortunately in the short term while everything gets moved upstream and settles out there will be some pain. > but as an example -- if bugs filed against the XO will be > summarily closed by the developers because "it's not our problem, > file it upstream", the larger OLPC community will be ill-served. They won't be summarily closed if they are related to Fedora, but if its the other application that is broken its very standard. I had Microsoft do exactly the same at work the other day when it was proven that it was a vendors AV causing the problem. Of course this will also depend on the package maintainer and how responsive the reporter is. For things like 3rd party stuff it might be worthwhile using/recommending some of the recognised fedora repos for mp3 stuff etc. I'm not sure how that would need to be handled from a legal perspective. > users of the XO are not typical open-source enthusiasts, and > they're not the audience that current linux distributions are > used to targeting. ?the XO isn't a general purpose laptop, and > was never intended to be. ?it's better considered a "device", > with special needs, and as such i think it will be under-served > by the new generic release and support scheme. ?while i agree > that the current plan is probably the best we can come up with, i > remain frustrated. Also most XO users will probably unlikely to go and get software that's not distributed through a supported stream such as a school server or fedora repos. While the current situation isn't ideal but it was my understanding that alot of the support was being moved to country based teams which would then liaise with upstream OLPC/sugarlabs/fedora so it might well work ok as that gets implemented. > thanks. ?and sorry for the non-technical venting... ?believe me, > the real target of my rant is not the folks like you two who are > continuing the mission. Its not an issue. We're all hear for the same reason and probably all frustrated for various reason. I came in at the very end of the 8.2.0 dev cycle. With the changes I've some how got a lot more involved than I originally planned.... I started getting involved with small Fedora devices because I wanted to help with a spin for Netbooks.... that's sort of been replaced with this :-) Peter From pbrobinson at gmail.com Tue Apr 7 21:45:01 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Tue, 7 Apr 2009 22:45:01 +0100 Subject: move to rawhide update In-Reply-To: References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> Message-ID: <5256d0b0904071445w1c2e28e1wa76428e6957485b0@mail.gmail.com> Hi Chris, > ? > It's pretty trivial to disable Rainbow, whereas it's not trivial to > ? > get maintainers of half a dozen packages to adopt patches that let > ? > them deal with Rainbow. > > Yes, we aren't using rainbow in the F11 builds. > > ? > Some of the initscript changes related to the bizarre idea of > ? > running the "anti-theft" process as pid 1 so it couldn't be killed > ? > by root. > > Or this. > > ? > But now, it appears that F11 won't be able to suspend on OLPC, > ? > which makes it almost useless for laptop use (as opposed to > ? > developer use when the laptop is sitting on a desk with permanent > ? > AC power). > > Sure, but you can install a different kernel on your F11 image, such as > OLPC's custom kernel (this has already been tested working), or just > the minimum set of patches to the F11 kernel that add suspend/resume > support, as Scott Douglass and Martin Dengler have been looking at > recently. > > I hope we can get some power management patches (even if they're basic > patches rather than everything we have) upstream and back for F12. ?We > started the F11 project with the knowledge that we wouldn't be able to > get much of what we need upstream and back in time for its release. So is that trying to get them into 2.6.30? Peter From cjb at laptop.org Tue Apr 7 21:52:42 2009 From: cjb at laptop.org (Chris Ball) Date: Tue, 07 Apr 2009 17:52:42 -0400 Subject: move to rawhide update In-Reply-To: <5256d0b0904071445w1c2e28e1wa76428e6957485b0@mail.gmail.com> (Peter Robinson's message of "Tue, 7 Apr 2009 22:45:01 +0100") References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> <5256d0b0904071445w1c2e28e1wa76428e6957485b0@mail.gmail.com> Message-ID: Hi, > So is that trying to get them into 2.6.30? Yes, that would be ideal. - Chris. -- Chris Ball From mikus at bga.com Wed Apr 8 00:30:47 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Tue, 07 Apr 2009 20:30:47 -0400 Subject: move to rawhide update Message-ID: <49DBF037.6010808@bga.com> > You don't need to do an exhaustive search on bugzilla. You just need > to search against the component that's causing issues. eg totem media > player. Generally most components will have < 10 bugs so its easy to > see if its an issue for the component. In another post you yourself said "I'm trying to help but I'm not god". 'components' are one of my biggest problems -- I feel I would have to have a god's knowledge to figure them out. [This was my principal problem with filing tickets on dev.laptop.org -- I had not the slightest idea of what was within the scope of each 'component'.] [I'm not a kid -- but assume that I were. Suppose in my XO I click on a video in Journal (and actually it would be quite difficult for me to describe how it came to be there). I would expect to see on the XO's screen something that I would call "moving pictures" (as opposed to something that I would call "static pictures"). If I don't see "moving pictures" when I expect to see them, how am I supposed to know which 'component' should be pointed at. I was using an XO -- I guess the 'component' should be an 'XO'.] By the way, the year-ago XO software did not have anything called "totem" installed. Instead it provided a "helper" Activity called 'Watch&Listen', which was some kind of port of what you call Totem. How am I supposed to divine that on fedora-xo this same "helper" capability needs to be referred to by the name 'Totem'? And regarding bugzilla search - when yum did not work for me with ~cjb's image, I wrote a problem report. Just now I tried to find that problem report (using bugzilla search) - and none of the bugs it listed for me were what I wrote. PLEASE tell me how to search against 'yum' (I presume it's a 'component') using bugzilla search (as if the bug # had been forgotten)! > But if your going to have an attitude of its a waste of your time, > I won't waste my time trying to get them to work for you. While it would be nice for you to get something to work for me -- that is not the reason why I "publicize" problems. I figure that if something does not work for me, it will also not work for other people. And my personal concept of a "bug response" is that by spending the time of a few people (let's call them developers), a much larger group of other people (let's call them users) will be saved the time and aggravation of running into "no go" situations. If I were being paid to write test cases (conforming to fedora bugzilla conventions), I would put the effort in (to get something to work for me). But if I volunteer "here's something I can't use", I would expect (perhaps wrongly) for those responsible for preparing the product to ask themselves "is this something which could affect a lot of the users of the product?" And if the conclusion were "yes", then let me suggest that it would be more constructive to assess the problem, instead of a reflexive "Are there bugzilla reports for these?" directed to whoever mentions the difficulty. You talk about my attitude. It was formed eons ago by incidents like the following: I submitted an APAR (with all required fields filled in) about a _software_ error in a package written by IBM (I called that package correctly according to its documentation, but the information it returned was incorrect). IBM rejected the APAR with the notation "this problem was reported on an EISA system - we don't have any EISA systems on which to reproduce the problem". I doubt very much that a software routine would change its output depending on whether the system it was running on used ISA or EISA - yet this _hardware_ detail was used by IBM as a reason to refuse to act on that bug report. [Let me illustrate my feeling of "wasting my time" with bug #487101. I installed the rawhide-xo image. I use yum to download additional packages, but, given the communications configuration I use, yum on that XO would not work. Since yum is fedora-supplied, I wrote that bug report. I got questions on this bug report, and spent (too many) hours finding the answers - but despite me providing what asked-for information I could, the bug report went nowhere. Finally, by trawling through bugzilla, I found where someone else (not using an XO) had discovered a bypass. Now I am doing an edit of the appropriate configuration file every time I install F-11.] [Only yesterday did an F-11 XO image become available with a new version of Browse. (The previous version did not work for me.) I have not yet had time to compare 'yum' with https vs. Browse with https, to see if the problem is with 'yum' or with "https support" in the XO. (And no, I would have no idea of what 'component' "https support" would fall under.)] > ... if the person that want helps > isn't prepared to do some legwork why should I. I'll say it again : I'm not the person that wants help. I'm drawing attention to some problems because I am of the opinion that there will be other persons who will encounter these problems. > I'm quite prepared to help him if he'll provide the information. > There's not a lot that can > be done unless he at least states what application it is. I'm sorry - but I do NOT know how to provide the "information" (particularly 'steps to reproduce'). Why do I have to explain what I mean by "moving pictures" - surely "movie", "movie theatre", etc., are not unknown concepts (they grew out of "moving pictures"). If someone else had tried (in any way whatsoever) to watch a movie on F-11 XO, and that succeeded, I would consider it a refutation of what I posted. But to 'reproduce' inability to "watch a movie" -- I simply do not function/think that way. And I do NOT have an "application" that does not work. I see a "function" that does not work. [By that I mean, *every* way that I have tried to get the "function" to work has not produced the expected audio-visual results.] I looked around at what were the most self-contained ways to get output in the form of 'sound' and 'moving pictures' - and settled on Fluendo and Mplayer. You say that they are unacceptable, since they were not supplied by Fedora. Well, damn it, let someone less volatile than me supply "acceptable" information. But I predict that if F-11 XO gets out of development in the shape it was last week, that will give more ammunition to those dissing the XO. > I'm someone who has done a _lot_ of very > patient bug testing and trying to get all the OLPC changes to Fedora > upstream so that we have the best release possible. This is now guesswork on my part (and I could be completely wrong), but I suspect the problem does not lie with pushing upstream the existing 'OLPC changes'. "Moving pictures" worked up through Joyride-2602. Then some sort of a change was made to some sort of an X11 module (I would be surprised if there were 'OLPC changes' in X11), and "moving pictures" stopped working. Likewise, "sound" appears to be a matter of changing the 'OLPC changes' to work with pulse audio (which I think is new with F-11). mikus From gnu at toad.com Wed Apr 8 07:31:41 2009 From: gnu at toad.com (John Gilmore) Date: Wed, 08 Apr 2009 00:31:41 -0700 Subject: move to rawhide update In-Reply-To: References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> Message-ID: <200904080731.n387Vf3S016946@new.toad.com> > > But now, it appears that F11 won't be able to suspend on OLPC, > > which makes it almost useless for laptop use (as opposed to > > developer use when the laptop is sitting on a desk with permanent > > AC power). > > Sure, but you can install a different kernel on your F11 image, such as > OLPC's custom kernel (this has already been tested working), or just > the minimum set of patches to the F11 kernel that add suspend/resume > support, as Scott Douglass and Martin Dengler have been looking at > recently. > > I hope we can get some power management patches (even if they're basic > patches rather than everything we have) upstream and back for F12. We > started the F11 project with the knowledge that we wouldn't be able to > get much of what we need upstream and back in time for its release. Since OLPC's "upstream" is both Linus's kernel releases, and Fedora's distributions, there are two upstream places to push OLPC's hardware support patches to. Have we only been trying to get them into one of those places (Linus's)? The F11 kernel currently carries about 60 patches beyond Linus's version. Some are tiny 4kb patches; others are 300KB. Why aren't any of the XO-1 hardware support patches included in the F11 kernel? John From michael at laptop.org Wed Apr 8 07:58:06 2009 From: michael at laptop.org (Michael Stone) Date: Wed, 8 Apr 2009 03:58:06 -0400 Subject: Rainbow, olpc-update, and olpcrd. In-Reply-To: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> Message-ID: <20090408075806.GA9565@heat> > The main and probably most major issues outstanding are the > kernel/boot process - so > kernel/initscripts/olpcrd/initscripts/upstart/rainbow collection > of stuff.... of which I have no real idea about. Updates? Peter, Your remark does not contain any specific questions so it's a little hard for me to give you a coherent update. Instead, I'll make some general remarks in the hope that they will elicit further questions. 1. As has been recently pointed out, Rainbow is not currently in use on any Sugar platform later than sugar-*-0.84 (i.e. OLPC's 8.2.*). However, some have wondered whether it might make a reappearance in sugar-*-0.86. To speed this outcome, I have prepared new versions of rainbow (0.8.*) which are easy to install and test on many different platforms. See http://wiki.laptop.org/go/Rainbow for current status information. (I await further rainbow-0.8.* questions, comments, concerns, and test results with particular interest.) 2. There is little change in the state of olpcrd and olpc-update. Daniel Drake did some nice work in February to make the toolchain support OFW-hosted key overlays and, so far as I know, is happily serving Paraguay-signed leases and software updates over Paraguay's test schools' wifi network. (Dan -- could you please update http://wiki.laptop.org/go/Security with links to a description of how you've deployed these technologies?) (Peter -- Did you have some specific question about the technology or about its inclusion [or lack thereof] in Fedora?) Regards from Athens, Michael From gnu at toad.com Wed Apr 8 08:08:33 2009 From: gnu at toad.com (John Gilmore) Date: Wed, 08 Apr 2009 01:08:33 -0700 Subject: move to rawhide update (Fedora QA breakage) In-Reply-To: <49DB8C7B.7020707@bga.com> References: <49DB8C7B.7020707@bga.com> Message-ID: <200904080808.n3888X3S020169@new.toad.com> > II. - What for me is an inhibitor is the bugzilla section "tell us > how to reproduce the problem". I have no desire whatsoever to try Mikus unfortunately plays a troll on the Internet. He probably isn't one in real life, but the way he uses the XO is extremely unusual, so he views the XO in ways that appear to be 77 degrees away from the usual viewpoint. His bug reports require careful interpretation if you want to avoid immediately discarding them as worthless. > What good would it do for > me to enter a bugzilla report? A dozen people would ask me for more > information, and for more "try this and try that". I have better > things to do with my time. I'm sad to report that I tried to participate in a Fedora QA "test day" last week for some particular hardware I have (low end Radeon graphics). I filed one clear bug report, and four days later got the usual "please send us lots of irrelevant info" form letter. I filed a testy reply telling them they don't need it and please stop pretending to close out bug reports by demanding that the user send some irrelevant info. See: https://bugzilla.redhat.com/show_bug.cgi?id=493748 One of these irrelevant busybodies self-identifies as one of the Fedora "BugZappers" with this link: https://fedoraproject.org/wiki/BugZappers "We are a group of volunteers and Red Hat employees whose primary mission is to review and triage bug report submissions on bugzilla.redhat.com, acting as a bridge between users and developers to aid in fixing and closing bugs." Now I see what's going on. Clueless people are crashing around in the bug database, "helping" developers by hassling users. Then if you don't answer the idiots, 30 days later they close out your bug report as "CLOSED:INSUFFICIENT_DATA". Instead of a bridge, they seem to be more of a barrier, though perhaps they do good work somewhere. I think these are the same people who also trashed the "OLPC suspend/resume is broken" bug report, by running a script that declared it an obsolete problem that only applied to F10, even though the problem persists long after F10. But as the BugZapper credo says, "No programming knowledge is necessary, and triagers don't necessarily need to understand the bugs they are working on." So I'll have to agree with Mikus's analysis of why not to bother filing Red Hat bugzilla bugs. Idiots will hassle you, and claim that the bug doesn't exist after all, then close it. (*) John (*): At Cygnus, we wrote a bug tracking system, PRMS. We made very sure that nobody except the original submitter could close out a bug report. The only thing developers or QA people could do was put the bug into "feedback" state, asking the original submitter to confirm that the bug really is fixed. I insisted on this process flow because of the numerous companies I'd reported bugs to, who regularly closed out my bugs without fixing them -- over and over. I'd search the bug reports at Sun and find six people all reporting the same bug I'd encountered -- and all six of them closed inappropriately by somebody whose "job" it was to close bug reports (not to fix bugs). Cygnus's customers appreciated the attention, even though it was sometimes a hassle for us to nudge them to close out the bugs we really HAD fixed. From pbrobinson at gmail.com Wed Apr 8 09:23:41 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 8 Apr 2009 10:23:41 +0100 Subject: Rainbow, olpc-update, and olpcrd. In-Reply-To: <20090408075806.GA9565@heat> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <20090408075806.GA9565@heat> Message-ID: <5256d0b0904080223i28a8b0b6o1a863baacc7dc95a@mail.gmail.com> > Peter, > > Your remark does not contain any specific questions so it's a little > hard for me to give you a coherent update. Instead, I'll make some > general remarks in the hope that they will elicit further questions. Sorry, there were no real questions, but its more about the status of where it stands within Fedora rawhide. The current understanding is what's documented at this link. If you have more to provide that would be great (I was already aware of rainbow and the PID changes but didn't put details in as I don't know alot about early boot processes). https://fedoraproject.org/wiki/OLPC/Packages_for_F11 > 1. As has been recently pointed out, Rainbow is not currently in use > on any Sugar platform later than sugar-*-0.84 (i.e. OLPC's 8.2.*). > However, some have wondered whether it might make a reappearance in > sugar-*-0.86. To speed this outcome, I have prepared new versions of > rainbow (0.8.*) which are easy to install and test on many different > platforms. See I presume you mean later than 0.8.2? > ?http://wiki.laptop.org/go/Rainbow > > for current status information. > ?(I await further rainbow-0.8.* questions, comments, concerns, and > ?test results with particular interest.) I believe the major concerns around about the changes to init to run it as PID 1 and what changes can be made for Fedora mainline acceptance. I have no idea about the pros and cons of this hence the generic query. > 2. There is little change in the state of olpcrd and olpc-update. > Daniel Drake did some nice work in February to make the toolchain > support OFW-hosted key overlays and, so far as I know, is happily > serving Paraguay-signed leases and software updates over Paraguay's > test schools' wifi network. > ?(Dan -- could you please update > ?http://wiki.laptop.org/go/Security > > ?with links to a description of how you've deployed these > ?technologies?) > > ?(Peter -- Did you have some specific question about the technology or > ?about its inclusion [or lack thereof] in Fedora?) About its inclusion in Fedora. Peter From pbrobinson at gmail.com Wed Apr 8 09:37:52 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 8 Apr 2009 10:37:52 +0100 Subject: move to rawhide update (Fedora QA breakage) In-Reply-To: <200904080808.n3888X3S020169@new.toad.com> References: <49DB8C7B.7020707@bga.com> <200904080808.n3888X3S020169@new.toad.com> Message-ID: <5256d0b0904080237s3283d16dmd26b2af56e15bf10@mail.gmail.com> > Now I see what's going on. ?Clueless people are crashing around in the > bug database, "helping" developers by hassling users. ?Then if you > don't answer the idiots, 30 days later they close out your bug report > as "CLOSED:INSUFFICIENT_DATA". ?Instead of a bridge, they seem to be > more of a barrier, though perhaps they do good work somewhere. ?I > think these are the same people who also trashed the "OLPC > suspend/resume is broken" bug report, by running a script that > declared it an obsolete problem that only applied to F10, even though > the problem persists long after F10. ?But as the BugZapper credo says, > "No programming knowledge is necessary, and triagers don't necessarily > need to understand the bugs they are working on." I agree with you to a certain extent. I believe the reason for the "relable as F10" is primarily due to the fact that Fedora is relatively fast moving. The idiots you refer to are in the case of the "this has been reported in rawhide during the F10 development process so assigning it to F10" are in fact scripts so are complete idiots. There's a good reason to assign it from rawhide to the specific release that it was reported under, its because it moves very quickly. X is an example of this. There's been massive changes in the last 3-4 fedora releases and for example errors related to input devices reported in F-9 are completely irrelevant in F-10 because the entire X input subsystem was replaced. So to be able to see that it was reported in what became F-9 is important because its going to be completely different issue in F-10. Just because it gets moved from a rawhide designator to a F-10 one doesn't mean its closed, and if its still relevant for rawhide, you can update it. I do so regularly. As for the bugZappers..... no comment :-) Peter From katzj at redhat.com Wed Apr 8 13:04:14 2009 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 8 Apr 2009 09:04:14 -0400 Subject: move to rawhide update In-Reply-To: <200904080731.n387Vf3S016946@new.toad.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> <200904080731.n387Vf3S016946@new.toad.com> Message-ID: <20090408130413.GA6608@redhat.com> On Wednesday, April 08 2009, John Gilmore said: > > > But now, it appears that F11 won't be able to suspend on OLPC, > > > which makes it almost useless for laptop use (as opposed to > > > developer use when the laptop is sitting on a desk with permanent > > > AC power). > > > > Sure, but you can install a different kernel on your F11 image, such as > > OLPC's custom kernel (this has already been tested working), or just > > the minimum set of patches to the F11 kernel that add suspend/resume > > support, as Scott Douglass and Martin Dengler have been looking at > > recently. > > > > I hope we can get some power management patches (even if they're basic > > patches rather than everything we have) upstream and back for F12. We > > started the F11 project with the knowledge that we wouldn't be able to > > get much of what we need upstream and back in time for its release. > > Since OLPC's "upstream" is both Linus's kernel releases, and Fedora's > distributions, there are two upstream places to push OLPC's hardware > support patches to. Have we only been trying to get them into one of > those places (Linus's)? > > The F11 kernel currently carries about 60 patches beyond Linus's version. > Some are tiny 4kb patches; others are 300KB. Why aren't any of the > XO-1 hardware support patches included in the F11 kernel? As has been said here again and again, as a matter of policy, the Fedora kernel maintainers are against adding patches that aren't already in an upstream subsystem maintainer's tree and thus headed to Linus. There are a few holdouts for legacy reasons, but those are dropping in number with each passing kernel release. If it's good enough for the Fedora kernel, it's good enough for upstream. And the flip side of that is that if it's not good enough for upstream, why would you think that it's good enough for Fedora? Jeremy From dsd at laptop.org Wed Apr 8 13:10:54 2009 From: dsd at laptop.org (Daniel Drake) Date: Wed, 8 Apr 2009 09:10:54 -0400 Subject: move to rawhide update In-Reply-To: <200904080731.n387Vf3S016946@new.toad.com> References: <5256d0b0904070239v528dbce3v23601f617e637a03@mail.gmail.com> <200904072120.n37LKn3S028702@new.toad.com> <200904080731.n387Vf3S016946@new.toad.com> Message-ID: <818423da0904080610l77a2d4e6p55f8bcd595f33d12@mail.gmail.com> 2009/4/8 John Gilmore : > Since OLPC's "upstream" is both Linus's kernel releases, and Fedora's > distributions, there are two upstream places to push OLPC's hardware > support patches to. ?Have we only been trying to get them into one of > those places (Linus's)? > > The F11 kernel currently carries about 60 patches beyond Linus's version. > Some are tiny 4kb patches; others are 300KB. ?Why aren't any of the > XO-1 hardware support patches included in the F11 kernel? I don't think any effort has been made (since layoffs) to get any kernel patches upstream anywhere, mostly due to time constraints. But anyone is welcome to step up and do so! During a quick discussion with Chris and some others we seemed to agree on the following: - regardless of Fedora/F11/F12 status, policies or whatever, the first thing to do in any case is to get the patches upstream to Linus - we haven't actually tried sending our patches specifically to Fedora (knowing that they aren't quite ready for Linus) - but IMO this would be a bad idea - we don't really know Fedora's kernel policies for accepting non-upstream patches, or for backporting upstreamed patches into current Fedora kernels - my opinion: getting patches upstream to Linus, or perhaps even as far as linux-next, would be enough for the fedora kernel maintainers to include the patches in the F11 release kernel as an update. So let's not rule out suspend-on-F11.. it's possible that F11-plus-updates may work in future. The biggest showstopper right now seems to be finding someone to do the work of upstreaming the patches. And, in my opinion and experience, the correct way to do this is to approach upstream saying "hey, we have this weird hardware, how would you like to see the kernel code crafted? here's a possible patch to act as the basis of discussions" and *not* "hey, we have this weird hardware, please take our patches as-is without consideration because we've shipped them internally for 2 years" which makes the task harder (since kernel hacking may be needed as a result of discussions), but should lead to success :) Daniel From martin.langhoff at gmail.com Mon Apr 13 10:29:19 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Mon, 13 Apr 2009 12:29:19 +0200 Subject: Debugging booting problems with F9 on SD card... Message-ID: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> On the mission of getting a XS image running on the XO, I have abused imagecreator (part of livecdtools) to create an ext3 image based on the XS ISO we distribute. Now I am trying to make the image boot on the XO, and it is not working. It fails in trying to mount (and then switchroot to) /dev/root. I suspect that it's the initrd mount process that is failing there, but I am a bit at a loss on where to focus my debugging next. OFW appears to read the initrd alright, and yet... - The whole image is i686 (while trying to convince imagecreator to set the arch to i586) so that may be a source of problems. - The resulting ext3 image is using vanilla F9 kernel 2.6.27.19-78.2.30.fc9.686 -- no olpc-specific kernels here. From what I understand, all the fixes applied to F10 initrds have also been applied to recent F9 kernels. - I've created vmlinuz / initrd symlinks to make things easier -- at least during debugging. Does anything in the kernel rpm %post set those up or update them if they're found? Or update olpc.fth? Either way, everytime a new kernel is installed I need to update *something*... - I have also set /etc/fstab to mount /dev/mmcblk0p1 as / - My olpc.fth is built thus: cat > /boot/olpc.fth << EOF \ Boot script " ro root=/dev/mmcblk0p1 rootfstype=ext3 rootdelay=5 console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22" to boot-file " sd:\boot\initrd" to ramdisk " sd:\boot\vmlinuz" to boot-device unfreeze boot EOF - Funny enough, unfreeze doesn't seem to work, and the boot fails while consistently showing a pretty screen. Hints welcome... cheers, m -- martin.langhoff at gmail.com martin at 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 From jvonau at shaw.ca Mon Apr 13 11:44:44 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Mon, 13 Apr 2009 06:44:44 -0500 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> Message-ID: <1239623084.4125.4.camel@f9.vonau.ca> I can download the image, or at least the initrd.img, from where? Jerry On Mon, 2009-04-13 at 12:29 +0200, Martin Langhoff wrote: > On the mission of getting a XS image running on the XO, I have abused > imagecreator (part of livecdtools) to create an ext3 image based on > the XS ISO we distribute. > > Now I am trying to make the image boot on the XO, and it is not > working. It fails in trying to mount (and then switchroot to) > /dev/root. I suspect that it's the initrd mount process that is > failing there, but I am a bit at a loss on where to focus my debugging > next. OFW appears to read the initrd alright, and yet... > > - The whole image is i686 (while trying to convince imagecreator to > set the arch to i586) so that may be a source of problems. > > - The resulting ext3 image is using vanilla F9 kernel > 2.6.27.19-78.2.30.fc9.686 -- no olpc-specific kernels here. From what > I understand, all the fixes applied to F10 initrds have also been > applied to recent F9 kernels. > > - I've created vmlinuz / initrd symlinks to make things easier -- at > least during debugging. Does anything in the kernel rpm %post set > those up or update them if they're found? Or update olpc.fth? Either > way, everytime a new kernel is installed I need to update > *something*... > > - I have also set /etc/fstab to mount /dev/mmcblk0p1 as / > > - My olpc.fth is built thus: > cat > /boot/olpc.fth << EOF > \ Boot script > " ro root=/dev/mmcblk0p1 rootfstype=ext3 rootdelay=5 > console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22" to boot-file > " sd:\boot\initrd" to ramdisk > " sd:\boot\vmlinuz" to boot-device > unfreeze > boot > > EOF > > - Funny enough, unfreeze doesn't seem to work, and the boot fails > while consistently showing a pretty screen. > > Hints welcome... > > cheers, > > > > m From martin.langhoff at gmail.com Mon Apr 13 11:53:46 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Mon, 13 Apr 2009 13:53:46 +0200 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <1239623084.4125.4.camel@f9.vonau.ca> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <1239623084.4125.4.camel@f9.vonau.ca> Message-ID: <46a038f90904130453w666b5ec0s6836d57a74e36c6a@mail.gmail.com> On Mon, Apr 13, 2009 at 1:44 PM, Jerry Vonau wrote: > I can download the image, or at least the initrd.img, from where? scp'ing to http://dev.laptop.org/~martin these 2 images (around 409MB size): 2438d2a520dd8b245f8f5e25e730e158853df34d ks-200904110217.img.gz 6165f36d5885eabbec65accb3aa49458a67a8e63 ks-200904132252.img.gz but the connection is slow, you might get better mileage by grabbing the latest updates to the xs-livecd repository, and issuing: sudo ./util/mkext3img OLPC-School-Server-0.5.2-i386.iso imgcreator/anaconda-f9.ks Which will give you an ext3 img file. The second image has i586 kernel (and 386 glibc and openssl). Both need some manual steps... - edit /etc/fstab - symlink vmlinuz, initrd cheers, martin -- martin.langhoff at gmail.com martin at 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 From abo at stacken.kth.se Mon Apr 13 12:44:47 2009 From: abo at stacken.kth.se (=?ISO-8859-1?Q?Alexander_Bostr=F6m?=) Date: Mon, 13 Apr 2009 14:44:47 +0200 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> Message-ID: <49E333BF.4010600@stacken.kth.se> Maybe something is missing from the initrd. The process of creating it is a bit of a mystery to me, but making sure /dev/root is set up right before generating the initrd seems to work. Try this: Boot the XO into the regular Sugar system. Insert SD card, open a root shell. mount -o remount,dev /media/something cd /media/something Create a proper /dev/root: stat /dev/mmcblk0p1 - stat outputs major/minor in hex mknod b dev/root X Y - mknod wants decimal stat /dev/mmcblk0p1 dev/root - make sure they're the same mount --bind /sys sys mount --bind /proc proc mount --bind /dev/pts dev/pts chroot . new-kernel-pkg --package kernel --mkinitrd --depmod \ --install 2.6.27.19-78.2.30.fc9.686 exit sync And yes, it would be great if new-kernel-pkg could be made to update olpc.fth. /abo From jvonau at shaw.ca Mon Apr 13 13:26:53 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Mon, 13 Apr 2009 08:26:53 -0500 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <49E333BF.4010600@stacken.kth.se> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <49E333BF.4010600@stacken.kth.se> Message-ID: <1239629214.4125.49.camel@f9.vonau.ca> On Mon, 2009-04-13 at 14:44 +0200, Alexander Bostr?m wrote: > Maybe something is missing from the initrd. The process of creating it > is a bit of a mystery to me, but making sure /dev/root is set up right > before generating the initrd seems to work. Try this: > The initrd is missing the modules mmc_block and sdhci... I'm going to try to create /etc/sysconfig/mkinitrd with the missing modules listed and re-creating the initrd in the %post of the kickstart file. Jerry From jvonau at shaw.ca Mon Apr 13 15:01:07 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Mon, 13 Apr 2009 10:01:07 -0500 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <1239629214.4125.49.camel@f9.vonau.ca> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <49E333BF.4010600@stacken.kth.se> <1239629214.4125.49.camel@f9.vonau.ca> Message-ID: <1239634868.4125.57.camel@f9.vonau.ca> On Mon, 2009-04-13 at 08:26 -0500, Jerry Vonau wrote: > On Mon, 2009-04-13 at 14:44 +0200, Alexander Bostr?m wrote: > > Maybe something is missing from the initrd. The process of creating it > > is a bit of a mystery to me, but making sure /dev/root is set up right > > before generating the initrd seems to work. Try this: > > > The initrd is missing the modules mmc_block and sdhci... > I'm going to try to create /etc/sysconfig/mkinitrd with the missing > modules listed and re-creating the initrd in the %post of the kickstart > file. > > Jerry So far I have added to %post: cat > /etc/sysconfig/mkinitrd << EOF MODULES="sdhci mmc_block" EOF cat > /etc/fstab.xs << EOF /dev/mmcblk0p1 / ext3 defaults,noatime 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 EOF /sbin/mkinitrd --fstab=/etc/fstab.xs /boot/initrd.img `ls /lib/modules` dd'ing the image to CF.. now for testing.. Jerry From martin.langhoff at gmail.com Mon Apr 13 17:16:58 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Mon, 13 Apr 2009 19:16:58 +0200 Subject: Unfreeze is not enough In-Reply-To: <49E36B12.8040908@firmworks.com> References: <49E36B12.8040908@firmworks.com> Message-ID: <46a038f90904131016l1332087eh88b25598b7e94fc6@mail.gmail.com> On Mon, Apr 13, 2009 at 6:40 PM, Mitch Bradley wrote: > You have to say "dcon-unfreeze unfreeze". > > "dcon-unfreeze" thaws the screen now. > > "unfreeze" prevents the next boot command from re-freezing the screen. Cool, so I need both -- the XS has no pretty boot to speak of, so thaw the dcon and make sure it stays that way... thanks! m -- martin.langhoff at gmail.com martin at 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 From skierpage at gmail.com Tue Apr 14 00:13:25 2009 From: skierpage at gmail.com (S Page) Date: Mon, 13 Apr 2009 17:13:25 -0700 Subject: problems (Re: Announcing Fedora 11 Beta for XO) Message-ID: <6509bebe0904131713t76e710at9432ec4416354a2b@mail.gmail.com> > Here's a build of the F11 beta release for XO: Here's my experience on an XO-1 with q2e33 firmware, booting it from an 8GB SD card made withLiveUSB Creator from the 20090403.iso file. I don't repeat all the issues mentioned at http://wiki.laptop.org/go/Rawhide-XO such as pressing checkmark to boot. Fairly late in the boot I get a Gnome-like alert on a black screen: "There is a problem with the configuration server (/libexec/gconf-sanity-check-2 exited with status 256)" ( commented "weird, probably a new rawhide bug") After choosing Sugar and login, I get the same alert again, then I'm dumped back to the login screen. I have no .sugar directory in /home/liveuser, so no logs. I didn't see a keyboard chooser on the login screen in this build, I wonder if that's related. Also the login prompt invited me to choose a language but there was no language chooser. I clicked the yellow triangle on the login screen for boot errors, there was one: Starting Avahi daemon... [FAILED] I logged in again, choosing Gnome startup. That gave me the same error, but I wasn't kicked back to the login screen like Sugar. On the Greek temple desktop, I got two alerts: * about battery trouble along the lines of "Couldn't make sense of your battery charge". * "Nautilus could not create the following required folders: /home/liveuser/Desktop, /home/liveuser/.nautilus". (They don't exist, but /home/liveuser is drwx------ owner liveuser group liveuser. Weird) After dismissing these, I just stare at the Greek temple; no icons, no menu bar, not even a mouse cursor. There are various dot files in /home/liveuser, but nothing that looks like a log. To return to the login screen, in a VT console I entered init 3, got the "Starting Avahi daemon... [FAILED]" again. Then init 5, got the same error. The display went back to booting with pretty much the same behavior with "There is a problem with the configuration server" alerts, but still no mouse cursor. I powered off and tried again. This time I noticed a brief error line, something about "problems with imem size"?, before the boot process bar appeared. Other than that the behavior was the same. Should I try the `zcat 2009403.bootable.gz > /dev/sdX` approach instead of LiveUSB Creator? Cheers, -- =S Page From skierpage at gmail.com Tue Apr 14 00:32:45 2009 From: skierpage at gmail.com (S Page) Date: Mon, 13 Apr 2009 17:32:45 -0700 Subject: Announcing Fedora 11 Beta for XO In-Reply-To: <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> Message-ID: <6509bebe0904131732u781f27fdv48d0b3521f77a8b3@mail.gmail.com> On Sat, Apr 4, 2009 at 9:39 AM, Martin Langhoff wrote: > Yeah, that's what I am thinking of doing. Is there stuff that is known > to be 'broken' on the XO? http://wiki.laptop.org/go/Rawhide-XO#Known_issues , edit away.It also links to the Sugar Labs Testing pages for SoaS images. -- =S Page From cjb at laptop.org Tue Apr 14 01:21:45 2009 From: cjb at laptop.org (Chris Ball) Date: Mon, 13 Apr 2009 21:21:45 -0400 Subject: problems (Re: Announcing Fedora 11 Beta for XO) In-Reply-To: <6509bebe0904131713t76e710at9432ec4416354a2b@mail.gmail.com> (S. Page's message of "Mon, 13 Apr 2009 17:13:25 -0700") References: <6509bebe0904131713t76e710at9432ec4416354a2b@mail.gmail.com> Message-ID: Hi, > I clicked the yellow triangle on the login screen for boot > errors, there was one: Starting Avahi daemon... [FAILED] I suspect this is all some kind of filesystem corruption associated with your write to the SD card. I don't think I've seen anything like these errors myself. > Should I try the `zcat 2009403.bootable.gz > /dev/sdX` approach > instead of LiveUSB Creator? Sure. - Chris. -- Chris Ball From martin.langhoff at gmail.com Tue Apr 14 07:26:21 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Tue, 14 Apr 2009 09:26:21 +0200 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <1239634868.4125.57.camel@f9.vonau.ca> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <49E333BF.4010600@stacken.kth.se> <1239629214.4125.49.camel@f9.vonau.ca> <1239634868.4125.57.camel@f9.vonau.ca> Message-ID: <46a038f90904140026g1d51c38byfdb227551f355ccb@mail.gmail.com> On Mon, Apr 13, 2009 at 5:01 PM, Jerry Vonau wrote: > So far I have added to %post: > > cat > /etc/sysconfig/mkinitrd << EOF > MODULES="sdhci mmc_block" > EOF I just tried a variation on that, and it didn't work. It does load sdhci and mmc_block now, but it still fails. There's something else at play... cheers, martin -- martin.langhoff at gmail.com martin at 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 From solutiongrove at gmail.com Tue Apr 14 11:14:44 2009 From: solutiongrove at gmail.com (Caroline Meeks) Date: Tue, 14 Apr 2009 07:14:44 -0400 Subject: [Sugar-devel] USB stick advice In-Reply-To: <242851610904140116m1c55256dt5e6b47d2dac6e8af@mail.gmail.com> References: <49E39848.4040502@laptop.org> <242851610904140116m1c55256dt5e6b47d2dac6e8af@mail.gmail.com> Message-ID: On Tue, Apr 14, 2009 at 4:16 AM, Tomeu Vizoso wrote: > [cc'ing fedora-olpc because we are using unmodified fedora tools] > > On Mon, Apr 13, 2009 at 23:33, Walter Bender > wrote: > > Thanks. This is all helpful. I wonder what the Fedora USB Creator does > > when it runs under Windows? > > AFAIK, what Mitch says is what we currently do when using both > livecd-iso-to-disk.sh and the Fedora Live USB creator. > > For flashing a big number of sticks with a port replicator, we could > first use livecd-iso-to-disk.sh to copy the partition files to one > stick and set the bootable flag, then use dd to read into an image and > then dd again to write it to the rest of the sticks, provided they are > actually identical inside. > I don't think they are actually identical inside. They show up as all different sizes. I used dd to make an image then zcat to write it to new sticks. zcat ./SoaS-Beta-4-9.img.Z > /dev/disk2 I got a fairly high failure rate so I'm not saying this is a good method. > > Regards, > > Tomeu > > > -walter > > > > On Mon, Apr 13, 2009 at 3:53 PM, Mitch Bradley wrote: > >> My first order recommendation is "don't use dd to blast an image over > the > >> existing partition map". > >> > >> The problem with doing so is that it wrecks the factory partition > layout. I > >> strongly suspect that said factory layout is, on many sticks, optimized > for > >> the characteristics of the stick's internal firmware and the hardware > block > >> sizes of the NAND Flash chips. > >> > >> Unfortunately, the alternative is rather more complicated procedurally > than > >> "dd and pray". But given the indifferent results from dd&pray, I think > it > >> may be worthwhile to go for a more elaborate procedure. > >> > >> Here is an outline of what I think really should be done: > >> > >> a) Ensure that your filesystem image is somewhat smaller than 1G (or 2G > or > >> whatever your base size) so it will fit on "all" 1G devices. > >> > >> b) The image is just the partition contents, excluding the partition > block > >> and master boot record. > >> > >> c) The installation procedure involves > >> > >> c1) Editing (not replacing) the existing partition map, setting the > first > >> partition's "boot flag" byte and changing its filesystem type to ext2 or > >> whatever. (Ideally it would better not to change the filesystem type, > >> instead sticking with the factory FAT partition, but I understand what a > >> hard nut that is to swallow for Linux enthusiasts.) > >> > >> c2) Copying the image into the partition > >> > >> c3) Installing your bootloader using an installation program instead of > dd, > >> thus replacing the first sector's Master Boot Record and doing whatever > else > >> is necessary to complete the bootloader's installation. I have had the > best > >> results with syslinux. > >> > >> There is, of course, a chicken-and-egg problem of how do you run the > >> bootloader's installer. On the other hand, you have the same problem > with > >> "dd" - in principle, on any machine that can run "dd", you can also run > >> syslinux. > >> > >> If you want to talk more about this issue, please feel free to keep the > >> conversation going. It is a topic that has been much on mind recently. > >> > >> Mitch > >> > >> > >> > >> Walter Bender wrote: > >>> > >>> I was wondering if you have any words of wisdom to share with us re > >>> USB stick compatibility, given your experience with the XO. There > >>> seems to be a lot of variability in terms of which sticks boot which > >>> machines in our Sugar-on-a-Stick experiments, e.g., using the same > >>> machine (a Classmate running XP) to burn the same image (the Beta SoaS > >>> iso) onto USB storage media from three different vendors, I cannot > >>> predict which one(s) will be bootable on any particular piece of > >>> hardware. Is there any deterministic way to proceed, or is trail and > >>> error our only recourse? > >>> > >>> thanks. > >>> > >>> -walter > >>> > >>> > >> > > > > > > > > -- > > Walter Bender > > Sugar Labs > > http://www.sugarlabs.org > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel at lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel at lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Caroline Meeks Solution Grove Caroline at SolutionGrove.com 617-500-3488 - Office 505-213-3268 - Fax -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.langhoff at gmail.com Tue Apr 14 12:24:44 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Tue, 14 Apr 2009 14:24:44 +0200 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904140026g1d51c38byfdb227551f355ccb@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <49E333BF.4010600@stacken.kth.se> <1239629214.4125.49.camel@f9.vonau.ca> <1239634868.4125.57.camel@f9.vonau.ca> <46a038f90904140026g1d51c38byfdb227551f355ccb@mail.gmail.com> Message-ID: <46a038f90904140524q1e9c3bbfjd97b1223dfdfc4aa@mail.gmail.com> On Tue, Apr 14, 2009 at 9:26 AM, Martin Langhoff wrote: > I just tried a variation on that, and it didn't work. It does load > sdhci and mmc_block now, but it still fails. There's something else at > play... If I replace the kernel with an OLPC kernel, at least it tries to open mmcblk0p1 -- and fails, because the drivers we need are built as modules. Have you had any success? cheers, martin -- martin.langhoff at gmail.com martin at 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 From martin.langhoff at gmail.com Tue Apr 14 18:45:25 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Tue, 14 Apr 2009 20:45:25 +0200 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904140524q1e9c3bbfjd97b1223dfdfc4aa@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <49E333BF.4010600@stacken.kth.se> <1239629214.4125.49.camel@f9.vonau.ca> <1239634868.4125.57.camel@f9.vonau.ca> <46a038f90904140026g1d51c38byfdb227551f355ccb@mail.gmail.com> <46a038f90904140524q1e9c3bbfjd97b1223dfdfc4aa@mail.gmail.com> Message-ID: <46a038f90904141145j4ebdc4b4qd4bd558f72711ec7@mail.gmail.com> On Tue, Apr 14, 2009 at 2:24 PM, Martin Langhoff wrote: > If I replace the kernel with an OLPC kernel, at least it tries to open > mmcblk0p1 -- and fails, because the drivers we need are built as > modules. > > Have you had any success? Using dsd's XO-alt-distro scripts we can get a kernel build that has all the relevant bits for the XO, and builds the MMC modules we want statically. As they are, dsd's scripts setup an initrd that fails exactly like the other ones. But as the modules we want are linked statically, we don't need the initrd. And without referring to the initrd, the image boots like a champ. So now I have an XS booting on the XO :-) -- with a hand-compiled kernel, so not quite the ideal thing yet. The fact that merely adding an initrd breaks it means there must be something wrong (read: non-XO-compatible) with how initrds are built under F9. I've reviewed the changelog of F-10s mkinitrd, but nothing jumps at me, and it's not trivial to use it on F9 as it pulls a lots of deps. Any ideas? Help? cheers, m -- martin.langhoff at gmail.com martin at 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 From jvonau at shaw.ca Tue Apr 14 22:51:47 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Tue, 14 Apr 2009 17:51:47 -0500 Subject: [Server-devel] Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904141145j4ebdc4b4qd4bd558f72711ec7@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <49E333BF.4010600@stacken.kth.se> <1239629214.4125.49.camel@f9.vonau.ca> <1239634868.4125.57.camel@f9.vonau.ca> <46a038f90904140026g1d51c38byfdb227551f355ccb@mail.gmail.com> <46a038f90904140524q1e9c3bbfjd97b1223dfdfc4aa@mail.gmail.com> <46a038f90904141145j4ebdc4b4qd4bd558f72711ec7@mail.gmail.com> Message-ID: <1239749507.3196.36.camel@f9.vonau.ca> On Tue, 2009-04-14 at 20:45 +0200, Martin Langhoff wrote: > On Tue, Apr 14, 2009 at 2:24 PM, Martin Langhoff > wrote: > > If I replace the kernel with an OLPC kernel, at least it tries to open > > mmcblk0p1 -- and fails, because the drivers we need are built as > > modules. > > > > Have you had any success? > not much really with F9.. > Using dsd's XO-alt-distro scripts we can get a kernel build that has > all the relevant bits for the XO, and builds the MMC modules we want > statically. > What version of the kernel does/can it build? I've looked at scripts, it's looking at a local source tree, can we rig it work a remote git? or maybe use a source tree based on the source rpm layout? I wouldn't have time till the weekend to look at any of that. > As they are, dsd's scripts setup an initrd that fails exactly like the > other ones. But as the modules we want are linked statically, we don't > need the initrd. And without referring to the initrd, the image boots > like a champ. > Try to move around some large files and see if the kernel crashes, see below. > So now I have an XS booting on the XO :-) -- with a hand-compiled > kernel, so not quite the ideal thing yet. > That would work if somebody maintains a kernel and source rpms (repo maybe?) for an XO kernel. No, that is not ideal. > The fact that merely adding an initrd breaks it means there must be > something wrong (read: non-XO-compatible) with how initrds are built > under F9. > The livecd based stuff doesn't seem to have this issue, more like the initrd needs a bit of a sleep while the module loads and finds the MMC card, or as a module, it sort of broken(see below). I have F11's anaconda booting, formatting and installing to the MMC card, only to have it kernel opps when installing the rpms. Thoughts anybody? Jerry From pbrobinson at gmail.com Wed Apr 15 09:08:17 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 15 Apr 2009 10:08:17 +0100 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> Message-ID: <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> Hi Martin, What would it take to move the next XS Server release to either F10 or F11 as F9 will be EOL as soon as F11 comes out in a month or so (one month after F11 is out F9 will be EOL). Peter On Mon, Apr 13, 2009 at 11:29 AM, Martin Langhoff wrote: > On the mission of getting a XS image running on the XO, I have abused > imagecreator (part of livecdtools) to create an ext3 image based on > the XS ISO we distribute. > > Now I am trying to make the image boot on the XO, and it is not > working. It fails in trying to mount (and then switchroot to) > /dev/root. I suspect that it's the initrd mount process that is > failing there, but I am a bit at a loss on where to focus my debugging > next. OFW appears to read the initrd alright, and yet... > > ?- The whole image is i686 (while trying to convince imagecreator to > set the arch to i586) so that may be a source of problems. > > ?- The resulting ext3 image is using vanilla F9 kernel > 2.6.27.19-78.2.30.fc9.686 -- no olpc-specific kernels here. From what > I understand, all the fixes applied to F10 initrds have also been > applied to recent F9 kernels. > > ?- I've created vmlinuz / initrd symlinks to make things easier -- at > least during debugging. Does anything in the kernel rpm %post set > those up or update them if they're found? Or update olpc.fth? Either > way, everytime a new kernel is installed I need to update > *something*... > > ?- I have also set /etc/fstab to mount /dev/mmcblk0p1 as / > > ?- My olpc.fth is built thus: > cat > /boot/olpc.fth << EOF > \ Boot script > " ro root=/dev/mmcblk0p1 rootfstype=ext3 rootdelay=5 > console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22" to boot-file > " sd:\boot\initrd" to ramdisk > " sd:\boot\vmlinuz" to boot-device > unfreeze > boot > > EOF > > ?- Funny enough, unfreeze doesn't seem to work, and the boot fails > while consistently showing a pretty screen. > > Hints welcome... > > cheers, > > > > m > -- > ?martin.langhoff at gmail.com > ?martin at 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 > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > From martin.langhoff at gmail.com Wed Apr 15 09:41:26 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Wed, 15 Apr 2009 11:41:26 +0200 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> Message-ID: <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> On Wed, Apr 15, 2009 at 11:08 AM, Peter Robinson wrote: > What would it take to move the next XS Server release to either F10 or > F11 as F9 will be EOL as soon as F11 comes out in a month or so (one > month after F11 is out F9 will be EOL). It's a bit of a recurring question. I am swamped with feature development for a while. My hope is to port to F11 or even F12 when I can. Help is welcome and Jerry is doing a lot of work on F10/11. But qualifiying something as an XS release is a sizable workload t is to do all the testing to ensure it is stable, installs/upgrades and works as desired. It takes quite a bit of effort and gear. And I want to limit how many Fedora releases I have to support. (My plan is to transition to a stable RHEL/Centos asap, hence my F11/F12 targets.) But that for the future. At this stage, people are needing to boot our F9 based XS-0.5.x and upcoming 0.6, and that's what I am asking for help with. Can you help me with that? :-) There's an odd issue with booting when an initrd is involved. cheers, martin -- martin.langhoff at gmail.com martin at 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 From pbrobinson at gmail.com Wed Apr 15 14:01:48 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 15 Apr 2009 15:01:48 +0100 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> Message-ID: <5256d0b0904150701v6706c4d0t94b3d3425ead3cb9@mail.gmail.com> >> What would it take to move the next XS Server release to either F10 or >> F11 as F9 will be EOL as soon as F11 comes out in a month or so (one >> month after F11 is out F9 will be EOL). > > It's a bit of a recurring question. I am swamped with feature > development for a while. My hope is to port to F11 or even F12 when I > can. Help is welcome and Jerry is doing a lot of work on F10/11. Is there a current status of list and a todo list around somewhere, I can help from a distro/packaging perspective but aren't much help from development side of things > But qualifiying something as an XS release is a sizable workload t is > to do all the testing to ensure it is stable, installs/upgrades and > works as desired. It takes quite a bit of effort and gear. And I want > to limit how many Fedora releases I have to support. (My plan is to > transition to a stable RHEL/Centos asap, hence my F11/F12 targets.) Is the process documented somewhere? > But that for the future. > > At this stage, people are needing to boot our F9 based XS-0.5.x and > upcoming 0.6, and that's what I am asking for help with. > > Can you help me with that? :-) There's an odd issue with booting when > an initrd is involved. Not massively knowledgeable from a initrd perspective. Peter From sverma at sfsu.edu Wed Apr 15 15:56:08 2009 From: sverma at sfsu.edu (Sameer Verma) Date: Wed, 15 Apr 2009 08:56:08 -0700 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> Message-ID: <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> On Wed, Apr 15, 2009 at 2:41 AM, Martin Langhoff wrote: > On Wed, Apr 15, 2009 at 11:08 AM, Peter Robinson wrote: >> What would it take to move the next XS Server release to either F10 or >> F11 as F9 will be EOL as soon as F11 comes out in a month or so (one >> month after F11 is out F9 will be EOL). > > It's a bit of a recurring question. I am swamped with feature > development for a while. My hope is to port to F11 or even F12 when I > can. Help is welcome and Jerry is doing a lot of work on F10/11. > > But qualifiying something as an XS release is a sizable workload t is > to do all the testing to ensure it is stable, installs/upgrades and > works as desired. It takes quite a bit of effort and gear. And I want > to limit how many Fedora releases I have to support. (My plan is to > transition to a stable RHEL/Centos asap, hence my F11/F12 targets.) > +1 Fedora releases are too fast a moving target. I personally use Ubuntu LTS or Debian Stable for my servers for this very reason. Sameer > But that for the future. > > At this stage, people are needing to boot our F9 based XS-0.5.x and > upcoming 0.6, and that's what I am asking for help with. > > Can you help me with that? :-) There's an odd issue with booting when > an initrd is involved. > > cheers, > > > martin > -- > ?martin.langhoff at gmail.com > ?martin at 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 at lists.laptop.org > http://lists.laptop.org/listinfo/devel From gdk at redhat.com Wed Apr 15 16:01:02 2009 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Wed, 15 Apr 2009 12:01:02 -0400 (EDT) Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> Message-ID: On Wed, 15 Apr 2009, Sameer Verma wrote: > On Wed, Apr 15, 2009 at 2:41 AM, Martin Langhoff > wrote: >> On Wed, Apr 15, 2009 at 11:08 AM, Peter Robinson wrote: >>> What would it take to move the next XS Server release to either F10 or >>> F11 as F9 will be EOL as soon as F11 comes out in a month or so (one >>> month after F11 is out F9 will be EOL). >> >> It's a bit of a recurring question. I am swamped with feature >> development for a while. My hope is to port to F11 or even F12 when I >> can. Help is welcome and Jerry is doing a lot of work on F10/11. >> >> But qualifiying something as an XS release is a sizable workload t is >> to do all the testing to ensure it is stable, installs/upgrades and >> works as desired. It takes quite a bit of effort and gear. And I want >> to limit how many Fedora releases I have to support. (My plan is to >> transition to a stable RHEL/Centos asap, hence my F11/F12 targets.) >> > > +1 > > Fedora releases are too fast a moving target. I personally use Ubuntu > LTS or Debian Stable for my servers for this very reason. Choose CentOS. The workflow for managing development atop Centos and Fedora are essentially the same. --g -- Computer Science professors should be teaching open source. Help make it happen. Visit http://teachingopensource.org. From martin.langhoff at gmail.com Wed Apr 15 16:43:00 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Wed, 15 Apr 2009 18:43:00 +0200 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> Message-ID: <46a038f90904150943k5e919d75ia992d3b081b023e8@mail.gmail.com> On Wed, Apr 15, 2009 at 6:01 PM, Greg Dekoenigsberg wrote: > Choose CentOS. ?The workflow for managing development atop Centos and Fedora > are essentially the same. That's the plan for the XS (I'm sure gregdek knows it, but it's good to broadcast the msg) :-) In the meantime, about that initrd brokenness... any takers? cheers, m -- martin.langhoff at gmail.com martin at 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 From gdk at redhat.com Wed Apr 15 16:47:22 2009 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Wed, 15 Apr 2009 12:47:22 -0400 (EDT) Subject: Debugging booting problems with F9 on SD card... In-Reply-To: <46a038f90904150943k5e919d75ia992d3b081b023e8@mail.gmail.com> References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> <46a038f90904150943k5e919d75ia992d3b081b023e8@mail.gmail.com> Message-ID: On Wed, 15 Apr 2009, Martin Langhoff wrote: > On Wed, Apr 15, 2009 at 6:01 PM, Greg Dekoenigsberg wrote: >> Choose CentOS. ?The workflow for managing development atop Centos and Fedora >> are essentially the same. > > That's the plan for the XS (I'm sure gregdek knows it, but it's good > to broadcast the msg) :-) > > In the meantime, about that initrd brokenness... any takers? Is there a bug I can herd people towards? --g -- Computer Science professors should be teaching open source. Help make it happen. Visit http://teachingopensource.org. From martin.langhoff at gmail.com Wed Apr 15 16:55:56 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Wed, 15 Apr 2009 18:55:56 +0200 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> <46a038f90904150943k5e919d75ia992d3b081b023e8@mail.gmail.com> Message-ID: <46a038f90904150955m42f6e302ua7a5057e93385f7f@mail.gmail.com> On Wed, Apr 15, 2009 at 6:47 PM, Greg Dekoenigsberg wrote: > Is there a bug I can herd people towards? Not a bug as such, as I haven't narrowed down steps to repro, but here's the start of the relevant threads: http://lists.laptop.org/pipermail/server-devel/2009-April/003209.html http://lists.laptop.org/pipermail/server-devel/2009-April/003225.html If anyone has an XO and reasonable kernel + initrd debugging chops, it's an interesting problem to tackle. It is -- unapologetically -- a F9 thing. The current XS is F9, and there's a push to make it usable on the XO hw for small pilots that are starting soon (as "yesterday"). cheers, m -- martin.langhoff at gmail.com martin at 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 From pbrobinson at gmail.com Wed Apr 15 20:57:09 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 15 Apr 2009 21:57:09 +0100 Subject: Debugging booting problems with F9 on SD card... In-Reply-To: References: <46a038f90904130329p37a974dfye1f5ac27dd5663a8@mail.gmail.com> <5256d0b0904150208n2386b23frc4c6db1a4b657c51@mail.gmail.com> <46a038f90904150241n247bd96eg2bef27e8ccaaf580@mail.gmail.com> <5fb387c70904150856m65be80c2nb2524668d1aff042@mail.gmail.com> Message-ID: <5256d0b0904151357x6efd21bdq8f693180dcd0689e@mail.gmail.com> > > Choose CentOS. ?The workflow for managing development atop Centos and Fedora > are essentially the same. I have no doubt about it, and I've read that going forward that is the plan for XS. The reason I originally asked the question about what we need to move it forward to F11 was so that we can get any of the core stuff that XS needs (if there is any that isn't there already) is there in F11 so that the move to what will ultimately be centos 6 is in place and it then makes it easier moving forward. Peter From sebastian at when.com Fri Apr 17 19:05:36 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Fri, 17 Apr 2009 21:05:36 +0200 Subject: Announcing Sugar on a Stick Beta 1 Message-ID: <49E8D300.8080806@when.com> Hi everybody, The SoaS team is happy to announce the availability of our Beta-1 Release today! There has been impressive progress over the last few weeks; many thanks all the people who contributed their time and effort. The images have been composed and are up and ready for download. A direct link to the Beta-1 image: http://download.sugarlabs.org/soas/releases/soas-beta.iso The release notes: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Beta Instructions on how to put the image onto a USB key: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick PLEASE NOTE: This is a beta release, which means that it will have bugs. But we need your help to test it. Please give it a try and report back any problems you encounter. General feedback is also most welcome. Please direct it to our IAEP list: iaep at lists.sugarlabs.org Thanks again and happy testing! From luke at faraone.cc Sat Apr 18 19:12:01 2009 From: luke at faraone.cc (Luke Faraone) Date: Sat, 18 Apr 2009 15:12:01 -0400 Subject: [sugar-devel] Mounting SoaS images In-Reply-To: <2eaf0c620904181202u22d0335fkbc72cbafa27dfa19@mail.gmail.com> References: <2eaf0c620904181202u22d0335fkbc72cbafa27dfa19@mail.gmail.com> Message-ID: <2eaf0c620904181212h443da3d0x96c3e4a4ccd3ee32@mail.gmail.com> This isn't really sugar specific, and Tomeu suggested that this might be more apropos for this list. ---------- Forwarded message ---------- From: Luke Faraone Date: Sat, Apr 18, 2009 at 3:02 PM Subject: Mounting SoaS images To: Sugar Devel Hi, I'm currently trying to develop SDM, a utility which will run on school lab computers and automaticaly detect when USB flash drives with SoaS are plugged in. The idea is that in a lab we don't want to have to fiddle with the BIOS, and want something like what the boothelper is doing but on the computers themselves. Basically, we'd have a local copy of Fedora on the lab computers and would simply use the /home directories on the SoaS sticks. In order to do that, we need to mount the filesystem created by liveUSB (which contains /home). LiveUSB used and still uses persistant LVM overlays/snapshots, and based on my current understanding it is very difficult to mount a LVM snapshot outside of the host system. The LiveUSB script has an option to create a normal home.img file, but this option is not exposed in the Windows GUI. The end result is that unless this option is used, the home dirtectory is inaccessable to SDM. Is there something we can do to fix this, or am I missing something about how LVM works? -- Luke Faraone http://luke.faraone.cc -- Luke Faraone http://luke.faraone.cc -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikus at bga.com Sat Apr 18 22:34:06 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Sat, 18 Apr 2009 18:34:06 -0400 Subject: XO becomes unresponsive Message-ID: <49EA555E.3010503@bga.com> Disclaimer: I am not asking for help - I can just reboot and continue with my work. This information is posted so that if anyone else runs into a similar situation, they might realize that they are not alone in seeing it. [I have not tried to create this situation deliberately, so I do not know how repeatable it is.] Running ~cjb/fedora-xo/20090416.img (installed via 'copy-nand'). This is a heavily customized system, using a swap partition on an SD card. [It also has an USB hub, with USB devices plugged into that.] Was running a 'find' command (in Terminal) against the principal partition of the SD card. Noticed that the XO became unresponsive. Went to the text console (ctl-alt-F2) and tried to log in. That, too, didn't go - because the XO never completed the login. In the meantime, every four or so seconds (i.e., periodically) the following group of 9 text lines was being output on the text console olpc-ec: running cmd 0x15 olpc-ec: received 0x33 olpc-ec: running cmd 0x15 olpc-ec: received 0x33 olpc-ec: running cmd 0x15 olpc-ec: received 0x33 olpc-ec: running cmd 0x10 olpc-ec: received 0x55 olpc-ec: received 0x2a The last of those lines kept changing from group to group. I saw values of 0x30,0x2e, 0x32, 0x28, 0x26, 0x34, 0x34, 0x2e, 0x32, 0x2a, 0x2c, 0x2e, ox28, etc., etc. in that last line. None of this meant anything to me - as I said, I just rebooted. Note: I typically experience unresponsiveness on F11-on-XO sooner or later (often during a 'find' [which I use heavily]). The unresponsiveness seems to come on sooner with Soas2 run from an USB stick - then I do not have a swap partition "active". mikus From martin.langhoff at gmail.com Sun Apr 19 10:55:59 2009 From: martin.langhoff at gmail.com (Martin Langhoff) Date: Sun, 19 Apr 2009 12:55:59 +0200 Subject: XO becomes unresponsive In-Reply-To: <49EA555E.3010503@bga.com> References: <49EA555E.3010503@bga.com> Message-ID: <46a038f90904190355g41872761jc10e00ba8d6b3af0@mail.gmail.com> On Sun, Apr 19, 2009 at 12:34 AM, Mikus Grinbergs wrote: > Was running a 'find' command (in Terminal) against the principal partition > of the SD card. ?Noticed that the XO became unresponsive. Went to the text > console (ctl-alt-F2) and tried to log in. ?That, too, didn't go - because > the XO never completed the login. Ouch. > In the meantime, every four or so seconds (i.e., periodically) the following > group of 9 text lines was being output on the text console > > ?olpc-ec: running cmd 0x15 I think that that's normal, and completely unrelated. > Note: ?I typically experience unresponsiveness on F11-on-XO sooner or later > (often during a 'find' [which I use heavily]). ?The unresponsiveness seems > to come on sooner with Soas2 run from an USB stick - then I do not have a > swap partition "active". Interesting. If you have the time and inclination, could you run that find (perhaps without the swap, so you hit the problem sooner), it should freeze, and ideally come back after a while (perhaps an hour or more). After it comes back, /var/log/messages may have something of value. Another thing to test is to disable the ramdisks for /var/log and ~/.sugar/default/log. I don't know where they are defined, IIRC there's a file in /etc that extends fstab. :: Aside :: anything that results in verbose logging to /var/log/* or ~/.sugar/default/log leads to memory pressure that doesn't abate. It bothers me that we have ever-growing ramdisks without any kind of gc on a notably ram-constrained platform. Was there ever a plan made for this? Perhaps it's time to execute it. cheers, m -- martin.langhoff at gmail.com martin at 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 From mikus at bga.com Sun Apr 19 19:00:52 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Sun, 19 Apr 2009 15:00:52 -0400 Subject: speak gets further Message-ID: <49EB74E4.9010007@bga.com> Disclaimer: I am not asking for help. I'm posting my experience, in case anyone noticed that the 'Speak' activity (distributed as part of honey) used to not launch on F11-on-XO. After manually upgrading to 'pygame-1.8.1-5' (plus dependencies), my (rawhide-xo .img) XO now launches 'Speak', though the "general" audio problem with F11-on-XO prevents me from hearing anything. mikus From pbrobinson at gmail.com Mon Apr 20 21:24:00 2009 From: pbrobinson at gmail.com (Peter Robinson) Date: Mon, 20 Apr 2009 22:24:00 +0100 Subject: Fwd: 2009-04-21 - Fedora Test Day - Minimal platform In-Reply-To: <1240261428.5078.362.camel@flatline.devel.redhat.com> References: <1240261428.5078.362.camel@flatline.devel.redhat.com> Message-ID: <5256d0b0904201424y3f8c9290y175a5c6588bdee6f@mail.gmail.com> Hi All, Sorry for the cross post from fedora-devel but this might be of interest to some of the olpc people. This is something I've been concentrating on for a while, as I know have others so if you can free a little bit of time for some testing that would be great. Cheers, Peter Greetings testers, Calling all package gurus and dependency junkies! ?The Fedora 11 MinimalPlatform feature [1] aims to provide a tiny installation package set by identifying unwanted deps from @Core and related groups. ?As described in the feature page, the benefits to Fedora include: ? ? ?* Security - lower the attack surface by installing only necessary ? ? ? ?packages ? ? ?* Performance - faster installation and less running services ? ? ?* Storage - installation is less than 500MB There will also be several new tools available to help navigate dependencies, including rpmreaper and rpm2comps. Come join #fedora-qa this Tuesday, April 21 2009 to help put an end to deps creep. ?Test cases and a Fedora live image will be available to aid testing. Stay tuned for more details are available at https://fedoraproject.org/wiki/Test_Day:2009-04-21_Minimal_Platform. Thanks, James [1] https://fedoraproject.org/wiki/Features/MinimalPlatform -- fedora-test-list mailing list fedora-test-list at redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From skierpage at gmail.com Sat Apr 25 01:10:44 2009 From: skierpage at gmail.com (S Page) Date: Fri, 24 Apr 2009 18:10:44 -0700 Subject: Help activity In-Reply-To: <49D8B435.6080305@fedoraproject.org> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> <49D8B435.6080305@fedoraproject.org> Message-ID: <6509bebe0904241810x5e86570ey7ea0295671f9f158@mail.gmail.com> On Sun, Apr 5, 2009 at 6:37 AM, Fabian Affolter wrote: > In the repos (the one at sugarlabs.org and dev.laptop.org) is Version 7 > of 'help' available but there is a new image (Version 10) mentioned on > the wiki page [1]. > > Where is the new source? Or is this just a mistake? > BTW, does anybody know where the source tarball of help could be found? That page http://wiki.laptop.org/go/Help_(activity) links to a newer v10 version of the .xo file that OLPC's Sj uploaded on 2008-09-26. You can install it on an XO, or unzip it. As that page indicates, the content comes from http://en.flossmanuals.net/XO and http://en.flossmanuals.net/Sugar , somehow someone turns these into a set of HTML pages and creates the Help activity (and you would hope, also updates http://www.laptop.org/8.2.0/manual ). What might be happening is people are updating the *content* on Flossmanuals and somehow making new .xo bundles, but not always updating git. Or vice-versa (thrice-versa?). It looks like http://dev.laptop.org/git/activities/help and http://git.sugarlabs.org/projects/help have changes up to v9 but not v10. To add to potential confusion, I think people have started updating the content on Flossmanuals to reflect Sugar 0.84, but there's no obvious "applies to release xx" in the pages. The people who really know might be on library at lists.laptop.org -- =S Page From dfarning at sugarlabs.org Sat Apr 25 17:03:40 2009 From: dfarning at sugarlabs.org (David Farning) Date: Sat, 25 Apr 2009 12:03:40 -0500 Subject: Help activity In-Reply-To: <6509bebe0904241810x5e86570ey7ea0295671f9f158@mail.gmail.com> References: <46a038f90904040405h65fb1e2dp91e6330faf32d7f9@mail.gmail.com> <20090404131050.GQ30746@ops-13.xades.com> <46a038f90904040939g73ec3dbbmda35c398ea871be3@mail.gmail.com> <49D8B435.6080305@fedoraproject.org> <6509bebe0904241810x5e86570ey7ea0295671f9f158@mail.gmail.com> Message-ID: Brian Jordan(CCed) has been the help maintainer. He should be able to shed more light on the situation. david On Fri, Apr 24, 2009 at 8:10 PM, S Page wrote: > On Sun, Apr 5, 2009 at 6:37 AM, Fabian Affolter wrote: > >> In the repos (the one at sugarlabs.org and dev.laptop.org) is Version 7 >> of 'help' available but there is a new image (Version 10) mentioned on >> the wiki page [1]. >> >> Where is the new source? Or is this just a mistake? >> BTW, does anybody know where the source tarball of help could be found? > > That page http://wiki.laptop.org/go/Help_(activity) links to a newer > v10 version of the .xo file that OLPC's Sj uploaded on 2008-09-26. > You can install it on an XO, or unzip it. ?As that page indicates, the > content comes from http://en.flossmanuals.net/XO and > http://en.flossmanuals.net/Sugar , somehow someone turns these into a > set of HTML pages and creates the Help activity (and you would hope, > also updates http://www.laptop.org/8.2.0/manual ). > > What might be happening is people are updating the *content* on > Flossmanuals and somehow making new .xo bundles, but not always > updating git. ?Or vice-versa (thrice-versa?). ?It looks like > http://dev.laptop.org/git/activities/help and > http://git.sugarlabs.org/projects/help have changes up to v9 but not > v10. > > To add to potential confusion, I think people have started updating > the content on Flossmanuals to reflect Sugar 0.84, but there's no > obvious "applies to release xx" in the pages. > > The people who really know might be on library at lists.laptop.org > > -- > =S Page > > _______________________________________________ > Fedora-olpc-list mailing list > Fedora-olpc-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > From mikus at bga.com Mon Apr 27 01:31:45 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Sun, 26 Apr 2009 21:31:45 -0400 Subject: fewer activities in latest rawhide-xo Message-ID: <49F50B01.8050201@bga.com> Noticed that ~cjb/rawhide-xo build 20090426.img did not define any directory /home/liveuser/Activities. It also left out the "honey" group of Activities from SugarLabs. mikus From mikus at bga.com Tue Apr 28 00:54:15 2009 From: mikus at bga.com (Mikus Grinbergs) Date: Mon, 27 Apr 2009 20:54:15 -0400 Subject: CAUTION: XO booting is sensitive to filesystem corruption Message-ID: <49F653B7.2050103@bga.com> Been running rawhide-xo lately on my XOs. Have also installed q2e41.rom . Each XO has a "permanent" SD card. I was getting intermittent occasions when an XO would not boot -- soon after the screen background (as for "ok" prompt) changed from white to black, its boot process would hang with only a mysterious output message: " mount: unknown filesystem type 'jffs2' ". [If I repeated trying to boot, the hang would normally go away.] But today after I had used 'copy-nand' to replace 20090416.img on an XO with with 20090426.img, the hang (with that strange message) kept repeating. By juggling external USB devices [my usual "fix" for XO booting problems] I finally got that XO booted - but happened to run into a problem trying to delete some files from the SD card on that XO. Googled for help - and found that 'fsck' was suggested. Ran 'fsck' against the filesystem on the SD card [it found a number of bad references involving the files I was trying to delete]. And now that XO boots without hanging !!! My guess is that the problem with the (ext2) filesystem on the SD card somehow triggered whatever led to that strange output message which mentioned 'jffs2'. mikus