Gentoo Archives: gentoo-user-de

From: rottenbeer <rottenbeer@×××.de>
To: gentoo-user-de@l.g.o
Subject: Re: [gentoo-user-de] Eingabegeräte zerschossen
Date: Mon, 12 Apr 2010 20:25:08
Message-Id: 4BC38192.8070703@web.de
In Reply to: Re: [gentoo-user-de] Eingabegeräte zerschossen by "Pablo.Aleman@t-online.de"
1 On 04/12/2010 10:17 PM, Pablo.Aleman@××××××××.de wrote:
2 >
3 >
4 > -----Original-Nachricht-----
5 > Subject: Re: [gentoo-user-de] Eingabegeräte zerschossen
6 > Date: Mon, 12 Apr 2010 22:09:12 +0200
7 > From: rottenbeer <rottenbeer@×××.de>
8 > To: gentoo-user-de@l.g.o
9 >
10 > On 04/12/2010 09:51 PM, Pablo.Aleman@××××××××.de wrote:
11 >
12 >
13 >
14 > -----Original-Nachricht-----
15 > Subject: Re: [gentoo-user-de] Eingabegeräte zerschossen
16 > Date: Mon, 12 Apr 2010 19:20:57 +0200
17 > From: "Tobias Stein" <tobias-stein@×××.net>
18 > To: gentoo-user-de@l.g.o
19 >
20 > > On 04/12/2010 04:05 PM, Pablo.Aleman@××××××××.de wrote:
21 > > > Hi Ihr alle,
22 > > >
23 > > > der letzte Emerge world wurde leider von der Steckdose beendet.
24 > > > Der nächste Versuch mein System hoch-zufahren klappte recht
25 > > > gut, lediglich meine Eingabegeräte (Maus und Tastatur) sind
26 > tot, das
27 > > > Runterfahren ist auch nur durch die harte Methode. Der
28 > > > Rechner lässt sich gut über andere Betriebssysteme sowohl von der
29 > > > Festplatte wie auch DVD-Laufwerk mit Eingabegeräte bedienen.
30 > > >
31 > > > Weis jemand wie ich mein Gentoo wieder in Ordnung bringen kann?
32 >
33 > Kann es sein das bei deinem Update auch der xorg-server
34 > aktualisiert wurde ?
35 > Dann hast du vlt. einfach nur vergessen erneut alle x11-drivers zu
36 > kompilieren...
37 >
38 > Wird z.B in diversen englischsprachigen Threads im Gentoo Forum
39 > behandelt:
40 > http://forums.gentoo.org/viewtopic-p-6239558.html
41 >
42 >
43 > Einfach beim nächsten Systemstart den interaktiven Bootmodus
44 > wählen und den X Server nicht starten.
45 > Oder eben die Methode über die Live CD wählen.
46 >
47 > Grüße
48 > Tobias Stein
49 >
50 >
51 > --
52 > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
53 > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
54 >
55 >
56 > hi Tobias,
57 > -xorg-server war erst vor 14 Tage dran, eher nicht.
58 > -hier die meldung des Versuches:
59 >
60 >
61 >
62 > (chroot) PartedMagic / # emerge $(qlist -I -C x11-drivers)
63 > * IMPORTANT: 1 news items need reading for repository 'gentoo'.
64 > * Use eselect news to read news items.
65 > Calculating dependencies... done!
66 > >>> Verifying ebuild manifests
67 > >>> Starting parallel fetch
68 > >>> Emerging (1 of 3) x11-drivers/nvidia-drivers-190.42-r3
69 > * NVIDIA-Linux-x86-190.42-pkg0.run RMD160 SHA1 SHA256 size ;-)
70 > ...
71 > [ ok ]
72 > * checking ebuild checksums ;-) ...
73 >
74 > [ ok ]
75 > * checking auxfile checksums ;-) ...
76 >
77 > [ ok ]
78 > * checking miscfile checksums ;-) ...
79 >
80 > [ ok ]
81 > * CPV: x11-drivers/nvidia-drivers-190.42-r3
82 > * REPO: gentoo
83 > * USE: acpi elibc_glibc gtk kernel_linux userland_GNU x86
84 > * Determining the location of the kernel source code
85 > * Found kernel source directory:
86 > * /usr/src/linux
87 > * Could not find a Makefile in the kernel source directory.
88 > * Please ensure that /usr/src/linux points to a complete set of
89 > Linux sources
90 > * Unable to calculate Linux Kernel version for build, attempting
91 > to use running version
92 > * Could not find a usable .config in the kernel source directory.
93 > * Please ensure that /usr/src/linux points to a configured set of
94 > Linux sources.
95 > * If you are using KBUILD_OUTPUT, please set the environment var
96 > so that
97 > * it points to the necessary object directory so that it might
98 > find .config.
99 > * ERROR: x11-drivers/nvidia-drivers-190.42-r3 failed:
100 > * Kernel not configured; no .config found in
101 > *
102 > * Call stack:
103 > * ebuild.sh, line 54: Called pkg_setup
104 > * nvidia-drivers-190.42-r3.ebuild, line 176: Called
105 > linux-mod_pkg_setup
106 > * linux-mod.eclass, line 586: Called
107 > require_configured_kernel
108 > * linux-info.eclass, line 275: Called die
109 > * The specific snippet of code:
110 > * die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
111 > *
112 > * If you need support, post the output of 'emerge --info
113 > =x11-drivers/nvidia-drivers-190.42-r3',
114 > * the complete build log and the output of 'emerge -pqv
115 > =x11-drivers/nvidia-drivers-190.42-r3'.
116 > * The complete build log is located at
117 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'.
118 > * The ebuild environment file is located at
119 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/die.env'.
120 > * S:
121 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86-190.42-pkg0'
122 > >>> Failed to emerge x11-drivers/nvidia-drivers-190.42-r3, Log file:
123 > >>>
124 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'
125 > * Messages for package x11-drivers/nvidia-drivers-190.42-r3:
126 > * Could not find a Makefile in the kernel source directory.
127 > * Please ensure that /usr/src/linux points to a complete set of
128 > Linux sources
129 > * Unable to calculate Linux Kernel version for build, attempting
130 > to use running version
131 > * Could not find a usable .config in the kernel source directory.
132 > * Please ensure that /usr/src/linux points to a configured set of
133 > Linux sources.
134 > * If you are using KBUILD_OUTPUT, please set the environment var
135 > so that
136 > * it points to the necessary object directory so that it might
137 > find .config.
138 > * ERROR: x11-drivers/nvidia-drivers-190.42-r3 failed:
139 > * Kernel not configured; no .config found in
140 > *
141 > * Call stack:
142 > * ebuild.sh, line 54: Called pkg_setup
143 > * nvidia-drivers-190.42-r3.ebuild, line 176: Called
144 > linux-mod_pkg_setup
145 > * linux-mod.eclass, line 586: Called
146 > require_configured_kernel
147 > * linux-info.eclass, line 275: Called die
148 > * The specific snippet of code:
149 > * die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
150 > *
151 > * If you need support, post the output of 'emerge --info
152 > =x11-drivers/nvidia-drivers-190.42-r3',
153 > * the complete build log and the output of 'emerge -pqv
154 > =x11-drivers/nvidia-drivers-190.42-r3'.
155 > * The complete build log is located at
156 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'.
157 > * The ebuild environment file is located at
158 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/die.env'.
159 > * S:
160 > '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86-190.42-pkg0'
161 > * IMPORTANT: 1 news items need reading for repository 'gentoo'.
162 > * Use eselect news to read news items.
163 > (chroot) PartedMagic / #
164 >
165 >
166 > * Please ensure that /usr/src/linux points to a configured set of
167 > Linux sources.
168 >
169 > Bitte sichergehn, dass /usr/src/linux auf deine Kernel Sources zeigt.
170 >
171 > eselect kernel list bzw. eselect kernel set [...] hilft dir dabei.
172 >
173 >
174 >
175 > (chroot) PartedMagic / # eselect kernel list
176 > Available kernel symlink targets:
177 > [1] linux-2.6.31-gentoo-r6 *
178 > [2] linux-2.6.32-gentoo-r7
179 Kann das sein, dass dir beim depclean deine Kernel Sources die du nutzt
180 gelöscht worden sind?
181 Poste mal uname -r

Replies

Subject Author
Re: [gentoo-user-de] Eingabegeräte zerschossen "Pablo.Aleman@××××××××.de" <Pablo.Aleman@××××××××.de>