JavaSoundDemo works, JMStudio fails on Capture

Has anyone else seen this problem?
I wrote a simple audio driver that only outputs data at 8KHz.
When I run the JavaSoundDemo to capture data, it works like a champ.
When I run JMStudio, I get an error that 44Khz capture isn't supported:
XX Audio not supported: interface TargetDataLine supporting format PCM_SIGNED, 44100.0 Hz, 16bit, stero, little-endian, audio data and buffers of 22050 to 22050 bytes.
This message, while certainly true in my case, is slightly interesting, since I have no idea why JMStudio is requesting an inpu format of that type.
As a matter of fact, it seems as if all types of formats are checked (my driver is reporting this info), before I get this failure message.
Bob

check if you have crossing use of JavaSound and JMF, they have some same-named classes.
And try to use any of CaptureDevice-s which getCaptureDevices(null) returns.
You can also try to set MediaLocator as javasound://44100/ or such, I dont remember in details
Good luck

Similar Messages

Captivate fails to capture screen

Hi,
I need some help in understanding why on certain applications
Captivate fails to :-
Capture drop down menus
and on the same application the "printscreen" function seems
not to work.
The application I'm trying to capture is Latent Zero.
Thanks
Tom.

Hello Tom,
What version of Captivate are you using? I have experienced
these sorts of problems when attempting to capture screens using an
application viewer program such as Real VNC with Captivate 1 but
this one was addressed in Adobe Captivate 2
Regards,
Mark

Failed to capture service in APP-V 5.0 SP2

Failed to capture service in APP-V 5.0 SP2
Seq’r Version: APP-V 5.0 SP2
OS version: Windows 7 64 bit SP2
Issue: Application (Source) installing two services.
IBM MQSeries
IBM WebSphere
But while seq’g the application, seq’r able to capture only one service (IBM MQSeries) not second service (IBM WebSPhere)
Cont...

My Observations:
1. If we observe second service “IBM WebSphere” is log on as “.\MUSR_MQADMIN” with password as shown below.
Apparently APP-V 5.0 SP2 Seq’r will capture only services log on as “localsystem” on source installation.
cont...

MacbookPro (Late 2013) FaceTime/iMessage suddenly stopped working "FaceTime Failed"

FaceTime/iMessage suddenly stopped working "FaceTime Failed" although i am calling the same number, what can i do to fix this?

Hello cameronmhill,
It sounds like you are unable to use FaceTime on your Mac with an error that it has failed. I recommend these troubleshooting steps from the article named:
FaceTime for Mac: Troubleshooting FaceTime
http://support.apple.com/kb/ts4185
Check that your email address is verified in FaceTime > Preferences.If FaceTime > Preferences shows your email status as "verifying," follow the instructions in the verification email that was sent to complete the process.
Toggle FaceTime off and on in FaceTime > Preferences.
If still unable to Sign In follow the instructions in FaceTime, Game Center, Messages on OS X: Troubleshooting Sign in
Troubleshooting FaceTime for Mac
You can make FaceTime calls using the FaceTime app. You can call FaceTime users whose contact information is in Contacts. You can add contacts and edit contact information in either FaceTime or Contacts. To place a video call, you may use a phone number or email address.
If you encounter issues making or receiving FaceTime calls, try the following:
Verify that FaceTime is enabled in FaceTime > Preferences.If the issue persists, or if you see the message "Waiting for Activation", try toggling FaceTime off and then on.
Verify that the Date, Time, and Time Zone are set correctly:
From the Apple () menu, choose System Preferences > Date & Time > Date & Time.
Enable "Set Automatically".
Click the Time Zone tab and confirm the closest city is correct
Thank you for using Apple Support Communities.
All the best,
Sterling

Mediator fails to capture bpel output

Mediator fails to capture bpel output
Edited by: soauser on Jan 8, 2012 10:24 AM

Mediator fails to capture bpel output
Edited by: soauser on Jan 8, 2012 10:24 AM

When the Worker.State FAILED occurs in a Task?

How to detect that a Worker.State FAILED occurs in a Task? or to say when the Worker.State FAILED occurs in a Task? Is it when an exception happens in the call() method of Task?
Consider the code below:
import java.io.BufferedReader;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.net.URI;
import java.net.URISyntaxException;
import java.net.URL;
import java.net.URLConnection;
import javafx.concurrent.Task;
* Background task to fetch the all classes documentation page from a URL
public class FetchDocListTask extends Task<String> {
private final String docsDirUrl;
public FetchDocListTask(String docsDirUrl) {
this.docsDirUrl = docsDirUrl;
@Override
protected String call() throws Exception {
System.out.println("---- FetchDocListTask docsUrl = " + docsDirUrl);
StringBuilder builder = new StringBuilder();
try {
URI uri = new URI(docsDirUrl + "allclasses-frame.html");
URL url = uri.toURL();
URLConnection urlConnection = url.openConnection();
urlConnection.setConnectTimeout(5000); // set timeout to 5 secs
InputStream in = urlConnection.getInputStream();
BufferedReader reader = new BufferedReader(
new InputStreamReader(in));
String line;
while ((line = reader.readLine()) != null) {
builder.append(line);
builder.append('\n');
reader.close();
} catch (URISyntaxException e) {
e.printStackTrace();
return builder.toString();
When the State.FAILED occurs? In fact, I want to write a code to simply detect whether the computer is connected to the internet. Hope for help~

Yes. If the call() method exits due to an unhandled exception, the state property changes to FAILED. If a return statement is successfully executed, the state property changes to SUCCEEDED. There are no other possibilities.
You can test with something like:
import javafx.application.Application;
    import javafx.concurrent.Task;
    import javafx.concurrent.WorkerStateEvent;
    import javafx.event.EventHandler;
    import javafx.scene.Scene;
    import javafx.scene.control.TextArea;
    import javafx.scene.layout.BorderPane;
    import javafx.stage.Stage;
    public class TaskStateTest extends Application {
        public static void main(String[] args) { launch(args); }
        @Override
        public void start(final Stage primaryStage) {
            Task<Void> exceptionHandlingTask = new Task<Void>() {
                @Override
                protected Void call() throws Exception {
                    try {
                        throw new Exception("Boom");
                    } catch (Exception exc) {
                        System.out.println(exc.getMessage() + " handled");
                    return null;
            Task<Void> exceptionThrowingTask = new Task<Void>() {
                @Override
                protected Void call() throws Exception {
                    throw new Exception("Boom");
        //            return null;
            final BorderPane root = new BorderPane();
            final TextArea textArea = new TextArea();
            root.setCenter(textArea);
            primaryStage.setScene(new Scene(root, 600, 400));
            primaryStage.show();
            registerHandlers(exceptionHandlingTask, "exceptionHandlingTask", textArea);
            registerHandlers(exceptionThrowingTask, "exceptionThrowingTask", textArea);
            Thread t1 = new Thread(exceptionHandlingTask);
            Thread t2 = new Thread(exceptionThrowingTask);
            t1.start();
            t2.start();
        private void registerHandlers(final Task<Void> task, final String msg, final TextArea textArea) {
            task.setOnFailed(new EventHandler<WorkerStateEvent>() {
                @Override
                public void handle(WorkerStateEvent event) {
                    textArea.appendText(msg + " failed\n");
            task.setOnSucceeded(new EventHandler<WorkerStateEvent>() {
                @Override
                public void handle(WorkerStateEvent event) {
                    textArea.appendText(msg + " succeeded\n");

Does NLB also works as fail over?

I have 2 WFEs and Windows NLB. I want to know if NLB also works as fail over i.e. if one of the WFE goes down, will it detect and then never send request to that WFE until it comes back online?
I am asking because I stopped IIS on one of the WFE and now the SharePoint site won't open. Looks like NLB is sending request to that WFE which is down.

I am using Windows NLB and I have come to know that it doesn't check whether IIS on particular server is running or not. It simply checks if the server itself is up and if it is then it sends request even though IIS is down.

JMStudio works with card video capture??

With any webcam its fine!!.
But with my pinnacle card video capture, JMStudio dont see any capture device....To somebody it works to him with any other?
Thanks.

This was answered in another thread:
http://forum.java.sun.com/thread.jspa?threadID=306405&messageID=3957613#3957613

Packages Work, Applications Fail

When deploying a Package everything works normally. When deploying an application it always fails unless the client is located in the primary site boundary.
I see this in the DataTransferService.log repeating over and over:
<![LOG[CDTSJob::HandleErrors: DTS Job ID='{FB8F9F4A-D278-4694-8B8F-3C82A570C148}' URL='http://fws-boi-dc.fws.farweststeel.com:80/SMS_MP' ProtType=1]LOG]!><time="08:20:51.244+420" date="02-23-2015" component="DataTransferService"
context="" type="1" thread="2092" file="dtsjob.cpp:5177">
<![LOG[CDTSJob::HandleErrors: DTS Job ID='{267B9394-27E7-4F5C-A084-889BCFABF7A7}' URL='http://fws-boi-dc.fws.farweststeel.com:80/SMS_MP' ProtType=1]LOG]!><time="08:21:09.012+420" date="02-23-2015" component="DataTransferService"
context="" type="1" thread="3912" file="dtsjob.cpp:5177">
The BITS job is getting a 500 error from the DP. The IIS logs on the DP show no 500 errors, but 200 instead. If I capture the traffic with wireshark I can see the 500 error that BITS is getting as well.
Wireshark Capture:
HEAD /SMS_MP/.sms_dcm?Id&DocumentId=ScopeId_FA5D768E-37EB-4B25-B6BE-B0C0BC93741B/RequiredApplication_760f562a-22e6-4d77-8494-b032ab7f6e55/3/PROPERTIES&Hash=802FCDE2A7B780A5C59A2A9F40ED8450EAF4BEE849EBA67C60706552610F3FE1&Compression=zlib HTTP/1.1
Connection: Keep-Alive
Accept: */*
Accept-Encoding: identity
User-Agent: Microsoft BITS/7.5
Host: fws-boi-dc.fws.farweststeel.com
HTTP/1.1 500 Internal Server Error
Content-Type: text/html
Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
Date: Mon, 23 Feb 2015 15:23:51 GMT
Connection: close

So I got this figured out late last night. There wasn't a CAS log or any app* logs on the remote clients.
When I installed the secondary sites I just let the primary install the SQL, IIS, etc... The secondary sites are also domain controllers.
When I checked the primary site server the SQL log showed all of the secondary sites logging in with a message "Logon Failed for 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Could not find a matching name provided"
The SPNs all looked good, but I created a service account and set SQL to run as the service account at all the sites, then added 'Trust this user for delegation to any service' in the Delegation tab of the user account.
Then I deleted and recreated all the SPNs for all the secondary sites and the Primary to use the new service account. Once that was complete applications are now deploying perfectly.
This one had me going in circles for days, none of the logs really lead me to SQL as the issue, it was just dumb luck that I looked at the SQL logs on the Primary.

Jmstudio failed

Hi! I'm using Debian etch with JMF 2.1.1e.
I've solved some installation problems with AWT, but now I can't execute jmstudio to view my captured device (device has been found with jmfinit).It only says "Aborted" and stops execution.
My Environment variables are :
JAVA_HOME=/opt/jdk1.5.0_07
JMFHOME=/opt/JMF-2.1.1e
CLASSPATH=/opt/JMF-2.1.1e/lib/jmf.jar:.:$CLASSPATH
LD_LIBRARY_PATH=/opt/JMF-2.1.1e/lib:.:$LD_LIBRARY_PATH
export JAVA_HOME JMFHOME CLASSPATH LD_LIBRARY_PATH
Any help ??
Thank you in advance!

Which OS ypo are working on ,
I am also facing some problem with jmstudio(jmf2.1.1e) on linux while it works well on windows.
Regards,
anuja K

TS fails to capture OS when installing updates

Hi
Scenario CM 2012 R2
Deploying a build and capture TS
If it installs updates in the TS the
“Prepare Configuration Manager Client” step fails
If software updates are not set to install it works fine
I am not sure why it fails here?
After the client cache us deleted as part of the
“Prepare Configuration Manager Client” step
Stopped the service 'ccmexec' successfully PrepareSMSClient 17/02/2014 13:52:15 3484 (0x0D9C)
Successfully stopped the client agent service. PrepareSMSClient 17/02/2014 13:52:15 3484 (0x0D9C)
Removing SitePolicy succeeded. PrepareSMSClient 17/02/2014 13:52:15 3484 (0x0D9C)
UnAssigning the SMSClient succeeded PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Successfully opened client certificate store. PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
No certificates to delete PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Deleting Client properties from file C:\WINDOWS\SMSCFG.INI succeeded. PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Reseting the Trusted Root Key successful PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Deleting instance of 'CCM_Client' successful PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Deleting any existing TS execution requests so they are not captured into the image PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Deleting 0 instance(s) of 'CCM_TSExecutionRequest' successful PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Deleting any existing maintenance tasks so they are not captured into the image PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Deleting 1 instance(s) of 'SMS_MaintenanceTaskRequests' successful PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Successfully reset Registration status flag to "not registered" PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Successfully disabled provisioning mode. PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
Start to cleanup TS policy PrepareSMSClient 17/02/2014 13:52:16 3484 (0x0D9C)
getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,463) PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,3666) PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
End TS policy cleanup PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,564) PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
Failed to delete policies compiled by TaskSequence (0xffffffff) PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
Failed to prepare SMS Client for capture, hr=ffffffff PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136) PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
Failed to prepare SMS Client for capture, hr=ffffffff PrepareSMSClient 17/02/2014 13:57:25 3484 (0x0D9C)
Process completed with exit code 4294967295 TSManager 17/02/2014 13:57:25 732 (0x02DC)
!--------------------------------------------------------------------------------------------! TSManager 17/02/2014 13:57:25 732 (0x02DC)
Failed to run the action: Prepare Configuration Manager Client.
Unknown error (Error: FFFFFFFF; Source: Unknown) TSManager 17/02/2014 13:57:25 732 (0x02DC)
Thanks

Hi!
This issue occurs if the machine has approx. or more than 65.000 Software Updates polices assigned to the machine. The "Prepare Configuration Manager Client" step in the TS will then fail.
To work around this issue, simply use below example "PowerShell script" and run it as a step before "Prepare ConfigMgr Client" in the Build Capture TS. The script will clean-up WMI correctly and the "Prepare ConfigMgr Client" will
run.
This is how the script works!
1. First the script Counts the number of "Software Updates Polices" assigned to the machine and logs this to the log file in CCM Logs Directory.
2. The script then tries to remove the "Software Updates Polices". It will fail to delete all polices.
3. By re-runing these steps, we will sucessfully be able to remove all Software Updates polices.
$Policy = @(Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'"))
$policy.Count | Out-File $Env:WinDir\CCM\Logs\OSD_PrePareConfigMgrClient.log -Append
Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'") | Remove-WmiObject
$RemainingPolicy = @(Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'"))
$RemainingPolicy.Count | Out-File $Env:WinDir\CCM\Logs\OSD_PrePareConfigMgrClient.log –Append
Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'") | Remove-WmiObject
$RemainingPolicy = @(Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'"))
$RemainingPolicy.Count | Out-File $Env:WinDir\CCM\Logs\OSD_PrePareConfigMgrClient.log –Append
Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'") | Remove-WmiObject
$RemainingPolicy = @(Get-WMIObject -Namespace root\ccm\policy\DefaultMachine\RequestedConfig -query("Select * from ccm_policy where PolicySource='ccmtasksequence'"))
$RemainingPolicy.Count | Out-File $Env:WinDir\CCM\Logs\OSD_PrePareConfigMgrClient.log –Append
Use it for what it is worthr, it resolved my issue :)
PS! This has been reported to Microsoft Premier Support.
Best Regards Anders Horgen

PDF-to-PDF link works online, fails on CD

We publish multi-part PDF docs on the web and on CD. Inside them are occasional placeholder pages for large maps, with the text CLICK HERE TO VIEW linked to an external file, also a PDF. We make the links with AA's Link tool. (Draw a rectangle around the text, Open File, browse to the map file, etc., you know the drill.) We’ve done this for years, but recently:
- Clicking the link from the local file finds the map just fine.
- Posting the doc and map to the web, opening the doc online (IE), and clicking the link in it for the map works fine.
- Burning the webpage, doc, and map to a CD in the exact same configuration puts up a Security Warning box when we click the map’s link inside the document. The box says the doc is trying to connect to [map's path (correct path)] and offers responses of Help, Allow, or Block. Clicking the obvious ‘Allow’ has no effect!
The CD setup has worked fine for years but now suddenly fails. Is there some parameter in IE that's wound too tight?
I've posted a sample of how it works. To see it, open the first doc linked on http://www.speakeasy.org/~mtangard/test/example.htm and click the red CLICK HERE.. link on page 5 or page 7.
Using Acrobat 9 Pro and IE 8.0.6. Grateful for any clues....
Mark

Dump the web page.
For deployment of PDF collections on optical storage media (OSM) avoid "entry" to the collection(s) from an HTML file on the OSM.
Rather, always provide a "start" PDF that is on the root of the OSM.
This avoids having to rely on the end-user's browser or browser version or one software house's updates gobbering another house's application.
Provided the PDFs are not PDF Packages, Acrobat 9 Portfolios, or Acrobat X Portfolios end-users with Adobe Reader / Acrobat back to version 5.x can use the PDFs in a reliable manner.
n.b., if a Cataloged Index or tiered indices are utilized users of version 5.x are 'locked out' as the licensed search engine/index builder was changed in version 6.x
Create a staging "burn zone" on a local machine's HDD.
Identified the common "parent" directory/folder that exists on the web deployment.
At the provided web space example this would be directory/folder "fier".
--| feir
.... file: exec_summ.pdf
.... --| figs
.... .... file: fig_es-1.pdf
~
~
When a link path traverses through directories/folders on its passage to a target file this very specific "path" must be maintained when a file collection is transfered.
True for a transfer of files to other web space, network space, other local machines, USB device, or OSM (any format - PDF, HTML, whatever).
~
~
So, with the parent "feir" and its child content present in the 'burn zone' what goes to OSM will contain functional links.
A Windows autorun file on the OSM root affords the possibility of calling Adobe Reader from the local machine to render the "start" PDF.
If, for the PDFs in the 'burn zone, a Catalog Index has been created then associate the PDX file to the 'start' PDF.
With it all on an OSM, the user has a mounted PDX as soon as the 'start' PDF is opened. This supports "anytime" use of Advanced Search.
n.b., newer releases of Acrobat / Adobe Reader can be expected to provide a security dialog when the PDX is accessed.
Be well...

Can't get NVIDIA/Intel Optimus (Dell XPS 15) to work, startx fails.

I have an up to date Arch and am working from a clean install. I'm trying to run X using NVIDIA only, as outlined here: https://wiki.archlinux.org/index.php/NV … ing_nvidia . I don't want to use bumblebee unless this just can't work.
The text that comes after a failed startx seems relevant, aswell as the dmesg. The only thing that seems off to me in the xorg log is:
[ 184.863] (EE) Screen 1 deleted because of no matching config section.
[ 184.863] (II) UnloadModule: "modesetting"
and
[ 189.571] (EE) NVIDIA(0): Failed to initiate mode change.
[ 189.571] (EE) NVIDIA(0): Failed to complete mode change
I've also add rcutree.rcu_idle_gp_delay=1 to /boot/syslinux/syslinux.cfg , if I don't do that the xorg log says that NVIDIA "fails to initialize".
I've also executed "systemctl start acpid.service" so I don't get ACPI errors in the xorg log file.
I don't think I have the intel drivers installed, don't think I need them, but I installed the xf86 modesetting driver.
Anyway here are my relevant logs and config files:
The last line that comes after a failed startx is:
waiting for X server to shut down .(EE) Server terminated successfully (0). Closing log file. out foradjust shatters 0 3200need to create shared pixmap 1xinit: connection to X server lost
My xorg.conf looks like this:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 337.19 (buildmeister@swio-display-x64-rhel04-03) Tue Apr 29 20:34:50 PDT 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "nvidia"
Inactive "intel"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
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 "Unknown"
# HorizSync 28.0 - 33.0
# VertRefresh 43.0 - 72.0
# Option "DPMS"
#EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:2:0:0"
VendorName "NVIDIA Corporation"
EndSection
Section "Device"
Identifier "intel"
Driver "modesetting"
# BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "nvidia"
Device "nvidia"
Option "UseDisplayDevice" "none"
# Option "AllowEmptyInitialConfiguration" "true"
# Monitor "Monitor0"
# DefaultDepth 24
# SubSection "Display"
# Depth 24
# EndSubSection
EndSection
Section "Screen"
Identifier "intel"
Device "intel"
EndSection
And here is the xorg log and dmesg output:
dmesg:
[ 185.077229] vgaarb: this pci device is not a vga device
[ 185.079025] nvidia 0000:02:00.0: irq 54 for MSI/MSI-X
[ 185.099233] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099382] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099467] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099545] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099620] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099694] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099814] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 185.099890] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 188.096884] ACPI Error: Field [TMPB] at 282624 exceeds Buffer [ROM1] size 262144 (bits) (20131218/dsopcode-236)
[ 188.096900] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP._ROM] (Node ffff88041f07ded8), AE_AML_BUFFER_LIMIT (20131218/psparse-536)
[ 188.111328] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 189.778474] vgaarb: this pci device is not a vga device
Xorg.0.log:
[ 184.732]
X.Org X Server 1.15.1
Release Date: 2014-04-13
[ 184.732] X Protocol Version 11, Revision 0
[ 184.732] Build Operating System: Linux 3.14.0-4-ARCH x86_64
[ 184.732] Current Operating System: Linux BASE 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
[ 184.732] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sdb1 rw rcutree.rcu_idle_gp_delay=1 initrd=../initramfs-linux.img
[ 184.732] Build Date: 14 April 2014 08:39:09AM
[ 184.732]
[ 184.733] Current version of pixman: 0.32.4
[ 184.733] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 184.733] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 184.733] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 27 21:10:17 2014
[ 184.735] (==) Using config file: "/etc/X11/xorg.conf"
[ 184.735] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 184.737] (==) ServerLayout "Layout0"
[ 184.737] (**) |-->Screen "nvidia" (0)
[ 184.737] (**) | |-->Monitor "<default monitor>"
[ 184.737] (**) | |-->Device "nvidia"
[ 184.737] (==) No monitor specified for screen "nvidia".
Using a default monitor configuration.
[ 184.737] (**) |-->Inactive Device "intel"
[ 184.737] (**) |-->Input Device "Keyboard0"
[ 184.737] (**) |-->Input Device "Mouse0"
[ 184.737] (==) Automatically adding devices
[ 184.737] (==) Automatically enabling devices
[ 184.737] (==) Automatically adding GPU devices
[ 184.744] (==) 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/
[ 184.744] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 184.744] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 184.744] (WW) Disabling Keyboard0
[ 184.744] (WW) Disabling Mouse0
[ 184.744] (II) Loader magic: 0x804c80
[ 184.744] (II) Module ABI versions:
[ 184.744] X.Org ANSI C Emulation: 0.4
[ 184.744] X.Org Video Driver: 15.0
[ 184.744] X.Org XInput driver : 20.0
[ 184.744] X.Org Server Extension : 8.0
[ 184.744] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 184.744] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 184.747] (--) PCI:*(0:0:2:0) 8086:0416:1028:05fe rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 184.747] (--) PCI: (0:2:0:0) 10de:0fe4:1028:05fe rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 184.748] (II) Open ACPI successful (/var/run/acpid.socket)
[ 184.748] Initializing built-in extension Generic Event Extension
[ 184.748] Initializing built-in extension SHAPE
[ 184.748] Initializing built-in extension MIT-SHM
[ 184.748] Initializing built-in extension XInputExtension
[ 184.748] Initializing built-in extension XTEST
[ 184.748] Initializing built-in extension BIG-REQUESTS
[ 184.748] Initializing built-in extension SYNC
[ 184.748] Initializing built-in extension XKEYBOARD
[ 184.748] Initializing built-in extension XC-MISC
[ 184.749] Initializing built-in extension SECURITY
[ 184.749] Initializing built-in extension XINERAMA
[ 184.749] Initializing built-in extension XFIXES
[ 184.749] Initializing built-in extension RENDER
[ 184.749] Initializing built-in extension RANDR
[ 184.749] Initializing built-in extension COMPOSITE
[ 184.749] Initializing built-in extension DAMAGE
[ 184.749] Initializing built-in extension MIT-SCREEN-SAVER
[ 184.749] Initializing built-in extension DOUBLE-BUFFER
[ 184.749] Initializing built-in extension RECORD
[ 184.749] Initializing built-in extension DPMS
[ 184.749] Initializing built-in extension Present
[ 184.749] Initializing built-in extension DRI3
[ 184.749] Initializing built-in extension X-Resource
[ 184.749] Initializing built-in extension XVideo
[ 184.750] Initializing built-in extension XVideo-MotionCompensation
[ 184.750] Initializing built-in extension XFree86-VidModeExtension
[ 184.750] Initializing built-in extension XFree86-DGA
[ 184.750] Initializing built-in extension XFree86-DRI
[ 184.750] Initializing built-in extension DRI2
[ 184.750] (II) LoadModule: "glx"
[ 184.754] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 184.846] (II) Module glx: vendor="NVIDIA Corporation"
[ 184.846] compiled for 4.0.2, module version = 1.0.0
[ 184.846] Module class: X.Org Server Extension
[ 184.846] (II) NVIDIA GLX Module 337.19 Tue Apr 29 19:48:33 PDT 2014
[ 184.846] Loading extension GLX
[ 184.846] (II) LoadModule: "nvidia"
[ 184.847] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 184.854] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 184.854] compiled for 4.0.2, module version = 1.0.0
[ 184.854] Module class: X.Org Video Driver
[ 184.855] (II) LoadModule: "modesetting"
[ 184.855] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 184.856] (II) Module modesetting: vendor="X.Org Foundation"
[ 184.856] compiled for 1.15.0, module version = 0.8.1
[ 184.856] Module class: X.Org Video Driver
[ 184.856] ABI class: X.Org Video Driver, version 15.0
[ 184.856] (II) NVIDIA dlloader X Driver 337.19 Tue Apr 29 19:22:36 PDT 2014
[ 184.856] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 184.856] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 184.856] (++) using VT number 1
[ 184.857] (II) Loading sub module "fb"
[ 184.858] (II) LoadModule: "fb"
[ 184.858] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 184.859] (II) Module fb: vendor="X.Org Foundation"
[ 184.859] compiled for 1.15.1, module version = 1.0.0
[ 184.859] ABI class: X.Org ANSI C Emulation, version 0.4
[ 184.859] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 184.859] (II) Loading sub module "wfb"
[ 184.859] (II) LoadModule: "wfb"
[ 184.859] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 184.861] (II) Module wfb: vendor="X.Org Foundation"
[ 184.861] compiled for 1.15.1, module version = 1.0.0
[ 184.861] ABI class: X.Org ANSI C Emulation, version 0.4
[ 184.861] (II) Loading sub module "ramdac"
[ 184.861] (II) LoadModule: "ramdac"
[ 184.861] (II) Module "ramdac" already built-in
[ 184.863] (II) modesetting(1): using drv /dev/dri/card0
[ 184.863] (II) modesetting(G0): using drv /dev/dri/card0
[ 184.863] (EE) Screen 1 deleted because of no matching config section.
[ 184.863] (II) UnloadModule: "modesetting"
[ 184.863] (II) NVIDIA(0): Creating default Display subsection in Screen section
"nvidia" for depth/fbbpp 24/32
[ 184.863] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 184.863] (==) NVIDIA(0): RGB weight 888
[ 184.863] (==) NVIDIA(0): Default visual is TrueColor
[ 184.863] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 184.863] (**) NVIDIA(0): Option "UseDisplayDevice" "none"
[ 184.863] (**) NVIDIA(0): Enabling 2D acceleration
[ 184.864] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; enabling NoScanout
[ 184.864] (**) NVIDIA(0): mode
[ 188.491] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 188.494] (II) NVIDIA(0): NVIDIA GPU GeForce GT 750M (GK107) at PCI:2:0:0 (GPU-0)
[ 188.494] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 188.494] (--) NVIDIA(0): VideoBIOS: 80.07.b3.00.10
[ 188.494] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 188.494] (--) NVIDIA(0): Valid display device(s) on GeForce GT 750M at PCI:2:0:0
[ 188.494] (--) NVIDIA(0): none
[ 188.494] (II) NVIDIA(0): Validated MetaModes:
[ 188.494] (II) NVIDIA(0): "NULL"
[ 188.494] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[ 188.494] (WW) NVIDIA(0): Unable to get display device for DPI computation.
[ 188.494] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[ 188.495] (==) modesetting(G0): Depth 24, (==) framebuffer bpp 32
[ 188.495] (==) modesetting(G0): RGB weight 888
[ 188.495] (==) modesetting(G0): Default visual is TrueColor
[ 188.495] (II) modesetting(G0): ShadowFB: preferred YES, enabled YES
[ 188.495] (II) modesetting(G0): Output eDP-1-0 has no monitor section
[ 188.520] (II) modesetting(G0): Output VGA-1-0 has no monitor section
[ 188.520] (II) modesetting(G0): Output HDMI-1-0 has no monitor section
[ 188.520] (II) modesetting(G0): Output DisplayPort-1-0 has no monitor section
[ 188.521] (II) modesetting(G0): Output HDMI-1-1 has no monitor section
[ 188.521] (II) modesetting(G0): EDID for output eDP-1-0
[ 188.521] (II) modesetting(G0): Manufacturer: SHP Model: 13f8 Serial#: 0
[ 188.521] (II) modesetting(G0): Year: 2013 Week: 34
[ 188.521] (II) modesetting(G0): EDID Version: 1.4
[ 188.521] (II) modesetting(G0): Digital Display Input
[ 188.521] (II) modesetting(G0): 8 bits per channel
[ 188.521] (II) modesetting(G0): Digital interface is DisplayPort
[ 188.521] (II) modesetting(G0): Max Image Size [cm]: horiz.: 35 vert.: 19
[ 188.521] (II) modesetting(G0): Gamma: 2.20
[ 188.521] (II) modesetting(G0): No DPMS capabilities specified
[ 188.521] (II) modesetting(G0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 188.521] (II) modesetting(G0): Default color space is primary color space
[ 188.521] (II) modesetting(G0): First detailed timing is preferred mode
[ 188.521] (II) modesetting(G0): Preferred mode is native pixel format and refresh rate
[ 188.521] (II) modesetting(G0): redX: 0.640 redY: 0.329 greenX: 0.300 greenY: 0.600
[ 188.521] (II) modesetting(G0): blueX: 0.149 blueY: 0.060 whiteX: 0.312 whiteY: 0.328
[ 188.521] (II) modesetting(G0): Manufacturer's mask: 0
[ 188.521] (II) modesetting(G0): Supported detailed timing:
[ 188.521] (II) modesetting(G0): clock: 373.2 MHz Image Size: 346 x 194 mm
[ 188.522] (II) modesetting(G0): h_active: 3200 h_sync: 3248 h_sync_end 3280 h_blank_end 3360 h_border: 0
[ 188.522] (II) modesetting(G0): v_active: 1800 v_sync: 1803 v_sync_end 1808 v_blanking: 1852 v_border: 0
[ 188.522] (II) modesetting(G0): 6RGW0\80LQ156Z1
[ 188.522] (II) modesetting(G0): Unknown vendor-specific block 0
[ 188.522] (II) modesetting(G0): EDID (in hex):
[ 188.522] (II) modesetting(G0): 00ffffffffffff004d10f81300000000
[ 188.522] (II) modesetting(G0): 22170104a52313780ede50a3544c9926
[ 188.522] (II) modesetting(G0): 0f505400000001010101010101010101
[ 188.522] (II) modesetting(G0): 010101010101cd9180a0c00834703020
[ 188.522] (II) modesetting(G0): 35005ac2100000180000001000000000
[ 188.522] (II) modesetting(G0): 00000000000000000000000000fe0036
[ 188.522] (II) modesetting(G0): 52475730804c513135365a3100000000
[ 188.522] (II) modesetting(G0): 0002010328001200000b010a2020001b
[ 188.522] (II) modesetting(G0): Printing probed modes for output eDP-1-0
[ 188.522] (II) modesetting(G0): Modeline "3200x1800"x60.0 373.25 3200 3248 3280 3360 1800 1803 1808 1852 -hsync -vsync (111.1 kHz eP)
[ 188.522] (II) modesetting(G0): Modeline "2048x1536"x60.0 266.95 2048 2200 2424 2800 1536 1537 1540 1589 -hsync +vsync (95.3 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1856x1392"x60.0 218.30 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.4 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1792x1344"x60.0 204.80 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.7 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1024x768"x120.1 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "960x720"x120.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "928x696"x120.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "896x672"x120.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "800x600"x120.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "700x525"x120.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "640x512"x120.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "640x480"x120.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "512x384"x120.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "400x300"x120.6 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "400x300"x112.7 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[ 188.522] (II) modesetting(G0): Modeline "320x240"x120.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[ 188.546] (II) modesetting(G0): EDID for output VGA-1-0
[ 188.547] (II) modesetting(G0): EDID for output HDMI-1-0
[ 188.547] (II) modesetting(G0): EDID for output DisplayPort-1-0
[ 188.547] (II) modesetting(G0): EDID for output HDMI-1-1
[ 188.547] (II) modesetting(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 188.548] (==) modesetting(G0): DPI set to (96, 96)
[ 188.548] (II) Loading sub module "fb"
[ 188.548] (II) LoadModule: "fb"
[ 188.548] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 188.548] (II) Module fb: vendor="X.Org Foundation"
[ 188.548] compiled for 1.15.1, module version = 1.0.0
[ 188.548] ABI class: X.Org ANSI C Emulation, version 0.4
[ 188.548] (II) Loading sub module "shadow"
[ 188.548] (II) LoadModule: "shadow"
[ 188.548] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 188.549] (II) Module shadow: vendor="X.Org Foundation"
[ 188.549] compiled for 1.15.1, module version = 1.1.0
[ 188.549] ABI class: X.Org ANSI C Emulation, version 0.4
[ 188.549] (--) Depth 24 pixmap format is 32 bpp
[ 188.551] (==) modesetting(G0): Backing store enabled
[ 188.551] (==) modesetting(G0): Silken mouse enabled
[ 188.551] (II) modesetting(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 188.551] (==) modesetting(G0): DPMS enabled
[ 188.551] (WW) modesetting(G0): Option "UseDisplayDevice" is not used
[ 189.560] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 189.560] (II) NVIDIA: access.
[ 189.571] (II) NVIDIA(0): Setting mode "NULL"
[ 189.571] (EE) NVIDIA(0): Failed to initiate mode change.
[ 189.571] (EE) NVIDIA(0): Failed to complete mode change
[ 189.604] (II) NVIDIA(0): Built-in logo is bigger than the screen.
[ 189.604] Loading extension NV-GLX
[ 189.617] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 189.617] (==) NVIDIA(0): Backing store enabled
[ 189.617] (==) NVIDIA(0): Silken mouse enabled
[ 189.617] (==) NVIDIA(0): DPMS enabled
[ 189.618] Loading extension NV-CONTROL
[ 189.619] (II) Loading sub module "dri2"
[ 189.619] (II) LoadModule: "dri2"
[ 189.619] (II) Module "dri2" already built-in
[ 189.619] (II) NVIDIA(0): [DRI2] Setup complete
[ 189.619] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 189.619] (--) RandR disabled
[ 189.642] (II) Initializing extension GLX
[ 189.644] (II) modesetting(G0): Damage tracking initialized
[ 189.985] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 189.985] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 189.985] (II) LoadModule: "evdev"
[ 189.986] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 189.989] (II) Module evdev: vendor="X.Org Foundation"
[ 189.989] compiled for 1.15.1, module version = 2.9.0
[ 189.989] Module class: X.Org XInput Driver
[ 189.989] ABI class: X.Org XInput driver, version 20.0
[ 189.989] (II) Using input driver 'evdev' for 'Power Button'
[ 189.989] (**) Power Button: always reports core events
[ 189.989] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 189.989] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 189.989] (--) evdev: Power Button: Found keys
[ 189.989] (II) evdev: Power Button: Configuring as keyboard
[ 189.989] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
[ 189.989] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 189.989] (**) Option "xkb_rules" "evdev"
[ 189.989] (**) Option "xkb_model" "pc104"
[ 189.989] (**) Option "xkb_layout" "us"
[ 190.041] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[ 190.041] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 190.041] (II) Using input driver 'evdev' for 'Video Bus'
[ 190.041] (**) Video Bus: always reports core events
[ 190.041] (**) evdev: Video Bus: Device: "/dev/input/event10"
[ 190.041] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 190.041] (--) evdev: Video Bus: Found keys
[ 190.041] (II) evdev: Video Bus: Configuring as keyboard
[ 190.041] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input11/event10"
[ 190.041] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 190.041] (**) Option "xkb_rules" "evdev"
[ 190.041] (**) Option "xkb_model" "pc104"
[ 190.041] (**) Option "xkb_layout" "us"
[ 190.042] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 190.042] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 190.042] (II) Using input driver 'evdev' for 'Video Bus'
[ 190.042] (**) Video Bus: always reports core events
[ 190.042] (**) evdev: Video Bus: Device: "/dev/input/event9"
[ 190.043] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 190.043] (--) evdev: Video Bus: Found keys
[ 190.043] (II) evdev: Video Bus: Configuring as keyboard
[ 190.043] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:4e/LNXVIDEO:00/input/input10/event9"
[ 190.043] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 190.043] (**) Option "xkb_rules" "evdev"
[ 190.043] (**) Option "xkb_model" "pc104"
[ 190.043] (**) Option "xkb_layout" "us"
[ 190.044] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 190.044] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 190.044] (II) Using input driver 'evdev' for 'Power Button'
[ 190.044] (**) Power Button: always reports core events
[ 190.044] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 190.044] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 190.044] (--) evdev: Power Button: Found keys
[ 190.044] (II) evdev: Power Button: Configuring as keyboard
[ 190.044] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event1"
[ 190.044] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
[ 190.044] (**) Option "xkb_rules" "evdev"
[ 190.044] (**) Option "xkb_model" "pc104"
[ 190.044] (**) Option "xkb_layout" "us"
[ 190.045] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 190.046] (II) No input driver specified, ignoring this device.
[ 190.046] (II) This device may have been added with another device file.
[ 190.046] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 190.046] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 190.047] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event13)
[ 190.047] (II) No input driver specified, ignoring this device.
[ 190.047] (II) This device may have been added with another device file.
[ 190.047] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event12)
[ 190.047] (II) No input driver specified, ignoring this device.
[ 190.047] (II) This device may have been added with another device file.
[ 190.048] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event11)
[ 190.048] (II) No input driver specified, ignoring this device.
[ 190.048] (II) This device may have been added with another device file.
[ 190.048] (II) config/udev: Adding input device Integrated_Webcam_HD (/dev/input/event15)
[ 190.048] (**) Integrated_Webcam_HD: Applying InputClass "evdev keyboard catchall"
[ 190.048] (II) Using input driver 'evdev' for 'Integrated_Webcam_HD'
[ 190.049] (**) Integrated_Webcam_HD: always reports core events
[ 190.049] (**) evdev: Integrated_Webcam_HD: Device: "/dev/input/event15"
[ 190.049] (--) evdev: Integrated_Webcam_HD: Vendor 0xbda Product 0x573c
[ 190.049] (--) evdev: Integrated_Webcam_HD: Found keys
[ 190.049] (II) evdev: Integrated_Webcam_HD: Configuring as keyboard
[ 190.049] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11:1.0/input/input17/event15"
[ 190.049] (II) XINPUT: Adding extended input device "Integrated_Webcam_HD" (type: KEYBOARD, id 10)
[ 190.049] (**) Option "xkb_rules" "evdev"
[ 190.049] (**) Option "xkb_model" "pc104"
[ 190.049] (**) Option "xkb_layout" "us"
[ 190.050] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:101b (/dev/input/event16)
[ 190.050] (**) Logitech Unifying Device. Wireless PID:101b: Applying InputClass "evdev pointer catchall"
[ 190.050] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:101b'
[ 190.050] (**) Logitech Unifying Device. Wireless PID:101b: always reports core events
[ 190.050] (**) evdev: Logitech Unifying Device. Wireless PID:101b: Device: "/dev/input/event16"
[ 190.050] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Vendor 0x46d Product 0xc52b
[ 190.051] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found 20 mouse buttons
[ 190.051] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found scroll wheel(s)
[ 190.051] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found relative axes
[ 190.051] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found x and y relative axes
[ 190.051] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Configuring as mouse
[ 190.051] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Adding scrollwheel support
[ 190.051] (**) evdev: Logitech Unifying Device. Wireless PID:101b: YAxisMapping: buttons 4 and 5
[ 190.051] (**) evdev: Logitech Unifying Device. Wireless PID:101b: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 190.051] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0005/input/input18/event16"
[ 190.051] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:101b" (type: MOUSE, id 11)
[ 190.051] (II) evdev: Logitech Unifying Device. Wireless PID:101b: initialized for relative axes.
[ 190.051] (**) Logitech Unifying Device. Wireless PID:101b: (accel) keeping acceleration scheme 1
[ 190.052] (**) Logitech Unifying Device. Wireless PID:101b: (accel) acceleration profile 0
[ 190.052] (**) Logitech Unifying Device. Wireless PID:101b: (accel) acceleration factor: 2.000
[ 190.052] (**) Logitech Unifying Device. Wireless PID:101b: (accel) acceleration threshold: 4
[ 190.052] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:101b (/dev/input/mouse2)
[ 190.052] (II) No input driver specified, ignoring this device.
[ 190.052] (II) This device may have been added with another device file.
[ 190.053] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2008 (/dev/input/event17)
[ 190.053] (**) Logitech Unifying Device. Wireless PID:2008: Applying InputClass "evdev keyboard catchall"
[ 190.053] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2008'
[ 190.053] (**) Logitech Unifying Device. Wireless PID:2008: always reports core events
[ 190.054] (**) evdev: Logitech Unifying Device. Wireless PID:2008: Device: "/dev/input/event17"
[ 190.054] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Vendor 0x46d Product 0xc52b
[ 190.054] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found 1 mouse buttons
[ 190.054] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found scroll wheel(s)
[ 190.054] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found relative axes
[ 190.054] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing relative x/y axes to exist.
[ 190.054] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found absolute axes
[ 190.054] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing absolute x/y axes to exist.
[ 190.054] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found keys
[ 190.054] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Configuring as mouse
[ 190.054] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Configuring as keyboard
[ 190.054] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Adding scrollwheel support
[ 190.054] (**) evdev: Logitech Unifying Device. Wireless PID:2008: YAxisMapping: buttons 4 and 5
[ 190.054] (**) evdev: Logitech Unifying Device. Wireless PID:2008: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 190.054] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0006/input/input19/event17"
[ 190.054] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2008" (type: KEYBOARD, id 12)
[ 190.054] (**) Option "xkb_rules" "evdev"
[ 190.054] (**) Option "xkb_model" "pc104"
[ 190.054] (**) Option "xkb_layout" "us"
[ 190.055] (II) evdev: Logitech Unifying Device. Wireless PID:2008: initialized for relative axes.
[ 190.055] (WW) evdev: Logitech Unifying Device. Wireless PID:2008: ignoring absolute axes.
[ 190.055] (**) Logitech Unifying Device. Wireless PID:2008: (accel) keeping acceleration scheme 1
[ 190.055] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration profile 0
[ 190.055] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration factor: 2.000
[ 190.055] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration threshold: 4
[ 190.056] (II) config/udev: Adding input device SYNAPTICS Synaptics Large Touch Screen (/dev/input/event14)
[ 190.056] (**) SYNAPTICS Synaptics Large Touch Screen: Applying InputClass "evdev touchscreen catchall"
[ 190.056] (II) Using input driver 'evdev' for 'SYNAPTICS Synaptics Large Touch Screen'
[ 190.056] (**) SYNAPTICS Synaptics Large Touch Screen: always reports core events
[ 190.056] (**) evdev: SYNAPTICS Synaptics Large Touch Screen: Device: "/dev/input/event14"
[ 190.056] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Vendor 0x6cb Product 0xac3
[ 190.056] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found absolute axes
[ 190.056] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found absolute multitouch axes
[ 190.057] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: No buttons found, faking one.
[ 190.057] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found x and y absolute axes
[ 190.057] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found absolute touchscreen
[ 190.057] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: Configuring as touchscreen
[ 190.057] (**) evdev: SYNAPTICS Synaptics Large Touch Screen: YAxisMapping: buttons 4 and 5
[ 190.057] (**) evdev: SYNAPTICS Synaptics Large Touch Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 190.057] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/0003:06CB:0AC3.0004/input/input15/event14"
[ 190.057] (II) XINPUT: Adding extended input device "SYNAPTICS Synaptics Large Touch Screen" (type: TOUCHSCREEN, id 13)
[ 190.057] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: initialized for absolute axes.
[ 190.057] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) keeping acceleration scheme 1
[ 190.057] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) acceleration profile 0
[ 190.057] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) acceleration factor: 2.000
[ 190.057] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) acceleration threshold: 4
[ 190.058] (II) config/udev: Adding input device SYNAPTICS Synaptics Large Touch Screen (/dev/input/mouse1)
[ 190.058] (II) No input driver specified, ignoring this device.
[ 190.058] (II) This device may have been added with another device file.
[ 190.059] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event5)
[ 190.059] (II) No input driver specified, ignoring this device.
[ 190.059] (II) This device may have been added with another device file.
[ 190.059] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event6)
[ 190.059] (II) No input driver specified, ignoring this device.
[ 190.059] (II) This device may have been added with another device file.
[ 190.060] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 190.060] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 190.060] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 190.060] (**) AT Translated Set 2 keyboard: always reports core events
[ 190.060] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 190.060] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 190.060] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 190.060] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 190.060] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 190.060] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
[ 190.060] (**) Option "xkb_rules" "evdev"
[ 190.060] (**) Option "xkb_model" "pc104"
[ 190.061] (**) Option "xkb_layout" "us"
[ 190.062] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
[ 190.062] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 190.062] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 190.062] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 190.062] (II) LoadModule: "synaptics"
[ 190.062] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 190.063] (II) Module synaptics: vendor="X.Org Foundation"
[ 190.063] compiled for 1.15.1, module version = 1.8.0
[ 190.063] Module class: X.Org XInput Driver
[ 190.063] ABI class: X.Org XInput driver, version 20.0
[ 190.063] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 190.063] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 190.063] (**) Option "Device" "/dev/input/event8"
[ 190.123] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5660 (res 42)
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4646 (res 44)
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 190.123] (**) Option "TapButton1" "1"
[ 190.123] (**) Option "TapButton2" "2"
[ 190.123] (**) Option "TapButton3" "3"
[ 190.123] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 190.123] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 190.123] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 190.150] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input6/event8"
[ 190.150] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 15)
[ 190.150] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 190.150] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 190.150] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 190.150] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 190.150] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 190.150] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 190.150] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 190.150] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 190.151] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 190.151] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 190.151] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 190.151] (II) No input driver specified, ignoring this device.
[ 190.151] (II) This device may have been added with another device file.
[ 190.152] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event7)
[ 190.152] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 190.152] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[ 190.152] (**) Dell WMI hotkeys: always reports core events
[ 190.152] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event7"
[ 190.152] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[ 190.152] (--) evdev: Dell WMI hotkeys: Found keys
[ 190.152] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[ 190.152] (**) Option "config_info" "udev:/sys/devices/virtual/input/input9/event7"
[ 190.152] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 16)
[ 190.152] (**) Option "xkb_rules" "evdev"
[ 190.152] (**) Option "xkb_model" "pc104"
[ 190.152] (**) Option "xkb_layout" "us"
[ 190.272] (II) modesetting(G0): EDID vendor "SHP", prod id 5112
[ 190.272] (II) modesetting(G0): Printing DDC gathered Modelines:
[ 190.272] (II) modesetting(G0): Modeline "3200x1800"x0.0 373.25 3200 3248 3280 3360 1800 1803 1808 1852 -hsync -vsync (111.1 kHz eP)
[ 190.297] reporting 3 5 25 194
[ 190.349] have a master to look out for
[ 190.349] adjust shatters 0 3200
[ 190.362] need to create shared pixmap 1(II) evdev: Dell WMI hotkeys: Close
[ 191.968] (II) UnloadModule: "evdev"
[ 191.968] (II) UnloadModule: "synaptics"
[ 191.968] (II) evdev: AT Translated Set 2 keyboard: Close
[ 191.968] (II) UnloadModule: "evdev"
[ 191.968] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: Close
[ 191.968] (II) UnloadModule: "evdev"
[ 191.968] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Close
[ 191.968] (II) UnloadModule: "evdev"
[ 191.969] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Close
[ 191.969] (II) UnloadModule: "evdev"
[ 191.969] (II) evdev: Integrated_Webcam_HD: Close
[ 191.969] (II) UnloadModule: "evdev"
[ 191.969] (II) evdev: Power Button: Close
[ 191.969] (II) UnloadModule: "evdev"
[ 191.969] (II) evdev: Video Bus: Close
[ 191.969] (II) UnloadModule: "evdev"
[ 191.969] (II) evdev: Video Bus: Close
[ 191.969] (II) UnloadModule: "evdev"
[ 191.969] (II) evdev: Power Button: Close
[ 191.969] (II) UnloadModule: "evdev"
[ 192.058] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 192.486] (EE) Server terminated successfully (0). Closing log file.
--Edit--
Forget to mention that I also have this in my .xinitrc file:
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
Last edited by gautamadude (2014-05-27 22:01:39)

I cant get my T530 to boot on the discrete graphics card either (Nvidia) unless I add (EDIT: to the kernel boot line in grub.cfg):
noapic
Note that I did NOT write noacpi, but noapic. See this thread:
https://bbs.archlinux.org/viewtopic.php?id=175672
**EDIT2** Actually, you might try noacpi and noapic, and then both at the same time considering your mention of acpi in your OP.
Last edited by GSF1200S (2014-05-29 17:08:07)

LEAP wireless clients work, then fail, Using WISM blades HELP

I am at a complete loss. Calls to Cisco, working with different vendors, nothing has worked to solve the problem. This is what we see, and we see this at every single one of our hospital sites.
All hospitals used to run just IOS code on their AP's. Some hospitals used the older 1200 series AP's, which have been upgraded from B only radios to A/B/G. Some hospitals were rolled out with newer 1240 series AP's. Every single hospital was just fine when using IOS code on the AP's. Users never disconnected or disassociated. They were fine. Clients run a mixture of the old Cisco 350 series cards, or Ubiquiti A/B/G cards.
Now, fast forward and we started installing WISM blades in all the 6509 distribution switches at each hospital. AP's were then upgraded to lightweight code and at first everything seemed great. Then the calls started.
All clients at all hospitals will just disassociate. It is completely random. Some machines can see it once, others 50 times a day, then tomorrow, totally different. I have witnessed the same thing with my laptop. We have 3 WLAN's in the hospitals. One that uses LEAP authentication, one that uses Certificates, and one that is our Patient WiFi. Both LEAP and Certs have the issue. I have never been kicked off of the Patient WiFi system. Not once.
LEAP clients use the same exact ACS servers they have always used. Nothing changed in the configs. Same goes for the clients using certificates.
I have upgraded code on the WISM blades 3 times now. Currently we are using the 5.187 code. I have tried forcing all AP's to use only B/G radios, tried using only A, doesn't matter. Same problem happens.
What is even worse, when this event happens, 50% of the time you have to actually reboot the workstation to get it to log back onto the wireless network. It fails the attempt and it just stops. This is not everyone at the same time either. There seems to be no event that I can find where all clients have the problem at the exact same time. I can have two devices side by side, same exact NIC, same software, everything. One will disassociate, the other is just fine.
I am out of ideas. Everyone I talk to at Cisco says never heard of this before. I just can't believe we are the only ones that have ever seen this problem.
I can take the same workstation that is breaking left and right on our wireless networks using the WISM blades, go to a site with AP's still in IOS mode, it will never disassociate and disconnect.
Has anyone heard of this, have any ideas of something I could try. Would you like to see any other information about this? I can post whatever you like to help. I am looking for any assistance on this.
I have been trying to do some searches on this forum, but for whatever reason it seems to be very slow so thought I might post my issue as I search around, maybe if it has already come up and there is a fix, someone could direct me right too it.
Thank you in advance.

I tried that in the beginning. Put all ap power and channel as hard set. It did not change anything. I am not sure if we have tried the 4.2.207 code. I know we went through several 4.x.x codes in testing. Cisco recommended the lastest one that we are on now.
What really gets me is how everything worked just fine until the WISM upgrade. No AP placement changed, no additional AP installs, we just installed the WISM blades, migrated code to lightweight and everything started flaking out.
What other NIC's do people use? Maybe the brand we use is not any good? I have been up and down with the vendor, tried different drivers, nothing seemed to change anything.
It looks to me like the WISM sends out some kind of response that the workstation NIC's do not understand, so they just sit there. On wireless sniffer traces, you can see where the request goes out to the workstation, but the workstation just never responds, hence the lockup so to speak. It will just sit there until a reboot of the PC.

WSUS Sync is not working Sync failed: UssCommunicationError: WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. --- System.Security.Authentication.AuthenticationException: The remote

I know there are loads of posts with same issue and most of them were related to proxy and connectivity .
This was case for me as well (few months back). Now the same error is back. But I've confirmed that FW ports and proxy are fine this time around.
server is configured on http port 80
ERROR
Sync failed: UssCommunicationError: WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid
according to the validation procedure.~~at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncWSUS
I've checked proxy server connectivity. I'm able browse following site from WSUS server
http://catalog.update.microsoft.com/v7/site/Home.aspx?sku=wsus&version=3.2.7600.226&protocol=1.8
I did telnet proxy server on the particular port (8080) and that is also fine.
I've doubt on certificates, any idea which are the certificates which we need to look? And if certificate is expired then (my guess) we won't be able open the above mentioned windows update catalog site?
Any tips appreciated !
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Hi Lawrence ! - Many thanks for looking into this thread and replying. Appreciate your help.
Your reply ("SSL is enabled/configured, and the certificate being used is invalid
(or the cert does not exist or cannot be obtained), or the SSL connection could not be established.") is very helpful.
I've already tested CONTENT DOWNLOAD and it's working fine. WSUS Sync was also working fine for years with proxy server configured on port (8080) and WSUS server on port 80.
My Guess (this is my best guess ;)) is this something to do with Firewall or Proxy side configuration rather than WSUS. However, I'm not finding a way to prove this to proxy/firewall team. From their perspective all the required port communication open and
proxy server is also reachable. More over we're able to access internet (Microsoft Update Catalog site) over same port (8080).
Any other hints where I can prove them it's a sure shot problem from their side.
Thanks again !!
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

JavaSoundDemo works, JMStudio fails on Capture

Similar Messages

Maybe you are looking for