602-OEAP Access Point broken after WLC upgrade to 7.4.100.0

Hey all,
I have a TAC case open, but it doesn't seem to be making any progress....
I upgraded my 5508 controller from 7.2.111.3 up to 7.4.100.0
Most of my APs are fine. 3500s, 1100s etc.except for 602i APs. The APs associate, they update software etc, but they won't broadcast the WLAN.
An interesting thing, on the 602 AP, in the log, I see this:
*Mar 06 15:08:12.667: SSID remote, WLAN Profile Name: RemoteOEAP, added to the slot[0], disabled
So the AP is definately talking to the WLC and being pushed the correct WLAN profile.
Another thing I noticed:
On the controller, the AP shows the the Admin status of the radios is showing DOWN, but the Admin status on the AP itself shows UP
I've done a factory reset on the APs to no avail. I have a 2504 WLC as well that i'm in the process of implementing in a DMZ specificially for these APs, and for testing purposes, I associated the 602 Ap to that WLC as well. This one is running 7.4.100.0 too, same results. It would appear to be a problem with this version of software?
Anyone else had this problem?

Hey, thanks for taking a look at this. Unfortenately, that's not the issue in this case. The AP is set to "United States" and the WLC is only configured for US. Just so I'm looking in the correct place:
On the AP in the WLC, it's under the "Advanced" tab
On the WLC, its under Wireless -> Country correct?
The frustrating part is that the 600 really doesn't have anything that can be configured on it, which means troubleshooting is also limited.

Similar Messages

TX Power Levels are low after WLC upgrade to 7.0.98.0

I recently upgraded our WLC 4404 to release 7.0.98.0. The process was very smooth with no
issues. The controller manages access points in two buildings. Prior to the upgrade the access points were maintaining high TX power levels...typically between 1 and 3. After the upgrade the power levels all droped to 6 and 8. I have confirmed that the correct external antenas have been set for each access point. I have not done a site survey to see if the lower power levels are acceptable. But the environment has been very consistent for the past year with regards to TX power levels. For the time being I have manually set a power level of 2 to prevent any service outages. Is there any explanation as to why the power levels have changed so drastically?

My customer is having a simlar problem with 2106 controller and 1131 AG access point.
After I upgrade the controller for 7.0.98.218, the access points was setting automaticly by controller with power level "0".
When its happening I see the follwing logs
Thu Dec 15 12:19:15 2011 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:3a:98:19:e7:c0 Cause=Heartbeat Timeout Status:NA
70 Thu Dec 15 12:19:15 2011 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:3a:98:19:e7:c0 Cause=Heartbeat Timeout Status:NA
Can You help me?
thanks, Murilo

Access Points not joining WLC

Hello All,
I am trying to deploy several AIR-CAP3502E-E-K9 access points from a cisco 5508 wire lan contoller running ver 7 code. However iam having difficulty regiserting the access points with the WLC. The wlc is connect to a 3650 switch, and each access point is connected to a 2960 switch.
Problem Solved. A bad update was not allowing the access points to get their correct firmware.

You need to provide what Leo stated, that would help a lot. Anyways you can't telnet or ssh into a capwap AP if it has not joined the WLC. So that being said, provide the info Leo requested and then console into the ap and provide use with output from the console. Make sure you reboot the AP and then start capturing the output for around 5 minutes.
Sent from Cisco Technical Support iPad App

Guest Unable to connect after WLC upgrade

Just upgrade software on my WLC5508 from 7.0.98.218 to 7.3.112.0 via GUI interface.
The upgrade was successfully,I can login to WLC.The other 2 WLC also upgraded to the same version and works.
The only issue,for Guest Vlan user didt get IP address and web login page.
Then we decide to revert to old image and working normally
Do you have any suggestion how to troubleshoot it?

I seemed to stumble across a lot of bugs in 7.3 and 7.4 - your symptoms are similar to one I found.
Have a look at CSCua39580 - WebAuth Fails post upgrade to 7.2.110.0
If you have an anchor controller (it's not clear from your post) then the work around is run the main 5508 on 7.3 and the anchor on 7.2.
After working for many weeks with Cisco, they finally released an enginneering version of 7.3 on, or about, 22-Feb-2013.
Try searching for "Addendum Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Special Build 7.3.103.10"
I never did try this version as it would have required a costly MSE upgrade and I'd lost my Mojo for all things wireless by that point.

[SOLVED] nfsroot install broken after kernel upgrade 3.5.6 to 3.6.2

It seems my nfsroot installations have broken after the kernel upgrade to 3.6.2.
This is as far as the boot process gets now (hand copied from the screen):
IP-Config: eth0 complete (from 10.48.50.20):
address: 10.48.50.240 broadcast: 10.48.50.255 netmask: 255.255.255.0
gateway: 0.0.0.0 dns0 : 0.0.0.0 dns1: 0.0.0.0
domain : local
rootserver: 10.48.50.20 rootpath:
filename : /var/tftpboot/pxelinux.0
NFS-Mount: 10.48.50.20:/srv/nfs4/kvmhost0-rootfs
Waiting 10 seconds for device /dev/nfs ...
mount: Protocol not supported
:: running cleanup hook [udev]
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[rootfs /]#
On the server this is what is logged:
Oct 16 21:10:04 tuon dhcpd: DHCPDISCOVER from 00:21:70:eb:02:25 via san
Oct 16 21:10:04 tuon dhcpd: DHCPOFFER on 10.48.50.240 to 00:21:70:eb:02:25 via san
Oct 16 21:10:04 tuon dhcpd: DHCPREQUEST for 10.48.50.240 (10.48.50.20) from 00:21:70:eb:02:25 via san
Oct 16 21:10:04 tuon dhcpd: DHCPACK on 10.48.50.240 to 00:21:70:eb:02:25 via san
Oct 16 21:10:14 tuon rpc.mountd[1323]: authenticated mount request from 10.48.50.240:684 for /srv/nfs4/kvmhost0-rootfs (/srv/nfs4/kvmhost0-rootfs)
Oct 16 21:10:14 tuon rpc.mountd[1323]: refused unmount request from 10.48.50.240 for /new_root (/): not exported
It looks to me like the client is sending the mount request, the server accepts and then for some reason the client thinks it has failed. I can't even see anything strange in the wireshark traces comparing the working client (3.5.6) to the broken one (3.6.2).
Anyone else using nfsroot successfully with the latest kernel?
Any other ideas?
(by the way - despite my directory names, this is using nfs v3 for the rootfs)
Last edited by kmshanah (2012-10-18 03:18:07)

mikep wrote:
Just to confirm that I also have this problem with nfsroot (nfs4 this time) with 3.6.2. Downgrading the kernel does make it go away.
When it is working normally I do seem to get refused unmount messages at shutdown for some reason
refused unmount request from 192.168.1.86 for / (/): not exported
, but the /new_root bit is new and I have no idea where it comes from.
refused unmount request from 192.168.1.86 for /new_root (/): not exported
So I wonder if it asking for the wrong path.
That unmount issue will be solved by FS#32021.
Unfortunately, that doesn't help with mounting in the first place with 3.6.2

Access points joining different WLC

hi
i have a wireless controller module( NME-AIR-WLC25-K9) installed in a Cisco 2851 ISR, this setup is in my remote site, we are connected through MAN network. In our main office i have a cisco 4402 wireless controller. so whenever i install a AP in my remote site instead of joiining the remote site WLC, the access point joins my main office 4402 controller, i dont why it is happening, the AP is not even trying to join the remote site WLC.. i have not configured high availability and both these controller are in separate RF network.
the firmware version in NME-AIR-WLC25-K9 is 7.0.98.0 ...
the version in the other controller is 6.0.196.0
Please let me know what is else i need to check asap
Thanks
karthik

Hi,
Did you even see the AP trying to join the local controller? If the controller are in different domains, the AP will prefer the remote controller since it join that one first. Since you are running 5.2, try configure on the AP the primary controller with the name, and local IP address of the local controller, and then reboot the AP. See if after that the AP join. run debug capwap events enable to see if you see the AP event trying to join the controller.
Regards,
Manuel

Access Points Joining Random WLC

My environment contains 4 seperate controllers. 1 controller in the datacenter which remote offices use with HREAP and discover this WLC using DNS We will call this Controller WLC1. 2 more controllers (WLC 2 and WLC 3) in the corporate headquarters to support >40 access points in a N+1 configuration and finally an anchor controller which doesnt matter in this post.
What I am experiencing is Access points in the Corporate office are using DHCP option 43 to discover the WLC2. every night or after long periods of time a random number of my access points are either rebooting or most likely sleeping. Then are attaching them selves to WLC 1 which is in the datacenter and is not supporting DHCP from that location which to clients make the wireless network seem to be down.
I think that with using a hybrid of DHCP and DNS is partly my issue but it shouldnt be. I have primed all the Access point to look at primary controller WLC1 and secondary controller WLC2 both by name and using the IP address of the respective management ports.
Can there be any explaination for this and why this seems to be so random?
WLCs are 5508
Corporate Access points are 1142
***EDIT
After some more investigation this isnt completely random rebooting the access points in question are connected to a new 4506-E chassis with the Sup 6-E while the other access points are connected to a 6509-E.. not sure how much this matters but I am seeing in the access point logs that about every 2-3 hours they are accessing DHCP again and sometime not successfully. Is there some EnergyWise or power savings happening on the 4500 possibly??

I understand that all and here is a screen shot (see attached) of an ap that was on WLC 2 last night at midnight when i wrote this orginally and now how jumped to WLC 2.. The major issue here is that WLC 1 does not give out DHCP because it is used for HREAP and remote office that have other local DHCP servers.
I am running code 6.0.199.4
Now yes all controllers WLC1,2,and3 are in the same mobilty group. Maybe I should move the WLC1 out of the mobility group and that might solve the issue. Here is a log too. See timing is 3 hours and then its trying to find another controller. I see a retransmission count exceeded here. What can cause that? I have 4 port LAG configured on both WLC2 and WLC3 and they are both on seperate 6500 switches. This access point is on a seperate floor connected to a 4500 with uplink to each of the 6500's
**********LOG from Access Point***********
*Oct 14 02:41:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.104.210.21 peer_port: 5246 This Is correct
*Oct 14 02:41:21.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Oct 14 02:41:21.826: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.104.210.21 peer_port: 5246
*Oct 14 02:41:21.827: %CAPWAP-5-SENDJOIN: sending Join Request to 10.104.210.21
*Oct 14 02:41:21.827: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Oct 14 02:41:21.911: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Oct 14 02:41:22.047: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Oct 14 02:41:22.052: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
*Oct 14 02:41:22.173: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller nwcp01-1211-02b
*Oct 14 02:41:22.254: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[0]
*Oct 14 02:41:22.255: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to WMM is not enabled
*Oct 14 02:41:22.257: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[0]
*Oct 14 02:41:22.259: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[1]
*Oct 14 02:41:22.261: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[1]
*Oct 14 02:41:22.263: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to WMM is not enabled
*Oct 14 02:41:22.263: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 2 due to WMM is not enabled
*Oct 14 02:41:22.264: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 2 due to WMM is not enabled
*Oct 14 02:41:22.274: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
*Oct 14 05:57:40.164: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_ECHO_REQUEST
., 3)
*Oct 14 05:57:40.164: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Oct 14 05:57:40.164: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.104.210.21:5246 *** This is correct
*Oct 14 05:57:40.206: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Oct 14 05:57:40.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 14 05:57:40.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 14 05:57:50.229: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Oct 14 05:57:49.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.98.10.20 peer_port: 5246 **This is the controller it should never get on.
*Oct 14 05:57:49.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Oct 14 05:57:49.844: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.98.10.20 peer_port: 5246
*Oct 14 05:57:49.845: %CAPWAP-5-SENDJOIN: sending Join Request to 10.98.10.20
*Oct 14 05:57:49.845: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Oct 14 05:57:49.930: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Oct 14 05:57:50.078: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Oct 14 05:57:50.078: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
*Oct 14 05:57:50.206: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller nep00WLC00e
*Oct 14 05:57:50.293: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[0]
*Oct 14 05:57:50.298: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[0]
*Oct 14 05:57:50.303: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[1]
*Oct 14 05:57:50.309: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[1]
*Oct 14 05:57:50.414: %WIDS-6-ENABLED: IDS Signature is loaded and enabled

IP Phone 7921 / 7925 roaming issues after WLC upgrade from Version 7.2 to 7.3 and / or 7.4

Hi,
We have a customer which is using a Cisco WLC 5508 and 3502I APs. As he used the 7.2.103 release, There were no issues with VoWLAN. Now he needed new APs and ordered the 2602I. To use them he needed to upgrade the WLC to a 7.3 or later release. After the upgrade, he now encounters problems while roaming with the phones. The phones were tested with FW 1.4.1, 1.4.2 and 1.4.3.
Configuration is set according to wireless voice design guides (VoWLAN DG 4.1, 7921 Deployment Guide). A Cisco TAC is also in progress, but they seem to be uncertain whether it is a wireless or CUCM issue, but I don't see a reason why it should be the CUCM when the only thing changed is the WLC Software Version.
Is there anybody who is aware of such issues and can offer help?
Thank you in advance.
Best regards,
Patrick

Hi,
we had a TAC ticket open with this customer and after some time, the TAC gave us the advise to use this release and the problems are now solved.
So for others having the same issue: If you only need to support the 2600 APs, stay with the latest 7.2 release as there are some issues with the 7.3 and 7.4 release. If the customer requires HA, AVC or any of the new features + wireless voice, be very careful as it seems that the newer releases are having problems with that. I hope that Cisco will fix this very soon.
regards,
Patrick

Access point connection to WLC

Hi all,
I wanted to know that in Cisco wireless or in general, is it possible to connect lightweigt access point with controller without any wired connection ? or a ethernet connection between an AP and WLC is mandatory ???

What can't you find?
Reference to the Wireless LAN Controller not having a Wireless NIC? The documents won't list everything the product doesn't come with, it lists what it does come with.
This guide is helpful:
http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED.pdf
It doesn't state that the Access Points can communicate with the WLC Wirelessly because they can't.

When trying to access itunes store after itunes upgrade, windows dep turns off program. have updated quicktime player

After newest upgrade to itunes when trying to access itunes store, windows dep turns off program. Have upgraded Quicktime player. Can not turn off dep for itunes.

miniart18 found a solution and posted it on another post. her solution is to right click on itunes shortcut & pick "run as administrator". thanks again miniart18!!

CISCO WAP4410N Access Point disconnect after a short while

Dear Sir,
i bought one access point then we configured as Wireless Client/Repeater but wireless connection disconnecting and connecting after a short while
i tried 4 more different ADSL and different IP range ADSL model showing same.
so please advice on this matter ASAP.
Thanks.
Rahmath.CK

My name Eric Moyers. I am an Engineer in the Small Business Support Center.
I am sorry that no one has responded before now. What is the router that you are trying to repeat?
What were the steps you went through to do this?
According to the Admin Guide for the WAP4410N it will only repeat the WRVS4400N and another WAP4410N.
Eric Moyers
.:|:.:|:. CISCO | Cisco Presales Technical Support | Wireless Subject Matter Expert
Please rate helpful Posts and Let others know when your Question has been answered.

1131 access point, broken flash?

I have had two 1131 access points die in the last few weeks, both with the same symptoms. I suspect both have broken flash systems and are due for the bin. If anyone can offer any confirmation or a way to fix it, I would be grateful.
On booting, it gives the following error:
Xmodem file system is available.
flashfs[0]: unable to allocate available block.
The system has been interrupted, or encountered an error
during initializion of the flash filesystem. The following
commands will initialize the flash filesystem, and finish
loading the operating system software:
    flash_init
    ether_init
    tftp_init
    boot
ap:
Trying to wake up the flash:
ap: flash_init
Initializing Flash...
flashfs[0]: unable to allocate available block.
...done Initializing Flash.
ap: dir flash
unable to stat flash/: permission denied
I have tried the standard recovery mode of uploading a new firmware via TFTP, but I can't even set variables:
ap: set IP_ADDR 10.0.0.1
flash:/env_vars.tmp: invalid argument
The filesystem containing the variables may not be initialized yet.

Thanks for the tip, however I should probably have said the access points are autonomous, so the method you suggested will not work.
Yes it does.
You need a two-step method.
Your AP is booting up with either no IOS or a corrupt IOS.
1. In order to efficiently transfer the IOS to an AP that has no IOS you need to use the process I've posted earlier.
2. Once the AP boots up in autonomous mode, it's as easy as giving the BVI1 an IP address and use the command "copy tftp: flash:" to transfer the LWAP/CAPWAP IOS to the AP.

Spotlight and Time Machine broken after restore/upgrade

I've found a few similar threads to this but none of those solutions has worked for me.
Two things happened at nearly the same time, so I don't exactly know the source of my problem:
I upgraded my old MacBook Pro (approx. Oct 2010, 2.66GHz I think, 300GB-ish HD) from Lion to Mountain Lion
The hard drive on my old MacBook Pro developed a terminal fault, so I had to buy a new one (8GB, 750GB HD) and restore a month-old Time Machine backup from my external drive.
I can't remember whether my last Time Machine backup to my external drive was before or after I upgraded to Mountain Lion.
Now I'm on OS X 10.8.2 on this new machine and I have two problems that seem to co-exist for a lot of other people too:
Spotlight won't index: this is f***ing infuriating, I love spotlight and I use it all the time. When I first restored from the TM backup I think the old index restored with the backup as I did get a decent number of search results (both in spotlight and in MS Outlook), but new files didn't seem to get recognised. I tried adding my hard drive to the exclusion list and removing it again in an attempt to get it to rebuild the index, but all that did was wipe the old index without building a new one, so now I get no spotlight results whatsoever. I tried this solution and sadly it hasn't worked either. Basically I can't search for anything. Even applications (which I like to launch from spotlight) don't appear. All I get is "estimating indexing time", and it never gets any further.
Time Machine won't back up: the first time I tried to backup my new machine it got a few hundred megabytes in before stalling; then a few hundred kilobytes in the next time I tried; and now it just doesn't get anywhere at all. The external drive I'm trying to backup to is recognised fine, I can see all the other files on it, and Time Machine seems to know that it's there, but the backup gets nowhere.
There are reports of this kinds of crap all over the Apple Support forums, but no definitive answer, especially for 10.8.2.
I could really do with some help on this. I need a backup before I screw another laptop, and I need spotlight to survive day-to-day life.
Thanks,
Craig

Hi Craig - I had the exact same problem - I'm using an old early 2009 MacBook Pro upgraded to 8 Gb Ram, 1 TB internal Hitachi HD, 10.8.2 - tried the fixes suggested - got it to work with these steps- everybodies mileage is different but hopefully it works for you as well.
a) I repaired disk permissions with Onyx (free utility) and then started up with Command-R using Disk Utility to repaired/check the Volume (harddisk checked out fine but the volume needed some minor repairs )- Onyx repair disk permission seems to go deeper -had to reinstall some apps - don't know if this solved it-seems to bring it back to the default state - you might get away with doing all from Disk Utility (but starting up with Command-R)
b) restart from my internal hd
c) downloaded the 10.8.2 combo update ( not the incremental shell update or whatever you call it which automatically gets installed with software update - combo update installs everything fresh from the .0 version)
d) with Onyx I deactivated spotlight and erased the spotlight index
d) restart
e) started TM backup - prep took pretty long 30 minutes but then 450 GB got backed up in 6 hours to my external HD which is fast enough for me
f) activated spotlight and 450 Gb were indexed in 9 hours or so
g) for 2 days everything runs fast and very responsive
best,
Franz

X/XFCE broken after recent upgrade

I just upgraded, and I am having some issues with X that don't match up with anything else posted recently. I am running XFCE on a GeForce 9800 GT, and I have a dual-monitor setup.
When I run
startxfce
both screens start up fine, but the mouse is the X 'X' instead of a pointer, and when one window is open I cannot interact with other windows, or change between them with alt-tab or the like. To get a terminal I am sshing in from another machine.
I have tried downgrading xorg-server and the nvidia package, with no result or I lose the ability to start X entirely. Here is my xorg.conf:
Section "ServerLayout"
# Removed Option "Xinerama" "0"
Identifier "Layout0"
Screen 0 "Screen0" 900 0
Screen 1 "Screen1" LeftOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Ancor Communications Inc MT276"
HorizSync 30.0 - 83.0
VertRefresh 50.0 - 76.0
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "ViewSonic VA1912w-3"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 85.0
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 9800 GT"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 9800 GT"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-0"
Option "metamodes" "DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "CRT-1"
Option "metamodes" "CRT: nvidia-auto-select +0+0 { Rotation=left }"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Monitor 1 is rotated vertically and to the left of monitor 0.
I'm not sure what else to play with/downgrade, and I'm not sure what caused these problems, they started after a reboot. Any ideas?

Here is my /var/log/Xorg.0.log:
[ 25.834]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 25.834] X Protocol Version 11, Revision 0
[ 25.834] Build Operating System: Linux 3.6.0-1-ARCH x86_64
[ 25.834] Current Operating System: Linux aitchbar 3.6.3-1-ARCH #1 SMP PREEMPT Mon Oct 22 10:23:56 CEST 2012 x86_64
[ 25.835] Kernel command line: root=/dev/disk/by-uuid/8afb427d-3196-4611-9073-044f84ea418c ro
[ 25.835] Build Date: 05 October 2012 01:57:18PM
[ 25.835]
[ 25.835] Current version of pixman: 0.26.2
[ 25.835] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 25.835] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 25.837] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 29 07:53:16 2012
[ 25.838] (==) Using config file: "/etc/X11/xorg.conf"
[ 25.838] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 25.839] (==) ServerLayout "Layout0"
[ 25.839] (**) |-->Screen "Screen0" (0)
[ 25.839] (**) | |-->Monitor "Monitor0"
[ 25.839] (**) | |-->Device "Device0"
[ 25.839] (**) |-->Screen "Screen1" (1)
[ 25.839] (**) | |-->Monitor "Monitor1"
[ 25.840] (**) | |-->Device "Device1"
[ 25.840] (**) |-->Input Device "Keyboard0"
[ 25.840] (**) |-->Input Device "Mouse0"
[ 25.840] (**) Option "Xinerama" "1"
[ 25.840] (==) Automatically adding devices
[ 25.840] (==) Automatically enabling devices
[ 25.840] (==) Automatically adding GPU devices
[ 25.840] (**) Xinerama: enabled
[ 25.843] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 25.843] Entry deleted from font path.
[ 25.847] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 25.847] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 25.847] (**) Extension "Composite" is disabled
[ 25.847] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 25.847] (WW) Disabling Keyboard0
[ 25.847] (WW) Disabling Mouse0
[ 25.847] (II) Loader magic: 0x7fcc20
[ 25.847] (II) Module ABI versions:
[ 25.847] X.Org ANSI C Emulation: 0.4
[ 25.847] X.Org Video Driver: 13.0
[ 25.847] X.Org XInput driver : 18.0
[ 25.847] X.Org Server Extension : 7.0
[ 25.851] (--) PCI:*(0:1:0:0) 10de:0614:0000:0000 rev 162, Mem @ 0xfa000000/16777216, 0xd0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000ef00/128, BIOS @ 0x????????/131072
[ 25.851] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 25.851] Initializing built-in extension Generic Event Extension
[ 25.851] Initializing built-in extension SHAPE
[ 25.851] Initializing built-in extension MIT-SHM
[ 25.851] Initializing built-in extension XInputExtension
[ 25.851] Initializing built-in extension XTEST
[ 25.852] Initializing built-in extension BIG-REQUESTS
[ 25.852] Initializing built-in extension SYNC
[ 25.852] Initializing built-in extension XKEYBOARD
[ 25.852] Initializing built-in extension XC-MISC
[ 25.852] Initializing built-in extension SECURITY
[ 25.852] Initializing built-in extension XINERAMA
[ 25.852] Initializing built-in extension XFIXES
[ 25.852] Initializing built-in extension RENDER
[ 25.853] Initializing built-in extension RANDR
[ 25.853] Initializing built-in extension COMPOSITE
[ 25.853] Initializing built-in extension DAMAGE
[ 25.853] Initializing built-in extension MIT-SCREEN-SAVER
[ 25.853] Initializing built-in extension DOUBLE-BUFFER
[ 25.853] Initializing built-in extension RECORD
[ 25.853] Initializing built-in extension DPMS
[ 25.853] Initializing built-in extension X-Resource
[ 25.854] Initializing built-in extension XVideo
[ 25.854] Initializing built-in extension XVideo-MotionCompensation
[ 25.854] Initializing built-in extension XFree86-VidModeExtension
[ 25.854] Initializing built-in extension XFree86-DGA
[ 25.854] Initializing built-in extension XFree86-DRI
[ 25.854] Initializing built-in extension DRI2
[ 25.854] (II) LoadModule: "glx"
[ 25.855] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 25.934] (II) Module glx: vendor="NVIDIA Corporation"
[ 25.934] compiled for 4.0.2, module version = 1.0.0
[ 25.934] Module class: X.Org Server Extension
[ 25.934] (II) NVIDIA GLX Module 304.60 Sun Oct 14 20:44:54 PDT 2012
[ 25.934] Loading extension GLX
[ 25.934] (II) LoadModule: "nvidia"
[ 25.935] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 25.943] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 25.943] compiled for 4.0.2, module version = 1.0.0
[ 25.943] Module class: X.Org Video Driver
[ 25.945] (II) NVIDIA dlloader X Driver 304.60 Sun Oct 14 20:24:42 PDT 2012
[ 25.945] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 25.945] (--) using VT number 7
[ 25.948] (II) Loading sub module "fb"
[ 25.948] (II) LoadModule: "fb"
[ 25.949] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 25.950] (II) Module fb: vendor="X.Org Foundation"
[ 25.950] compiled for 1.13.0, module version = 1.0.0
[ 25.950] ABI class: X.Org ANSI C Emulation, version 0.4
[ 25.950] (II) Loading sub module "wfb"
[ 25.950] (II) LoadModule: "wfb"
[ 25.950] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 25.951] (II) Module wfb: vendor="X.Org Foundation"
[ 25.951] compiled for 1.13.0, module version = 1.0.0
[ 25.951] ABI class: X.Org ANSI C Emulation, version 0.4
[ 25.951] (II) Loading sub module "ramdac"
[ 25.951] (II) LoadModule: "ramdac"
[ 25.951] (II) Module "ramdac" already built-in
[ 25.952] (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the
[ 25.952] (WW) NVIDIA: X server.
[ 25.953] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 25.954] (==) NVIDIA(0): RGB weight 888
[ 25.954] (==) NVIDIA(0): Default visual is TrueColor
[ 25.954] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 25.954] (**) NVIDIA(0): Option "Stereo" "0"
[ 25.954] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-0"
[ 25.954] (**) NVIDIA(0): Stereo disabled by request
[ 25.954] (**) NVIDIA(0): Option "MetaModes" "DFP: nvidia-auto-select +0+0"
[ 25.954] (**) NVIDIA(1): Option "MetaModes" "CRT: nvidia-auto-select +0+0 { Rotation=left }"
[ 25.954] (**) NVIDIA(0): Enabling 2D acceleration
[ 26.890] (II) NVIDIA(GPU-0): Display (ViewSonic VA1912w-3 (CRT-1)) does not support NVIDIA
[ 26.890] (II) NVIDIA(GPU-0): 3D Vision stereo.
[ 26.973] (II) NVIDIA(GPU-0): Display (Ancor Communications Inc MT276 (DFP-0)) does not
[ 26.973] (II) NVIDIA(GPU-0): support NVIDIA 3D Vision stereo.
[ 26.975] (II) NVIDIA(0): NVIDIA GPU GeForce 9800 GT (G92) at PCI:1:0:0 (GPU-0)
[ 26.975] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 26.975] (--) NVIDIA(0): VideoBIOS: 62.92.84.00.06
[ 26.975] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 26.975] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 26.984] (--) NVIDIA(0): Valid display device(s) on GeForce 9800 GT at PCI:1:0:0
[ 26.984] (--) NVIDIA(0): CRT-0
[ 26.984] (--) NVIDIA(0): ViewSonic VA1912w-3 (CRT-1) (connected)
[ 26.984] (--) NVIDIA(0): Ancor Communications Inc MT276 (DFP-0) (connected)
[ 26.984] (--) NVIDIA(0): DFP-1
[ 26.984] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 26.984] (--) NVIDIA(0): ViewSonic VA1912w-3 (CRT-1): 400.0 MHz maximum pixel clock
[ 26.984] (--) NVIDIA(0): Ancor Communications Inc MT276 (DFP-0): 330.0 MHz maximum pixel clock
[ 26.984] (--) NVIDIA(0): Ancor Communications Inc MT276 (DFP-0): Internal Dual Link TMDS
[ 26.984] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 26.984] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 26.984] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 26.984] (**) NVIDIA(0): device Ancor Communications Inc MT276 (DFP-0) (Using EDID
[ 26.984] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 26.986] (WW) NVIDIA(GPU-0): The EDID for Ancor Communications Inc MT276 (DFP-0)
[ 26.986] (WW) NVIDIA(GPU-0): contradicts itself: mode "1920x1080" is specified in the
[ 26.986] (WW) NVIDIA(GPU-0): EDID; however, the EDID's valid HorizSync range
[ 26.986] (WW) NVIDIA(GPU-0): (30.000-83.000 kHz) would exclude this mode's HorizSync
[ 26.986] (WW) NVIDIA(GPU-0): (28.1 kHz); ignoring HorizSync check for mode
[ 26.986] (WW) NVIDIA(GPU-0): "1920x1080".
[ 26.988] (II) NVIDIA(0): Validated MetaModes:
[ 26.988] (II) NVIDIA(0): "DFP:nvidia-auto-select+0+0"
[ 26.988] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 27.017] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" X config
[ 27.017] (--) NVIDIA(0): option
[ 27.017] (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
[ 27.017] (==) NVIDIA(1): RGB weight 888
[ 27.017] (==) NVIDIA(1): Default visual is TrueColor
[ 27.017] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[ 27.017] (**) NVIDIA(1): Option "Stereo" "0"
[ 27.017] (**) NVIDIA(1): Option "nvidiaXineramaInfoOrder" "CRT-1"
[ 27.017] (**) NVIDIA(1): Stereo disabled by request
[ 27.017] (II) NVIDIA(1): NVIDIA GPU GeForce 9800 GT (G92) at PCI:1:0:0 (GPU-0)
[ 27.017] (--) NVIDIA(1): Memory: 1048576 kBytes
[ 27.017] (--) NVIDIA(1): VideoBIOS: 62.92.84.00.06
[ 27.017] (II) NVIDIA(1): Detected PCI Express Link width: 16X
[ 27.017] (--) NVIDIA(1): Interlaced video modes are supported on this GPU
[ 27.025] (--) NVIDIA(1): Valid display device(s) on GeForce 9800 GT at PCI:1:0:0
[ 27.025] (--) NVIDIA(1): CRT-0
[ 27.025] (--) NVIDIA(1): ViewSonic VA1912w-3 (CRT-1) (connected)
[ 27.025] (--) NVIDIA(1): Ancor Communications Inc MT276 (DFP-0) (connected)
[ 27.025] (--) NVIDIA(1): DFP-1
[ 27.025] (--) NVIDIA(1): CRT-0: 400.0 MHz maximum pixel clock
[ 27.025] (--) NVIDIA(1): ViewSonic VA1912w-3 (CRT-1): 400.0 MHz maximum pixel clock
[ 27.025] (--) NVIDIA(1): Ancor Communications Inc MT276 (DFP-0): 330.0 MHz maximum pixel clock
[ 27.025] (--) NVIDIA(1): Ancor Communications Inc MT276 (DFP-0): Internal Dual Link TMDS
[ 27.025] (--) NVIDIA(1): DFP-1: 165.0 MHz maximum pixel clock
[ 27.025] (--) NVIDIA(1): DFP-1: Internal Single Link TMDS
[ 27.025] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
[ 27.025] (**) NVIDIA(1): device ViewSonic VA1912w-3 (CRT-1) (Using EDID frequencies
[ 27.025] (**) NVIDIA(1): has been enabled on all display devices.)
[ 27.028] (II) NVIDIA(1): Validated MetaModes:
[ 27.028] (II) NVIDIA(1): "CRT:nvidia-auto-select+0+0{Rotation=left}"
[ 27.028] (II) NVIDIA(1): Virtual screen size determined to be 900 x 1440
[ 27.038] (--) NVIDIA(1): DPI set to (55, 140); computed from "UseEdidDpi" X config
[ 27.038] (--) NVIDIA(1): option
[ 27.038] (--) Depth 24 pixmap format is 32 bpp
[ 27.038] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 27.043] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 27.043] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 27.043] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 27.043] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 27.043] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 27.043] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 27.043] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 27.043] (II) NVIDIA(0): Config Options in the README.
[ 27.051] (II) NVIDIA(0): Setting mode "DFP:nvidia-auto-select+0+0"
[ 27.084] Loading extension NV-GLX
[ 27.105] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 27.105] (==) NVIDIA(0): Backing store disabled
[ 27.105] (==) NVIDIA(0): Silken mouse enabled
[ 27.105] (**) NVIDIA(0): DPMS enabled
[ 27.105] Loading extension NV-CONTROL
[ 27.105] (II) Loading sub module "dri2"
[ 27.105] (II) LoadModule: "dri2"
[ 27.105] (II) Module "dri2" already built-in
[ 27.106] (II) NVIDIA(0): [DRI2] Setup complete
[ 27.106] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 27.106] (WW) NVIDIA(0): Not registering RandR
[ 27.106] (==) RandR enabled
[ 27.110] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 27.110] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
[ 27.110] (II) NVIDIA(1): configuration option may not be set correctly. When the
[ 27.110] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
[ 27.110] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
[ 27.110] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
[ 27.110] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
[ 27.110] (II) NVIDIA(1): Config Options in the README.
[ 27.110] (II) NVIDIA(1): Setting mode "CRT:nvidia-auto-select+0+0{Rotation=left}"
[ 27.201] (==) NVIDIA(1): Disabling shared memory pixmaps
[ 27.201] (==) NVIDIA(1): Backing store disabled
[ 27.201] (==) NVIDIA(1): Silken mouse enabled
[ 27.201] (==) NVIDIA(1): DPMS enabled
[ 27.202] (II) Loading sub module "dri2"
[ 27.202] (II) LoadModule: "dri2"
[ 27.202] (II) Module "dri2" already built-in
[ 27.202] (II) NVIDIA(1): [DRI2] Setup complete
[ 27.202] (II) NVIDIA(1): [DRI2] VDPAU driver: nvidia
[ 27.202] (WW) NVIDIA(1): Not registering RandR
[ 27.202] (==) RandR enabled
[ 27.209] (II) Initializing extension GLX
[ 27.370] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 27.370] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 27.370] (II) LoadModule: "evdev"
[ 27.371] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 27.372] (II) Module evdev: vendor="X.Org Foundation"
[ 27.372] compiled for 1.13.0, module version = 2.7.3
[ 27.372] Module class: X.Org XInput Driver
[ 27.372] ABI class: X.Org XInput driver, version 18.0
[ 27.372] (II) Using input driver 'evdev' for 'Power Button'
[ 27.372] (**) Power Button: always reports core events
[ 27.372] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 27.372] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 27.372] (--) evdev: Power Button: Found keys
[ 27.372] (II) evdev: Power Button: Configuring as keyboard
[ 27.372] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 27.372] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 27.372] (**) Option "xkb_rules" "evdev"
[ 27.372] (**) Option "xkb_model" "evdev"
[ 27.372] (**) Option "xkb_layout" "us"
[ 27.401] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 27.401] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 27.401] (II) Using input driver 'evdev' for 'Power Button'
[ 27.401] (**) Power Button: always reports core events
[ 27.401] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 27.401] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 27.401] (--) evdev: Power Button: Found keys
[ 27.401] (II) evdev: Power Button: Configuring as keyboard
[ 27.401] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 27.401] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 27.401] (**) Option "xkb_rules" "evdev"
[ 27.401] (**) Option "xkb_model" "evdev"
[ 27.402] (**) Option "xkb_layout" "us"
[ 27.403] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event11)
[ 27.403] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 27.403] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 27.403] (**) Logitech USB Receiver: always reports core events
[ 27.403] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event11"
[ 27.403] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 27.403] (--) evdev: Logitech USB Receiver: Found keys
[ 27.403] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 27.403] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.2/usb3/3-2/3-2.2/3-2.2:1.0/input/input11/event11"
[ 27.403] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 8)
[ 27.403] (**) Option "xkb_rules" "evdev"
[ 27.403] (**) Option "xkb_model" "evdev"
[ 27.403] (**) Option "xkb_layout" "us"
[ 27.405] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event12)
[ 27.405] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 27.405] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 27.405] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 27.405] (**) Logitech USB Receiver: always reports core events
[ 27.405] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event12"
[ 27.405] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 27.405] (--) evdev: Logitech USB Receiver: Found 12 mouse buttons
[ 27.405] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 27.405] (--) evdev: Logitech USB Receiver: Found relative axes
[ 27.405] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 27.405] (--) evdev: Logitech USB Receiver: Found absolute axes
[ 27.405] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[ 27.405] (--) evdev: Logitech USB Receiver: Found keys
[ 27.405] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 27.405] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 27.405] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 27.405] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 27.405] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 27.405] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.2/usb3/3-2/3-2.2/3-2.2:1.1/input/input12/event12"
[ 27.405] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[ 27.405] (**) Option "xkb_rules" "evdev"
[ 27.405] (**) Option "xkb_model" "evdev"
[ 27.405] (**) Option "xkb_layout" "us"
[ 27.406] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 27.407] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[ 27.407] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 27.407] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 27.407] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 27.407] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 27.407] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 27.407] (II) No input driver specified, ignoring this device.
[ 27.407] (II) This device may have been added with another device file.
[ 27.407] (II) config/udev: Adding input device HDA ATI SB Line Out Front (/dev/input/event10)
[ 27.407] (II) No input driver specified, ignoring this device.
[ 27.407] (II) This device may have been added with another device file.
[ 27.407] (II) config/udev: Adding input device HDA ATI SB Line (/dev/input/event3)
[ 27.407] (II) No input driver specified, ignoring this device.
[ 27.407] (II) This device may have been added with another device file.
[ 27.407] (II) config/udev: Adding input device HDA ATI SB Front Mic (/dev/input/event4)
[ 27.407] (II) No input driver specified, ignoring this device.
[ 27.407] (II) This device may have been added with another device file.
[ 27.407] (II) config/udev: Adding input device HDA ATI SB Rear Mic (/dev/input/event5)
[ 27.407] (II) No input driver specified, ignoring this device.
[ 27.407] (II) This device may have been added with another device file.
[ 27.407] (II) config/udev: Adding input device HDA ATI SB Front Headphone (/dev/input/event6)
[ 27.407] (II) No input driver specified, ignoring this device.
[ 27.408] (II) This device may have been added with another device file.
[ 27.408] (II) config/udev: Adding input device HDA ATI SB Line Out Side (/dev/input/event7)
[ 27.408] (II) No input driver specified, ignoring this device.
[ 27.408] (II) This device may have been added with another device file.
[ 27.408] (II) config/udev: Adding input device HDA ATI SB Line Out CLFE (/dev/input/event8)
[ 27.408] (II) No input driver specified, ignoring this device.
[ 27.408] (II) This device may have been added with another device file.
[ 27.408] (II) config/udev: Adding input device HDA ATI SB Line Out Surround (/dev/input/event9)
[ 27.408] (II) No input driver specified, ignoring this device.
[ 27.408] (II) This device may have been added with another device file.
[ 27.408] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 27.408] (II) No input driver specified, ignoring this device.
[ 27.408] (II) This device may have been added with another device file.
I tried downgrading xorg-server-common along with xorg-server (both from version 1.13.0-3 to 1.13.0-2) and rebooted, with no change. I do not have an older version of xf86-input-evdev.
I notice that xfce4-settings has been upgraded recently (10/20) but I do not have an older version of that either.

Failed to verify preflight file ... App Store broken after Mavericks upgrade

I upgraded my OS X to Mavericks and the install was very smooth. Since then, however, I cannot update any apps or purchase new ones in the App Store. I receive a message saying "Failed to verify the preflight file. It is not signed by Apple. The application will be available from the Purchases page." Unfortunately the same thing happens when I use the Purchases page as well.
Am I doing something wrong or did something break with App Store after my installation?

What worked for me was changing the certificate preferences in Keychain Access (open Keychain Access app and then go to preferences).
I just changed both of the first two options to 'Best Attempt', they were originaly at 'Require if certificate indicates'.
Hope this Helps

602-OEAP Access Point broken after WLC upgrade to 7.4.100.0

Similar Messages

Maybe you are looking for