Hemmann, Volker Armin wrote:
On Sunday 29 October 2006 03:32, sean wrote:
I received the following error running emerge --newuse world.
Would anyone be able to explain and advise on how to cure?
I was seeing this error recently, even before my recent upgrade of gcc.
emerge --newuse world
>>> --newuse implies --update... adding --update to options.
Calculating world dependencies /
emerge: there are no ebuilds to satisfy "media-video/nvidia-glx".
(dependency required by "media-libs/smpeg-0.4.4-r8" [ebuild])
emerge nvidia-driver and retry.
Well as you said I emerged nvidia-driver and that has now killed X for
me. Tried following the Gentoo nvidia guide again, but unable to get X
up again.
Things I have noticed.
1) In Dmesg Linux version lists 'Linux version 2.6.16-gentoo-r9' and
(gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
Since I just upgraded GCC to 4 should this be GCC 4 now, does this mean
the kernel needs to be compiled again?
2) Also in Dmesg 'nvidia: version magic '2.6.16-gentoo-r9 SMP gcc-4.1'
should be '2.6.16-gentoo-r9 SMP gcc-3.4'
This line starts popping up several times during the rest of Dmesg.
3) emerge --update --deep --newuse --world;revdep-rebuild;revdep-rebuild
keeps stating similar to what I wrote originally up above
emerge: there are no ebuilds to satisfy "media-video/nvidia-glx".
(dependency required by "media-libs/libsdl-1.2.11" [ebuild)
NOTE: There is no nvidia-glx in portage.
4) Startx fails with the following
FATAL: Error inserting nvidia
(lib/modules/2.6.16-gentoo-r9/video/nvidia.ko): Invalid module format
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usuable configuration.
Fatal server error:
no screen found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
NOTE: I have not changed my xorg.conf.
Thanks for any help,
Sean
--
gentoo-amd64@gentoo.org mailing list
