Re: [Sugar-devel] XO-1 keyboard issues, partial setxkbmap workaround
by S Page
(including fedora-olpc-list)
I think there are three Fedora XO-1 keyboard bugs:
1. Any Rawhide should auto-detect you have an OLPC keyboard. The hal
and evdev bits and pieces are there, yet it doesn't work. I filed
<https://bugzilla.redhat.com/show_bug.cgi?id=490310>. I made n00b
notes at http://wiki.laptop.org/go/User:Skierpage/Redhat-XO_OLPC_keyboard
2. Although OLPC keymap is in Rawhide, there's dispute over the exact
contents, e.g. the Frame key and brightness vs. function keys.
Existing bugs <http://dev.sugarlabs.org/ticket/291> and
<https://bugzilla.redhat.com/show_bug.cgi?id=468744>
I'm really confused if this needs to be fixed in /usr/share/hal or in
/usr/share/X11/xkb or both.
3. OLPC keyboard variants should appear in system-config-keyboard and
the Gnome desktop manager "first boot" keyboard selector. Only the
latter has a few Afghanistan OLPC keyboard layouts, none of them has
"U.S. English (olpc)". I filed
<https://bugzilla.redhat.com/show_bug.cgi?id=490311> for
system-config-keyboard, I don't know if the "first boot" GDM keyboard
selector should be a different bug.
It ought to Just Work :-) , but they've been saying that about X
keyboard handling for about 20 years.
Regarding 3, Martin Dengler made additional progress on this one in
his message. I don't know how Fedora builds that hardcoded list of
keyboards, and I don't know where /etc/sysconfig/keyboard gets set.
Hope this helps,
--
=S Page
15 years, 1 month
first steps in collaboration
by Mikus Grinbergs
Running, on my wired ethernet, an XO with rawhide-xo 20090323. It
saw an XO with build 811, and an XO with build 2663. Was able to
set up a working Chat session among all three XOs (on ethernet).
[At this time I was not able to set up collaboration in Write.]
mikus
15 years, 1 month
JFFS2 compression type 7
by Scott Douglass
I was loading different kernels, and just switched from 2.6.27+ to
2.6.29+ (rawhide with OLPC patches).
While running my custom 2.6.29-0.256.rc8.git2 kernel, I "init 6" and
start over. Now none of the kernels I've got installed can boot the XO
from NAND. All of them (2.6.25 OLPC, 2.6.27 OLPC and mine) give
various flavors of JFFS2 compression type 7 not supported.
How the heck did I change the compression type on my NAND's JFFS2?
Since no kernels are able to boot my XO now, I'll have to reblast the
NAND. I'm just curious how this could have happened. I've been
experimenting with enabling CONFIG_* options such that I can boot my
custom kernels, and I had got a combination that worked!
I did enable multiple types of compression for JFFS2 however,
including LZO. Could the type of compression be changed on an already
created JFFS2 system, at run time by the kernel modules?
15 years, 1 month
Making an XS installable img for the XO
by Martin Langhoff
What is the state of the Fedora / Puritan / Pilgrim toolchain if I
want to build an installable img of the XS spin? Noting that...
- targetting developer-key-unlocked XOs so no signing of initrd needed
- XS is F9
- the current XS build is F9 - (a mock chroot with any Fedora can be used too)
- the kernel and initrd are _vanilla_ Fedora, and there is a strong
desire to remain so
- hoping for a simple cli build tool
cheers,
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
Adding new activities to comps.xml
by Steven M. Parrish
We have added quite a few new activiies to Fedora in the past few weeks. As
it stands now they are not installed by default when someone does a
yum groupinstall "SUGAR Desktop Environment"
So the question is do we want them to be installed by default or left to the
user to manually install. Here is what I am looking at adding.
sugar-update-control
sugar-artwork
sugar-moon
sugar-memorize
sugar-speak
sugar-distance
sugar-implode
sugar-connect
sugar-help
sugar-finance
sugar-playgo
sugar-xoirc
sugar-xomail
sugar-clock
sugar-read
sugar-stopwatch
Any comments or issues?
Steven
15 years, 1 month
Re: wired & wired
by Mikus Grinbergs
>> the only clue I had was seeing *two* 'wired' icons in the Frame.
>
> Hi Mikus,
> what do you think that should appear there instead?
In my opinion, no software changes are needed - what was there
worked as it ought to. [I don't know how to explain this, but what
might be useful is to re-educate the *user* to recognize a 'wired'
icon as representing a __connection__ instead of __connectivity__.]
----
Now, if someone has too much time on their hands (ha ha), I've
noticed that a 'disconnect' entry is present in the drop-down
palette for 'wireless' icons, but not for 'wired' icons.
But there is work (on connectivity indicators) that is much more
useful, but currently appears to be incomplete. For instance, in my
experience with rawhide-xo images, the Frame is showing a gray
circle where it should be showing a functional 'wireless' icon.
mikus
15 years, 1 month
wired & wired
by Mikus Grinbergs
ok - I figured it out - I had plugged in a second USB hub, without
realizing that that hub also had an ethernet adapter attached to it
- that makes two ethernet adapters and two interfaces. Good to know
the system can handle such a situation. But the only clue I had was
seeing *two* 'wired' icons in the Frame.
mikus
15 years, 1 month
wired & wired
by Mikus Grinbergs
I have a single USB-ethernet adapter on my (rawhide-xo 20090319.img)
XO. Have no idea how this happened, but just noticed that there
were *two* active ethernet interfaces opened for that adapter.
mikus
----
NetworkManager Tool
State: connected
- Device: msh0
-----------------------------------------------------------------
Type: 802.11 WiFi
Driver: usb
State: disconnected
Default: no
HW Address: 00:17:C4:10:A2:2E
Capabilities:
Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes
Wireless Access Points
- Device: eth0
-----------------------------------------------------------------
Type: 802.11 WiFi
Driver: usb
State: disconnected
Default: no
HW Address: 00:17:C4:10:A2:2E
Capabilities:
Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes
Wireless Access Points
olpc-mesh: Ad-Hoc, 02:29:19:37:CB:5C, Freq 2412 MHz, Rate
0 Mb/s, Strength 100
Home Wireless Network: Infra, 00:1C:DF:D9:4E:03, Freq 2412 MHz,
Rate 54 Mb/s, Strength 57 WPA
- Device: eth2 [Auto eth2]
----------------------------------------------------
Type: Wired
Driver: pegasus
State: connected
Default: yes
HW Address: 00:10:60:C7:0D:DB
Capabilities:
Carrier Detect: yes
Speed: 100 Mb/s
Wired Properties
Carrier: on
IPv4 Settings:
Address: 192.168.1.12
Prefix: 24 (255.255.255.0)
Gateway: 192.168.1.1
DNS: 192.168.1.1
- Device: eth1 [Auto eth1]
----------------------------------------------------
Type: Wired
Driver: pegasus
State: connected
Default: no
HW Address: 00:10:60:16:9D:F6
Capabilities:
Carrier Detect: yes
Speed: 100 Mb/s
Wired Properties
Carrier: on
IPv4 Settings:
Address: 192.168.1.9
Prefix: 24 (255.255.255.0)
Gateway: 192.168.1.1
DNS: 192.168.1.1
15 years, 1 month
[SoaS] A Roadmap to our first Release
by Sebastian Dziallas
Hi all.
As promised, I've got some news regarding the SoaS roadmap. Here is it:
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap#Roadmap
Let me talk about the major points for a second.
(a) We're targeting 2009-04-10 as the release date, as that's the date
when Caroline and Walter will be showing it off at FOSSVT.
(b) We'll clearly indicate that this is *beta* software. Nevertheless,
it's a *release*. The final release is scheduled for Q3 2009.
(c) Fedora 11 Beta has been delayed for 7 days, which means that it will
be generally available on 2009-03-31.
(d) We're going to use F11 beta as the base system. Why? Because it's
currently frozen and will become more unstable after the beta release,
when the freeze is lifted. So instead, we'll clone the Rawhide state
being used for the Beta Release and base SoaS-2 on that.
What does this mean for testers, as well as developers?
(1) I'd like to encourage everybody to give SoaS-2 a shot. Please report
any issues you encounter, also with regard to hardware support, *now*!
The latest snapshots have been announced here: http://tinyurl.com/cufy75
(2) We'll continue to build and release new snapshots, as Rawhide should
become more stable now.
(3) After the F11 beta release, testing should focus on providing a good
Sugar experience. So information which activities (and features) and
which don't are appreciated!
(4) Activity maintainers for honey should be aware of the fact that
their activities can only be included if they have been uploaded and
approved on activities.sugarlabs.org.
(5) Package maintainers for Fedora are asked to update their packages to
the latest version until 2009-04-05. That's also the latest date for
getting packages included! Non-working stuff might be removed as of that
date.
You can keep track of the latest package version here. Please update
this page accordingly.
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap#Packaging
If you've any general ideas or suggestions, please add them here:
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO
Thanks and let's make this a great release! :)
--Sebastian
15 years, 1 month
the new background of the login screen upsets me
by Mikus Grinbergs
What is the software location of the picture shown as background?
I'd like to replace that picture on my personal system.
Seems to me whoever chose the background that was introduced last
week did not consider that items with overtones of dissentious
subjects such as politics or religion might elicit emotional
reactions. I'm concerned that when my system prominently shows a
picture with a temple, that might be interpreted as "Mikus worships
paganism". I want the choice of whether my system presents arcane
associations to be mine - not that of an anonymous release builder.
mikus
15 years, 2 months
