problems (Re: Announcing Fedora 11 Beta for XO)
by S Page
> 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)"
(<cjb> 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
15 years, 1 month
Re: Unfreeze is not enough
by Martin Langhoff
On Mon, Apr 13, 2009 at 6:40 PM, Mitch Bradley <wmb(a)firmworks.com> 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(a)gmail.com
martin(a)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
15 years, 1 month
move to rawhide update
by Peter Robinson
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
15 years, 1 month
Re: move to rawhide update
by Mikus Grinbergs
>> 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
15 years, 1 month
Re: move to rawhide update
by Mikus Grinbergs
> 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
15 years, 1 month
Re: move to rawhide update
by Peter Robinson
>> > 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
15 years, 1 month
Re: move to rawhide update
by Mikus Grinbergs
> 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
15 years, 1 month
F11 kernel for XO-1
by Martin Dengler
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....
http://www.martindengler.com/proj/soas/kernel-devel-2.6.29-16soas.fc10.i5...
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_T...
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/kern...
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
15 years, 1 month
[SoaS] Deadlines for upcoming FOSSVT Release
by Sebastian Dziallas
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
15 years, 1 month
Pippy
by Fabian Affolter
-----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-----
15 years, 1 month
