From: ameer armaly <ameer@charter.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: keyboard doesn't respond when booting 2.6.5
Date: Thu, 6 May 2004 20:37:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0405062036300.8486@debian> (raw)
In-Reply-To: <20040507001136.GA467@lava-net.com>
Never, and I've been using 2.6 for 2 months; only thing tI can think of is
to make sure you have input, serio, and the at keyboard selected.
On Thu, 6 May 2004, Igor Gueths wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all. I am attempting to get 2.6.5 running here. However, whenever I
> reboot from 2.4.25 to 2.6.5, Speakup seems to not respond to keyborad
> input. I am not sure about the rest of the kernel, however when I hit
> control for example there is no response. I ran the checkout script to
> patch 2.6.5 (I am not sure what the build date is on the Speakup I
> have). On the list recently I've seen some reference to something called
> Genmap...So I checked /usr/src/linux/drivers/char/speakup. And sure
> enough, there's genmap.c but it didn't compile. I compiled in all the
> correct support in input devices in terms of what the kernel requires,
> however I'm thinking its Speakup that may be the problem. Has anyone
> experienced behavior of this type? I haven't seen anything like it until
> now. Thanks!
> - --
> Failure is not an option, it comes bundled with your Microsoft product.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAmtQ4Nohoaf1zXJMRAjiEAJ9hFzs3XCKx3i8ITxkbJTofwO9AdwCfae7Y
> QcET1g4/2kGUGrMLxGoKbww=
> =P4h8
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` ameer armaly [this message]
` Igor Gueths
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=Pine.LNX.4.58.0405062036300.8486@debian \
--to=ameer@charter.net \
--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).