On Thu, Jul 13, 2006 at 07:21:06AM -0400, [EMAIL PROTECTED] wrote: > On Wed, Jul 12, 2006 at 09:43:55PM -0500, Jaime Ochoa Malag?n wrote: > > An importat thing about havig ssh acces is the problem is not wqith > > the machine is with your applications, try vesa X driver... > > > > You could have only a unstable X... > > I'm currently running the vesa X driver. Previously I had the problem > with the nvidia X drivers. > > The problem shows up as dead mouse pointer. Which maked X pretty > useless. But if the system is in a state where it might expect keyboard > input, it continues to react to the keyboard. I can continue to enter a > URL into firefox (though it won't load a new one when I press enter), > and the tab key allows me to change panes in firefox -- tab between ads, > images, and so forth. However, the ctrl-alt-F* keys no longer work. > > In fact, the specificity of the problem suggests that it is probably not > a RAM problem at all. But it doesn't rule out other hardware, such as > maybe the mouse itself, or the USB controller the mouse plugs into.
And it doesn't seem to be a problem with 64-bit cleanlines or with leftovers from tortuous upgrades. I installed 32-bit etch on a spare partition, with the same failures. It might be hardware, but probably not RAM. It might be a device-driver for one of the new nvidia chips on the AMD-64 motherboard (the reason why I'm using etch instead of stable). Still no idea how to track this down. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
