Switch from G to N causing system to freeze up

I work from home on a Lenovo Laptop. I connect to my work network, and ultimately to a midrange ISeries. For the past year I've had no major problems with my Netgear Linksys WRT54G. I switched to a Netgear N300 last weekend because my husband's desktop was having a lot of issues. His connection is much better now.
I'm able to connect to the internet with no problem, and I can access my company network & email pretty well. But, when I log on the ISeries it slows to way less than a crawl. According to my netwok icon, the connection is anywhere from 104 to 130 MBPS at any given time. But it freezes up so badly that it takes about 20 - 30 seconds just to type each letter, or to go from one window to another, or just to move the cursor down one line. It's infuriating. Every once in awhile if I disconnect and reconnect it works almost normally for awhile, but eventually slows down almost to a stop again. I actually worked for about 90 minutes the other day with no problem before it started acting up again. When I put the old G router back it works fine again.
Is there a setting that I'm missing, or something I don't know about that I could check? My laptop has an Intel(R) Centrino(R) Advanced-N 620 wireless adaptor. As long as I don't connect to the iseries, I have good speed and no issues with the internet or work intranet. Any ideas?

First of all, is this issue with the netgear router, or the Linksys router?
Second of all, if you're browsing the Internet and the typing is slow and all that, then it seems like a laptop issue.
I don't work for Cisco. I'm just here to help.

Similar Messages

Using Acrobat Pro XI to open PDF causes system to freeze.

Frequently, when I open a PDF document (double click the PDF file), my Adobe Acrobat Pro XI ver. 11.0.03, (and X before) causes my system to freeze (hourglass icon runs for up to 30 seconds) not allowing me to perform any other command, and less frequently causes Adobe Acrobat Pro XI to quit. Following the unexpected quit, Windows Error Reporting takes over and I am directed to Windows for a solution (http://wer.microsoft.com/responses/Response.aspx/5044/en-us/5.1.2600.2.00010100.3.0?SGD=83 458a54-94bd-481a-834b-9713fc92dccf&iBucketTable=1&iBucket=-692234318&BucketHash=e4711a21f7 5b0d1473d68945071e3721), and the solution always directs me to install Adobe Reader XI (11.0.03) (http://get.adobe.com/reader/). This occurs on a daily basis. Should I install Adobe Reader even though I have Adobe Acrobat Pro XI installed? Any ideas why my system hangs or why Adobe Acrobat Pro XI quits unexpectedly? My system is a Win XP Pro Version 2002 Service Pack 3 with all the latest updates installed; 3 GB Ram and Intel Core2 Duo CPU T5670 @ 1.80 GHz, Dell Vostro 2510. I have Norton Anti Virus and I have performed a nightly full system virus scan, and I have performed a deep system virus scan. There are no viruses.

Bill@VT: Thanks for the reply. I haven't tried the suggested steps, but will shortly. Will let you know what occurs.

Windows media player causing system to freeze

My system ran fine for a year or so. Recently my system started freezing almost randomly, mostly when watching videos. I tried using different video players however nothin seemed to change. I tried eliminating all the usual suspects but nothing seemed
to stop the freezing. I finally removed windows media player and the freezing seems to have stopped. I'm not looking for a solution as I'm perfectly fine running without wmp. I just wanted to let the community know about this issue.

Hi,
Since you mentioned that different video players however nothing seemed to change, I suspect there also might be caused by the incompatibility of video card.
Try the install the latest video card applied to your computer for test.
Karen Hu
TechNet Community Support

Google Chrome causing system to freeze

Google Chrome has been sporadically causing my system to freeze. It may work fine for a few days, or for less than twenty-four hours. Without warning, the browser will suddenly begin reading and waiting on its cache, and become unresponsive. When I try to force quit the application, the system locks up and Finder will freeze but imputs are still responsive, causing me to have to do a hard reboot. Once rebooted, Spotlight re-indexes my hard drive [which I believe is a separate issue (mdworker unable to talk to lsboxd)]. This only occurs with Google Chrome and is not replicable with other browsers or applications.
I have cleared all caches and reset my PRAM and SMC controller, but the issue persists. Any thoughts?
System info:
Early 2008 Macbook Pro (4,1)
OS 10.8.2
Chrome Version: 24.0.1312.57
Extensions: Disconnect 4.2.0, DoNotTrackMe 2.2.8.109, Ghostery 4.1.0, Reddit Enhancement Suite 4.1.5
Console log up until forced reboot:
2/5/13 12:40:06.603 PM mdworker[5062]: Unable to talk to lsboxd
2/5/13 12:40:07.000 PM kernel[0]: Sandbox: sandboxd(5063) deny mach-lookup com.apple.coresymbolicationd
2/5/13 12:40:07.457 PM sandboxd[5063]: ([5062]) mdworker(5062) deny mach-lookup com.apple.ls.boxd
2/5/13 12:42:08.365 PM mdworker[5066]: Unable to talk to lsboxd
2/5/13 12:42:08.629 PM sandboxd[5067]: ([5066]) mdworker(5066) deny mach-lookup com.apple.ls.boxd
2/5/13 12:42:08.000 PM kernel[0]: Sandbox: sandboxd(5067) deny mach-lookup com.apple.coresymbolicationd
2/5/13 12:45:27.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=5071[GoogleSoftwareUp] clearing CS_VALID
2/5/13 12:46:10.892 PM mdworker[5074]: Unable to talk to lsboxd
2/5/13 12:46:11.000 PM kernel[0]: Sandbox: sandboxd(5075) deny mach-lookup com.apple.coresymbolicationd
2/5/13 12:46:11.634 PM sandboxd[5075]: ([5074]) mdworker(5074) deny mach-lookup com.apple.ls.boxd
2/5/13 12:46:48.837 PM WindowServer[101]: Created shield window 0x685 for display 0x042720c0
2/5/13 12:46:48.837 PM WindowServer[101]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
2/5/13 12:46:48.849 PM WindowServer[101]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
2/5/13 12:47:41.744 PM WindowServer[101]: handle_will_sleep_auth_and_shield_windows: no lock state data
2/5/13 12:50:41.653 PM mdworker[5094]: Unable to talk to lsboxd
2/5/13 12:50:42.000 PM kernel[0]: Sandbox: sandboxd(5095) deny mach-lookup com.apple.coresymbolicationd
2/5/13 12:50:42.217 PM sandboxd[5095]: ([5094]) mdworker(5094) deny mach-lookup com.apple.ls.boxd
2/5/13 12:51:51.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1360065113
2/5/13 1:00:54.000 PM bootlog[0]: BOOT_TIME 1360065654 0

There are several "shared libraries" in the Extensions folder. There is also "Shared Library Manager" (and "Shared Library Manager PPC") which are not shared libraries themselves, but provides support for using shared libraries. Since you know the extensions, can you post back with their exact file names?

QuickLook causing system-wide freezes/hanging the Finder

Hello --
Just picked up a brand new MacBook Pro 2.5 GHz, 2GB RAM, 250 MB HD. Running 10.5.2.
QuickLook is causing my entire system to lock up and become completely unresponsive. Here's what is happening:
Using the Finder, I open a folder containing images and sometimes other folders. Anywhere from 6 to 80 images. Strictly JPGs and TIFFs, nothing unusual.
I hit command-A to select all, then command-Y to QuickLook.
QuickLook previews the first image in my selection. And the system is now locked up. My clock stops. Keyboard no longer works (cannot command-tab, cannot command-option-escape, cannot do anything with keyboard). Mouse pointer still moves around, but nothing responds to clicking. Sometimes I get the spinning beach ball for awhile, then it goes back to normal arrow pointer. Still, clicking does nothing, even if I wait. Have waited up to 10 minutes. I always end up pressing the power button to shut the machine down and then restart.
I can re-create this problem, but only when the folder in question has not been QuickLooked before. After forcing a reboot, I can return to the image folder that caused the freeze, open it, command-A, command-Y, and QuickLook works just fine. The QuickLook freeze seems to occur only on a group of images that have never been QuickLooked before.
If somebody has some tips on how I can troubleshoot this, or perhaps any fixes, I would be most grateful.
Thanks in advance!
Mike

...Does this help at all...?
Mar 12 18:53:26 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 0000000c
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 00200000 00005097 0000047c 00000000
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 00000486 00001224 00000001 00000003
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 00000000 00000000 01bff803
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 0000000c
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 00200000 00005097 0000047c 00000000
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 00000486 00001224 00000001 00000003
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 00000000 00000000 00000002
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:53:39 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:53:40 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:53:40 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:53:40 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:53:40 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:53:52 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel timeout!
Mar 12 18:53:52 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:53:52 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:04 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel timeout!
Mar 12 18:54:04 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:04 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel timeout!
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:16 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:17 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:29 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel timeout!
Mar 12 18:54:29 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 12 18:54:29 mwks-macbook-pro kernel[0]: 0000000b
Mar 12 18:54:41 mwks-macbook-pro kernel[0]: NVChannel(GL): Graphics channel timeout!
Mar 12 19:02:10 localhost kernel[0]: npvhash=4095

SB Audigy 4 causes system to freeze

Hello,
As the title suggests, I've got a problem with my Audigy 4. From time to time it will freeze my computer completely, often creating a sound loop or some wierd screeching noises. It mostly happens when playing certain games, but also sometimes in Windows or when watching video/TV. However it is not possible to predict if and when it will happen, as there are no signs of crashing before the actual freeze and it can happen after 5 minutes as well as after several hours.
The same happened by the way with my previous (completely different) system, I just didn't realize that it was the soundcard that caused those crashes...
My chipset and graphics drivers are up to date, as well as Win XP and DirectX. Of course I am also using the newest SB driver (2.8.000).
I know there are already plenty of threads about that issue, but well... it's not quite easy to get an overview.
I don't know if this is just a driver issue, some kind of hardware defect or... whatever.
So... I'd appreciate any help.
This is my current system:
CPU: AMD Phenom II X4 955 Black Edition
Mainboard: Gigabyte GA-MA770T-UD3P (AMD 770 chipset)
RAM: 2*2GB Corsair DDR3 333 ?
PSU: Enermax LibertyECO 500W
GPU: Sapphire Toxic Radeon HD 4890
HD: Western Digital Caviar Blue 640GB
TV: Leadtek Winfast PVR2000

Thanks for the hint, I gave it a try.
But unfortunately it didn't help.

One of four ipods causes system lockup/freeze

Off and on when my son connects his ipod to charge or load new songs, sometimes it freezes the entire system - iTunes and everything. i cannot move the mouse and keystrokes dont do anything either. I am forced to hold the power button to power down and startup again. His ipod is set to manual and only sync two items (one playlist and calendar) and it is NOT selected to use as a drive. I tried to restore the settings and start over; the problem still reoccurs.
Any ideas? This is more than iTunes lockup - I lose control of the whole system.

If turning up the fan speed seems to help you out then I'd be surprised if your issue wasn't heat-related. Then again, I wasn't able to diagnose my problem either so what do I know?
I know that heat isn't the issue for mine, though. The times that it froze were when the computer was all different temperatures. Also, when running intensive applications it didn't necessarily freeze.
Aaaaaaaaaanyhow, taking it in to the Apple Store today was certainly an experience. I know how they make all of their money now! It really makes me think that if they're able to diagnose the issue then I'm just going to fix it myself. Even though the RAM tested fine for me, the tech seemed to think that it was still a RAM issue. He wanted to keep the computer there so they could run some tests on it. They were going to quote me ~$190 to diagnose it and replace a single stick of RAM if that was the issue.
I mean.. seriously? $190? I can buy 2GB of RAM online that would work with the MBP for about $30. I know how to replace it myself. I told him I was going to replace it and see if that fixed the issue. He said it might be something else and offered a MUCH less costly diagnostic just to keep me from walking out of the store.
Anyhow, he also said that if it wasn't the RAM then more then likely the logic board would need to be replaced. It would cost ~$350 for them to ship it out for a diagnostic and then another ~$1200 for a logic board. Forget that. For ~$1550 I can buy a refurb MacBook Pro at the online Apple Store. It would be newer, faster and have a warranty. I've pretty much come to the conclusion that if it's not the RAM then I'll need to either find a logic board and replace it myself (I've found them on eBay for ~$500) or just get rid of it and get a new laptop. The new ThinkPads are looking pretty nice actually. We'll see. I'll update this thread once I get the final diagnosis.

Edit in Photoshop CS6 from LR 4.1 Causes PS to Freeze

I have uninstalled PS CS6 and Lightroom and reinstalled PS CS6 then LR4.1. When I select EDIT IN Photoshop CS6, PS opens but freezes after a few seconds and the file is never transferred into PS. Files will open when I select other 3rd party editors like Photomatix Pro.
LR Version 4.1
Camera RAW version 7.1
Photoshop Version
Adobe Photoshop Version: 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x64
Any help would be appreciated.
System Information:
Operating System: Windows 7 64-bit
Version: 6.1
System architecture: AMD CPU Family:15, Model:10, Stepping:0 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 6
Processor speed: 2812 MHz
Built-in memory: 16382 MB
Free memory: 12911 MB
Memory available to Photoshop: 14680 MB
Memory used by Photoshop: 70 %
Image tile size: 132K
Image cache levels: 4
The GPU Sniffer crashed on 5/31/2012 at 6:40:23 PM
OpenGL Drawing: Disabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: ATI Radeon HD 5570

Anyone? The only way I can edit in PS is to export to the HD as a TIFF, edit, then manually reimport into PS.

MSI N560GTX-Ti Twin Frozr II OC causes system to freeze

I'm having occassional freezes with my GTX 560 Ti Twin Frozr OC (system completely stops responding while display and sound freeze and it takes around 5 seconds for the PC to respond to reset button ie. to reboot). This happens, for example, under Windows 7 in 3DMark11 Deep Sea Demo and in Windows XP randomly, but most often in web browser when watching Adobe Flash content with hardware acceleration enabled? Maybe BIOS update could help? Thank you in advance.
My system specs are as follows:
Intel i5 2500k
MSI P67A-C43 Rev1.0
EXCELERAM 2x2GB E30101B (XMP selected in BIOS - 1600MHz)
MSI N560GTX-Ti Twin Frozr II OC
WD Caviar Blue WDC WD5000AAKX-001CA 500GB Sata 3.0
Dual Boot: Windows XP Pro SP3 32-bit updated / Windows 7 Ultimate SP1 64-bit updated
OCZ Stealth Xstream OCZ500SXS 500W +12V1~18A +12V2~18A, +5V~30A, +3.3V~30A

This is strange! I've just discovered that if I turn off C6 state (it's no problem to leave c states enabled, only need to set c state limit to C2) the freeze issue is gone. I guess my i5 2500k doesn't like c6 state or there is some kind of incompatibility between Intel C states and Windows or MSI P67A-C43 is ready for another BIOS update after version 1.9. What do you think Svet? After some quick googling on this issue I found out that Nehalem CPUs had somewhat similar problem.

Two questions: Compiz causes system to freeze and ati drivers

Hi everyone.
I have an ati integrated motherboard x1200 video card (r690 chipset), and of course arch64.
The first question:
When I activate compiz the system freezes randomly. I found an archwiki page where they put the following:
System freeze with ATI Express cardsI had to edit /etc/xorg.conf to avoid a system freeze with my PCI-Express ATI X700:
Section "Device"
Identifier "AtiGraphicsCard"
Driver "fglrx"
# I had to add these 2 options
Option "UseInternalAGPGART" "no"
Option "KernelModuleParm" "agplock=0"
BusID "PCI:1:0:0"
EndSection
I had to add those 2 Options to get it working properly. Other ATI PCI Express are reported to be affected too. (X200, X300, X600, X700, X1400... and possibly others)
I can't do that, because i don't have a xorg.conf file. The only way to change some parameters is with the driconf application, but i haven't found any documentation about those parameters...
And the second question: if i have an ati x1200 video card, which open source driver i have to install?
I have installed the xf86-video-ati. I wonder if that is the correct one.
Thanks.

Hyugga wrote:I' ve been using my arch64 with compiz with the "indirect-rendering" option activated and there is no freezes for now.
So, what is indirect-rendering anyways? Some one can explain it to me?
Thanks for the reply.
Your system is doing all of the 3D rendering in software in your CPU rather than using the direct method of using the GPU in your video card. It is slow and makes the CPU bandwidth unavailable for other things.

Can switching from CRT to LCD monitors cause system problems?

My 9.1 locks up periodically (but the cursor still moves) since I replaced two 20" CRT monitors with two Samsung 19" LCD monitors. Could this affect the performance of my machine? I've tried everything else to address the freeze problem but recall the issue started when I installed the LCD monitors. Anything I can do?

Studedot,
You may have issues with the amount of video memory depending on the resolutions of the new LCD screens.
I find LCD screens go up to insane resolutions, way more than the corresponding size CRT monitor, ie. a 17in Dell LCD monitor with higher resolution than a 21in CRT.
It shouldn't cause crashes or freezes, but may cause -redraw problems when closing / moving windows in 2D and playing 3D games.

Trying to switch from nvidia to nouveau; startx freezes system

I'm having high cpu issues, possibly related to nvidia and want to switch to nouveau to test this out. I followed the Arch Wiki for nouveau but am having issues being able to startx. My process:
- Logout of openbox
- Remove nvidia stuff:
# pacman -Rsc nvidia nvidia-utils opencl-nvidia
# pacman -S xf86-video-nouveau
Installing nouveau also prompted the removal of nvidia-libgl and replaced it with mesa-libgl, as well as the installation of nouvea-dri.
- Removed my existing monitor config file:
# mv /etc/X11/xorg.conf.d/10-monitor.conf /etc/X11/xorg.conf.d/10-monitor.conf.bk
- Verified that I have no modeset options specified to kernel options via syslinux, nor blacklisting of nouveau in /etc/modprobe.d/ files.
$ cat /etc/modprobe.d/modprobe.conf
# /etc/modprobe.d/modprobe.conf
blacklist uvcvideo
blacklist pcspkr
$ ls /etc/X11/xorg.conf.d/
10-evdev.conf 10-monitor.conf.bk 10-quirks.conf 50-synaptics.conf
Nothing related to monitors or screens in 10-evdev, 10-quirks or 50-synaptics, and the 10-monitor.conf.bk file has the following contents (just in the event it *is* picked up by Xorg):
$ cat /etc/X11/xorg.conf.d/10-monitor.conf.bk
Section "Monitor"
Identifier "Monitor0"
ModelName "LGD"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
# Option "Enable" "True"
# Option "PreferredMode" "1600x900"
EndSection
Section "Device"
Identifier "Device0"
Driver "nouveau"
# Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro FX 1800M"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x900"
EndSubSection
# Option "SLI" "Auto"
# Option "AddARGBGLXVisuals" "True"
EndSection
- Reboot
I am at work and have my computer docked. Nouveau seemed to be active, observed by the fact that it auto-switched to KMS during boot. It also picked up my external monitor, which was off, and started duplicating the display on my external monitor and laptop during text boot (which nvidia does not do). The laptop had what I'll call "screen artifacts" on the lower right (white lines, jumbled pixels) after switching to KMS, but not a huge deal. I went to startx and it just froze after spitting out the various initialization lines. I have to hard kill and reboot. From there, I uninstall nouveau, re-install nvidia (which replaces mesa-libgl with nvidia-libgl), and reboot again to a working system.
Any suggestions?
Last edited by jwhendy (2013-10-24 16:36:15)

Here's the recent Xorg.log:
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 102.581] X Protocol Version 11, Revision 0
[ 102.581] Build Operating System: Linux 3.11.1-1-ARCH x86_64
[ 102.581] Current Operating System: Linux bigBang 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
[ 102.581] Kernel command line: root=/dev/mapper/root cryptdevice=/dev/sda3:root ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 102.581] Build Date: 08 October 2013 08:48:10PM
[ 102.581]
[ 102.581] Current version of pixman: 0.30.2
[ 102.581] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 102.581] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 102.582] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 24 19:46:30 2013
[ 102.599] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 102.618] (==) No Layout section. Using the first Screen section.
[ 102.618] (==) No screen section available. Using defaults.
[ 102.618] (**) |-->Screen "Default Screen Section" (0)
[ 102.618] (**) | |-->Monitor "<default monitor>"
[ 102.618] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 102.618] (==) Automatically adding devices
[ 102.618] (==) Automatically enabling devices
[ 102.618] (==) Automatically adding GPU devices
[ 102.666] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 102.666] Entry deleted from font path.
[ 102.666] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 102.667] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 102.667] Entry deleted from font path.
[ 102.667] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 102.667] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 102.667] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 102.667] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 102.667] (II) Loader magic: 0x7fdc20
[ 102.667] (II) Module ABI versions:
[ 102.667] X.Org ANSI C Emulation: 0.4
[ 102.667] X.Org Video Driver: 14.1
[ 102.667] X.Org XInput driver : 19.1
[ 102.667] X.Org Server Extension : 7.0
[ 102.667] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 102.671] (--) PCI:*(0:1:0:0) 10de:0cbc:103c:1521 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
[ 102.671] Initializing built-in extension Generic Event Extension
[ 102.672] Initializing built-in extension SHAPE
[ 102.672] Initializing built-in extension MIT-SHM
[ 102.672] Initializing built-in extension XInputExtension
[ 102.672] Initializing built-in extension XTEST
[ 102.672] Initializing built-in extension BIG-REQUESTS
[ 102.672] Initializing built-in extension SYNC
[ 102.672] Initializing built-in extension XKEYBOARD
[ 102.673] Initializing built-in extension XC-MISC
[ 102.674] Initializing built-in extension SECURITY
[ 102.675] Initializing built-in extension XINERAMA
[ 102.676] Initializing built-in extension XFIXES
[ 102.677] Initializing built-in extension RENDER
[ 102.678] Initializing built-in extension RANDR
[ 102.679] Initializing built-in extension COMPOSITE
[ 102.680] Initializing built-in extension DAMAGE
[ 102.681] Initializing built-in extension MIT-SCREEN-SAVER
[ 102.682] Initializing built-in extension DOUBLE-BUFFER
[ 102.683] Initializing built-in extension RECORD
[ 102.684] Initializing built-in extension DPMS
[ 102.684] Initializing built-in extension X-Resource
[ 102.685] Initializing built-in extension XVideo
[ 102.686] Initializing built-in extension XVideo-MotionCompensation
[ 102.687] Initializing built-in extension XFree86-VidModeExtension
[ 102.688] Initializing built-in extension XFree86-DGA
[ 102.689] Initializing built-in extension XFree86-DRI
[ 102.690] Initializing built-in extension DRI2
[ 102.690] (II) LoadModule: "glx"
[ 102.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 102.719] (II) Module glx: vendor="X.Org Foundation"
[ 102.719] compiled for 1.14.3, module version = 1.0.0
[ 102.719] ABI class: X.Org Server Extension, version 7.0
[ 102.719] (==) AIGLX enabled
[ 102.721] Loading extension GLX
[ 102.721] (==) Matched nouveau as autoconfigured driver 0
[ 102.721] (==) Matched nvidia as autoconfigured driver 1
[ 102.721] (==) Matched nv as autoconfigured driver 2
[ 102.721] (==) Matched nouveau as autoconfigured driver 3
[ 102.721] (==) Matched nvidia as autoconfigured driver 4
[ 102.721] (==) Matched nv as autoconfigured driver 5
[ 102.721] (==) Matched vesa as autoconfigured driver 6
[ 102.721] (==) Matched modesetting as autoconfigured driver 7
[ 102.721] (==) Matched fbdev as autoconfigured driver 8
[ 102.721] (==) Assigned the driver to the xf86ConfigLayout
[ 102.721] (II) LoadModule: "nouveau"
[ 102.721] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 102.751] (II) Module nouveau: vendor="X.Org Foundation"
[ 102.751] compiled for 1.14.2, module version = 1.0.9
[ 102.751] Module class: X.Org Video Driver
[ 102.751] ABI class: X.Org Video Driver, version 14.1
[ 102.751] (II) LoadModule: "nvidia"
[ 102.765] (WW) Warning, couldn't open module nvidia
[ 102.765] (II) UnloadModule: "nvidia"
[ 102.765] (II) Unloading nvidia
[ 102.765] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 102.765] (II) LoadModule: "nv"
[ 102.765] (WW) Warning, couldn't open module nv
[ 102.765] (II) UnloadModule: "nv"
[ 102.765] (II) Unloading nv
[ 102.765] (EE) Failed to load module "nv" (module does not exist, 0)
[ 102.765] (II) LoadModule: "vesa"
[ 102.765] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 102.776] (II) Module vesa: vendor="X.Org Foundation"
[ 102.776] compiled for 1.14.0, module version = 2.3.2
[ 102.776] Module class: X.Org Video Driver
[ 102.776] ABI class: X.Org Video Driver, version 14.1
[ 102.776] (II) LoadModule: "modesetting"
[ 102.776] (WW) Warning, couldn't open module modesetting
[ 102.776] (II) UnloadModule: "modesetting"
[ 102.776] (II) Unloading modesetting
[ 102.776] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 102.776] (II) LoadModule: "fbdev"
[ 102.776] (WW) Warning, couldn't open module fbdev
[ 102.776] (II) UnloadModule: "fbdev"
[ 102.776] (II) Unloading fbdev
[ 102.776] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 102.776] (II) NOUVEAU driver
[ 102.776] (II) NOUVEAU driver for NVIDIA chipset families :
[ 102.776] RIVA TNT (NV04)
[ 102.776] RIVA TNT2 (NV05)
[ 102.776] GeForce 256 (NV10)
[ 102.776] GeForce 2 (NV11, NV15)
[ 102.776] GeForce 4MX (NV17, NV18)
[ 102.776] GeForce 3 (NV20)
[ 102.776] GeForce 4Ti (NV25, NV28)
[ 102.776] GeForce FX (NV3x)
[ 102.776] GeForce 6 (NV4x)
[ 102.776] GeForce 7 (G7x)
[ 102.776] GeForce 8 (G8x)
[ 102.776] GeForce GTX 200 (NVA0)
[ 102.776] GeForce GTX 400 (NVC0)
[ 102.776] (II) VESA: driver for VESA chipsets: vesa
[ 102.776] (++) using VT number 1
[ 102.776] (II) [drm] nouveau interface version: 1.1.1
[ 102.777] (WW) Falling back to old probe method for vesa
[ 102.777] (II) Loading sub module "dri2"
[ 102.777] (II) LoadModule: "dri2"
[ 102.777] (II) Module "dri2" already built-in
[ 102.777] (--) NOUVEAU(0): Chipset: "NVIDIA NVA3"
[ 102.777] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 102.777] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 102.777] (==) NOUVEAU(0): RGB weight 888
[ 102.777] (==) NOUVEAU(0): Default visual is TrueColor
[ 102.777] (==) NOUVEAU(0): Using HW cursor
[ 102.777] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 102.777] (==) NOUVEAU(0): Page flipping enabled
[ 102.777] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 102.845] (II) NOUVEAU(0): Output LVDS-1 has no monitor section
[ 102.950] (II) NOUVEAU(0): Output DP-1 has no monitor section
[ 103.056] (II) NOUVEAU(0): Output DP-2 has no monitor section
[ 103.056] (II) NOUVEAU(0): Output eDP-1 has no monitor section
[ 103.163] (II) NOUVEAU(0): Output DP-3 has no monitor section
[ 103.184] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 103.211] (II) NOUVEAU(0): EDID for output LVDS-1
[ 103.211] (II) NOUVEAU(0): Manufacturer: CMO Model: 1595 Serial#: 0
[ 103.211] (II) NOUVEAU(0): Year: 2009 Week: 12
[ 103.211] (II) NOUVEAU(0): EDID Version: 1.3
[ 103.211] (II) NOUVEAU(0): Digital Display Input
[ 103.211] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 19
[ 103.211] (II) NOUVEAU(0): Gamma: 2.20
[ 103.211] (II) NOUVEAU(0): No DPMS capabilities specified
[ 103.211] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 103.211] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 103.211] (II) NOUVEAU(0): redX: 0.610 redY: 0.343 greenX: 0.342 greenY: 0.581
[ 103.211] (II) NOUVEAU(0): blueX: 0.162 blueY: 0.083 whiteX: 0.313 whiteY: 0.329
[ 103.211] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 103.211] (II) NOUVEAU(0): Supported detailed timing:
[ 103.211] (II) NOUVEAU(0): clock: 107.8 MHz Image Size: 344 x 193 mm
[ 103.211] (II) NOUVEAU(0): h_active: 1600 h_sync: 1626 h_sync_end 1686 h_blank_end 1892 h_border: 0
[ 103.211] (II) NOUVEAU(0): v_active: 900 v_sync: 909 v_sync_end 919 v_blanking: 949 v_border: 0
[ 103.212] (II) NOUVEAU(0): N156O6-L01
[ 103.212] (II) NOUVEAU(0): CMO
[ 103.212] (II) NOUVEAU(0): N156O6-L01
[ 103.212] (II) NOUVEAU(0): EDID (in hex):
[ 103.212] (II) NOUVEAU(0): 00ffffffffffff000daf951500000000
[ 103.212] (II) NOUVEAU(0): 0c130103802213780a7b959c57579429
[ 103.212] (II) NOUVEAU(0): 15505400000001010101010101010101
[ 103.212] (II) NOUVEAU(0): 0101010101011c2a4024618431301a3c
[ 103.212] (II) NOUVEAU(0): 9a0058c110000018000000fe004e3135
[ 103.212] (II) NOUVEAU(0): 364f362d4c30310a2020000000fe0043
[ 103.212] (II) NOUVEAU(0): 4d4f0a202020202020202020000000fe
[ 103.212] (II) NOUVEAU(0): 004e3135364f362d4c30310a2020001c
[ 103.212] (II) NOUVEAU(0): Printing probed modes for output LVDS-1
[ 103.212] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 103.212] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
[ 103.316] (II) NOUVEAU(0): EDID for output DP-1
[ 103.423] (II) NOUVEAU(0): EDID for output DP-2
[ 103.423] (II) NOUVEAU(0): EDID for output eDP-1
[ 103.530] (II) NOUVEAU(0): EDID for output DP-3
[ 103.550] (II) NOUVEAU(0): EDID for output VGA-1
[ 103.550] (II) NOUVEAU(0): Output LVDS-1 connected
[ 103.550] (II) NOUVEAU(0): Output DP-1 disconnected
[ 103.550] (II) NOUVEAU(0): Output DP-2 disconnected
[ 103.551] (II) NOUVEAU(0): Output eDP-1 disconnected
[ 103.551] (II) NOUVEAU(0): Output DP-3 disconnected
[ 103.551] (II) NOUVEAU(0): Output VGA-1 disconnected
[ 103.551] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 103.551] (II) NOUVEAU(0): Output LVDS-1 using initial mode 1600x900
[ 103.551] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 103.551] (--) NOUVEAU(0): Virtual size is 1600x900 (pitch 0)
[ 103.551] (**) NOUVEAU(0): Driver mode "1600x900": 107.8 MHz (scaled from 0.0 MHz), 57.0 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 103.551] (**) NOUVEAU(0): Driver mode "1152x864": 81.8 MHz (scaled from 0.0 MHz), 53.8 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
[ 103.551] (==) NOUVEAU(0): DPI set to (96, 96)
[ 103.551] (II) Loading sub module "fb"
[ 103.551] (II) LoadModule: "fb"
[ 103.551] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 105.504] (II) Module fb: vendor="X.Org Foundation"
[ 105.504] compiled for 1.14.3, module version = 1.0.0
[ 105.504] ABI class: X.Org ANSI C Emulation, version 0.4
[ 105.504] (II) Loading sub module "exa"
[ 105.504] (II) LoadModule: "exa"
[ 105.504] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 105.508] (II) Module exa: vendor="X.Org Foundation"
[ 105.508] compiled for 1.14.3, module version = 2.6.0
[ 105.508] ABI class: X.Org Video Driver, version 14.1
[ 105.508] (II) Loading sub module "shadowfb"
[ 105.508] (II) LoadModule: "shadowfb"
[ 105.508] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 105.518] (II) Module shadowfb: vendor="X.Org Foundation"
[ 105.518] compiled for 1.14.3, module version = 1.0.0
[ 105.518] ABI class: X.Org ANSI C Emulation, version 0.4
[ 105.518] (II) UnloadModule: "vesa"
[ 105.518] (II) Unloading vesa
[ 105.518] (--) Depth 24 pixmap format is 32 bpp
[ 105.521] (II) NOUVEAU(0): Opened GPU channel 0
[ 105.547] (II) NOUVEAU(0): [DRI2] Setup complete
[ 105.547] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 105.547] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 108.224] (II) EXA(0): Driver allocated offscreen pixmaps
[ 108.224] (II) EXA(0): Driver registered support for the following operations:
[ 108.224] (II) Solid
[ 108.224] (II) Copy
[ 108.224] (II) Composite (RENDER acceleration)
[ 108.224] (II) UploadToScreen
[ 108.224] (II) DownloadFromScreen
[ 108.224] (==) NOUVEAU(0): Backing store disabled
[ 108.224] (==) NOUVEAU(0): Silken mouse enabled
[ 108.226] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 108.226] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 108.226] (==) NOUVEAU(0): DPMS enabled
[ 108.226] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 108.228] (--) RandR disabled
[ 142.503] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 142.503] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 142.504] (II) AIGLX: enabled GLX_ARB_create_context
[ 142.504] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 142.504] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 142.504] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 142.504] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 142.505] (II) AIGLX: Loaded and initialized nouveau
[ 142.505] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 159.503] (II) NOUVEAU(0): NVEnterVT is called.
[ 159.532] (II) NOUVEAU(0): Setting screen physical size to 423 x 238
[ 159.532] resize called 1600 900
[ 160.324] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 160.324] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 160.324] (II) LoadModule: "evdev"
[ 160.324] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 160.355] (II) Module evdev: vendor="X.Org Foundation"
[ 160.355] compiled for 1.14.3, module version = 2.8.2
[ 160.355] Module class: X.Org XInput Driver
[ 160.355] ABI class: X.Org XInput driver, version 19.1
[ 160.355] (II) Using input driver 'evdev' for 'Power Button'
[ 160.355] (**) Power Button: always reports core events
[ 160.355] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 160.355] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 160.355] (--) evdev: Power Button: Found keys
[ 160.355] (II) evdev: Power Button: Configuring as keyboard
[ 160.355] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 160.355] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 160.355] (**) Option "xkb_rules" "evdev"
[ 160.355] (**) Option "xkb_model" "pc104"
[ 160.355] (**) Option "xkb_layout" "us"
[ 160.392] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 160.392] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 160.392] (II) Using input driver 'evdev' for 'Video Bus'
[ 160.392] (**) Video Bus: always reports core events
[ 160.392] (**) evdev: Video Bus: Device: "/dev/input/event4"
[ 160.392] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 160.392] (--) evdev: Video Bus: Found keys
[ 160.392] (II) evdev: Video Bus: Configuring as keyboard
[ 160.392] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input4/event4"
[ 160.392] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 160.392] (**) Option "xkb_rules" "evdev"
[ 160.392] (**) Option "xkb_model" "pc104"
[ 160.393] (**) Option "xkb_layout" "us"
[ 160.393] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 160.393] (II) No input driver specified, ignoring this device.
[ 160.393] (II) This device may have been added with another device file.
[ 160.394] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 160.394] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 160.394] (II) Using input driver 'evdev' for 'Sleep Button'
[ 160.394] (**) Sleep Button: always reports core events
[ 160.394] (**) evdev: Sleep Button: Device: "/dev/input/event1"
[ 160.394] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 160.394] (--) evdev: Sleep Button: Found keys
[ 160.394] (II) evdev: Sleep Button: Configuring as keyboard
[ 160.394] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
[ 160.394] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 160.394] (**) Option "xkb_rules" "evdev"
[ 160.394] (**) Option "xkb_model" "pc104"
[ 160.394] (**) Option "xkb_layout" "us"
[ 160.395] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[ 160.396] (II) No input driver specified, ignoring this device.
[ 160.396] (II) This device may have been added with another device file.
[ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 160.396] (II) No input driver specified, ignoring this device.
[ 160.396] (II) This device may have been added with another device file.
[ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 160.397] (II) No input driver specified, ignoring this device.
[ 160.397] (II) This device may have been added with another device file.
[ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 160.397] (II) No input driver specified, ignoring this device.
[ 160.397] (II) This device may have been added with another device file.
[ 160.398] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 160.398] (II) No input driver specified, ignoring this device.
[ 160.398] (II) This device may have been added with another device file.
[ 160.398] (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event10)
[ 160.398] (II) No input driver specified, ignoring this device.
[ 160.398] (II) This device may have been added with another device file.
[ 160.399] (II) config/udev: Adding input device HDA Intel MID Dock Headphone (/dev/input/event7)
[ 160.399] (II) No input driver specified, ignoring this device.
[ 160.399] (II) This device may have been added with another device file.
[ 160.399] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event8)
[ 160.399] (II) No input driver specified, ignoring this device.
[ 160.399] (II) This device may have been added with another device file.
[ 160.400] (II) config/udev: Adding input device HDA Intel MID Line (/dev/input/event9)
[ 160.400] (II) No input driver specified, ignoring this device.
[ 160.400] (II) This device may have been added with another device file.
[ 160.400] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 160.400] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 160.401] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 160.401] (**) AT Translated Set 2 keyboard: always reports core events
[ 160.401] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 160.401] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 160.401] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 160.401] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 160.401] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 160.401] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 160.401] (**) Option "xkb_rules" "evdev"
[ 160.401] (**) Option "xkb_model" "pc104"
[ 160.401] (**) Option "xkb_layout" "us"
[ 160.402] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event11)
[ 160.402] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[ 160.402] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
[ 160.402] (**) PS/2 Generic Mouse: always reports core events
[ 160.402] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event11"
[ 160.402] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found relative axes
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
[ 160.402] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
[ 160.402] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[ 160.402] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 160.402] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event11"
[ 160.402] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 10)
[ 160.402] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
[ 160.402] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[ 160.403] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
[ 160.403] (II) No input driver specified, ignoring this device.
[ 160.403] (II) This device may have been added with another device file.
[ 160.403] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event17)
[ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 160.403] (II) LoadModule: "synaptics"
[ 160.403] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 160.415] (II) Module synaptics: vendor="X.Org Foundation"
[ 160.415] compiled for 1.14.1, module version = 1.7.1
[ 160.415] Module class: X.Org XInput Driver
[ 160.415] ABI class: X.Org XInput driver, version 19.1
[ 160.415] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 160.415] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 160.415] (**) Option "Device" "/dev/input/event17"
[ 160.503] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5600 (res 57)
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4884 (res 123)
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 160.503] (**) Option "VertScrollDelta" "250"
[ 160.503] (**) Option "VertTwoFingerScroll" "on"
[ 160.504] (**) Option "HorizTwoFingerScroll" "off"
[ 160.504] (**) Option "TapButton1" "1"
[ 160.504] (**) Option "TapButton2" "2"
[ 160.504] (**) Option "TapButton3" "3"
[ 160.504] (**) Option "CoastingSpeed" "0"
[ 160.504] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 160.504] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 160.530] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input17/event17"
[ 160.530] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11)
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 160.531] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 160.531] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 160.531] (II) No input driver specified, ignoring this device.
[ 160.531] (II) This device may have been added with another device file.
[ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event5)
[ 160.532] (II) No input driver specified, ignoring this device.
[ 160.532] (II) This device may have been added with another device file.
[ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
[ 160.532] (II) No input driver specified, ignoring this device.
[ 160.532] (II) This device may have been added with another device file.
[ 160.533] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event12)
[ 160.533] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 160.533] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[ 160.533] (**) HP WMI hotkeys: always reports core events
[ 160.533] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event12"
[ 160.533] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[ 160.533] (--) evdev: HP WMI hotkeys: Found keys
[ 160.533] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[ 160.533] (**) Option "config_info" "udev:/sys/devices/virtual/input/input12/event12"
[ 160.533] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 12)
[ 160.533] (**) Option "xkb_rules" "evdev"
[ 160.533] (**) Option "xkb_model" "pc104"
[ 160.533] (**) Option "xkb_layout" "us"
[ 164.083] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 164.083] (II) NOUVEAU(0): NVLeaveVT is called.
[ 181.123] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 181.123] (II) NOUVEAU(0): NVEnterVT is called.
[ 181.179] (II) NOUVEAU(0): EDID vendor "CMO", prod id 5525
[ 181.179] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 181.179] (II) NOUVEAU(0): Modeline "1600x900"x0.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 181.517] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 181.517] setversion 1.4 failed
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x5615bb]
(EE) 2: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
(EE) 3: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
(EE) 5: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 6: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 7: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
(EE) 8: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
(EE) 9: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
(EE) 10: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
(EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
(EE) 12: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
(EE) 13: /usr/bin/X (0x400000+0x170563) [0x570563]
(EE) 14: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
(EE) 15: /usr/bin/X (0x400000+0x104193) [0x504193]
(EE) 16: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 17: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
(EE) 19: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
(EE) 2: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
(EE) 4: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 5: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 6: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
(EE) 7: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
(EE) 8: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
(EE) 9: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
(EE) 10: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
(EE) 11: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
(EE) 12: /usr/bin/X (0x400000+0x170563) [0x570563]
(EE) 13: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
(EE) 14: /usr/bin/X (0x400000+0x104193) [0x504193]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
[ 216.437] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 216.438] [mi] EQ processing has resumed after 188 dropped events.
[ 216.438] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt02: Input/output error
[ 216.438] Failed to switch from vt01 to vt03: Input/output error
[ 216.438] Failed to switch from vt01 to vt04: Input/output error
[ 216.438] Failed to switch from vt01 to vt05: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt07: Input/output error
[ 216.438] Failed to switch from vt01 to vt08: Input/output error
[ 216.438] Failed to switch from vt01 to vt09: Input/output error
[ 216.438] Failed to switch from vt01 to vt10: Input/output error
[ 216.438] Failed to switch from vt01 to vt11: Input/output error
[ 216.438] Failed to switch from vt01 to vt02: Input/output error
[ 216.810] (II) evdev: HP WMI hotkeys: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) UnloadModule: "synaptics"
[ 216.811] (II) evdev: PS/2 Generic Mouse: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: AT Translated Set 2 keyboard: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Sleep Button: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Video Bus: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Power Button: Close
[ 216.811] (II) UnloadModule: "evdev"
In addition, I can't seem to find any other files related nvidia that seem like they would matter, except for ~/.nvidia-settings-rc, which I moved to ~/.nvidia-settings-rc.bk (prior to the attempt which created the log above). Keep in mind that this is after re-installing nvidia so I can startx and have a working system... Is there anything that looks like it wouldn't be removed by the nvidia package?
# find / -name *nvidia*
/proc/irq/63/nvidia
/proc/driver/nvidia
/home/jwhendy/.nvidia-settings-rc.bk
[hits from /usr/share/icons excluded]
[hits from /usr/share/ excluded]
/usr/lib/libnvidia-tls.so
/usr/lib/modules/extramodules-3.11-ARCH/nvidia.ko.gz
/usr/lib/modules/3.11.6-1-ARCH/kernel/drivers/net/ethernet/nvidia
/usr/lib/nvidia
/usr/lib/libnvidia-tls.so.325.15
/usr/lib/libnvidia-ml.so
/usr/lib/libnvidia-glcore.so
/usr/lib/vdpau/libvdpau_nvidia.so
/usr/lib/vdpau/libvdpau_nvidia.so.1
/usr/lib/vdpau/libvdpau_nvidia.so.325.15
/usr/lib/libnvidia-glcore.so.325.15
/usr/lib/libnvidia-ml.so.325.15
/usr/lib/libnvidia-cfg.so
/usr/lib/xorg/modules/drivers/nvidia_drv.so
/usr/lib/libnvidia-cfg.so.325.15
/usr/lib/modprobe.d/nvidia.conf # owned by nvidia; removed when I switch to nouveau
/usr/lib/libnvidia-cfg.so.1
/usr/lib/libnvidia-ml.so.1
/usr/bin/nvidia-settings
/usr/bin/nvidia-xconfig
/usr/bin/nvidia-smi
/usr/bin/nvidia-bug-report.sh
/usr/bin/nvidia-debugdump
/root/.nvidia-settings-rc
[hits from /var/abs/ removed]
/dev/nvidia0
/dev/nvidiactl
/sys/bus/pci/drivers/nvidia
/sys/kernel/slab/nvidia_p2p_page_t
/sys/module/drm/holders/nvidia
/sys/module/i2c_core/holders/nvidia
/sys/module/nvidia
/sys/module/nvidia/drivers/pci:nvidia
Anything look odd in the log or the files?
As always, feel free to suggest other things to try -- I can pipe ls into files to show what files are available when I'm pre-startx with nouveau installed, or more Xorg logs... My computer is not happy wtih nvidia at all and is nearly unusable. I really need to solve this until nvidia is compatible with 3.11 kernels again.

What would cause my iMac's desktop resolution to briefly readjust whenever I switch from my user to another?

I recently started to notice that whenever I switch from one user account to another on my recently purchased iMac, the resolution of my desktop wallpaper very briefly readjusts. Both users have the same default resolution and are using wallpaper that came standard with Mavericks. Does anyone have any suggestions as to what could be causing this?
Thanks!

Hello there, Conor68.
The following Knowledge Base article provides some great recommendations for troubleshooting display issues on your Mac:
Apple computers: Troubleshooting issues with video on internal or external displays
http://support.apple.com/kb/ht1573
Once you're reviewed the recommendations in regards to updates, this portion of the section on "No video or no signal, image distortion, "snow," or flickering" is useful:
Reset the system
You can reset the Mac's parameter RAM and SMC.
Reset the resolution
Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
Start up in Safe Mode.
From the Apple () menu, choose System Preferences.
Choose Displays from the View menu to open the preferences pane.
Select any resolution and refresh rate that your display supports.
Restart your computer.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

I have an iphone6. I am unsure whether to go from 8.1.3 operating system and switch to ICloud Drive or not? Has anyone done this? Is it awesome? I need to be able to access my resume from phone. I think this will help me achieve this.am i right?

I have an iphone6. I am unsure whether to go from 8.1.3 operating system and switch to ICloud Drive or not? Has anyone done this? Is it awesome? I need to be able to access my resume from phone. I think this will help me achieve this? Am i right? Is there any body out there right now that could help me? I'm thinking about going from 8.1.3 to I guess yosemite? Or is that for Mac computers? I don't understand the language entirely on the help page. Anyone's straight forward and easy stepped advice would be much appreciated. I'm so frustrated and I need a job so badly! Drowning in debt. Any help appreciated!
Thanks,
A

You're a Windows user, correct? If so, read here:
http://support.apple.com/kb/DL1455

Switch from G to N causing system to freeze up

Similar Messages

Maybe you are looking for