| View previous topic :: View next topic |
| Author |
Message |
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
 Posted: Fri Mar 01, 2013 8:35 pm Post subject: new install, attempting kde, slot conflict, udev [SOLVED] |
 |
|
I'm new to gentoo, have completed the basic install and am attempting to get kde functional. I'm running into a few errors, possibly related, that I've noted here. Any help would be much appreciated.
Following http://wiki.gentoo.org/wiki/KDE
I did get startx to work properly (see http://wiki.gentoo.org/wiki/X_server , or better, http://www.gentoo.org/doc/en/xorg-config.xml)
Going back to:
http://wiki.gentoo.org/wiki/KDE
which takes me to: http://wiki.gentoo.org/wiki/Display_manager
rc-update add xdm default
/etc/init.d/xdm start
ERROR: Please set your DISPLAYMANAGER variable in /etc/conf.d/xdm,
or install x11-apps/xdm package
* Setting up xdm ...
* start-stop-daeon: /usr/bin/xdm does not exist
* ERROR: could not start the Display Manager
It IS set in /etc/conf.d/xdm. DISPLAYMANAGER="kdm"
Also, whenever I emerge something, I get this error:
* IMPORTANT: config file '/etc/conf.d/xdm' needs updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
Also, when I do emerge --changed-use --deep @world, I get this error:
Multiple package instances within a single pachage slot have been pulled into the dep graph, resulting in a
slot conflict: virtual/udev:0
(virtual/udev-171::gentoo, installed) pulled in by
=virtual/udev-171 required by (sys-auth/consolekit-0.4.5_p20120320-r1::gentoo, installed)
(and 7 more with the same problem)
(virtual/udev-197-r1::gentoo,ebuild scheduled for merge) pulled in by
>=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)
sys-fs/udev:0
(sys-fs/udev-171-r10::gentoo,installed) pulled in by
~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?] required by (virtual/udev-171::gentoo,installed)
(sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?] required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
It may be possible....package.mask...
I'm only trying to install a basic kde, so I don't expect I would have to do anything fancy like set up a package mask. But I could be wrong.
My profile is set to [5] default/linux/amd64/13.0/desktop/kde
/etc/portage/make.conf:
USE="bindist mmx sse sse2 X dbus kde_meta consolekit policykit udev udisks bzip2 ipv6 truetype nptl suid xorg"
Any help on any of these probs would be excellent. Thanks very much.
Jack
Last edited by Jblue on Thu Mar 07, 2013 8:18 pm; edited 1 time in total |
|
| Back to top |
|
 |
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Fri Mar 01, 2013 9:43 pm Post subject: |
|
|
what is the output of:
| Code: | | cat /etc/conf.d/xdm |
| The X Server Configuration HOWTO wrote: | Using startx
Now try startx to start up your X server. startx is a script that executes an X session; that is, it starts the X server and some graphical applications on top of it. It decides which applications to run using the following logic:
If a file named .xinitrc exists in the home directory, it will execute the commands listed there.
Otherwise, it will read the value of the XSESSION variable and will execute one of the sessions available in /etc/X11/Sessions/ accordingly. You can set the value of XSESSION in /etc/env.d/90xsession to make it a default for all the users on the system. For example, as root, run echo XSESSION="Xfce4" > /etc/env.d/90xsession. This will create the 90xsession file and set the default X session to Xfce. Remember to run env-update after changing 90xsession. |
Is XSESSION set to KDE-4??
| Code: | | #echo XSESSION="KDE-4" > /etc/env.d/90xsession |
_________________
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 |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Fri Mar 01, 2013 10:35 pm Post subject: |
|
|
Thanks eyoung for your response.
/etc/conf.d/xdm: DISPLAYMANAGER="kdm"
XSESSION was set to 'kde'. The gentoo/kde guide only gave Xfce4 as an option, so I didn't know exactly how to call kde, and I had 'kde'. So I fixed this to KDE-4, env-update'ed and rebooted.
Now, echo $XSESSION yields KDE-4.
Still, when I do "/etc/init.d/xdm start" I get the same error,
ERROR: Please set your DISPLAYMANAGER variable in /etc/conf.d/xdm,
or install x11-apps/xdm package
* Setting up xdm ...
* start-stop-daeon: /usr/bin/xdm does not exist
* ERROR: could not start the Display Manager
The other two error messages are also the same as before.
Thanks again eyoung. Anything else? |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Fri Mar 01, 2013 10:47 pm Post subject: |
|
|
emerge -pv xdm > emxdm.out 2>emxdm.err
emxdm.err is blank
emxdm.out:
These are the packages that would be merged, in order:
Calculating dependencies .. ... done!
[ebuild N ] x11-apps/xconsole-1.0.4 113 kB
[ebuild N ] x11-apps/sessreg-1.0.7 118 kB
[ebuild N ] x11-libs/libXinerama-1.1.2 USE="-static-libs" 274 kB
[ebuild N ] x11-misc/util-macros-1.17 76 kB
[ebuild N ] x11-apps/xdm-1.1.11-r1 USE="(consolekit) ipv6 pam" 437 kB
Total: 5 packages (5 new), Size of downloads: 1,015 kB
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items. |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Fri Mar 01, 2013 11:07 pm Post subject: |
|
|
Perform the following:
| Code: | rc-update del xdm default
emerge -v xdm
rc-update add xdm default
/etc/int.d/xdm start |
I'll help with udev after X is up and running.
_________________
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 |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Fri Mar 01, 2013 11:56 pm Post subject: |
|
|
you might try emerge -s kdm to see if kdm is installed. if you are wanting to use kdm as your login manager, emerging xdm is redundant but harmless.
_________________
Defund the FCC. |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Sat Mar 02, 2013 1:53 am Post subject: |
|
|
| DONAHUE wrote: | | you might try emerge -s kdm to see if kdm is installed. if you are wanting to use kdm as your login manager, emerging xdm is redundant but harmless. |
It's not redundant if his output shows New:
| Code: | [ebuild N ] x11-apps/xconsole-1.0.4 113 kB
[ebuild N ] x11-apps/sessreg-1.0.7 118 kB
[ebuild N ] x11-libs/libXinerama-1.1.2 USE="-static-libs" 274 kB
[ebuild N ] x11-misc/util-macros-1.17 76 kB
[ebuild N ] x11-apps/xdm-1.1.11-r1 USE="(consolekit) ipv6 pam" 437 kB
Total: 5 packages (5 new), Size of downloads: 1,015 kB |
Every ebuild is New which means it was never installed
_________________
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 |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sat Mar 02, 2013 3:22 am Post subject: |
|
|
If you wish to use kdm as your display manager you do not need to emerge xdm. You do need to emerge kdm. Barring accidents emerging kde should emerge kdm.
My machine has the status: | Quote: | x11-apps/xdm
Latest version available: 1.1.11-r1
Latest version installed: [ Not Installed ] |
xdm never emerged. However it has a script at /etc/init.d/xdm | Quote: | #!/sbin/runscript
# Copyright 1999-2012 Gentoo Foundation
# Distributed under the terms of the GNU General Public License, v2
# $Header: /var/cvsroot/gentoo-x86/x11-base/xorg-server/files/xdm.initd-9,v 1.1 2012/11/11 01:49:30 chithanh Exp $
# This is here to serve as a note to myself, and future developers.
#
# Any Display manager (gdm,kdm,xdm) has the following problem: if
# it is started before any getty, and no vt is specified, it will
# usually run on vt2. When the getty on vt2 then starts, and the
# DM is already started, the getty will take control of the keyboard,
# leaving us with a "dead" keyboard.
#
# Resolution: add the following line to /etc/inittab
#
# x:a:once:/etc/X11/startDM.sh
#
# and have /etc/X11/startDM.sh start the DM in daemon mode if
# a lock is present (with the info of what DM should be started),
# else just fall through.
#
# How this basically works, is the "a" runlevel is a additional
# runlevel that you can use to fork processes with init, but the
# runlevel never gets changed to this runlevel. Along with the "a"
# runlevel, the "once" key word means that startDM.sh will only be
# run when we specify it to run, thus eliminating respawning
# startDM.sh when "xdm" is not added to the default runlevel, as was
# done previously.
#
# This script then just calls "telinit a", and init will run
# /etc/X11/startDM.sh after the current runlevel completes (this
# script should only be added to the actual runlevel the user is
# using).
#
# Martin Schlemmer
# aka Azarah
# 04 March 2002
depend() {
need localmount xdm-setup
# this should start as early as possible
# we can't do 'before *' as that breaks it
# (#139824) Start after ypbind and autofs for network authentication
# (#145219 #180163) Could use lirc mouse as input device
# (#70689 comment #92) Start after consolefont to avoid display corruption
# (#291269) Start after quota, since some dm need readable home
# (#390609) gdm-3 will fail when dbus is not running
# (#366753) starting keymaps after X causes problems
after bootmisc consolefont modules netmount
after readahead-list ypbind autofs openvpn gpm lircmd
after quota keymaps
before alsasound
# Start before X
use consolekit dbus xfs
}
setup_dm() {
local MY_XDM
MY_XDM=$(echo "${DISPLAYMANAGER}" | tr '[:upper:]' '[:lower:]')
# Load our root path from profile.env
# Needed for kdm
PATH=${PATH}:$(. /etc/profile.env; echo "${ROOTPATH}")
NAME=
case "${MY_XDM}" in
kdm|kde)
EXE=/usr/bin/kdm
PIDFILE=/var/run/kdm.pid
;;
entrance*)
EXE=/usr/sbin/entrance
PIDFILE=/var/run/entrance.pid
;;
gdm|gnome)
EXE=/usr/bin/gdm
[ "${RC_UNAME}" != "Linux" ] && NAME=gdm-binary
PIDFILE=/var/run/gdm.pid
;;
wdm)
EXE=/usr/bin/wdm
PIDFILE=
;;
gpe)
EXE=/usr/bin/gpe-dm
PIDFILE=/var/run/gpe-dm.pid
;;
lxdm)
EXE=/usr/sbin/lxdm-binary
PIDFILE=/var/run/lxdm.pid
START_STOP_ARGS="--background"
;;
lightdm)
EXE=/usr/sbin/lightdm
PIDFILE=/var/run/lightdm.pid
START_STOP_ARGS="--background"
;;
*)
# first find out if there is such executable
EXE="$(command -v ${MY_XDM} 2>/dev/null)"
PIDFILE="/var/run/${MY_XDM}.pid"
# warn user that he is doing sick things if the exe was not found
if [ -z "${EXE}" ]; then
echo "ERROR: Your XDM value is invalid."
echo " No ${MY_XDM} executable could be found on your system."
fi
;;
esac
if ! [ -x "${EXE}" ]; then
EXE=/usr/bin/xdm
PIDFILE=/var/run/xdm.pid
if ! [ -x "/usr/bin/xdm" ]; then
echo "ERROR: Please set your DISPLAYMANAGER variable in /etc/conf.d/xdm,"
echo " or install x11-apps/xdm package"
eend 255
fi
fi
}
# Check to see if something is defined on our VT
vtstatic() {
if [ -e /etc/inittab ] ; then
grep -Eq "^[^#]+.*\<tty$1\>" /etc/inittab
elif [ -e /etc/ttys ] ; then
grep -q "^ttyv$(($1 - 1))" /etc/ttys
else
return 1
fi
}
start() {
local EXE NAME PIDFILE
setup_dm
if [ -f /etc/.noxdm ]; then
einfo "Skipping ${EXE##*/}, /etc/.noxdm found or \"nox\" bootparam passed."
rm /etc/.noxdm
return 0
fi
ebegin "Setting up ${EXE##*/}"
# save the prefered DM
save_options "service" "${EXE}"
save_options "name" "${NAME}"
save_options "pidfile" "${PIDFILE}"
save_options "start_stop_args" "${START_STOP_ARGS}"
if [ -n "${CHECKVT-y}" ] ; then
if vtstatic "${CHECKVT:-7}" ; then
if [ -x /sbin/telinit ] && [ "${SOFTLEVEL}" != "BOOT" ] && [ "${RC_SOFTLEVEL}" != "BOOT" ]; then
ewarn "Something is already defined on VT ${CHECKVT:-7}, will start X later"
telinit a >/dev/null 2>&1
return 0
else
eerror "Something is already defined on VT ${CHECKVT:-7}, not starting"
return 1
fi
fi
fi
/etc/X11/startDM.sh
eend 0
}
stop() {
local curvt retval
retval=0
if [ -t 0 ]; then
if type fgconsole >/dev/null 2>&1; then
curvt=$(fgconsole 2>/dev/null)
else
curvt=$(tty)
case "${curvt}" in
/dev/ttyv[0-9]*) curvt=${curvt#/dev/ttyv} ;;
*) curvt= ;;
esac
fi
fi
local myexe myname mypidfile myservice
myexe=$(get_options "service")
myname=$(get_options "name")
mypidfile=$(get_options "pidfile")
myservice=${myexe##*/}
[ -z "${myexe}" ] && return 0
ebegin "Stopping ${myservice}"
if start-stop-daemon --quiet --test --stop --exec "${myexe}"; then
start-stop-daemon --stop --exec "${myexe}" --retry TERM/5/TERM/5 \
${mypidfile:+--pidfile} ${mypidfile} \
${myname:+--name} ${myname}
retval=${?}
fi
# switch back to original vt
if [ -n "${curvt}" ]; then
if type chvt >/dev/null 2>&1; then
chvt "${curvt}"
else
vidcontrol -s "$((curvt + 1))"
fi
fi
eend ${retval} "Error stopping ${myservice}"
return ${retval}
}
# vim: set ts=4 : |
which will read /etc/conf.d/xdm and if DISPLAYMANAGER="kdm" is selected look for /usr/bin/kdm. Instead it is looking for /usr/bin/xdm. This suggests a typo in /etc/conf.d/xdm. Another possibility is reflected in the | Quote: | | IMPORTANT: config file '/etc/conf.d/xdm' needs updating. |
. May be some unusual interference with the updated file. Suggest running etc-update, select /etc/conf.d/xdm and replace the existing file with the update. Edit the update to DISPLAYMANAGER="kdm". If you emerge xdm without correcting the current problem you will get xdm as your displkay manager. That is fine also.
_________________
Defund the FCC. |
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sat Mar 02, 2013 5:35 am Post subject: |
|
|
Okay, I've done this:
| Code: |
rc-update del xdm default
emerge -v xdm
rc-update add xdm default
/etc/int.d/xdm start
|
and that seemed to work well. I also rebooted just for the L of it and got some kind of gui login screen, but the login wouldn't work. The rc-update and xdm start command basically said the service was already started, and did not give the previous error. Nice.
I tried 'emerge -s kdm' and kdm is not installed. I also checked and kde-meta is not installed either. I'm guessing kdm will be installed when my emerge --changed-use works without the udev error, with the USE="... kde-meta ..."
After emerging a program, I do still get the notice:
| Quote: |
* IMPORTANT: config file '/etc/conf.d/xdm' needs updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
|
and upon emerge --changed-use ...., I still get the udev slot conflict.
Thanks eyoung, donahue. What next? |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sat Mar 02, 2013 7:24 am Post subject: |
|
|
the use flag is kde not kde-meta; should not be the problem you are seeing. should reveal that kde is already in your profile. However you should delete kde-meta from USE=
| Code: | rc-update del udev-postmount
grep -i devtmpfs /usr/src/linux/.config |
If you do not see CONFIG_DEVTMPFS=y you need to reconfigure/recompile/recopy the kernel to include Device Drivers-> Generic Driver Options->[*] Maintain a devtmpfs filesystem to mount at /dev in the config.
then | Code: | emerge --sync
emerge --unmerge udev virtual/udev udev-init-scripts consolekit
emerge udev
emerging udev should emerge udev-197-r8 , virtual/udev-197-r1 , udev-init-scripts-23
emerge consolekit
/etc/init.d/udev restart
/etc/init.d/consolekit restart
emerge kdebase-meta
emerge -uND world |
_________________
Defund the FCC. |
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sat Mar 02, 2013 8:57 pm Post subject: |
|
|
k, I've deleted kde-meta from the USE variable.
I did these:
| Code: |
rc-update del udev-postmount
grep -i devtmpfs /usr/src/linux/.config
|
and got -->
| Quote: |
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
|
All of the following seemed to work properly except for the last command:
| Code: |
emerge --sync
emerge --unmerge udev virtual/udev udev-init-scripts consolekit
emerge udev
emerging udev should emerge udev-197-r8 , virtual/udev-197-r1 , udev-init-scripts-23
emerge consolekit
/etc/init.d/udev restart
/etc/init.d/consolekit restart
emerge kdebase-meta
emerge -uND world
|
It's probably not important, but on the udev restart, I got
| Quote: |
* Failed to stop udev using udevadm
* Trying with start-stop-daemon ...
* ...
|
after emerge -uND world, I started seeing errors around here:
| Quote: |
Making all in modetest
make[3]: Entering directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests/modetest'
CC modetest.o
CC buffers.o
/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40/tests/modetest/modetest.c: In function ‘parse_plane’:
/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40/tests/modetest/modetest.c:886:2: warning: format ‘%s’ expects argument of type ‘char *’, but argument 6 has type ‘char (*)[5]’ [-Wformat]
CCLD modetest
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libudev.so.0, needed by /usr/lib64/libEGL.so.1, not found (try using -rpath or -rpath-link)
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_property_value'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_new_from_devnum'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_parent'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_unref'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_devnode'
/usr/lib64/libEGL.so.1: undefined reference to `udev_new'
/usr/lib64/libEGL.so.1: undefined reference to `udev_unref'
collect2: ld returned 1 exit status
make[3]: *** [modetest] Error 1
make[3]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests/modetest'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
make: *** [all] Error 2
* ERROR: x11-libs/libdrm-2.4.40 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=x11-libs/libdrm-2.4.40'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libdrm-2.4.40'`.
* The complete build log is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/environment'.
* Working directory: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
* S: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40'
>>> Failed to emerge x11-libs/libdrm-2.4.40, Log file:
>>> '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'
* Messages for package dev-libs/mpc-1.0.1:
* Old versions of installed libraries were detected on your system.
* In order to avoid breaking packages that depend on these old libs,
* the libraries are not being removed. You need to run revdep-rebuild
* in order to remove these old dependencies. If you do not have this
* helper program, simply emerge the 'gentoolkit' package.
*
* # revdep-rebuild --library '/usr/lib64/libmpc.so.2' && rm '/usr/lib64/libmpc.so.2'
* Messages for package x11-libs/libdrm-2.4.40:
* ERROR: x11-libs/libdrm-2.4.40 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=x11-libs/libdrm-2.4.40'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libdrm-2.4.40'`.
* The complete build log is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/environment'.
* Working directory: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
* S: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40'
* Regenerating GNU info directory index...
* Processed 93 info files.
* IMPORTANT: config file '/etc/conf.d/xdm' needs updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
|
You can see the whole file (of emerge output) here if you need to: http://www.mediafire.com/?3stnpqze0t68dr0 |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Sat Mar 02, 2013 10:32 pm Post subject: |
|
|
Wow JBlue I'm proud to have helped you get this far with DONAHUE. Unmerging udev is easy but it's not for the faint of heart.
Lets make sure that infact udev-197 installed with:
| Quote: | * Failed to stop udev using udevadm
* Trying with start-stop-daemon ...
* ... |
is important because udev cannot be restarted while a system is running as you have devices still running. We could go through each one, and find out but this should be easier:
If 197 did install properly upon reboot libudev.so.0 will be relinked to version 197 and this will succeed. The reason it is failing is 2 fold:
1. It was removed by the previous emerge and the failure of udev to restart w/o error caused it not to be restarted.
2. Even though you restarted udev your kernel image in RAM is still linked to the old module/object in RAM. Restarting relinks the kernel to the proper udev version, when you see the line:
| Quote: | | *Waiting for events to be populated by udev |
during reboot
_________________
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 |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Mar 03, 2013 12:06 am Post subject: |
|
|
| Code: | emerge --sync
emerge portage # if suggested after sync
gcc-config -l
#set to latest version in the list by its number
gcc-config number
emerge -1 libtool
emerge lafilefixer perl-cleaner python-updater
lafilefixer --justfixit
perl-cleaner all
python-updater
emerge -uND --keep-going world
emerge -uNDav world |
any remaining unmerged items?
_________________
Defund the FCC. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Mar 03, 2013 12:18 am Post subject: |
|
|
interesting? side comment :
I performed the | Code: | emerge --unmerge udev virtual/udev udev-init-scripts consolekit
emerge udev
emerging udev should emerge udev-197-r8 , virtual/udev-197-r1 , udev-init-scripts-23
emerge consolekit
/etc/init.d/udev restart
/etc/init.d/consolekit restart |
steps here without incident and without a reboot. These steps do not stop udev and accord with the news item concerning udev upgrade. I agree with the reboot as therapy for the problem reported.
_________________
Defund the FCC. |
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sun Mar 03, 2013 12:55 am Post subject: |
|
|
eyoung: Yeah, there were some pretty hefty warnings about whether I really wanted to do that or not, but it looks like you guys know what you're doing so I went with it.
With this,
Both before and after reboot, I get,
| Quote: |
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild R ] sys-fs/udev-197-r8 USE="acl gudev hwdb introspection keymap kmod openrc -doc (-selinux) -static-libs" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
|
About this line,
| Quote: | | libudev.so.0 will be relinked to version 197 and this will succeed. |
, how do I know if libudev.so.0 was properly linked to v 197, and what will succeed?
Also, on reboot, I do not see the line,
| Quote: | | *Waiting for events to be populated by udev |
I've checked dmesg, /var/log/messages, and /var/log/rc.log and it's not there. Possibly related is a line in dmesg (and similar lines in messages),
| Quote: | | [ 1.767654] md: Waiting for all devices to be available before autodetect |
Should I attempt 'emerge -uND world' again now after reboot, or should I continue on with donahue's chain of commands?,
| Code: |
emerge --sync
emerge portage # if suggested after sync
gcc-config -l
#set to latest version in the list by its number
gcc-config number
emerge -1 libtool
emerge lafilefixer perl-cleaner python-updater
lafilefixer --justfixit
perl-cleaner all
python-updater
emerge -uND --keep-going world
emerge -uNDav world
|
I'm guessing move on with the above commands... continuing.
side Question: gcc-config -l' gives:
| Quote: | | [1] x86_64-pc-linux-gnu-4.6.3 * |
so the next command should be,
right? going with that... |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Mar 03, 2013 1:00 am Post subject: |
|
|
good so far
_________________
Defund the FCC. |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Sun Mar 03, 2013 4:34 am Post subject: |
|
|
Assuming:
| Code: | emerge emerge -uND --keep-going world
emerge -uNDav world |
complete, edit /etc/conf.d/xdm. Set DISPLAYMANAGER="kdm" then:
| Code: | eselect news read new
env-update && source /etc/profile
/etc/init.d/xdm restart |
should give you a running KDE. In case your curious, the second emerge world catches the ones passed on by --keep-going
_________________
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 |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sun Mar 03, 2013 6:39 am Post subject: |
|
|
emerge --sync does say that I need to update portage.
emerge portage went fine, so did all commands through lafilefixer. lafilefixer --justfixit returned all files 'already clean'. Basically the same with the perl-cleaner.
Python-updater had one error:
| Quote: |
/usr/bin/install -c -m 0644 ./html/index.sgml /var/tmp/portage/dev-libs/libxslt-1.1.28/image//usr/share/doc/libxslt-1.1.28/html/html
/usr/bin/install: cannot stat ‘./html/index.sgml’: No such file or directory
make[2]: [install-data-local] Error 1 (ignored)
|
Looks like it could be harmless. continuing...
| Code: |
emerge -uND --keep-going world > emukg.out 2>emukg.err
|
This produced many errors.
File emukg.err:
| Quote: |
*
* The following 20 packages have failed to build or install:
*
* (x11-libs/libdrm-2.4.40::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'
* (media-libs/mesa-9.0.1::gentoo, ebuild scheduled for merge)
* (x11-libs/gtk+-2.24.12::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/x11-libs/gtk+-2.24.12/temp/build.log'
* (x11-libs/gtk+-3.4.4::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/x11-libs/gtk+-3.4.4/temp/build.log'
* (app-crypt/pinentry-0.8.2::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/app-crypt/pinentry-0.8.2/temp/build.log'
* (sys-auth/polkit-0.110::gentoo, ebuild scheduled for merge)
* (kde-base/katepart-4.9.5::gentoo, ebuild scheduled for merge)
* (net-libs/libproxy-0.4.10-r1::gentoo, ebuild scheduled for merge)
* (net-libs/libsoup-2.38.1::gentoo, ebuild scheduled for merge)
* (kde-base/kdelibs-4.9.5::gentoo, ebuild scheduled for merge)
* (kde-base/khelpcenter-4.9.5::gentoo, ebuild scheduled for merge)
* (kde-misc/polkit-kde-kcmodules-0.98_pre20120917::gentoo, ebuild scheduled for merge)
* (media-libs/phonon-4.6.0-r1::gentoo, ebuild scheduled for merge)
* (media-libs/phonon-gstreamer-4.6.2-r1::gentoo, ebuild scheduled for merge)
* (sys-auth/polkit-kde-agent-0.99.0::gentoo, ebuild scheduled for merge)
* (media-plugins/gst-plugins-soup-0.10.31::gentoo, ebuild scheduled for merge)
* (net-libs/glib-networking-2.32.3::gentoo, ebuild scheduled for merge)
* (kde-base/nepomuk-core-4.9.5::gentoo, ebuild scheduled for merge)
* (app-crypt/gnupg-2.0.19::gentoo, ebuild scheduled for merge)
* (kde-base/kdesu-4.9.5::gentoo, ebuild scheduled for merge)
*
* After world updates, it is important to remove obsolete packages with
* emerge --depclean. Refer to `man emerge` for more information.
|
I include one of the above-mentioned log files for reference, the first,
/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log
Here's the udev-related errors,
| Quote: |
make[3]: Entering directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests/modetest'
CC modetest.o
CC buffers.o
/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40/tests/modetest/modetest.c: In function ‘parse_plane’:
/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40/tests/modetest/modetest.c:886:2: warning: format ‘%s’ expects argument of type ‘char *’, but argument 6 has type ‘char (*)[5]’ [-Wformat]
CCLD modetest
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libudev.so.0, needed by /usr/lib64/libEGL.so.1, not found (try using -rpath or -rpath-link)
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_property_value'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_new_from_devnum'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_parent'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_unref'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_devnode'
/usr/lib64/libEGL.so.1: undefined reference to `udev_new'
/usr/lib64/libEGL.so.1: undefined reference to `udev_unref'
collect2: ld returned 1 exit status
make[3]: *** [modetest] Error 1
make[3]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests/modetest'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
make: *** [all] Error 2
* ERROR: x11-libs/libdrm-2.4.40 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=x11-libs/libdrm-2.4.40'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libdrm-2.4.40'`.
* The complete build log is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/environment'.
* Working directory: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
* S: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40'
|
If you need to, you can see the whole log file here http://www.mediafire.com/?b5mv116z7ryd527
stopping here...
What do you think? Did I do something wrong on the install?
Thanks again, by the way, for the continued support. It's much appreciated. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Mar 03, 2013 7:20 am Post subject: |
|
|
Do sys-fs/udev-197-r8, udev-init-scripts-23, and virtual/udev-197-r1 appear in the output?
Do udev and udev-mount appear in sysinit?
Do udev, udev-mount, devfs, and dmesg show started? Has udev-postmount in fact been removed?
| Code: | | emerge udev virtual/udev |
any problems?
| Code: | emerge gentoolkit
revdep-rebuild |
any problems?
| Code: | | emerge --info | grep udev |
output should show udev is in the use flags
_________________
Defund the FCC. |
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sun Mar 03, 2013 6:05 pm Post subject: |
|
|
sys-fs/udev-197-r8, udev-init-scripts-23, and virtual/udev-197-r1 do appear in the output.
udev and udev-mount appear in sysinit
udev, udev-mount, devfs, and dmesg show started, and I don't see udev-postmount.
No problems with emerge udev virtual/udev, but I do see this notice:
| Quote: |
>>> Installing (2 of 2) virtual/udev-197-r1
>>> Recording virtual/udev in "world" favorites file...
* Messages for package sys-fs/udev-197-r8:
*
* udev-197 and newer introduces a new method of naming network
* interfaces. The new names are a very significant change, so
* they are disabled by default on live systems.
* Please see the contents of /etc/udev/rules.d/80-net-name-slot.rules for more
* information on this feature.
* You still have /etc/udev/rules.d/70-persistent-net.rules in place from previous udev release.
* Upstream has removed the possibility of renaming to existing
* network interfaces. For example, it's not possible to assign based
* on MAC address to existing interface eth0.
* See https://bugs.gentoo.org/453494 for more information.
* Rename your file to something else starting with 70- to silence
* this warning.
*
* You need to restart udev as soon as possible to make the upgrade go
* into effect.
* The method you use to do this depends on your init system.
*
*
* For more information on udev on Gentoo, writing udev rules, and
* fixing known issues visit:
* http://www.gentoo.org/doc/en/udev-guide.xml
|
but I think you're probably aware of this already. I just read /etc/udev/rules.d/80-net-name-slot.rules and it looks like if I do nothing re: this, it should be fine.
| Code: |
revdep-rebuild > revreb.out 2>revreb.err
|
-->errors
file revreb.err:
| Quote: |
* broken /usr/bin/Xorg (requires libudev.so.0)
* broken /usr/lib64/egl/egl_gallium.so (requires libudev.so.0)
* broken /usr/lib64/opengl/xorg-x11/lib/libEGL.so.1.0.0 (requires libudev.so.0)
* broken /usr/lib64/xorg/modules/drivers/nouveau_drv.so (requires libudev.so.0)
* broken /usr/lib64/xorg/modules/input/evdev_drv.so (requires libudev.so.0)
* /usr/bin/Xorg -> x11-base/xorg-server
* /usr/lib64/egl/egl_gallium.so -> media-libs/mesa
* /usr/lib64/opengl/xorg-x11/lib/libEGL.so.1.0.0 -> media-libs/mesa
* /usr/lib64/xorg/modules/drivers/nouveau_drv.so -> x11-drivers/xf86-video-nouveau
* /usr/lib64/xorg/modules/input/evdev_drv.so -> x11-drivers/xf86-input-evdev
* revdep-rebuild failed to emerge all packages.
* you have the following choices:
|
Looks like it failed on modetest again.
file revreb.out:
| Quote: |
make[3]: Entering directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests/modetest'
CC buffers.o
CC modetest.o
/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40/tests/modetest/modetest.c: In function ‘parse_plane’:
/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40/tests/modetest/modetest.c:886:2: warning: format ‘%s’ expects argument of type ‘char *’, but argument 6 has type ‘char (*)[5]’ [-Wformat]
CCLD modetest
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libudev.so.0, needed by /usr/lib64/libEGL.so.1, not found (try using -rpath or -rpath-link)
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_property_value'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_new_from_devnum'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_parent'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_unref'
/usr/lib64/libEGL.so.1: undefined reference to `udev_device_get_devnode'
/usr/lib64/libEGL.so.1: undefined reference to `udev_new'
/usr/lib64/libEGL.so.1: undefined reference to `udev_unref'
collect2: ld returned 1 exit status
make[3]: *** [modetest] Error 1
make[3]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests/modetest'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
make: *** [all] Error 2
* ERROR: x11-libs/libdrm-2.4.40 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=x11-libs/libdrm-2.4.40'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libdrm-2.4.40'`.
* The complete build log is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/environment'.
* Working directory: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
* S: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40'
>>> Failed to emerge x11-libs/libdrm-2.4.40, Log file:
>>> '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'
* Messages for package x11-libs/libdrm-2.4.40:
* ERROR: x11-libs/libdrm-2.4.40 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=x11-libs/libdrm-2.4.40'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libdrm-2.4.40'`.
* The complete build log is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/libdrm-2.4.40/temp/environment'.
* Working directory: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40_build'
* S: '/var/tmp/portage/x11-libs/libdrm-2.4.40/work/libdrm-2.4.40'
|
the error info in the log file, /var/tmp/portage/x11-libs/libdrm-2.4.40/temp/build.log is exactly the same as above.
and udev is in the USE variable... |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Mar 03, 2013 6:26 pm Post subject: |
|
|
does | Code: | | ls /lib32/libudev.so.0.11.5 |
produce | Quote: | | /lib32/libudev.so.0.11.5 |
the actual compiled code
_________________
Defund the FCC.
Last edited by DONAHUE on Sun Mar 03, 2013 6:43 pm; edited 1 time in total |
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sun Mar 03, 2013 6:35 pm Post subject: |
|
|
Close. I've got
/lib32/libudev.so.0 -> libudev.so.0.11.5 |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Mar 03, 2013 6:50 pm Post subject: |
|
|
does | Code: | | ls /lib32/libudev.so.0 |
produce | Quote: | | /lib32/libudev.so.0 |
a symlink to libudev.so.0
does | Code: | | cat /usr/lib32/pkgconfig/libudev.pc |
show | Quote: | prefix=/usr
exec_prefix=/usr
libdir=/usr/lib32
includedir=/usr/include
Name: libudev
Description: Library to access udev device information
Version: 171
Libs: -L${libdir} -ludev -lrt
Libs.private:
Cflags: -I${includedir} |
_________________
Defund the FCC. |
|
| Back to top |
|
|
Jblue
n00b
Joined: 28 Feb 2013
Posts: 35
|
| Posted: Sun Mar 03, 2013 6:58 pm Post subject: |
|
|
| Code: | | ls /lib32/libudev.so.0 |
yes, produces -->
| Quote: | | /lib32/libudev.so.0 |
| Code: | | ls -l /lib32/libudev.so.0 |
produces -->
| Quote: | | /lib32/libudev.so.0 -> libudev.so.0.11.5 |
| Code: | | cat /usr/lib32/pkgconfig/libudev.pc |
produces exactly as you have:
| Quote: |
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib32
includedir=/usr/include
Name: libudev
Description: Library to access udev device information
Version: 171
Libs: -L${libdir} -ludev -lrt
Libs.private:
Cflags: -I${includedir}
|
|
|
| Back to top |
|
|
|
|
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
|
|
Installing Gentoo
