Kernels in Debian

Kernels in Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hey, just curious.  When updating to latest git-pull of speakup, do
most Deb users go with Debian's kernel source or do they use the
generic one from ftp.kernel.org?  I'm about to update my copy of
speakup and even with 2.6.26, the install script in speakup appears to
need a kernel source tree.  Is my observation correct here?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj8aCYACgkQWSjv55S0LfG1ugCg+mOnm+sbu8luuI2ZTI7nzavC
eyUAnimQ4/ykAqdSIcAr4ozMqlzdtvS2
=vYcp
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Chuck Hallenbeck]

Steve,

I have always used the Debian source tree, but I think most people go
with the original release from kernel.org. The Debian patches are
available as a separate package if anyone needs them.

Chuck


On Mon, Oct 20, 2008 at 04:14:47AM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> Hey, just curious.  When updating to latest git-pull of speakup, do
> most Deb users go with Debian's kernel source or do they use the
> generic one from ftp.kernel.org?  I'm about to update my copy of
> speakup and even with 2.6.26, the install script in speakup appears to
> need a kernel source tree.  Is my observation correct here?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> 
> iEYEAREDAAYFAkj8aCYACgkQWSjv55S0LfG1ugCg+mOnm+sbu8luuI2ZTI7nzavC
> eyUAnimQ4/ykAqdSIcAr4ozMqlzdtvS2
> =vYcp
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
The Moon is Waning Gibbous (62% of Full)

My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022.
                                --------
It is wise to keep in mind that neither success nor failure is ever final.

Re: Kernels in Debian

[Kitty Litter]

I made a 2.6.27.1 kernel package from sources with latest speakup for my 
debian machine with no problems and used dpkg -i to install it like the good 
windows user I am!
. 

Re: Kernels in Debian

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I personally use the stock sources from kernel.org without the debian
patches, and I use kernel-package to build a debian package of the
kernel, which I then install with dpkg -i. Yes, your observation
regarding speakup is correct, you do need a configured kernel source
tree on your system to build speakup from the git sources.

Greg


On Mon, Oct 20, 2008 at 04:14:47AM -0700, Steve Holmes wrote:
> Hey, just curious.  When updating to latest git-pull of speakup, do
> most Deb users go with Debian's kernel source or do they use the
> generic one from ftp.kernel.org?  I'm about to update my copy of
> speakup and even with 2.6.26, the install script in speakup appears to
> need a kernel source tree.  Is my observation correct here?
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkj8yDoACgkQ7s9z/XlyUyCcRwCggnwdlrX04eYpCTHYyjwj8i3L
Ao4An1iuf/VsdTsO+xXyAE3lxpsdNmKU
=u82o
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I thought as much concerning the speakup and kernel situation.  I
thought the 2.6.26 and later could somehow be done without having to
build a kernel? I'm thinking of those machines or situations where one
could sit down at the computer and drop in speakup without modifying
the kernel on that machine.  Are we not quite there yet?  I think it
would be really cool if one could slap Speakup modules on a thunb
drive or something and boot a linux machine that is being visitted and
have the speakup modules loaded from the USB device with a mere boot
parameter or something like that.  This would be similar to the U3
implementations in windows or the Screen reader on a stick concempt.

On Mon, Oct 20, 2008 at 11:04:51AM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I personally use the stock sources from kernel.org without the debian
> patches, and I use kernel-package to build a debian package of the
> kernel, which I then install with dpkg -i. Yes, your observation
> regarding speakup is correct, you do need a configured kernel source
> tree on your system to build speakup from the git sources.
> 
> Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj80mQACgkQWSjv55S0LfEvHwCfaTjRDv6yC8oztxYSLF1m12Qb
zPsAoJjOed13WIQBAm5Z8NXChPSti4Qf
=fiH1
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[John covici]

The problem is module versioning -- the modules have to be compiled
with the same compiler and have the same version information as the
kernel.

One thing which would be nice, is if the Makefile in the src directory
of the git sources were arranged   to make
speakup for a non running kernel.  I tried doing a make with the
ubuntu 2.6.27 kernel which I had configured, but not installed speakup
in and the Make failed -- I think because I was not running the kernel
I wanted the speakup for.

on Monday 10/20/2008 Steve Holmes(steve@holmesgrown.com) wrote
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: RIPEMD160
 > 
 > I thought as much concerning the speakup and kernel situation.  I
 > thought the 2.6.26 and later could somehow be done without having to
 > build a kernel? I'm thinking of those machines or situations where one
 > could sit down at the computer and drop in speakup without modifying
 > the kernel on that machine.  Are we not quite there yet?  I think it
 > would be really cool if one could slap Speakup modules on a thunb
 > drive or something and boot a linux machine that is being visitted and
 > have the speakup modules loaded from the USB device with a mere boot
 > parameter or something like that.  This would be similar to the U3
 > implementations in windows or the Screen reader on a stick concempt.
 > 
 > On Mon, Oct 20, 2008 at 11:04:51AM -0700, Gregory Nowak wrote:
 > > -----BEGIN PGP SIGNED MESSAGE-----
 > > Hash: SHA1
 > > 
 > > I personally use the stock sources from kernel.org without the debian
 > > patches, and I use kernel-package to build a debian package of the
 > > kernel, which I then install with dpkg -i. Yes, your observation
 > > regarding speakup is correct, you do need a configured kernel source
 > > tree on your system to build speakup from the git sources.
 > > 
 > > Greg
 > -----BEGIN PGP SIGNATURE-----
 > Version: GnuPG v1.4.9 (GNU/Linux)
 > 
 > iEYEAREDAAYFAkj80mQACgkQWSjv55S0LfEvHwCfaTjRDv6yC8oztxYSLF1m12Qb
 > zPsAoJjOed13WIQBAm5Z8NXChPSti4Qf
 > =fiH1
 > -----END PGP SIGNATURE-----
 > _______________________________________________
 > Speakup mailing list
 > Speakup@braille.uwo.ca
 > http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: Kernels in Debian

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Oct 20, 2008 at 11:48:04AM -0700, Steve Holmes wrote:
> I thought as much concerning the speakup and kernel situation.  I
> thought the 2.6.26 and later could somehow be done without having to
> build a kernel?

Yes, this is possible on 2.6.26-later, provided that you build speakup
and all synths as modules. If you want to have a synth built into the
kernel, (which is what you wanted from my understanding), then you
need to patch speakup into the kernel, and rebuild. If you're ok with
having synths and speakup main code as modules only, and if you're
running at least 2.6.26, then you don't need to patch and rebuild the kernel.

> I'm thinking of those machines or situations where one
> could sit down at the computer and drop in speakup without modifying
> the kernel on that machine.  Are we not quite there yet?  I think it
> would be really cool if one could slap Speakup modules on a thunb
> drive or something and boot a linux machine that is being visitted and
> have the speakup modules loaded from the USB device with a mere boot
> parameter or something like that.  This would be similar to the U3
> implementations in windows or the Screen reader on a stick concempt.

As John pointed out, you need to have modules compiled against the
running kernel, so no, we're not there yet. I'd say the best
suggestion for what you're suggesting is a livecd, but that wouldn't
cover all possibilities either, (I.E. you can't reboot the machine
you're sitting in front of, or can't boot it off the cd drive).

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkj9BboACgkQ7s9z/XlyUyDsmgCfTU5RVpcu9Ow939vT8m9qeOsO
YzEAn1qvCka2RnHXhK2b2yRClOLp2HsN
=7Tyd
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Mon, Oct 20, 2008 at 03:27:07PM -0700, Gregory Nowak wrote:
> Yes, this is possible on 2.6.26-later, provided that you build speakup
> and all synths as modules. If you want to have a synth built into the
> kernel, (which is what you wanted from my understanding), then you
> need to patch speakup into the kernel, and rebuild. If you're ok with
> having synths and speakup main code as modules only, and if you're
> running at least 2.6.26, then you don't need to patch and rebuild the kernel.

Right, that's exactly what I want to do for the time being.  Just take
the existing kernel from Debian and replace the speakup modules.  When
I looked at the installation file from git/speakup, it appeared to me
that it had to have a kernel source tree to work with.  Maybe I missed
something some place?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj9FTEACgkQWSjv55S0LfHnQACglA5bLLIE4OMRgUrIQbukj/5A
30gAoMM1CotxG5Ny880/eO71k9UIWk6v
=kH2h
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Oct 20, 2008 at 04:33:06PM -0700, Steve Holmes wrote:
> Right, that's exactly what I want to do for the time being.  Just take
> the existing kernel from Debian and replace the speakup modules.  When
> I looked at the installation file from git/speakup, it appeared to me
> that it had to have a kernel source tree to work with.  Maybe I missed
> something some place?

The docs you get with the git sources could be out of date. See:

http://speech.braille.uwo.ca/pipermail/speakup/2008-May/046202.html

Also note that you will still need the sources for your running
kernel, simply the binary package isn't enough. Someone please correct
me if I'm wrong on that.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkj9GYgACgkQ7s9z/XlyUyB72ACdFCJcZWYaQ8pzE9vAkkqy9ozo
13EAnjHCQUW0LuEbHIynNT0VDwPtlo3/
=ji3v
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Mon, Oct 20, 2008 at 04:51:36PM -0700, Gregory Nowak wrote:
> The docs you get with the git sources could be out of date. See:
> 
> http://speech.braille.uwo.ca/pipermail/speakup/2008-May/046202.html
> 
> Also note that you will still need the sources for your running
> kernel, simply the binary package isn't enough. Someone please correct
> me if I'm wrong on that.

They are definitly out dated.  From what I could tell, there was
nomention of how to do a modules-only install.  The install script
looks like it is for the older way with patching and all.  Tonight, I
did a 'make' followed by a 'make modules_install' and that seemed to
work.  I did notice some reference to /usr/src/linux-headers... with a
depmod; not sure what exactly was going on in there.

This brings up another problem I ran into.  The modules_install target
put the modules in /lib/modules/2.6.26.1.../extra instead of
..../extra/speakup.  The debian packages placed the original speakup
modules in a speakup directory.  That sounds like the right place to
me.  This make file from git left the modules in one level up so I
moved them down into speakup and I now have a later speakup.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj9UesACgkQWSjv55S0LfGw0gCgnB8tKlSD4wcb0rlOi464twQO
p9AAn3F4JpOf55xnxpocPxCZFM81/f9q
=8nmF
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Tony Baechler]

Hi,

I'm sure you got many good responses on this, but this is what I do 
because it's far quicker and easier for me. I run the following commands:

aptitude -q install module-assistant
m-a prepare

Then, cd to the Speakup git pull and the src directory. For me, this is 
usually /usr/local/src/speakup/src or /home/tony/speakup/src. Then run:

make modules_install

The m-a prepare command will download and set up the necessary kernel 
tree structure. This will be a fairly big download, but will include all 
the Debian security patches that you won't necessarily get in the 
vanilla kernel.org source tree. That builds as modules. If you don't 
want modules, see below. After the modules are built, do:

cd /lib/modules/`uname -r`
I think cd extra, but it could be kernel/extra

You'll have a speakup directory and the speakup modules in the current 
dir. Just mv *.ko speakup to fix this:

mv speakup* speakup

This is important! Run this to make sure your system boots with speech:

depmod

As I said, that's if you want modules. If you want it built into your 
kernel, do this:

aptitude -q install kernel-package

You'll also need to install a Debian kernel source package, such as 
linux-source-2.6.26 or similar. Again, m-a prepare from the above 
commands should do this for you.

Change to the kernel source tree, usually /usr/src
tar -jxf *.bz2

Change to the Speakup git pull, such as ~/speakup
Run the patch script, telling it the source is in /usr/src/linux. You'll 
probably need to make a symlink from /usr/src/linux to 
/usr/src/linux-2.6.26. It should patch without errors. If you get 
errors, post a log on this list. After it patches, read the man page and 
help for the "make-kpkg" command. Run make-kpkg with the parameters and 
build options you want, such as if you want a custom version number. It 
should do all the build and compile steps for you, including "make 
config." You probably want to copy /boot/*config* to /usr/src/linux so 
you don't have to answer hundreds of config questions while still 
getting the Debian default options. Eventually, it will ask the Speakup 
questions. I build the dectlk driver into the kernel, the rest as 
modules. After that, come back in a couple hours and you'll have a bunch 
of .deb packages in /usr/src/linux. From there, just do:

dpkg -i /usr/src/linux/*speakup*.deb

or whatever you choose to call your kernel version. You could also just do:

dpkg -i /usr/src/linux/linux-image*deb

Then, run lilo as always and reboot. It will run update-initramfs and 
lilo for you, but I always run lilo again by hand just to make sure it 
works. Speakup should come up talking on the next reboot. If not, go 
back to the old kernel and try again or ssh in and look at dmesg.

Steve Holmes wrote:
> Hey, just curious.  When updating to latest git-pull of speakup, do
> most Deb users go with Debian's kernel source or do they use the
> generic one from ftp.kernel.org?  I'm about to update my copy of
> speakup and even with 2.6.26, the install script in speakup appears to
> need a kernel source tree.  Is my observation correct here?
>   

Re: Kernels in Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Thanks Tony for that good summary of steps.  I also looked around in
the /usr/share/doc/kernel-package (I believe it's called) and there
was a good write-up there too.  Your steps confirmed my observation
about where to put the speakup/*.ko modules.  I found out the hard way
I had to mv them down to the speakup directory.  I would have thought
the 'make modules_install' would have done this directly.

I'll have to read up on modules-assistent.  I didn't do anything in
that area yesterday and speakup is working for me.  I did install the
kernel headers; I'll have to take stock of the kernel stuff I did
install but I had not untarred the source tree yet.  I'm currently
satisfied with using modules right now.  I may eventually go with a
strait kernel with one speakup module included and bypass initrd
completely.  Personally, I wonder about the usefullness of a initrd on
a large desktop of my own.  I suppose those are good for smaller
systems where decisions have to be made as to which modules to
include.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj94CoACgkQWSjv55S0LfFHvwCfa/CpPrWx7BzBkbBbNVXDyIsI
COAAoOQrz4rtNQdQM8H/CMv0EaJpe+VP
=m7u6
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Chuck Hallenbeck]

Hi,

Tony's summary was extremely helpful. I just followed his steps, and
found that the resulting speakup modules ended up where they belong,
under extras/speakup, no need to move them there. The latest
combination of speakup, espeak, and espeakup, work much better than
with the debian package for the speakup modules in the lenny archives.

Chuck


On Tue, Oct 21, 2008 at 06:59:06AM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> Thanks Tony for that good summary of steps.  I also looked around in
> the /usr/share/doc/kernel-package (I believe it's called) and there
> was a good write-up there too.  Your steps confirmed my observation
> about where to put the speakup/*.ko modules.  I found out the hard way
> I had to mv them down to the speakup directory.  I would have thought
> the 'make modules_install' would have done this directly.
> 
> I'll have to read up on modules-assistent.  I didn't do anything in
> that area yesterday and speakup is working for me.  I did install the
> kernel headers; I'll have to take stock of the kernel stuff I did
> install but I had not untarred the source tree yet.  I'm currently
> satisfied with using modules right now.  I may eventually go with a
> strait kernel with one speakup module included and bypass initrd
> completely.  Personally, I wonder about the usefullness of a initrd on
> a large desktop of my own.  I suppose those are good for smaller
> systems where decisions have to be made as to which modules to
> include.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> 
> iEYEAREDAAYFAkj94CoACgkQWSjv55S0LfFHvwCfa/CpPrWx7BzBkbBbNVXDyIsI
> COAAoOQrz4rtNQdQM8H/CMv0EaJpe+VP
> =m7u6
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
The Moon is Waning Crescent (49% of Full)

My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022.
                                --------
It is wise to keep in mind that neither success nor failure is ever final.

Re: Kernels in Debian

[Kerry Hoath]

For reasons I am unclear on people seem to be alergic to initial ramdisks in 
modern Linux distributions.

The reason initial ramdisks are used in modern distributions is so that you 
can load modules required for boot devices, allow time for USB devices to 
settle before using them.

An initrd allows boot from raid and lvm, it also gives you a recovery 
environment in ram that does not rely on your disk systems.
It also allows partitions to be identified by uuid which will allow drives 
to change ids without the system becoming unbootable.

I seem to recall that kernel-package expects to build initial ram disks and 
unless you bypass the build machinery it might not be easy to switch off.
Once speakup integrates more seamlessly into Debian and it's getting better 
all the time then kernel package will be something worth sticking with for 
speakup.


I doubt it is the initrd that is preventing your large screens; you need to 
pass the option to the kernel as part of grub configuration and then run 
update-grub to copy it through the rest of the file.

I might look harder into this on the holidays although I run ubuntu not 
Debian.
Regards, Kerry.

----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, October 21, 2008 9:59 PM
Subject: Re: Kernels in Debian


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Thanks Tony for that good summary of steps.  I also looked around in
> the /usr/share/doc/kernel-package (I believe it's called) and there
> was a good write-up there too.  Your steps confirmed my observation
> about where to put the speakup/*.ko modules.  I found out the hard way
> I had to mv them down to the speakup directory.  I would have thought
> the 'make modules_install' would have done this directly.
>
> I'll have to read up on modules-assistent.  I didn't do anything in
> that area yesterday and speakup is working for me.  I did install the
> kernel headers; I'll have to take stock of the kernel stuff I did
> install but I had not untarred the source tree yet.  I'm currently
> satisfied with using modules right now.  I may eventually go with a
> strait kernel with one speakup module included and bypass initrd
> completely.  Personally, I wonder about the usefullness of a initrd on
> a large desktop of my own.  I suppose those are good for smaller
> systems where decisions have to be made as to which modules to
> include.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEAREDAAYFAkj94CoACgkQWSjv55S0LfFHvwCfa/CpPrWx7BzBkbBbNVXDyIsI
> COAAoOQrz4rtNQdQM8H/CMv0EaJpe+VP
> =m7u6
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: Kernels in Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I suppose the resistance to initrd might be the lack of full
understanding on how they work and how to manipulate them.  At least
that is my problem.  I know in concept how they work but I haven't
really figured out how to easily add to them; example would be adding
speakup modules to the initrd.  Perhaps the kernel-package does that?
not sure now.  

Concerning the larger screens, yes I have been passing 'vga=791' or
'vga=extended' all along with no effect.  I'm using lilo for now but I
have always been able to do that with Slackware with no problems.
With Slack, I was able to use 'vga=extended' flawlessly. I never could
get 'vga=791' to work.  After installing gnome on slackware, I got the
larger screen at boot time but not otherwise.  I probably have a
problem with display modules.  I have no fb devices show in /dev.

Personally, I like the integration os speakup in Debian so far; I had
no problems at all with getting started using my hardware speakout.  I
realize software speech is all the rage and that does not occur
natively with a Debian install.  That may improve over time.

On Wed, Oct 22, 2008 at 09:40:30AM +0800, Kerry Hoath wrote:
>
> For reasons I am unclear on people seem to be alergic to initial ramdisks 
> in modern Linux distributions.
>
> The reason initial ramdisks are used in modern distributions is so that 
> you can load modules required for boot devices, allow time for USB 
> devices to settle before using them.
>
> An initrd allows boot from raid and lvm, it also gives you a recovery  
> environment in ram that does not rely on your disk systems.
> It also allows partitions to be identified by uuid which will allow 
> drives to change ids without the system becoming unbootable.
>
> I seem to recall that kernel-package expects to build initial ram disks 
> and unless you bypass the build machinery it might not be easy to switch 
> off.
> Once speakup integrates more seamlessly into Debian and it's getting 
> better all the time then kernel package will be something worth sticking 
> with for speakup.
>
>
> I doubt it is the initrd that is preventing your large screens; you need 
> to pass the option to the kernel as part of grub configuration and then 
> run update-grub to copy it through the rest of the file.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj+55cACgkQWSjv55S0LfHNvQCfczzDbMkmWP2gyMwkTf3k5GVU
3sMAn1ilBye1b2LVI1HN9o4mYk4jfqXJ
=CzEp
-----END PGP SIGNATURE-----

Re: Kernels in Debian

[Samuel Thibault]

Steve Holmes, le Wed 22 Oct 2008 01:43:05 -0700, a écrit :
> example would be adding speakup modules to the initrd.

See /usr/share/doc/speakup-source/README.Debian:

Speakup may be included into the initrd, thus permitting to have speech feedback
before the root filesystem is mounted without having to patch the kernel. To do
so, add the name of the desired module to /etc/initramfs-tools/modules and run
update-initramfs -u

Samuel

Re: Kernels in Debian

[Chuck Hallenbeck]

Tony and all,

It looks like one needs to do a make, or perhaps a make modules, in the
speakup/src directory before doing a make modules_install. 

When I do that, my modules extras directory is populated by the new
compiles, and moving them into extras/speakup seems to complete the
process as you described.

Chuck

-- 
The Moon is Waning Crescent (20% of Full)

My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022.
                                --------
It is wise to keep in mind that neither success nor failure is ever final.

Re: Kernels in Debian

[Tony Baechler]

lutz kaiser wrote:
> i use debian and with installed speakup-modules for my kernel.
>
> now i tried to switch to the newer version of speakup.
> git pulling, went ok.
>
> then i followed your steps, received no errors, but still i have the 
> old modules installed.
> (date september 1th)


Hi,

Did you move the speakup* modules to the speakup directory?  Did you run 
depmod?  I had the old modules until I did both steps.  Try rebooting 
after running depmod.  You could also try "modinfo speakup" or 
"dmesg|grep speakup" to see if that shows anything useful.

Re: Kernels in Debian

[lutz kaiser]

Hi Tony and list,
i use debian and with installed speakup-modules for my kernel.

now i tried to switch to the newer version of speakup.
git pulling, went ok.

then i followed your steps, received no errors, but still i have the old 
modules installed.
(date september 1th)

What am i missing? Do you habe any ideas?

thanks in advance
Lutz

On 21.10.2008 10:02, Tony Baechler wrote:
> Hi,
>
> I'm sure you got many good responses on this, but this is what I do 
> because it's far quicker and easier for me. I run the following commands:
>
> aptitude -q install module-assistant
> m-a prepare
>
> Then, cd to the Speakup git pull and the src directory. For me, this 
> is usually /usr/local/src/speakup/src or /home/tony/speakup/src. Then 
> run:
>
> make modules_install
>
> The m-a prepare command will download and set up the necessary kernel 
> tree structure. This will be a fairly big download, but will include 
> all the Debian security patches that you won't necessarily get in the 
> vanilla kernel.org source tree. That builds as modules. If you don't 
> want modules, see below. After the modules are built, do:
>
> cd /lib/modules/`uname -r`
> I think cd extra, but it could be kernel/extra
>
> You'll have a speakup directory and the speakup modules in the current 
> dir. Just mv *.ko speakup to fix this:
>
> mv speakup* speakup
>
> This is important! Run this to make sure your system boots with speech:
>
> depmod
>
> As I said, that's if you want modules. If you want it built into your 
> kernel, do this:
>
> aptitude -q install kernel-package
>
> You'll also need to install a Debian kernel source package, such as 
> linux-source-2.6.26 or similar. Again, m-a prepare from the above 
> commands should do this for you.
>
> Change to the kernel source tree, usually /usr/src
> tar -jxf *.bz2
>
> Change to the Speakup git pull, such as ~/speakup
> Run the patch script, telling it the source is in /usr/src/linux. 
> You'll probably need to make a symlink from /usr/src/linux to 
> /usr/src/linux-2.6.26. It should patch without errors. If you get 
> errors, post a log on this list. After it patches, read the man page 
> and help for the "make-kpkg" command. Run make-kpkg with the 
> parameters and build options you want, such as if you want a custom 
> version number. It should do all the build and compile steps for you, 
> including "make config." You probably want to copy /boot/*config* to 
> /usr/src/linux so you don't have to answer hundreds of config 
> questions while still getting the Debian default options. Eventually, 
> it will ask the Speakup questions. I build the dectlk driver into the 
> kernel, the rest as modules. After that, come back in a couple hours 
> and you'll have a bunch of .deb packages in /usr/src/linux. From 
> there, just do:
>
> dpkg -i /usr/src/linux/*speakup*.deb
>
> or whatever you choose to call your kernel version. You could also 
> just do:
>
> dpkg -i /usr/src/linux/linux-image*deb
>
> Then, run lilo as always and reboot. It will run update-initramfs and 
> lilo for you, but I always run lilo again by hand just to make sure it 
> works. Speakup should come up talking on the next reboot. If not, go 
> back to the old kernel and try again or ssh in and look at dmesg.
>
> Steve Holmes wrote:
>> Hey, just curious. When updating to latest git-pull of speakup, do
>> most Deb users go with Debian's kernel source or do they use the
>> generic one from ftp.kernel.org? I'm about to update my copy of
>> speakup and even with 2.6.26, the install script in speakup appears to
>> need a kernel source tree. Is my observation correct here?
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Kernels in Debian

[lutz kaiser]

Hi Chuck,

many thanks for yor fast reply.
It did the trick - also the "direct" option works fine.

The german "ö" = "o" with two points above is now spelled correctly 
through espeak.

"make" did it

greatings
Lutz

On 24.10.2008 09:53, Chuck Hallenbeck wrote:
> Tony and all,
>
> It looks like one needs to do a make, or perhaps a make modules, in the
> speakup/src directory before doing a make modules_install.
>
> When I do that, my modules extras directory is populated by the new
> compiles, and moving them into extras/speakup seems to complete the
> process as you described.
>
> Chuck
>
>    

direct-option

[lutz kaiser]

hi list,
2 observations with the new feature:
if a word contains a special charakter, like "ö" (möglich) it is spoken 
m öglich.
caused by speakup thinking that on the special character a new word ist 
starting.
You can easyly reproduce it, when using "6" on the numberblock.
second:
a Word starting with such a charakter is overjumped when using "6"

To be on the save side, i used espeak directly, and there are no gaps or 
problems when speaking german words

many thanks for this feature
Lutz

Re: Kernels in Debian

[lutz kaiser]

hi Tony and List,

Chuck's advice helped - together with your steps i got it working.

Without "make" i got no speakup-files under .../extra which i could move 
to the folder

greatings
lutz

On 24.10.2008 10:52, Tony Baechler wrote:
> lutz kaiser wrote:
>> i use debian and with installed speakup-modules for my kernel.
>>
>> now i tried to switch to the newer version of speakup.
>> git pulling, went ok.
>>
>> then i followed your steps, received no errors, but still i have the 
>> old modules installed.
>> (date september 1th)
>
>
> Hi,
>
> Did you move the speakup* modules to the speakup directory? Did you 
> run depmod? I had the old modules until I did both steps. Try 
> rebooting after running depmod. You could also try "modinfo speakup" 
> or "dmesg|grep speakup" to see if that shows anything useful.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>