CKIP with LEAP on Intel 2200BG
Access Connections 5.2 and Intel 2200BG only WEP with LEAP but I need CKIP to connect to my office network.
Intel PRO/Wireless 2200BG Network driver 9.1.2.10 from Intel
After uninstalling, the Microsoft 9.1.0.104 Network driver as installed
Suggested patch Windows6.0-KB932063-x86 does not apply to my system (Post Vista SP1)
So I downloaded 7kwv50ww but it identified itself for 11abgn, abg, bg) but it installed fine but the IBM website said the 2200BG was not upported.
* Cisco LEAP version 1.0.11.0
* ThinkPad Power Mangaer 2.33
* ThinkVantage Access Connections version 5.22
* Hotkey Features Setup 2.08.2008
* Lenovo System Interface Driver 1.01.0805
* X41 Tablet with 2200BG Internal NIC
Intel site doesn't say CKIP isn't supported, so what do I try next?
And are there instructions on reading the diagnostic log file?
Message Edited by vorear on 10-04-2008 03:45 AM
I need to know this too. I have a Lenovo X61 and we need CKIP. I found only one Access Connections that would install on this laptop and it doesn't have CKIP.
I know that CKIP is considered "non-standard", or so I was told and that TKIP replaces that, but we need CKIP.
Similar Messages
-
Tecra A4: Wlan Intel 2200bg not stable with 802.11 G WLan
With the latest driver re-installed (9.0.4.39), I've found that a connection to a "g" network was unstable. (Slightly better than before re-installing, when it would connect to a "g" network but not pass any data.)
With both a BT Homehub and now a DLink DSL-2640R router (TalkTalk), I have found that one way to get a stable connection with the latest driver is to set the router to use only "b" networking. But this is slower.
Until I got a different router (recent change of telco provider) I had just assumed it was a BT Homehub problem (believe me, I had spent some time trying to resolve it!). However, now that I have tried two routers and found the same problem, I thought it might be an issue relating to the setup of the laptop...
I've kept the many wireless driver downloads that I've installed, and tried to think back to happy time when both laptop and homehub were happy to communicate on a "g" network. So I went back to driver version 9.0.4.17, and guess what, all the problems have gone away with the new router and it's happily connected to a "g" network.
Normally the advice is to use the latest driver version, so why would I have success with an older driver. What have I done wrong? I tried different types of encryption available and it hasn't affected the problem.
I've got the box ticked to allow windows to configure my network settings. I while ago I did try using the Proset Software, but that stopped the ConfigFree from running properly so I went back to the original set up.
Does anyone have any suggestions as to what I need to do to get a stable connection to a "g" network with an Intel 2200bg with the latest driver (9.0.4.39)? I'm wary that I may run into some other issues if I continue to use the older driver?There are always compatibility issues with Wireless products, especially when connecting with different brands. Manufacturers are constantly updating the drivers to fix issues, but sometimes it can introduce problems with older Adapters such as the 2200BG.
First thing to do is update the firmware on your Router, then update the drivers on the Wireless Adapter. If later drivers don't work, it wont hurt to revert back to a previous version.
You can also try changing the Advanced settings in the Wireless Adapters Properties in Device Manager. For example, try setting it to "802.11g only", try a different channel, try different power settings, etc.. -
Intel 2200BG NOT Fixed with Drivers!!!
I installed the Intel Pro/Wireless 2200BG mini PCI WLAN card into my Windows XP Pro SP2 Toshiba laptop (Toshiba Satellite 5205-S505). It will not access my Linksys BEFW11S4 v.2 Router!
Specifically, it will not connect to this router with (128-bit) WEP turned on. It WILL if I turn WEP off. My Sony Viao has no issues connecting.
I have installed the new 9.0.4.27 [1-19-07].
PLEASE HELP!!!!Message Edited by Byrdman on 03-21-200709:30 PMTry rolling back the wireless drivers in the Windows Device Manager to the previous version. My wife's laptop (Dell Inspiron 600m) has the Intel 2200BG wireless and she was also having trouble connecting to one Linksys wireless router, although the laptop would connect fine at her other offices (all with same wireless security settings -- not necessarily same hardware tho) and our Linksys router at home.
She told me after rolling the drivers back a version she was then able to connect to this particular network that was giving her grief. -
Mon0 error in airmon-ng on Dell Inspiron 6000 w/ Intel 2200BG wireless
I'm testing my home network's security, and no matter what I try,
sudo airmon-ng start wlp3s3
returns
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
2619 wpa_supplicant
2697 dhcpcd
Process with PID 2619 (wpa_supplicant) is running on interface wlp3s3
Process with PID 2697 (dhcpcd) is running on interface wlp3s3
Interface Chipset Driver
wlp3s3 Intel 2200BG ipw2200 - [phy0]
(monitor mode enabled on mon0)
mon0: ERROR while getting interface flags: No such device
iwconfig outputs
lo no wireless extensions.
eth0 no wireless extensions.
wlp3s3 IEEE 802.11abg ESSID:"wilrout"
Mode:Managed Frequency:2.457 GHz Access Point: 00:18:E7:E2:D4:72
Bit Rate:48 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=72/100 Signal level=-56 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:9Not all wireless cards can handle packet injection, which will be needed when using the aircrack-ng suite.
Two things stand out:
It appears that you are using your internal wireless card,(Intel 2200BG chipset) which may not support packet injection. Some chipsets won't work at all, some can be patched.
Simple fix: grab a wireless card (usb) from ebay that is known to work. My favorite is the netgear WG111v2, about $10.00 U.S.
It seems you are connected to the internet:
wlp3s3 IEEE 802.11abg ESSID:"wilrout"
Mode:Managed Frequency:2.457 GHz Access Point: 00:18:E7:E2:D4:72
You don't want to be connected for this.
The best place to start for you would be http://www.aircrack-ng.org/documentation.html
You can check your chipset and find any patches you may need, as well as follow their tutorials.
You tube also has a lot of video tutorials.
Good luck.
Edit: this may be of interest, note the "mon0: ERROR while getting interface flags: No such device" errors.
http://www.backtrack-linux.org/forums/s … hp?t=41677
Last edited by rfk1ll (2013-02-17 07:24:10) -
Satellite P10: How to enable Intel 2200BG WiFi card
Hi
I have a Satellite psp10e which I have recently installed an Intel 2200BG WiFi card. After having problems getting it to switch on I have put tape on pin 13 on the card to switch the radio on.
I have installed all the latest drivers/ BIOS updates and spending hours searching the internet I am still yet to find a cure to get the hardware switch/fn+f8 and the WiFi led to work.
Is there something that anybody has figured out to make the hardware switch/led work? There must be a better cure than a piece of tape!!! It is it the BIOS that has anything to do with the hardware switch?You cannot get it work with the switch because the Toshiba wireless cards have another pin to power off. And noone knows that pin. You could get one original toshiba from somewere and put it in and check out which pin is connected to the power switch.
Then you could change the pins on the new 2200b/g card. As the pins are very small and close together - it is nearly impossible to isolate them... But make your try ;) -
Intel 2200BG wifi nic and aironet 1131 LWAPP's
We recently had a nice sized installation of 1131 LWAPPS's (180) w/ WLC's and a WCS. The problem I'm having is out of the blue one day my Dell Latitude D400 w/ intell 2200BG internal wifi just disconnected and I wasn't able to reconnect. I've since formatted and rebuilt the system to ensure it's the latest n' greatest drivers (I'm running 9.0.4.13) from Dell. I checked Intel's site and they have 9.0.3.26 but nothing mentioned about the connection to LWAPP's problem. I can connect at home and other locations just fine. If I put in an external nic, I can connect to the 1131 LWAPP.
Suggestions? Help?
-Rob-Hi Rob,
My WLC current software version is 4.0.179.8. Please tell us the stability of 4.0.206.0.
I enabled only 802.11b and 802.11g in my LWAPP environment. The LAP model is LAP1242AG-C-K9. Antenna is AIR-ANT4941 (diversity).
I'm using L3 LWAPP transport mode; the two WLCs (within the same Mobility/RF group) are located at a centralized data center while the LAPs are located at a remote office building. WAN is MPLS L3 VPN. WLC redundancy mode is 1+1. All LAPs join to one controller; the other acts as hot standby.
Clients use Windows Zero Configuration (WZC). Encryption is WPA2/AES and user authentication is using Microsoft PEAP against a backend AD. ACS version 4.0.
Clients use Dell Latitude D610 with Intel PRO 2200BG chipset. Driver version is either 9.0.4.17 or the latest 9.0.4.26. They face frequent disconnections while users with 3945ABG chipset have more stable connections.
Please advise.
Thank you.
B.Rgds,
Lim TS -
I've been doing some maintenance and updating on a friends laptop and just updated a driver from the Intel site for their Intel Pro Wireless 2200BG Wireless adapter.
(Set to channel 2, using WPA-PSK encryption - working fine before the update) After installing it - the wireless won't connect to my Homehub v1 6.2.6.E
The adapter is working fine and seeing various networks with good signal strength. They also have a HH at home, also v1 - I haven't tried that one yet.
My other devices work fine on the wifi. I rebooted both hub and computer. The adapter can see several networks - I tried turning off the windows firewall - that didn't make any difference.
It tries to connect but never acquires a network address. Device manager reports no problems or conflicts. Intel (R) Pro wireless 2200BG Intel - 19.12.2007 9.0.4.39 - w29n515s.dll 9.0.4.95 - netwc32.dll 9.0.4.95 netwr32.dll I've checked the various settings, and tried setting it to connect via 802.11b only instead of g I don't know about the various other settings.
Anyone any ideas? The machine has a non connected ethernet adapter, and a mysterious other adapter Anyone any ideas? Otherwise I have just messed up my friends wireless connection. I'm fairly sure the adapter is working fine, it is just not connecting with the hub which makes me think there are some defaults that have changed. I see a fair bit about these 2200BG Wireless adapters and BT Homehub wifie problems in google - but not sure if it applies as the 2200BG was working before the driver "update".
My broadband secrets and tipsOkay I've given up with the Intel 2200BG- I've jumped through all the hoops I can think of - uninstalled the adapter replaced the original manufacturers old drivers, uninstalled again, updated with Intel drivers from last year, tried on an unencrypted HHub network. Anyone recommend a replacement internal WiFi adapter for the Intel 2200BG Mini PCI to go in a Hi-Grade Green 553 Notebook? I've also tried running the hub and adapter in the b mode only, with the hub also only running in b mode.
It can detect all the networks and the software all works fine, it it can not connect. No matter WHAT I do.
Must be compatible with Win XP Home, the Hi Grade laptop and the BTHomeHub v1- and come with compatible drivers.
They look to be reasonably priced, and I'd rather get some friendly supportive peer to peer advice here before trusting myself to PCNurld.
If the worst comes to the worst I could always get a usb wifi adapter and forget the internal interface.
Again - thanks for any help
My broadband secrets and tips -
Problem with 3 monitors Intel HD Graphics and GeForce GTX 560
I would like to attach 3 monitors to my box -- 1 to integrated Intel card and 2 to discreet Nvidia. I've tried different configs but I failed to make monitors connected to different cards to work at the same time. I have system with stock kernel, latest updates and the following configuration:
$ lspci | egrep "VGA|Disp"
00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
$ pacman -Qi xorg-server xf86-video-intel nvidia awesome-git linux | egrep "Name|Version"
Name : xorg-server
Version : 1.17.1-3
Name : xf86-video-intel
Version : 2.99.917-3
Name : nvidia
Version : 346.47-3
Name : awesome-git
Version : 3.5.2.397.gdde5b1b-1
Name : linux
Version : 3.18.6-1
$ lsmod | egrep 'i915|nvidia'
nvidia 8335766 46
i915 946695 2
button 12953 1 i915
i2c_algo_bit 12744 1 i915
video 18043 2 i915,asus_wmi
drm_kms_helper 80985 1 i915
drm 263481 7 i915,drm_kms_helper,nvidia
i2c_core 50152 6
drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nvidia
intel_gtt 17848 2 i915,intel_agp
I've tried different xorg configs. Here is the best one. All 3 monitors are active with it (I could drag cursor over them) but only 2 (which connected to nvidia card) display DE.
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "SAM"
ModelName "Samsung SMS27A850"
HorizSync 30.0 - 90.0
VertRefresh 56.0 - 75.0
Option "DPMS"
DisplaySize 597 336 # In millimeters
EndSection
Section "Monitor"
Identifier "VS"
ModelName "ViewSonic VG1930wm"
Option "DPMS"
Option "RightOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Monitor"
Identifier "BNQ"
ModelName "BenQ FP737s"
Option "DPMS"
Option "LeftOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-1" "SAM"
Option "Monitor-DVI-I-2" "VS"
EndSection
Section "Device"
Identifier "intel"
Driver "intel"
Option "AccelMethod" "none"
VendorName "Intel"
BoardName "Intel Integrated Graphic Controller"
BusID "00:02:0"
Option "Monitor-VGA-0" "BNQ"
EndSection
Section "Screen"
Identifier "SAM-Screen"
Device "nvidia"
Monitor "SAM"
EndSection
Section "Screen"
Identifier "VS-Screen"
Device "nvidia"
Monitor "VS"
EndSection
Section "Screen"
Identifier "BNQ-Screen"
Device "intel"
Monitor "BNQ"
EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "SAM-Screen"
Screen 1 "VS-Screen" RightOf "SAM-Screen"
Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
Option "Xinerama" "0"
EndSection
Also, xrandr shows last monitor (VGA-0, it plugged into Intel card) as disconnected
$ xrandr
Screen 0: minimum 8 x 8, current 3460 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
2560x1440 59.95*+
1920x1200 59.88
1920x1080 60.00 50.00
1680x1050 59.95
1600x1200 60.00
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 60.00 50.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-I-2 connected 900x1440+2560+0 left (normal left inverted right x axis y axis) 410mm x 256mm
1440x900 59.89*+ 74.98
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
640x400 70.10
But it's still posible to start application on last monitor with 'env DISPLAY:=0.1 urxvt'
Here is full Xorg log file and highlights:
[ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
[ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
[ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
[ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
[ 4792.053] (EE) intel(G0): Failed to claim DRM device.
[ 4792.053] (II) UnloadModule: "intel"
[ 4789.342]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 4789.342] X Protocol Version 11, Revision 0
[ 4789.342] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 4789.342] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
[ 4789.342] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
[ 4789.342] Build Date: 22 February 2015 12:50:32PM
[ 4789.342]
[ 4789.342] Current version of pixman: 0.32.6
[ 4789.342] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4789.342] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4789.342] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:43:55 2015
[ 4789.342] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4789.342] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4789.342] (==) ServerLayout "Layout0"
[ 4789.342] (**) |-->Screen "SAM-Screen" (0)
[ 4789.342] (**) | |-->Monitor "SAM"
[ 4789.343] (**) | |-->Device "nvidia"
[ 4789.343] (**) |-->Screen "VS-Screen" (1)
[ 4789.343] (**) | |-->Monitor "VS"
[ 4789.343] (**) | |-->Device "nvidia"
[ 4789.343] (**) |-->Screen "BNQ-Screen" (2)
[ 4789.343] (**) | |-->Monitor "BNQ"
[ 4789.343] (**) | |-->Device "intel"
[ 4789.343] (**) Option "Xinerama" "0"
[ 4789.343] (==) Automatically adding devices
[ 4789.343] (==) Automatically enabling devices
[ 4789.343] (==) Automatically adding GPU devices
[ 4789.343] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 4789.343] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4789.343] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4789.343] (II) Loader magic: 0x815d80
[ 4789.343] (II) Module ABI versions:
[ 4789.343] X.Org ANSI C Emulation: 0.4
[ 4789.343] X.Org Video Driver: 19.0
[ 4789.343] X.Org XInput driver : 21.0
[ 4789.343] X.Org Server Extension : 9.0
[ 4789.344] (EE) systemd-logind: failed to get session: PID 10086 does not belong to any known session
[ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 4789.345] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4789.347] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 4789.347] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 4789.347] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4789.347] (II) LoadModule: "glx"
[ 4789.347] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4789.359] (II) Module glx: vendor="NVIDIA Corporation"
[ 4789.359] compiled for 4.0.2, module version = 1.0.0
[ 4789.359] Module class: X.Org Server Extension
[ 4789.359] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 4789.359] (II) LoadModule: "nvidia"
[ 4789.359] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 4789.360] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 4789.360] compiled for 4.0.2, module version = 1.0.0
[ 4789.360] Module class: X.Org Video Driver
[ 4789.360] (II) LoadModule: "intel"
[ 4789.360] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 4789.360] (II) Module intel: vendor="X.Org Foundation"
[ 4789.360] compiled for 1.17.1, module version = 2.99.917
[ 4789.360] Module class: X.Org Video Driver
[ 4789.360] ABI class: X.Org Video Driver, version 19.0
[ 4789.360] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 4789.360] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 4789.360] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 4789.360] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 4789.360] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 4789.360] (++) using VT number 7
[ 4789.471] (II) Loading sub module "fb"
[ 4789.471] (II) LoadModule: "fb"
[ 4789.471] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 4789.471] (II) Module fb: vendor="X.Org Foundation"
[ 4789.471] compiled for 1.17.1, module version = 1.0.0
[ 4789.471] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4789.472] (II) Loading sub module "wfb"
[ 4789.472] (II) LoadModule: "wfb"
[ 4789.472] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 4789.472] (II) Module wfb: vendor="X.Org Foundation"
[ 4789.472] compiled for 1.17.1, module version = 1.0.0
[ 4789.472] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4789.472] (II) Loading sub module "ramdac"
[ 4789.472] (II) LoadModule: "ramdac"
[ 4789.472] (II) Module "ramdac" already built-in
[ 4789.473] (II) intel(1): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
[ 4789.474] (II) intel(G0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
[ 4789.474] (II) NVIDIA(0): Creating default Display subsection in Screen section
"SAM-Screen" for depth/fbbpp 24/32
[ 4789.474] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 4789.474] (==) NVIDIA(0): RGB weight 888
[ 4789.474] (==) NVIDIA(0): Default visual is TrueColor
[ 4789.474] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 4789.474] (**) NVIDIA(0): Enabling 2D acceleration
[ 4789.841] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 4789.842] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[ 4789.842] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 4789.842] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
[ 4789.842] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 4789.875] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[ 4789.875] (--) NVIDIA(0): CRT-0
[ 4789.875] (--) NVIDIA(0): CRT-1
[ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
[ 4789.875] (--) NVIDIA(0): DFP-1
[ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
[ 4789.875] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
[ 4789.875] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 4789.875] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 4789.875] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
[ 4789.875] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
[ 4789.875] (**) NVIDIA(0): Option "Rotate" "left"
[ 4789.875] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4789.875] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4789.875] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4789.875] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4789.875] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4789.875] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4789.875] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4789.875] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4789.876] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4789.876] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4789.876] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4789.876] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4789.876] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4789.876] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4789.877] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4789.877] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4789.877] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4789.878] (==) NVIDIA(0):
[ 4789.878] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 4789.878] (==) NVIDIA(0): will be used as the requested mode.
[ 4789.878] (==) NVIDIA(0):
[ 4789.878] (II) NVIDIA(0): Validated MetaModes:
[ 4789.878] (II) NVIDIA(0):
[ 4789.878] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
[ 4789.878] (II) NVIDIA(0): Virtual screen size determined to be 3460 x 1440
[ 4789.905] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 4789.905] (--) NVIDIA(0): option
[ 4789.906] (--) intel(1): Integrated Graphics Chipset: Intel(R) HD Graphics 2000
[ 4789.906] (--) intel(1): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
[ 4789.906] (II) intel(1): Creating default Display subsection in Screen section
"BNQ-Screen" for depth/fbbpp 24/32
[ 4789.906] (==) intel(1): Depth 24, (--) framebuffer bpp 32
[ 4789.906] (==) intel(1): RGB weight 888
[ 4789.906] (==) intel(1): Default visual is TrueColor
[ 4789.906] (**) intel(1): Option "AccelMethod" "none"
[ 4789.906] (II) intel(1): Output VGA1 using monitor section BNQ
[ 4789.906] (**) intel(1): Option "LeftOf" "SAM"
[ 4789.906] (**) intel(1): Option "Rotate" "left"
[ 4789.906] (II) intel(1): Enabled output VGA1
[ 4789.906] (II) intel(1): Output HDMI1 has no monitor section
[ 4789.906] (II) intel(1): Enabled output HDMI1
[ 4789.906] (II) intel(1): Output DP1 has no monitor section
[ 4789.906] (II) intel(1): Enabled output DP1
[ 4789.906] (II) intel(1): Output HDMI2 has no monitor section
[ 4789.906] (II) intel(1): Enabled output HDMI2
[ 4789.906] (II) intel(1): Output HDMI3 has no monitor section
[ 4789.906] (II) intel(1): Enabled output HDMI3
[ 4789.906] (II) intel(1): Output DP2 has no monitor section
[ 4789.906] (II) intel(1): Enabled output DP2
[ 4789.906] (II) intel(1): Output DP3 has no monitor section
[ 4789.906] (II) intel(1): Enabled output DP3
[ 4789.906] (--) intel(1): Using a maximum size of 256x256 for hardware cursors
[ 4789.906] (II) intel(1): Output VIRTUAL1 has no monitor section
[ 4789.906] (II) intel(1): Enabled output VIRTUAL1
[ 4789.906] (II) intel(1): EDID for output DP1
[ 4789.906] (II) intel(1): EDID for output DP2
[ 4789.906] (II) intel(1): EDID for output DP3
[ 4789.906] (II) intel(1): EDID for output HDMI1
[ 4789.906] (II) intel(1): EDID for output HDMI2
[ 4789.907] (II) intel(1): EDID for output HDMI3
[ 4789.920] (II) intel(1): EDID for output VGA1
[ 4789.920] (II) intel(1): Manufacturer: BNQ Model: 7659 Serial#: 28
[ 4789.920] (II) intel(1): Year: 2003 Week: 39
[ 4789.920] (II) intel(1): EDID Version: 1.3
[ 4789.920] (II) intel(1): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 4789.920] (II) intel(1): Sync: Separate Composite
[ 4789.920] (II) intel(1): Max Image Size [cm]: horiz.: 34 vert.: 27
[ 4789.920] (II) intel(1): Gamma: 2.20
[ 4789.920] (II) intel(1): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 4789.920] (II) intel(1): First detailed timing is preferred mode
[ 4789.920] (II) intel(1): redX: 0.640 redY: 0.340 greenX: 0.290 greenY: 0.611
[ 4789.920] (II) intel(1): blueX: 0.140 blueY: 0.069 whiteX: 0.310 whiteY: 0.330
[ 4789.920] (II) intel(1): Supported established timings:
[ 4789.920] (II) intel(1): 720x400@70Hz
[ 4789.920] (II) intel(1): 640x480@60Hz
[ 4789.920] (II) intel(1): 640x480@67Hz
[ 4789.920] (II) intel(1): 640x480@72Hz
[ 4789.920] (II) intel(1): 640x480@75Hz
[ 4789.920] (II) intel(1): 800x600@56Hz
[ 4789.920] (II) intel(1): 800x600@60Hz
[ 4789.920] (II) intel(1): 800x600@72Hz
[ 4789.920] (II) intel(1): 800x600@75Hz
[ 4789.920] (II) intel(1): 832x624@75Hz
[ 4789.920] (II) intel(1): 1024x768@60Hz
[ 4789.920] (II) intel(1): 1024x768@70Hz
[ 4789.920] (II) intel(1): 1024x768@75Hz
[ 4789.920] (II) intel(1): 1280x1024@75Hz
[ 4789.920] (II) intel(1): 1152x864@75Hz
[ 4789.920] (II) intel(1): Manufacturer's mask: 0
[ 4789.920] (II) intel(1): Supported standard timings:
[ 4789.920] (II) intel(1): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 4789.920] (II) intel(1): #1: hsize: 1280 vsize 1024 refresh: 76 vid: 36993
[ 4789.920] (II) intel(1): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 4789.920] (II) intel(1): #3: hsize: 1280 vsize 1024 refresh: 72 vid: 35969
[ 4789.920] (II) intel(1): Supported detailed timing:
[ 4789.920] (II) intel(1): clock: 108.0 MHz Image Size: 338 x 270 mm
[ 4789.920] (II) intel(1): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 4789.920] (II) intel(1): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 4789.920] (II) intel(1): Supported detailed timing:
[ 4789.920] (II) intel(1): clock: 25.2 MHz Image Size: 304 x 228 mm
[ 4789.920] (II) intel(1): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 0
[ 4789.920] (II) intel(1): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 0
[ 4789.920] (II) intel(1): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 145 MHz
[ 4789.920] (II) intel(1): Monitor name: BenQ FP737s
[ 4789.920] (II) intel(1): EDID (in hex):
[ 4789.920] (II) intel(1): 00ffffffffffff0009d159761c000000
[ 4789.920] (II) intel(1): 270d01036c221b78eac6f6a3574a9c23
[ 4789.920] (II) intel(1): 114f54bfef80714f81908180818c0101
[ 4789.920] (II) intel(1): 010101010101302a009851002a403070
[ 4789.920] (II) intel(1): 1300520e1100001ed50980a0205e6310
[ 4789.920] (II) intel(1): 1060520830e41000001a000000fd0038
[ 4789.920] (II) intel(1): 4b1f510e000a202020202020000000fc
[ 4789.920] (II) intel(1): 0042656e51204650373337730a200072
[ 4789.920] (II) intel(1): Printing probed modes for output VGA1
[ 4789.920] (II) intel(1): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 4789.920] (II) intel(1): Modeline "1280x1024"x76.0 141.81 1280 1376 1512 1744 1024 1025 1028 1070 -hsync +vsync (81.3 kHz)
[ 4789.920] (II) intel(1): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 4789.920] (II) intel(1): Modeline "1280x1024"x72.0 132.84 1280 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.9 kHz)
[ 4789.920] (II) intel(1): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 4789.920] (II) intel(1): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 4789.920] (II) intel(1): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 4789.920] (II) intel(1): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 4789.920] (II) intel(1): Modeline "640x350"x70.1 25.17 640 656 752 800 350 387 389 449 +hsync -vsync (31.5 kHz e)
[ 4789.920] (II) intel(1): EDID for output VIRTUAL1
[ 4789.920] (II) intel(1): Output DP1 disconnected
[ 4789.920] (II) intel(1): Output DP2 disconnected
[ 4789.920] (II) intel(1): Output DP3 disconnected
[ 4789.920] (II) intel(1): Output HDMI1 disconnected
[ 4789.920] (II) intel(1): Output HDMI2 disconnected
[ 4789.920] (II) intel(1): Output HDMI3 disconnected
[ 4789.920] (II) intel(1): Output VGA1 connected
[ 4789.920] (II) intel(1): Output VIRTUAL1 disconnected
[ 4789.920] (II) intel(1): Using user preference for initial modes
[ 4789.920] (II) intel(1): Output VGA1 using initial mode 1280x1024
[ 4789.920] (EE) intel(1): Cannot position output VGA1 relative to unknown output SAM
[ 4789.920] (II) intel(1): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 4789.920] (==) intel(1): TearFree disabled
[ 4789.920] (==) intel(1): DPI set to (96, 96)
[ 4789.920] (II) Loading sub module "dri2"
[ 4789.920] (II) LoadModule: "dri2"
[ 4789.920] (II) Module "dri2" already built-in
[ 4789.920] (II) Loading sub module "present"
[ 4789.920] (II) LoadModule: "present"
[ 4789.920] (II) Module "present" already built-in
[ 4792.053] (EE) intel(G0): [drm] failed to set drm interface version: Permission denied [13].
[ 4792.053] (II) intel(G0): [drm] Contents of '/sys/kernel/debug/dri/0/clients':
[ 4792.053] (II) intel(G0): [drm] command pid dev master a uid magic
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 y y 0 0
[ 4792.053] (II) intel(G0): [drm] Xorg 10086 0 n y 0 0
[ 4792.053] (EE) intel(G0): Failed to claim DRM device.
[ 4792.053] (II) UnloadModule: "intel"
[ 4792.053] (--) Depth 24 pixmap format is 32 bpp
[ 4792.053] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 4792.053] (II) NVIDIA: access.
[ 4792.057] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 4792.057] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 4792.057] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 4792.057] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 4792.057] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 4792.057] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 4792.057] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 4792.057] (II) NVIDIA(0): Config Options in the README.
[ 4792.091] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-2:nvidia-auto-select{Rotation=90}"
[ 4792.264] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 4792.264] (==) NVIDIA(0): Backing store enabled
[ 4792.264] (==) NVIDIA(0): Silken mouse enabled
[ 4792.264] (**) NVIDIA(0): DPMS enabled
[ 4792.264] (II) Loading sub module "dri2"
[ 4792.264] (II) LoadModule: "dri2"
[ 4792.264] (II) Module "dri2" already built-in
[ 4792.264] (II) NVIDIA(0): [DRI2] Setup complete
[ 4792.264] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 4792.264] (--) RandR disabled
[ 4792.264] (II) intel(1): SNA initialized with disabled backend
[ 4792.264] (==) intel(1): Backing store enabled
[ 4792.264] (==) intel(1): Silken mouse enabled
[ 4792.264] (II) intel(1): HW Cursor enabled
[ 4792.264] (II) intel(1): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 4792.264] (**) intel(1): DPMS enabled
[ 4792.264] (==) intel(1): display hotplug detection enabled
[ 4792.264] (II) intel(1): Textured video not supported on this hardware
[ 4792.264] (WW) intel(1): loading DRI2 whilst the GPU is wedged.
[ 4792.264] (II) intel(1): [DRI2] Setup complete
[ 4792.264] (II) intel(1): [DRI2] DRI driver: i965
[ 4792.264] (II) intel(1): [DRI2] VDPAU driver: i965
[ 4792.264] (II) intel(1): direct rendering: DRI2 enabled
[ 4792.265] (II) intel(1): hardware support for Present enabled
[ 4792.265] (WW) intel(1): Option "Monitor-VGA-0" is not used
[ 4792.265] (WW) intel(1): Option "LeftOf" is not used
[ 4792.265] (WW) intel(1): Option "Rotate" is not used
[ 4792.265] (--) RandR disabled
[ 4792.268] (II) Initializing extension GLX
[ 4792.268] (II) Indirect GLX disabled.(II) intel(1): switch to mode [email protected] on VGA1 using pipe 0, position (0, 0), rotation left, reflection none
[ 4792.332] (II) intel(1): Setting screen physical size to 270 x 338
[ 4792.386] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 4792.386] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4792.386] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 4792.386] (**) Power Button: Applying InputClass "system-keyboard"
[ 4792.386] (II) LoadModule: "libinput"
[ 4792.386] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 4792.387] (II) Module libinput: vendor="X.Org Foundation"
[ 4792.387] compiled for 1.17.1, module version = 0.7.0
[ 4792.387] Module class: X.Org XInput Driver
[ 4792.387] ABI class: X.Org XInput driver, version 21.0
[ 4792.387] (II) Using input driver 'libinput' for 'Power Button'
[ 4792.387] (**) Power Button: always reports core events
[ 4792.387] (**) Option "Device" "/dev/input/event2"
[ 4792.387] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 4792.387] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[ 4792.399] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 4792.399] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 4792.399] (**) Option "xkb_model" "pc104"
[ 4792.399] (**) Option "xkb_layout" "us,ru"
[ 4792.399] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.432] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 4792.432] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[ 4792.432] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 4792.432] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4792.432] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 4792.432] (**) Power Button: Applying InputClass "system-keyboard"
[ 4792.432] (II) Using input driver 'libinput' for 'Power Button'
[ 4792.432] (**) Power Button: always reports core events
[ 4792.432] (**) Option "Device" "/dev/input/event1"
[ 4792.433] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[ 4792.433] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[ 4792.489] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[ 4792.489] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 4792.489] (**) Option "xkb_model" "pc104"
[ 4792.489] (**) Option "xkb_layout" "us,ru"
[ 4792.489] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.490] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[ 4792.490] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event0)
[ 4792.490] (II) No input driver specified, ignoring this device.
[ 4792.490] (II) This device may have been added with another device file.
[ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[ 4792.490] (II) No input driver specified, ignoring this device.
[ 4792.490] (II) This device may have been added with another device file.
[ 4792.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
[ 4792.490] (II) No input driver specified, ignoring this device.
[ 4792.490] (II) This device may have been added with another device file.
[ 4792.491] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event19)
[ 4792.491] (II) No input driver specified, ignoring this device.
[ 4792.491] (II) This device may have been added with another device file.
[ 4792.491] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event3)
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
[ 4792.491] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
[ 4792.491] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
[ 4792.491] (**) Option "Device" "/dev/input/event3"
[ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
[ 4792.491] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
[ 4792.554] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:045E:07B2.0004/input/input24/event3"
[ 4792.554] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 8)
[ 4792.554] (**) Option "xkb_model" "pc104"
[ 4792.554] (**) Option "xkb_layout" "us,ru"
[ 4792.554] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is tagged by udev as: Keyboard
[ 4792.554] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event3 is a keyboard
[ 4792.555] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event4)
[ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev pointer catchall"
[ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput pointer catchall"
[ 4792.555] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
[ 4792.555] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
[ 4792.555] (**) Option "Device" "/dev/input/event4"
[ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
[ 4792.555] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
[ 4792.609] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:045E:07B2.0005/input/input25/event4"
[ 4792.610] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: MOUSE, id 9)
[ 4792.610] (**) Option "AccelerationScheme" "none"
[ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) selected scheme none/0
[ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration factor: 2.000
[ 4792.610] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration threshold: 4
[ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is tagged by udev as: Mouse
[ 4792.610] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event4 is a pointer caps
[ 4792.610] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/mouse0)
[ 4792.610] (II) No input driver specified, ignoring this device.
[ 4792.610] (II) This device may have been added with another device file.
[ 4792.611] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event5)
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "joystick catchall"
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "libinput keyboard catchall"
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
[ 4792.611] (II) Using input driver 'libinput' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'
[ 4792.611] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events
[ 4792.611] (**) Option "Device" "/dev/input/event5"
[ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
[ 4792.611] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
[ 4792.676] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:045E:07B2.0006/input/input26/event5"
[ 4792.676] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 10)
[ 4792.676] (**) Option "xkb_model" "pc104"
[ 4792.676] (**) Option "xkb_layout" "us,ru"
[ 4792.676] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is tagged by udev as: Keyboard Joystick
[ 4792.676] (II) input device 'Microsoft Microsoft® 2.4GHz Transceiver v8.0', /dev/input/event5 is a keyboard
[ 4792.677] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/js0)
[ 4792.677] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.677] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
[ 4792.677] (II) No input driver specified, ignoring this device.
[ 4792.677] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event12)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.678] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
[ 4792.678] (II) No input driver specified, ignoring this device.
[ 4792.678] (II) This device may have been added with another device file.
[ 4792.679] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
[ 4792.679] (II) No input driver specified, ignoring this device.
[ 4792.679] (II) This device may have been added with another device file.
[ 4792.679] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event6)
[ 4792.679] (II) No input driver specified, ignoring this device.
[ 4792.679] (II) This device may have been added with another device file.
[ 4792.679] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event16)
[ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[ 4792.679] (**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
[ 4792.679] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[ 4792.679] (**) Eee PC WMI hotkeys: always reports core events
[ 4792.679] (**) Option "Device" "/dev/input/event16"
[ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
[ 4792.679] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
[ 4792.712] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input19/event16"
[ 4792.712] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 11)
[ 4792.712] (**) Option "xkb_model" "pc104"
[ 4792.713] (**) Option "xkb_layout" "us,ru"
[ 4792.713] (**) Option "xkb_options" "caps:swapescape,grp:toggle"
[ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is tagged by udev as: Keyboard
[ 4792.713] (II) input device 'Eee PC WMI hotkeys', /dev/input/event16 is a keyboard
[ 4793.050] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.050] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4793.050] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.081] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.081] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4793.081] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.081] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.081] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4793.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.081] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4793.081] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.081] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.081] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4793.129] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.129] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4793.129] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.160] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.160] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4793.160] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.160] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.160] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4793.160] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.160] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4793.160] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.160] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.160] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4793.229] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.229] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4793.229] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.259] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4793.259] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4793.259] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.259] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.259] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4793.259] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4793.259] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4793.259] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4793.259] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4793.259] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4849.763] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4849.763] (**) NVIDIA(0): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4849.763] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4849.794] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4849.794] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4849.794] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4849.794] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4849.794] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4849.794] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4849.794] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4849.794] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4849.795] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4849.795] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4849.795] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4849.795] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4849.795] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4849.795] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
I also tried other configs, but neither of them made me happy:
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "SAM"
ModelName "Samsung SMS27A850"
HorizSync 30.0 - 90.0
VertRefresh 56.0 - 75.0
Option "DPMS"
DisplaySize 597 336 # In millimeters
EndSection
Section "Monitor"
Identifier "VS"
ModelName "ViewSonic VG1930wm"
Option "DPMS"
Option "RightOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Monitor"
Identifier "BNQ"
ModelName "BenQ FP737s"
Option "DPMS"
Option "LeftOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Device"
Identifier "nvidia-sam"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-1" "SAM"
Screen 0
EndSection
Section "Device"
Identifier "nvidia-vs"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-2" "VS"
Screen 1
EndSection
Section "Device"
Identifier "intel"
Driver "modesetting"
Option "AccelMethod" "none"
VendorName "Intel"
BoardName "Intel Integrated Graphic Controller"
BusID "00:02:0"
Option "Monitor-VGA-0" "BNQ"
Screen 2
EndSection
Section "Screen"
Identifier "SAM-Screen"
Device "nvidia-sam"
Monitor "SAM"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "VS-Screen"
Device "nvidia-vs"
Monitor "VS"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "BNQ-Screen"
Device "intel"
Monitor "BNQ"
EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "SAM-Screen"
Screen 1 "VS-Screen" RightOf "SAM-Screen"
Screen 2 "BNQ-Screen" LeftOf "SAM-Screen"
Option "Xinerama" "0"
EndSection
[ 4488.527]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 4488.527] X Protocol Version 11, Revision 0
[ 4488.527] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 4488.527] Current Operating System: Linux earth 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
[ 4488.527] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=dc49b07c-e67c-4b6f-91f7-7c1adc050e21 rw quiet ipv6.disable=1 init=/usr/lib/systemd/systemd security=tomoyo TOMOYO_trigger=/usr/lib/systemd/systemd
[ 4488.527] Build Date: 22 February 2015 12:50:32PM
[ 4488.527]
[ 4488.527] Current version of pixman: 0.32.6
[ 4488.527] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4488.527] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4488.527] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 1 14:38:54 2015
[ 4488.527] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4488.527] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4488.528] (==) ServerLayout "Layout0"
[ 4488.528] (**) |-->Screen "SAM-Screen" (0)
[ 4488.528] (**) | |-->Monitor "SAM"
[ 4488.528] (**) | |-->Device "nvidia-sam"
[ 4488.528] (**) |-->Screen "VS-Screen" (1)
[ 4488.528] (**) | |-->Monitor "VS"
[ 4488.528] (**) | |-->Device "nvidia-vs"
[ 4488.528] (**) |-->Screen "BNQ-Screen" (2)
[ 4488.528] (**) | |-->Monitor "BNQ"
[ 4488.528] (**) | |-->Device "intel"
[ 4488.528] (**) Option "Xinerama" "0"
[ 4488.528] (==) Automatically adding devices
[ 4488.528] (==) Automatically enabling devices
[ 4488.528] (==) Automatically adding GPU devices
[ 4488.528] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 4488.528] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4488.528] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4488.528] (II) Loader magic: 0x815d80
[ 4488.528] (II) Module ABI versions:
[ 4488.528] X.Org ANSI C Emulation: 0.4
[ 4488.528] X.Org Video Driver: 19.0
[ 4488.528] X.Org XInput driver : 21.0
[ 4488.528] X.Org Server Extension : 9.0
[ 4488.529] (EE) systemd-logind: failed to get session: PID 32224 does not belong to any known session
[ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 4488.530] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4488.531] (--) PCI: (0:0:2:0) 8086:0102:1043:84ca rev 9, Mem @ 0xf6400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 4488.531] (--) PCI:*(0:1:0:0) 10de:1200:10b0:0401 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 4488.531] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4488.531] (II) LoadModule: "glx"
[ 4488.531] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4488.542] (II) Module glx: vendor="NVIDIA Corporation"
[ 4488.542] compiled for 4.0.2, module version = 1.0.0
[ 4488.542] Module class: X.Org Server Extension
[ 4488.542] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 4488.542] (II) LoadModule: "nvidia"
[ 4488.542] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 4488.543] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 4488.543] compiled for 4.0.2, module version = 1.0.0
[ 4488.543] Module class: X.Org Video Driver
[ 4488.543] (II) LoadModule: "modesetting"
[ 4488.543] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 4488.543] (II) Module modesetting: vendor="X.Org Foundation"
[ 4488.543] compiled for 1.17.1, module version = 1.17.1
[ 4488.543] Module class: X.Org Video Driver
[ 4488.543] ABI class: X.Org Video Driver, version 19.0
[ 4488.543] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 4488.543] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 4488.543] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 4488.543] (++) using VT number 7
[ 4488.645] (II) Loading sub module "fb"
[ 4488.645] (II) LoadModule: "fb"
[ 4488.645] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 4488.645] (II) Module fb: vendor="X.Org Foundation"
[ 4488.646] compiled for 1.17.1, module version = 1.0.0
[ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4488.646] (II) Loading sub module "wfb"
[ 4488.646] (II) LoadModule: "wfb"
[ 4488.646] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 4488.646] (II) Module wfb: vendor="X.Org Foundation"
[ 4488.646] compiled for 1.17.1, module version = 1.0.0
[ 4488.646] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4488.646] (II) Loading sub module "ramdac"
[ 4488.646] (II) LoadModule: "ramdac"
[ 4488.646] (II) Module "ramdac" already built-in
[ 4488.647] (II) modeset(2): using drv /dev/dri/card0
[ 4488.647] (II) modeset(G0): using drv /dev/dri/card0
[ 4488.647] (EE) Screen 2 deleted because of no matching config section.
[ 4488.647] (II) UnloadModule: "modesetting"
[ 4488.647] (II) NVIDIA(0): Creating default Display subsection in Screen section
"SAM-Screen" for depth/fbbpp 24/32
[ 4488.647] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 4488.647] (==) NVIDIA(0): RGB weight 888
[ 4488.647] (==) NVIDIA(0): Default visual is TrueColor
[ 4488.647] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 4488.648] (II) NVIDIA(1): Creating default Display subsection in Screen section
"VS-Screen" for depth/fbbpp 24/32
[ 4488.648] (**) NVIDIA(0): Enabling 2D acceleration
[ 4489.049] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 4489.050] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[ 4489.050] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 4489.050] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
[ 4489.050] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 4489.082] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[ 4489.082] (--) NVIDIA(0): CRT-0
[ 4489.082] (--) NVIDIA(0): CRT-1
[ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0) (boot, connected)
[ 4489.082] (--) NVIDIA(0): DFP-1
[ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2) (connected)
[ 4489.082] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(0): Samsung SMS27A850 (DFP-0): Internal TMDS
[ 4489.082] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 4489.082] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 4489.082] (--) NVIDIA(0): ViewSonic VG1930wm (DFP-2): Internal TMDS
[ 4489.082] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
[ 4489.083] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4489.083] (**) NVIDIA(0): device Samsung SMS27A850 (DFP-0) (Using EDID frequencies
[ 4489.083] (**) NVIDIA(0): has been enabled on all display devices.)
[ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4489.083] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4489.083] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 4489.083] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850 (DFP-0) contradicts itself:
[ 4489.083] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 4489.083] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 4489.083] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 4489.083] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 4489.084] (==) NVIDIA(0):
[ 4489.084] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 4489.084] (==) NVIDIA(0): will be used as the requested mode.
[ 4489.084] (==) NVIDIA(0):
[ 4489.084] (II) NVIDIA(0): Validated MetaModes:
[ 4489.084] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
[ 4489.084] (II) NVIDIA(0): Virtual screen size determined to be 2560 x 1440
[ 4489.113] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 4489.113] (--) NVIDIA(0): option
[ 4489.114] (==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
[ 4489.114] (==) NVIDIA(1): RGB weight 888
[ 4489.114] (==) NVIDIA(1): Default visual is TrueColor
[ 4489.114] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[ 4489.114] (II) NVIDIA(1): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[ 4489.114] (--) NVIDIA(1): Memory: 1048576 kBytes
[ 4489.114] (--) NVIDIA(1): VideoBIOS: 70.24.21.00.00
[ 4489.114] (II) NVIDIA(1): Detected PCI Express Link width: 16X
[ 4489.146] (--) NVIDIA(1): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[ 4489.146] (--) NVIDIA(1): CRT-0
[ 4489.146] (--) NVIDIA(1): CRT-1
[ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0) (boot, connected)
[ 4489.146] (--) NVIDIA(1): DFP-1
[ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2) (connected)
[ 4489.146] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(1): Samsung SMS27A850 (DFP-0): Internal TMDS
[ 4489.146] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-0): 330.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(1): DFP-1: Internal TMDS
[ 4489.146] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 4489.146] (--) NVIDIA(1): ViewSonic VG1930wm (DFP-2): Internal TMDS
[ 4489.146] (--) NVIDIA(GPU-0): ViewSonic VG1930wm (DFP-2): 330.0 MHz maximum pixel clock
[ 4489.146] (**) NVIDIA(1): Option "Rotate" "left"
[ 4489.146] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
[ 4489.146] (**) NVIDIA(1): device ViewSonic VG1930wm (DFP-2) (Using EDID frequencies
[ 4489.146] (**) NVIDIA(1): has been enabled on all display devices.)
[ 4489.147] (==) NVIDIA(1):
[ 4489.147] (==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
[ 4489.147] (==) NVIDIA(1): will be used as the requested mode.
[ 4489.147] (==) NVIDIA(1):
[ 4489.147] (II) NVIDIA(1): Validated MetaModes:
[ 4489.147] (II) NVIDIA(1): "DFP-2:nvidia-auto-select{Rotation=90}"
[ 4489.147] (II) NVIDIA(1): Virtual screen size determined to be 900 x 1440
[ 4489.150] (--) NVIDIA(1): DPI set to (55, 140); computed from "UseEdidDpi" X config
[ 4489.150] (--) NVIDIA(1): option
[ 4489.150] (EE)
[ 4489.150] (EE) Backtrace:
[ 4489.151] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
[ 4489.151] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f64dd88653f]
[ 4489.151] (EE) 2: /usr/lib/xorg-server/Xorg (xf86nameCompare+0x19) [0x4a9159]
[ 4489.151] (EE) 3: /usr/lib/xorg-server/Xorg (xf86findOption+0x2c) [0x4a2c6c]
[ 4489.151] (EE) 4: /usr/lib/xorg-server/Xorg (xf86SetDepthBpp+0x430) [0x4828d0]
[ 4489.151] (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x25e1) [0x7f64d695aab1]
[ 4489.151] (EE) 6: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
[ 4489.151] (EE) 7: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
[ 4489.152] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f64dd873800]
[ 4489.152] (EE) 9: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
[ 4489.152] (EE) 10: ? (?+0x29) [0x29]
[ 4489.152] (EE)
[ 4489.152] (EE) Segmentation fault at address 0x231
[ 4489.152] (EE)
Fatal server error:
[ 4489.152] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 4489.152] (EE)
[ 4489.152] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 4489.152] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 4489.152] (EE)
[ 4489.295] (EE) Server terminated with error (1). Closing log file.
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "SAM"
ModelName "Samsung SMS27A850"
HorizSync 30.0 - 90.0
VertRefresh 56.0 - 75.0
Option "DPMS"
DisplaySize 597 336 # In millimeters
EndSection
Section "Monitor"
Identifier "VS"
ModelName "ViewSonic VG1930wm"
Option "DPMS"
Option "RightOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Monitor"
Identifier "BNQ"
ModelName "BenQ FP737s"
Option "DPMS"
Option "LeftOf" "SAM"
Option "Rotate" "left"
EndSection
Section "Device"
Identifier "nvidia-sam"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-1" "SAM"
Screen 0
EndSection
Section "Device"
Identifier "nvidia-vs"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560 Ti"
BusID "01:00:0"
Option "Monitor-DVI-I-2" "VS"
Screen 1
EndSection
Section "Device"
Identifier "intel"
Driver "intel"
Option "AccelMethod" "none"
VendorName "Intel"
BoardName "Intel Integrated Graphic Controller"
BusID "00:02:0"
Option "Monitor-VGA-0" "BNQ"
Screen 2
EndSection
Section "Screen"
Identifier "SAM-Screen"
Device "nvidia-sam"
Monitor "SAM"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "VS-Screen"
Device "nvidia-vs"
Monitor "VS"
#DefaultDepth 24
# Option "Stereo" "0"
# Option "SLI" "Off"
# Option "MultiGPU" "Off"
# Option "BaseMosaic" "off"
#Option "AllowEmptyInitialConfiguration"
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "BNQ-Screen"
Device "intel"
Monitor "BNQ"
EndSection
SectionHi:
There is a specific order you need to install the graphics drivers for the notebooks with the nvidia/intel graphics.
1. Install the Intel chipset installation utility and reboot. If the one on your notebook's support page doesn't work, use this one.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775&lang=eng&ProdId=816
2. Install the Intel HD graphics driver and reboot. If the one on your notebook's suport page doesn't work, try this one.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24348
3. Install the nVidia HD graphics driver and reboot. If the one on your notebook's support page doesn't work, try this one.
http://www.nvidia.com/download/driverResults.aspx/81879/en-us -
can I run adobe master collection in a windows partition on a basic mbp 13" with only the intel chipset?
I want to install 16 gb ram but I don't think I can change the lack of video card. I wanted this basic machine because it has fairly long battery life. I don't need or want retina at this time. My model is the mid 2012 model. I am running the adobe collection for mac, I want to run the windows versions. Is it possible? What is the most ram I could access using something like fusion 5, assuming I could get fusion 5 to work? would it refuse to run because of the intel chipset and lack of video card?
If I'm wrong and there is a way to add a video card to this model, could some version of fusion and windows 7 access more than 2 gb operating ram?
What cost would I be incurring, and would it be cheaper to buy a windows laptop with more ram than I could access via a virtual machine?
I want to work on a client's work in the windows versions of the creative suite, with occasional usage of after effects for windows, and to use some web plug-ins only available in windows versions, and to try some windows-only video and audio software.
thanks for any suggestions. While many people have told me I can run everything on my macbook, I am concerned about what I think is a limited amount of ram that can be accessed over the virtual machine partition softwares, and I don't know if what I want to attempt is actually possible.
My mbp os is 10.8.2 on a 2.5 GHz intel core i5 4 gb 1600MHz DDR3 with 500 hard drive. the basic 13" mid 2012 machine.
I'm hoping to install 16 G of opertating ram to allow more adobe programs to run concurrently- just when I am working on the mac side.
also, off track but, for years I have wanted a small machine that is more easily portable than my 15" machines. I have only had this used machine for a few weeks, but already I have been very satisfied and used it for presentations at clients. I don't want an air because I really want the dvd burner and player. No matter what apple says about wireless, there are decades of legacy work stored on optical discs all over the world, and I don't want to be unable to open something at a client's office because I don't have a dvd drive. Additionally, I have very large files I want to transfer via ethernet or firewire so that the transfer will take less time and be more secure than wifi. I resist apple's trend to make every machine a disposable toy that is viable only a year or so. I have read reviews that label the mbp it a poor value compared to the air. If all you need to do is text and communicate via wifi, many devices will sufice, and an air is certainly the most elegant. But what about the cost of large ssd's and protecting the drive against damage from shock? I want to be able to move this thing around and the small size is much safer inside my padded bag when I sit in narrow airplane seats, crowded trains and other congested spaces. I am much more likely to be able to borrow a large screen in a client's office ( with the use of one of the three adapters I had to buy) than to be able to borrow a dvd drive that has drivers for mac os 10.8.2. I suspect this may be the last generation of machines that have optical drives and ethernet, and that was why I purchased it so that I could continue to do work into the next few years. I am impressed by the retina display, but I need long battery life. And as beautiful as the retina display is, it is even more of a problem when trying to cross platform with the windows world. I wish I could infuence apple to do a trial product flow for a machine designed to work with 80% of the business world that uses windows. How spectacular that would be. With all their expertise and adept hardware design, to create a machine that cross platforms better than a windows machine itself works? Now that would be an accomplishment. Instead of 8 or 9 percent of the total computer sales, why not aim for a higher percentage? Smart devices will keep moving toward portable computers in power, anyway.confused, bothered and bewildered wrote:
can I run adobe master collection in a windows partition on a basic mbp 13" with only the intel chipset?
I want to install 16 gb ram but I don't think I can change the lack of video card. I wanted this basic machine because it has fairly long battery life. I don't need or want retina at this time. My model is the mid 2012 model. I am running the adobe collection for mac, I want to run the windows versions. Is it possible? What is the most ram I could access using something like fusion 5, assuming I could get fusion 5 to work? would it refuse to run because of the intel chipset and lack of video card?
If I'm wrong and there is a way to add a video card to this model, could some version of fusion and windows 7 access more than 2 gb operating ram?
What cost would I be incurring, and would it be cheaper to buy a windows laptop with more ram than I could access via a virtual machine?...
Fusion should work on your machine and if you put 16 GB of RAM in (see http://eshop.macsales.com/shop/memory/Apple_MacBook_MacBook_Pro/Upgrade/DDR3_160 0MHz_SDRAM), Fusion can access a good portion of that. Also, in a Virtual Machine, the guest OS is presented with Fusion's video card emulation, not what's in hardware on your Mac. Of course, finding Windows 7 now that Win 8 has been released could take some doing and the Win 8 Pro upgrade price is supposed to jump to $200 the end of the month. Add that to the price of Fusion and the extra RAM and you're beginning to get into the realm of low end real PC's.
As to cross platform, I assume you're aware of BootCamp (http://support.apple.com/kb/HT1461). -
How do I get more memory for my Macbook Pro Spring 2010 13-inch with 2.66GHz Intel Core 2 Duo?
How do I get more memory for my Macbook Pro spring 2010 13-inch with 2.66GHz Intel Core 2 Duo. Apple says no memory currently available for that model. I have 4 GB memory and 3.99 used. Help!
macette1976 wrote:
Now I'm confused. This is the one Crucial told me to get:
CT3309356 - 4GB DDR3 PC3-8500 Unbuffered NON-ECC 1.35V 512Meg x 64
$45.99
Also what do you mean that actual memory is 16GB but with Apple it's 8?
When I go to the "About this Mac" it says Memory 4G 1067 MHz DDR3, then when I go to System Report it says
Memory Slot
Bank 0/ DIMM0 2G DDR3 1067 MHZ OK
Bank 1/ DIMM0 2G DDR3 1067 MHZ OK
Sorry I'm clueless. Just don't want to buy something that messes up my machine more than it already is.
The Crucial site appears to have recommended the correct spec 4gB RAM stick for your model. Please note that you will need to remove the existing sticks of RAM to install new, so you will need 2x4gB to get to 8gB.
When your model of computer was designed/built, it was tested with readily available 2x4gB (8gB). After release RAM retailers have tested it with higher amounts, and Apple didn't update their quoted specs. -
Can I set up new events with leaps?
I've tried to set up some Maya calendars on iCal without success. My idea has been creating a group of calendars made up by "full day" events, in which every event represents a day, and every calendar, a count. The point is that in those calendars there are always leaps that are repeated every while, and as far as I've done, after a leap happens, I must re-start to create the same events. Am I clear?
Let's make an example. Imaging a calendar made up by four days (too short, but its for the example). I have created an iCal calendar with four events, and each one is set up to be repeated every four days; till this point it works as desired. But there's a leap of one day that happens every year, and I haven't been able to set it up; after erasing the event of that day, I must re-start to set up the future (four, for this example) events... Can't I set events with leaps on iCal?
I've also thought about another possible way to set a calendar like that. I found a table for finding out the correspondence between Gregorian calendar and a 260 days Maya Calendar, by making an adding. There's a number for each month of the year, and also every year has a number. You have to add the number of the month plus the number of the year plus the number of the day of the month, and only if it is higher than 260, you will need to subtract 260; thus you will know which of those 260 days is today (or another date).
So, if I can set an iCal calendar using something like "if today is 2nd =2, of June =151, 2011 = 7; add 2+151+7; and if answer is higher than 260 subtract 260; so day number is 160". I could also set some other calendars from that one, like "if answer is 109 or 110 or 111 or 112, then "codon" number is X. Any suggestion for creating an iCal calendar like that from other way, like Developer Apps? Or if not for creating an iCal Calendar, maybe for making a Widget?
Thanks for your attention.Am I not clear? I guess I got excited trying to be clear explaining details... But got dark!
And if I just say, Can I create an iCal Calendar event, set up to be repeated every monday, but after a specific date, be repeated weekly every tuesday? If not on iCal, another advice?
Thanks in advance! -
Tearing on VGA output, LVDS OK on 950GMA with xf86-video-intel-2.6.10
I'm crossposting this message i sent on intel-graphics ml and xorg bugzilla, because maybe some of you can point me to a solution.
i own an asus eeepc1005ha, it uses intel gma 950.
Playing a video on the internal LVDS panel is very pleasing and tear
free, but as soon as i connect the vga output, i can notice tearing or
flickering on the picture.
I tried all possible configurations:
-Booting with the lid open (tty on LVDS) and then switching to xorg
with a VGA only output. (VGA tears)
-Booting with the lid closed (tty on VGA) and using xorg on VGA. (VGA tears)
-VGA+LVDS in clone mode (VGA and LVDS tears)
-VGA+LVDS in multihead mode (expanded desktop) (VGA and LVDS tears)
Using xv adaptor via mplayer results in a different tear effect, seems
more like a flickering, while the GL output definitely tears.
I couldn't try overlay adaptor because i don't have a 2.6.33 kernel yet
(believe it or not, i've seen overlay tearing too with an old intel
driver in the past, i think 2.7.1, in a cloned mode if lvds was at
60hz, while vga was at 70hz)
I'm using xf86-video-intel 2.10.0 and kernel 2.6.32.9
I used the framerate test videos available here:
http://spng.se/frame-rate-test/
Thanks for reading.
Last edited by kokoko3k (2010-03-07 08:23:48)You're right, here's the references:
http://lists.freedesktop.org/archives/i … 06092.html
http://bugs.freedesktop.org/show_bug.cgi?id=26925
About your command, i'll try, but what it does is just picking the first port from first adaptor, right?
By now (xf86-video-intel 2.10.0 and kernel 2.6.32.9), we just have a single adaptor, the textured one;
why the first port should make a difference?
Maybe with your setup the overlay adaptor was picked, and in 99% of the cases that would certanly help.
As a side note, newer mplayer versions comes with an useful option: -vo xv:adaptor=#
What i think is that vblank interrupts generation is (and was) messed up in the drivers code.
see:
(believe it or not, i've seen overlay tearing too with an old intel
driver in the past, i think 2.7.1, in a cloned mode if lvds was at
60hz, while vga was at 70hz) -
[Solved] Problem with xf86-video-intel after upgrade to xorg 1.16
Hi everyone,
since the upgrade to xorg-server 1.16 i can't get X to work again on my thinkpad R50e with an old intel integrated chip (Intel Extreme Graphics 2).
I first encountered the error "cannot open /dev/tty0": http://okraits.de/upload/xorg/Xorg.0.log
Then i created /etc/X11/Xwrapper.config: http://okraits.de/upload/xorg/Xwrapper.config
Then i got the error "failed to set mode": http://okraits.de/upload/xorg/Xorg.1.log
My xorg.conf looks like this: http://okraits.de/upload/xorg/xorg.conf
I start X with startx and this .xinitrc: http://okraits.de/upload/xorg/.xinitrc
I have no clue how to fix this. Any help would be much appreciated!
Greetings,
Oliver
Last edited by okraits (2014-08-08 06:33:09)lolilolicon wrote:
How do you start X? Note you must start X from the same VT where you login, if you use Xorg.bin (no setuid). From your log there're mentions of /dev/tty0 and "Using VT number 2", so I suppose that might be the problem.
If you simply use `startx`, the actual process running will be something like
/usr/bin/Xorg.bin -nolisten tcp :0 -auth /tmp/serverauth.XXXXXXXXXX vt1
Note the `vt1` in the line must be specified, where 1 is the value of $XDG_VTNR in the VT where you login.
Edit
In my log there's something yours are missing
[ 45.465] (++) using VT number 1
[ 45.465] (--) controlling tty is VT number 1, auto-enabling KeepTty
I login at tty1 (which is the first one visible after boot) and run startx from there.
I added the following to my .xinitrc:
echo "vt: $XDG_VTNR"
The output was:
vt: 1
That would be ok, right? Or is it $XDG_VTNR + 1?
So i am wondering what is forcing X to use vt 2. Or how i can tell X to use vt 1.
Last edited by okraits (2014-08-07 12:37:17) -
I want to upgrade to Lightroom 5, but I'm concerned about compatibility with my 2008 intel Core 2 Duo iMac with only 4G of Ram. Will I be able to run Lightroom 5 okay if I upgrade from Snow Leopard to Lion? What will happen to the applications that aren't 64-bit compatible? Also the Eye-one Display 2 colorimeter to calibrate the monitor will not run on Lion, so that will be an expensive upgrade to an i1DisplayPro. Is the upgrade important enough to offset the expense? I have an Epson R2000 printer. Will there be problems with the drivers if I upgrade to Lion? It would be great to hear from other mac users who are also photographers and who print their own photos.
Before upgrading to Lion be sure to read this link:
https://discussions.apple.com/docs/DOC-6271
Adobe lists these requirements:
http://www.adobe.com/products/photoshop-lightroom/tech-specs.html
Looking at http://www.everymac.com/ even the earliest 2008 iMac was fully 64 bit, even though Boot Camp doesn't support 64 bit Windows on that machine. -
What hard drive can I upgrade with on iMac intel early 2010
what hard drive can I upgrade with on iMac intel 27 inches early 2010
You can install any 3'5" SATA hard drive on a Late 2009 iMac. Have a look at OWC > http://eshop.macsales.com/shop/internal_storage/hard_drives_and_SSD
Note that Late 2009 and later iMacs have got the temperature sensor inside the hard drive. If you install a hard drive without a sensor, fans won't work correctly. Read > http://blog.macsales.com/2751-proprietary-cable-can-put-the-brakes-on-upgrading- late-09-imacs
Maybe you are looking for
-
Dear All, My client wants to do the performance tuning in a query where it has the Global structure of 300 CKF & 300 RKF. They dont want to touch the MP, all they want to do some performance tuning through the front end without touching the Multiprov
-
Advantages of Using Queued Message Handler vs. Standard State Machine
Hello, What are the advantages of using a Queued Message Handler? Also, why are they more powerful than using Standard State Machines? Thanks!
-
help
-
I already paid for the service, but I can't seem to do the above. If I upload the entire thing the process fails, saying the file is too large...
-
Stop Safari from launching at start up
Can someone please tell me how to stop Safari from launching automatically when I boot my computer. One day it just started launching on it's own. Very annoying to wait for Safari as it pauses my bootup. If you can help, please email me at [email pro