From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure
Date: Fri, 23 Dec 2011 07:55:26 -0500 [thread overview]
Message-ID: <CA+czFiCqyZve9oKA5+iOtzS_6+mfbj8jkoXxcrLSb06nX3YpnQ@mail.gmail.com> (raw)
In-Reply-To: <4EF415B1.4080100@gmail.com>
On Fri, Dec 23, 2011 at 12:46 AM, Dale <rdalek1967@gmail.com> wrote:
> Michael Mol wrote:
>> On Thu, Dec 22, 2011 at 7:58 AM, Alex Schuster<wonko@wonkology.org>
>> wrote:
>>> G.Wolfe Woodbury writes:
>>>> On 12/22/2011 02:00 AM, Pintér Tibor wrote:
>>>>> Reemerge all xf86* packages
>>>>> Quite obvious as the log clearly gives the clue (new xorg server
>>>>> version, driver version mismatch)
>>>>
>>>> I looked right at it and missed the obvious! Thanks for the
>>>> clue-by-four.
>>>
>>> BTW, emerge -a @x11-module-rebuild will do this.
>>>
>>> Wonko
>>>
>> emerge: There are no sets to satisfy 'x11-module-rebuild'. The
>> following sets exist:
>>
>> selected
>> system
>> world
>>
>
> Someone posted this one liner a while back:
>
> emerge -1a $(qlist -I -C x11-drivers/)
>
> That takes care of the video driver, mouse, keyboard and such. Mine is
> these packages:
>
> root@fireball / # qlist -I -C x11-drivers/
> x11-drivers/nvidia-drivers
> x11-drivers/xf86-input-evdev
> x11-drivers/xf86-video-nv
> x11-drivers/xf86-video-vesa
> root@fireball / #
I wound up doing something similar, involving a mix of eix, grep and sed.
>
> I try to remember to run that when I upgrade the kernel or xorg. I usually
> forget and have to do the SysReq keystroke magic. After I slap my forehead
> of course.
I still don't know the SysReq magic. I've just ssh'd in. If I can't do
that, it usually means something hardlocked.
>
> There are quite a few of these commands that gets posted from time to time.
> As a hint, I have a text file in my /root directory that contains the
> commands and a description. I just cat and grep the file when I need to. I
> wouldn't recommend a user directory tho. If for someone reason only root is
> mounted, then you can get to /root but not /home if it is a separate
> partition. You, and other Gentooers, may want to think about doing
> something like this.
>
> Hope this helps in some small way.
Funny thing is, I thought I'd taken care of it. It didn't crop up for
me until xscreensaver kicked in, which crashed X due to differeing ABI
versions between what was already running and what xscreensaver tried
to get linked in. Guess I should remember to restart X. :)
--
:wq
next prev parent reply other threads:[~2011-12-23 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 7:00 [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure Pintér Tibor
2011-12-22 8:02 ` G.Wolfe Woodbury
2011-12-22 12:58 ` Alex Schuster
2011-12-23 5:12 ` Michael Mol
2011-12-23 5:46 ` Dale
2011-12-23 12:55 ` Michael Mol [this message]
2011-12-23 14:02 ` Dale
2011-12-23 10:38 ` Mick
2011-12-23 12:57 ` Michael Mol
2011-12-23 14:05 ` Dale
2011-12-23 14:38 ` Michael Mol
2011-12-23 23:17 ` Dale
2011-12-23 23:47 ` Neil Bothwick
2011-12-25 2:56 ` Stroller
-- strict thread matches above, loose matches on Subject: below --
2011-12-22 6:16 G.Wolfe Woodbury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+czFiCqyZve9oKA5+iOtzS_6+mfbj8jkoXxcrLSb06nX3YpnQ@mail.gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox