[raspberry-vi] Re: Accessible Arch
- From: Mike Ray <mike@xxxxxxxxxxxxxxx>
- To: raspberry-vi@xxxxxxxxxxxxx
- Date: Tue, 21 Jan 2014 20:39:03 +0000
Greg,
I think you're right and I will release the image as it is now. There's
no harm in releasing another version if I manage to get stuttery boot
messages fixed.
The only thing that makes me hesitate is that I have many years of
experience with belonging to email groups, and while this group is very
friendly and very small compared to some, there's always some joker
ready to pounce on the 2% that is wrong and disregard the 98% that works
like a dream.
I am getting a fibre-optic connection on Thursday so I will be able to
squirt images up to the web site much more quickly, if it all goes to plan.
After I have put the beta of the image on the site I will take a step
away from it for a few days and come back to it fresh.
Compiling pulseaudio on the Pi (about an hours worth of compiling) has
made me take another look at my cross-compiler tool-chain. So far I
have only built kernels and modules on my desktop Arch machine but there
is something called 'sysidk' which seems to be something to do with
setting up a full environment on a build machine. But there is zero
documentation for it. Judging by kernel builds my quad-core machine
should be able to compile pulseaudio in about two minutes.
Mike
On 21/01/2014 18:41, Gregory Osborne wrote:
> Mike,
> It sounds to me like you've made a lot of progress, and releasing what you
> have thus far would be acceptable / better than waiting for perfection unless
> you feel like you will have more time to put into the project in the
> immediate future. Even so, with all the time you've put in thus far, if this
> is in doubt at all or if you may want to step back and take a break, I'd say
> release what you have and just put a disclaimer on the list announcement /
> release notice. Obviously, something is better than nothing, and you've gone
> a long way past nothing.
>
> Just my two cents worth.
>
> - Greg
> -----Original Message-----
> From: raspberry-vi-bounce@xxxxxxxxxxxxx
> [mailto:raspberry-vi-bounce@xxxxxxxxxxxxx] On Behalf Of Mike Ray
> Sent: Tuesday, January 21, 2014 12:19 PM
> To: raspberry-vi@xxxxxxxxxxxxx
> Subject: [raspberry-vi] Accessible Arch
>
> Hello,
>
> Here's where I am currently with the accessible version of Arch Linux I am
> working on.
>
> I have managed now to configure pulseaudio on a per-user basis and set up a
> user account so that pulseaudio starts when the user logs in.
>
> When logged in, SpeakUp works fine and the audio is not stuttery because once
> the pulseaudio server is running espeak switches to using it instead of
> portaudio.
>
> But, the boot messages in this configuration are still very stuttery because
> at the point of boot up pulseaudio is not running for the system user and
> thus espeak is still using portaudio at that point.
>
> I have managed to get pulseaudio compiled without dbus support, it was dbus
> which was preventing it from starting in system mode before and changing
> security settings for dbus servers is beyond me at the moment.
>
> But I cannot get pulseaudio started with systemd. So I have to find a way to
> start it at boot for the root user without systemd.
>
> I might release beta 1 of this image with the boot messages still stuttering
> so that something that will boot Hynix boards is out there, and then return
> to trying to solve the stuttery boot messages issue.
>
> Oh and there is a problem with the kernel. When I compile SpeakUp modules
> for 3.10.27, which is the latest version, trying to load the modules results
> in 'exec format error' messages, while using kernel
> 3.6.11 this does not happen.
>
> So if I release an image before I can fix this I will have to blacklist the
> kernel to keep pacman from updating it. This is no great fault because I
> would have to blacklist the kernel anyway to stop the version number from
> changing and hence stopping SpeakUp modules from loading after update.
>
> People might want to tell me what they think about an image with stuttery
> boot messages.
>
> And I am aware that Arch is not everybody's cup of tea. Now that I know
> pulse solves the tts problem I will go back and re-address Raspbian.
>
> I am also considering forking espeak and trying to get it to set the latency
> in it's interface to portaudio. Currently it does not do anything in the
> portaudio API to select latency times but lets portaudio choose. There
> should probably be a Raspberry Pi version of espeak which allows for 'worse'
> latency to reflect the slower processor and lower memory of the Pi.
>
> Mike
>
--
Michael A. Ray
Analyst/Programmer
Witley, Surrey, South-east UK
I KEEP six honest serving-men, They taught me all I know. Their names are What
and Why and When and How and Where and Who.
-- Rudyard Kipling (paraphrased)
Interested in accessibility on the Raspberry Pi?
Visit: http://www.raspberryvi.org/
From where you can join our mailing list for visually-impaired Pi hackers
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views and
attitudes expressed by the subscribers to this list do not reflect those of the
Foundation.
Mike Ray, list creator, January 2013
Other related posts:
