Re: SD card won't power up in OFW

2008-01-19 Thread Mitch Bradley
Fixed in Q2D08

http://dev.laptop.org/ticket/5717

David Howard wrote:
> Saw a short thread with this subject in December 2007.
>
> I also got the "SDHCI: Card didn't power up after 1 second" message.
>
> The SD is a Toshiba SDHC 4GB.
>
> Q2D07 and 650/653/656 OS.  I tried last two on the SD after verifying  
> the images with Q (QEMU).
>
> Here is where it's more interesting.  I imaged the SD from my Mac  
> using an Ativa SD to USB gizmo.  If I put the SD with no changes into  
> the USB adapter it boots the OLPC fine.
>
> I've used the instructions at:
>
> http://wiki.laptop.org/go/OS_images_for_USB_disks
>
> and a slight variation of the instructions at:
>
> http://lists.laptop.org/pipermail/devel/2007-April/004751.html
>
> The variation being I skipped the RPM part since I imaged with a  
> stable build.
>
> Santa Fe Dave
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>   

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


SD card won't power up in OFW

2008-01-19 Thread David Howard
Saw a short thread with this subject in December 2007.

I also got the "SDHCI: Card didn't power up after 1 second" message.

The SD is a Toshiba SDHC 4GB.

Q2D07 and 650/653/656 OS.  I tried last two on the SD after verifying  
the images with Q (QEMU).

Here is where it's more interesting.  I imaged the SD from my Mac  
using an Ativa SD to USB gizmo.  If I put the SD with no changes into  
the USB adapter it boots the OLPC fine.

I've used the instructions at:

http://wiki.laptop.org/go/OS_images_for_USB_disks

and a slight variation of the instructions at:

http://lists.laptop.org/pipermail/devel/2007-April/004751.html

The variation being I skipped the RPM part since I imaged with a  
stable build.

Santa Fe Dave


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Why can't i access /dev/dsp or /dev/snd on my XO

2008-01-19 Thread M. Edward (Ed) Borasky
Albert Cahalan wrote:
> On Jan 19, 2008 4:33 PM, victor <[EMAIL PROTECTED]> wrote:
> 
>> I can't speak for TamTam because I am not involved in their
>> design details, but I can say this, Csound's standard score
>> preceeds MIDI by at least a decade (or two if you consider where
>> it came from). It is much more flexible to convey musical data
>> than MIDI. There are MIDI to csound score converters, but
>> that is beside the point, because Csound can play MIDI files
>> directly, receive realtime MIDI data and even output it.
>> There is no problem whatsoever, with the proper instruments,
>> Csound will be a MIDI synthesizer like any other. The main
>> thing is, that it is not limited to it (thank goodness...).
> 
> How about showing some support for standards by
> dropping the non-standard stuff? You can #ifdef it.
> Maybe you can even save a few bytes.
> 
> If you really must, you can embed the non-standard
> stuff into a MIDI file. It's better to avoid non-standard
> stuff entirely of course, and any extended MIDI file
> had better play decently on a standard MIDI player.
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
> 

One of the main reasons I got an XO was because it has CSound. It's a
ghastly API, but it's been around for years and there are thousands of
working instruments! There's a huge book on it, and I doubt very
seriously if anyone will ever come up with a digital sound analysis and
synthesis tool set as comprehensive without investing a lot of effort
re-inventing a bunch of wheels, levers, inclined planes and such.

By the way -- I've been meaning to check to see if this is in Trac, but
the csound-manual and csound-tutorial RPMs in the repository appear to
be empty. I can install them, but there isn't anything on the machine
after I do.

I'm also attempting to get some of the Planet CCRMA software loaded on
the system. At this point, all I really want is Common Music -- I don't
need another synthesizer since I have CSound, and I don't need a music
notation program. If anyone else has already done this, I'd love to hear
about it.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Why can't i access /dev/dsp or /dev/snd on my XO

2008-01-19 Thread Albert Cahalan
On Jan 19, 2008 4:33 PM, victor <[EMAIL PROTECTED]> wrote:

> I can't speak for TamTam because I am not involved in their
> design details, but I can say this, Csound's standard score
> preceeds MIDI by at least a decade (or two if you consider where
> it came from). It is much more flexible to convey musical data
> than MIDI. There are MIDI to csound score converters, but
> that is beside the point, because Csound can play MIDI files
> directly, receive realtime MIDI data and even output it.
> There is no problem whatsoever, with the proper instruments,
> Csound will be a MIDI synthesizer like any other. The main
> thing is, that it is not limited to it (thank goodness...).

How about showing some support for standards by
dropping the non-standard stuff? You can #ifdef it.
Maybe you can even save a few bytes.

If you really must, you can embed the non-standard
stuff into a MIDI file. It's better to avoid non-standard
stuff entirely of course, and any extended MIDI file
had better play decently on a standard MIDI player.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New update.1 build 682

2008-01-19 Thread david
similar effects, but what I'm seeing is after a full power cycle. I'm not 
doing a suspend


attached is the sugar logfile

David Lang

On Sat, 19 Jan 2008, Tomeu Vizoso wrote:


Date: Sat, 19 Jan 2008 20:02:02 -0500
From: Tomeu Vizoso <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: New update.1 build 682

Hi,

looks like you have found http://dev.laptop.org/ticket/4013 .

Could you check, please?

Should work in latest joyride builds.

Thanks,

Tomeu

On Sat, 2008-01-19 at 18:00 -0800, [EMAIL PROTECTED] wrote:

sorry for the delay in responding (I've been traveling for the last week)

attached is the messages file, it looks like the system is trying to
unmount the SD card immediatly after boot (<2 seconds)

I'll enable the sugar debugging and go into the journal immediatly after
boot and then see if there is anything interesting there.

I'll be upgrading to a new build as soon as the RC is released.

David Lang

On Wed, 16 Jan 2008, Tomeu Vizoso wrote:


Date: Wed, 16 Jan 2008 10:29:25 -0500
From: Tomeu Vizoso <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: New update.1 build 682

Can you give some more details?

Particularly, see
http://wiki.laptop.org/go/Attaching_Sugar_Logs_to_Tickets and
also /var/log/messages would be of interest.

Thanks,

Tomeu

On Wed, 2008-01-16 at 07:18 -0800, [EMAIL PROTECTED] wrote:

I can't get the journal to see the SD card with this build.
I can see it from the command line just fine.

David Lang

On Tue, 15 Jan 2008, Build Announcer Script wrote:


Date: Tue, 15 Jan 2008 15:00:03 -0500 (EST)
From: Build Announcer Script <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: New update.1 build 682

http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build682/

-Paint-15.xo
+Paint-17.xo
-Read-38.xo
+Read-40.xo
-Record-49.xo
+Record-50.xo
-Terminal-5.xo
+Terminal-8.xo
-Web-83.xo
+Web-84.xo
+bash.i386 0:3.2-19.fc7
-bash.i386 0:3.2-9.fc7
-gnash.i386 0:0.8.1-1.olpc2
+gnash.i386 0:0.8.1-2.olpc2.20071226cvs
-gnash-plugin.i386 0:0.8.1-1.olpc2
+gnash-plugin.i386 0:0.8.1-2.olpc2.20071226cvs
-hulahop.i386 0:0.4.0-1.olpc2
+hulahop.i386 0:0.4.0-2.olpc2
-initscripts.i386 0:8.54.1-15.olpc2
+initscripts.i386 0:8.54.1-17.olpc2
-libabiword.i386 0:2.6.0.svn20071106-1
+libabiword.i386 0:2.6.0.svn20071127-1
-libabiword-plugins.i386 0:2.6.0.svn20071106-1
+libabiword-plugins.i386 0:2.6.0.svn20071127-2
-libxml2.i386 0:2.6.29-1.fc7
+libxml2.i386 0:2.6.31-1.fc7
-libxml2-python.i386 0:2.6.29-1.fc7
+libxml2-python.i386 0:2.6.31-1.fc7
-mingetty.i386 0:1.07-5.2.2
+mingetty.i386 0:1.07-9.olpc2
-ohm.i386 0:0.1.1-6.1.20080102git.fc7
+ohm.i386 0:0.1.1-6.3.20080102git.fc7
-olpc-utils.i386 0:0.63-1.olpc2
+olpc-utils.i386 0:0.63-2.olpc2
-pyabiword.i386 0:0.6.0.svn20071106-1
+pyabiword.i386 0:0.6.0.svn20071127-1
-rainbow.noarch 0:0.7.6-1.olpc2
+rainbow.noarch 0:0.7.8-1.olpc2
-sugar-evince.i386 0:2.20.0-4.olpc2
+sugar-evince.i386 0:2.20.1.1-1.olpc2
-sugar-evince-python.i386 0:2.20.0-4.olpc2
+sugar-evince-python.i386 0:2.20.1.1-1.olpc2
-sugar.i386 0:0.75.7-1
+sugar.i386 0:0.75.8-1
-totem.i386 0:2.18.2-11
+totem.i386 0:2.18.2-12
-totem-mozplugin.i386 0:2.18.2-11
+totem-mozplugin.i386 0:2.18.2-12
-totem-plparser.i386 0:2.18.2-11
+totem-plparser.i386 0:2.18.2-12
-xkeyboard-config.noarch 0:1.1-7.20071130cvs.olpc2
+xkeyboard-config.noarch 0:1.1-8.20071130cvs.olpc2
-xulrunner.i386 0:1.9-0.beta1.9.olpc2
+xulrunner.i386 0:1.9-0.beta2.1.olpc2

--- Paint-17 ---
   * Make the fix for #5586 work with security. (tomeu)

--- Read-40 ---
   * Fix zoom-to-width (tomeu), #5866

--- Record-50 ---
  * #4525 updates
  * #5899 workaround
  * #5830 fix

--- Web-84 ---
* Use ellipsis, #5765 (rwh)
* Implement can_close(), #5493 (rwh)

--
This email was automatically generated
Aggregated logs at http://dev.laptop.org/~bert/update.1-pkgs.html
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel






1200819339.429483 DEBUG root: *** Act f708c98ee5d0902d517204866cf00c3256f9245e, 
mesh instance None, scope private
1200819340.288800 DEBUG root: ListView.update_with_query
1200819340.391905 DEBUG root: bus_name:  at 
0x840576c>
1200819340.501348 DEBUG root: do_size_allocate: 0
1200819340.687227 DEBUG root: do_size_allocate: 11
1200819340.858381 DEBUG root: VolumeToolbar._add_hal_device: 
dbus.String(u'/org/freedesktop/Hal/devices/volume_uuid_2FD2_5097')
1200819341.130904 DEBUG root: VolumeToolbar._add_button: 'Journal'
1200819341.153855 DEBUG root: _vadjustment_changed_cb:
0.0
11.0
11.0
1.0
0.0

1200819341.158139 DEBUG root: _Cache.__init__: connecting signals.
1200819341.192275 DEBUG root: dbus_helpers.find: {'mountpoints': 
[dbus.String(u'59a4ae61-a0c4-4b00-8934-11e9c42379f5', variant_level=1)

Re: New update.1 build 682

2008-01-19 Thread Tomeu Vizoso
Hi,

looks like you have found http://dev.laptop.org/ticket/4013 .

Could you check, please?

Should work in latest joyride builds.

Thanks,

Tomeu

On Sat, 2008-01-19 at 18:00 -0800, [EMAIL PROTECTED] wrote:
> sorry for the delay in responding (I've been traveling for the last week)
> 
> attached is the messages file, it looks like the system is trying to 
> unmount the SD card immediatly after boot (<2 seconds)
> 
> I'll enable the sugar debugging and go into the journal immediatly after 
> boot and then see if there is anything interesting there.
> 
> I'll be upgrading to a new build as soon as the RC is released.
> 
> David Lang
> 
> On Wed, 16 Jan 2008, Tomeu Vizoso wrote:
> 
> > Date: Wed, 16 Jan 2008 10:29:25 -0500
> > From: Tomeu Vizoso <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: New update.1 build 682
> > 
> > Can you give some more details?
> >
> > Particularly, see
> > http://wiki.laptop.org/go/Attaching_Sugar_Logs_to_Tickets and
> > also /var/log/messages would be of interest.
> >
> > Thanks,
> >
> > Tomeu
> >
> > On Wed, 2008-01-16 at 07:18 -0800, [EMAIL PROTECTED] wrote:
> >> I can't get the journal to see the SD card with this build.
> >> I can see it from the command line just fine.
> >>
> >> David Lang
> >>
> >> On Tue, 15 Jan 2008, Build Announcer Script wrote:
> >>
> >>> Date: Tue, 15 Jan 2008 15:00:03 -0500 (EST)
> >>> From: Build Announcer Script <[EMAIL PROTECTED]>
> >>> Reply-To: [EMAIL PROTECTED]
> >>> To: [EMAIL PROTECTED]
> >>> Subject: New update.1 build 682
> >>>
> >>> http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build682/
> >>>
> >>> -Paint-15.xo
> >>> +Paint-17.xo
> >>> -Read-38.xo
> >>> +Read-40.xo
> >>> -Record-49.xo
> >>> +Record-50.xo
> >>> -Terminal-5.xo
> >>> +Terminal-8.xo
> >>> -Web-83.xo
> >>> +Web-84.xo
> >>> +bash.i386 0:3.2-19.fc7
> >>> -bash.i386 0:3.2-9.fc7
> >>> -gnash.i386 0:0.8.1-1.olpc2
> >>> +gnash.i386 0:0.8.1-2.olpc2.20071226cvs
> >>> -gnash-plugin.i386 0:0.8.1-1.olpc2
> >>> +gnash-plugin.i386 0:0.8.1-2.olpc2.20071226cvs
> >>> -hulahop.i386 0:0.4.0-1.olpc2
> >>> +hulahop.i386 0:0.4.0-2.olpc2
> >>> -initscripts.i386 0:8.54.1-15.olpc2
> >>> +initscripts.i386 0:8.54.1-17.olpc2
> >>> -libabiword.i386 0:2.6.0.svn20071106-1
> >>> +libabiword.i386 0:2.6.0.svn20071127-1
> >>> -libabiword-plugins.i386 0:2.6.0.svn20071106-1
> >>> +libabiword-plugins.i386 0:2.6.0.svn20071127-2
> >>> -libxml2.i386 0:2.6.29-1.fc7
> >>> +libxml2.i386 0:2.6.31-1.fc7
> >>> -libxml2-python.i386 0:2.6.29-1.fc7
> >>> +libxml2-python.i386 0:2.6.31-1.fc7
> >>> -mingetty.i386 0:1.07-5.2.2
> >>> +mingetty.i386 0:1.07-9.olpc2
> >>> -ohm.i386 0:0.1.1-6.1.20080102git.fc7
> >>> +ohm.i386 0:0.1.1-6.3.20080102git.fc7
> >>> -olpc-utils.i386 0:0.63-1.olpc2
> >>> +olpc-utils.i386 0:0.63-2.olpc2
> >>> -pyabiword.i386 0:0.6.0.svn20071106-1
> >>> +pyabiword.i386 0:0.6.0.svn20071127-1
> >>> -rainbow.noarch 0:0.7.6-1.olpc2
> >>> +rainbow.noarch 0:0.7.8-1.olpc2
> >>> -sugar-evince.i386 0:2.20.0-4.olpc2
> >>> +sugar-evince.i386 0:2.20.1.1-1.olpc2
> >>> -sugar-evince-python.i386 0:2.20.0-4.olpc2
> >>> +sugar-evince-python.i386 0:2.20.1.1-1.olpc2
> >>> -sugar.i386 0:0.75.7-1
> >>> +sugar.i386 0:0.75.8-1
> >>> -totem.i386 0:2.18.2-11
> >>> +totem.i386 0:2.18.2-12
> >>> -totem-mozplugin.i386 0:2.18.2-11
> >>> +totem-mozplugin.i386 0:2.18.2-12
> >>> -totem-plparser.i386 0:2.18.2-11
> >>> +totem-plparser.i386 0:2.18.2-12
> >>> -xkeyboard-config.noarch 0:1.1-7.20071130cvs.olpc2
> >>> +xkeyboard-config.noarch 0:1.1-8.20071130cvs.olpc2
> >>> -xulrunner.i386 0:1.9-0.beta1.9.olpc2
> >>> +xulrunner.i386 0:1.9-0.beta2.1.olpc2
> >>>
> >>> --- Paint-17 ---
> >>>* Make the fix for #5586 work with security. (tomeu)
> >>>
> >>> --- Read-40 ---
> >>>* Fix zoom-to-width (tomeu), #5866
> >>>
> >>> --- Record-50 ---
> >>>   * #4525 updates
> >>>   * #5899 workaround
> >>>   * #5830 fix
> >>>
> >>> --- Web-84 ---
> >>> * Use ellipsis, #5765 (rwh)
> >>> * Implement can_close(), #5493 (rwh)
> >>>
> >>> --
> >>> This email was automatically generated
> >>> Aggregated logs at http://dev.laptop.org/~bert/update.1-pkgs.html
> >>> ___
> >>> Devel mailing list
> >>> Devel@lists.laptop.org
> >>> http://lists.laptop.org/listinfo/devel
> >>>
> >> ___
> >> Devel mailing list
> >> Devel@lists.laptop.org
> >> http://lists.laptop.org/listinfo/devel
> >
> >


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


OLPC wifi interrupts wireless internet connection of _other_ laptop

2008-01-19 Thread Oliver
Hi all,

i have a rather strange problem. While my OLPC (g1g1 model) is turned
on another laptop of mine (Samsung Q10, 5 years old) has serious
trouble connecting to an access point (Linksys BEFW11S4).

I tried turning off the wireless connection of the OLPC
(sugar-control-panel -s radio off) but the problem persists until i
completely turn off the OLPC (with the power button) and restart the
Samsung laptop.

At one point i thought it's the router not being able to handle more
than a fixed number of clients. But the problem is that the Samsung
laptop doesn't even see any wireless networks. It goes so far that
NetStumbler fails with "orinoco error 5".

The wireless adapter of the Samsung is a "Orinoco mini-pc card' by
Lucent. If more information is need please let me know.

Any advice is appreciated. Cheers,

  Oliver
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Why can't i access /dev/dsp or /dev/snd on my XO

2008-01-19 Thread victor
Ah, I thought you were saying there was some problem with
Csound's MIDI implementation... (in which case we needed
to fix it). No need for that, all's well. Yes, Csound can handle
MIDI and it has done it for the most part of fifteen years.

I can't speak for TamTam because I am not involved in their
design details, but I can say this, Csound's standard score 
preceeds MIDI by at least a decade (or two if you consider where
it came from). It is much more flexible to convey musical data
than MIDI. There are MIDI to csound score converters, but
that is beside the point, because Csound can play MIDI files
directly, receive realtime MIDI data and even output it.
There is no problem whatsoever, with the proper instruments,
Csound will be a MIDI synthesizer like any other. The main
thing is, that it is not limited to it (thank goodness...).

(In fact, I am hoping that with the work on a sugar toolkit for Csound
apps, things like MIDI players will be put together with minimal
effort).

If you think that a MIDI file output for TamTam is needed,
then you should suggest it to them. So you'll be able to produce
these and play them on the XO laptop with Csound!

Perhaps we need to get more users from the Csound
community involved in the OLPC effort, so that they can
educate everyone in the ins and outs of the software.

Victor

- Original Message - 
From: "Albert Cahalan" <[EMAIL PROTECTED]>
To: "victor" <[EMAIL PROTECTED]>
Sent: Saturday, January 19, 2008 9:00 PM
Subject: Re: Why can't i access /dev/dsp or /dev/snd on my XO


> On Jan 19, 2008 2:48 PM, victor <[EMAIL PROTECTED]> wrote:
>> Hmm, if there are problems with Csound and
>> MIDI (of which I am not aware), we need to fix
>> them. Can you provide an example?
> 
> I'll start with the user-visible thing which is probably
> not entirely Csound's fault. Tam Tam is not using
> MIDI for input, output, or saved work. It should be
> using MIDI for all three, because MIDI is the standard
> for everything from consumer toys to professional
> performances. Even the selfish companies like Sony
> and Microsoft support MIDI.
> 
> From what I can tell, MIDI is not the native format for
> Csound. Musical scores are stored in an incompatible
> format. I can't play one with any normal MIDI player.
> I can only use Csound to play one. This is bad.
> 
> This isn't even like the *.mp3 or *.doc situation. There
> is no legal barrier to being standard. There is no problem
> with lack of documentation. Open source MIDI tools
> even exist, which does bring into question the need for
> having Csound at all.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Help : font size in console

2008-01-19 Thread Emiliano Pastorino
don't unzip the file, just copy it to /lib/kbd/consolefonts (or something
like that) and then

setfont 15x30pc

2008/1/19, Mr frÿffe9dÿffe9ric pouchal <[EMAIL PROTECTED]
>:
>
> Hello
>
> I downloaded the 15x30pc.psf.gz
> did gzip -d 15x30pc.psf.gz
>
> and then
>
> setfont -m 15x30pc.psf
> Error parsing symbolic map from '15x30pc.psf' , line
> 62
>
> consolechars -f 15x30pc.psf
> read_simple_font(): Bad font file format
>
> How can I use this font ?
>
> I run Debian 4.0r1
>
> By the way , which tool did you use to create this
> font ?
>
> Thanks
>
> Frederic Pouchal
>
>
>
>   
> 
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>



-- 
Emiliano Pastorino
LATU - Plan Ceibal
Av. Italia 6201 CP: 11500, Montevideo, Uruguay
Tel: (598 2) 601 3724 int.: 467
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Classroom tools

2008-01-19 Thread Yoshiki Ohshima
At Tue, 15 Jan 2008 14:11:40 -0800,
Edward Cherlin wrote:
> At the schoolroom level, the difference is between knowing rules for
> manipulating variables, and understanding what a variable is.
> (Basically, a variable name is a pronoun that can refer to a different
> number each time it is used.) Caleb Gattegno was particularly good at
> inducing understanding of arithmetic and elementary algebra using
> Cuisenaire rods. Everybody involved in XO software and content should
> read his work. In fact, a Cuisenaire rod activity would be brilliant.

  Yes.  In fact, the idea of making the numbers viewable as rods and
making them addable in Etoys has been popping on and off quite while.
Scott Wallace even has an experimental implementation.

-- Yoshiki
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Why can't i access /dev/dsp or /dev/snd on my XO

2008-01-19 Thread victor
Hmm, if there are problems with Csound and
MIDI (of which I am not aware), we need to fix
them. Can you provide an example? 

Victor

- Original Message - 
From: "Albert Cahalan" <[EMAIL PROTECTED]>
To: "victor" <[EMAIL PROTECTED]>
Sent: Saturday, January 19, 2008 7:24 PM
Subject: Re: Why can't i access /dev/dsp or /dev/snd on my XO


> On Jan 19, 2008 3:40 AM, victor <[EMAIL PROTECTED]> wrote:
>> Hannu's opinions are just that: opinions. The fact is that Linux
>> audio developers have been using alsa much more than OSS.
> 
> Hannu argues his points well. Do not discount him
> simply because he created OSS.
> 
> Linux audio developers have not been using ALSA.
> They have been using ugly wrapper libraries to deal
> with the incompatible mess we've gotten into. Those
> libraries support OSS as well.
> 
> There are far more OSS-only programs than ALSA-only
> programs. This is partly because writing a native ALSA
> program is overcomplicated, and partly because OSS is
> portable to *BSD and Solaris.
> 
>> Are you saying that Csound is not appropriate for the XO?
> 
> As a general audio system, yes. Csound may have some
> legitimate use on the XO. Shoving normal audio through
> Csound is bad. Using Csound to generate synthetic audio
> might be OK, though I note that Csound seems to have
> some incompatibilities with the MIDI standard. The XO
> should be able to function as both MIDI hardware roles,
> over both USB and IP. (the XO has one USB port that can
> act as a gadget-side device; MIDI has been standardized
> over both USB and IP)
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


OLPC News 2008-01-19

2008-01-19 Thread Walter Bender
1. Cambridge: A third Learning Workshop was held at OLPC this past
week. There was excellent attendance and participation; a real network
of laptop learning activists is forming. Workshop attendees are not
merely listening but are contributing to the conceptual basis of
practice in schools and communities. There was a blend between the
conceptual and practical concepts, and the localities beginning will
help innovate the learning environments and communities of the 21st
century. The presentation by Dr. Felton Earls and Maya Carlson of the
Harvard School of Public Health on participatory surveys and
indicators for community development as well as their work in Tanzania
and Chicago was inspirational. The Learning team of Edith Ackermann,
Ed Baafi, Fatimata Seye Sylla, Juliano Bittencourt, Elana Langer,
Julain Daily, Cynthia Solomon, Alice Cavallo, and David Cavallo
contributed mightily. Special thanks for support especially to Felice
Gardner, as well as Tracy Price and Jennifer Amaya. As always, a
highlight is the Activity Open House where developers demonstrate
their activities on the XO.

2. G1G1: During the reconciliation process of the "get" laptops
shipped during Give One Get One, a number of unfulfilled order records
were uncovered. The OLPC team has been working hard with our partners
to resolve all open issues. We expect another ~5000 XO laptops will be
shipped on Monday. The remaining orders pose an extra challenge as
they either have incomplete or no shipping and contact information. If
you have not yet received your XO laptop, you should be getting an
individualized email that addresses your specific situation. If you
are scheduled to receive your laptop next week, you will also be
getting a follow-up email with tracking information. We'll be adding
additional phone lines and shifting agents to reduce wait times. A
further reconciliation of the data will be conducted this week,
although hopeful, we can anticipate additional incomplete orders. Our
apologies for these delays.

3. Ulaan Baatar: Enkhmunkh Zurgaanjin, Carla Gomez Monroy, Jan
Jungclaus, and RedHat's David Woodhouse are working hard to set up a
structure that can provide sustainability to the project in Mongolia
such that it can spread it throughout the country. On Wednesday, the
Minister of Education visited the school for the "laptop hand out"
event. On Friday, an optical-fiber cable was set up, in spite of the
extreme low temperatures; on Saturday, the schools were connected to
the Internet. David has been working with a group of local technical
people on the servers and Internet set up infrastructure as well as on
configuration. John Watlington has been providing support remotely
from OLPC.

We have been meeting almost every evening with the strategic team of
the Ministry of Education to provide feedback and sort out challenges.
We met yesterday with the Ministry of Education team, teachers,
principals, ICTA, content team and pilot research team to provide
detailed feedback of how the project is going so far and to bring up
things to be considered for the short and long terms.

Teachers are putting their hearts into the program. They had their
first sessions with the children. Parents, too, have shown support.
And the children, of course, love it. The Constructionist model of
learning has found wide-spread support within the MoE.

There are more photos (See http://wiki.laptop.org/go/Ulaanbaatar) in our wiki.

4. School Server: John Watington reports that we have a new build
which supports schools with multiple servers in a school and including
a Jabber server! Build 150 was released, along with lengthy
configuration notes (See
http://wiki.laptop.org/go/XS_Installing_Software#OLPC_XS_150).

The configuration interface is still stone knife and bear skin, but
functionality appears to be there. We hope to have a build improving
the configuration process and adding web caching by the end of next
week.

David Woodhouse is in Ulaan Baatar, Mongolia helping Carla Gomez
Monroy deploy school servers along with the laptops. The servers we
shipped from Cambridge have arrived and are being installed. David has
been handling the difficult task of positioning two servers (with six
antennae) to cover a three-floor school. He is also facing the need to
upgrade the laptops right away to avoid a networking meltdown. The
good news is that the school is finally connected to the Internet; we
can assist from Cambridge.

5: Firmware: Richard Smith fixed the "repeated game keys on resume
bug" (Ticket #2401). During a resume, the main processor is not ready
to receive key codes for about 100ms after the delivery of the SCI
wakeup event. The EC dealt with this long delay badly. Fixing this
should unblock ebook mode. Richard released a new EC code version that
is available in Firmware Q2D09. This should show up in a signed
Joyride build soon.

6. Battery issues: Richard did a large amount work on batman.fth; he
added the ability to run a manual charge while wat

Help : font size in console

2008-01-19 Thread fr�ffffffffffe9d�ffffffffffe9ric
Hello

I downloaded the 15x30pc.psf.gz
did gzip -d 15x30pc.psf.gz

and then

setfont -m 15x30pc.psf
Error parsing symbolic map from '15x30pc.psf' , line
62

consolechars -f 15x30pc.psf
read_simple_font(): Bad font file format

How can I use this font ?

I run Debian 4.0r1

By the way , which tool did you use to create this
font ?

Thanks

Frederic Pouchal


  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Update.1 & testing

2008-01-19 Thread Jim Gettys
One other note, from what I've observed in trac about Joyride 1551:
apparently we may be in the reverse situation from before, with working
WPA and broken WEP wireless encryption, though I haven't confirmed this
first hand.  Testing (and fixes!) gratefully accepted...
 - Jim

On Sat, 2008-01-19 at 10:40 -0500, Jim Gettys wrote:
> Update.1
> 
> Update 1 is about to start the release process. Update.1RC1 is almost
> ready (by sometime Monday I hope). 
> 
> The first order of business for everyone with code in the build should
> be to go through closed bugs for Update.1 and verify they are fixed
> (you've been wondering what the little checkbox was for, haven't you)
> that they are fixed in the Update.1 build. Please also close bugs that
> you've fixed, but forgotten to close.
> 
> Suspend and resume is turned on (on MP systems); this will be ongoing
> work to improve into the indefinite future.  See this as a work in
> progress. Suspend and resume will only operate fully on mass production
> machines, since prototypes had hardware problems.  On B4's, the plan for
> RC1 is to allow manual sleep (momentary push of the power button will
> suspend the machine), though that is not in Joyride 1551.
> 
> Rainbow security is enabled.  The Web browser has been updated to use
> the technology in Firefox 3 Beta 2, which is significantly faster and
> better at memory usage. Innumerable bugs have been fixed.  Performance
> is significantly improved. Memory and file leakage of the system is
> reduced.
> 
> Update.1RC1
> ---
> Joyride 1551 is very, very close to Update.1RC1's contents, though has
> some additional activities we do no plan to ship in Update.1 bundled on
> the base system.  Those developers of you who read this over the weekend
> before the Update.1RC1 build is available please make sure to update to
> the the new firmware version (Q2D09), which is necessary to fix a number
> of key bugs for suspend and resume. We hope the firmware process will be
> automated in the real Update.1RC1 build.
> 
> RC2 will pick up additional translations and key bug fixes that missed
> RC1. The community is working to complete the Spanish translation, which
> was not complete by the string freeze date due to the holidays.  There
> will therefore be a refresh of packages to complete the translations.
> Activity developers should only be picking up translations (and fixes
> for approved bugs).
> 
> RC3 is intended to pick up critical bug fixes discovered during testing,
> and is the first candidate that is a real candidate for widespread
> release.  We'll do an RC4 if necessary.
> 
> Testing
> ===
> Joyride will be reopened for the start of Update.2 development later
> this week just after Update.1RC1 is available.  
> 
> As soon as RC1 is available, we will start a testing cycle:
> o suspend/resume cycling for reliability.  During the run up to
> mass production the hardware/firmware was found to be able to reliably
> suspend/resume at least 50,000 cycles (the length of the tests we were
> willing to tolerate). We need to ensure there are not software or
> firmware regressions in this area.
> o scaling tests - we need to ensure sane behavior of the systems
> in circumstances such as 300 children resuming their laptops all at once
> in the morning.
> o verification of power use in different use states, on our
> power measurement systems.
> o wireless driver testing and upgrade testing
> o testing with the school server software
>   o application testing: Kim Quirk has been hard at work with others on
> getting together test plans for core applications.
> 
> Those with blocking issues or who can help with them should stay focused
> on those tasks, and the first order of business is for everyone to go
> through their fixed bugs and *verify* they are fixed.
> 
> Thank you all for your hard work! Many children all over the world
> benefit immensely from your dedication
> 
>  - Jim
> 
> 
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing the Wireless driver changes

2008-01-19 Thread Michail Bletsas
> 
> Does the Boot2 code take care of figuring out the correct address to
> write the thick firmware to, or does the flash tool have to figure out
> the address to write it to?  Normally this address is embedded in the
> firmware flash file header, is there an address the tool should check
> for to verify, or is that address completely irrelevant because the
> boot2 code is smart enough to figure out where to put it?
> 
Dan,

You have to ask Ronak that. Right now the flash writing logic lives in the 
firmware.

M.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing the Wireless driver changes

2008-01-19 Thread Dan Williams
On Sat, 2008-01-19 at 13:05 -0500, Michail Bletsas wrote:
> 
> 
> Dan Williams <[EMAIL PROTECTED]> wrote on 01/19/2008 12:48:06 PM:
> 
> 
> > 
> > Hmm, ok... So all the external USB 8388 dongles have a larger SPI
> flash
> > to contain both the Boot2 code and the 100K thick firmware?
> > 
> yes, 

Does the Boot2 code take care of figuring out the correct address to
write the thick firmware to, or does the flash tool have to figure out
the address to write it to?  Normally this address is embedded in the
firmware flash file header, is there an address the tool should check
for to verify, or is that address completely irrelevant because the
boot2 code is smart enough to figure out where to put it?

Dan


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing the Wireless driver changes

2008-01-19 Thread Michail Bletsas
Dan Williams <[EMAIL PROTECTED]> wrote on 01/19/2008 12:48:06 PM:


> 
> Hmm, ok... So all the external USB 8388 dongles have a larger SPI flash
> to contain both the Boot2 code and the 100K thick firmware?
> 
yes,

M.___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Testing the Wireless driver changes

2008-01-19 Thread Dan Williams
On Sat, 2008-01-19 at 04:31 +0800, David Woodhouse wrote:
> On Fri, 2008-01-18 at 14:47 -0500, Dan Williams wrote:
> > What is the post-boot firmware flash functionality supposed to apply to,
> > the host-less active antenna? (which is what I heretofore had
> > understood).
> 
> As Ben says, they're the same thing. If you don't load the firmware
> within 5 seconds of the boot2 code starting up, the thing loads its own
> firmware from the internal flash.

Hmm, ok... So all the external USB 8388 dongles have a larger SPI flash
to contain both the Boot2 code and the 100K thick firmware?

Dan

> Yes, it's horrid. It doesn't even preserve the boot2 version, because we
> did some stupid hack to preserve that in the _driver_ rather than
> keeping it internal, so when we send the CMD_802_11_RESET command to
> kick the device back into boot2, we get 'device firmware changed' from
> the kernel and it appears as a completely new device...
> 
> Ideally, we want to just kill the auto-mesh-repeater mode, where boot2
> times out after 5 seconds and loads the firmware from the internal flash
> (which is obviously larger on these devices than on the XO). Can we
> achieve that just by updating to a 'normal' Boot2 version from the XO?
> 
> (Yes, I should be sleeping. No, I have no idea what timezone I'm in).
> 

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Downtime tonight Jan18 6PM EST

2008-01-19 Thread Ivan Krstić
On Jan 18, 2008, at 12:23 PM, Ivan Krstić wrote:
> Development services (git, trac) will be going down for 6-12 hours
> tonight, Jan 18, starting around 6PM EST.

We completed all maintenance in the designated timeframe, and  
dev.laptop.org in particular is in a substantially better shape than  
before. There was a 6-hour time window after maintenance where the SSH  
host keys for dev were changed; this is now reverted to the old keys.  
RSA fingerprint is:

 d5:e6:7d:59:16:9b:0d:e3:26:58:42:4a:cd:82:2a:cc

Cheers,

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Update.1 & testing

2008-01-19 Thread Jim Gettys
Update.1

Update 1 is about to start the release process. Update.1RC1 is almost
ready (by sometime Monday I hope). 

The first order of business for everyone with code in the build should
be to go through closed bugs for Update.1 and verify they are fixed
(you've been wondering what the little checkbox was for, haven't you)
that they are fixed in the Update.1 build. Please also close bugs that
you've fixed, but forgotten to close.

Suspend and resume is turned on (on MP systems); this will be ongoing
work to improve into the indefinite future.  See this as a work in
progress. Suspend and resume will only operate fully on mass production
machines, since prototypes had hardware problems.  On B4's, the plan for
RC1 is to allow manual sleep (momentary push of the power button will
suspend the machine), though that is not in Joyride 1551.

Rainbow security is enabled.  The Web browser has been updated to use
the technology in Firefox 3 Beta 2, which is significantly faster and
better at memory usage. Innumerable bugs have been fixed.  Performance
is significantly improved. Memory and file leakage of the system is
reduced.

Update.1RC1
---
Joyride 1551 is very, very close to Update.1RC1's contents, though has
some additional activities we do no plan to ship in Update.1 bundled on
the base system.  Those developers of you who read this over the weekend
before the Update.1RC1 build is available please make sure to update to
the the new firmware version (Q2D09), which is necessary to fix a number
of key bugs for suspend and resume. We hope the firmware process will be
automated in the real Update.1RC1 build.

RC2 will pick up additional translations and key bug fixes that missed
RC1. The community is working to complete the Spanish translation, which
was not complete by the string freeze date due to the holidays.  There
will therefore be a refresh of packages to complete the translations.
Activity developers should only be picking up translations (and fixes
for approved bugs).

RC3 is intended to pick up critical bug fixes discovered during testing,
and is the first candidate that is a real candidate for widespread
release.  We'll do an RC4 if necessary.

Testing
===
Joyride will be reopened for the start of Update.2 development later
this week just after Update.1RC1 is available.  

As soon as RC1 is available, we will start a testing cycle:
o suspend/resume cycling for reliability.  During the run up to
mass production the hardware/firmware was found to be able to reliably
suspend/resume at least 50,000 cycles (the length of the tests we were
willing to tolerate). We need to ensure there are not software or
firmware regressions in this area.
o scaling tests - we need to ensure sane behavior of the systems
in circumstances such as 300 children resuming their laptops all at once
in the morning.
o verification of power use in different use states, on our
power measurement systems.
o wireless driver testing and upgrade testing
o testing with the school server software
o application testing: Kim Quirk has been hard at work with others on
getting together test plans for core applications.

Those with blocking issues or who can help with them should stay focused
on those tasks, and the first order of business is for everyone to go
through their fixed bugs and *verify* they are fixed.

Thank you all for your hard work! Many children all over the world
benefit immensely from your dedication

 - Jim


-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: How to? School server implementation

2008-01-19 Thread Ivan Krstić
On Jan 19, 2008, at 1:09 AM, John Watlington wrote:
> The correct way to do this is to work with the Journal to treat the
> laptop as a cache of a larger Journal datastore located on the
> Schoolserver (and beyond, "in the cloud").  Perhaps Ivan can detail
> his vision and we can get other people to help implement it.


The current datastore codebase is hopeless and being scrapped. The new  
DS which supports this mode of operation natively was designed during  
this week's DS summit (spec to follow for public discussion in the  
next 2-3 weeks), and is currently planned to land in joyride as soon  
as update.2 is out, targeting full system integration in the update.3  
cycle.

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel