On Saturday 25 June 2011 17:36:17 Alan Mackenzie wrote: > Good evening, Volker! > > On Sat, Jun 25, 2011 at 02:01:50PM +0200, Volker Armin Hemmann wrote: > > 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, <[email protected]> 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. > > Hmmm. Yes. The problem is not so much the reading, but that the > pertinent text is only fleetingly on the screen. I'm quite sure I saw > these warnings, but their seriousness didn't impinge on my consciousness. > Sadly. > > Are these warnings stored in a log anywhere? Looking for them in ebuilds > before emerging would be a bit tedious. > > Or maybe it needs a script which would take the output of "emerge -puND > world", extract the ebuild names, and run them through "grep ewarn". Or > does such already exist?
those warnings ARE stored. For the ultra lazy way: PORTAGE_ELOG_CLASSES="warn error log" PORTAGE_ELOG_SYSTEM="mail save" PORTAGE_ELOG_MAILURI="root@localhost /usr/sbin/sendmail" PORTAGE_ELOG_MAILFROM="portage@localhost" and then have the stuff dumped in your mailbox. -- #163933
