Yes it is related to ACPI. You may have to recompile your kernel to turn on certain ACPI features IF your laptop will run ACPI properly. The link to linuxlaptops I sent you does relate how that person went through some ACPI hacks to get everything working. Since it is working during the load of linux and then stops at some point when some program/deamon is loaded and running we know your hardware is good.
I would totally try to recompile my kernel if I had even the slightest clue how. My downfall on this approach is that there are a great many things I don't know how to do and this is but one of them. I read that guy's directions but, because I know so little, some of it was over my head. I'm really new at this and I'm also hindered by the fact that I'm a law student; much of this is a hobby for me. So, I absolutely appreciate all of the help from the people on this list because you all know so much more than I do.
Have you run YOU and updated your system with all available patches and bug fixes?
Yeah, I think so. I tried doing a fresh install on my laptop just to see if maybe something I downloaded caused the problem but it wasn't what I though (Ximian Desktop 2). So, as part of the install I performed an online update to get all of the latest patches and bug fixes.
YaST doesn't have ACPI choices at this time. Might in the future. You may have to do several things to get it all working such as: - recompile your kernel with all ACPI functions turned on/enabled. Several aren't by default - learn ACPI hacking to enable all the stuff that the linuxlaptops Compaq Presario 2800T author did one year ago (very detailed instructions) - find a utility that works and does what you want versus the errors you encountered running what was recommended at linuxlaptops - Google for other helpful hints with linux and Compaq Presario 2800T
See above.
Are you using Gnome's GDM (Gnome Display Manager) versus KDE's KDM? Or is that a reference to gpm the mouse driver? If you are using GDM you may want to try switching to KDM to see if there's a difference...
I'm using Gnome's (Ximian's) GDM. After I did the fresh install the system default was kdm and kde, though and the problem existed with those. I guess, if nothing else, I can tough it out until the next SuSE upgrade, where it might, hopefully be fixed. Does anyone know if the 2.6.x kernel has this problem fixed? Thank you everyone for your knowledge and help. Jack