FYI, 

I havn't tested it yet, but my search at Toshiba's site for BIOS info,
led me to 'debouce keys', which led me here:
http://linux.toshiba-dme.co.jp/ML/tlinux-users/2300/2390.html

There's a slew of ways to (hopefully) fix the issue, which seems to be
some pieces of hardware sending 2 keyup events (Funny, it's opposite of
my Wine issue where the mouse L button up is never called ;)

Will report tomorrow. 

Question: If the patch listed DOES fix the bounce problem, wouldn't it
be included in the kernel at some point?


On Wed, 2002-09-25 at 14:04, J. Greenlees wrote:
> actually the delay before kicking in.
> my laptop has it in the bios, strange yours doesn't
> only bios I have seen that is completely user unfriendly is ibm's, an 
> old toshiba bios had the option to delay the typomatic kickin in it.
> 
> 
> Rick Romero wrote:
> 
> >I assume you mean the 'Typmatic Rate Programming' or something like
> >that.
> >
> >Unfortunately, the laptop doesn't have that setting, or anything close
> >to that.
> >
> >I'll keep that in mind for the desktop (Home PC) though.
> >
> >On Wed, 2002-09-25 at 12:10, J. Greenlees wrote:
> >
> >>have you tried setting the rate in the bios higher?
> >>it solved this problem for me.
> >>
> >>Rick Romero wrote:
> >>
> >>>I have a strange problem that I've actually run into on my home PC as
> >>>well.
> >>>
> >>>I've installed Mandrake 9.0 RC2 on a new Toshiba 1405S171 laptop.
> >>>Everything went PERFECTLY.  Audio/Video/Networking.  It all works just
> >>>fine.  
> >>>
> >>>Here's the issue.  When I type at 'normal speed', the input is doubled.
> >>>So if I type 'rick' I actually get 'rriicckk'.   
> >>>
> >>>I've had this issue occur on my home PC (home built) with Mandrake 8.1,
> >>>but I assumed it was my not-so-good (ok cheap) motherboard..
> >>>
> >>>Has anyone heard of an issue like this?  I'm not sure where else to ask,
> >>>most queries I've tried end up linking to c code.. (type double bleh ;)
> >>>
> >>>
> >>>Thanks
> >>>
> >>>Rick
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
> >
> 
> 
> 
> 



Reply via email to