Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Solved: Stuck in grub2
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Fri Nov 08, 2013 8:50 pm    Post subject: Reply with quote

eyoung100 wrote:
Your done with grub... Now we will setup the X Server, then add KDE, then emerge Grub:2, test the chainloader, then actuall install grub 2
  1. Are you logged in as root :?:
  2. Have you configured XOrg already :?:
  3. Have you emerged kde-meta :?:


Yes, actually I have done each of them, except for actually installing grub 2? I thought that with the chainloader showing up and bringing me to a prompt, that grub 2 was somehow still in the system. Perhaps not? I will be home very soon as I get off work in a few minutes, so I will go ahead and do that.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Fri Nov 08, 2013 9:08 pm    Post subject: Reply with quote

Logging in as root is a bad idea when using a desktop, so before we start please emerge app-admin/sudo, put your user in the wheel group.

Sudo Wiki

Since Xorg is already emerged, we need to add some tools:
Code:
emerge twm xterm xclock
startx


What happened :?: In case nothing happens look at the Gentoo: XOrg/Configuration Wiki

If the answer is correct:
Code:
nano -w/etc/conf.d/xdm
DISPLAYMANAGER=kdm
(Save)
nano -w /etc/env.d/90xsession
XSESSION=KDE-4
(Save)
rc-update add xdm default
reboot


You should see a KDE login window. If you do we will add grub 2
_________________
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
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sat Nov 09, 2013 1:57 am    Post subject: Reply with quote

Doing startx, after all that, simply put me back into the 3 xterm window mode. So I looked at the link you provided and followed the suggestions to the point of emerging xorg-server. The next step after doing emerge @x11 module-rebuild, is:
Code:
root # env-update
root # source /etc/profile


And then I will follow your next instructions.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Sat Nov 09, 2013 2:34 am    Post subject: Reply with quote

The answer was correct, skip to the next...
_________________
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
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sat Nov 09, 2013 2:44 am    Post subject: Reply with quote

No KDE login window. Am at the gentux login:

Does not matter whether I login as root or my user, I still have the 3 xterm windows.

EDIT:**Hold the fort! I had forgotten the env update and the source etc/profile. This time when I rebooted I still came to the command line login, but then logging and doing startx, I got the gui desktop. I was able to configure my dual monitor setup.**
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Sat Nov 09, 2013 3:30 am    Post subject: Reply with quote

now add xdm to the default run level after setting DISPLAYMANAGER to kdm
_________________
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
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sat Nov 09, 2013 3:34 am    Post subject: Reply with quote

eyoung100 wrote:
now add xdm to the default run level after setting DISPLAYMANAGER to kdm

Yes, that part was done. Does it need to be done again?
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Sat Nov 09, 2013 3:40 am    Post subject: Reply with quote

no:
Code:
/etc/init.d/xdm restart
if its not already 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
View user's profile Send private message
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sat Nov 09, 2013 3:53 am    Post subject: Reply with quote

Ok, I had messed up and left DISPLAYMANAGER=XDM. Changed it to KDM and did the restart. KDM is setup. Can't reboot right now because I have Firefox emerging and it is taking some time. As soon as that finishes, I will reboot to see what happens. But Firefox is doing version 17.0.9 and I know that current version is 25.0. I will need to revisit some threads to remember how to get that to install correctly.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Sat Nov 09, 2013 4:18 am    Post subject: Reply with quote

/etc/portage/package.accept_keywords
www-client/firefox ~amd64 or ~x86 depending on your arch
_________________
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
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sat Nov 09, 2013 5:25 am    Post subject: Reply with quote

Thank you for the tip there. I have, however, apparently gone two steps back. I rebooted after the Firefox emerge and now I don't get a chance to login at all. It comes to a login prompt and before I can even type a user name, it goes black with a blinking cursor in the upper left corner and all I can do is Ctrl-Alt-Del to reboot once more. It doesn't matter whether I choose the Gentoo or the chainloader, it does the same thing.

I did emerge the nvidia-drivers because my card is an Nvidia. It installed version 308.104 which was OK I figured, but I don't think that is what has caused the problem here.

Edit: Actually, I just realized that I had two screens apparently. I pressed Alt-F2 and it showed me the login prompt so I logged in. When I do startx, I see a red entry that failed to load Nvidia kernel module and then /dev/nvidiactl does not exist. I did emerge xorg-server again, but that did nothing. Also noticed:
Code:
xauth: file /root/.serverauth.19997 does not exist

As a matter of fact, when I
Code:
cd /

and then
Code:
ls

I see all the directories. But when I
Code:
cd root

there is nothing at all in there. Is this normal?
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Sat Nov 09, 2013 11:13 pm    Post subject: Reply with quote

mark2 wrote:
Thank you for the tip there. I have, however, apparently gone two steps back. I rebooted after the Firefox emerge and now I don't get a chance to login at all. It comes to a login prompt and before I can even type a user name, it goes black with a blinking cursor in the upper left corner and all I can do is Ctrl-Alt-Del to reboot once more. It doesn't matter whether I choose the Gentoo or the chainloader, it does the same thing.

I did emerge the nvidia-drivers because my card is an Nvidia. It installed version 308.104 which was OK I figured, but I don't think that is what has caused the problem here.

Edit: Actually, I just realized that I had two screens apparently. I pressed Alt-F2 and it showed me the login prompt so I logged in. When I do startx, I see a red entry that failed to load Nvidia kernel module and then /dev/nvidiactl does not exist. I did emerge xorg-server again, but that did nothing. Also noticed:
Code:
xauth: file /root/.serverauth.19997 does not exist

As a matter of fact, when I
Code:
cd /

and then
Code:
ls

I see all the directories. But when I
Code:
cd root

there is nothing at all in there. Is this normal?


Code:
modprobe nvidia

/etc/conf.d/modules
modules_3="nvidia"

and yes it's normal
_________________
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
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3264
Location: Canada

PostPosted: Sun Nov 10, 2013 1:12 am    Post subject: Reply with quote

mark2 wrote:

As a matter of fact, when I
Code:
cd /

and then
Code:
ls

I see all the directories. But when I
Code:
cd root

there is nothing at all in there. Is this normal?


sure, /root is a home directory for user "root". If you (as root) did not put anything there, there is nothing there but some . (dot) files
Back to top
View user's profile Send private message
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sun Nov 10, 2013 2:47 pm    Post subject: Reply with quote

So that makes sense about root. Anyway, modprobe nvidia returns:
Code:
ERROR: could not insert 'nvidia': No such device

and
Code:
emerge nvidia-drivers

came back with
Code:
ERROR: x11-drivers/nvidia-drivers-304.108::gentoo failed (compile phase):emake failed

The log file shows:
Code:
[32;01m * Package:    x11-drivers/nvidia-drivers-304.108
 * Repository: gentoo
 * Maintainer: jer@gentoo.org xarthisius@gentoo.org
 * USE:        X abi_x86_64 acpi amd64 elibc_glibc kernel_linux multilib policykit tools userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.10.7-gentoo-r1/build
 * Found sources for kernel version:
 *     3.10.7-gentoo-r1
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-304.108.run to /var/tmp/portage/x11-drivers/nvidia-drivers-304.108/work
>>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-304.108/work
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-304.108/work ...
 * Converting /kernel/Makefile.kbuild to use M= instead of SUBDIRS= ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/x11-drivers/nvidia-drivers-304.108/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/x11-drivers/nvidia-drivers-304.108/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.10.7-gentoo-r1/build CC=x86_64-pc-linux-gnu-gcc clean module
Your kernel was configured to include nvidiafb support!

The nvidiafb driver conflicts with the NVIDIA driver, please
reconfigure your kernel and *disable* nvidiafb support, then
try installing the NVIDIA kernel module again.

*** Failed nvidiafb sanity check. Bailing out! ***

make[1]: *** [build-sanity-checks] Error 1
make: *** [module] Error 2
 * ERROR: x11-drivers/nvidia-drivers-304.108::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-304.108::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-304.108::gentoo'`.
 * The complete build log is located at '/var/log/portage/x11-drivers:nvidia-drivers-304.108:20131110-092524.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-304.108/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-304.108/temp/environment'.
 * Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-304.108/work/kernel'
 * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-304.108/work/'

And so, looks like its time to reconfigure the kernel to eliminate the conflict. I'll post back when this completes.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3264
Location: Canada

PostPosted: Sun Nov 10, 2013 6:18 pm    Post subject: Reply with quote

Yes, you should eliminate nvidiafb frame buffer for the the kernel. Actually binaary nvidia says that it doesn't like any framebuffers, so you may want to eliminated all of them. Although I still use vesafb with nvidia drivers and has not run into problems yet.
Back to top
View user's profile Send private message
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sun Nov 10, 2013 7:27 pm    Post subject: Reply with quote

Eliminated nvidiafb but that did not help. This time it ran emerge nvidia-drivers, but at the end it unloaded the module. It also found no screens.
Code:
[ 89325.509]
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 89325.509] X Protocol Version 11, Revision 0
[ 89325.509] Build Operating System: Linux 3.10.7-gentoo-r1 x86_64 Gentoo
[ 89325.509] Current Operating System: Linux gentux 3.10.7-gentoo-r1 #1 SMP Sat Nov 9 13:31:55 EST 2013 x86_64
[ 89325.509] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-3.10.7-gentoo-r1 root=UUID=b762b3ef-e3ab-4ff8-bb32-1198abf07277 ro
[ 89325.510] Build Date: 09 November 2013  09:04:34AM
[ 89325.510] 
[ 89325.510] Current version of pixman: 0.30.2
[ 89325.510]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[ 89325.510] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 89325.510] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 10 14:52:20 2013
[ 89325.510] (==) Using config file: "/etc/X11/xorg.conf"
[ 89325.511] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 89325.511] (==) ServerLayout "Layout0"
[ 89325.511] (**) |-->Screen "Screen0" (0)
[ 89325.511] (**) |   |-->Monitor "Monitor0"
[ 89325.511] (**) |   |-->Device "Device0"
[ 89325.511] (**) |-->Input Device "Keyboard0"
[ 89325.511] (**) |-->Input Device "Mouse0"
[ 89325.511] (==) Automatically adding devices
[ 89325.511] (==) Automatically enabling devices
[ 89325.511] (==) Automatically adding GPU devices
[ 89325.511] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 89325.511]    Entry deleted from font path.
[ 89325.511] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 89325.511]    Entry deleted from font path.
[ 89325.511] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 89325.511]    Entry deleted from font path.
[ 89325.511] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 89325.511]    Entry deleted from font path.
[ 89325.511]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 89325.511] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 89325.511]    Entry deleted from font path.
[ 89325.511]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 89325.511] (==) FontPath set to:
   /usr/share/fonts/misc/
[ 89325.511] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 89325.511] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 89325.511] (WW) Disabling Keyboard0
[ 89325.511] (WW) Disabling Mouse0
[ 89325.511] (II) Loader magic: 0x7e7b00
[ 89325.511] (II) Module ABI versions:
[ 89325.511]    X.Org ANSI C Emulation: 0.4
[ 89325.511]    X.Org Video Driver: 14.1
[ 89325.511]    X.Org XInput driver : 19.1
[ 89325.511]    X.Org Server Extension : 7.0
[ 89325.513] (--) PCI:*(0:1:0:0) 10de:0165:10de:0334 rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfc000000/16777216, BIOS @ 0x????????/131072
[ 89325.513] Initializing built-in extension Generic Event Extension
[ 89325.513] Initializing built-in extension SHAPE
[ 89325.513] Initializing built-in extension MIT-SHM
[ 89325.513] Initializing built-in extension XInputExtension
[ 89325.513] Initializing built-in extension XTEST
[ 89325.513] Initializing built-in extension BIG-REQUESTS
[ 89325.514] Initializing built-in extension SYNC
[ 89325.514] Initializing built-in extension XKEYBOARD
[ 89325.514] Initializing built-in extension XC-MISC
[ 89325.514] Initializing built-in extension XINERAMA
[ 89325.514] Initializing built-in extension XFIXES
[ 89325.514] Initializing built-in extension RENDER
[ 89325.514] Initializing built-in extension RANDR
[ 89325.514] Initializing built-in extension COMPOSITE
[ 89325.514] Initializing built-in extension DAMAGE
[ 89325.514] Initializing built-in extension MIT-SCREEN-SAVER
[ 89325.514] Initializing built-in extension DOUBLE-BUFFER
[ 89325.514] Initializing built-in extension DPMS
[ 89325.514] Initializing built-in extension X-Resource
[ 89325.514] Initializing built-in extension XVideo
[ 89325.514] Initializing built-in extension XVideo-MotionCompensation
[ 89325.514] Initializing built-in extension XFree86-VidModeExtension
[ 89325.514] Initializing built-in extension XFree86-DGA
[ 89325.514] (II) LoadModule: "nvidia"
[ 89325.515] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[ 89325.516] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 89325.516]    compiled for 4.0.2, module version = 1.0.0
[ 89325.516]    Module class: X.Org Video Driver
[ 89325.553] (II) NVIDIA dlloader X Driver  304.108  Wed Jul 31 19:36:56 PDT 2013
[ 89325.553] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 89325.554] (--) using VT number 7

[ 89325.556] (II) Loading sub module "fb"
[ 89325.556] (II) LoadModule: "fb"
[ 89325.557] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 89325.557] (II) Module fb: vendor="X.Org Foundation"
[ 89325.557]    compiled for 1.14.3, module version = 1.0.0
[ 89325.557]    ABI class: X.Org ANSI C Emulation, version 0.4
[ 89325.557] (II) Loading sub module "wfb"
[ 89325.557] (II) LoadModule: "wfb"
[ 89325.557] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[ 89325.557] (II) Module wfb: vendor="X.Org Foundation"
[ 89325.557]    compiled for 1.14.3, module version = 1.0.0
[ 89325.557]    ABI class: X.Org ANSI C Emulation, version 0.4
[ 89325.557] (II) Loading sub module "ramdac"
[ 89325.557] (II) LoadModule: "ramdac"
[ 89325.557] (II) Module "ramdac" already built-in
[ 89325.557] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 89325.557] (==) NVIDIA(0): RGB weight 888
[ 89325.557] (==) NVIDIA(0): Default visual is TrueColor
[ 89325.557] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 89325.558] (**) NVIDIA(0): Enabling 2D acceleration
[ 89325.558] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[ 89325.558] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[ 89325.558] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[ 89325.558] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[ 89325.558] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
[ 89325.686] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
[ 89325.686] (EE) NVIDIA(0):     system's kernel log for additional error messages and
[ 89325.686] (EE) NVIDIA(0):     consult the NVIDIA README for details.
[ 89325.686] (EE) NVIDIA(0):  *** Aborting ***
[ 89325.686] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 89325.686] (II) UnloadModule: "nvidia"
[ 89325.686] (II) UnloadSubModule: "wfb"
[ 89325.686] (II) UnloadSubModule: "fb"
[ 89325.686] (EE) Screen(s) found, but none have a usable configuration.
[ 89325.686] (EE)
Fatal server error:
[ 89325.686] (EE) no screens found(EE)
[ 89325.687] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[ 89325.687] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 89325.687] (EE)
[ 89325.692] (EE) Server terminated with error (1). Closing log file.

but that didn't help. Still had warnings and errors. So I created the fonts.dir where it said it needed them, but that didn't work either. Output of /var/log/Xorg.0.log produced:
Code:
[ 90452.570]
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 90452.570] X Protocol Version 11, Revision 0
[ 90452.570] Build Operating System: Linux 3.10.7-gentoo-r1 x86_64 Gentoo
[ 90452.570] Current Operating System: Linux gentux 3.10.7-gentoo-r1 #1 SMP Sat Nov 9 13:31:55 EST 2013 x86_64
[ 90452.570] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-3.10.7-gentoo-r1 root=UUID=b762b3ef-e3ab-4ff8-bb32-1198abf07277 ro
[ 90452.570] Build Date: 09 November 2013  09:04:34AM
[ 90452.571] 
[ 90452.571] Current version of pixman: 0.30.2
[ 90452.571]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[ 90452.571] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 90452.571] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 10 15:11:07 2013
[ 90452.571] (==) Using config file: "/etc/X11/xorg.conf"
[ 90452.571] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 90452.571] (==) ServerLayout "Layout0"
[ 90452.572] (**) |-->Screen "Screen0" (0)
[ 90452.572] (**) |   |-->Monitor "Monitor0"
[ 90452.572] (**) |   |-->Device "Device0"
[ 90452.572] (**) |-->Input Device "Keyboard0"
[ 90452.572] (**) |-->Input Device "Mouse0"
[ 90452.572] (==) Automatically adding devices
[ 90452.572] (==) Automatically enabling devices
[ 90452.572] (==) Automatically adding GPU devices
[ 90452.572] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF/".
[ 90452.572]    Entry deleted from font path.
[ 90452.572]    (Run 'mkfontdir' on "/usr/share/fonts/TTF/").
[ 90452.572] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[ 90452.572]    Entry deleted from font path.
[ 90452.572]    (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[ 90452.572] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/Type1/".
[ 90452.572]    Entry deleted from font path.
[ 90452.572]    (Run 'mkfontdir' on "/usr/share/fonts/Type1/").
[ 90452.572] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 90452.572]    Entry deleted from font path.
[ 90452.572]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 90452.572] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 90452.572]    Entry deleted from font path.
[ 90452.572]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 90452.572] (==) FontPath set to:
   /usr/share/fonts/misc/
[ 90452.572] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 90452.572] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 90452.572] (WW) Disabling Keyboard0
[ 90452.572] (WW) Disabling Mouse0
[ 90452.572] (II) Loader magic: 0x7e7b00
[ 90452.572] (II) Module ABI versions:
[ 90452.572]    X.Org ANSI C Emulation: 0.4
[ 90452.572]    X.Org Video Driver: 14.1
[ 90452.572]    X.Org XInput driver : 19.1
[ 90452.572]    X.Org Server Extension : 7.0
[ 90452.574] (--) PCI:*(0:1:0:0) 10de:0165:10de:0334 rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfc000000/16777216, BIOS @ 0x????????/131072
[ 90452.574] Initializing built-in extension Generic Event Extension
[ 90452.574] Initializing built-in extension SHAPE
[ 90452.574] Initializing built-in extension MIT-SHM
[ 90452.574] Initializing built-in extension XInputExtension
[ 90452.574] Initializing built-in extension XTEST
[ 90452.574] Initializing built-in extension BIG-REQUESTS
[ 90452.574] Initializing built-in extension SYNC
[ 90452.574] Initializing built-in extension XKEYBOARD
[ 90452.574] Initializing built-in extension XC-MISC
[ 90452.574] Initializing built-in extension XINERAMA
[ 90452.575] Initializing built-in extension XFIXES
[ 90452.575] Initializing built-in extension RENDER
[ 90452.575] Initializing built-in extension RANDR
[ 90452.575] Initializing built-in extension COMPOSITE
[ 90452.575] Initializing built-in extension DAMAGE
[ 90452.575] Initializing built-in extension MIT-SCREEN-SAVER
[ 90452.575] Initializing built-in extension DOUBLE-BUFFER
[ 90452.575] Initializing built-in extension DPMS
[ 90452.575] Initializing built-in extension X-Resource
[ 90452.575] Initializing built-in extension XVideo
[ 90452.575] Initializing built-in extension XVideo-MotionCompensation
[ 90452.575] Initializing built-in extension XFree86-VidModeExtension
[ 90452.575] Initializing built-in extension XFree86-DGA
[ 90452.575] (II) LoadModule: "nvidia"
[ 90452.576] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[ 90452.576] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 90452.576]    compiled for 4.0.2, module version = 1.0.0
[ 90452.576]    Module class: X.Org Video Driver
[ 90452.577] (II) NVIDIA dlloader X Driver  304.108  Wed Jul 31 19:36:56 PDT 2013
[ 90452.577] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 90452.577] (--) using VT number 7

[ 90452.579] (II) Loading sub module "fb"
[ 90452.579] (II) LoadModule: "fb"
[ 90452.580] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 90452.580] (II) Module fb: vendor="X.Org Foundation"
[ 90452.580]    compiled for 1.14.3, module version = 1.0.0
[ 90452.580]    ABI class: X.Org ANSI C Emulation, version 0.4
[ 90452.580] (II) Loading sub module "wfb"
[ 90452.580] (II) LoadModule: "wfb"
[ 90452.580] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[ 90452.580] (II) Module wfb: vendor="X.Org Foundation"
[ 90452.580]    compiled for 1.14.3, module version = 1.0.0
[ 90452.580]    ABI class: X.Org ANSI C Emulation, version 0.4
[ 90452.580] (II) Loading sub module "ramdac"
[ 90452.580] (II) LoadModule: "ramdac"
[ 90452.580] (II) Module "ramdac" already built-in
[ 90452.580] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 90452.580] (==) NVIDIA(0): RGB weight 888
[ 90452.580] (==) NVIDIA(0): Default visual is TrueColor
[ 90452.580] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 90452.581] (**) NVIDIA(0): Enabling 2D acceleration
[ 90452.581] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[ 90452.581] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[ 90452.581] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[ 90452.581] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[ 90452.581] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
[ 90452.706] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
[ 90452.706] (EE) NVIDIA(0):     system's kernel log for additional error messages and
[ 90452.706] (EE) NVIDIA(0):     consult the NVIDIA README for details.
[ 90452.706] (EE) NVIDIA(0):  *** Aborting ***
[ 90452.706] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 90452.706] (II) UnloadModule: "nvidia"
[ 90452.706] (II) UnloadSubModule: "wfb"
[ 90452.706] (II) UnloadSubModule: "fb"
[ 90452.706] (EE) Screen(s) found, but none have a usable configuration.
[ 90452.706] (EE)
Fatal server error:
[ 90452.706] (EE) no screens found(EE)
[ 90452.707] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[ 90452.707] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 90452.707] (EE)
[ 90452.712] (EE) Server terminated with error (1). Closing log file.

The file /usr/share/X11/xorg.conf.d was empty, but the /etc/X11/xorg.conf shows:
Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 304.108  (buildmeister@swio-display-x64-rhel04-06)  Wed Jul 31 20:47:43 PDT 2013


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from data in "/etc/conf.d/gpm"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

And modprobe nvidia still cannot insert 'nvidua': No such device. I am obviously 'not getting it'.

/dev/nvidiactl still does not exist.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sun Nov 10, 2013 8:02 pm    Post subject: Reply with quote

So, for some reason I just decided to reboot after adding my user to the audio, cdrom, wheel, usb, and video groups. And I have booted straight into my KDE gui. True it showed an error about Consolekit
Code:
Warning: Cannot open ColsoleKit session: Unable to open session:Failedto connect to socket /var/run/dbus/system_bus_socket: No such file or diredtory.


I did not have to login through the prompt. It came up to the graphical login instead. That's a first. I'm sure there must be more cleaning up to do, but I will have to study on that. Plus it said that Root logins are not allowed. I've never seen that before. Must be something new.

Thanks guys. And modprobe nvidia still shows nothing. I am puzzled, very puzzled. :roll: I am going to try another reboot just to see if it sticks.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3264
Location: Canada

PostPosted: Sun Nov 10, 2013 9:54 pm    Post subject: Reply with quote

mark2 wrote:
And modprobe nvidia still shows nothing.


What do you mean by that ? It does not suppose to show anything if module is loaded correctly.

The root logins are not allowed is probably ConsoleKit related
Back to top
View user's profile Send private message
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Sun Nov 10, 2013 10:44 pm    Post subject: Reply with quote

Quote:
What do you mean by that ? It does not suppose to show anything if module is loaded correctly.

I was not sure of that, but that sounds like it was loaded correctly. And before it showed an error about not being found, so that's good. I am not very knowledgeable when it commands to linux commands and what they are supposed to show. I am forced to live in a Windows world at work, my cross to bear. But when I no longer have to put up with that, you can bet I'll be sticking with Gentoo. I really like it because it can be tailored to fit just what I need.

Now I just have to get my CDRom and USB devices working. But I will visit other topics to dig into those issues.

I think I may need to emerge grub:2 again, just to be sure. I have been able to use the chainloader for that as well as the grub 0.97, so that remains the last thing in this area.

Thanks, and if there any other suggestions, I am more than glad to follow up. For now I will go back to the migration guide and hope it takes care of things. :D
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3264
Location: Canada

PostPosted: Sun Nov 10, 2013 11:50 pm    Post subject: Reply with quote

mark2 wrote:
Quote:
What do you mean by that ? It does not suppose to show anything if module is loaded correctly.

I was not sure of that, but that sounds like it was loaded correctly. And before it showed an error about not being found, so that's good. I am not very knowledgeable when it commands to linux commands and what they are supposed to show. I am forced to live in a Windows world at work, my cross to bear. But when I no longer have to put up with that, you can bet I'll be sticking with Gentoo. I really like it because it can be tailored to fit just what I need.

Now I just have to get my CDRom and USB devices working. But I will visit other topics to dig into those issues.

I think I may need to emerge grub:2 again, just to be sure. I have been able to use the chainloader for that as well as the grub 0.97, so that remains the last thing in this area.

Thanks, and if there any other suggestions, I am more than glad to follow up. For now I will go back to the migration guide and hope it takes care of things. :D


Right, just as a general info, if you want to see the results of kernel module insersion, look at the output of 'dmesg'. (if you 'modprobe nvidia' and do dmesg right after, then the end of the output will have info about nvidia initialization). Also 'cat /proc/modules' is useful to see all succesfully loaded kernel modules.

One should also remember that nvidia kernel module, and nvidia graphics module (loaded by X and logged in /var/log/Xorg.0.log) are two separate things.

If you want to boot for some debugging purposes into console and not straight into GUI, remove /etc/init.d/xdm from default level ( 'rc-update del xdm default')
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Mon Nov 11, 2013 2:38 pm    Post subject: Reply with quote

mark2 wrote:
So, for some reason I just decided to reboot after adding my user to the audio, cdrom, wheel, usb, and video groups. And I have booted straight into my KDE gui. True it showed an error about Consolekit
Code:
Warning: Cannot open ColsoleKit session: Unable to open session:Failedto connect to socket /var/run/dbus/system_bus_socket: No such file or diredtory.


I did not have to login through the prompt. It came up to the graphical login instead. That's a first. I'm sure there must be more cleaning up to do, but I will have to study on that. Plus it said that Root logins are not allowed. I've never seen that before. Must be something new.

Thanks guys. And modprobe nvidia still shows nothing. I am puzzled, very puzzled. :roll: I am going to try another reboot just to see if it sticks.


You need to make sure the consolekit and dbus USE flags are enabled in KDE

Code:
emerge ufed
eselect profile list
eselect profile set 6 <-- Should be KDE
ufed
emerge -e system && emerge -e world


This should automatically set the dbus and consolekit USE Flag. The ufed command should verify that.
_________________
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
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Mon Nov 11, 2013 3:19 pm    Post subject: Reply with quote

Ok the Firefox tip worked great. It gave me version 24.0, guess 25 hasn't been packaged yet for Gentoo.

@dmpogo: Also, the dmesg following modprobe nvidia pulls up some very interesting info. And is there some way I can pull the text out of dmesg as well as cat /proc/modules so that I can post when needed?

Am running
Code:
emerge -e system && emerge -e world

That's going to take a while to finish.

Btw, the ufed is really a neat tool. I never knew about that one. Thanks, eyoung100.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3264
Location: Canada

PostPosted: Mon Nov 11, 2013 4:28 pm    Post subject: Reply with quote

mark2 wrote:


@dmpogo: Also, the dmesg following modprobe nvidia pulls up some very interesting info. And is there some way I can pull the text out of dmesg as well as cat /proc/modules so that I can post when needed?



both 'dmesg' and 'cat' output info into stdout (standard output), so simple redirect will do

Code:

dmesg > yourfilename
cat /proc/modules > otherfilename
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Mon Nov 11, 2013 6:01 pm    Post subject: Reply with quote

To add to dmpogo's post. There is also a tool named wgetpaste that's used in conjunction with the pipe operator as in:
Code:
wgetpaste | <command>
as in
Code:
wgetpaste | dmesg


then post the URL here.
_________________
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
mark2
Apprentice
Apprentice


Joined: 22 May 2012
Posts: 293
Location: South Carolina

PostPosted: Mon Nov 11, 2013 6:35 pm    Post subject: Reply with quote

@dmpogo: That's extremely useful to know.

And @eyoung100: I have the wgetpaste and I used it to copy and paste here, but I did not know that it would do a <command> as well. Also a great piece of information.

Just looked at the last emerge screen, going on 300 or 466 packages. Should be done by the time I get home from work. I'll do a reboot then and see if I still get the ConsoleKit message.

Thanks.

11/12/13 - Late edit post: Must have read something wrong. It is still running and saying 654 of 873. Now I don't have any idea of when it will complete.
_________________
Thanks,
Mark
__________________________________________________________________
"Flying is learning how to throw yourself at the ground and miss." - Douglas Adams
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 3 of 5

 
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