I don't know much about this particular problem, but I do know that some
older IBM machines have issues with the *kernel*'s power management and
the CPU interrupts.  Try not only turning off ACPI in the bios, but pass
the kernel params:  "apm=off acpi=off" or some such.  

To pass kernel params to an Etherboot client, use option-129 in
dhcpd.conf.

To pass kernel params to a PXE client, add the params on the command
line in pxelinux.cfg/default (or a separate client-specific file if
desired).

HTH,

-Gadi

On Mon, 2006-07-24 at 10:02 -0400, Gentgeen wrote:
> On Sun, 23 Jul 2006 11:02:05 -0500
> John McMonagle <[EMAIL PROTECTED]> wrote:
> 
> > I have a bunch of  older  (1999 bios) pcs with the same problem.
> > Acted the same with usb keyboard.
> > A bios upgrade fixed it. Improved usb support also.
> > Experimenting with the settings found that if I tuned on acpi support
> > the problem came back.
> > So you may want to try turning off acpi in the bios.
> > 
> > John
> 
> 
> I have done a BIOS upgrade, that did not work.
> 
> I have turned off all the USB stuff in the BIOS, that did not work.
> 
> I have tried a USB, a PS/2, and a Serial Mouse, that did not work.
> 
> I have turned off the "power management", that did not work. (IIRC that
> is ACPI)
> 
> I have tried 3 different PS/2 keyboards (one was the old AT keyboard
> with a PS/2 adaptor), that did not work.
> 
> The only thing that has worked so far was a special XF86Config file,
> with:
>    
> Section "InputDevice"
>         Identifier      "IBM Keyboard"
>         Driver  "kbd"
>         Option  "CoreKeyboard" 
>         Option  "XkbModel"      "pc104"
>         Option  "XkbLayout"     "us"
>         Option  "XKbOptions"    ""
>         Option  "XkbRules"      "xfree86"
>         Option  "AutoRepeat"    "5000 30"
> EndSection
> 
> 
> as you can see, the repeat rate is HUGE.  Which is not too bad but the
> Backspace, Delete, Arrows, and such are annoying to use now.
> 
> Also, now that the keyboard response was slow enough, I was finally able
> to log in.  I found that a "Double Click" now required some CRAZY speed
> to register.  Many times I would just have to click as fast as I can a
> number of times (4,5,6, etc) just to get a response.  Not sure if that
> is related or not, but since I can not log in without the AutoRepeat
> set, I can not isolate this issue yet.
> 
> As noted in my first post, the most frustrating thing is that it worked
> fine with LTSP 4.1.  In fact this was my "gem" terminal for 4.1.  I
> "just worked" right out of the box.  
> 
> It is a mostly STOCK IBM Aptiva 2170-175.  I have only added memory and
> a NIC.
> 
> Anyone got some more ideas?  (I am going to look for a USB keyboard from
> a neighbor and see if that might help.)
> 
-- 
--------------------------------------------------------
Gideon Romm | Proud LTSP Developer
[EMAIL PROTECTED]

Support LTSP!  Buy your hardware at:

        www.DisklessWorkstations.com
        www.DisklessThinClients.com 
 
(use coupon code: LTSP5P for 5% off thin clients from DisklessThinClients.com)


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to