From: rottenbeer <rottenbeer@web.de>
To: gentoo-user-de@lists.gentoo.org
Subject: Re: [gentoo-user-de] Eingabegeräte zerschossen
Date: Mon, 12 Apr 2010 22:09:12 +0200 [thread overview]
Message-ID: <4BC37DE8.1020504@web.de> (raw)
In-Reply-To: <1O1PfJ-1GsYoi0@fwd06.aul.t-online.de>
[-- Attachment #1: Type: text/plain, Size: 6717 bytes --]
On 04/12/2010 09:51 PM, Pablo.Aleman@t-online.de wrote:
>
>
> -----Original-Nachricht-----
> Subject: Re: [gentoo-user-de] Eingabegeräte zerschossen
> Date: Mon, 12 Apr 2010 19:20:57 +0200
> From: "Tobias Stein" <tobias-stein@gmx.net>
> To: gentoo-user-de@lists.gentoo.org
>
> > On 04/12/2010 04:05 PM, Pablo.Aleman@t-online.de wrote:
> > > Hi Ihr alle,
> > >
> > > der letzte Emerge world wurde leider von der Steckdose beendet.
> > > Der nächste Versuch mein System hoch-zufahren klappte recht
> > > gut, lediglich meine Eingabegeräte (Maus und Tastatur) sind tot, das
> > > Runterfahren ist auch nur durch die harte Methode. Der
> > > Rechner lässt sich gut über andere Betriebssysteme sowohl von der
> > > Festplatte wie auch DVD-Laufwerk mit Eingabegeräte bedienen.
> > >
> > > Weis jemand wie ich mein Gentoo wieder in Ordnung bringen kann?
>
> Kann es sein das bei deinem Update auch der xorg-server aktualisiert
> wurde ?
> Dann hast du vlt. einfach nur vergessen erneut alle x11-drivers zu
> kompilieren...
>
> Wird z.B in diversen englischsprachigen Threads im Gentoo Forum behandelt:
> http://forums.gentoo.org/viewtopic-p-6239558.html
>
>
> Einfach beim nächsten Systemstart den interaktiven Bootmodus wählen
> und den X Server nicht starten.
> Oder eben die Methode über die Live CD wählen.
>
> Grüße
> Tobias Stein
>
>
> --
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>
>
> hi Tobias,
> -xorg-server war erst vor 14 Tage dran, eher nicht.
> -hier die meldung des Versuches:
>
>
>
> (chroot) PartedMagic / # emerge $(qlist -I -C x11-drivers)
> * IMPORTANT: 1 news items need reading for repository 'gentoo'.
> * Use eselect news to read news items.
> Calculating dependencies... done!
> >>> Verifying ebuild manifests
> >>> Starting parallel fetch
> >>> Emerging (1 of 3) x11-drivers/nvidia-drivers-190.42-r3
> * NVIDIA-Linux-x86-190.42-pkg0.run RMD160 SHA1 SHA256 size ;-) ...
> [ ok ]
> * checking ebuild checksums ;-) ...
> [ ok ]
> * checking auxfile checksums ;-) ...
> [ ok ]
> * checking miscfile checksums ;-) ...
> [ ok ]
> * CPV: x11-drivers/nvidia-drivers-190.42-r3
> * REPO: gentoo
> * USE: acpi elibc_glibc gtk kernel_linux userland_GNU x86
> * Determining the location of the kernel source code
> * Found kernel source directory:
> * /usr/src/linux
> * Could not find a Makefile in the kernel source directory.
> * Please ensure that /usr/src/linux points to a complete set of Linux
> sources
> * Unable to calculate Linux Kernel version for build, attempting to
> use running version
> * Could not find a usable .config in the kernel source directory.
> * Please ensure that /usr/src/linux points to a configured set of
> Linux sources.
> * If you are using KBUILD_OUTPUT, please set the environment var so that
> * it points to the necessary object directory so that it might find
> .config.
> * ERROR: x11-drivers/nvidia-drivers-190.42-r3 failed:
> * Kernel not configured; no .config found in
> *
> * Call stack:
> * ebuild.sh, line 54: Called pkg_setup
> * nvidia-drivers-190.42-r3.ebuild, line 176: Called
> linux-mod_pkg_setup
> * linux-mod.eclass, line 586: Called
> require_configured_kernel
> * linux-info.eclass, line 275: Called die
> * The specific snippet of code:
> * die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
> *
> * If you need support, post the output of 'emerge --info
> =x11-drivers/nvidia-drivers-190.42-r3',
> * the complete build log and the output of 'emerge -pqv
> =x11-drivers/nvidia-drivers-190.42-r3'.
> * The complete build log is located at
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/die.env'.
> * S:
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86-190.42-pkg0'
> >>> Failed to emerge x11-drivers/nvidia-drivers-190.42-r3, Log file:
> >>>
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'
> * Messages for package x11-drivers/nvidia-drivers-190.42-r3:
> * Could not find a Makefile in the kernel source directory.
> * Please ensure that /usr/src/linux points to a complete set of Linux
> sources
> * Unable to calculate Linux Kernel version for build, attempting to
> use running version
> * Could not find a usable .config in the kernel source directory.
> * Please ensure that /usr/src/linux points to a configured set of
> Linux sources.
> * If you are using KBUILD_OUTPUT, please set the environment var so that
> * it points to the necessary object directory so that it might find
> .config.
> * ERROR: x11-drivers/nvidia-drivers-190.42-r3 failed:
> * Kernel not configured; no .config found in
> *
> * Call stack:
> * ebuild.sh, line 54: Called pkg_setup
> * nvidia-drivers-190.42-r3.ebuild, line 176: Called
> linux-mod_pkg_setup
> * linux-mod.eclass, line 586: Called
> require_configured_kernel
> * linux-info.eclass, line 275: Called die
> * The specific snippet of code:
> * die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
> *
> * If you need support, post the output of 'emerge --info
> =x11-drivers/nvidia-drivers-190.42-r3',
> * the complete build log and the output of 'emerge -pqv
> =x11-drivers/nvidia-drivers-190.42-r3'.
> * The complete build log is located at
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/temp/die.env'.
> * S:
> '/var/tmp/portage/x11-drivers/nvidia-drivers-190.42-r3/work/NVIDIA-Linux-x86-190.42-pkg0'
> * IMPORTANT: 1 news items need reading for repository 'gentoo'.
> * Use eselect news to read news items.
> (chroot) PartedMagic / #
>
* Please ensure that /usr/src/linux points to a configured set of Linux
sources.
Bitte sichergehn, dass /usr/src/linux auf deine Kernel Sources zeigt.
eselect kernel list bzw. eselect kernel set [...] hilft dir dabei.
[-- Attachment #2: Type: text/html, Size: 10205 bytes --]
next prev parent reply other threads:[~2010-04-12 20:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 11:48 [gentoo-user-de] bash und "return -1" Juergen Rose
2010-04-10 20:45 ` Alex Schuster
2010-04-10 22:33 ` Juergen Rose
2010-04-12 14:05 ` [gentoo-user-de] Eingabegeräte zerschossen Pablo.Aleman
2010-04-12 15:23 ` rottenbeer
2010-04-12 17:20 ` Tobias Stein
2010-04-12 19:51 ` Pablo.Aleman
2010-04-12 20:09 ` rottenbeer [this message]
2010-04-12 20:17 ` Pablo.Aleman
2010-04-12 20:24 ` rottenbeer
2010-04-12 20:31 ` Pablo.Aleman
2010-04-12 20:39 ` rottenbeer
2010-04-12 20:56 ` Pablo.Aleman
2010-04-15 16:14 ` Pablo.Aleman
2010-04-15 17:43 ` rottenbeer
2010-04-15 17:54 ` Pablo.Aleman
2010-04-15 18:06 ` rottenbeer
2010-04-15 18:07 ` Roland Damm
2010-04-15 19:26 ` [gentoo-user-de] Eingabegeräte zerschossen [SOLVED] Pablo Alemán
2010-04-15 19:38 ` asdf asdf
2010-04-15 20:17 ` Pablo Alemán
2010-04-15 20:23 ` Pablo Alemán
2010-04-15 20:29 ` rottenbeer
2010-04-15 20:39 ` Roland Damm
2010-04-15 20:57 ` Daniel Pielmeier
2010-04-15 20:44 ` Pablo Alemán
2010-04-12 19:08 ` [gentoo-user-de] Eingabegeräte zerschossen Pablo.Aleman
2010-04-12 19:24 ` rottenbeer
2010-04-12 19:40 ` Pablo.Aleman
2010-04-12 19:45 ` rottenbeer
2010-04-12 19:47 ` Christoph Scheurer
2010-04-12 19:54 ` Pablo.Aleman
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=4BC37DE8.1020504@web.de \
--to=rottenbeer@web.de \
--cc=gentoo-user-de@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