gnome-shell hang

If you are new to Linux or new to Sabayon Linux and just not sure where to post, here ya go. Post without fear of being told to RTFM :-)

Moderator: Moderators

Re: gnome-shell hang

Postby doobydave » Sun Apr 22, 2012 20:03

Code: Select all
[    23.836] (II) NVIDIA(0): Computing DPI using physical size from Idek Iiyama (CRT-1)'s
[    23.836] (II) NVIDIA(0):     EDID and first mode to be programmed on Idek Iiyama
[    23.836] (II) NVIDIA(0):     (CRT-1):
[    23.836] (II) NVIDIA(0):   width  : 1280 pixels  400  mm (DPI: 81)
[    23.836] (II) NVIDIA(0):   height : 960  pixels  300  mm (DPI: 81)
[    23.836] (--) NVIDIA(0): DPI set to (81, 81); computed from "UseEdidDpi" X config
[    23.836] (--) NVIDIA(0):     option
[    23.836] (**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[    23.836] (--) Depth 24 pixmap format is 32 bpp
[    23.836] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[    23.837] (II) NVIDIA(0): Initialized GPU GART.
[    23.839] (II) NVIDIA(0): kernel module enabled successfully
[    23.839] (II) NVIDIA(0): GPU initialized
[    23.839] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    23.839] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    23.839] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    23.839] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    23.839] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    23.839] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    23.839] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    23.839] (II) NVIDIA(0):     Config Options in the README.
[    23.843] (II) NVIDIA(0): Setting mode "1280x960+0+0"
[    23.871] (II) NVIDIA(0): First mode initialized
[    23.903] (II) NVIDIA(0): Using built-in logo image.
[    23.903] (II) NVIDIA(0): Logo is 744x537 with depth 24.
[    23.914] (II) Loading extension NV-GLX
[    23.936] (II) NVIDIA(0): Initialized OpenGL Acceleration
[    23.944] (II) NVIDIA(0): Visuals set up
[    23.944] (II) NVIDIA(0): Pixmap depths set up
[    23.948] (II) NVIDIA(0): GLX visuals set up
[    23.948] (II) NVIDIA(0): Framebuffer set up
[    23.955] (==) NVIDIA(0): Disabling shared memory pixmaps
[    23.955] (II) NVIDIA(0): Initialized X Rendering Acceleration
[    23.955] (II) NVIDIA(0): Composite wrapper disabled.
[    23.955] (==) NVIDIA(0): Backing store disabled
[    23.955] (==) NVIDIA(0): Silken mouse enabled
[    23.955] (II) NVIDIA(0): Default colormap initialized.
[    23.955] (II) NVIDIA(0): Palette loaded
[    23.955] (==) NVIDIA(0): DPMS enabled
[    23.955] (II) Loading extension NV-CONTROL
[    23.955] (II) Loading extension XINERAMA
[    23.955] (II) Loading sub module "dri2"
[    23.955] (II) LoadModule: "dri2"
[    23.956] (WW) Warning, couldn't open module dri2
[    23.956] (II) UnloadModule: "dri2"
[    23.956] (II) Unloading dri2
[    23.956] (EE) NVIDIA: Failed to load module "dri2" (module does not exist, 0)
[    23.956] (II) NVIDIA(0): Failed to load the DRI2 module.
[    23.956] (II) NVIDIA(0): The X server will not be able to send the VDPAU driver name to
[    23.956] (II) NVIDIA(0):     libvdpau.
[    23.956] (II) NVIDIA(0): Screen initialization complete
[    23.956] (==) RandR enabled
[    23.956] (II) Initializing built-in extension Generic Event Extension
[    23.956] (II) Initializing built-in extension SHAPE
[    23.956] (II) Initializing built-in extension MIT-SHM
[    23.956] (II) Initializing built-in extension XInputExtension
[    23.956] (II) Initializing built-in extension XTEST
[    23.956] (II) Initializing built-in extension BIG-REQUESTS
[    23.956] (II) Initializing built-in extension SYNC
[    23.956] (II) Initializing built-in extension XKEYBOARD
[    23.956] (II) Initializing built-in extension XC-MISC
[    23.956] (II) Initializing built-in extension XINERAMA
[    23.956] (II) Initializing built-in extension XFIXES
[    23.956] (II) Initializing built-in extension RENDER
[    23.956] (II) Initializing built-in extension RANDR
[    23.956] (II) Initializing built-in extension COMPOSITE
[    23.956] (II) Initializing built-in extension DAMAGE
[    23.957] (II) Initializing extension GLX
[    24.794] (II) XKB: Reusing cached keymap
[    24.804] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    24.804] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    24.804] (II) LoadModule: "evdev"
[    24.804] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    24.817] (II) Module evdev: vendor="X.Org Foundation"
[    24.817]    compiled for 1.11.4, module version = 2.7.0
[    24.817]    Module class: X.Org XInput Driver
[    24.817]    ABI class: X.Org XInput driver, version 13.0
[    24.817] (II) Using input driver 'evdev' for 'Power Button'
[    24.817] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    24.817]    Option "XkbRules" "evdev"
[    24.817]    Option "XkbModel" "evdev"
[    24.817]    Option "XkbLayout" "us"
[    24.817]    Option "_source" "server/udev"
[    24.817]    Option "name" "Power Button"
[    24.817]    Option "path" "/dev/input/event1"
[    24.817]    Option "device" "/dev/input/event1"
[    24.817]    Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[    24.817]    Option "driver" "evdev"
[    24.817] (**) Power Button: always reports core events
[    24.817] (**) evdev: Power Button: Device: "/dev/input/event1"
[    24.826] (--) evdev: Power Button: Vendor 0 Product 0x1
[    24.826] (--) evdev: Power Button: Found keys
[    24.826] (II) evdev: Power Button: Configuring as keyboard
[    24.826] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[    24.826] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    24.826] (**) Option "xkb_rules" "evdev"
[    24.826] (**) Option "xkb_model" "evdev"
[    24.826] (**) Option "xkb_layout" "us"
[    24.844] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    24.844] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    24.844] (II) Using input driver 'evdev' for 'Power Button'
[    24.844] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    24.844]    Option "XkbRules" "evdev"
[    24.844]    Option "XkbModel" "evdev"
[    24.844]    Option "XkbLayout" "us"
[    24.844]    Option "_source" "server/udev"
[    24.844]    Option "name" "Power Button"
[    24.844]    Option "path" "/dev/input/event0"
[    24.844]    Option "device" "/dev/input/event0"
[    24.844]    Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[    24.844]    Option "driver" "evdev"
[    24.844] (**) Power Button: always reports core events
[    24.844] (**) evdev: Power Button: Device: "/dev/input/event0"
[    24.855] (--) evdev: Power Button: Vendor 0 Product 0x1
[    24.855] (--) evdev: Power Button: Found keys
[    24.855] (II) evdev: Power Button: Configuring as keyboard
[    24.855] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[    24.855] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    24.855] (**) Option "xkb_rules" "evdev"
[    24.855] (**) Option "xkb_model" "evdev"
[    24.855] (**) Option "xkb_layout" "us"
[    24.855] (II) XKB: Reusing cached keymap
[    24.855] (II) config/udev: Adding input device Logitech Optical USB Mouse (/dev/input/event3)
[    24.855] (**) Logitech Optical USB Mouse: Applying InputClass "evdev pointer catchall"
[    24.855] (II) Using input driver 'evdev' for 'Logitech Optical USB Mouse'
[    24.855] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    24.855]    Option "XkbRules" "evdev"
[    24.855]    Option "XkbModel" "evdev"
[    24.855]    Option "XkbLayout" "us"
[    24.855]    Option "_source" "server/udev"
[    24.855]    Option "name" "Logitech Optical USB Mouse"
[    24.855]    Option "path" "/dev/input/event3"
[    24.855]    Option "device" "/dev/input/event3"
[    24.855]    Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input3/event3"
[    24.855]    Option "driver" "evdev"
[    24.855] (**) Logitech Optical USB Mouse: always reports core events
[    24.855] (**) evdev: Logitech Optical USB Mouse: Device: "/dev/input/event3"
[    24.862] (--) evdev: Logitech Optical USB Mouse: Vendor 0x46d Product 0xc016
[    24.862] (--) evdev: Logitech Optical USB Mouse: Found 3 mouse buttons
[    24.862] (--) evdev: Logitech Optical USB Mouse: Found scroll wheel(s)
[    24.862] (--) evdev: Logitech Optical USB Mouse: Found relative axes
[    24.862] (--) evdev: Logitech Optical USB Mouse: Found x and y relative axes
[    24.862] (II) evdev: Logitech Optical USB Mouse: Configuring as mouse
[    24.862] (II) evdev: Logitech Optical USB Mouse: Adding scrollwheel support
[    24.862] (**) evdev: Logitech Optical USB Mouse: YAxisMapping: buttons 4 and 5
[    24.862] (**) evdev: Logitech Optical USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    24.862] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input3/event3"
[    24.862] (II) XINPUT: Adding extended input device "Logitech Optical USB Mouse" (type: MOUSE, id 8)
[    24.862] (II) evdev: Logitech Optical USB Mouse: initialized for relative axes.
[    24.862] (**) Logitech Optical USB Mouse: (accel) keeping acceleration scheme 1
[    24.862] (**) Logitech Optical USB Mouse: (accel) acceleration profile 0
[    24.862] (**) Logitech Optical USB Mouse: (accel) acceleration factor: 2.000
[    24.862] (**) Logitech Optical USB Mouse: (accel) acceleration threshold: 4
[    24.862] (II) config/udev: Adding input device Logitech Optical USB Mouse (/dev/input/mouse0)
[    24.862] (II) No input driver specified, ignoring this device.
[    24.862] (II) This device may have been added with another device file.
[    24.862] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event2)
[    24.862] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[    24.862] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    24.862] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    24.862]    Option "XkbRules" "evdev"
[    24.862]    Option "XkbModel" "evdev"
[    24.862]    Option "XkbLayout" "us"
[    24.862]    Option "_source" "server/udev"
[    24.862]    Option "name" "AT Translated Set 2 keyboard"
[    24.862]    Option "path" "/dev/input/event2"
[    24.862]    Option "device" "/dev/input/event2"
[    24.862]    Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input2/event2"
[    24.862]    Option "driver" "evdev"
[    24.862] (**) AT Translated Set 2 keyboard: always reports core events
[    24.862] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event2"
[    24.868] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[    24.868] (--) evdev: AT Translated Set 2 keyboard: Found keys
[    24.868] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[    24.868] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input2/event2"
[    24.868] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[    24.868] (**) Option "xkb_rules" "evdev"
[    24.868] (**) Option "xkb_model" "evdev"
[    24.868] (**) Option "xkb_layout" "us"
[    24.868] (II) XKB: Reusing cached keymap
[    24.868] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[    24.868] (II) No input driver specified, ignoring this device.
[    24.868] (II) This device may have been added with another device file.
[   578.782] (II) NVIDIA(0): Setting mode "1280x960+0+0"
[   578.840] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   578.840] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   578.840] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   578.840] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   578.840] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   578.840] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   578.840] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   578.840] (II) NVIDIA(0):     Config Options in the README.
doobydave
Young Hen
 
Posts: 32
Joined: Wed Feb 02, 2011 16:49

Re: gnome-shell hang

Postby doobydave » Sun Apr 22, 2012 20:07

I do have a hunch it's down to incorrect monitor detection.
After I have had something to eat I will dig out another monitor to see if it makes a difference.
doobydave
Young Hen
 
Posts: 32
Joined: Wed Feb 02, 2011 16:49

Re: gnome-shell hang

Postby mélodie » Sun Apr 22, 2012 20:22

doobydave wrote:I do have a hunch it's down to incorrect monitor detection.
After I have had something to eat I will dig out another monitor to see if it makes a difference.


I have copied your different pastes to pastebin:
http://pastealacon.com/30124

I didn't think you would have a log that big. I see only 2 warnings related to the dri and dri2 which could not be loaded and no error:
[ 21.797] (II) LoadModule: "dri"
[ 21.798] (WW) Warning, couldn't open module dri
[ 21.798] (II) UnloadModule: "dri"
[ 21.798] (II) Unloading dri
[ 21.798] (EE) Failed to load module "dri" (module does not exist, 0)


[ 22.497] (WW) Warning, couldn't open module dri2
[ 22.497] (II) UnloadModule: "dri2"
[ 22.497] (II) Unloading dri2
[ 22.497] (EE) Failed to load module "dri2" (module does not exist, 0)


and you are right about the monitor, it does not like it:
[ 22.736] (**) NVIDIA(0): Enabling 2D acceleration
[ 23.707] (II) NVIDIA(GPU-0): Display (Idek Iiyama (CRT-1)) does not support NVIDIA 3D


When you have updated, I suppose you had mesa 8.0.2 (you can check with a grep against /var/log/entropy/entropy.log). I wonder if you would not have a system working better with a more recent couple kernel/driver ?

If someone else sees something else... I bring here the very little I believe I know.
mélodie
Simple Hen
 
Posts: 97
Joined: Tue Feb 14, 2012 10:41

Re: gnome-shell hang

Postby oboedad55 » Mon Apr 23, 2012 5:00

I'm wondering why you're on kernel 2.6.37 and I'm on 3.3.0. If it were me I would start by updating the kernel as explained in the wiki, then installing the corresponding Nvidia driver. Maybe there is something I don't understand, but in all my years of computing I've never seen a problem where a monitor caused the situation you describe. Perhaps I've just been lucky.
Registered Linux user #436067
-----------------------------------
Linux assumes you know exactly what you are doing.
oboedad55
Baby Hen
 
Posts: 18
Joined: Thu Feb 28, 2008 17:55

Re: gnome-shell hang

Postby mélodie » Mon Apr 23, 2012 6:56

oboedad55 wrote:I'm wondering why you're on kernel 2.6.37 and I'm on 3.3.0. If it were me I would start by updating the kernel as explained in the wiki, then installing the corresponding Nvidia driver. Maybe there is something I don't understand, but in all my years of computing I've never seen a problem where a monitor caused the situation you describe. Perhaps I've just been lucky.


Hi,

At the forum and Entropy wiki page they said to use the kernel-switcher program, as root in console...

Yes, you have been lucky : some screens send wrong messages to the system... that happens.
mélodie
Simple Hen
 
Posts: 97
Joined: Tue Feb 14, 2012 10:41

Re: gnome-shell hang

Postby oboedad55 » Mon Apr 23, 2012 7:19

mélodie wrote:
oboedad55 wrote:I'm wondering why you're on kernel 2.6.37 and I'm on 3.3.0. If it were me I would start by updating the kernel as explained in the wiki, then installing the corresponding Nvidia driver. Maybe there is something I don't understand, but in all my years of computing I've never seen a problem where a monitor caused the situation you describe. Perhaps I've just been lucky.


Hi,

Yes, you have been lucky : some screens send wrong messages to the system... that happens.


You've seen an incorrect monitor resolution hang a system?
Registered Linux user #436067
-----------------------------------
Linux assumes you know exactly what you are doing.
oboedad55
Baby Hen
 
Posts: 18
Joined: Thu Feb 28, 2008 17:55

Re: gnome-shell hang

Postby doobydave » Mon Apr 23, 2012 11:21

I borrowed a TFT monitor, and (hunch disproved..) I am still getting the same problem.

Is it worth upgrading the kernel?
doobydave
Young Hen
 
Posts: 32
Joined: Wed Feb 02, 2011 16:49

Re: gnome-shell hang

Postby oboedad55 » Mon Apr 23, 2012 16:54

doobydave wrote:I borrowed a TFT monitor, and (hunch disproved..) I am still getting the same problem.

Is it worth upgrading the kernel?


Certainly, especially on a rolling-release system the first order of business is to get the system up-to-date. Then install the correct drivers for the new kernel. It's in the all-mighty wiki.
Registered Linux user #436067
-----------------------------------
Linux assumes you know exactly what you are doing.
oboedad55
Baby Hen
 
Posts: 18
Joined: Thu Feb 28, 2008 17:55

Re: gnome-shell hang

Postby doobydave » Tue Apr 24, 2012 13:27

Thanks for your help, and whilst part of me feels I should continue trying to get to the bottom of this (and undoubtably become more knowledgeable about linux..), another part of me has just ordered an SSD drive, so I imagine there will be some re-installing to do.
doobydave
Young Hen
 
Posts: 32
Joined: Wed Feb 02, 2011 16:49

Re: gnome-shell hang

Postby doobydave » Tue Apr 24, 2012 18:10

You've seen an incorrect monitor resolution hang a system?


Maybe not technically, but my monitor is capable of rendering many a (more recent) distro utterly unusable.
doobydave
Young Hen
 
Posts: 32
Joined: Wed Feb 02, 2011 16:49

PreviousNext

Return to Beginners|Newbies Area

Who is online

Users browsing this forum: No registered users and 2 guests