Debian ist kaput, revisited...

Debian ist kaput, revisited...

[Gaijin]

	Hello again,

	Alright.  Looked over grub's menu.lst file, and I can see that
every kernel listed  (both the new 2.6.25 w/separate SpeakUP module, and
old Shane SpeakUP kernel with built-in module) have the
speakup_synth=ltlk parameter.  Would this be the cause of the problems
with being unable to echo things to
/sys/module/speakup/parameters/whatever?  TIA,

			Michael

Re: Debian ist kaput, revisited...

[Tony Baechler]

Gaijin wrote:
> 	Alright.  Looked over grub's menu.lst file, and I can see that
> every kernel listed  (both the new 2.6.25 w/separate SpeakUP module, and
> old Shane SpeakUP kernel with built-in module) have the
> speakup_synth=ltlk parameter.  Would this be the cause of the problems
> with being unable to echo things to
> /sys/module/speakup/parameters/whatever?  TIA,
>   



Hi,

I don't know but I would doubt it.  I'm using a DEC Express and have the 
same problem.  I have two kernels, the newest Debian kernel from Sid and 
my custom compiled one.  I use lilo, not grub.  If I boot into kernel 1, 
or "Linux," I have the same problem as you.  My /etc/rc.local also quit 
working.  If I boot into my old Linux kernel, everything works as 
before.  Both kernels, or both sets of modules, have the same bug where 
speech will stop after about a screen and a half of text, say about 4 
KB.  I haven't tried doing anything with git as I really don't feel like 
compiling a new kernel package set again and it takes several hours.  I 
haven't figured how to pull from git and just compile modules but I 
think module-assistant would do that if I could get it not to 
automatically download the "latest" Speakup Debian source, which is 
3.0.2-20080517.  Also, I want a stable set of Speakup modules and it 
looks like the past few weeks are not stable yet.

Re: Debian ist kaput, revisited...

[Samuel Thibault]

Tony Baechler, le Mon 21 Jul 2008 03:28:27 -0700, a écrit :
> I haven't tried doing anything with git as I really don't feel like 
> compiling a new kernel package set again and it takes several hours.

You don't really need to recompile a new kernel if you are fine with
speakup being compiled as modules.

> I haven't figured how to pull from git and just compile modules

sudo module-assistant prepare
git clone http://www.linux-speakup.org/speakup.git
cd speakup/src
make
sudo make modules_install

voilà.

> but I think module-assistant would do that if I could get it not to   
> automatically download the "latest" Speakup Debian source, which is   
> 3.0.2-20080517.
> Also, I want a stable set of Speakup modules and it looks like the
> past few weeks are not stable yet.

It should be now (or at least as much as 20080517).  I actually intend
to push a new snapshot to debian.  But without people testing the git
tree, we can not be so sure that it's stable enough...

Samuel

Re: Debian ist kaput, revisited...

[Tony Baechler]

Samuel Thibault wrote:
>> I haven't figured how to pull from git and just compile modules
>>     
>
> sudo module-assistant prepare
> git clone http://www.linux-speakup.org/speakup.git
> cd speakup/src
> make
> sudo make modules_install
>
> voilà.
>   



Hi,

Thank you!  That's exactly what I was looking for.  I got 
module-assistant to compile but I couldn't get it to use local sources 
instead of downloading them.  Yes, you have a good point in that new 
changes need to be tested, but again I didn't want to wait for hours to 
generate a new set of kernel packages.  For now, I'm fine with Speakup 
compiled as modules until I know it's stable and doesn't have crashes or 
unusual problems.

Re: Debian ist kaput, revisited...

[Gaijin]

On Mon, Jul 21, 2008 at 03:28:27AM -0700, Tony Baechler wrote:
> If I boot into kernel 1, or "Linux," I have the same problem as you.

Yeah, that's a pretty strange error to have returned.  I'm wondering
what-all would cause and "Invalid argument" error now.  File and
ownership permissions were all okay.  I'll reboot and try the keyboard
controls for speed and volume, etc., and see if those work.  I should
have thought to check those, but didn't think of it until just now.

> My /etc/rc.local also quit working.

	rc.local is run "set -e" which will exit immediately on any
error.  I have mine set up to use 'uname -r' to read the kernel name, so
if it's Shane's kernel, to do things one way and address the /proc
system, and if not, address the /sys system.  ie:

if [ `uname -r` != "Shane's kernel name" ]; then
	echo to /sys-modules
else
	echo to /proc-modules
fi

	Anyway, it keeps rc.local from quitting during setting up the
synth on the Shane kernel, and addresses the correct modules.  Also did 
it to some scripts in /usr/local/sbin, where I keep the synthesizer's 
speed, bolume, and default-settings controls.
	Actually, I did a:

	uname -r > /etc/proc-kernel

	...while I was using Shane's kernel, and the real line in
rc.local is"

if [ `uname -r` != `cat /etc/proc-kernel` ]; then

...so I only have to change/create one proc-synth file in case I have to
reinstall Etch from scratch again.  Once I have scripts set up for
something, I hate having to go in and  re-edit them all over again.
/usr/local is on it's own partition.  That last Lenny update last night
did something to the system after cron.daily had ran, I think, because I
couldn't su into root until I had rebooted.  Seems  to be working okay
now, though.


  If I boot into my old Linux kernel, everything works as  
> before.  Both kernels, or both sets of modules, have the same bug where  
> speech will stop after about a screen and a half of text, say about 4  
> KB.  I haven't tried doing anything with git as I really don't feel like  
> compiling a new kernel package set again and it takes several hours.  I  
> haven't figured how to pull from git and just compile modules but I  
> think module-assistant would do that if I could get it not to  
> automatically download the "latest" Speakup Debian source, which is  
> 3.0.2-20080517.  Also, I want a stable set of Speakup modules and it  
> looks like the past few weeks are not stable yet.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Debian ist kaput, revisited...

[Gaijin]

On Mon, Jul 21, 2008 at 12:15:37PM -0700, Yours Truly wrote:
> I'll reboot and try the keyboard controls

	Yes!  Alright, the keyboard controls appear to all be working to
control synthesizer settings, but echo still returns the "Invalid
argument" error.  Weird.  Is there a Debian package that enters
keystrokes for you as if you were typing them and is scriptable? <grins>
Just  tried rc.local again after controlling the synth via keyboard
controls and am still getting the invalid argument error, so it's not
something that can be hammered into place to make it work.  I guess I'll
try this kernel out for awhile and see what happens.  I can live without
being able to echo things to the synth for now, since the keyboard
controls werk.  Could barely understand things before, with the synth
talking so fast.

			Michael

Re: Debian ist kaput, revisited...

[Georgina Joyce]

> I guess I'll
> try this kernel out for awhile and see what happens. 

I found the same here too.  You might also find that if you alt + left
arrow, to switch consoles.  The system freezes.  Here's what I did:

Boot machine (debian unstable updated 21 July 2008.).
Installed kernel image for AMD64 and speakup modules.
Entered into menu.lst and rebooted.
Logged in as root.
modprobe speakup_ltlk.
Found that the echo commands were giving errors.
Pressing left arrow locked the machine.
Rebooted machine and after loading speakup the same result with left
arrow to ttyS11, for a second time.

I use the UK key map.

> Gena 

http://www.ready2golinux.com

M0EBP