Gnome 3 / GPU problem

Dear archusers,
Another question. Gnome 3 boots, but that's it. whenever I even click the bar on the top it crashes. \
My GPU might be too old or just not installed correctly. I'm using a radeon 7000 IGP.
I tried to install it by installing # pacman -S xf86-video-ati. do i need to install or config anything more besides this?
KDE also isn't that smooth.
thanks
Last edited by archwill (2011-06-26 20:19:37)

Thank you, I'll try something like dmesg > boot.messages and post it here.
edit:
http://gamerneeds.org/errorlog
Last edited by archwill (2011-06-27 07:22:20)

Similar Messages

  • GPU Problems with my GT60 2OC-024US

    Hi guys!
    A couple of days ago, I opened up my GT60 to add a new SSD I bought and, since I was opening it up, I also repasted the GPU and CPU. It was the first time I was doing it on this computer, but its not the first time I do a repasting on a pc. So, everything went smoothly, changed the paste, put the heatsink back in place, and then, when I tried to boot the PC, it got stuck after posting, like waiting from a response from the GPU I guess...
    Tried a couple of reboots and nothing worked, so then i proceeded to enter in safe mode to check if it was only a GPU problem and it was. With the integrated graphics i was able to uninstall NVIDIA drivers and then, voilá, I booted normally without problems, EXCEPT, of course, I cant use the dedicated gpu.
    Already tried all kinds of drivers, tried opening it up again, repasting, reconnecting the GPU, and nothing works. As soon as the OS tries to use the dedicated GPU (after I install NVIDIA's drivers) the same problem appears. So it seems something has happened with it.
    Any ideas or insight on this? I don't know how to proceed. I bought the notebook on the USA but I live in Argentina and i'm not sure if there's official RMA or something around here.
    Thanks a lot!

    Did you ever think it might be a SSD compatilibty problem?
    What is your SSD brand & model?  Have you check that SSD website and see if there is firmware update?
    http://www.msi.com/page/service-location/#n-tab1
    Argentina
    Address: Av. Corrientes 4006 1 er piso Oficina 9 – Capital Federal – Buenos Aires
    TEL: (54) 11 4139 6049
    Website: http://WWW.Z-NET.COM.AR/
    You can also register on MSI service page and ask for help there.
    https://register.msi.com/

  • AE CS6 crashes at startup - indicating GPU problem

    Hi,
    I am new to the Abobe suite. Using a MacPro running 10.7 Lion, Intel based processors. Using a Radeon ATI 6xxx video card (2 monitors connected via mini-display, HDMI not used at the moment). Installed AE properly (support desk Adobe verified this remotely). AE CS6 is crashing at startup, indicating a GPU problem. Support desk Adobe has advised to contact 'the Mac guys' in order to see if an update to the video card driver might resolve the issue. Mac support is confirming my system to be fully up to date. From other topics on this forum I noticed more people are suffering (or have suffered) the same problem. However I haven't seen any firm/clear resolution to this problem.
    Can anyone tell me (in simple language) what I can do in order to get this configuration to work (ideally without having to replace my Graphics Card - as I believe it is a rather new model that I would expect to be supported)?
    Thanks in advance,
    Marcel

    Begin by giving us more information, including answering all of the questions here:
    http://forums.adobe.com/thread/961743
    Be sure to tell us the exact version number for your display driver.

  • Has the Asus G71GX-RX05 GPU problem been fixed?

    Has the Asus G71GX-RX05 GPU problem been fixed? And if so what do you have to do to fix it.

    hi vanhelsing.
    i know that asus was working on an updated BIOS to fix the GPU issue, and according to the last post in this thread on the asus support forums (http://vip.asus.com/forum/view.aspx?id=20090627114124765&board_id=3&model=G71Gx(BestBuy)&SLanguage=e...), rev. 1201 seems to have done the trick.
    i checked the asus support website (http://support.asus.com), and i found that there is an even new version of the BIOS - rev. 1302. i would recommend moving to this BIOS upon unboxing your G71GX.
    i have updated the BIOS on both notebooks and desktops before, and the process is fairly painless. i found this link off the asus support site (http://support.asus.com/technicaldocuments/technicaldocuments.aspx?root=198&SLanguage=en-us), and it describes how to update the BIOS. i would recommend having a conversation with your local geek squad if you're not comfortable doing the process yourself.

  • Backlight AND GPU Problems? ARGHHHH

    Even though my iBook G3 800 MHz has been having the flickering screen, lines, and freezes common of the GPU problem for about 6 months, it's been tolerable. I just told myself as soon as I couldn't deal with it, I'd send it in. Well, I wouldn't be posting this right now, if my backlight hadn't gone out. I opened it up, and it looks to me like it's the "pinched inverter cable" problem. So, I guess it's time to send it in. Problem is, I don't have the money to send it to Apple, but I really don't think I'm handy enough to fix it myself.
    My question is, does anyone know a reputable website or company that would fix this sort of thing (I actully can live with the GPU problem, they don't need to fix that) cheaper then Apple?
    Thanks in advance

    You may want to try DT & T Computer Services, but don't go halfway with it. Have them fix it completely or don't even bother sending it in. Why? Because one week after you get it back, that logic board could quit on you completely. Mine got so I could only use it 20 minutes a day.
    If you ask, they may give you a discount on fixing the cable/logic board problem at the same time, since they only have to open it once. You could ask (I would.)
    Good luck.

  • MAC OS X + stage.fullScreenSourceRect + renderMode set to GPU = problem with mouse position

    When setting stage.fullScreenSourceRect, stage.displayState to StageDisplayState.FULL_SCREEN_INTERACTIVE; and renderMode to GPU, mouse position is read incorrectly. This is not only for mouseX and mouseY position, but also all the mouse interactions with Sprites, Buttons etc are not working correctly.
    Anybody know a solution for this issue?
    Here is the bug reported, but there is no response yet.
    https://bugbase.adobe.com/index.cfm?event=bug&id=3486120
    Greg.

    Bump up.
    Anybody has the same problem and have an idea how to fix it? Or please just check if you have the same problem.. I'm going to submit my game "Amelia and Terror of the Night" (successfully added to iOS store) to MAC App Store but can't do it while this problem appears.
    I am disappointed nobody  even verified the bugs I submitted at  the bugbase.adobe.com for AIR 3.5 and 3.6
    thanks
    Greg

  • [Solved] gnome install problem

    Fresh install of Arch and I'm trying to get gnome installed, I've done it before without a problem but today when I try to install gnome "pacman -S gnome" it says "error: target not found: gnome" I have the [extra] repo enabled so I'm not sure what the problem is.
    Last edited by nixbin (2012-04-24 22:02:42)

    Do:
    pacman repository syncronization
    sudo pacman -Syu
    Then:
    Gnome Wiki
    sudo pacman -S gnome
    Last edited by headkase (2012-04-24 21:47:26)

  • Gnome-terminal problems

    Hi there,after upgrade to gnome-terminal 3.12.1-1,I found some errors appears :
    First, when I want to open a new terminal use my custom shortcuts Ctrl+Alt+T,sometimes it will make the whole screen freeze, and I have to switch to another TTY to kill it.Then I check my system log, there are many warnings like:
    org.gnome.Terminal[958]: (gnome-terminal-server:7346): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref 0x7faec0b2c420(0x14e1550)
    Is there something wrong ?I also try to compile it by myself , but it gives a warning:
    server.c: In function ‘main’:
    server.c:113:5: warning: ignoring return value of ‘chdir’, declared with attribute warn_unused_result [-Wunused-result]
         (void) chdir ("/");
         ^
    are all the problems caused by this ?How could I handle this, can anyone fix that?Thanks for your works.Sorry for my poor English.

    That compiler warning is probably benign (harmless).  The function appears to change the working directory and then return a void pointer.  The pointer is not used because, apparently, in this case it is not needed.

  • [Solved]Gnome settings problem

    Hi all.
    I have some strange problems with Gnome 3.2, it is hard to explain but these screenshots should:
    http://bildr.no/image/1012613.jpeg
    http://bildr.no/image/1012614.jpeg
    In the first picture you can see that something that is selected by default is pink, this happens all over Gnome. In the second one you can see that in nautilus when I want to select with the mouse it creates a white block so you can't see behind. I know it is a settings problem because the same doesn't happen on a new account, but the problem is that I have tried to delete .gnome2/ .gconf and .config but once I start to customize again the problem reappers. So I was wondering if there is anything else that I can try to delete without deleting the whole account or if there is some settings that I could to to remove this problem.
    Thanks in advanced
    Mod edit: The included images are too big, see our forum etiquette about this. For  screenshot posting rules you may also look here.
    Last edited by nordmoen (2011-11-01 13:57:18)

    caligo wrote:If you launch a GTK3 app from the terminal, are there any GTK related error messages (e.g. CSS errors)?
    Yes!
    Havn't noticed that before:
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:620:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:626:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:632:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:639:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:645:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:651:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:657:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:663:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:669:27: Whitespace between 'url' and '(' is deprecated
    (gnome-system-monitor:3153): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:675:27: Whitespace between 'url' and '(' is deprecated

  • [SOLVED] GNOME 3 problem when typing to find application

    Hi everybody,
    Last night i tried to open an application in GNOME 3 (the last version available), then i pressed the windows key (activities) and tried to type the name of the app. When i typed the second character (i think), the UI restarted, and once i tried it again, it crashed. I tried to disable/uninstall the extensions i currently have in GNOME , but it didn't fix the problem.
    Is there a problem with some updates with GNOME?
    Thank you for your help.
    Jaime
    Last edited by japenagosc (2012-02-19 12:57:56)

    Kaurin wrote:
    btw rolling back to the previous driver solves it (temporarily)
    cd /var/cache/pacman/pkg
    sudo pacman -U nvidia-utils-290.10-1-x86_64.pkg.tar.xz nvidia-290.10-3-x86_64.pkg.tar.xz
    and any other nvidia-related packages. I had one more:
    sudo pacman -U opencl-nvidia-290.10-1-x86_64.pkg.tar.xz
    reboot. voila.
    Great, thanks! Now i have a *newbie* problem. How do i downgrade nvidia if i have
    pacman -Scc
    Last edited by japenagosc (2012-02-19 04:46:27)

  • Apple gurus please help. GPU problems

    Hi everyone. Having a horrible gpu issue and cannot find a solution anywhere. I have one of the 2008 Macbook Pros with the dreaded 8600 gpu. If I run any OS past 10.6.3 I get artifacts on my display. But, with 10.6.3 all is pretty much ok except for watching movies from dvd or my drive. youtube video no problem full screen. The minute I go to 10.6.8 it's back to artifacts on certain web pages and youtube video. Lion to Mavericks I get artifacts on EVERYTHING. It seems to me that something in the 10.6.8 update and up is taxing the faulty gpu but I cannot figure out what. I don't mind sticking with Snow kitty but would like to have at least 10.6.8 for iTunes 11 so I can use my iphone sync. Any ideas or solutions? I tried updating to 10.6.8 and then using the old 10.6.3 video kexts but that didn't work and I had to reinstall. And I can't afford a new Mac or repair right now. Thanks in advance!

    Make an appointment at an Apple store genius bar and have them test you MBP and define what is exactly wrong with it.  The evaluation will be FREE!
    Ciao.

  • Help With PS Cs4 GPU Problem Can't see photo

    I have an problem with the graphics card acceleration. It detects my video card but when i enabled it, and go open a photo, the photo opens but can't see no photo. I can see that i'm zooming in and out of the photo but nothing, the only thing i see is gray. Nothing more. And when i close PS, and then open it again it tells me to go to the manufacturer's site to update the latest drivers. And i have already installed the latest but the same problem.
    I hope you guys can help me out...
    Pc Specs
    Intel Core 2 Quad Q9300 2.50GHz
    RAM 8.00GB
    64 Bit Vista Home Premium Service pack 1
    Graphic Card Asus ENGTX 280 1GB
    Graphics GPU Features
    NVIDIA® GeForce GTX280
    PCI Express & PCI Express 2.0 support
    Microsoft DirectX 10 and Shader Model 4.0 support
    OpenGL®2.1 support
    HDCP complian

    Contact NVidia - you need updated drivers, and they may not have posted all the fixes for your model card and OS yet.

  • Macbook Pro Retina 2013 GPU Problem

    So i was surfing on the web, 10 minutes ago i had a warning about my graphics. and here what happened at kernel. Where can i learn detail of problem anybody has idea ?
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 00 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012440  :  0x00000000 0x00000000 0x00100000 0x00000000 0x00000000 0x00200020 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012460  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012480  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000124a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000124c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000124e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012500  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012520  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012540  :  0x00000000 0x00000000 0x00100000 0x00000000 0x00000000 0x00200020 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012560  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012580  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000125a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000125c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000125e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012600  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012620  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012640  :  0x00000000 0x00000000 0x00100000 0x00000000 0x00000000 0x00200020 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012660  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012680  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000126a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000126c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000126e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012700  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012720  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012740  :  0x00000000 0x00000000 0x00100000 0x00000000 0x00000000 0x00200020 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012760  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x00012780  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000127a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000127c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x000127e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOX MMIO Registers
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: -------------------------------------------------
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: COMMAND_VECS_HWS_PGA                : 0x10204000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: RING_BUFFER_VECS_RING_TAIL          : 0x000066d0
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: RING_BUFFER_VECS_RING_HEAD          : 0x008066c0
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: RING_BUFFER_VECS_RING_START         : 0x10235000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: RING_BUFFER_VECS_RING_CTL           : 0x0000f401
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VEBSYNC                     : 0x00055f98
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VERSYNC                     : 0x0015a852
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VEVSYNC                     : 0x00008d9e
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_RC_PSMI_CTRL             : 0x00000010
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_RC_PWRCTX_MAXCNT         : 0x0000000a
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_VECS_IPEIR               : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_VECS_IPEHR               : 0x0b160001
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_VECS_INSTDONE            : 0xfffffffe
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_VECS_ACTHD               : 0x008066cc
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOXDEBUG_VECS_DMA_FADD            : 0x1023b6c0
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: IDENTIFICATION_VECS_NOPID           : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VECS_HWSTAM                 : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VECS_MI_MODE                : 0x00000200
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VECS_IMR                    : 0xfffffbff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VECS_EIR                    : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VECS_EMR                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: CONTROL_VECS_ESR                    : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOX_VECS_INSTPM                   : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: BATCHBUFF_VECS_BB_STATE             : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: BATCHBUFF_VECS_BB_ADDR              : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: PAGETABLE_VECS_PP_DCLV              : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: PAGETABLE_VECS_PP_DIR_BASE          : 0x10000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: VEBOX_TIMESTAMP                     : 0xc041d253
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: MMIO Offset:
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: ------------
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a000  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a020  :  0x00000000 0x00000000 0x00000000 0x00000000 0x000066d0 0x008066c0 0x10235000 0x0000f401
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a040  :  0x00055f98 0x0015a852 0x00008d9e 0x00000000 0x00000010 0x0000000a 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a060  :  0x00000000 0x00000000 0x0b160001 0xfffffffe 0x00000000 0x008066cc 0x1023b6c0 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a080  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0xffffffff 0x00000200
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a0a0  :  0x00000000 0x00000000 0xfffffbff 0x00000000 0x00000000 0xffffffff 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a0c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a0e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a100  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a120  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a140  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a160  :  0x00000000 0xffffffff 0x00000000 0x00000000 0x00000000 0x00000000 0xffffffff 0x00150000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a180  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a1a0  :  0x00004800 0x00004900 0x00040002 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a1c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a1e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a200  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a220  :  0xffffffff 0x00000000 0x10000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a240  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a260  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a280  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000200
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a2a0  :  0x00080000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a2c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a2e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a300  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a320  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a340  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0xc041d67d 0x00000009
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a360  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a380  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a3a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a3c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a3e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a400  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a420  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a440  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a460  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a480  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a4a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a4c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a4e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a500  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a520  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a540  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a560  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a580  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a5a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a5c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a5e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a600  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a620  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a640  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a660  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a680  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a6a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a6c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a6e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a700  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a720  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a740  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a760  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a780  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a7a0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a7c0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: 0x0001a7e0  :  0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: OTHER MMIO Registers
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: -------------------------------------------------
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_DFSM                      : 0x20000002
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_DSSM                      : 0x00000001
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_DPFC_CONTROL_SA           : 0x20000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_DPFC_CPU_FENCE_OFFSET     : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_TILECTL                   : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_MISC0                     : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_MGGC                      : 0x00000000
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_MTOLUD                    : 0x7fa00001
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GFX_FLSH_CNTL             : 0x00000211
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_MTOUUD                    : 0x7f600001
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_MBDSM                     : 0x7ba00001
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_MBGSM                     : 0x7b800001
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD0                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD1                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD2                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD3                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD4                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD5                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD6                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD7                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD8                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD9                    : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD10                   : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD11                   : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD12                   : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD13                   : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD14                   : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: SYSCONFIG_GTVTD15                   : 0xffffffff
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: ===========================================================================
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: End Hang Analysis
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: ===========================================================================
    Dec 18 23:35:59 Alps-MacBook-Pro kernel[0]: Trying restart GPU ...
    Dec 18 23:35:59 Alps-MacBook-Pro.local DumpGPURestart[705]: Saved gpuRestart report for kernel to /Library/Logs/DiagnosticReports/Kernel_2014-12-18-233559_Alps-MacBook-Pro.gpuRe start
    Dec 18 23:35:59 Alps-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.auditd[706]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd

    Hi... Under Wi-Fi preferences remove/delete/forgot your current Wi-Fi network and then create new network as if it was the first time you're setting this up for Wi-Fi.  This might help your problem, also you mentioned only your router, you may want to try to restart your modem as well.  Good luck with this!

  • Gnome 3.4 gnome-keyring problem

    hey,
    just upgraded to gnome 3.4.
    First thanks for the hard work over the weekend besides your jobs and private life :-) to bring gnome 3.4.1 to extra.
    i had a problem after log in, that the desktop didn`t come up.
    Found a solution with downgrading gnome-keyring to the version 3.2.2.
    In .xsession-errors there are two lines, which could explain the behaviour:
    /usr/bin/gnome-keyring-daemon: error while loading shared libraries: libgck-1.so.0: cannot open shared object file: No such file or directory
    /usr/bin/gnome-shell: error while loading shared libraries: libgcr-3.so.1: cannot open shared object file: No such file or directory
    Any ideas to get theses libraries?
    Or are there old dependencies, that were not completely deleted?
    regards

    I had a problem with evolution and network manager with the gnome-keyring 3.4.1 update. A downgrade to 3.2.2-3 worked, but I have since re-installed (pacman -S) gnome-keyring followed by gcr. That works. Fyi, resintalling gcr then gnome-keyring did not work for me .

  • Gnome numlockx problem [SOLVED]

    After the installation of the latest release 2009.02 of Arch along with Gnome DE, the numlockx package seems not to work. More precisely, when I restart X and enter my credentials, the numlock's led remains off. Any suggestions?
    Last edited by gpan (2009-04-08 07:04:05)

    Ok ok... all along I thought it was working here.
    There is this GConf key
    /desktop/gnome/peripherals/keyboard/host-<hostname>/0/numlock_on
    that gnome-settings-daemon uses to set the numlock state between sessions if the "remember_numlock_state" key is checked.
    It is supposed to store the current state of the numlock key.  Setting this to true/false will toggle the numlock key state, and vice versa... meaning, pressing the actual numlock key will alter this GConf key as well.  Right now, the latter does not work, because of the current xkb not alerting gnome-settings-daemon when the numlock key is pressed.
    Upgrading to xorg-1.6.0-1 in testing fixed the problem here.
    Last edited by biloky (2009-03-11 14:40:21)

Maybe you are looking for