CTS+ Problem
Hi,
I´ve configured the CTS. The domain controller is the Solution Manager , the request are transported from Dev portal to QAS portal but the problem is although the transport is OK (no problems during import) no changes appear in QAS portal.
Could someone help me with this?????
Resolved
Similar Messages
-
Hi..
I have to communicate between RS485 (NI card) to RS485 of the application board "with handshaking RTS/CTS"
I use serial VISA of labview and set Flow Control = RTS/CTS. and I monitor the status of RTS and CTS by property node to LED.
I espect that when I run my program first RTS should be green but it always red (no signal when I measure from Oscilloscope).
When I connect with the board, CTS is green and I can receive some wrong data from the board !!
I don't understand firstly, why the status of RTS is always red ? Is this behavior is correct ?
Thanks for any kind help.If you are using RTS/CTS flow control, you should not be looking at the RTS state. It will always return -1. Depending on how you handle the -1 case, I could believe your LED would be either green or red (I know you said it is red) but it will never change color.
The driver itself will properly set the state of RTS, but it's just not something we allow you to monitor, because you are not directly in control of it. If you measured the RTS signal from the pin with an oscilloscope, you should see it change when you write data with VISA Write.
CTS, on the other hand, should always be returning a valid value. If CTS is set, your device is telling you that you have data to read. And if you get garbage, perhaps your instrument is not properly set up in RT
S/CTS mode?
Dan Mondrik
National Instruments -
RFC problem (CTS with Solution Manager)
Hi everybody,
I'm configuring a transport landscape with Solman.
For demo purpose I created 3 clients in a Sandbox system (SBX), which should function like a 3-system-landscape. I created a transport domain in Solman (SM1) and added SBX into the domain (SM1 and SBX are not in one transport directory). The transport routes are configured from SBX:810 - SBX:820 - SBX:830. After I distributed the configuration, I can also see routes in SBX.
I also used SOLMAN_SETUP to generate the RFC connections to every client (READ and TMW), also to SBX:000 and SM1:000.
Then I created a Solman Project and wanted to configure the IMG-Project in "System Landscape" tab (so that I can use this project for CTS). But as I tried to create the IMG, I got an error:
S:No RFC authorization:000 function module SPROJECT_CREATE_NO_DIA_R.
Message no. No RFC authorization000
Can somebody give me a hint?
Another problem is, I created a customizing request and a workbench request in SBX:810, I can see them in SE09 in SBX, but in SM1 I cannot see them! I also don't understand here...
I'd preciate any help from you!Hello Charlie
Seeing all the STMS queus in Solution Manager is no problem. The way we have set it up is that the Solution Manager is the TMS domain controller and all systems are included into the TMS domain of the Solution Manager.
That makes the STMS queues of the managed SAP systems visible in transaction STMS.
About two years ago SAP showed plans for a new layer for CTS called CCTS (central CTS) which would only be available on Solution Manager and it's purpose would be even more features and central transport request management. However CCTS has vanished from the radar. It's no longer mentioned and at SAP TechED 2011 it was nowhere to be found.
Using CHARM the idea is also that person X creates a request which then a developer Y can use to insert objects into. Why? Segregation of duties is the answer. Creating a request is always done in the managed SAP system, using RFC you will jump to SE01 or another respective transaction to create the request.
QGM and CHARM add another layer (control) on top of CTS, that's how you should visualize it. If you look up presentations on CCTS you will be able to visualy see that.
You can read up on CHARM on https://service.sap.com/solutionmanager
There are also interesting SAPPress books available
The customizing option is to be found in SE09 I believe but I'll check tomorrow and update this reply because I'm on my iPad now without SAP system available.
The obligation is then you must have an IMG_Project in your managed SAP system that has been CTS enabled. Creating such an img project is easy, transaction spro_admin, fill in title, save, go to tab transport request (or something) and enable the project for CTS.
Kind regards
Tom -
Problem w/ serial CTS: asserted when it shouldn't be
Hey,
I have an old Klinger CC1.2 motor controller I'm trying to control with labview through a standard RS-232-C serial port. As far as I know there is no driver for it
According to the manual, the CTS signal should be asserted when a) it is first turned on, b) it finishes accepting a command, or c) it finishes executing a command.The CTS will be deasserted during command acceptance and exectution.
I'm trying to use the CTS signal to tell me when a command has finished executing, which (from the description above) is what the manual suggests I should be able to do. To do this, I'm sending commands to the motor controller via the Instrument I/O Assistant. After that I have a while loop that waits 100 ms before checking the CTS State using a Property Node. The program leaves the while loop when the CTS is asserted (when it outputs a 1).
The problem I'm having is that the CTS doesn't always deassert itself when the motor is still moving, i.e. when a command is still being executed. I'm hoping this is just labview operator error and not some problem internal to the CC1.2.
Any suggestions?I would not hold your breath waiting for a reply the original poster hasn't been on this site for almost a year, and then it was only on a couple of times. Hopefully someone else may have the manual, but they may not look at this thread unless they are having serial comm issues.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion -
CTS+ in PI 7.10 - problem starting cts browser from stms
Hi folks!
We have successfully configured and tested CTS+ for PI 7.1 ESR and ID objects as well as for 7.1 SLD objects. So far the world is "brave".
But we have one little issue and after scanning SMP and SDN it seems as if we are the only ones all over the world having this problem.
When we launch the CTS Browser (Transport Organizer WebUI) from ESR, ID and/or SLD and/or manually by entering the URL in the browser the CTS browser starts as desired. But when we try to start it from within ABAP transaction STMS (via Icon or via F7) only an empty browser window is launched, but not the CTS borwser in it.
Has anybody any ideas what's going on here?
Thanx in advance,
Regards,
VolkerHi Volker,
This will work with SAP GUI SP09 or higher.
Regards,
Sunil Deopurkar -
CTS Based Simple Bike Speedometer - Problem with CTS Pulse
Everytime a magnet rotates, a sensor sends a CTS signal...I know the hardware works, as it works with another Speedometer writen with Delphi (Spinner on SourceForge). However, my program is getting the right speed, then numbers way too big for about three pulses, the right speed, garbage again, etc.... I'm assuming there is something about the CTS protocol and how the Java program needs to respond to a CTS event that I'm not getting. Or could it be my use of systemtime?
Here's code snippets.....
Oh, and I'm using DSR for cadence, and RI for heartrate, any similar issues that I need to be aware of using them?
Thanks
serialPort = (SerialPort)portID.open("IntervalTrack", 0);
serialPort.setSerialPortParams(9600,
SerialPort.DATABITS_8,
SerialPort.STOPBITS_1,
SerialPort.PARITY_NONE);
serialPort.addEventListener(this);
serialPort.notifyOnDSR(true);
serialPort.notifyOnCTS(true);
serialPort.notifyOnCarrierDetect(true);
serialPort.notifyOnRingIndicator(true);
serialPort.notifyOnDataAvailable(true);
serialPort.setDTR(false);
serialPort.setRTS(true);--- snip ----
public void serialEvent(SerialPortEvent e) {
System.out.println(e.getEventType());
switch (e.getEventType())
case SerialPortEvent.CTS:
doCTS();
break;
case SerialPortEvent.DSR:
doDSR();
break;
case SerialPortEvent.RI:
doRI();
break;
private void doCTS(){
double dblSpeedT2 = System.currentTimeMillis();
double dblDeltaSpeedTime = dblSpeedT2 - this.dblSpeedT1;
//todo resolve divide by zero if (dblDeltaSpeedTime == 0.0)
// dblDeltaSpeedTime = 1;
this.dblSpeedKmPerHour = 3.6 * this.getWheelSizeInMM() /
dblDeltaSpeedTime;
this.dblSpeedT1 = dblSpeedT2;
}Just for future reference if someone googles this unanswered question (so much for Java forums help.....).
The problem was that I needed to distinguish between the evt. changing from true to false and only computing for one or the other. So if it was false I computed, if it was true I continued. (err....or was it the other way around?) either way, thats the fix.....not sure on the why of this though.. -
802.11 RTS/CTS and hidden node problem
Guys,
A little confused here.
The hidden node problem is if two nodes within a cell can hear the AP but not each other. OK.
But, when we talk about 802.11b and 802.11g backwards compatibility causing reduced throughtput in terms of bandwidth, it seems that this is always blamed on 802.11g stations having to use RTS/CTS.
But,
Even in an 802.11g only cell, dont stations still have to use RTS/CTS mechanisms for the hidden node problem?
I'm confused.com!
Thx
KenWhen 802.11b clients are associated to an 802.11g access point, the access point will turn on a protection mechanism called Request to Send/Clear to Send (RTS/CTS). Originally a mechanism for addressing the "hidden node problem" , RTS/CTS adds a degree of determinism to the otherwise multiple access network. When RTS/CTS is invoked, clients must first request access to the medium from the access point with an RTS message. Until the access point replies to the client with a CTS message, the client will refrain from accessing the medium and transmitting its data packets. When received by clients other than the one that sent the original RTS, the CTS command is interpreted as a "do not send" command, causing them to refrain from accessing the medium. One can see that this mechanism will preclude 802.11b clients from transmitting simultaneously with an 802.11g client, thereby avoiding collisions that decrease throughput due to retries. One can see that this additional RTS/CTS process adds a significant amount of protocol overhead that also results in a decrease in network throughput.
In addition to RTS/CTS, the 802.11g standard adds one other significant requirement to allow for 802.11b compatibility. In the event that a collision occurs due to simultaneous transmissions (the likelihood of which is greatly reduced due to RTS/CTS), client devices "back off" the network for a random period of time before attempting to access the medium again. The client arrives at this random period of time by selecting from a number of slots, each of which has a fixed duration. For 802.11b, there are 31 slots, each of which are 20 microseconds long. For 802.11a, there are 15 slots, each of which are nine microseconds long. 802.11a generally provides shorter backoff times than does 802.11b, which provides for better performance than 802.11a, particularly as the number of clients in a cell increases. When operating in mixed mode (operating with 802.11b clients associated) the 802.11g network will adopt 802.11b backoff times. When operating without 802.11b clients associated, the 802.11g network will adopt the higher-performance 802.11a backoff times. -
Problem in transports EP with CTS+
Hi gurus,
We installed Solution Manager 4.0 SPS13 and 2 Portals 7.0 SPS13.
Solution Manager is configured as Domain Controller and configured the
TMS with all the systems. The Transport Routes are Portal DEV --> Portal PRO.
We have the configuration indicated in:
http://help.sap.com/saphelp_nw70/helpdata/en/45/ec25370fdc3481e10000000a1553f6/content.htm
The transport strategy is:
WBO_GET_REQ_STRATEGY = Smart
WBO_REL_ REQ_STRATEGY = Auto
We created a transport order in the CTS+ Browser (Standard Request), but when we try to export a package in the Portal DEV shows the error: "<i>No valid transport request found</i>".
The same error is displayed if in the CTS+ Browser there isn't transport order created.
Kind RegardsWe restarted all servers and it seems that this problem has been solved.
Now, we have the following problem when we trying release the order:
Deployment
Transport request : SID_DEVK900009
System : SID_PRO
tp path : tp
Version and release: 372.04.08 700
CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL = http://eSID_PROl705:50118
SLD Deploy URL =
XI Deploy URL =
Non-ABAP system SID_PRO (communication system SID_DomainControler)
Deploy for SDM
Deploy File = com.company.package.my_package_20071115_120006
Start of Web Service Log
Deploy Service called with following parameters:
CommunicationData-Type:0
CommunicationData-Address:http://eSID_PROl705:50118
CommunicationData-Host:eSID_PROl705
CommunicationData-Port:50118
CommunicationData-User:'filled'
CommunicationData-Password:'filled'
Deployable(0)
Deployable-Type:0
Deployable-Id:/usr/sap/trans/data/SID_DEVK900009/com.company.package.my_package_20071115_120006.epa
class java.io.IOException:The file /usr/sap/trans/data/SID_DEVK900009/com.company.package.my_package
>>>_20071115_120006.epa does not exist on the filesystem.
com.sap.sdm.util.sduread.impl.SduReaderImpl.readFile (SduReaderImpl.java:56)
com.sap.sdm.util.sduread.impl.SduReaderImpl.readFile (SduReaderImpl.java:45)
com.sap.cts.converter.ConversionSelector.isArchiveAnSdu (ConversionSelector.java:83)
com.sap.cts.converter.ConversionSelector.execute(ConversionSelector.java:31)
com.sap.cts.core.Deployables.convert (Deployables.java:62)
com.sap.cts.core.DeployManager.deploy (DeployManager.java:57)
com.sap.cts.ejb.DeployBean.deploy (DeployBean.java:98)
com.sap.cts.ejb.DeployLocalLocalObjectImpl0_0.deploy (DeployLocalLocalObjectImpl0_0.java:103)
sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke (Method.java:324)
com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod (EJBImplementat
>>>ionContainer.java:126)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:157)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:79)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost (ServletDispatcher
>>>Impl.java:92)
SoapServlet.doPost (SoapServlet.java:51)
javax.servlet.http.HttpServlet.service (HttpServlet.java:760)
javax.servlet.http.HttpServlet.service (HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet (HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest (HttpHandlerImpl.java:266
>>>)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:387)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:365)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer (RequestAnalizer.java:
>>>944)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle (RequestAnalizer.java:266)
com.sap.engine.services.httpserver.server.Client.handle (Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request (Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process (A
>>>pplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run (MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged (AccessController.java:-2)
com.sap.engine.core.thread.impl3.SingleThread.execute (SingleThread.java:100)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
End of Web Service Log
Return Code = 12
Highest Return Code = 12
Deployment
End date and time : 20071116145206
Ended with return code: ===> 12 <===
Any idea??
Thanks -
Problem while generating CTS request
Hi All,
I am working on a SAP 3.1 i system where I have created a report program as local object($tmp).
Now when I am trying to assign it a Development Class the request gets created however in SE10
it comes under the status Local Non Transportable. Other customizing request were created without any issues as transportable.
Please suggest how that request will be made transportable.
Regards
Pravesh SharmaHi,
Delete that created request and save the program once again, then it will ask the request number(give development class - package) now u can create new request and try to transport. Just try once (it may work).
Edited by: Ravi Kumar on Jun 9, 2008 3:34 PM -
Error while transporting using CTS
Hello Everyone,
While transporting the ESR changes from Dev to integration environment i am getting this error.
Its a SOAP to RFC scenario and first time it worked fine. today when i did some changes and wanted to move again through CTS its giving a problem . Its SAP 7.11 version.
CTS Deploy Service - Version 0.93 06.03.2007
========================================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL =
SoapFaultCode:5 Authentication failed. For details see log entry logID=1ADC6A3175029F4D000000040025
>>>80B2 in security log.
Deployment
End date and time : 20120119234349
Ended with return code: ===> 12 <===
Thanks
RaviHi Ravi,
Please check this forum thread which talks about same issue:
CTS+ For PI Error: SoapFaultCode:5 Authentication failed
Regards,
Ashutosh -
Active Directory Server Problem
Hi All,
This mail Seeks to get help from people who have worked with Active Directory Server.
The following is our Current scenario.
We are in the process of establishing an SSL connection to Active Directory Server from java environment(a standalone class) in Windows 2000.
1.Active Directory Server is installed in an independent Win 2k machine.
2.SSL is enabled in the Active Directory Server Machine by installing the Enterprise Root Certificate.
3.Microsoft High Encryption pack is installed in both the client and the Server(AD)
4.The .cer file from the AD machine is imported in to the Client's keystore(cacerts) using the keytool utility.
5.The AD m/c is part of a domain named "rsa" and client m/c is part of the domain named "cts"
With the above setup,The following code tries to Establish an SSL context to the AD through JNDI.
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL,"ldap://blr03srv1.rsa.com:636");
env.put(Context.SECURITY_PROTOCOL, "ssl");
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL,"CN=Administrator,CN=Users,DC=rsa,DC=com");
env.put(Context.SECURITY_CREDENTIALS,"password");
try{
DirContext ctx = new InitialDirContext(env);
ctx.close();
}catch (Exception e){
e.printStackTrace();
When we try to run this Client we are facing a SSLHandShakeException with a message saying "No trusted certificate found".
As far as we know the .cer file is successfully imported in to the cacerts which is used by the J2SE as the default keystore.
Hence we ran out of ideas,as we think that there could be some other issue which is causing this problem.
We are looking forward to get inputs from AD enlightened people to Solve this issue
Thanks in Advance,
Manivannan.AI had problem the same and still I did not obtain to decide it, if for perhaps obtaining he passes me the solution.
thank's
Fernando Queiroz Fonseca
Graduando em Engenharia El�trica
Universidade Federal de Uberl�ndia
http://www.fernandoqueiroz.com.br
email : [email protected] -
Error when adding EPA file to transport request via CTS
I have a rather strange problem. Sometimes when attempting to add an EPA file to a Transport Request via CTS I get the following error in my logs with a corresponding short dump. This does not happen all the time.
#000255D36E8F005B00015391000003DC00046C0470FF1359#1244666238275#com.sap.portal.pcdadmintools#sap.com/irj#com.sap.portal.pcdadmintools#MOROZOWSKIJO#24750##rp1.conair.com_RP1_2406850#MOROZOWSKIJO#28167c7055fe11dea0f1000255d36e8f#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Server#Java### [com.sapportals.portal.pcd.admintools.export.ExportCTSHandling] Could not attach epa file to transport request
[EXCEPTION]
{0}#1#com.sap.tc.di.draft.ts.TsExecutionException: Error executing function (check stacktrace for details):CTS_FILE_APPEND_TO_REQUEST, (service=com.sap.tms)
at java.lang.Throwable.<init>(Throwable.java:216)
at java.lang.Exception.<init>(Exception.java:59)
at com.sap.tc.di.draft.ts.TsException.<init>(TsException.java:19)
at com.sap.tc.di.draft.ts.TsServiceException.<init>(TsServiceException.java:16)
at com.sap.tc.di.draft.ts.TsExecutionException.<init>(TsExecutionException.java:16)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsServiceException(TmsJCoExceptions.java:74)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsException(TmsJCoExceptions.java:35)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:536)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.handOverAsStream(TmsTransportService.java:253)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.requestUpdate(TmsTransportService.java:202)
at com.sap.tc.di.draft.ts.impl.TransportRequestImpl.transmit(TransportRequestImpl.java:97)
at com.sap.tc.di.draft.ts.impl.TransmissionPackageImpl.transmit(TransmissionPackageImpl.java:49)
at com.sapportals.portal.pcd.admintools.export.ExportCTSHandling.attachFileToPackage(ExportCTSHandling.java:209)
at com.sapportals.portal.pcd.admintools.export.pages.ExportStatusPage.prepareGenericPageSettings(ExportStatusPage.java:417)
at com.sapportals.portal.pcd.admintools.export.pages.ExportStatusPage.dispatchPageRequest(ExportStatusPage.java:241)
at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:89)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:103)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The current application triggered a termination with a short dump.
at java.lang.Throwable.<init>(Throwable.java:194)
at java.lang.Exception.<init>(Exception.java:41)
at java.lang.RuntimeException.<init>(RuntimeException.java:43)
at com.sap.mw.jco.JCO$Exception.<init>(JCO.java:1117)
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1224)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3909)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:112)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:133)
at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:531)
... 38 more
Edited by: Jon Morozowski on Jun 10, 2009 10:57 PMHere is the short dump in the ABAP system.
Short text of error message:
INTERNAL ERROR UPDATING REQUEST DESC OF RP1K900690
Long text of error message:
Technical information about the message:
Message class....... "PU"
Number.............. 601
Variable 1.......... "INTERNAL ERROR UPDATING REQUEST DESC OF"
Variable 2.......... "RP1K900690"
Variable 3.......... " "
Variable 4.......... " "
I have checked the RFC destination in the J2EE Admin and that works OK. This has me kind of stumped. -
How to Migrate the open transports in CTS+
Hi Experts
We are planning to implement CTS+ in our organisation, after implementing the CTS+ it's possible to migrate the open transports in CTS+
Thanks & Regards
VenkatHi venkat,
what i understand is you are already having some TR on which work is gng on and now you want to add.
no problem
in your CTS+ when you create a TR just merge the old TR into this
or
you can also you the Copy objects
in SE09
this is very common technique use by developers so just ask them to check in se09.
how it ans ur query
Regards
Prakhar -
CTS+ : Error while importing transport into Portal QA system
Hi All,
we have configured CTS+ for Portal systesms, then we have created a
test transport in Portal Development system (PD5). SOlution manager is the communication systesm. We are also able to release this transport from transport organizer web UI.
This tranpsort is available in transport queue of Portal Qua system , but on importing this transport in PQ7 we are getting following
error
Problem during file access, stopping. Error is:'The file (/usr/sap/trans_SM/data/PD5K900003/Test_CTS_20110215_031956.epa) does
not exist on the filesystem.'.
We have checked in /usr/sap/trans_SM/data/PD5K900003/ file
Test_CTS_20110215_031956.epa exist.
CTSDEPLOY and sap.com/com.sap.tc.di.CTSserver connection are working fine.
Kindly suggest.
Regards,
AkhileshError is
puhi078:sp5adm 54> more PD5T900003.PQ7
59y0C1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order : "PD5K900003"
1 ETP102 system : "PQ7"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "372.04.71" "701"
1 ETP198
2 EPU601X"CTS Import Service - Version 0.94" "04.04.2008" " " " "
2 ETW000 ========================================================================
2 EPU601 "Deploy web service destination =" "CTSDEPLOY" " " " "
2 EPU601 "Directory =" "/usr/sap/trans_SM/data" " " " "
2 EPU601 "SDM Deploy URL =" "http://cqhepad1.contact-energy.co.nz:50018" " " " "
2 EPU601 "SLD Deploy URL =" " " " " " "
2 EPU601 "XI Deploy URL =" " " " " " "
4 EPU607 Non-ABAP system "PQ7" (communication system "SP5")
1 ETW000 Start import with id:4D5ADEC1C8D6540AE10000000ACE01D3
4 ETW000 DeployProxy (patch level:0) called with following parameters:
4 ETW000 Deployable(0)
4 ETW000 Deployable-Type:0
4 ETW000 Deployable-Id:4D5A0D6A05111633E10000000ACE01D3
4 ETW000 Deployable-TransportContainerId:PD5K900003
4 ETW000 Deployable-ContentLocator:/usr/sap/trans_SM/data/PD5K900003/Test_CTS_20110215_031956.epa
1EETW000 Problem during file access, stopping. Error is:'The file (/usr/sap/trans_SM/data/PD5K900003/Test_CTS_20110215_031956.epa) does not
1EETW000 exist on the filesystem.'.
3 ETW000 End import with returncode:'12'
4AEPU601 "Highest Return Code =" "12" " " " "
1 ETP189 DEPLOYMENT -
Arch64 ati radeon 3870 radeonhd driver. Problem with xorg.conf.
I've got a small problem with my xorg. I won't hide that i'm not a xorg nerd and i've used the automatic xorg tool to generate the xorg.conf. After starting X, the screen goes black and then after ~5 seconds montior switches to power-saving mode.
So here we go.
That's xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "extmod"
Load "record"
Load "dri2"
Load "dbe"
Load "dri"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "AccelMethod" # [<str>]
#Option "offscreensize" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "ignoreconnector" # [<str>]
#Option "forcereduced" # [<bool>]
#Option "forcedpi" # <i>
#Option "useconfiguredmonitor" # [<bool>]
#Option "HPD" # <str>
#Option "NoRandr" # [<bool>]
#Option "RROutputOrder" # [<str>]
#Option "DRI" # [<bool>]
#Option "TVMode" # [<str>]
#Option "ScaleType" # [<str>]
#Option "UseAtomBIOS" # [<bool>]
#Option "AtomBIOS" # [<str>]
#Option "UnverifiedFeatures" # [<bool>]
#Option "Audio" # [<bool>]
#Option "HDMI" # [<str>]
#Option "COHERENT" # [<str>]
Identifier "Card0"
Driver "radeonhd"
VendorName "ATI Technologies Inc"
BoardName "Radeon HD 3870"
BusID "PCI:1:0:0"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "AccelMethod" # [<str>]
#Option "offscreensize" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "ignoreconnector" # [<str>]
#Option "forcereduced" # [<bool>]
#Option "forcedpi" # <i>
#Option "useconfiguredmonitor" # [<bool>]
#Option "HPD" # <str>
#Option "NoRandr" # [<bool>]
#Option "RROutputOrder" # [<str>]
#Option "DRI" # [<bool>]
#Option "TVMode" # [<str>]
#Option "ScaleType" # [<str>]
#Option "UseAtomBIOS" # [<bool>]
#Option "AtomBIOS" # [<str>]
#Option "UnverifiedFeatures" # [<bool>]
#Option "Audio" # [<bool>]
#Option "HDMI" # [<str>]
#Option "COHERENT" # [<str>]
Identifier "Card1"
Driver "radeonhd"
VendorName "ATI Technologies Inc"
BoardName "Radeon HD 3870"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
and that's the log
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64
Current Operating System: Linux kasia 2.6.31-ARCH #1 SMP PREEMPT Tue Oct 13 11:33:39 CEST 2009 x86_64
Build Date: 04 September 2009 05:45:43PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 21 20:31:45 2009
(++) Using config file: "xorg.conf.new"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Screen "Screen1" (1)
(**) | |-->Monitor "Monitor1"
(**) | |-->Device "Card1"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/TTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/TTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loader magic: 0x1d40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7
(!!) More than one possible primary device found
(--) PCI: (0:1:0:0) 1002:9501:1458:21a4 ATI Technologies Inc Radeon HD 3870 rev 0, Mem @ 0xd0000000/268435456, 0xf7000000/65536, I/O @ 0x0000a000/256, BIOS @ 0x????????/131072
(--) PCI: (0:2:0:0) 1002:9501:1458:21a4 ATI Technologies Inc Radeon HD 3870 rev 0, Mem @ 0xe0000000/268435456, 0xf5000000/65536, I/O @ 0x0000b000/256, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "radeonhd"
(II) Loading /usr/lib/xorg/modules/drivers//radeonhd_drv.so
(II) Module radeonhd: vendor="AMD GPG"
compiled for 1.6.0, module version = 1.2.5
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) RADEONHD: X driver for the following AMD GPG (ATI) graphics devices:
RV505 : Radeon X1550, X1550 64bit.
RV515 : Radeon X1300, X1550, X1600; FireGL V3300, V3350.
RV516 : Radeon X1300, X1550, X1550 64-bit, X1600; FireMV 2250.
R520 : Radeon X1800; FireGL V5300, V7200, V7300, V7350.
RV530 : Radeon X1300 XT, X1600, X1600 Pro, X1650; FireGL V3400, V5200.
RV535 : Radeon X1300, X1650.
RV550 : Radeon X2300 HD.
RV560 : Radeon X1650.
RV570 : Radeon X1950, X1950 GT; FireGL V7400.
R580 : Radeon X1900, X1950; AMD Stream Processor.
R600 : Radeon HD 2900 GT/Pro/XT; FireGL V7600/V8600/V8650.
RV610 : Radeon HD 2350, HD 2400 Pro/XT, HD 2400 Pro AGP; FireGL V4000.
RV620 : Radeon HD 3450, HD 3470.
RV630 : Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630;
FireGL V3600/V5600.
RV635 : Radeon HD 3650, HD 3670.
RV670 : Radeon HD 3690, 3850, HD 3870, FireGL V7700, FireStream 9170.
R680 : Radeon HD 3870 X2.
M52 : Mobility Radeon X1300.
M54 : Mobility Radeon X1400; M54-GL.
M56 : Mobility Radeon X1600; Mobility FireGL V5200.
M58 : Mobility Radeon X1800, X1800 XT; Mobility FireGL V7100, V7200.
M62 : Mobility Radeon X1350.
M64 : Mobility Radeon X1450, X2300.
M66 : Mobility Radeon X1700, X1700 XT; FireGL V5250.
M68 : Mobility Radeon X1900.
M71 : Mobility Radeon HD 2300.
M72 : Mobility Radeon HD 2400; Radeon E2400.
M74 : Mobility Radeon HD 2400 XT.
M76 : Mobility Radeon HD 2600;
(Gemini ATI) Mobility Radeon HD 2600 XT.
M82 : Mobility Radeon HD 3400.
M86 : Mobility Radeon HD 3650, HD 3670, Mobility FireGL V5700.
M88 : Mobility Radeon HD 3850, HD 3850 X2, HD 3870, HD3870 X2.
RS600 : Radeon Xpress 1200, Xpress 1250.
RS690 : Radeon X1200, X1250, X1270.
RS740 : RS740, RS740M.
RS780 : Radeon HD 3100/3200/3300 Series.
RV770 : Radeon HD 4800 Series; Everest, K2, Denali ATI FirePro.
R700 : Radeon R700.
M98 : Radeon M98 Mobility.
RV730 : Radeon HD4670, HD4650.
M96 : Radeon M96 Mobility.
RV710 : Radeon HD4570, HD4350.
(II) RADEONHD: version 1.2.5, built from dist of git branch master, commit cb54f48b
(II) Primary Device is:
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] 1 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[8] 1 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[9] 1 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[11] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[12] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[13] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
[14] 1 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[15] 1 0 0x000003c0 - 0x000003df (0x20) IS[b]
(==) RADEONHD(0): Depth 24, (--) framebuffer bpp 32
(**) RADEONHD(0): Selected ShadowFB.
(II) RADEONHD(0): Unknown card detected: 0x9501:0x1458:0x21A4.
If - and only if - your card does not work or does not work optimally
please contact [email protected] to help rectify this.
Use the subject: 0x9501:0x1458:0x21A4: <name of board>
and *please* describe the problems you are seeing
in your message.
(--) RADEONHD(0): Detected an RV670 on an unidentified card
(II) RADEONHD(0): Mapped IO @ 0xf7000000 to 0x7f39ca36f000 (size 0x00010000)
(II) RADEONHD(0): PCIE Card Detected
(II) RADEONHD(0): Getting BIOS copy from PCI ROM
(II) RADEONHD(0): ATOM BIOS Rom:
SubsystemVendorID: 0x1458 SubsystemID: 0x21a4
IOBaseAddress: 0xa000
Filename: Test.bin
BIOS Bootup Message:
GV-RX387512HP_F10
(II) RADEONHD(0): Default Engine Clock: 825000
(II) RADEONHD(0): Default Memory Clock: 900000
(II) RADEONHD(0): Calling ASIC Init
(II) RADEONHD(0): ASIC_INIT Successful
(II) RADEONHD(0): Analog TV Default Mode: 1
(II) RADEONHD(0): Found default TV Mode NTSC
(II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture.
(II) RADEONHD(0): Using only 262144kB of the total 524288kB.
(--) RADEONHD(0): VideoRAM: 262144 kByte
(II) RADEONHD(0): Framebuffer space used by Firmware (kb): 16
(II) RADEONHD(0): Start of VRAM area used by Firmware: 0x1fffc000
(II) RADEONHD(0): AtomBIOS requests 16kB of VRAM scratch space
(II) RADEONHD(0): AtomBIOS VRAM scratch base: 0x1fffc000
(WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area 536854528 (size: 16384) extends beyond available framebuffer size 268435456
(II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory instead
(II) RADEONHD(0): Default Engine Clock: 825000
(II) RADEONHD(0): Default Memory Clock: 900000
(II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Input: 13500
(II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Input: 1000
(II) RADEONHD(0): Maximum Pixel Clock: 400000
(II) RADEONHD(0): Reference Clock: 27000
(II) RADEONHD(0): Direct rendering not officially supported on R600 and up
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) RADEONHD(0): Reference Clock: 27000
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f90
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f90
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 0" initialized.
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f94
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f94
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 1" initialized.
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f98
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f98
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 2" initialized.
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f80
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f80
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 3" initialized.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) RADEONHD(0): Detected VGA mode.
(II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEONHD(0): Maximum Pixel Clock: 400000
(II) RADEONHD(0): Reference Clock: 27000
(II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00000000 (size = 0x00004000)
(II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00004000 (size = 0x00004000)
(II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I DFP1 CRT2", RHD_DDC_1, RHD_HPD_0, { RHD_OUTPUT_TMDSA, RHD_OUTPUT_DACB } }
(II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_TV, "7PIN_DIN TV1 CV", RHD_DDC_0, RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector[2] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I CRT1 DFP2", RHD_DDC_0, RHD_HPD_1, { RHD_OUTPUT_LVTMA, RHD_OUTPUT_DACA } }
(--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1
(--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1
(--) RADEONHD(0): Attaching Output DAC B to Connector TV 7PIN_DIN
(--) RADEONHD(0): Attaching Output TMDS B to Connector DVI-I 2
(--) RADEONHD(0): Attaching Output DAC A to Connector DVI-I 2
(II) RADEONHD(0): RandR: Adding RRoutput DVI-I_1/digital for Output TMDS A
(II) RADEONHD(0): RandR: Adding RRoutput DVI-I_1/analog for Output DAC B
(II) RADEONHD(0): RandR: Adding RRoutput TV_7PIN_DIN for Output DAC B
(II) RADEONHD(0): RandR: Adding RRoutput DVI-I_2/digital for Output TMDS B
(II) RADEONHD(0): RandR: Adding RRoutput DVI-I_2/analog for Output DAC A
(II) RADEONHD(0): Output DVI-I_1/digital using monitor section Monitor0
(II) RADEONHD(0): Output DVI-I_1/digital has no monitor section
(II) RADEONHD(0): Output DVI-I_1/analog has no monitor section
(II) RADEONHD(0): Output TV_7PIN_DIN has no monitor section
(II) RADEONHD(0): Output DVI-I_2/digital has no monitor section
(II) RADEONHD(0): Output DVI-I_2/analog has no monitor section
(II) RADEONHD(0): TMDS A: Sensed Output: DVI
(II) RADEONHD(0): Setting TMDS A to incoherent
(II) RADEONHD(0): I2C device "RHD I2C line 1:E-EDID segment register" registered at address 0x60.
(II) RADEONHD(0): I2C device "RHD I2C line 1:ddc2" registered at address 0xA0.
(II) RADEONHD(0): EDID data for W2253
(II) RADEONHD(0): Manufacturer: GSM Model: 56dc Serial#: 385315
(II) RADEONHD(0): Year: 2009 Week: 5
(II) RADEONHD(0): EDID Version: 1.3
(II) RADEONHD(0): Digital Display Input
(II) RADEONHD(0): Max Image Size [cm]: horiz.: 49 vert.: 32
(II) RADEONHD(0): Gamma: 2.20
(II) RADEONHD(0): DPMS capabilities: StandBy Suspend Off
(II) RADEONHD(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEONHD(0): First detailed timing is preferred mode
(II) RADEONHD(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
(II) RADEONHD(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
(II) RADEONHD(0): Supported established timings:
(II) RADEONHD(0): 720x400@70Hz
(II) RADEONHD(0): 640x480@60Hz
(II) RADEONHD(0): 640x480@75Hz
(II) RADEONHD(0): 800x600@56Hz
(II) RADEONHD(0): 800x600@60Hz
(II) RADEONHD(0): 800x600@75Hz
(II) RADEONHD(0): 832x624@75Hz
(II) RADEONHD(0): 1024x768@60Hz
(II) RADEONHD(0): 1024x768@75Hz
(II) RADEONHD(0): 1280x1024@75Hz
(II) RADEONHD(0): 1152x870@75Hz
(II) RADEONHD(0): Manufacturer's mask: 0
(II) RADEONHD(0): Supported standard timings:
(II) RADEONHD(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
(II) RADEONHD(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) RADEONHD(0): #2: hsize: 1280 vsize 1024 refresh: 75 vid: 36737
(II) RADEONHD(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) RADEONHD(0): Supported detailed timing:
(II) RADEONHD(0): clock: 138.5 MHz Image Size: 510 x 290 mm
(II) RADEONHD(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
(II) RADEONHD(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
(II) RADEONHD(0): Supported detailed timing:
(II) RADEONHD(0): clock: 148.5 MHz Image Size: 510 x 290 mm
(II) RADEONHD(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
(II) RADEONHD(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
(II) RADEONHD(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 150 MHz
(II) RADEONHD(0): Monitor name: W2253
(II) RADEONHD(0): EDID (in hex):
(II) RADEONHD(0): 00ffffffffffff001e6ddc5623e10500
(II) RADEONHD(0): 0513010380312078eaee91a3544c9926
(II) RADEONHD(0): 0f5054a76b80b3008180818f714f0101
(II) RADEONHD(0): 0101010101011a3680a070381f403020
(II) RADEONHD(0): 3500fe221100001e023a801871382d40
(II) RADEONHD(0): 582c4500fe221100001c000000fd0038
(II) RADEONHD(0): 4b1e530f000a202020202020000000fc
(II) RADEONHD(0): 0057323235330a202020202020200081
(II) RADEONHD(0): EDID vendor "GSM", prod id 22236
(II) RADEONHD(0): Using EDID range info for horizontal sync
(II) RADEONHD(0): Using EDID range info for vertical refresh
(II) RADEONHD(0): Printing DDC gathered Modelines:
(II) RADEONHD(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync +vsync (66.6 kHz)
(II) RADEONHD(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 -hsync +vsync (67.5 kHz)
(II) RADEONHD(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEONHD(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(II) RADEONHD(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) RADEONHD(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEONHD(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEONHD(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) RADEONHD(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(II) RADEONHD(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) RADEONHD(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(II) RADEONHD(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) RADEONHD(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) RADEONHD(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz)
(II) RADEONHD(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEONHD(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) RADEONHD(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) RADEONHD(0): Output DVI-I_1/digital connected
(II) RADEONHD(0): Output DVI-I_1/analog disconnected
(II) RADEONHD(0): Output TV_7PIN_DIN disconnected
(II) RADEONHD(0): Output DVI-I_2/digital disconnected
(II) RADEONHD(0): Output DVI-I_2/analog disconnected
(II) RADEONHD(0): Using exact sizes for initial modes
(II) RADEONHD(0): Output DVI-I_1/digital using initial mode 1920x1080
(II) RADEONHD(0): RandR 1.2 support enabled
(==) RADEONHD(0): RGB weight 888
(==) RADEONHD(0): Default visual is TrueColor
(==) RADEONHD(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEONHD(0): Using 1920x1920 Framebuffer with 1920 pitch
(II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x00008000 (size = 0x00E10000)
(**) RADEONHD(0): Display dimensions: (490, 320) mm
(**) RADEONHD(0): DPI set to (99, 152)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) RADEONHD(0): Using ShadowFB
(==) RADEONHD(1): Depth 24, (--) framebuffer bpp 32
(**) RADEONHD(1): Selected ShadowFB.
(II) RADEONHD(1): Unknown card detected: 0x9501:0x1458:0x21A4.
If - and only if - your card does not work or does not work optimally
please contact [email protected] to help rectify this.
Use the subject: 0x9501:0x1458:0x21A4: <name of board>
and *please* describe the problems you are seeing
in your message.
(--) RADEONHD(1): Detected an RV670 on an unidentified card
(II) RADEONHD(1): Mapped IO @ 0xf5000000 to 0x7f39ca36f000 (size 0x00010000)
(II) RADEONHD(1): PCIE Card Detected
(II) RADEONHD(1): Getting BIOS copy from PCI ROM
(II) RADEONHD(1): ATOM BIOS Rom:
SubsystemVendorID: 0x1458 SubsystemID: 0x21a4
IOBaseAddress: 0x0000
Filename: Test.bin
BIOS Bootup Message:
GV-RX387512HP_F10
(II) RADEONHD(1): Default Engine Clock: 825000
(II) RADEONHD(1): Default Memory Clock: 900000
(II) RADEONHD(1): Calling ASIC Init
(II) RADEONHD(1): ASIC_INIT Successful
(II) RADEONHD(1): Analog TV Default Mode: 27049664
(II) RADEONHD(1): The detected amount of videoram exceeds the PCI BAR aperture.
(II) RADEONHD(1): Using only 262144kB of the total 524288kB.
(--) RADEONHD(1): VideoRAM: 262144 kByte
(II) RADEONHD(1): Framebuffer space used by Firmware (kb): 0
(WW) RADEONHD(1): rhdAtomGetFbBaseAndSize: AtomBIOS specified VRAM scratch space size invalid
(II) RADEONHD(1): default to: 20480
(II) RADEONHD(1): Cannot get VRAM scratch space. Allocating in main memory instead
(II) RADEONHD(1): Default Engine Clock: 825000
(II) RADEONHD(1): Default Memory Clock: 900000
(II) RADEONHD(1): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEONHD(1): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEONHD(1): Maximum Pixel ClockPLL Frequency Input: 13500
(II) RADEONHD(1): Minimum Pixel ClockPLL Frequency Input: 1000
(II) RADEONHD(1): Maximum Pixel Clock: 400000
(II) RADEONHD(1): Reference Clock: 27000
(II) RADEONHD(1): Direct rendering not officially supported on R600 and up
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) RADEONHD(1): Reference Clock: 27000
(II) RADEONHD(1): GPIO_I2C_Clk_Mask: 0x1f90
(II) RADEONHD(1): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(1): GPIO_I2C_Data_Mask: 0x1f90
(II) RADEONHD(1): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(1): I2C bus "RHD I2C line 0" initialized.
(II) RADEONHD(1): GPIO_I2C_Clk_Mask: 0x1f94
(II) RADEONHD(1): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(1): GPIO_I2C_Data_Mask: 0x1f94
(II) RADEONHD(1): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(1): I2C bus "RHD I2C line 1" initialized.
(II) RADEONHD(1): GPIO_I2C_Clk_Mask: 0x1f98
(II) RADEONHD(1): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(1): GPIO_I2C_Data_Mask: 0x1f98
(II) RADEONHD(1): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(1): I2C bus "RHD I2C line 2" initialized.
(II) RADEONHD(1): GPIO_I2C_Clk_Mask: 0x1f80
(II) RADEONHD(1): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(1): GPIO_I2C_Data_Mask: 0x1f80
(II) RADEONHD(1): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(1): I2C bus "RHD I2C line 3" initialized.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) RADEONHD(1): Detected VGA mode.
(II) RADEONHD(1): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEONHD(1): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEONHD(1): Maximum Pixel Clock: 400000
(II) RADEONHD(1): Reference Clock: 27000
(II) RADEONHD(1): FB: Allocated Cursor Image at offset 0x00000000 (size = 0x00004000)
(II) RADEONHD(1): FB: Allocated Cursor Image at offset 0x00004000 (size = 0x00004000)
(II) RADEONHD(1): Connector[0] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I DFP1 CRT2", RHD_DDC_1, RHD_HPD_0, { RHD_OUTPUT_TMDSA, RHD_OUTPUT_DACB } }
(II) RADEONHD(1): Connector[1] {RHD_CONNECTOR_TV, "7PIN_DIN TV1 CV", RHD_DDC_0, RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } }
(II) RADEONHD(1): Connector[2] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I CRT1 DFP2", RHD_DDC_0, RHD_HPD_1, { RHD_OUTPUT_LVTMA, RHD_OUTPUT_DACA } }
(--) RADEONHD(1): Attaching Output TMDS A to Connector DVI-I 1
(--) RADEONHD(1): Attaching Output DAC B to Connector DVI-I 1
(--) RADEONHD(1): Attaching Output DAC B to Connector TV 7PIN_DIN
(--) RADEONHD(1): Attaching Output TMDS B to Connector DVI-I 2
(--) RADEONHD(1): Attaching Output DAC A to Connector DVI-I 2
(II) RADEONHD(1): RandR: Adding RRoutput DVI-I_1/digital for Output TMDS A
(II) RADEONHD(1): RandR: Adding RRoutput DVI-I_1/analog for Output DAC B
(II) RADEONHD(1): RandR: Adding RRoutput TV_7PIN_DIN for Output DAC B
(II) RADEONHD(1): RandR: Adding RRoutput DVI-I_2/digital for Output TMDS B
(II) RADEONHD(1): RandR: Adding RRoutput DVI-I_2/analog for Output DAC A
(II) RADEONHD(1): Output DVI-I_1/digital using monitor section Monitor1
(II) RADEONHD(1): Output DVI-I_1/digital has no monitor section
(II) RADEONHD(1): Output DVI-I_1/analog has no monitor section
(II) RADEONHD(1): Output TV_7PIN_DIN has no monitor section
(II) RADEONHD(1): Output DVI-I_2/digital has no monitor section
(II) RADEONHD(1): Output DVI-I_2/analog has no monitor section
(II) RADEONHD(1): Output DVI-I_1/digital disconnected
(II) RADEONHD(1): Output DVI-I_1/analog disconnected
(II) RADEONHD(1): Output TV_7PIN_DIN disconnected
(II) RADEONHD(1): Output DVI-I_2/digital disconnected
(II) RADEONHD(1): Output DVI-I_2/analog disconnected
(WW) RADEONHD(1): No outputs definitely connected, trying again...
(II) RADEONHD(1): Output DVI-I_1/digital disconnected
(II) RADEONHD(1): Output DVI-I_1/analog disconnected
(II) RADEONHD(1): Output TV_7PIN_DIN disconnected
(II) RADEONHD(1): Output DVI-I_2/digital disconnected
(II) RADEONHD(1): Output DVI-I_2/analog disconnected
(WW) RADEONHD(1): Unable to find initial modes
(EE) RADEONHD(1): RandR: No valid modes. Disabling RandR support.
(EE) RADEONHD(1): Failed to detect a connected monitor
(II) RADEONHD(1): Destroying TMDS A
(II) RADEONHD(1): Destroying DAC B
(II) RADEONHD(1): Destroying TMDS B
(II) RADEONHD(1): Destroying DAC A
(II) RADEONHD(1): I2C bus "RHD I2C line 0" removed.
(II) RADEONHD(1): I2C bus "RHD I2C line 1" removed.
(II) RADEONHD(1): I2C bus "RHD I2C line 2" removed.
(II) RADEONHD(1): I2C bus "RHD I2C line 3" removed.
(II) UnloadModule: "radeonhd"
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) RADEONHD(0): Mapped IO @ 0xf7000000 to 0x7f39ca36f000 (size 0x00010000)
(II) RADEONHD(0): Mapped FB @ 0xd0000000 to 0x7f39b66f6000 (size 0x10000000)
(WW) RADEONHD(0): RHDCSInit: No CS for R600 and up yet.
(==) RADEONHD(0): Backing store disabled
(==) RADEONHD(0): Silken mouse enabled
(II) RADEONHD(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) RADEONHD(0): On Crtc 0 Setting 59.9 Hz Mode: Modeline "1920x1080" 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync +vsync
None
(II) RADEONHD(0): RHDAudioSetClock: using TMDS A as clock source with 138500 khz
(II) RADEONHD(0): Using ACR timing N=4096 CTS=138500 for frequency 32000
(II) RADEONHD(0): Using ACR timing N=6272 CTS=153888 for frequency 44100
(II) RADEONHD(0): Using ACR timing N=6144 CTS=138500 for frequency 48000
(II) RADEONHD(0): RHDAudioSetSupported: config 0x60040 codec 0x1
(II) RADEONHD(0): DPMS enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) RADEONHD(0): Setting screen physical size to 510 x 290
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 2.2.5
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device ImPS/2 Logitech Wheel Mouse
(**) ImPS/2 Logitech Wheel Mouse: always reports core events
(**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event5"
(II) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
(II) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
(II) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
(II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
(**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
(**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE)
(**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
(**) ImPS/2 Logitech Wheel Mouse: (accel) filter chain progression: 2.00
(**) ImPS/2 Logitech Wheel Mouse: (accel) filter stage 0: 20.00 ms
(**) ImPS/2 Logitech Wheel Mouse: (accel) set acceleration profile 0
(II) ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event4"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) RADEONHD(0): RHDHdmiUpdateAudioSettings: stoped with 1 channels, 48000 Hz sampling rate, 8 bits per sample,
(II) RADEONHD(0): RHDHdmiUpdateAudioSettings: 0x00 IEC60958 status bits and 0x00 category code
(II) RADEONHD(0): RHDHdmiUpdateAudioSettings: stoped with 1 channels, 48000 Hz sampling rate, 8 bits per sample,
(II) RADEONHD(0): RHDHdmiUpdateAudioSettings: 0x00 IEC60958 status bits and 0x00 category code
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) ImPS/2 Logitech Wheel Mouse: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
Last edited by warnab (2009-10-21 18:53:12)i'm getting then such log
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64
Current Operating System: Linux kasia 2.6.31-ARCH #1 SMP PREEMPT Tue Oct 13 11:33:39 CEST 2009 x86_64
Build Date: 04 September 2009 05:45:43PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 21 22:35:22 2009
(II) Loader magic: 0x1d40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7
(!!) More than one possible primary device found
(--) PCI: (0:1:0:0) 1002:9501:1458:21a4 ATI Technologies Inc Radeon HD 3870 rev 0, Mem @ 0xd0000000/268435456, 0xf7000000/65536, I/O @ 0x0000a000/256, BIOS @ 0x????????/131072
(--) PCI: (0:2:0:0) 1002:9501:1458:21a4 ATI Technologies Inc Radeon HD 3870 rev 0, Mem @ 0xe0000000/268435456, 0xf5000000/65536, I/O @ 0x0000b000/256, BIOS @ 0x????????/131072
Primary device is not PCI
(==) Using default built-in configuration (21 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default vesa Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/TTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "vesa"
(WW) Warning, couldn't open module vesa
(II) UnloadModule: "vesa"
(EE) Failed to load module "vesa" (module does not exist, 0)
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Maybe you are looking for
-
APEX 4.2. - SkillBuilders Modal Page plugin not sizing fields or labels
I recently migrated from 4.1 to 4.2, bringing over the Skillbuilders plugin 2.0.0. My page has a Popup template. When I open the page as a Skillbuilders Modal Page, all of the fields have the same width, ignoring the width I've given it with the labe
-
Data Merge - Not removing blank lines when more than one in a row
I am having the same problem as mentioned here: http://forums.adobe.com/message/2109531#2109531 That post is for some reason set as "answered" though the poster said the latest update did not resolve the issue. Has anyone found a solution to this i
-
Using PSE on Mac. When attempting to Edit a file system advises that requires Premiere Elements. Help!!!
-
Enable Virtualization BIOS option
What about me? I have a X48C Platinum motherboard and a Core 2 Duo E6850. Thrust me... they both suport Intel VT. But in bios there is no on or of swich for vanderpool or Intel VT. I to want to use XP Mode in Windows 7, but it tells me that this opti
-
Corba error when running rich clients in 3-tier mode.
Hello I am dealing with an Error when running Rich Clients (WebI and DeskI) with 3-tier ODBC connection to the server. The client does come up and I'm able to create the query but when the data in refreshed I do get the error: A database error occure