GNOME 3.12 Power and Graphics Issues

Hello, this is my first post.  Please excuse any stupidity...I didn't mean it.  These issues seem related, so I am going to list them all here.  I have searched extensively for infomation on how to fix these problems over the past few weeks and have come up empty handed.  I will try to mention everything I think is relevant and be as concise as possible (but will probably fail).
My Arch is installed on a desktop system, a GPT partition, no dual boot, and uses GRUB (efi) as boot manager.
My packages are fully updated with both "gnome" and "gnome-extra" groups installed.
Kernel is 3.14.2-1 (also tried 3.14.3 from testing - same behavior)
Video is xf86-video-ati with a Radeon 6670 (same problems with a AMD 7950 and onboard Trinity APU)
I did not use GNOME 3.10 so do not know if these problems existed in previous versions.  I switched to 3.12 from KDE (did a fresh install on a wiped HDD)
Problems:
1. When I boot the computer I see the boot messages and everything is fine.  When it gets done and tries to start GDM the screen turns black for approx 5 seconds and then returns to the boot messages for approx. 3 seconds.  Then the screen goes black again for approx. 10 seconds and finally GDM appears.
2. Any time GDM is open, i.e. I have not logged in yet or have logged out of a previous session, and I go to a tty, log in as root or my user, and type "systemctl stop/restart gdm" the computer freezes (including the tty I am on).
3. The blank screen setting in GNOME settings behaves strangely.  If I let it blank and then move the mouse it shows me that clock screen.  If I press escape and the lock screen is enable the clock plays an upwards animation, shows the lock screen, and when I log it shows my desktop, but for approx. 2 seconds none of my user settings (favorites, date in the clock, etc.) are applied.  After the 2 seconds the settings  violently flash into place.  When the lock screen is not enable (what I want), and I wake the screen I get the clock thing and when I press escape there is no upward animation.  The clock screen goes away immediately and then I get the desktop with the same delay in applying my settings.
4. If the screen is blanked for a long time (it is hard to tell how long) and I move the mouse I get the clock but the computer is frozen.  I can kill X with Ctrl+Alt+Backspace and log back in and everything is normal.
5. Suspend is utterly broken.  If I have both the blank screen and suspend timers turned on in the GNOME settings the screen will blank at the appropriate time but the suspend will never happen.  If I have the blank screen option off and auto suspend on the computer suspends but freezes on the clock screen.  In this case if kill X and log back in the desktop works but I have no graphical effects (fade, zoom, etc.).  As far as I can tell the only way to get them back is to reboot the computer.
5.1 If I type "systemctl suspend" in a terminal the suspend happens, and when I wake the computer I am returned directly to the desktop (no clock), but the same graphics problem occurs.  Reloading the shell or logging in/out does not fix it.
5.2 If I boot using "linux-lts" (currently version 3.10.39-1) and suspend using the GNOME setting I get the clock and can get back into the desktop but have the same graphical effects problem.
5.3 If I edit the idle options in "/etc/systemd/logind.conf" the system becomes unstable (choppy effects, delayed keyboard input).  Even after a reboot.
What I've Noticed:
1. In both Cinnamon and Openbox "systemctl suspend" works as expected.
2. Cinnamon's screen blanking and suspend functions work correctly.
3. I tried lightdm, and when using GNOME no power settings work at all.  It seems these features are intrinsic to GDM now.  However, with lightdm I do not get the log in screen delay durring boot.
4. I tried reinstalling the system thinking maybe something got corrupted somehow but it did not help.
5. I tried removing all user settings files from my home directory and it did not help.
6. There are other things I've done as suggested by the wiki or random forum posts, but none of that helped either and probably isn't worth mentioning.
7. These issues are reproducable consistently with no variation.  I believe that these are bugs in GNOME's code, but thought I'd ask anyway (what do I know?).
There are some interesting things in the system logs, but Google returns nothing useful.  There are tons of things in these logs that look important to me, so if you think a particular one will be helpful please tell me which one.
I have found several things (forum threads, bug reports) that resemble what is happening to me, but they all claim that the problems have been fixed or suggest solutions that are not relevant to me (but have led me to believe that the problem is related to ati graphics).
Thank you for your help.
UPDATE:
It seems this is a problem with GDM.  If I use Lightdm "systemctl suspend" works fine when logged into GNOME.  Screen blanking works fine with Xscreensaver.  Unfortunately Xscreensaver turns the screen off when I'm watching videos, so it is useless to me.  I guess the solution for now is to turn the monitor off when I leave the computer and use a terminal and the sleep command to suspend (logind idle settings don't do anything at all with Lightdm, I guess).  This is a terrible solution, but I guess it will have to do until a fix is released, if it ever is.
Last edited by d81 (2014-05-10 23:28:30)

@Strider:
Concerning the second part: Gnome uses tracker to index music, videos etc. globally.
Which directories are indexed can be configured under system settings > search > [cog menu].
There you can add the /videos folder to the indexed folders.
I'm not sure whether this also solves the first problem.

Similar Messages

  • Windows 7 In Place Upgrade Pre-Windows boot and Graphics issue Alienware M17x

    So I'm having multiple issues here.  The first issue surfaced immediately after I removed and reinserted my graphics card.  For reference The computer in question is an Alienware M17XR3 with an AMD 6870m.  Anyhow, The issue I had then was
    that my built in display showed a black screen (would see a quick flicker of what was supposed to be on it when changing display settings but then a black screen) after Windows botted up.  I could use an external monitor with no problem, and safe mode
    or Windows without graphics drivers allowed everything to run normally.  The on screen display also works normally on boot screens or boot disks such as the windows install disk and Hyrens boot CD.  I am assuming my graphics card is shot.  Either
    that or my motherboard.  Input on this is greatly appreciated.  I do intend to upgrade it myself to a 6970m, but I won't have the money until another 1 or 2 paychecks roll around, and I woulld like to be able to use the on-screen display sooner than
    that.
    Anyhow, to ensure that it is a hardware issue, rather than a software issue, I cleaned old drivers then installed drivers I knew were fully functional.  I did this several times with several driver versions.  Nothing yielded any results.  I
    do not wish to do aclean install unless absolutely necessary or at least not until after the weekend, when I will have time to reinstall my 300+programs, games, themes, mods, etc.  I am not opposed to doing this but I need the computer tonight and
    do not have time to do all that before then.  I'll be using it with an external display tonight, so the graphics issue can wait, however, to test with a clean install, I was using Aomei Partition Assistant to break off some free space as a second partition
    on which I could install a second Windows 7 installation for testing purposes.  I have done this multiple times before.  Unfortunatly, on 4.5 hours of sleep and having been up for about 18 hours straight I wasn't thinking and forgot to plug my laptop
    in.  It lost power during the process and the Windows installation is now totally glitched.  I've tried several fixes all to no avail and would prefer to avoid a clean install until after the weekend.
    In Windows XP, I could boot from the install disk and perform a repair install, similar to the Windows 7 upgrade/in place upgrade.  I would like to do this, but seeing as I cannot access the Windows environment, I'm in a bit of a jam.  I could
    run that program again from mini Windows XP (Hyren's Boot CD) I believe and create the second partition and dual boot.  My question is, can I drop the new Windows folder over the old one or do something similar to avoid losing my programs and files?  Thanks

    Hi,
    Based on my knowledge, we cannot just copy the windows folder to make programs work in the new operating system.
    Hope it helps.
    Regards,
    Blair Deng
    Blair Deng
    TechNet Community Support

  • 7 year, 100+ PC Veteran Stumped ! Power, and performance issues. Full detail included.

    Good morning everyone! (At least it's morning in wonderful Pennsylvania USA!)
    AMD Athlon 64 3200+ (New Castle)
    Thermaltake Venus 12 CPU Cooler w/ Manual Adjust
    MSI "K8T Neo-FIS2R" K8T800
    512MB x 2 Corsair TWINX1024-3200C2PT (Rated 2-3-3-6 1T)
    Antec TruePower 430w PS (+5V@36A +3.3V@28A +12V@20A)
    Gainward Dual DVI w/ VIVO GeForce FX5700 Ultra
    2x Viewsonic 19" VX900 LCD Monitors
    Creative SoundBlaster Audigy Platinum eX
    Plextor 712a Black 12x+/8x- DVD-RW
    Lite-On SOHD-167T Black 16x DVD-ROM
    Western Digital WD740GD 74GB 10,000rpm Raptor SATA
    Western Digital WD2500JB 250GB 7,200rpm 8MB IDE
    Seagate Barracuda ST3200822AS 200GB 7,200rpm 8MB IDE
    Lian-Li PC-65B Black Aluminum Case
    Vantech PCI Slot Fan
    CyberPower 825va Voltage Regulating UPS
    Windows XP Professional SP1a
         There we have it, I think that that is all you need to know to perhaps give opinions and advice. Allow me to elaborate on why I am posting today after browsing this wonderful forum for the last two weeks. (...and by the way, my hat's off to some of you knowledgeable regulars for helping out a lot of newbies and folks in trouble!) Without further adieu:
    Problem #1: POWER ISSUE
    When, or if, I remove AC Power from my PC for whatever reason I run into a problem in which after reconnecting the AC Power and attempting to turn on the computer it goes into a 3-5 second startup loop in which the PC does not post, but rather cycles power to all of the components indefinitely. I notice the LEDs on my optical drives cycling repeatedly ad infinitum until I power off using the 4-second hold method, and then press the power button again. At this point the PC boots up fine, and boots up fine going forward from all restarts and shut downs. How strange? I've never, EVER, encountered something like this before.
    Problem #2: PERFORMANCE ISSUE
    This PC has a handful of serious performace issues.
    3dMark03 scored horribly.
    Prime95 runs ridiculously slow although there are no erros! It runs much more quickly on my work PC which is a PIII 866mhz with 384MB of PC133 RAM.
    I receive, on no regular frequency, or while doing anything in particular, Explorer memory errors. Not BSOD's mind you, but "...blah blah blah referenced memory address xxxxx-xxxxx and could not be written". This causes Explorer to restart itself, blowing away the start menu, task bar, and any Explorer windows open. They reappear, of course, without incident.
    The most off performance issue of all is that when opening an Explorer window for either of my IDE HDs, designated D and E drives, I find that when using the highlighting rectangle tool the Explorer window freezes or lags. I can double-click and open or move/copy files without incident, but if I attempt to highlight by this method this halt or lag occurs.
    Also, since my update of the BIOS from 1.2 to 1.7, and then to 1.8 system startup times prior to Windows loading are HORRID. I have disabled just about everything, and yet the SATA BIOS loads for 5 seconds, and then I must wait 20 seconds for Windows itself to come to the login screen. No other BIOS related issues to report per se, but this is terrible for what should be a blazingly fast computer.
    Now let's see.. what have I tried to do to repair the issues?
    1) 2 BIOS flashes. First from 1.2->1.7, and then from 1.7->1.8. Ostensibly this was just "because". The power user need to have the latest! I noticed the incorrect CPU temperature being reported, however.. This led to me buying this massive ThermalTake HSF to replace my stocker. I also added more thermal goop than I ever have before, as well as a PCI slot fan before I became aware that it was a BIOS issue! GRRRR MSI.
    2) I thought perhaps for the one issue that one of the hard drives was an issue, and even perhaps for power, but I replaced each with new drives and tested all 4 on another PC. NO problems. Also I should perhaps mention that my IDE drives are all hooked up using Antec Cobra cables. Expensive yes, but why the hell not, right? I've never seen a hang-off grounding wire for IDE before. Decided not to use them as I could think of a great place to screw them in, nor have other PC using them had trouble skipping the ground wire.
    3) I unplugged every molex cable, the 4-pin CPU power, and the 20-pin ATX power and rerranged them all - as well as removed and then reinserted the RAM.
    4) I tried changing my memory timings and power management settings, etc in BIOS. Nothing seem to impact the issue. I didn't fiddle with the voltages, but I should not need to running the RAM at SPD or lower settings and without overclocking the system at all!
    5) Another issue that I had that seems to have vanished, come back, vanished, and then come back a "little bit" is my USB ports. When set to enable legacy devices in BIOS my USB items like my Logitech wireless keyboard would just cycle power and refuse to function. Also my UPS connected VIA USB seems to sometimes handshake with Windows and sometimes not. I've tried using all of the different ports, etc but the problem remains. I NEED 6 ports for my devices so it is all that I could do!
    6) I have an Enermax 550w EG651P-VE(FMA) with 36 amps on each voltage rail on it's way, and it should arrive tomorrow. Despite all of the crap regarding power supplies that I see on this board I am not confident that it's the problem. That Antec PSU should be able to hold it's on with 20 amps on the +12v channel. C'mon now. I build a nearly identical system with the same power supply for a customer and he has no problems at all. He also has 3 HDs, same motherboard, etc.. the only difference is he has but one optical drive and a 2800+ rather than a 3200+. That power difference should be decimal nature in amps needed.
    ...oh and the sound card is in PCI slot 3, for those that remember the glory days of sound card IRQ issues that Creative was once notorious for... oh, and I disable the ethernet boot device, etc so my slow startups should not be related. My serial ATA drive is also on connection 1 of the VIA controller.. Promise can kiss my a**.
    Soooo.. Show me what a n00b I am, oh great ones. I've built over 100 PCs since 1998 for myself, friends, families, and customers... and I've never seen an issue like this one! I'm no dummy, but please don't assume too much. Other pros on here know full well you can forget the most simple mundane detail in spite of experience! I want to solve this problem. I am on the verge of shelling out for a new motherboard and processor of the 939 pin variety.. and am now wary of MSI's long awaited socket 939 K8 Neo2 board despite it's awesome reviews. MSI has never really given me trouble before.. but I don't really want to spend money to the order of $200+ for that damned Gigabyte board. Gigabyte has always been good to me as well. Save my wallet! PLEASE!!!
    Thanks so much everyone, I tried very hard not to leave out any details!
    Az (Ian)
    You can reach me on Yahoo or AIM just about any time, and I will check here frequently.

    Quote
    Originally posted by AzaghalSEI
    Good morning everyone! (At least it's morning in wonderful Pennsylvania USA!)
    AMD Athlon 64 3200+ (New Castle)
    Thermaltake Venus 12 CPU Cooler w/ Manual Adjust
    MSI "K8T Neo-FIS2R" K8T800
    512MB x 2 Corsair TWINX1024-3200C2PT (Rated 2-3-3-6 1T)
    Antec TruePower 430w PS (+5V@36A +3.3V@28A +12V@20A)
    Gainward Dual DVI w/ VIVO GeForce FX5700 Ultra
    2x Viewsonic 19" VX900 LCD Monitors
    Creative SoundBlaster Audigy Platinum eX
    Plextor 712a Black 12x+/8x- DVD-RW
    Lite-On SOHD-167T Black 16x DVD-ROM
    Western Digital WD740GD 74GB 10,000rpm Raptor SATA
    Western Digital WD2500JB 250GB 7,200rpm 8MB IDE
    Seagate Barracuda ST3200822AS 200GB 7,200rpm 8MB IDE
    Lian-Li PC-65B Black Aluminum Case
    Vantech PCI Slot Fan
    CyberPower 825va Voltage Regulating UPS
    Windows XP Professional SP1a
         There we have it, I think that that is all you need to know to perhaps give opinions and advice. Allow me to elaborate on why I am posting today after browsing this wonderful forum for the last two weeks. (...and by the way, my hat's off to some of you knowledgeable regulars for helping out a lot of newbies and folks in trouble!) Without further adieu:
    Problem #1: POWER ISSUE
    When, or if, I remove AC Power from my PC for whatever reason I run into a problem in which after reconnecting the AC Power and attempting to turn on the computer it goes into a 3-5 second startup loop in which the PC does not post, but rather cycles power to all of the components indefinitely. I notice the LEDs on my optical drives cycling repeatedly ad infinitum until I power off using the 4-second hold method, and then press the power button again. At this point the PC boots up fine, and boots up fine going forward from all restarts and shut downs. How strange? I've never, EVER, encountered something like this before.
    Problem #2: PERFORMANCE ISSUE
    This PC has a handful of serious performace issues.
    3dMark03 scored horribly.
    Prime95 runs ridiculously slow although there are no erros! It runs much more quickly on my work PC which is a PIII 866mhz with 384MB of PC133 RAM.
    I receive, on no regular frequency, or while doing anything in particular, Explorer memory errors. Not BSOD's mind you, but "...blah blah blah referenced memory address xxxxx-xxxxx and could not be written". This causes Explorer to restart itself, blowing away the start menu, task bar, and any Explorer windows open. They reappear, of course, without incident.
    The most off performance issue of all is that when opening an Explorer window for either of my IDE HDs, designated D and E drives, I find that when using the highlighting rectangle tool the Explorer window freezes or lags. I can double-click and open or move/copy files without incident, but if I attempt to highlight by this method this halt or lag occurs.
    Also, since my update of the BIOS from 1.2 to 1.7, and then to 1.8 system startup times prior to Windows loading are HORRID. I have disabled just about everything, and yet the SATA BIOS loads for 5 seconds, and then I must wait 20 seconds for Windows itself to come to the login screen. No other BIOS related issues to report per se, but this is terrible for what should be a blazingly fast computer.
    Now let's see.. what have I tried to do to repair the issues?
    1) 2 BIOS flashes. First from 1.2->1.7, and then from 1.7->1.8. Ostensibly this was just "because". The power user need to have the latest! I noticed the incorrect CPU temperature being reported, however.. This led to me buying this massive ThermalTake HSF to replace my stocker. I also added more thermal goop than I ever have before, as well as a PCI slot fan before I became aware that it was a BIOS issue! GRRRR MSI.
    2) I thought perhaps for the one issue that one of the hard drives was an issue, and even perhaps for power, but I replaced each with new drives and tested all 4 on another PC. NO problems. Also I should perhaps mention that my IDE drives are all hooked up using Antec Cobra cables. Expensive yes, but why the hell not, right? I've never seen a hang-off grounding wire for IDE before. Decided not to use them as I could think of a great place to screw them in, nor have other PC using them had trouble skipping the ground wire.
    3) I unplugged every molex cable, the 4-pin CPU power, and the 20-pin ATX power and rerranged them all - as well as removed and then reinserted the RAM.
    4) I tried changing my memory timings and power management settings, etc in BIOS. Nothing seem to impact the issue. I didn't fiddle with the voltages, but I should not need to running the RAM at SPD or lower settings and without overclocking the system at all!
    5) Another issue that I had that seems to have vanished, come back, vanished, and then come back a "little bit" is my USB ports. When set to enable legacy devices in BIOS my USB items like my Logitech wireless keyboard would just cycle power and refuse to function. Also my UPS connected VIA USB seems to sometimes handshake with Windows and sometimes not. I've tried using all of the different ports, etc but the problem remains. I NEED 6 ports for my devices so it is all that I could do!
    6) I have an Enermax 550w EG651P-VE(FMA) with 36 amps on each voltage rail on it's way, and it should arrive tomorrow. Despite all of the crap regarding power supplies that I see on this board I am not confident that it's the problem. That Antec PSU should be able to hold it's on with 20 amps on the +12v channel. C'mon now. I build a nearly identical system with the same power supply for a customer and he has no problems at all. He also has 3 HDs, same motherboard, etc.. the only difference is he has but one optical drive and a 2800+ rather than a 3200+. That power difference should be decimal nature in amps needed.
    ...oh and the sound card is in PCI slot 3, for those that remember the glory days of sound card IRQ issues that Creative was once notorious for... oh, and I disable the ethernet boot device, etc so my slow startups should not be related. My serial ATA drive is also on connection 1 of the VIA controller.. Promise can kiss my a**.
    Soooo.. Show me what a n00b I am, oh great ones. I've built over 100 PCs since 1998 for myself, friends, families, and customers... and I've never seen an issue like this one! I'm no dummy, but please don't assume too much. Other pros on here know full well you can forget the most simple mundane detail in spite of experience! I want to solve this problem. I am on the verge of shelling out for a new motherboard and processor of the 939 pin variety.. and am now wary of MSI's long awaited socket 939 K8 Neo2 board despite it's awesome reviews. MSI has never really given me trouble before.. but I don't really want to spend money to the order of $200+ for that damned Gigabyte board. Gigabyte has always been good to me as well. Save my wallet! PLEASE!!!
    Thanks so much everyone, I tried very hard not to leave out any details!
    Az (Ian)
    You can reach me on Yahoo or AIM just about any time, and I will check here frequently.
    The startup problem might just be a screwy psu. Your antec *should* be able to power your stuff just fine, but maybe it is defective in some strange way.
    What is your 3dmark03 score? If it is 3000-4000, (approx perf. level of ati 9600xt), then it is fine.
    Check your memory using memtest86+, and try underclocking it to ddr333.
    UNplug usb devices, and see if it speeds up boot. Also, I would not recommend bios 1.8 since people seem to have some troubles with it.
    Also, try disabling agp fast writes, disabling spread spectrum, and maybe boosting ram voltage a tiny bit.
    Try booting without your audigy plugged in, and try booting barebones (nothing but 1 hard drive with os) and see what happens.
    I'm no expert, but you might get lucky trying these steps.

  • Aperture 3, Snow Leopard, iMac ATI Radeon X1600 and graphics issues

    I have been searching the web to see if 10.6.4 has finally solved the graphics issues with the white iMac 2.16 intel with the ATI Radeon X1600 graphics processors and seen some mixed reviews. What is the consensus here, has 10.6.4 finally solved the graphics issues when editing photos in Aperture 3 (not to mention problems with iPhoto and iChat also). I had to downgrade to Leopard before so I don't want to upgrade to SL again and go back down the downgrade path. Thanks in advance for the feedback

    I can say that 10.6.4 has worked out the kinks for my white 24" iMac with 7300GT card. From what others have posted here, it appears the x1600 issues have been resolved as well. I was running 10.6.2 prior to this update and advising everyone else of same. Of course, 10.6.2 and SL was not perfect, with some issues cropping up here and there. IMHO the 10.6.4 release is equivalent to the 10.5.3 release by comparison. In fact, I upgraded my Mac mini after my good experiences with 10.6.4 on my iMac. Not sure if this helps or not.

  • Kernal panics and graphics issues

    I have a 2008 MacBook Pro.  Over the last few weeks I've been getting strange graphics issues.  At first every other vertical line would go black and make the display unreadable.  That happened occasionally for a few days then would snap out of it and go back to normal.  The problem got worse, where the whole screen would shift colors, turning either a certain color like blue or green.  Then it started to cycle through the colors and would flicker like a bad MTv music video from the 1980s.  Eventually the display would always come back to normal, but I'm never sure for how long. 
    Lately I've received a few kernal panics, which I think are related to this issue.  I've extracted the relevant logs below.  My hunch is that my graphics card is going bad, but I've never had that happen on a computer before.  Is this a known issue, is there anything I can do about it (replace / upgrade the card?)
    Thanks.
    Kernel Panic Log Entries:
    panic(cpu 1 caller 0x00CED6A4): NVRM[0]: Read Error 0x00000100: BAR0 0xd2000000 0x5f681000 0x084700a2 D0 P2/4
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    panic(cpu 0 caller 0x00CED6A4): NVRM[0]: Read Error 0x00020400: BAR0 0xd2000000 0x654a0000 0x084700a2 D0 P0/4
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    com.apple.driver.AppleIntelCPUPowerManagement          76.2.0
    panic(cpu 0 caller 0x001AB0FE): Kernel trap at 0x00cf0c1e, type 14=page fault, registers:
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    com.apple.driver.AppleIntelCPUPowerManagement          76.2.0

    The third-party system modification "Logitech Control Center" may be contributing to your problem. I suggest you back up all data, then uninstall it according to the developer's instructions. Reboot and see whether there's any improvement.
    Back up all data before making any changes.

  • Wifi, power and cooling issues with my MacBook Pro.

    I've had my MacBook Pro for about 2 years and I've been really pleased with its performance from work I've thrown at it. I initially got this MacBook Pro refurbished from the Mac store and it has a Apple Care protection plan. Although this past year I've noticed several issues that are probably hardware related. First, my MacBook's WiFi does not receive WiFi signals from the great distances it used to anymore. The times I can pick up WiFi are within like 5 yards from my wireless router. Second, I'm having an issue with the power. This past week, it seems my Macbook Pro does not run off the battery anymore. It only powers on when connected into the power supply. If I unplug the power supply, my Macbook turns off. It does not revert to the battery which is strange. Third, cooling seems to be a problem. The Macbook Pro is getting very hot. It burns my lap when it is holding there. The cooling problem has lasted since I got my Macbook back in January of 2007. I thought it was normal since I would load the CPU with some graphics intensive games. Now the Macbook Pro gets hot to doing some less CPU intensive tasks like surfing the web or word processing. I have noticed, a decrease in performance, longer boot times, loading of web browsers, and word processing applications. Would this be the best time to consider taking my Macbook Pro and for repair with apple care? I'd like to trouble shoot these issues to know exactly why these problems are happening. I have a feeling it could be due to the Macbook Pro getting hot. As for cooling I go by the manual and place it on a table or hard surface, or my lap. I pretty much want to know what is wrog and how to prevent issues like this in the future.
    Thanks.

    Welcome to Apple Discussions!
    It sounds like you have several issues:
    I don't know why your MBP can only receive wireless signals from 5 feet away. Unless possibly the antenna has worked loose. But I'm just guessing.
    Regarding the power, is your battery still good? Have you tried resetting the SMC?
    http://support.apple.com/kb/HT1411?viewlocale=en_US
    Regarding the heat issue, have you tried running the extended version of the Apple Hardware Test? If you check your fans with iStatPro, are both running at an appropriate speed for the heat?
    Also, have you checked in Activity Monitor for any out of control processes which might be running in the background and hogging the CPU?
    A good place to start would be with the AHT. Since you have Applecare, you should also have a Tech Tool Deluxe disc, and you can run that too. Should anything turn up in the form of an error code, that would indicate a hardware problem. Write down the code and call Apple to arrange for repair.
    If you have access to an Apple Store, you could also just take your Mac in for evaluation.
    Good luck!

  • Macbook Pro Usability and Graphics Issues

    I recently took my MBP 3,1 to get the logic board replaced because of a dead graphics card but when I got back home the system would lock up and display visual glitches (I took some pictures from separate occasions with phone so the links are below). After this happens I have to force the system to restart by holding down the power button. One of those restart attempts I got the typical apple logo but with a lot of artifacts and the screen/system locked up. I thought that possibly I could have a corrupt driver somewhere since the hardware is new, so I reinstalled a fresh copy of Leopard and I'm still having the same problem. I'm starting to lean towards a hardware issue. Has occurred during regular use (light web surfing, music, chat), gaming (World Of Warcraft), and Screensaver. Below are some links so you can get an idea of what I am looking at. Thanks for taking the time and reading through my hysteria. =)
    http://i38.tinypic.com/24pgrk6.jpg
    http://i34.tinypic.com/2dqnhuc.jpg
    When it does not do this the screen just goes black and the system refuses to respond unless I force it with the power button held down and turning it on again.
    edit: This is what apple care replaced: 605-1790 PCBA, MLB,2.2GHZ,REV2
    605-7933 PCBA,BANDCAMP, M75
    and details about the grapics card:
    GeForce 8600M GT:
    Chipset Model: GeForce 8600M GT
    Type: Display
    Bus: PCIe
    PCIe Lane Width: x16
    VRAM (Total): 128 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0407
    Revision ID: 0x00a1
    ROM Revision: 3175
    Message was edited by: gquinte2

    If you can reproduce the problem in front of the genius, that would be the best thing. If it will happen predictably 30 minutes into use, go 30 minutes early and let it run for 30 minutes. As soon as the problem appears, get a genius (or any Apple Store person) to look at it. Sometimes things are heat related, and the machine needs to be warm enough to show up the problem.
    Some time ago, I had problems with my iBook freezing, but it had to run 20-30 minutes to do it. So I made sure I got there early enough to give it plenty of time to act up. Often people come into the store and their machines have been off and cooled down, and of course the machine will function perfectly in front of the genius because it hasn't been on long enough to malfunction.
    It sounds like your graphics problem is intermittent, but do your best to reproduce a situation where it happens. It does sound like you possibly just got a bum replacement logic board--or there is some other problem, possibly even caused by the repair. But it isn't right, and I would recommend you be persistent about having it fixed.
    Good luck!

  • G4 PMU and graphical issues

    I've been using this computer (Power Mac G4) for more than five years.
    About 8 months ago, It wouldn't boot, and I had to reset the PMU...and it worked fine up until a few days ago. Now, each time I want to turn on the computer, I have to open it up and reset the PMU.
    On top of this, about 8/10 times I try to use the computer, the screen starts to look like this: http://img25.imageshack.us/img25/8584/picture4xm.png
    I have to restart when this happens. Keep in mind I use 2 monitors, and the exact same glitchy pattern showed up on each screen. I have a feeling this has something to do with the graphics card? It's strange, because sometimes the computer becomes completely inoperative, and I have to manually restart it up to 6 times before it works. Other times it works perfectly without any graphical glitches, and stays like that until I have to turn it on again. However, I don't trust the computer very much, and I feel like it could spaz out at any time when I'm writing a paper or something.
    Anyway, what could be the problem? Are these two issues possibly connected? Also, is this computer still salvageable?
    Thanks in advance for any help.

    Let me get this straight: there's a possibility that these graphical hiccups could be related to a low battery?
    If the battery is low, a host of strange things can happen. Your battery almost certainly is close to dead. Replacing the battery very probably will solve the intermittent start up issues, and it might also solve your display problems. The battery is needed to preserve the integrity of the information stored in the computer's PRAM. That information includes display settings. However, the display problems could have other causes, as Allan has pointed out.
    The logic is quite simple: if more than one thing can be at fault, fix the most likely culprit first.

  • Constant crashes and graphical issues after updating to Yosemite

    This problem started gradually. First a game I tried to launch crashed. Then I was unable to open any applications at all. I restarted the computer after having to force quit out of everything. The user sign in screen would let me type in my password and then I would get a white screen. I restarted twice more before being able to log in. Then the graphics problems started. No online videos would play. I tried opening a different game to see what would happen. That froze and made me have to restart again. The first time I got a grey striped screen. Then when I was able to log back in I got an error saying something like "a graphics problem has been detected."
    I have tried.
    Restarting
    Hardware diagnostic test
    PRAM reset
    SMC reset
    A second user account (logs on but I haven't been able to test it by loading a game or graphics intensive program + it's not a real fix)
    Still running into the same problems if I do much more that web browsing.

    Yep, mine's a mid-2010 27" iMac and it keeps giving me issues like this. This time it actually froze like this and I had to do a hard reboot. Usually the "pixel squares" come and go as I move the mouse or open and close windows. Pretty ridiculous that this wide range of iMacs are having this problem.

  • Event ID 41 Kernel- Power and Memory Issues with P67A-GD65

    Alright guys, the reason I'm starting this topic is because I have recently bought an i7-2600K, 8GB (2GBx4) Corsair Dominator CMP4GX3M2A1600C8, a Radeon HD 6970 for an update to my system, I also have an Intel X-25M First Generation 80GB SSD as the boot drive and then 2 Western Digital Black Cavier 1TB storage drives. I currently have OC Genie turned on and my processor is OCed to 4.2GHZ, I have a Zalman 9900Max air cooler on it and my usual processor temp is 34C. Basically every once and a while I'm get Blue Screens on my system, Windows Event Viewer Tags it as Event ID 41 Kernel-Power, I've also gotten PFN_LIST_CORRUPT while playing Crysis once. I'm wondering if it's memeory so I'm about to run my system through MemTest and see what it turns up. So here are my reasons for this post.
    1. MSI's website lists only triple channel memeory for corsair for this board which of course is dual channel, so does anyone have a recommendations on memory if I do have to switch them out which I would hate to leave corsair.
    2. Has anyone else had this problem with their system?
    Thanks guys

    Quote from: michael4man on 24-January-11, 08:13:52
    Alright guys, the reason I'm starting this topic is because I have recently bought an i7-2600K, 8GB (2GBx4) Corsair Dominator CMP4GX3M2A1600C8, a Radeon HD 6970 for an update to my system, I also have an Intel X-25M First Generation 80GB SSD as the boot drive and then 2 Western Digital Black Cavier 1TB storage drives. I currently have OC Genie turned on and my processor is OCed to 4.2GHZ, I have a Zalman 9900Max air cooler on it and my usual processor temp is 34C. Basically every once and a while I'm get Blue Screens on my system, Windows Event Viewer Tags it as Event ID 41 Kernel-Power, I've also gotten PFN_LIST_CORRUPT while playing Crysis once. I'm wondering if it's memeory so I'm about to run my system through MemTest and see what it turns up. So here are my reasons for this post.
    1. MSI's website lists only triple channel memeory for corsair for this board which of course is dual channel, so does anyone have a recommendations on memory if I do have to switch them out which I would hate to leave corsair.
    2. Has anyone else had this problem with their system?
    Thanks guys
    I sold my 3x 2GB Corsair Dominator 1600s for 2x 4GB G.SKILL RipJaw X 1333s because they are 1.5V CL7 and XMP Sandy Bridge optimized  : P

  • Performance and Graphical Issues with iOS 4.3 and IPod Touch 4th Generation

    My Ipod touch is only a week old and I just updated it to iOS 4.3 from the original firmware, but after I updated the device it seemed to start generating white lines in the status bar area unexpectedly. Then at the same time my device would stop responding for a couple of seconds or become extremely slow. I also notice that my album art is misplaced and/or obscured and nothing is misplaced on iTunes. I've restored it two to three times. The device can not be downgraded so I'm not sure what to do.

    Hmmmm... you know what... some of my album art was misplaced also... mainly for my "Unknown Artists" but still... Oh yeah and everyone knows about the glitch on the top bar, theres a post with about 20,000 views on it so maybe you should check there

  • Mac Pro Quad core power and cooling concerns

    My current MDD 867 is getting a bit long in the tooth. I am looking at getting a quad mac pro this fall. Waiting till MacWorld is a verrrrry long wait option. Did I mention that the MDD cooked off one of my drives recently?
    What I plan on building is the following :
    Mac Pro Quad 3 GHz
    4 Gb ram
    Ati X1900 (extra cooling fan?)
    250 GB boot drive
    500 GB Barracuda mirror raid
    16X SuperDrive
    Knowing the power and cooling issues that the MDD has intimately, this new machine configuration gives me pause. Can anyone attest to the power and cooling capabilities of the Mac Pro? Will the above configuration be ok? How about possible fan speed noise? The MDD, with new power supply is a noise beast!
    TIA
    Poirot

    Thanks for the reply.
    To be a a little more clear, when I referred to quad, I meant 2x dual-core processors.
    The raid was for storage of my images. I have an external firewire drive for backups of the system drive, and other important files. Photography is my hobby, and need to build a new workstation to store and edit the images.
    The UPS was a good idea. That was in the back of my mind. I could try and bring an APC SU2200XL from work
    I was hoping that Apple would announce the new Mac Pro this fall. I know that the raw processor speed difference is not that much, but the FSB speed difference could make a nice improvement. I just didn't want to get one now, and then 10 days later, there is a new one. I would be really mad at myself. I was looking at the refurb models. The price difference between the 4 and 8 core models is $100, when available. The downside is that the 8-core model does not come with the Ati card.
    The allure of Leopard is not that strong to me. We are running the beta at work, and while nice, it is still too buggy.
    The main intent of the thread was to make sure that the specs'd out model would not generate too much heat, and suck up too much power from the power supply. I know that the MDD compared tot he Mac Pro is night and day, but a little reassurance is always helpful.
    Thanks
    Mack

  • GDM and Gnome graphical issues with Nvidia card

    Hi !
    I want to install archlinux with cinnamon as desktop environment on the computer of a friend, but I have some issue with it, and especially with (I think) the graphic card, it's a Nvidia GeForce FX 5200LE.
    I tried installing nvidia-173xx from the aur first. I installed gdm, but it's extremly slow, as a result that I can't log in (nevertheless the mouse is fluid..)  the cpu is not so much used yet, and it's the same thing in the cinnamon session or the gnome session (I tried installing lightdm to log in which works fine). Moreover, in the session I've got some strange graphical things, such as some missing white pixels, or a blue window when I launch nautilus, ... (here are some screenshots : http://i49.tinypic.com/2efhm6s.png and a with a window : http://i46.tinypic.com/116m05k.png)
    I tried to install the nouveau driver instead, and now gdm don't freeze, I can log in, but there is always these strange graphical issues.
    Is the graphic card too old for gnome ? Or did I forget something ?
    Thank you in advance for your help !! And sorry for my english ..
    Here are some log with the nouveau driver :
    - Xorg.log :
    [ 9.026]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 9.026] X Protocol Version 11, Revision 0
    [ 9.026] Build Operating System: Linux 3.4.8-1-ARCH i686
    [ 9.026] Current Operating System: Linux famille-workstation 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 08:15:06 UTC 2012 i686
    [ 9.026] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=83840f06-da6c-4558-a8ef-8ed779442ff3 ro quiet pci=nomsi
    [ 9.026] Build Date: 27 August 2012 08:08:29AM
    [ 9.026]
    [ 9.026] Current version of pixman: 0.26.2
    [ 9.026] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 9.026] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 9.027] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 5 13:26:01 2012
    [ 9.053] (==) Using config file: "/etc/X11/xorg.conf"
    [ 9.053] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 9.072] (==) No Layout section. Using the first Screen section.
    [ 9.072] (==) No screen section available. Using defaults.
    [ 9.072] (**) |-->Screen "Default Screen Section" (0)
    [ 9.072] (**) | |-->Monitor "<default monitor>"
    [ 9.074] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 9.074] (**) Option "AIGLX" "off"
    [ 9.074] (==) Automatically adding devices
    [ 9.074] (==) Automatically enabling devices
    [ 9.127] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 9.127] Entry deleted from font path.
    [ 9.128] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 9.128] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/Type1/".
    [ 9.128] Entry deleted from font path.
    [ 9.128] (Run 'mkfontdir' on "/usr/share/fonts/Type1/").
    [ 9.128] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 9.128] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 9.128] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 9.128] (II) Loader magic: 0x82225a0
    [ 9.128] (II) Module ABI versions:
    [ 9.128] X.Org ANSI C Emulation: 0.4
    [ 9.128] X.Org Video Driver: 12.1
    [ 9.128] X.Org XInput driver : 16.0
    [ 9.128] X.Org Server Extension : 6.0
    [ 9.129] (--) PCI:*(0:1:0:0) 10de:0323:107d:1334 rev 161, Mem @ 0xe0000000/16777216, 0xd8000000/134217728, BIOS @ 0x????????/131072
    [ 9.129] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 9.129] (II) LoadModule: "extmod"
    [ 9.145] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 9.156] (II) Module extmod: vendor="X.Org Foundation"
    [ 9.156] compiled for 1.12.4, module version = 1.0.0
    [ 9.156] Module class: X.Org Server Extension
    [ 9.156] ABI class: X.Org Server Extension, version 6.0
    [ 9.156] (II) Loading extension MIT-SCREEN-SAVER
    [ 9.156] (II) Loading extension XFree86-VidModeExtension
    [ 9.156] (II) Loading extension XFree86-DGA
    [ 9.156] (II) Loading extension DPMS
    [ 9.156] (II) Loading extension XVideo
    [ 9.156] (II) Loading extension XVideo-MotionCompensation
    [ 9.156] (II) Loading extension X-Resource
    [ 9.156] (II) LoadModule: "dbe"
    [ 9.157] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 9.157] (II) Module dbe: vendor="X.Org Foundation"
    [ 9.157] compiled for 1.12.4, module version = 1.0.0
    [ 9.157] Module class: X.Org Server Extension
    [ 9.157] ABI class: X.Org Server Extension, version 6.0
    [ 9.157] (II) Loading extension DOUBLE-BUFFER
    [ 9.157] (II) LoadModule: "glx"
    [ 9.157] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 9.164] (II) Module glx: vendor="X.Org Foundation"
    [ 9.164] compiled for 1.12.4, module version = 1.0.0
    [ 9.164] ABI class: X.Org Server Extension, version 6.0
    [ 9.164] (**) AIGLX disabled
    [ 9.165] (II) Loading extension GLX
    [ 9.165] (II) LoadModule: "record"
    [ 9.165] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 9.166] (II) Module record: vendor="X.Org Foundation"
    [ 9.166] compiled for 1.12.4, module version = 1.13.0
    [ 9.166] Module class: X.Org Server Extension
    [ 9.166] ABI class: X.Org Server Extension, version 6.0
    [ 9.166] (II) Loading extension RECORD
    [ 9.166] (II) LoadModule: "dri"
    [ 9.166] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 9.172] (II) Module dri: vendor="X.Org Foundation"
    [ 9.172] compiled for 1.12.4, module version = 1.0.0
    [ 9.172] ABI class: X.Org Server Extension, version 6.0
    [ 9.172] (II) Loading extension XFree86-DRI
    [ 9.172] (II) LoadModule: "dri2"
    [ 9.172] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 9.173] (II) Module dri2: vendor="X.Org Foundation"
    [ 9.173] compiled for 1.12.4, module version = 1.2.0
    [ 9.173] ABI class: X.Org Server Extension, version 6.0
    [ 9.173] (II) Loading extension DRI2
    [ 9.173] (==) Matched nouveau as autoconfigured driver 0
    [ 9.173] (==) Matched nvidia as autoconfigured driver 1
    [ 9.173] (==) Matched nv as autoconfigured driver 2
    [ 9.173] (==) Matched vesa as autoconfigured driver 3
    [ 9.173] (==) Matched fbdev as autoconfigured driver 4
    [ 9.173] (==) Assigned the driver to the xf86ConfigLayout
    [ 9.173] (II) LoadModule: "nouveau"
    [ 9.180] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 9.191] (II) Module nouveau: vendor="X.Org Foundation"
    [ 9.191] compiled for 1.12.2, module version = 1.0.1
    [ 9.191] Module class: X.Org Video Driver
    [ 9.191] ABI class: X.Org Video Driver, version 12.0
    [ 9.191] (II) LoadModule: "nvidia"
    [ 9.191] (WW) Warning, couldn't open module nvidia
    [ 9.191] (II) UnloadModule: "nvidia"
    [ 9.191] (II) Unloading nvidia
    [ 9.192] (EE) Failed to load module "nvidia" (module does not exist, 0)
    [ 9.192] (II) LoadModule: "nv"
    [ 9.192] (WW) Warning, couldn't open module nv
    [ 9.192] (II) UnloadModule: "nv"
    [ 9.192] (II) Unloading nv
    [ 9.192] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 9.192] (II) LoadModule: "vesa"
    [ 9.192] (WW) Warning, couldn't open module vesa
    [ 9.192] (II) UnloadModule: "vesa"
    [ 9.192] (II) Unloading vesa
    [ 9.192] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 9.192] (II) LoadModule: "fbdev"
    [ 9.193] (WW) Warning, couldn't open module fbdev
    [ 9.193] (II) UnloadModule: "fbdev"
    [ 9.193] (II) Unloading fbdev
    [ 9.193] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 9.193] (II) NOUVEAU driver
    [ 9.193] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 9.193] RIVA TNT (NV04)
    [ 9.193] RIVA TNT2 (NV05)
    [ 9.193] GeForce 256 (NV10)
    [ 9.193] GeForce 2 (NV11, NV15)
    [ 9.193] GeForce 4MX (NV17, NV18)
    [ 9.193] GeForce 3 (NV20)
    [ 9.193] GeForce 4Ti (NV25, NV28)
    [ 9.193] GeForce FX (NV3x)
    [ 9.193] GeForce 6 (NV4x)
    [ 9.193] GeForce 7 (G7x)
    [ 9.193] GeForce 8 (G8x)
    [ 9.193] GeForce GTX 200 (NVA0)
    [ 9.193] GeForce GTX 400 (NVC0)
    [ 9.193] (++) using VT number 7
    [ 9.196] drmOpenDevice: node name is /dev/dri/card0
    [ 9.196] drmOpenDevice: open result is 7, (OK)
    [ 9.196] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    [ 9.196] drmOpenDevice: node name is /dev/dri/card0
    [ 9.196] drmOpenDevice: open result is 7, (OK)
    [ 9.196] drmOpenByBusid: drmOpenMinor returns 7
    [ 9.196] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    [ 9.196] (II) [drm] nouveau interface version: 1.0.0
    [ 9.196] (II) Loading sub module "dri"
    [ 9.196] (II) LoadModule: "dri"
    [ 9.197] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 9.197] (II) Module dri: vendor="X.Org Foundation"
    [ 9.197] compiled for 1.12.4, module version = 1.0.0
    [ 9.197] ABI class: X.Org Server Extension, version 6.0
    [ 9.197] (II) NOUVEAU(0): Loaded DRI module
    [ 9.197] drmOpenDevice: node name is /dev/dri/card0
    [ 9.197] drmOpenDevice: open result is 8, (OK)
    [ 9.197] drmOpenDevice: node name is /dev/dri/card0
    [ 9.197] drmOpenDevice: open result is 8, (OK)
    [ 9.197] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    [ 9.197] drmOpenDevice: node name is /dev/dri/card0
    [ 9.197] drmOpenDevice: open result is 8, (OK)
    [ 9.197] drmOpenByBusid: drmOpenMinor returns 8
    [ 9.197] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    [ 9.197] (II) [drm] DRM interface version 1.4
    [ 9.197] (II) [drm] DRM open master succeeded.
    [ 9.197] (--) NOUVEAU(0): Chipset: "NVIDIA NV34"
    [ 9.197] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 9.197] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 9.197] (==) NOUVEAU(0): RGB weight 888
    [ 9.197] (==) NOUVEAU(0): Default visual is TrueColor
    [ 9.197] (==) NOUVEAU(0): Using HW cursor
    [ 9.197] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 9.197] (==) NOUVEAU(0): Page flipping enabled
    [ 9.197] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
    [ 9.227] (II) NOUVEAU(0): Output VGA-1 has no monitor section
    [ 9.280] (II) NOUVEAU(0): Output TV-1 has no monitor section
    [ 9.309] (II) NOUVEAU(0): EDID for output VGA-1
    [ 9.309] (II) NOUVEAU(0): Manufacturer: SAM Model: 1b Serial#: 1195913527
    [ 9.309] (II) NOUVEAU(0): Year: 2003 Week: 16
    [ 9.309] (II) NOUVEAU(0): EDID Version: 1.3
    [ 9.309] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 9.309] (II) NOUVEAU(0): Sync: Separate Composite SyncOnGreenSerration on. V.Sync Pulse req. if CompSync or SyncOnGreen
    [ 9.309] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 27
    [ 9.309] (II) NOUVEAU(0): Gamma: 2.40
    [ 9.309] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 9.309] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 9.309] (II) NOUVEAU(0): redX: 0.634 redY: 0.354 greenX: 0.304 greenY: 0.581
    [ 9.309] (II) NOUVEAU(0): blueX: 0.143 blueY: 0.102 whiteX: 0.318 whiteY: 0.339
    [ 9.309] (II) NOUVEAU(0): Supported established timings:
    [ 9.309] (II) NOUVEAU(0): 720x400@70Hz
    [ 9.309] (II) NOUVEAU(0): 640x480@60Hz
    [ 9.309] (II) NOUVEAU(0): 640x480@67Hz
    [ 9.309] (II) NOUVEAU(0): 640x480@72Hz
    [ 9.310] (II) NOUVEAU(0): 640x480@75Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@56Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@60Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@72Hz
    [ 9.310] (II) NOUVEAU(0): 800x600@75Hz
    [ 9.310] (II) NOUVEAU(0): 832x624@75Hz
    [ 9.310] (II) NOUVEAU(0): 1024x768@60Hz
    [ 9.310] (II) NOUVEAU(0): 1024x768@70Hz
    [ 9.310] (II) NOUVEAU(0): 1024x768@75Hz
    [ 9.310] (II) NOUVEAU(0): 1280x1024@75Hz
    [ 9.310] (II) NOUVEAU(0): 1152x864@75Hz
    [ 9.310] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 9.310] (II) NOUVEAU(0): Supported standard timings:
    [ 9.310] (II) NOUVEAU(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 9.310] (II) NOUVEAU(0): #1: hsize: 1024 vsize 768 refresh: 60 vid: 16481
    [ 9.310] (II) NOUVEAU(0): #2: hsize: 800 vsize 600 refresh: 60 vid: 16453
    [ 9.310] (II) NOUVEAU(0): #3: hsize: 640 vsize 480 refresh: 60 vid: 16433
    [ 9.310] (II) NOUVEAU(0): Supported detailed timing:
    [ 9.310] (II) NOUVEAU(0): clock: 108.0 MHz Image Size: 338 x 270 mm
    [ 9.310] (II) NOUVEAU(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    [ 9.310] (II) NOUVEAU(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    [ 9.310] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 145 MHz
    [ 9.310] (II) NOUVEAU(0): Monitor name: SyncMaster
    [ 9.310] (II) NOUVEAU(0): Serial No: HJGW403719
    [ 9.310] (II) NOUVEAU(0): EDID (in hex):
    [ 9.310] (II) NOUVEAU(0): 00ffffffffffff004c2d1b0037314847
    [ 9.310] (II) NOUVEAU(0): 100d01030f221b8cea6f8ba25a4d9424
    [ 9.310] (II) NOUVEAU(0): 1a5156bfef8081806140454031400101
    [ 9.310] (II) NOUVEAU(0): 010101010101302a009851002a403070
    [ 9.310] (II) NOUVEAU(0): 1300520e1100001e000000fd00384c1e
    [ 9.310] (II) NOUVEAU(0): 510e000a202020202020000000fc0053
    [ 9.310] (II) NOUVEAU(0): 796e634d61737465720a2020000000ff
    [ 9.310] (II) NOUVEAU(0): 00484a47573430333731390a20200057
    [ 9.310] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 9.310] (II) NOUVEAU(0): Using EDID range info for horizontal sync
    [ 9.310] (II) NOUVEAU(0): Using EDID range info for vertical refresh
    [ 9.310] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 9.310] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.310] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Printing probed modes for output VGA-1
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 9.311] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.311] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.363] (II) NOUVEAU(0): EDID for output TV-1
    [ 9.363] (II) NOUVEAU(0): Output VGA-1 connected
    [ 9.363] (II) NOUVEAU(0): Output TV-1 disconnected
    [ 9.363] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 9.363] (II) NOUVEAU(0): Output VGA-1 using initial mode 1280x1024
    [ 9.363] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 9.363] (--) NOUVEAU(0): Virtual size is 1280x1024 (pitch 0)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x800": 106.5 MHz (scaled from 0.0 MHz), 62.8 kHz, 74.9 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x800": 83.5 MHz (scaled from 0.0 MHz), 49.7 kHz, 59.8 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x768": 102.2 MHz (scaled from 0.0 MHz), 60.3 kHz, 74.9 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
    [ 9.363] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.364] (**) NOUVEAU(0): Mode "1024x576": 47.0 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 9.364] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
    [ 9.364] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.364] (**) NOUVEAU(0): Display dimensions: (340, 270) mm
    [ 9.364] (**) NOUVEAU(0): DPI set to (95, 96)
    [ 9.364] (II) Loading sub module "fb"
    [ 9.364] (II) LoadModule: "fb"
    [ 9.364] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 9.375] (II) Module fb: vendor="X.Org Foundation"
    [ 9.375] compiled for 1.12.4, module version = 1.0.0
    [ 9.375] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 9.375] (II) Loading sub module "exa"
    [ 9.375] (II) LoadModule: "exa"
    [ 9.376] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 9.380] (II) Module exa: vendor="X.Org Foundation"
    [ 9.380] compiled for 1.12.4, module version = 2.5.0
    [ 9.380] ABI class: X.Org Video Driver, version 12.1
    [ 9.380] (II) Loading sub module "shadowfb"
    [ 9.380] (II) LoadModule: "shadowfb"
    [ 9.380] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 9.382] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 9.382] compiled for 1.12.4, module version = 1.0.0
    [ 9.382] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 9.382] (--) Depth 24 pixmap format is 32 bpp
    [ 9.382] (II) NOUVEAU(0): Opened GPU channel 1
    [ 9.384] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 9.384] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 9.384] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 9.399] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 9.399] (II) EXA(0): Driver registered support for the following operations:
    [ 9.399] (II) Solid
    [ 9.399] (II) Copy
    [ 9.399] (II) Composite (RENDER acceleration)
    [ 9.399] (II) UploadToScreen
    [ 9.399] (II) DownloadFromScreen
    [ 9.399] (==) NOUVEAU(0): Backing store disabled
    [ 9.399] (==) NOUVEAU(0): Silken mouse enabled
    [ 9.399] (II) NOUVEAU(0): [XvMC] Associated with NV30 texture adapter.
    [ 9.399] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 9.399] (==) NOUVEAU(0): DPMS enabled
    [ 9.399] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 9.399] (--) RandR disabled
    [ 9.399] (II) Initializing built-in extension Generic Event Extension
    [ 9.399] (II) Initializing built-in extension SHAPE
    [ 9.399] (II) Initializing built-in extension MIT-SHM
    [ 9.400] (II) Initializing built-in extension XInputExtension
    [ 9.400] (II) Initializing built-in extension XTEST
    [ 9.400] (II) Initializing built-in extension BIG-REQUESTS
    [ 9.400] (II) Initializing built-in extension SYNC
    [ 9.400] (II) Initializing built-in extension XKEYBOARD
    [ 9.400] (II) Initializing built-in extension XC-MISC
    [ 9.400] (II) Initializing built-in extension SECURITY
    [ 9.400] (II) Initializing built-in extension XINERAMA
    [ 9.400] (II) Initializing built-in extension XFIXES
    [ 9.400] (II) Initializing built-in extension RENDER
    [ 9.400] (II) Initializing built-in extension RANDR
    [ 9.400] (II) Initializing built-in extension COMPOSITE
    [ 9.400] (II) Initializing built-in extension DAMAGE
    [ 9.800] (II) AIGLX: Loaded and initialized swrast
    [ 9.800] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [ 9.807] (II) NOUVEAU(0): NVEnterVT is called.
    [ 9.807] (II) NOUVEAU(0): Setting screen physical size to 338 x 270
    [ 9.807] resize called 1280 1024
    [ 10.066] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 10.066] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 10.066] (II) LoadModule: "evdev"
    [ 10.066] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 10.075] (II) Module evdev: vendor="X.Org Foundation"
    [ 10.075] compiled for 1.12.3.901, module version = 2.7.3
    [ 10.075] Module class: X.Org XInput Driver
    [ 10.075] ABI class: X.Org XInput driver, version 16.0
    [ 10.075] (II) Using input driver 'evdev' for 'Power Button'
    [ 10.076] (**) Power Button: always reports core events
    [ 10.076] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 10.076] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 10.076] (--) evdev: Power Button: Found keys
    [ 10.076] (II) evdev: Power Button: Configuring as keyboard
    [ 10.076] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 10.076] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 10.076] (**) Option "xkb_rules" "evdev"
    [ 10.076] (**) Option "xkb_model" "evdev"
    [ 10.076] (**) Option "xkb_layout" "us"
    [ 10.117] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 10.117] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 10.117] (II) Using input driver 'evdev' for 'Power Button'
    [ 10.117] (**) Power Button: always reports core events
    [ 10.117] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 10.118] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 10.118] (--) evdev: Power Button: Found keys
    [ 10.118] (II) evdev: Power Button: Configuring as keyboard
    [ 10.118] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 10.118] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 10.118] (**) Option "xkb_rules" "evdev"
    [ 10.118] (**) Option "xkb_model" "evdev"
    [ 10.118] (**) Option "xkb_layout" "us"
    [ 10.118] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 10.118] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 10.118] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 10.119] (**) AT Translated Set 2 keyboard: always reports core events
    [ 10.119] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 10.119] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 10.119] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 10.119] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 10.119] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 10.119] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
    [ 10.119] (**) Option "xkb_rules" "evdev"
    [ 10.119] (**) Option "xkb_model" "evdev"
    [ 10.119] (**) Option "xkb_layout" "us"
    [ 10.120] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event4)
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 10.120] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
    [ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event4"
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Vendor 0x2 Product 0x5
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found relative axes
    [ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
    [ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: Configuring as mouse
    [ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
    [ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 10.120] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
    [ 10.120] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 9)
    [ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
    [ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
    [ 10.121] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
    [ 10.121] (II) No input driver specified, ignoring this device.
    [ 10.121] (II) This device may have been added with another device file.
    [ 10.121] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 10.121] (II) No input driver specified, ignoring this device.
    [ 10.121] (II) This device may have been added with another device file.
    [ 10.174] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 10.174] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 10.174] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 10.174] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 10.174] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 10.174] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 14.960] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 14.960] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 14.960] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 14.960] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 14.960] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 14.961] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 84.256] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 111.559] (II) NOUVEAU(0): NVEnterVT is called.
    [ 111.601] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 111.601] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 111.601] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 111.601] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 111.601] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 111.601] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 111.602] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 119.891] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 119.891] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 119.891] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 119.891] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 119.892] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 119.892] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 121.162] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 121.162] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 121.162] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 121.162] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 121.163] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 121.163] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 122.743] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 122.743] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 122.743] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 122.743] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 122.744] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 122.744] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 138.896] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 167.669] (II) NOUVEAU(0): NVEnterVT is called.
    [ 167.720] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
    [ 167.720] (II) NOUVEAU(0): Using hsync ranges from config file
    [ 167.720] (II) NOUVEAU(0): Using vrefresh ranges from config file
    [ 167.720] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 167.720] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 167.720] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 186.390] (II) NOUVEAU(0): NVLeaveVT is called.
    - .xsession-errors in gnome session :
    GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
    GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
    GPG_AGENT_INFO=/home/olivier/.cache/keyring-D3uSoF/gpg:0:1
    GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
    GPG_AGENT_INFO=/home/olivier/.cache/keyring-D3uSoF/gpg:0:1
    SSH_AUTH_SOCK=/home/olivier/.cache/keyring-D3uSoF/ssh
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    Failed to play sound: File or data not found
    ** Message: applet now removed from the notification area
    ** Message: applet now embedded in the notification area
    Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
    Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
    nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
    (gnome-shell:700): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'.
    Individuals will not be linked properly and creating new links between Personas will not work.
    The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
    (gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
    (gnome-settings-daemon:657): color-plugin-WARNING **: Done switch to new account, reload devices
    (gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
    (gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
    Last edited by Jejel59 (2012-09-06 11:34:53)

    I'm no expert on reading the xsession errors, but I had all sorts of problems running gnome3 with my machine of the same vintage.   Cinamon is based on gnome3.  I switched to Mate which is a re-packaging of the old gnome2 along with Compiz for the window manager and all works well.
    I strongly suspect that they are using the newer OpenGL 4 API.  The Nvidia FX5200 is stuck at OpenGL 2.1.

  • Sporadic hangups, and now some graphics issue

    Mid 2010 15" MBP, OS X 10.6.8 with all software up to date, Core i5 2.53ghz, 8gb RAM here. Every so often when I've had the laptop on (with some occasional sleep) for a few days, it becomes unresponsive and I have to hold the power button in order to get anywhere with it. I've dealt with this for a while, and it's not too much of a concern. I upgraded from 4gb to 8gb RAM to see if that could help, but I'm not sure if that helped at all.
    Now I've encountered a pretty strange graphical issue. The laptop became unresponsive, and google chrome began rendering very strangely. The dock had this happen as well. Terminal windows I had open were unaffected. After some time, the laptop became responsive again, albeit sluggishly. Screenshot of Chrome:
    Any idea what's causing this? Should I be worried? I still have applecare, so if necessary I can bring it in to a service center without worrying about cost, but I'm writing a thesis and I'd rather not have to relocate everything to my windows box and find a whole new set of software for experimentation/writing/etc. Thanks for reading.

    Can you post a link to a public page that doesn't require authentication (log in) to access it?
    Reload web page(s) and bypass the cache.
    *Press and hold Shift and left-click the Reload button.
    *Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
    *Press "Cmd + Shift + R" (MAC)
    A good place to ask advice about web development is at the MozillaZine "Web Development/Standards Evangelism" forum.
    *http://forums.mozillazine.org/viewforum.php?f=25
    The helpers at that forum are more knowledgeable about web development issues.<br>
    You need to register at the MozillaZine forum site in order to post at that forum.

  • Graphic issues in Word 2010 and 2013

    The problem is it reformats your original image to fall within this shape below. Everything within that triangle is white and your original image only shows through the remaining part of the oval. I have attached a Word document with a few examples. It cuts
    off part of the logo, signatures, etc. 
    So far, we have found this occurring in 2 situations:
    1. .docx is generated in third party application. We open this in Word 2003 and save as .doc. Then if that .doc is then opened by someone else using Word 2010 or 2013, it has this issue.
    2. The other situation was just a .doc created (outside of the third party application) that is used as a VBA component. If they open that .doc in Word 2013 it has this issue but other .doc files are fine.
    One other note, we can open these files in Word 2003 and 2007 and the images look fine. It only happens when opening in Word 2010 or 2013.
    Has anyone experienced this or have any suggestions? I have tested both .tif & .jpg to see if the original image format made a difference and it doesn’t appear to. Unfortunately, it’s impacting tens of thousands of Word docs stored in archive.
    I don't see where I could upload a file, but I do have example documents.
    Thanks,
    Dawn

    Hi Dawn:
    After testing from myside, I found if you
    change the picture format, it will fix the display issue. You can
    manually changing the format of the Graphic: select the graphic->select format tab on the Ribbon->change to any format you want. You can also
    use VBA code to change the format of the picture, for detailed information you can refer to
    This article.
    Below are some findings for your reference.
    I checked the documents you sent to me, as the issue occurred when if the file saved as .docx or opened with word 2010/2013, so I zipped the file and compared the xml files, I found something
    might be the cause of this issue.
    The pictures in media folder were all fine no missing parts even for those ones displayed wrongly in Word.
    I compared the document.xml file under ….\Graphic issue\Issue.docx\word(where I stored the zip file), I found the documents.xml of issue.docx file has section called <a:custGeom>………
    </a:custGeom>, which contains data like below,  maybe it’s inherited from the design tool, somehow, change formatting can get rid of the custGeom. So we suggest you change the format of
    the picture.
    Definition of
    custGeom (Custom Geometry)This element specifies the existence of a custom geometric shape.
    Detailed Defination
    -<a:custGeom>
    <a:avLst/>
    -<a:gdLst>
    <a:gd name="G0" fmla="+- 0 0 0"/>
    <a:gd name="G1" fmla="+- 0 0 0"/>
    <a:gd name="G2" fmla="+- 0 0 0"/>
    <a:gd name="G3" fmla="+- 10800 0 0"/>
    <a:gd name="G4" fmla="+- 0 0 0"/>
    <a:gd name="T0" fmla="*/ 360 256 1"/>
    <a:gd name="T1" fmla="*/ 0 256 1"/>
    <a:gd name="G5" fmla="+- G2 T0 T1"/>
    <a:gd name="G6" fmla="?: G2 G2 G5"/>
    <a:gd name="G7" fmla="+- 0 0 G6"/>
    <a:gd name="G8" fmla="+- 0 0 0"/>
    <a:gd name="G9" fmla="+- 0 0 0"/>
    ………………………same type of data………………………………………
    <a:gd name="T31" fmla="*/ 10800 h 21600"/>
    <a:gd name="T32" fmla="*/ 10800 w 21600"/><a:gd name="T33" fmla="*/ 10800 h 21600"/>
    <a:gd name="T34" fmla="*/ 3163 w 21600"/>
    <a:gd name="T35" fmla="*/ 3163 h 21600"/>
    <a:gd name="T36" fmla="*/ 18437 w 21600"/>
    <a:gd name="T37" fmla="*/ 18437 h 21600"/></a:gdLst><a:ahLst/>
    -<a:cxnLst>
    -<a:cxn ang="0"><a:pos y="T5" x="T4"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T7" x="T6"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T9" x="T8"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T11" x="T10"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T13" x="T12"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T15" x="T14"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T17" x="T16"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T19" x="T18"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T21" x="T20"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T23" x="T22"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T25" x="T24"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T27" x="T26"/></a:cxn>
    -<a:cxn ang="0"><a:pos y="T29" x="T28"/></a:cxn>
    -<a:cxn ang="0">
    <a:pos y="T31" x="T30"/>
    </a:cxn>
    -<a:cxn ang="0">
    <a:pos y="T33" x="T32"/>
    </a:cxn>
    </a:cxnLst>
    <a:rect r="T36" b="T37" t="T35" l="T34"/>
    +<a:pathLst>
    </a:custGeom>

Maybe you are looking for