Using Multiproviders and Virtual Providers
Hi Everyone,
I have just created some virtual providers in our BW Dev environment. I have also created a Multiprovider on those Virtual Providers, so that we can report off all of the VP's. I have also created different BW source systems, in order for us to look at data from different boxes. I did an Activate Direct Access on all VP's for the three BW source systems that I want to report against.
I have a couple questions.
1. When I attempt to run a query against that Multiprovider, it generates a short dump on one of the BW source systems (TSV_TNEW_PAGE_ALLOC_FAILED). I guess it's trying to extend memory on an internal table, but I'm barely returning any data, so I don't understand why it would do that. Is anyone familiar with this?
2. When I attempt to run a query against that Multiprovider for the other BW source system I created, it doesn't even try and remote into it. All my BW source systems have the same properties, other than their server information. Does anyone know if we're limited to the amount of source systems we can use as an Activate Direct Access on a VP?
Please let me know if you can help.
Thanks,
John
Short text
No more storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
The internal table "\PROGRAM=GP4FUVGPUVXRMVKI98TNSALEQMM\FORM=SELECT_DATA\DATA=
L_T_TFSTRUCT" could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 826
Number of rows: 3894032
Allocated rows: 3894032
Newly requested rows: 16 (in 1 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server osprey_WWQ_45 on host osprey (wp 0)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
Source Code Extract
The error reported by the operating system is:
Error number..... " "
Error text....... " "
490
491 e_subrc = sy-subrc.
492 CASE e_subrc.
493 WHEN 0. "process fetched records
494
495 IF l_initflag NE sbiwa_c_flag_off.
496 l_initflag = sbiwa_c_flag_off.
497 CONTINUE.
498 ELSE.
499 * convert extract structure to transfer structure
500 LOOP AT l_t_exstruct ASSIGNING <l_s_exstruct>.
>>>>> APPEND INITIAL LINE TO l_t_tfstruct.
502 READ TABLE l_t_tfstruct ASSIGNING <l_s_tfstruct>
503 INDEX sy-tabix.
504 MOVE-CORRESPONDING <l_s_exstruct> TO <l_s_tfstruct>.
505 ENDLOOP.
506 CLEAR l_t_exstruct[].
507 DESCRIBE TABLE l_t_tfstruct LINES e_lines.
508 IF i_package_size EQ 0 OR
509 i_package_size GT e_lines.
510 CONTINUE.
511 ENDIF.
512 ENDIF.
513
514 WHEN 1. "exit do loop with rc = 1
515
516 WHEN OTHERS. "exit do loop with error message
Similar Messages
-
Trying to deploy a Service using Orchestrator and Virtual Machine Manager
Hello,
I'm trying to create a runbook to deploy a Service in a cloud using Orchstrator and Virtual Machine Manager, 2012 R2 both of them.
I'm following these 2 links, but not luck.
http://daniyar-tech.blogspot.com.es/2013/07/system-center-2012-sp1-orchestrator.html
http://www.systemcentercentral.com/orchestrator-by-example-deploying-a-service-from-template-with-vmm-and-orchestrator-2/
I'm receiving this error in "Configure Service Deployment" step:
The following errors occurred when invoking PowerShell script:Could not find service template
I configured the Cloud Name and it does not work for me...
Thanks!Thanks, Marc! This solution worked for me, after many other attempts failed.
Senior Tech Writer, SharePoint Performance and Capacity Management -
Hello everyone,
I recently bummed into an error message when I want to deploy a service template.
Setup:
1 HyperV server on win2k12 r2
1 SCCM VMM 2k12r2 on the hyperv server
1 template with all the objects in the library
Error:
When I deploy the the service template I get the below error message.
22591
The specified computer name (%ComputerName;) is already in use by another virtual machine or by a virtual machine configuration object.
Ensure that the computer name is unique in the VMM environment, and then try again.
The issue is that I can't find it anywhere, not on my domain controller not on my dns server as a record and also not as a vm in sccm or in powershell when doing get-vm. So where do I need to remove it ( no it is not an option to create a new Hostname for
this service template ).
AndreThere could be a couple things happening.
One - you have a Service Template, it defines %Computername% as a variable. And you have deployed this Template once using 'foo' and you are deploying it again as 'foo' without deleting the previous instance.
Two - you hardcoded the computer name into the template.
Three - you are scaling out and you have hit the bug that the wizard does not increment the machinename if you have something like computername## where SCVMM should be incrementing the machine name.
Windows does not support identically named machines (you can't have two machines on the same network with the same computer name - they broadcast their name and the 'second' one shuts down its network stack). In support of this SCVMM also enforces
this rule.
And with any templates SCVMM is in charge of machine names at deployment.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat. -
I am planning to buy ipad 2 wifi 3g verizon carrier, will be taking it to india need to know if the same can be used with the local providers there or would the ipad be locked and restricted only to verizon
I'm fairly sure the Verizon CDMA iPad 2 had no GSM sim slot. So it won't work with any other carrier except Verizon.
As far as the AT&T version goes, it should technically work but will not support 4G/LTE cellular bands.
Given iPad 2's are no longer being sold, I doubt any that could be bought would have a warranty still. Or have at most very little of it left.
Why an iPad 2? its now 3 generations behind the current one.
Perhaps an iPad 4 would be a better choice. -
My wife has ALS and no use of her hands and virtually no voice.
My wife has no use of her hands and virtually no voice, she can turn on her iPhone 3G with a Bluetooth device that has a large button connected to it that she can touch with her arm to turn on the phone ready to redial the last number typed in......however she cannot activate the "Swipe to Unlock" feature? Is there an App or any way I can get rid of the Swipe to Unlock button or replace it with a Large Button she can hit, we have tried the Security code method with no sucess.
Any suggestions from the experts out there very welcome. ( There's an app called Nose Dial with two large buttons in the German iTunes store but I cannot get it easily from Canada) DaveSorry to hear of your wife's issues with using an iPad
I can't help specifically but have you seen this help
http://support.apple.com/kb/HT5018
You may find something here you could use
You could also consider calling Apple in Canada to see if they can link you to an accessibility team in Apple
Good luck -
Whats is the key difference in Virtual providers suing BAPI and Functionmodules?
i know about vietual provider based on DTP.
i know about BAPI and Functionmodules too.
But wat is the difference Between BAPI and Function Module?Hi ,
BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.
Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench. They are then called RFC function modules. BAPIs are complete sets of (BAPI) function modules that model a business application.
When you are familiar with web developments: RFC can be compared to HTTP and BAPIs are CGI applications.
In other words: A BAPI function is a function module that can be called remotely using the RFC technology.
BAPI's are RFC enabled API's where as FM's are not.
FM :
actualy function module is used for external subrotine inside sap server its supports for only local excution programs
BAPI :
its as similar to function module but we need to follow some rules while creating bapi function module thats it.
its used for communicate in between sap server and non sap server.
Most of the companies thay are maintain not only sap server for their Business thay maintain non sap like vb, .net .
so using this bapi two srvers are sharing their data through bapi import, export, tables parameters......
what is BAPI?
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
u can check the below the material also
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
hope it clears everything.
Regards,
neelima. -
How to Install Physical and Virtual Host
I am getting licensing issues after I installed Essentials 2012R2 on a physical machine and then used the same license to virtualize it. It's saying my physical machine needs to hold all the FSMO roles in which my virtual machine is hosting those roles.
I read that Microsoft allows you to use the Essentials license for the physical and virtual server. Is that correct?
Is there a specific service I need to remove on the physical machine in order for these errors to stop? I still have the Windows Server Essentials Experience service installed. Is that what needs to be removed?
Thanks,
DougHi Doug,
There is an article that provide details of licensing for Windows Server 2012 R2 Essentials. Please refer to and check if can help us to understand licensing for Windows Server 2012 R2 Essentials better.
Understanding Licensing for Windows Server 2012 R2 Essentials and the Windows
Server Essentials Experience role
Please also refer to following article and check if can help you.
Customize Deployment - Windows Server Essentials
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
What is the difference between "Invisible" (11g) and "virtual" index?
Hi
What is the difference between the "Invisible" index and "virtual" index?
Thanks
BalajiIndexes can be visible or invisible. An invisible index is maintained by DML operations and cannot be used by the optimizer. Actually takes space, but is not to be used as part of a potential access path.
AFAIK, a virtual index is created by the tools used in SQL statement access path tuning to provide an alternative for the optimizer to test. It does not take any real space as it is a pure in memory definition. -
Troubleshooting issues using the BlackBerry Virtual Expert
Posted originally on the Inside BlackBerry Help Blog
Does your BlackBerry need a health assessment? Are you considering a repair? If so, check out the BlackBerry Virtual Expert (BBVE), a simple, self-guided diagnostic app for BlackBerry smartphones.
Depending on what type of smartphone you are using, you can run tests to help identify if an issue is occurring and get recommendations on how to solve the problem.
To help you get started with BBVE, here’s a quick overview of how to use this app and what to do if a tests fails.
How to use the BlackBerry Virtual Expert
If you are using BlackBerry 10 OS version 10.2.1, BlackBerry Virtual Expert is built in and can be found by opening the Help app followed by tapping Testing along the bottom toolbar. Within this screen, tap Try this now to open BBVE.
For smartphones running BlackBerry OS version 10.2 or earlier, or BlackBerry OS version 7.1 and earlier, to use BBVE you need to install it first.
To do this, open BlackBerry World on your smartphone and search for “BlackBerry Virtual Expert,” or use the following steps to scan a barcode. After installation is complete, look for the BBVE icon that appears on your home screen.
Open BlackBerry World.
Complete one of the following:
If your smartphone is running BlackBerry 10 OS, swipe down from the top of the screen and tapScan Barcode.
If your smartphone is running BlackBerry OS version 7.1 or earlier, press the Menu key followed by Scan a Barcode.
Scan the following barcode and tap Download.
After opening the BBVE, the Health tab appears by default which allows you to identify basic details about your smartphone and quickly access specific settings.
If you select Tests along the bottom toolbar, you can run all of the available tests at once or test a specific feature. To test everything at once, tap All Tests or select a specific feature or function you’d like to test.
If you have concerns about your headphone jack for example, select Audio Test to run a variety of audio-related tests, or optionally select Choose A Test followed by tapping on the specific test you’d like to run.
When you start testing a feature, follow the instructions displayed on your smartphone and complete the required actions followed by recording a result: Pass , Skip , or Fail . When all of the selected tests are completed you are shown your results indicating what passed, what tests were skipped, and of course, any tests that may have failed.
One of the BBVE tests failed! Help!
Should a test fail while using BBVE, after reviewing the suggestions on the Results tab, here are a few things you can do to help get an issue resolved efficiently.
Step 1 – Summarize the issue
Creating a summary of the issue you are encountering and recording what troubleshooting steps you have already taken is a great step that helps our support teams better assist you. In addition to creating a summary, obtain your BlackBerry smartphone details using the steps below.
If you are using a BlackBerry 10 smartphone, to identify your OS version, tap Settings > About and in theCategory drop-down list, select OS. To identify your PIN, tap Settings > About and in the Category drop-down list, select Hardware.
If you are using a BlackBerry OS smartphone, check out this post for help identifying this information.
Step 2 – Back up your device
When you contact support for a potential repair issue, they will guide you through this process, so doing this before you contact support can help speed things along.
If you are using a BlackBerry 10 smartphone, download and install BlackBerry Link for PC or Mac so you can back up your smartphone. For help backing up and restoring your smartphone data, please review the BlackBerry Link User Guide for PC or Mac.
If you are using a BlackBerry OS device, download BlackBerry Desktop Software to back up your smartphone. For help backing up and restoring your data, review the BlackBerry Desktop Software user guide (PC, Mac).
Step 3 – Use self-service support options
Join the BlackBerry Support Community Forums and create a new post about your issue. Be sure to include the summary you created in step 1 because this allows community members to suggest alternative steps that may help resolve the issue you are encountering.
Review and search the BlackBerry Knowledge Base for a support article that may provide a solution to the issue you are encountering.
Step 4 – Contact your service provider or visit a BlackBerry Expert Center
If you are still unable to resolve the issue, consider contacting your service provider or BlackBerry Expert Center for additional assistance. As mentioned earlier, having your smartphone details and a summary of troubleshooting performed will help out whoever is assisting you with the issue.
For help contacting your service provider, search using your favorite browser for your service provider’s support website.
Depending on where you are located, you may have the option of visiting a BlackBerry Expert Center. For help finding a BlackBerry Expert Center near you, check out the following link: Find help at a BlackBerry Expert Center.
Frequently asked questions
Why does BlackBerry Virtual Expert need permission X, Y & Z?
For BBVE to perform specific tests, select permissions must be enabled the first time you open BBVE. You can optionally disable some or all permissions but keep in mind any tests requiring disabled permissions will not work. If you run a test that requires a specific permission such as the ability to use the camera, you will receive a notification to update your permission settings.
What tests does BBVE include?
Depending on which type of BlackBerry model you are using, available tests include:
Touch Screen
Display
USB Port
Main Keypad
Keyboard
Side keys
Slider
Cameras
Camera Flash
Receiver Speaker
Loudspeaker
Stereo Loudspeaker
Stereo Headset
Microphone
Vibrator Bluetooth
Status LED
Gyroscope
Accelerometer
Orientation Sensors
HDMI Connector
USB Connector
SIM Card Connector
SD Card Connector
Wireless Charger
GPS hardware
Light Sensor
Proximity Sensor
Wi-Fi
Where can I learn more about BlackBerry Virtual Expert?
If you are using a BlackBerry 10 smartphone, check out our web-based training for an interactive overview of how to use this application or use the Help app on your smartphone and search for “BlackBerry Virtual Expert.”
Did someone help you? Click Like! Did a post solve your issue? Click Accept as Solution!
Follow me on Twitter or Google+ and subscribe to the Inside BlackBerry Help Blogthis should be floated aka stickied
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V -
How to use CAN256 and CAN257 in Labwindows CVI?
I am trying to learn about CAN programming in LabWindows CVI. None of the samples do anything other than generate cryptic error messages. I do not have a card or interface device yet, but reading in the help files I found this:
"NI-CAN provides a virtual CAN card with two interfaces, CAN256 and CAN257. The two virtual interfaces are connected by a virtual bus. When you write CAN frames to one virtual interface, those frames are received by the other virtual interface, and can be read as channels. This feature allows you to read and write CAN data in the same manner as two real CAN interfaces connected by a real CAN cable. The conversion does not require real NI CAN hardware, and your application is not required to check for specific CAN IDs."
I modified the Waveform ouput project and add CAN256 to the dropdown in the uir file. However when I run it, I get the same error message as always, error -1074388725.
Is there an example CVI code someplace to demonstrate the use of these virtual channels?Thanks Drew.
Ultimately, my customer provided me with a WriteCAN256.vi and ReadCAN257.vi that were perfect for my needs. The WriteCAN256.vi along with my NI USB 8473s allowed me to provide data collection on multiple CAN devices and to verify that my Software can handle all data types from CAN devices.
Note: My customer allowed me to share his .vi's. They are enclosed ...
Best Regards,
Don W
Attachments:
CanBus Read (Frames)_85.vi 55 KB
CanBus Write (Frames)_85.vi 48 KB -
HT4847 How to use iCloud as virtual storage
Sorry for my ignorance but does anyone know how to use iCloud as virtual storage for music n photos that I don't want on almost full iPhone? I have an iPad too and don't mind if these items are on there. Thx!
You can't. It doesn't have an option that allows you to not have a copy of the data on your Mac. You can make the suggestion to Apple at https://www.apple.com/feedback/icloud.html
-
Using slim and xfce4, something crashes on exit
I recently did a fresh install of Arch onto an older PC that I have. It's running a P4 3.06GHz, an nVidia GeForce FX 5900, and 1GB RAM. Because of the lower resources, I decided to use xfce4 and slim. I have a monitor and TV hooked up through s-video with the "seperate X screen" option. Whenever I logout of xfce (this includes, logout, reboot, shutdown), it goes to a blank black screen with a cursor at the top left and just hangs. I have slim configured to run from inittab, so it picks up after a couple seconds. However, if I run startx from console, and then logout of xfce the system just hangs and wont accept any keyboard input (including ctrl+alt+function to switch run levels). Also, if I choose to shutdown or reboot, the system will do so but the only thing I see is the blank screen until the POST. If I do a startx from console, the logout, I'm able to ssh in from my laptop, login and issue a reboot (again the screen doesn't change until the POST). Also, if I turn the "seperate x screen" option off, and just run the desktop on the monitor, it doesn't freeze. I've worked my way through a number of issues so far, but this one has me completely stumped. I'm not sure if there's something wrong with my configuration or if it's just a problem with the graphics driver. Any advice and/or help is greatly appreciated.
Here are configuration and log files:
Xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder75) Wed Jan 27 03:03:53 PST 2010
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
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 "dri2"
Load "dri"
Load "dbe"
Load "record"
Load "extmod"
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
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 "Unknown"
Option "DPI" "95 x 96"
ModelName "CMO CMC 17 AD"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV35 [GeForce FX 5900]"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5900"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5900"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
sessionstart_cmd /usr/bin/sessreg -a -l $DISPLAY %user
sessionstop_cmd /usr/bin/sessreg -d -l $DISPLAY %user
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user desktopuser
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password yes
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login yes
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
slim.log isolated reboot
/usr/bin/xauth: creating new authority file /var/run/slim.auth
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.7.5.902 (1.7.6 RC 2)
Release Date: 2010-03-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux ArchDaemon 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/49d062ba-9f7b-4d18-98f2-87249f723889 ro 5 acpi_enforce_resources=lax vga=771
Build Date: 13 March 2010 07:33:22PM
Current version of pixman: 0.16.6
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: Fri Mar 19 14:07:00 2010
(==) Using config file: "/etc/X11/xorg.conf"
/usr/bin/xauth: creating new authority file /home/desktopuser/.Xauthority
/usr/bin/startxfce4: X server already running on display :0.0
/tmp/xrdb_dysqQd:1: error: Unknown #directive "Those"
# Those are fallback settings, use the ui plugin to change it
/tmp/xrdb_dysqQd:2: error: Unknown #directive "or"
# or add your overrides to ~/.Xresources
/tmp/xrdb_dysqQd:3: error: Unknown #directive "Xft"
# Xft.hintstyle: hintnone/hintslight/hintmedium/hintfull
/tmp/xrdb_dysqQd:4: error: Unknown #directive "Xft"
# Xft hinting: 1/0
4 errors in preprocessor.
xrdb: "Xft.hinting" on line 9 overrides entry on line 6
xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7
/tmp/xrdb_dysqQd:1: error: Unknown #directive "Those"
# Those are fallback settings, use the ui plugin to change it
/tmp/xrdb_dysqQd:2: error: Unknown #directive "or"
# or add your overrides to ~/.Xresources
/tmp/xrdb_dysqQd:3: error: Unknown #directive "Xft"
# Xft.hintstyle: hintnone/hintslight/hintmedium/hintfull
/tmp/xrdb_dysqQd:4: error: Unknown #directive "Xft"
# Xft hinting: 1/0
4 errors in preprocessor.
xrdb: "Xft.hinting" on line 9 overrides entry on line 6
xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7
Agent pid 1617
xfdesktop[1637]: starting up
(xfce4-settings-helper:1639): GLib-GObject-CRITICAL **: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
(xfce4-settings-helper:1639): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
slim.log isolated logout
slim: waiting for X server to shut down..........
slim: X server slow to shut down, sending KILL signal.
slim: waiting for server to die
/usr/bin/xauth: creating new authority file /var/run/slim.auth
slim: waiting for X server to begin accepting connections
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.7.5.902 (1.7.6 RC 2)
Release Date: 2010-03-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux ArchDaemon 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/49d062ba-9f7b-4d18-98f2-87249f723889 ro 5 acpi_enforce_resources=lax vga=771
Build Date: 13 March 2010 07:33:22PM
Current version of pixman: 0.16.6
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: Fri Mar 19 14:01:03 2010
(==) Using config file: "/etc/X11/xorg.conf"
Xorg.0.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.7.5.902 (1.7.6 RC 2)
Release Date: 2010-03-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux ArchDaemon 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/49d062ba-9f7b-4d18-98f2-87249f723889 ro 5 acpi_enforce_resources=lax vga=771
Build Date: 13 March 2010 07:33:22PM
Current version of pixman: 0.16.6
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: Fri Mar 19 18:39:41 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Videocard0"
(**) |-->Screen "Screen1" (1)
(**) | |-->Monitor "Monitor1"
(**) | |-->Device "Videocard1"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "BlankTime" "0"
(**) Option "StandbyTime" "0"
(**) Option "SuspendTime" "0"
(**) Option "OffTime" "0"
(**) Option "Xinerama" "0"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) 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: 0x81e4c40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7
(--) PCI:*(0:1:0:0) 10de:0331:0000:0000 nVidia Corporation NV35 [GeForce FX 5900] rev 161, Mem @ 0xfd000000/16777216, 0xe0000000/134217728, BIOS @ 0x????????/131072
(--) PCI: (0:2:10:0) 4444:0016:0070:b7f3 Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder rev 1, Mem @ 0xf0000000/67108864
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(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="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 173.14.25 Wed Jan 27 02:59:37 PST 2010
(II) Loading extension GLX
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.5.902, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.5.902, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 173.14.25 Wed Jan 27 02:34:38 PST 2010
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(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.7.5.902, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +0+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "CRT-0"
(**) NVIDIA(0): Option "DPI" "95 x 96"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5900 (NV35) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 04.35.20.18.04
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5900 at PCI:1:0:0:
(--) NVIDIA(0): CMO CMC 17" AD (CRT-0)
(--) NVIDIA(0): NVIDIA TV Encoder (TV-0)
(--) NVIDIA(0): CMO CMC 17" AD (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): NVIDIA TV Encoder (TV-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): TV encoder: NVIDIA
(II) NVIDIA(0): Display Device found referenced in MetaMode: CRT-0
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "CRT:nvidia-auto-select+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(**) NVIDIA(0): DPI set to (95, 96); computed from "DPI" X config option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Option "TwinView" "0"
(**) NVIDIA(1): Option "MetaModes" "TV: nvidia-auto-select +0+0"
(**) NVIDIA(1): Enabling RENDER acceleration
(II) NVIDIA(1): NVIDIA GPU GeForce FX 5900 (NV35) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(1): Memory: 131072 kBytes
(--) NVIDIA(1): VideoBIOS: 04.35.20.18.04
(II) NVIDIA(1): Detected AGP rate: 8X
(--) NVIDIA(1): Interlaced video modes are supported on this GPU
(--) NVIDIA(1): Connected display device(s) on GeForce FX 5900 at PCI:1:0:0:
(--) NVIDIA(1): CMO CMC 17" AD (CRT-0)
(--) NVIDIA(1): NVIDIA TV Encoder (TV-0)
(--) NVIDIA(1): CMO CMC 17" AD (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): NVIDIA TV Encoder (TV-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): TV encoder: NVIDIA
(II) NVIDIA(1): Display Device found referenced in MetaMode: TV-0
(II) NVIDIA(1): Assigned Display Device: TV-0
(II) NVIDIA(1): Validated modes:
(II) NVIDIA(1): "TV:nvidia-auto-select+0+0"
(II) NVIDIA(1): Virtual screen size determined to be 1024 x 768
(==) NVIDIA(1): DPI set to (75, 75); computed from built-in default
(==) NVIDIA(1): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "CRT:nvidia-auto-select+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(==) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) NVIDIA(1): Initialized AGP GART.
(II) NVIDIA(1): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(1): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(1): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(1): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(1): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(1): Config Options in the README.
(II) NVIDIA(1): Setting mode "TV:nvidia-auto-select+0+0"
(II) NVIDIA(1): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(1): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(1): Backing store disabled
(==) NVIDIA(1): Silken mouse enabled
(==) NVIDIA(1): DPMS enabled
(==) RandR enabled
(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) Initializing extension GLX
(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.7.3, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.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 relative axes
(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) acceleration profile 0
(II) Macintosh mouse button emulation: 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 Microsoft Microsoft Wireless Optical Desktop® 1.00
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: always reports core events
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: Device: "/dev/input/event6"
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found 9 mouse buttons
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found scroll wheel(s)
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found relative axes
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found x and y relative axes
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found keys
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Configuring as mouse
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Configuring as keyboard
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft Wireless Optical Desktop® 1.00" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: (accel) keeping acceleration scheme 1
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: (accel) acceleration profile 0
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: initialized for relative axes.
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Desktop® 1.00
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: always reports core events
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: Device: "/dev/input/event5"
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found keys
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsoft Microsoft Wireless Optical Desktop® 1.00" (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/event2"
(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"
errors from errors.log, this stuff just repeats
Mar 19 15:44:43 ArchDaemon kernel: ACPI: I/O resource smsc47m1 [0x680-0x6ff] conflicts with ACPI region IOPM [0x680-0x6ff]
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes)
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Did you put the firmware in the hotplug firmware directory?
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes)
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Did you put the firmware in the hotplug firmware directory?
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 3
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 0
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 1
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 2
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 2
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 0
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 3
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 1
Mar 19 18:39:22 ArchDaemon kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Mar 19 18:39:22 ArchDaemon kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Mar 19 18:39:30 ArchDaemon kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
errors common in auth.log
Mar 19 13:10:25 ArchDaemon sudo: desktopuser : pam_authenticate: Conversation error ; TTY=unknown ; PWD=/home/desktopuser ; USER=root ; COMMAND=/usr/lib/xfce4/xfsm-shutdown-helper
Mar 19 13:10:30 ArchDaemon dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.10" (uid=1001 pid=1567 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1336 comm="/usr/sbin/hald))I recently did a fresh install of Arch onto an older PC that I have. It's running a P4 3.06GHz, an nVidia GeForce FX 5900, and 1GB RAM. Because of the lower resources, I decided to use xfce4 and slim. I have a monitor and TV hooked up through s-video with the "seperate X screen" option. Whenever I logout of xfce (this includes, logout, reboot, shutdown), it goes to a blank black screen with a cursor at the top left and just hangs. I have slim configured to run from inittab, so it picks up after a couple seconds. However, if I run startx from console, and then logout of xfce the system just hangs and wont accept any keyboard input (including ctrl+alt+function to switch run levels). Also, if I choose to shutdown or reboot, the system will do so but the only thing I see is the blank screen until the POST. If I do a startx from console, the logout, I'm able to ssh in from my laptop, login and issue a reboot (again the screen doesn't change until the POST). Also, if I turn the "seperate x screen" option off, and just run the desktop on the monitor, it doesn't freeze. I've worked my way through a number of issues so far, but this one has me completely stumped. I'm not sure if there's something wrong with my configuration or if it's just a problem with the graphics driver. Any advice and/or help is greatly appreciated.
Here are configuration and log files:
Xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder75) Wed Jan 27 03:03:53 PST 2010
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
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 "dri2"
Load "dri"
Load "dbe"
Load "record"
Load "extmod"
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
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 "Unknown"
Option "DPI" "95 x 96"
ModelName "CMO CMC 17 AD"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV35 [GeForce FX 5900]"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5900"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5900"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
sessionstart_cmd /usr/bin/sessreg -a -l $DISPLAY %user
sessionstop_cmd /usr/bin/sessreg -d -l $DISPLAY %user
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user desktopuser
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password yes
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login yes
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
slim.log isolated reboot
/usr/bin/xauth: creating new authority file /var/run/slim.auth
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.7.5.902 (1.7.6 RC 2)
Release Date: 2010-03-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux ArchDaemon 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/49d062ba-9f7b-4d18-98f2-87249f723889 ro 5 acpi_enforce_resources=lax vga=771
Build Date: 13 March 2010 07:33:22PM
Current version of pixman: 0.16.6
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: Fri Mar 19 14:07:00 2010
(==) Using config file: "/etc/X11/xorg.conf"
/usr/bin/xauth: creating new authority file /home/desktopuser/.Xauthority
/usr/bin/startxfce4: X server already running on display :0.0
/tmp/xrdb_dysqQd:1: error: Unknown #directive "Those"
# Those are fallback settings, use the ui plugin to change it
/tmp/xrdb_dysqQd:2: error: Unknown #directive "or"
# or add your overrides to ~/.Xresources
/tmp/xrdb_dysqQd:3: error: Unknown #directive "Xft"
# Xft.hintstyle: hintnone/hintslight/hintmedium/hintfull
/tmp/xrdb_dysqQd:4: error: Unknown #directive "Xft"
# Xft hinting: 1/0
4 errors in preprocessor.
xrdb: "Xft.hinting" on line 9 overrides entry on line 6
xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7
/tmp/xrdb_dysqQd:1: error: Unknown #directive "Those"
# Those are fallback settings, use the ui plugin to change it
/tmp/xrdb_dysqQd:2: error: Unknown #directive "or"
# or add your overrides to ~/.Xresources
/tmp/xrdb_dysqQd:3: error: Unknown #directive "Xft"
# Xft.hintstyle: hintnone/hintslight/hintmedium/hintfull
/tmp/xrdb_dysqQd:4: error: Unknown #directive "Xft"
# Xft hinting: 1/0
4 errors in preprocessor.
xrdb: "Xft.hinting" on line 9 overrides entry on line 6
xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7
Agent pid 1617
xfdesktop[1637]: starting up
(xfce4-settings-helper:1639): GLib-GObject-CRITICAL **: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
(xfce4-settings-helper:1639): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
slim.log isolated logout
slim: waiting for X server to shut down..........
slim: X server slow to shut down, sending KILL signal.
slim: waiting for server to die
/usr/bin/xauth: creating new authority file /var/run/slim.auth
slim: waiting for X server to begin accepting connections
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.7.5.902 (1.7.6 RC 2)
Release Date: 2010-03-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux ArchDaemon 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/49d062ba-9f7b-4d18-98f2-87249f723889 ro 5 acpi_enforce_resources=lax vga=771
Build Date: 13 March 2010 07:33:22PM
Current version of pixman: 0.16.6
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: Fri Mar 19 14:01:03 2010
(==) Using config file: "/etc/X11/xorg.conf"
Xorg.0.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.7.5.902 (1.7.6 RC 2)
Release Date: 2010-03-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux ArchDaemon 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/49d062ba-9f7b-4d18-98f2-87249f723889 ro 5 acpi_enforce_resources=lax vga=771
Build Date: 13 March 2010 07:33:22PM
Current version of pixman: 0.16.6
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: Fri Mar 19 18:39:41 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Videocard0"
(**) |-->Screen "Screen1" (1)
(**) | |-->Monitor "Monitor1"
(**) | |-->Device "Videocard1"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "BlankTime" "0"
(**) Option "StandbyTime" "0"
(**) Option "SuspendTime" "0"
(**) Option "OffTime" "0"
(**) Option "Xinerama" "0"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) 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: 0x81e4c40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7
(--) PCI:*(0:1:0:0) 10de:0331:0000:0000 nVidia Corporation NV35 [GeForce FX 5900] rev 161, Mem @ 0xfd000000/16777216, 0xe0000000/134217728, BIOS @ 0x????????/131072
(--) PCI: (0:2:10:0) 4444:0016:0070:b7f3 Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder rev 1, Mem @ 0xf0000000/67108864
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(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="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 173.14.25 Wed Jan 27 02:59:37 PST 2010
(II) Loading extension GLX
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.5.902, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.5.902, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 173.14.25 Wed Jan 27 02:34:38 PST 2010
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(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.7.5.902, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.5.902, 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
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +0+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "CRT-0"
(**) NVIDIA(0): Option "DPI" "95 x 96"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5900 (NV35) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 04.35.20.18.04
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5900 at PCI:1:0:0:
(--) NVIDIA(0): CMO CMC 17" AD (CRT-0)
(--) NVIDIA(0): NVIDIA TV Encoder (TV-0)
(--) NVIDIA(0): CMO CMC 17" AD (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): NVIDIA TV Encoder (TV-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): TV encoder: NVIDIA
(II) NVIDIA(0): Display Device found referenced in MetaMode: CRT-0
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "CRT:nvidia-auto-select+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(**) NVIDIA(0): DPI set to (95, 96); computed from "DPI" X config option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Option "TwinView" "0"
(**) NVIDIA(1): Option "MetaModes" "TV: nvidia-auto-select +0+0"
(**) NVIDIA(1): Enabling RENDER acceleration
(II) NVIDIA(1): NVIDIA GPU GeForce FX 5900 (NV35) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(1): Memory: 131072 kBytes
(--) NVIDIA(1): VideoBIOS: 04.35.20.18.04
(II) NVIDIA(1): Detected AGP rate: 8X
(--) NVIDIA(1): Interlaced video modes are supported on this GPU
(--) NVIDIA(1): Connected display device(s) on GeForce FX 5900 at PCI:1:0:0:
(--) NVIDIA(1): CMO CMC 17" AD (CRT-0)
(--) NVIDIA(1): NVIDIA TV Encoder (TV-0)
(--) NVIDIA(1): CMO CMC 17" AD (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): NVIDIA TV Encoder (TV-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): TV encoder: NVIDIA
(II) NVIDIA(1): Display Device found referenced in MetaMode: TV-0
(II) NVIDIA(1): Assigned Display Device: TV-0
(II) NVIDIA(1): Validated modes:
(II) NVIDIA(1): "TV:nvidia-auto-select+0+0"
(II) NVIDIA(1): Virtual screen size determined to be 1024 x 768
(==) NVIDIA(1): DPI set to (75, 75); computed from built-in default
(==) NVIDIA(1): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "CRT:nvidia-auto-select+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(==) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) NVIDIA(1): Initialized AGP GART.
(II) NVIDIA(1): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(1): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(1): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(1): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(1): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(1): Config Options in the README.
(II) NVIDIA(1): Setting mode "TV:nvidia-auto-select+0+0"
(II) NVIDIA(1): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(1): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(1): Backing store disabled
(==) NVIDIA(1): Silken mouse enabled
(==) NVIDIA(1): DPMS enabled
(==) RandR enabled
(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) Initializing extension GLX
(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.7.3, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.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 relative axes
(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) acceleration profile 0
(II) Macintosh mouse button emulation: 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 Microsoft Microsoft Wireless Optical Desktop® 1.00
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: always reports core events
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: Device: "/dev/input/event6"
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found 9 mouse buttons
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found scroll wheel(s)
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found relative axes
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found x and y relative axes
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found keys
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Configuring as mouse
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Configuring as keyboard
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft Wireless Optical Desktop® 1.00" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: (accel) keeping acceleration scheme 1
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: (accel) acceleration profile 0
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: initialized for relative axes.
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Desktop® 1.00
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: always reports core events
(**) Microsoft Microsoft Wireless Optical Desktop® 1.00: Device: "/dev/input/event5"
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Found keys
(II) Microsoft Microsoft Wireless Optical Desktop® 1.00: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsoft Microsoft Wireless Optical Desktop® 1.00" (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/event2"
(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"
errors from errors.log, this stuff just repeats
Mar 19 15:44:43 ArchDaemon kernel: ACPI: I/O resource smsc47m1 [0x680-0x6ff] conflicts with ACPI region IOPM [0x680-0x6ff]
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes)
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Did you put the firmware in the hotplug firmware directory?
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes)
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Did you put the firmware in the hotplug firmware directory?
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 3
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 0
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 1
Mar 19 18:39:21 ArchDaemon kernel: ivtv0: Failed to initialize on minor 2
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 2
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 0
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 3
Mar 19 18:39:22 ArchDaemon kernel: ivtv0: Failed to initialize on minor 1
Mar 19 18:39:22 ArchDaemon kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Mar 19 18:39:22 ArchDaemon kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Mar 19 18:39:30 ArchDaemon kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
errors common in auth.log
Mar 19 13:10:25 ArchDaemon sudo: desktopuser : pam_authenticate: Conversation error ; TTY=unknown ; PWD=/home/desktopuser ; USER=root ; COMMAND=/usr/lib/xfce4/xfsm-shutdown-helper
Mar 19 13:10:30 ArchDaemon dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.10" (uid=1001 pid=1567 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1336 comm="/usr/sbin/hald)) -
I have moved from a G5 Powermac to an Intel Mac Pro and selectively porting over items from a backup hard drive.
How can I access and use documents and drawings created on the PC based computer ?Clarisworks, you need Appleworks, which will only work with Mac OS X10.6.8 or earlier. See this tip if you must go newer. Mac Pros with newer hardware configuration than July 20, 2011 can't use Mac OS X 10.6.8 or earlier without this tip and then it would be Mac OS X Server. I'm not sure if the new black Mac Pro supports that configuration or not.
iPhoto, there is an iPhoto for all versions of Mac OS X.
iTunes, there is an iTunes for all versions of Mac OS X. Note with iTunes versions 11 and later, which are needed for syncing with iOS 7 or or later, you will lose coverflow, if you liked that feature. Sadly you can't run an older version of iTunes from within Mac OS X 10.9 or later.
Sketchup: http://help.sketchup.com/en/article/60107 shows the versions that will work with intermediate Mac OS X versions, and this shows the latest version: http://help.sketchup.com/en/article/36208 be sure to click on the operating system you choose to use.
GIF - Viewing GIFs Apple's Preview can do that. Editing them, I like http://www.lemkesoft.com/ Graphicconverter.
DMG is able to be opened by all versions of Mac OS X. This are just "disk images" which store programs on a virtual disk that will open when double clicked. Frequently you'll find the installer of the said program inside. To find out if the program itself is compatible with 10.7 through 10.9, see http://www.roaringapps.com/
Otherwise see the resources on:
https://discussions.apple.com/docs/DOC-2455
If you end up deciding to stick with Snow Leopard. -
Difference between logical and virtual terms
Hello,
This is not purely oracle question; but in documentation so many times we find 2 terms:
A. Logical
B.Virtual.
So what is the principle difference between logical and virtual? As I know physical is that which I can see and touch; while logical/virtual is that is imaginary. We say tablespace is logical not virtual; while Java Virtual Machine; not Java Logical Machine. So I want to know; what is the principle difference; why two words for an imaginary thing. Before posting question; I searched in google as “Difference between virtual and logical” but I couldn’t found the answer.
Please quote your comments.
Thanks & Kind Regards
Girish SharmaGirish,
I wont say that I am correcting you as this is like that half glass full/empty thing.May be what I see is half empty , you would see the same as half full.
Well now coming to the explanation.I am saying honestly , I got more confused after reading your definitions.What do you mean by saing that tablespace is not virtual.I see it as purely virtual.We don't say it as virtual tablespace or logical tablespace but it is actualy logical/virtual, having no existance but just the definition right?
How can you say that the size of virtual is larger than logcial?The size of tablespace is actualy the sum total of size of datafiles.So it actualy becomes very larger right?Much larger than JVM which is of few megs only.
The point 3 totally knocked me out.I have no idea what you said.
Ok I tell you this.Just remember the definition that Hans gave already.If you ask me than its the best definition that we can have. Just remember this and if some one asks you more further than give them your point 3 definition and tell them understand this ;-).Please don'tmind I am just kidding. Its just semantics.Don't get lost into it.You will find many people using both the terms interchangibly. So its ok.I shall stick with Hans's defintion,simple and concise.There are lot more other topics to dig upon in oracle.I can mail you lots of them.Spend time on those.Don't think that I am demotivating you.I understand you asked only because you have a doubt.But we got a good resolution of it and beyond that, its not of much use to dig it atleast not in the technial terms.
Cheers
Aman....
PS:Are you on oraclecommunity.net? -
Load balancing weirdness using NAT and same-metric route
Hi.
I'm trying to set up a double-WAN load-balancing scenario:
I decided to attempt the "multiple same-metric routes with NAT" approach so I went for the example used in the IOS NAT Load-Balancing for Two ISP Connections Configuration Guide [1].
I decided to use an upside-down Cisco 871-SEC/K9: use Vlan1 and Vlan2 for the routers and Fa4 for the LAN. I am hoping this is not an issue.
There is this weirdness with some connections, particularly FTP. I pinpointed the problem to the following scenario: if I do a couple of pings to 100.1.1.1 using the FastEthernet4 as the source address, this is what I get in the logs:
=== PING 1 ECHO REQUEST ===
*Mar 3 04:38:43.521: IP: tableid=0, s=192.168.60.4 (FastEthernet4), d=100.1.1.1 (Vlan1), routed via RIB
*Mar 3 04:38:43.521: NAT: s=192.168.60.4->10.129.124.2, d=100.1.1.1 [14152]
*Mar 3 04:38:43.521: IP: s=10.129.124.2 (FastEthernet4), d=100.1.1.1 (Vlan1), g=10.129.124.1, len 60, forward
*Mar 3 04:38:43.521: ICMP type=8, code=0
=== PING 1 ECHO REPLY ===
*Mar 3 04:38:45.589: NAT*: s=100.1.1.1, d=10.129.124.2->192.168.60.4 [19824]
*Mar 3 04:38:45.589: IP: tableid=0, s=100.1.1.1 (Vlan1), d=192.168.60.4 (FastEthernet4), routed via RIB
*Mar 3 04:38:45.589: IP: s=100.1.1.1 (Vlan1), d=192.168.60.4 (FastEthernet4), g=192.168.60.4, len 60, forward
*Mar 3 04:38:45.589: ICMP type=0, code=0
=== (something else) ===
*Mar 3 04:38:52.353: RT: SET_LAST_RDB for 0.0.0.0/0
OLD rdb: via 10.129.124.33, Vlan2
NEW rdb: via 10.129.124.1, Vlan1
=== PING 2 ECHO REQUEST ===
*Mar 3 04:38:52.353: IP: tableid=0, s=192.168.60.4 (FastEthernet4), d=100.1.1.1 (Vlan2), routed via RIB
*Mar 3 04:38:52.353: NAT: s=192.168.60.4->10.129.124.2, d=100.1.1.1 [14159]
*Mar 3 04:38:52.353: IP: s=10.129.124.2 (FastEthernet4), d=100.1.1.1 (Vlan2), g=10.129.124.33, len 60, forward
*Mar 3 04:38:52.353: ICMP type=8, code=0
=== PING 2 ECHO REPLY ===
*Mar 3 04:38:53.029: NAT*: s=100.1.1.1, d=10.129.124.2->192.168.60.4 [19825]
*Mar 3 04:38:53.029: IP: tableid=0, s=100.1.1.1 (Vlan1), d=192.168.60.4 (FastEthernet4), routed via RIB
*Mar 3 04:38:53.033: IP: s=100.1.1.1 (Vlan1), d=192.168.60.4 (FastEthernet4), g=192.168.60.4, len 60, forward
*Mar 3 04:38:53.033: ICMP type=0, code=0
In the section "Ping 2 Echo Request" line 2 shows the NAT translating the packet to the address for the first provider but line 3 shows it routing it through the second one.
In this case, the ICMP packet goes through but it is problematic if the ISP restricts the service by source-address (like RPF) or there is some acceleration mechanism inside the provider cloud, other than just plain routing.
What am I missing? Here is the relevant part of the configuration. I deliberately disabled CEF to be able to debug the messages, but I *think* this may be altering the actual router behavior. This router does not have a "debug ip cef packet" command.
no ip cef
ip dhcp pool lan-side
import all
network 192.168.60.0 255.255.255.0
default-router 192.168.60.1
domain-name doublewan.local
dns-server 8.8.8.8 8.8.4.4
lease infinite
ip domain name doublewan
interface FastEthernet0
!doesn't appear on running-config: vlan 1 is the default access vlan
!switchport access vlan 1
interface FastEthernet1
switchport access vlan 2
interface FastEthernet2
shutdown
interface FastEthernet3
shutdown
interface FastEthernet4
ip address 192.168.60.1 255.255.255.0
ip nat inside
ip virtual-reassembly
no ip route-cache
duplex auto
speed auto
interface Vlan1
ip address 10.129.124.2 255.255.255.224
ip nat outside
ip virtual-reassembly
no ip route-cache
interface Vlan2
ip address 10.129.124.35 255.255.255.224
ip nat outside
ip virtual-reassembly
no ip route-cache
ip route 0.0.0.0 0.0.0.0 Vlan1 10.129.124.1
ip route 0.0.0.0 0.0.0.0 Vlan2 10.129.124.33
ip nat inside source route-map nat1 interface Vlan1 overload
ip nat inside source route-map nat2 interface Vlan2 overload
ip access-list standard acl4-nexthop-vlan1
permit 10.129.124.1
ip access-list standard acl4-nexthop-vlan2
permit 10.129.124.33
route-map nat2 permit 10
match ip address 102
match ip next-hop acl4-nexthop-vlan2
match interface Vlan2
route-map nat1 permit 10
match ip address 101
match ip next-hop acl4-nexthop-vlan1
match interface Vlan1
control-plane
Of course, there is some configuration pending for redundancy and stuff.
Thanks a lot in advance.
[1] http://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/100658-ios-nat-load-balancing-2isp.htmlHello.
This might be a bug in debug command or the IOS (without ip cef) you use; as routing is done before NAT (inside to outside).
To make sure it works fine with ip cef, just enable strict uRPF (or just ACL) on .1 and .33 interfaces and see if you see any packet sent over wrong interface.
PS: please check "sh ip cef 100.1.1.1"; I guess ip cef would tell you "per-destination sharing".
Maybe you are looking for
-
HT4906 Can a pdf be saved on iCloud?
Can a pdf be saved on iCloud?
-
hiall, here i have a scenario where i have to give Advance shipment Notification to the customer ,now i have made the basic setting of EDI and the output cond type i'm using is LAVA.which is in the delivery. now when i do issue output i could see the
-
Connecting 3rd party devices to my computer
How do I connect lap tops and i phones to my imac so that they can access app stores etc?
-
Showing Horizontal scroll bar in JTabel
I am creating a table as follows: private ResultSetTableModel tableModel; // create TableModel for results of query tableModel = new ResultSetTableModel( JDBC_DRIVER, DATABASE_URL, USERNAME, PASSWORD, DEFAULT_QUERY ); // create JTable delegate for ta
-
Hi all, I am trying to build a primary key based on a sequence. 1. i built the table 2. i built the sequence 3. i execute the following code CREATE OR REPLACE TRIGGER TBL1_ID_TRG BEFORE INSERT ON TBL1 FOR EACH ROW BEGIN SELECT TBL1_M_ID_SEQ.nextval I