IIRC, you can use ALT+PRNT+K to kill/restart X; I know it works for
Ubuntu, but I think they were going to make that standard.  Also, I
believe there is a file located somewhere that defines which modules
need to be started on suspend resume, but I can't remember where it's
located.

2011/1/8 Matthew Gardner <[email protected]>:
> On Sat, Jan 8, 2011 at 2:35 PM, RT Hatfield <[email protected]> wrote:
>>
>> I'm no expert, but it sounds to me like X is thinking it has to drop the
>> driver after a power state transition.  I think the easiest way to get the
>> mouse driver working again is to straight-up restart X.  That's probably
>> gonna be no fun for you, so make sure your files are all up to date and
>> google to see if this is a known issue (no idea how many people run Fedora
>> on mb airs, so it might not be).  That's all I've got.  Best bet is asking
>> someone who's an expert on configuring X.
>
> Hmm...  Now that I think about it, the problem seems to be in X, you're
> right.  But when I restart X (just killing the Xorg process from a terminal,
> because ctrl-alt-backspace for some reason doesn't work), the mouse still
> doesn't work.  I had thought of what you suggested, and I tried it, to no
> avail.  So that doesn't give me much hope...  Any other ideas?
>
> --------------------
> BYU Unix Users Group
> http://uug.byu.edu/
>
> The opinions expressed in this message are the responsibility of their
> author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
> ___________________________________________________________________
> List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
>



-- 
Dallin Terry
--------------------
BYU Unix Users Group 
http://uug.byu.edu/ 

The opinions expressed in this message are the responsibility of their
author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG. 
___________________________________________________________________
List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list

Reply via email to