public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] no keyboard no mouse
Date: Sat, 25 Jun 2011 14:01:50 +0200	[thread overview]
Message-ID: <8135889.K81uB0G1ml@localhost> (raw)
In-Reply-To: <20110624114348.GA7217@acm.acm>

On Friday 24 June 2011 11:43:48 Alan Mackenzie wrote:
> Hi, Adam.
> 
> On Fri, Jun 24, 2011 at 06:59:42PM +1000, Adam Carter wrote:
> > On Fri, Jun 24, 2011 at 6:47 PM,  <alain.didierjean@free.fr> wrote:
> > > After upgrading xcb, ati driver and rebooting xorg can't read mouse
> > > and keyboard anymore. No more access to the system besides booting
> > > an unbuntu livecd. According to /var/log/Xorg.0.log, evdev cant't
> > > be loaded any more (see below). What can I do ? Is there an upgrade
> > > to evdev ?
> > 
> > No you just need to rebuild it, so emerge xf86-input-evdev
> 
> This problem hit me too.  Can you give us an explanation for needing to
> rebuild evdev?  Was there some missing dependency in an ebuild, or
> something?


from xorg-server ebuild:

                elog "You should consider reading upgrade guide for this 
release:"
                elog "  http://www.gentoo.org/proj/en/desktop/x/x11/xorg-
server-$(get_version_component_range 1-2)-upgrade-guide.xml"
                echo
                ewarn "You must rebuild all drivers if upgrading from <xorg-
server-$(get_version_component_range 1-2)"
                ewarn "because the ABI changed. If you cannot start X because"
                ewarn "of module version mismatch errors, this is your 
problem."

                echo
                ewarn "You can generate a list of all installed packages in 
the x11-drivers"
                ewarn "category using this command:"
                ewarn " emerge portage-utils; qlist -I -C x11-drivers/"
                ewarn "or using sets from portage-2.2:"
                ewarn " emerge @x11-module-rebuild"
        fi


people. learn to read.

-- 
#163933



  parent reply	other threads:[~2011-06-25 12:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  8:47 [gentoo-user] no keyboard no mouse alain.didierjean
2011-06-24  8:59 ` Sebastian Beßler
2011-06-24  8:59 ` Adam Carter
2011-06-24 11:43   ` Alan Mackenzie
2011-06-24 12:03     ` Dale
2011-06-24 12:07     ` Adam Carter
2011-06-24 14:42       ` Alan Mackenzie
2011-06-24 14:57         ` Alan McKinnon
2011-06-25  9:50           ` Alan Mackenzie
2011-06-25 18:53             ` Alan McKinnon
2011-06-25 12:01     ` Volker Armin Hemmann [this message]
2011-06-25 17:36       ` Alan Mackenzie
2011-06-25 17:48         ` Dale
2011-06-25 20:23         ` Volker Armin Hemmann
2011-06-24  9:05 ` Matthew Finkel
2011-06-24  9:34   ` Neil Bothwick
2011-06-24 13:36     ` Mick
     [not found] <658292104.5336901308919354379.JavaMail.root@spooler5n-g27.priv.proxad.net>
2011-06-24 12:43 ` Alain DIDIERJEAN
2011-06-24 12:53   ` Adam Carter
2011-06-26  6:08     ` Jonathan
2011-06-26  6:34       ` Alain DIDIERJEAN
2011-06-26  7:38         ` Jonathan
2011-06-24 22:00   ` Neil Bothwick
2011-06-24 22:22     ` Dale
2011-06-25  4:31     ` Pandu Poluan
2011-06-25  6:52       ` Alan McKinnon
2011-06-25  7:37     ` Alain DIDIERJEAN
2011-06-25 11:50       ` Neil Bothwick

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=8135889.K81uB0G1ml@localhost \
    --to=volkerarmin@googlemail.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