Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
new install, attempting kde, slot conflict, udev [SOLVED]
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Sun Mar 03, 2013 7:04 pm    Post subject: Reply with quote

Does
Code:
ls -l /usr/lib32/libudev.so
show
Quote:
/usr/lib32/libudev.so -> ../../lib32/libudev.so.0.11.5

_________________
Defund the FCC.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Sun Mar 03, 2013 7:17 pm    Post subject: Reply with quote

BTW, have you run revdep-rebuild ?
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Sun Mar 03, 2013 7:26 pm    Post subject: Reply with quote

Yes, I ran revdep-rebuild, but just the once, when I got all those errors a few posts ago (6:05pm). Was I supposed to run it again?

and yes,

Code:
ls -l /usr/lib32/libudev.so


gives:
Quote:
/usr/lib32/libudev.so -> ../../lib32/libudev.so.0.11.5
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Sun Mar 03, 2013 7:43 pm    Post subject: Reply with quote

on to lib64, shortening:
Code:
 ls -l /usr/lib64/libudev.so

output: /usr/lib64/libudev.so -> ../../lib64/libudev.so.1.2.1
Code:
 ls -l /lib64/libudev.so.1.2.1

output: /lib64/libudev.so.1.2.1
Code:
 ls -l /lib64/libudev.so.1

output: /lib64/libudev.so.1 -> libudev.so.1.2.1
Code:
cat /usr/lib64/pkgconfig/libudev.pc

output: # This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.

prefix=/usr
exec_prefix=/usr
libdir=/usr/lib64
includedir=/usr/include

Name: libudev
Description: Library to access udev device information
Version: 197
Libs: -L${libdir} -ludev -lrt
Libs.private:
Cflags: -I${includedir}

Code:
emerge wgetpaste
revdep-rebuild | wgetpase
emerge --info | wgetpaste
emerge -uND | /und
wgetpaste /und

post url's returned here
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Sun Mar 03, 2013 8:18 pm    Post subject: Reply with quote

Quote:

$ ls -l /usr/lib64/libudev.so
lrwxrwxrwx 1 root root 28 Mar 3 09:36 /usr/lib64/libudev.so -> ../../lib64/libudev.so.1.2.1


Quote:

$ ls -l /lib64/libudev.so.1.2.1
-rwxr-xr-x 1 root root 75632 Mar 3 09:36 /lib64/libudev.so.1.2.1


Quote:

$ ls -l /lib64/libudev.so.1
lrwxrwxrwx 1 root root 16 Mar 3 09:36 /lib64/libudev.so.1 -> libudev.so.1.2.1


Quote:

$ cat /usr/lib64/pkgconfig/libudev.pc
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.

prefix=/usr
exec_prefix=/usr
libdir=/usr/lib64
includedir=/usr/include

Name: libudev
Description: Library to access udev device information
Version: 197
Libs: -L${libdir} -ludev -lrt
Libs.private:
Cflags: -I${includedir}


emerge wgetpaste, went fine.

revdep-rebuild | wgetpaste
--> http://bpaste.net/show/81183/
emerge --info | wgetpaste
--> http://bpaste.net/show/81184/

Code:

emerge -uND | /und

gives:
Quote:

--> bash: /und: No such file or directory

Looks like a typo. emerge -uND only gives a quick help info on emerge usage. Did you mean,
Quote:
emerge -uND world
?

going with that...
emerge -uND world > emundw.out 2>&1
wgetpaste emundw.out
--> http://bpaste.net/show/81188/

Then sorry I have to leave for a bit, will check back about 5 hrs from now. Thanks again.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Sun Mar 03, 2013 8:24 pm    Post subject: Reply with quote

sorry,
Code:
emerge -uND world | /und


not only a typo, as I wanted to get as many build logs as i could as easily as possible I wanted to write
Code:
emerge -uND --keep-going world | /und
wgetpaste /und

_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Mon Mar 04, 2013 1:21 am    Post subject: Reply with quote

Is that a typo again? It looks like you're trying to pipe to another command at /und, but then you're wgetpaste'ing it as if it's the output file. Do you mean redirect to /und, as in,

Code:

emerge -uND --keep-going world > /und
wgetpaste /und
?

going with that, and will post result in a few minutes...
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Mon Mar 04, 2013 1:25 am    Post subject: Reply with quote

typo day, good catch, have seen a hint that this version of libdrm marks an abi change for lidrm-nouveau if there is a dependency chain back to libdrm for the rest of this ... I'm off to switch another machine fron nvidia to nouveau...thiis one is a radeon...switch to nouveau went smoothly, unfortunately-could not duplicate the problem.
Code:
 emerge -s libdrm-nouveau 
should show up as masked and not installed.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Mon Mar 04, 2013 2:11 am    Post subject: Reply with quote

und: http://bpaste.net/show/81242/

emerge -s libdrm-nouveau

-->
Quote:

Searching...
[ Results for search key : libdrm-nouveau ]
[ Applications found : 0 ]
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Mon Mar 04, 2013 3:06 am    Post subject: Reply with quote

what happens if you
Code:
emerge --nodeps  mesa
it appears that libEGL was not linked against the new libudev. libEGL belongs to mesa. So we need to emerge mesa. But mesa depends on libdrm. Which won't emerge because libEGL is not linked to libudev Need to break the circle. If mesa emerges with nodeps try
Code:
 emerge libdrm
emerge mesa
if that happens
Code:
 emerge -uND world
My head hurts 8O
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Mon Mar 04, 2013 4:42 am    Post subject: Reply with quote

on emerge --nodeps mesa, I get:

Quote:

...
checking for XORG... yes
checking for LIBDRM_XORG... yes
checking for LIBKMS_XORG... no
configure: error: Package requirements (libkms >= 1.0.0) were not met:

No package 'libkms' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBKMS_XORG_CFLAGS
and LIBKMS_XORG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1/config.log
* ERROR: media-libs/mesa-9.0.1 failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3502: Called econf '--enable-dri' '--enable-glx' '--disable-texture-float' '--disable-debug' '--enable-egl' '--disable-gbm' '--disable-gles1' '--disable-gles2' '--enable-glx-tls' '--disable-osmesa' '--enable-asm' '--enable-shared-glapi' '--disable-xa' '--enable-xorg' '--with-dri-drivers=,swrast,nouveau' '--with-gallium-drivers=,swrast,nouveau' '--with-egl-platforms=x11' '--enable-gallium-egl' '--disable-gallium-g3dvl' '--enable-gallium-llvm' '--disable-openvg' '--disable-r600-llvm-compiler' '--disable-vdpau' '--disable-xvmc'
* phase-helpers.sh, line 518: Called die
* The specific snippet of code:
* die "econf failed"
*
*
* If you need support, post the output of `emerge --info '=media-libs/mesa-9.0.1'`,
* the complete build log and the output of `emerge -pqv '=media-libs/mesa-9.0.1'`.
* The complete build log is located at '/var/tmp/portage/media-libs/mesa-9.0.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-9.0.1/temp/environment'.
* Working directory: '/var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1'
* S: '/var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1'

>>> Failed to emerge media-libs/mesa-9.0.1, Log file:

>>> '/var/tmp/portage/media-libs/mesa-9.0.1/temp/build.log'
* Messages for package media-libs/mesa-9.0.1:
* ERROR: media-libs/mesa-9.0.1 failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 3502: Called econf '--enable-dri' '--enable-glx' '--disable-texture-float' '--disable-debug' '--enable-egl' '--disable-gbm' '--disable-gles1' '--disable-gles2' '--enable-glx-tls' '--disable-osmesa' '--enable-asm' '--enable-shared-glapi' '--disable-xa' '--enable-xorg' '--with-dri-drivers=,swrast,nouveau' '--with-gallium-drivers=,swrast,nouveau' '--with-egl-platforms=x11' '--enable-gallium-egl' '--disable-gallium-g3dvl' '--enable-gallium-llvm' '--disable-openvg' '--disable-r600-llvm-compiler' '--disable-vdpau' '--disable-xvmc'
* phase-helpers.sh, line 518: Called die
* The specific snippet of code:
* die "econf failed"
*
* If you need support, post the output of `emerge --info '=media-libs/mesa-9.0.1'`,
* the complete build log and the output of `emerge -pqv '=media-libs/mesa-9.0.1'`.
* The complete build log is located at '/var/tmp/portage/media-libs/mesa-9.0.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-9.0.1/temp/environment'.
* Working directory: '/var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1'
* S: '/var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1'
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Mon Mar 04, 2013 5:14 am    Post subject: Reply with quote

Am I dead? Is this heaven?

I never could get Joshua to learn the most important lesson. --Prof. Falkan

Is this where we give up?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Mon Mar 04, 2013 5:31 am    Post subject: Reply with quote

shoot. still looped.
Code:
env-update
source /etc/profile
fix_libtool_files.sh 4.6.3
ldconfig
emerge mesa


after that fails, if ready for bed
Code:
emerge -e --keep-going system


alternate: a new kernel, new make.conf, with nothing fancy just vga or vesafb support, no kms no nouveau, which might get past the loop
_________________
Defund the FCC.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1411

PostPosted: Mon Mar 04, 2013 8:37 pm    Post subject: Reply with quote

Wow, in All my Years(Since 2004.0) this has to be one of the nastiest circular dependency messes ive ever seen. After you wake up, let's see the output of:
Code:
emerge -pv libdrm
emerge gentoolkit
equery hasuse libkms

Add the following to /etc/portage/package.use
x11-libs/libdrm -libkms
(Save)
Continue with:
Code:
emerge mesa
emerge v86d
emerge genkernel
genkernel --menuconfig --clean --mountboot all


In the Drivers section enable:
Userspace linker blah blah <--Should be the first option in Drivers
Under Frame Buffer disable kernel mode setting, nouveau
Disable DRM
Enable uvesa

Under General Options:
Enable RamDisk
Include in ramdisk(/usr/share/v86d/initramfs)
Esc Esc
Save and Compile

Continue:
Code:
emerge nvidia-drivers
eselect opengl set nvidia
reboot


Upon Reboot:
Code:
emerge -e --keep-going system
emerge -e system

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Tue Mar 05, 2013 5:17 pm    Post subject: Reply with quote

donahue:
emerge mesa,
fails at modetest...
--> http://bpaste.net/show/81685/

emerge -e --keep-going system
fails at modetest; total 20 packages failed to build or install
--> http://bpaste.net/show/81613/

eyoung:
emerge -pv libdrm
--> seemed to go okay...

emerge v86d
--> also went fine.

by the way, I used to get the /etc/conf.d/xdm needs to be updated error. Now I get "3 config files in '/etc' need updating." It doesn't say which 3 files.

emerge genkernel
--> all okay.

genkernel --menuconfig --clean --mountboot all
-->
Drivers -> < > Connector - unified userspace <-> kernelspace linker --->
was unselected, so I marked Y/*.
<*> Connector - unified userspace <-> kernelspace linker --->


Quote:
Under Frame Buffer disable kernel mode setting, nouveau

--> Not for sure I've got this right. Couldn't find 'Frame Buffer'. Did search for nouveau, found under
Device Drivers -> Graphics Support -> < > Nouveau (nVidia) cards

This was not checked. I'm sure I had it checked before, but I guess the "genkernel --menuconfig --clean" probably cleaned this out?... Anyway, it's not checked now. Please let me know if I should be looking for something else.

Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) -->
was marked <M>, changed for non-inclusion < >.

oh, I just noticed, Device Drivers -> Graphics Support -> Support for frame buffer devices ---> < > nVidia Framebuffer support.
This is unmarked < >. Is this what you were referring to?

Enable uvesa:
Device Drivers -> Graphics Support -> Support for frame buffer devices ---> < > Userspace VESA VGA graphics support (NEW)

--> marked <*> for inclusion.


Under General Options:
General setup ---> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support

was already marked for inclusion. a search for RamDisk returned no results. Searches for v86d also returned none. A search for initramfs only turned up the above. So I think this is probably what you're looking for.


saving and compiling now.

So, I should move the kernel over to /boot at some point I guess. Just before reboot? Or does genkernel move it for me?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Tue Mar 05, 2013 5:29 pm    Post subject: Reply with quote

ls -l /boot and check new kernel and new initramfs names are in a menu item in /boot/grub/grub.conf
genkernel all does write to /boot
_________________
Defund the FCC.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1411

PostPosted: Tue Mar 05, 2013 5:32 pm    Post subject: Reply with quote

That's perfect, except you'll have to do it again:
Code:
genkernel --menuconfig --clean --mountboot all

Underneath <*>Include RAM Disk Support, is an option that says something like:
Code:
Include Source Files in RAM Disk

By Default it is set to () which implies include nothing. Please fill in the ()'s w/ /usr/share/v86d/initramfs, so that the screen will look like:
Code:
(/usr/share/v86d/initramfs)
(save)

Continue:

If you forget that line, the uvesafb framebuffer driver will not function

To double check my path, please
Code:
ls -al /usr/share/v86d/


You should see initramfs in the listing. If it is incorrect reissue:
Code:
genkernel --menuconfig --clean --mountboot all
and repair

Once this is done, continue with:
Code:
emerge nvidia-drivers
eselect opengl set nvidia


Once this diver is correctly in place we will emerge mesa and libdrm again. If they succeed, we will finish building KDE and then properly install the nouveau and kms drivers
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Tue Mar 05, 2013 6:22 pm    Post subject: Reply with quote

http://wiki.gentoo.org/wiki/Uvesafb is a reasonable explanation of the complications of uvesa
Historically, I have had enough patience and wit to get uvesa to work, to get genkernel to work, but not enough of either to get genkernel and uvesa to work.
If trouble does ensue suggest simple vesafb using a menuconfig like:
Quote:
Device Drivers --->
Graphics support --->
<M> /dev/agpgart (AGP Support) --->
--- /dev/agpgart (AGP Support)
<M> AMD Opteron/Athlon64 on-CPU GART support
< > Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< > SiS chipset support
< > VIA chipset support
-*- VGA Arbitration
(2) Maximum number of GPUs
[ ] Laptop Hybrid Graphics - GPU switching support
< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --
< > Intel GMA500 Stub Driver
<*> Lowlevel video output switch controls
<*> Support for frame buffer devices --->
--- Support for frame buffer devices
[*] Enable firmware EDID
[ ] Framebuffer foreign endianness support --->
[*] Enable Video Mode Handling Helpers
[*] Enable Tile Blitting Support
*** Frame buffer hardware drivers ***
< > Cirrus Logic support
< > Permedia2 support
< > CyberPro 2000/2010/5000 support
< > Arc Monochrome LCD board support
[ ] Asiliant (Chips) 69000 display support
[ ] IMS Twin Turbo display support
< > VGA 16-color graphics support
< > Userspace VESA VGA graphics support
[*] VESA VGA graphics support
[ ] EFI-based Framebuffer Support
< > N411 Apollo/Hecuba devkit support
< > Hercules mono graphics support
< > Epson S1D13XXX framebuffer support
< > nVidia Framebuffer Support
< > nVidia Riva support
< > Intel740 support (EXPERIMENTAL)
< > Intel LE80578 (Vermilion) support
< > Matrox acceleration
< > ATI Radeon display support
< > ATI Rage128 display support
< > ATI Mach64 display support
< > S3 Trio/Virge support
< > S3 Savage support
< > SiS/XGI display support
< > VIA UniChrome (Pro) and Chrome9 display support
< > NeoMagic display support
< > IMG Kyro support
< > 3Dfx Banshee/Voodoo3/Voodoo5 display support
< > 3Dfx Voodoo Graphics (sst1) support
< > VIA VT8623 support
< > Trident/CyberXXX/CyberBlade support
< > ARK 2000PV support
< > Permedia3 support (EXPERIMENTAL)
< > Fujitsu carmine frame buffer support
[ ] AMD Geode family framebuffer support (EXPERIMENTAL)
< > SMSC UFX6000/7000 USB Framebuffer support
< > Displaylink USB Framebuffer support
< > Virtual Frame Buffer support (ONLY FOR TESTING!)
< > E-Ink Metronome/8track controller support
< > Fujitsu MB862xx GDC support
< > E-Ink Broadsheet/Epson S1D13521 controller support
< > AUO-K190X EPD controller suppor
[ ] Exynos Video driver support --->
[*] Backlight & LCD device support --->
--- Backlight & LCD device support
<*> Lowlevel LCD controls
< > Platform LCD controls
<*> Lowlevel Backlight controls
< > Generic (aka Sharp Corgi) Backlight Driver
< > Apple Backlight Driver
< > Tabletkiosk Sahara Touch-iT Backlight Driver
< > Backlight Driver for ADP8860/ADP8861/ADP8863 using WLED
< > Backlight Driver for ADP8870 using WLED
< > Backlight Driver for LM3630
< > Backlight Driver for LM3639
< > Backlight driver for TI LP855X
Console display driver support --->
-*- VGA text console
[*] Enable Scrollback Buffer in System RAM
(256) Scrollback Buffer Size (in KB)
<*> Framebuffer Console support
[*] Map the console to the primary display device
[ ] Framebuffer Console Rotation
[ ] Select compiled-in fonts
[*] Bootup logo --->
--- Bootup logo
[ ] Standard black and white Linux logo
[ ] Standard 16-color Linux logo
[*] Standard 224-color Linux logo

_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Tue Mar 05, 2013 6:48 pm    Post subject: Reply with quote

okay, adding this to /boot/grub/grub.conf:
Code:

title Gentoo Linux genkernel 3.7.9, with initramfs
root (hd0,0)
kernel /boot/kernel-genkernel-x86_64-3.7.9-gentoo root=/dev/sda3
initrd /boot/initramfs-genkernel-x86_64-3.7.9-gentoo

Am I supposed to re-install grub now, via running "grub --no-floppy"?

Yeah, that makes sense now e, I've now put (/usr/share/v86d/initramfs) as ramfs source files.

continuing with:
Code:

emerge nvidia-drivers

emerge nvidia-drivers --> Failed.
Quote:

>>> Source configured.
>>> Compiling source in /var/tmp/portage/x11-drivers/nvidia-drivers-310.32/work ...
* Preparing nvidia module
make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' ARCH=x86_64 IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.7.9-gentoo/build CC=x86_64-pc-linux-gnu-gcc clean module
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1
* ERROR: x11-drivers/nvidia-drivers-310.32 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-310.32'`,
* the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-310.32'`.
* The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-310.32/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-310.32/temp/environment'.
* Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-310.32/work/kernel'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-310.32/work/'

complete output: http://bpaste.net/show/81655/

stopping here. Do I need a more complete genkernel setup?[/code]
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1411

PostPosted: Tue Mar 05, 2013 7:09 pm    Post subject: Reply with quote

From your log:
Quote:
* Gentoo supports kernel's which are supported by NVIDIA
* which are limited to the following kernels:
* <sys-kernel/gentoo-sources-3.7
* <sys-kernel/vanilla-sources-3.7


Edit /etc/portage/package.mask. Add:
>sys-kernel/gentoo-sources-3.6.11-r1

Redo:
Code:
genkernel --menuconfig --clean --mountboot all


I apologize for having to do this, but since we masked 3.7.x we need to redo it. And yes, I'll answer you as to why we are doing this. We need a functioning graphics platform in order to rebuild it the way you want it, and for nvidia nouveau and nvidia-drivers are the only 2 options.
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6648
Location: Goose Creek SC

PostPosted: Tue Mar 05, 2013 7:39 pm    Post subject: Reply with quote

simpler
if
Quote:
x11-drivers/nvidia-drivers ~amd64
is inserted in /etc/portage/package.keywords
Code:
emerge nvidia
will bring in version 313 which supports kernels < 3.8
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Tue Mar 05, 2013 7:56 pm    Post subject: Reply with quote

okay, tried inserting " x11-drivers/nvidia-drivers ~amd64 " into /etc/portage/package.keywords and then emerge'ing nvidia-drivers, and got the same errors as before.

So, removing /etc/portage/package.keywords and trying:

/etc/portage/package.mask: >sys-kernel/gentoo-sources-3.6.11-r1

and choosing the same options as a few posts ago.
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Tue Mar 05, 2013 8:53 pm    Post subject: Reply with quote

Looks like I might have missed some things from eyoung's earlier post.

I must have missed the 'equery hasuse libkms' line. Doing now, and it returns 'x11-libs/libdrm-2.4.40'

Also trying emerge mesa, --> failed on modetest.
I also noticed it's building nouveau still. I guess this is from my /etc/portage/make.conf:
VIDEO_CARDS="nouveau"
INPUT_DEVICES="evdev"

Do these need to be removed/edited?


emerge nvidia-drivers also failed.
Quote:

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1
* ERROR: x11-drivers/nvidia-drivers-313.18 failed (compile phase):
* emake failed

complete output: http://bpaste.net/show/81704/

oh, and yeah, initramfs is in /usr/share/v86d/.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1411

PostPosted: Tue Mar 05, 2013 9:06 pm    Post subject: Reply with quote

Jblue wrote:
Looks like I might have missed some things from eyoung's earlier post.

I must have missed the 'equery hasuse libkms' line. Doing now, and it returns 'x11-libs/libdrm-2.4.40'

Also trying emerge mesa, --> failed on modetest.
I also noticed it's building nouveau still. I guess this is from my /etc/portage/make.conf:
VIDEO_CARDS="nouveau"
INPUT_DEVICES="evdev"

Do these need to be removed/edited?


emerge nvidia-drivers also failed.
Quote:

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1
* ERROR: x11-drivers/nvidia-drivers-313.18 failed (compile phase):
* emake failed

complete output: http://bpaste.net/show/81704/

oh, and yeah, initramfs is in /usr/share/v86d/.

Change to:

Code:
VIDEO_CARDS="nvidia nv"


Target Version will be wrong until you issue:
Code:
nano -w /etc/portage/package.use
x11-libs/libdrm   -libkms <--This will Fix what you missed.
(Save)
reboot


After reboot:
Code:
emerge nvidia-drivers
nvidia-xconfig

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
Jblue
n00b
n00b


Joined: 28 Feb 2013
Posts: 35

PostPosted: Tue Mar 05, 2013 10:20 pm    Post subject: Reply with quote

/etc/portage/make.conf changed to: VIDEO_CARDS="nvidia nv"

/etc/portage/package.use already had:
Quote:

x11-base/xorg-server udev


changing to:
Quote:

x11-base/xorg-server udev x11-libs/libdrm -libkms


and rebooting...

booting up with genkernel kernel, initramfs,
...seemed to go okay.

emerge nvidia-drivers failed, errors look identical to before. Complete output: http://bpaste.net/81733/
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page Previous  1, 2, 3  Next
Page 2 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum