From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: New kernel problems
Date: Sun, 19 Oct 2008 17:13:53 -0500 [thread overview]
Message-ID: <20081019221353.GA4052@linux1> (raw)
In-Reply-To: <DCD2060FD48547B0A6CF417CEE947FDF@BOE>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Jason,
Correct, the kernel needs to be installed before emerging speakup.
I do not have a special script that I use to install kernels. If you
have sys-apps/debianutils installed, it has a script that will do this.
I do this to compile and install a kernel:
cd /usr/src/linux
# configure the kernel
make # this compiles the kernel after configuring it
make modules_install install
Then you have to edit the /etc/modules.autoload.d/kernel-2.6 file and
put in there a line for the speakup module you want to load.
Once that is done, you should be up and running on your next reboot.
William
On Sun, Oct 19, 2008 at 05:19:10PM -0400, Jayson Smith wrote:
> Hi,
>
> I'm compiling the kernel now. Let me get this right. I need to also
> install the kernel, before emerging Speakup?
> I have a kernel.sh script I used to use to install kernels once compiled.
> It goes like this:
>
> #!/bin/bash
> cd /usr/src/linux
> echo Moving the system map
> mv System.map /boot/System.map-2.6
> cd arch/i386/boot
> echo moving the kernel
> mv bzImage /boot/vmlinuz-2.6
> cd ~
> echo Running Lilo
> lilo
> echo Done.
>
> Does this still work? This was a few years ago. Do I need to do this before
> emerging speakup? Also, it's been a while, what's the kernel boot command
> to get Speakup going again? Is it speakup synth=dectlk? I'm using a Dectalk
> Express.
> Thanks again.
> Jayson
>
> ----- Original Message ----- From: "William Hubbs" <w.d.hubbs@gmail.com>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Sunday, October 19, 2008 4:52 PM
> Subject: Re: New kernel problems
>
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi Jason,
>>
>> make sure that "symlink" is in your use flags when you emerge the
>> kernel. That will make sure that /usr/src/linux points to the new
>> kernel.
>>
>> Then, configure and install the kernel.
>>
>> After that, emerge speakup then set up the boot system to load the
>> module for your synthesizer, then reboot.
>>
>> At that point you should have speech.
>>
>> Thanks,
>>
>> William
>>
>> On Sun, Oct 19, 2008 at 04:42:23PM -0400, Jayson Smith wrote:
>>> Hi,
>>>
>>> Okay, so I need to configure and install the new kernel first? Does
>>> that mean I need to reboot, and will be without console speech?
>>> Thanks.
>>> Jayson
>>>
>>> ----- Original Message ----- From: "William Hubbs" <w.d.hubbs@gmail.com>
>>> To: "Speakup is a screen review system for Linux."
>>> <speakup@braille.uwo.ca>
>>> Sent: Sunday, October 19, 2008 4:04 PM
>>> Subject: Re: New kernel problems
>>>
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Hi Jason,
>>>>
>>>> First off, do not bother with cvs speakup. All of the work is going on
>>>> in a git repository.
>>>>
>>>> On gentoo, the first thing you have to do is emerge, compile, configure
>>>> and install gentoo-sources-2.6.25 or later. Make sure that the
>>>> /usr/src/linux symlink points to the correct kernel.
>>>>
>>>> Then, emerge speakup, and set it up to load the module automatically on
>>>> boot for your synthesizer and you should be ready to go.
>>>>
>>>> I'm not sure about the access violation you got, without seeing what was
>>>> going on at the time.
>>>>
>>>> If you have any questions, feel free to let me know.
>>>>
>>>> Thanks,
>>>>
>>>> William
>>>>
>>>> On Sun, Oct 19, 2008 at 03:42:35PM -0400, Jayson Smith wrote:
>>>>> Hi,
>>>>>
>>>>> Long time off this list. Anyway, I need to upgrade my kernel,
>>>>> mine's
>>>>> way out of date. I'm using Gentoo, and downloaded the Gentoo 2.6.25-R8
>>>>> Kernel sources. I can't get Speakup to install into that directory. If
>>>>> I
>>>>> use the CVS checkout script, a lot of the patching hunks fail. There's
>>>>> a
>>>>> Portage package for Speakup which is masked, but I grabbed it anyway.
>>>>> It
>>>>> compiles, then gives an access violation. So, how do I get Speakup
>>>>> patched
>>>>> into this kernel?
>>>>> Thanks!
>>>>> Jayson
>>>>>
>>>>> _______________________________________________
>>>>> Speakup mailing list
>>>>> Speakup@braille.uwo.ca
>>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>> -----BEGIN PGP SIGNATURE-----
>>>> Version: GnuPG v2.0.9 (GNU/Linux)
>>>>
>>>> iEUEARECAAYFAkj7ktsACgkQblQW9DDEZTjk8wCePr7o4odX/un54bBR+w08Imvt
>>>> OkgAlj1zjOryKkivNF3rIhHU2Pm2dO8=
>>>> =sU/N
>>>> -----END PGP SIGNATURE-----
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@braille.uwo.ca
>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.9 (GNU/Linux)
>>
>> iEYEARECAAYFAkj7niAACgkQblQW9DDEZTi8TQCfWzV4E/kDOnJ6X2UohwDPnnVa
>> 4CsAoIOh8JXg7ZgQXkashz+JGNTyZpgy
>> =aLv8
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkj7sSEACgkQblQW9DDEZTgBNACff3uWnrQe65YIMtUi4Je+1zSr
Df8AnjxN5kTgIHKcAEMR0EVLMYHcEFeq
=5sWk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Jayson Smith
` William Hubbs
` Jayson Smith
` William Hubbs
` Jayson Smith
` William Hubbs [this message]
` William Hubbs
` Jayson Smith
` John covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081019221353.GA4052@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).