1 |
Good evening, Volker! |
2 |
|
3 |
On Sat, Jun 25, 2011 at 02:01:50PM +0200, Volker Armin Hemmann wrote: |
4 |
> On Friday 24 June 2011 11:43:48 Alan Mackenzie wrote: |
5 |
> > Hi, Adam. |
6 |
|
7 |
> > On Fri, Jun 24, 2011 at 06:59:42PM +1000, Adam Carter wrote: |
8 |
> > > On Fri, Jun 24, 2011 at 6:47 PM, <alain.didierjean@××××.fr> wrote: |
9 |
> > > > After upgrading xcb, ati driver and rebooting xorg can't read |
10 |
> > > > mouse and keyboard anymore. No more access to the system besides |
11 |
> > > > booting an unbuntu livecd. According to /var/log/Xorg.0.log, |
12 |
> > > > evdev cant't be loaded any more (see below). What can I do ? Is |
13 |
> > > > there an upgrade to evdev ? |
14 |
|
15 |
> > > No you just need to rebuild it, so emerge xf86-input-evdev |
16 |
|
17 |
> > This problem hit me too. Can you give us an explanation for needing |
18 |
> > to rebuild evdev? Was there some missing dependency in an ebuild, or |
19 |
> > something? |
20 |
|
21 |
|
22 |
> from xorg-server ebuild: |
23 |
|
24 |
> elog "You should consider reading upgrade guide for this |
25 |
> release:" |
26 |
> elog " http://www.gentoo.org/proj/en/desktop/x/x11/xorg- |
27 |
> server-$(get_version_component_range 1-2)-upgrade-guide.xml" |
28 |
> echo |
29 |
> ewarn "You must rebuild all drivers if upgrading from <xorg- |
30 |
> server-$(get_version_component_range 1-2)" |
31 |
> ewarn "because the ABI changed. If you cannot start X because" |
32 |
> ewarn "of module version mismatch errors, this is your |
33 |
> problem." |
34 |
|
35 |
> echo |
36 |
> ewarn "You can generate a list of all installed packages in |
37 |
> the x11-drivers" |
38 |
> ewarn "category using this command:" |
39 |
> ewarn " emerge portage-utils; qlist -I -C x11-drivers/" |
40 |
> ewarn "or using sets from portage-2.2:" |
41 |
> ewarn " emerge @x11-module-rebuild" |
42 |
> fi |
43 |
|
44 |
|
45 |
> people. learn to read. |
46 |
|
47 |
Hmmm. Yes. The problem is not so much the reading, but that the |
48 |
pertinent text is only fleetingly on the screen. I'm quite sure I saw |
49 |
these warnings, but their seriousness didn't impinge on my consciousness. |
50 |
Sadly. |
51 |
|
52 |
Are these warnings stored in a log anywhere? Looking for them in ebuilds |
53 |
before emerging would be a bit tedious. |
54 |
|
55 |
Or maybe it needs a script which would take the output of "emerge -puND |
56 |
world", extract the ebuild names, and run them through "grep ewarn". Or |
57 |
does such already exist? |
58 |
|
59 |
> -- |
60 |
> #163933 |
61 |
|
62 |
-- |
63 |
Alan Mackenzie (Nuremberg, Germany). |