Your problem with the keypad enter is actually a problem with all
Speakup keypad functions in the 3.4 and 3.5 kernels. In all these
kernels, pressing any Speakup keypad key causes the kernel to crash and
burn, and the system must be hard rebooted in order to get things back
up and running.
Th
Two situations are a bit puzzling after installation for me.
1) on booting the system it doesn't matter what is in syslinux.cfg, enter
must be hit to turn sound on and finish the login. I've adjusted prompt
from 0 to 1 and it had no effect.
The second puzzle is a bit more troublesome and has to
Am Samstag, den 15.09.2012, 00:43 +0200 schrieb Ralf Mardorf:
is there a recommended free as in beer speech recognition for the
German
and English language?
Depends on your needs. I made quite good experience with julius¹
([AUR]²) and simon for the german language which can be found on
voxfo
Hi :)
is there a recommended free as in beer speech recognition for the German
and English language?
The information about Linux speech recognition I found until now is
outdated, resp. meager.
http://en.wikipedia.org/wiki/Speech_recognition_in_Linux#
http://www.linux-community.de/Internal/Nachri
> Do others have any thoughts on this matter?
Rather than null, why not just send to an empty tty which a user can
optionally switch to.
--
___
'Write programs that do one thing and do it well. Write programs to work
together.
>
> Do others have any thoughts on this matter?
>
I like to know whats going on. Output in some form is always welcome,
although errors should stand out and be obvious.
--
Yesterday is history.
Tomorrow is a mystery.
Today is a gift.
That's why its called the present.
Headmaster Squall :: Th
On Fri, 14 Sep 2012 00:10:54 +0200
Sébastien Luttringer wrote:
> > However, the issue is more general, and I'm
> > unsure whether I should continue posting such bugs.
> Systemd will probably remove all this *bad* but convenient hiding.
> I reminds you, this is to have a clean boot when everyth
Am 14.09.2012 16:10, schrieb David J. Haines:
> You always want to mount root read-only until such time as the system
> itself remounts read-write. This is by design. IIRC, it's related to the
> fact that you can't fsck a disk mounted read-write, thus the "-R" option
> for fsck.
As far as I can se
On Fri, Sep 14, 2012 at 07:39:50AM -0600, DG wrote:
> The partitioning step walks you through to this point, showing that
> the root partition is /dev/sda3 (if you are following the same
> scheme). So the syslinux line with root=/dev/sda3 ro is correct. I'm
> not sure about the ro vs rw, but mine
The partitioning step walks you through to this point, showing that
the root partition is /dev/sda3 (if you are following the same
scheme). So the syslinux line with root=/dev/sda3 ro is correct. I'm
not sure about the ro vs rw, but mine is ro and works fine.
NameFlags Part TypeFS Ty
According to Jude DaShiell:
# Failed to create secure file system message went away after I changed
ro to rw in
# syslinux.cfg. Should /dev/sda3 have been mentioned in syslinux.cfg where
# I have /home? If so, I didn't do that and this may explain some of the
# difficulties.
The device mentio
First, the hack to force the sound card on and to be unmuted does work.
I put it into /etc/profile since that should apply to the whole system.
I did manage to get dmesg output saved to a file. I'll see if I can get
that copied to another place where it can be shared later. I failed to
crea
The line syslinux.cfg leaves as root=/dev/sda3 ro if the example in the
beginner's guide is followed needs to be changed to:
root=/dev/sda1 rw
I am having further problems with the archlinux installation but these are
off topic for this message.
13 matches
Mail list logo
