Speakup V0.09 & new kernel 2.2.16...no talkie

Speakup V0.09 & new kernel 2.2.16...no talkie

[Buddy Brannan]

Hey y'all,

Well, because somehow I managed to screw up my previous kernel source tree
(patching to 2.2.16 and then Speakup, it didn't go very well, but it's
probably because I forgot I did something--or forgot to do something), I
downloaded a new complete 2.2.16 tarball, untarred it, patched in Speakup
V0.09A (Yes, I used the correct patch file), configured it--I lost my
original old .config, so I started it over--installed it--rebooted--and no
speech. 

I have the Accent SA on /dev/ttyS1 and wonder if it's not detecting there
for some reason? I have a modem (external, switched on) on /dev/ttyS0...I
haven't tried booting with the modem switched off. I think I shall try
this. In any case, how do you force Speakup to use a particular serial
port--I don't exactly recall.

Thanks.


-- 
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

RE: Speakup V0.09 & new kernel 2.2.16...no talkie

[Kaare Dehard]

hmm sounds encouraging:) just beginning the lerning with linux well...
today! best of luck to you:)

-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Buddy Brannan
Sent: Saturday, July 01, 2000 2:36 PM
To: speakup@braille.uwo.ca
Subject: Speakup V0.09 & new kernel 2.2.16...no talkie


Hey y'all,

Well, because somehow I managed to screw up my previous kernel source tree
(patching to 2.2.16 and then Speakup, it didn't go very well, but it's
probably because I forgot I did something--or forgot to do something), I
downloaded a new complete 2.2.16 tarball, untarred it, patched in Speakup
V0.09A (Yes, I used the correct patch file), configured it--I lost my
original old .config, so I started it over--installed it--rebooted--and no
speech.

I have the Accent SA on /dev/ttyS1 and wonder if it's not detecting there
for some reason? I have a modem (external, switched on) on /dev/ttyS0...I
haven't tried booting with the modem switched off. I think I shall try
this. In any case, how do you force Speakup to use a particular serial
port--I don't exactly recall.

Thanks.


--
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[Jacob Schmude]

Hi
	Add speakup_ser=1 to the kernel command line. This will force
speakup to look on ttyS1. My guess is that it's finding that modem and
attempting to use it as a synth. Of course, no response from the modem, so
no speech.


On Sat, 1 Jul 2000, Buddy Brannan wrote:

> Hey y'all,
> 
> Well, because somehow I managed to screw up my previous kernel source tree
> (patching to 2.2.16 and then Speakup, it didn't go very well, but it's
> probably because I forgot I did something--or forgot to do something), I
> downloaded a new complete 2.2.16 tarball, untarred it, patched in Speakup
> V0.09A (Yes, I used the correct patch file), configured it--I lost my
> original old .config, so I started it over--installed it--rebooted--and no
> speech. 
> 
> I have the Accent SA on /dev/ttyS1 and wonder if it's not detecting there
> for some reason? I have a modem (external, switched on) on /dev/ttyS0...I
> haven't tried booting with the modem switched off. I think I shall try
> this. In any case, how do you force Speakup to use a particular serial
> port--I don't exactly recall.
> 
> Thanks.
> 
> 
> -- 
> Buddy Brannan, KB5ELV        | And if the ground yawned,
> Email: davros@ycardz.com     | I'd step to the side and say,
> Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
> Voice mail: (877) 791-5298   | --Eddie From Ohio
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[Buddy Brannan]

Kernel command line--where's that? In lilo.conf?


-- 
Buddy Brannan, KB5ELV        | And if the ground yawned,
Email: davros@ycardz.com     | I'd step to the side and say,
Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
Voice mail: (877) 791-5298   | --Eddie From Ohio

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[Jacob Schmude]

Hi
	That depends. If you're on a dedicated partition and use lilo, put
the following in the configuration file after the read-only line for the
kernel:
	append="speakup_ser=1"
	Now, rerun /sbin/lilo. Note: you can put it anywhere after the
image=/vmlinuz line. In slackware and debian, the kernel is /vmlinuz. In
redhat, it's /boot/vmlinuz. Here's what a section of my lilo.conf looks
like (with my kernel params replaced with yours):
image=/vmlinuz
	root=/dev/hda4
	read-only
	append="speakup_ser=1"
	Don't forget to rerun lilo to update the boot sector. Or, just
type:
linux speakup_ser=1
to boot linux at the boot: prompt if you don't want to edit lilo.conf.
	If you're using zipspeak or zipslack, add it to the loadlin line 
that loads your kernel in linux.bat.

On Sat, 1 Jul 2000, Buddy Brannan wrote:

> Kernel command line--where's that? In lilo.conf?
> 
> 
> -- 
> Buddy Brannan, KB5ELV        | And if the ground yawned,
> Email: davros@ycardz.com     | I'd step to the side and say,
> Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
> Voice mail: (877) 791-5298   | --Eddie From Ohio
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[brent harding]

I've had that happen when I compiled a kernel once too. I didn't configure
it right, that was the problem even though I have thought I configured
everything right. It's likely that the kernel probably doesn't make it to
the login prompt. It's hard to know what's needed or isn't as even using a
default config and doing oldconfig asks questions I don't know the answer
to. Defaults seem to make things unbootable, don't know how the applied
kernels configure, but they work for me. It was probably the lack of an
ethernet card in the machine and compiling support for it by mistake that
made it unbootable some of the times. At least I have a .config file that
seems to work. My config file though is for a debian kernel version 2.2.15,
as that's the latest one out distributed for it. I like it now though
because dynamic dns allocation is a snap, kind of a coincidence as that
wasn't the major reason I chose that distribution.
 I find packages easy to install, and it picks the right programs when you
don't have what it needs to install. But the thing that sold me was the
upgrading features and the ability to get started by downloading files, but
that took awhile to download what I have, as it installs more minimally
than zipspeak as a base install. I hear that it has one of the best
configuration tools for setting up pcmcia on laptops, something I've yet to
do.
 

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[brent harding]

I think one could put append in there, don't know the exact way of doing
it, what seems even harder is to make lilo be able to answer the modem, if
I get dialin ppp going when I get a better connection. I'd have to make
sure it doesn't send a return as it'd boot to windows, and I'd have no
remote control of the system. When using ips on the local network, is it a
big issue about the windows file sharing that two people connected to my
machine by modem with for say 10.0.0.1 and 10.0.0.2 would blame me for
allowing person 1 to map person 2's c drive to their computer, seeing all
machines on my network at the time would be visible in network neighborhood
in windows? Does this only apply to the machines directly hooked by
ethernet, or does dialup connections have the same properties and abilities
that my computer could do when hooked to my laptop. I intend to just hook
the main computer to the network card and whatever kind of connection
becomes available, and have a place to hook my laptop in so I can solve the
problem of how to transfer files between the two machines, but the dialups
connected by modem off the main computer would have access to all the
devices just like I would on my laptop, right? That wouldn't be good if
they use my sound card when I'm trying to record something, I guess that's
what userdel becomes necessary for, but don't particularly want to use that
method to prevent them from using my audio devices over the network when
I'm doing stuff with it. How would I make my dialup line use the isp's dns,
as I don't even know a thing about dns config files, and updating the
millions of domains in the internic database to be able to be resolved when
I use dialup? That's one thing ipmasking won't give me, and I don't like
entering ip addresses in to my web browser and email, do I have to run dns
just to give me a dialup line to get on the net when I'm using my laptop
somewhere else, or does it use the one my regular machine is set to?
At 04:28 PM 7/1/00 -0500, you wrote:
>Kernel command line--where's that? In lilo.conf?
>
>
>-- 
>Buddy Brannan, KB5ELV        | And if the ground yawned,
>Email: davros@ycardz.com     | I'd step to the side and say,
>Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
>Voice mail: (877) 791-5298   | --Eddie From Ohio
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[Gene Collins]

Hi Buddy!  try speakup_ser=1.

Gene

>Hey y'all,
>
>Well, because somehow I managed to screw up my previous kernel source tree
>(patching to 2.2.16 and then Speakup, it didn't go very well, but it's
>probably because I forgot I did something--or forgot to do something), I
>downloaded a new complete 2.2.16 tarball, untarred it, patched in Speakup
>V0.09A (Yes, I used the correct patch file), configured it--I lost my
>original old .config, so I started it over--installed it--rebooted--and no
>speech. 
>
>I have the Accent SA on /dev/ttyS1 and wonder if it's not detecting there
>for some reason? I have a modem (external, switched on) on /dev/ttyS0...I
>haven't tried booting with the modem switched off. I think I shall try
>this. In any case, how do you force Speakup to use a particular serial
>port--I don't exactly recall.
>
>Thanks.
>
>
>-- 
>Buddy Brannan, KB5ELV        | And if the ground yawned,
>Email: davros@ycardz.com     | I'd step to the side and say,
>Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
>Voice mail: (877) 791-5298   | --Eddie From Ohio
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[Buddy Brannan]

Yep, did that over the weekend and it works fine now...thanks.

--
Buddy Brannan, KB5ELV
Email: davros@ycardz.com
Voice mail: 877-791-5298
All opinions are all mine!

Re: Speakup V0.09 & new kernel 2.2.16...no talkie

[Gene Collins]

Just add an append line to your lilo.conf file, or type in the
speakup_ser=1 parameter at the lilo prompt, like this:

linux speakup_ser=1

Gene


>Kernel command line--where's that? In lilo.conf?
>
>
>-- 
>Buddy Brannan, KB5ELV        | And if the ground yawned,
>Email: davros@ycardz.com     | I'd step to the side and say,
>Phone: (972) 276-6360        | "Hey ground! I'm nobody's lunch!"
>Voice mail: (877) 791-5298   | --Eddie From Ohio
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup