Unity analog module to harris 20-20Lx integration

I will integrate a unity via analog module to harris pbx 20-20LX and I read the cisco integration guide but anybody knows what means?:
phone system? means pbx?
The voice messaging ports in the phone system means analog ext(lines)?
What realy need for make this integration?
Thanks

Hi Mike thanks for the response.
I ended up going with SIP between the CUBE/Unity SRSV as well with dial peers for DID's (higher preference ) and the voicemail extension.
I ran into an issue where calls from Unity SRSV to registered ephones were going back out the ITSP SIP trunk. The following setting resolved it:
voice service voip
no supplementary-service sip refer
From my understanding the CUBE would attempt SIP refer first, and when refer is not an available option it will drop back to SCCP which then uses the ephone related dial peers.
Hopefully this helps someone else as well.

Similar Messages

Compilation Problem with Analog Modulation in Debug64 mod

I can compile and run the AMDemodulate program in the analog modulation toolkilt with Debug mode successfully.
However, I get the following link errors with Debug64 mod.
4 Project link errors
Undefined symbol 'ModtCreateSessionHandle' referenced in "AMDemodulation.c".
Undefined symbol 'ModtDestroySessionHandle' referenced in "AMDemodulation.c".
Undefined symbol 'ModtGetErrorString' referenced in "AMDemodulation.c".
Undefined symbol 'ModtAMDemodulate_DSB' referenced in "AMDemodulation.c".
Is there any configuration for analog module?
Thanks,
Cihan.

Hello Culas,
We do not have a time line for upgrading the modulation toolkit for CVI over to 64-bit. We also do not have a suggested method to migrate to 64 bit because of the restrictions of Windows on Windows 64(cannot use 32 bit DLL within 64 bit programs).
Anthony F.
Product Marketing Engineer
National Instruments

What SAP-modules can be SAP HR integrated with?

Hi to all!
I have a following question: What SAP-modules can be SAP HR integrated with? What HR objects and business processes could be involved in integration. What are the main advantages of this kind of integration.

The best advantage of SAP HCM is that we have Integration with other Modules
as per as SAP HCM i worked integration with FICO , SD
Business objects form FICO side will be Cost Center
and there are many Advantages with the integrations with other modules

NI DualPoint Analog Module Problems

I have been unsuccessful in making NI's 778069-08 (Analog Input) and 778070-06 (Analog Output) modules work in my FP-TB-10 bases. They physically don't plug in easily, and when they finally fit, are not seen as analog modules, in MAX - they are seen as digital!
I have ordered Grayhill 73L-IV10's and 73L-OV10's, and they fit and work perfectly, every time (and MAX sees them as analog!)
My local rep sent the modules back to Austin, and they couldn't find anything wrong with them...they are now saying there's an issue with the TB-10 bases.
I'm guessing that NI's got the modules labeled wrong, or Grayhill slid the wrong PC boards into the modules they made for NI before they epoxied them shut.
Anyone else have any experiences with this?
Mike

Like Chris , I also Just wanted to add my experiences for the benefit of others.
I had a similar problem, and desolved it exactly like Cheris.
But I still have an Undissolve issue with FP-AI-V100m dualpoint in FP-2015 system.
My system works 24/365 (non-stop), somtime for monthes with no problems. Then I find that the FP-2015 is not working, and all it's leds are off, although the power supplay is OK (24vdc). After a power reset the system will continue working fine for some days/hours, but then it will fell down again, and so on..
I replaced the TB-10 (type D), the FP-2015, the Power supplay, but the issue have not "stop" until I replaced the PF-AI-V100m. Not really stop, but give me some more monthes of silence.
I test the voltage of the Oxygen sensor (only 1 is connected to that DualPoint), and it is in the range ot 0-100mv.
I replaced the FP-AI-V100m already twice, the "bad" DualPoint caused the same problem when it is connected to a different Controler.
I have a second system, with a same configuration, and have no problems their ..
After more than a year of problems, reading also other's problems in this forum,
I'm changing sensors and TB-10 to FP-AI-110, with a hope that it will be more stable.
My configuration is:
FP-2015, TB-10 (FP-RTD-PT100 in slot 1, FP-AI-v100m in slot 2), FP-DI-301, FP-DO-420 *2 modules.
I use 2 24vdc power suppliers, each with 2 separate V.out for the different modules.
Try to take over the world!

Knowledge Modules for ODI- Oracle BAM Integration

Could we please know who develops the Knowledge Modules for ODI- Oracle BAM Integration?
Is there a separate team that develops these KMs?
Learnt that ODI development team does not develop these KMs.

BAM development team is responsible for the BAM ODI KMs.

Creating Assets with modules (PO-AP-PA-FA) integration

FA or PA
We make use of various modules that are integrated. The current workflow of creating Capital Assets using PO-AP-PA-FA is time consuming. At times when PRC:Interface Supplier brings in the costs to capitalize, the users do not have a clue which assets will need to be created under what projects ?. Does your company make use of custom reports or some sort of automation to automatically create assets in PA.
I will be interested in hearing back if any of you make make use of following:
* Make use of FA module to maintain all assets and then use APIs to transfer assets back into PA. (pa_project_asset_lines_all a, pa_project_assets_all)
* Some automation process to automatically create Capital Asset items in PA.
Thanks,
Roshan

Hello!
My office is interested in learning the exact implementation and uses of Oracle's Fixed Assets. We are located in Kennett Square, PA. We were curious of if there is a charge and if so what this cost would be for us to be trained. In total there are 5 people that would need training.
Please respond to my email at [email protected]
Thank you,
Megan Galbraith

COBRAS Import for Unity Connection 8.5 and Subscriber LDAP Integration Status

Using COBRAS Import for Unity Connection 1.1 Build 212 with Unity 4.2 Voicemail Only and Connection 8.5(1)SU1 with LDAP Directory Integration
When I run COBRAS the old alias matches the new alias and my desire is for subscribers being moved to be LDAP inegrated. However after COBRAS runs, the radio box for LDAP Integration Status on the subscriber is set to Do Not Integrate with LDAP Directory. Is there a way for COBRAS to select Integrate with LDAP Directory when the alias matches on LDAP?

Hi ben,
If you are just importing from and not authenticating against LDAP, then the PIN comes
from the Connection Template you used to build the users;
Note that no passwords or PINs are copied from the LDAP directory to the Connection database. If
you want Connection users to authenticate against the LDAP directory, see the “LDAP
Authentication” section on page 9-7.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg040.html
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen

COBRAS migration from Unity 5 (Domino) to CXN 8 (AD Integrated)

Customer has an existing Unity 5 platform on a Domino back end. We will be doing a COBRAS export and import into the new Unity Connection 8 system.
I'm trying to understand the following:
1. If the users in Unity Connection are to be AD integrated, can COBRAS handle this as part of the import? I'm not seeing anything that says it can, or it can't, or really addressing this situation at all. I'm thinking the mailboxes may need to be created via LDAP import first, and then COBRAS import run in. Can anyon sanity check me on this?
2. When running COBRAS export out of a Domino backed Unity 5, what rights does the tool need (i.e. what account should be used to collect the export package)?
TIA for suggestions.
Cliff

The help files are pretty giant and I’ll be the first to admit probably not organized perfectly – sometimes helps to search on “LDAP” or the like in this case. There’s a section titled “Important Note About Importing Users into Connection with LDAP Integration” that’s relevant here: http://www.ciscounitytools.com/Applications/General/COBRAS/Help/COBRAS_Briefcase/COBRAS_Briefcase.htm#_Toc276653859
Short version it’s best to import users first (regardless of what the external integration is) and then import COBRAS over those users. At the time that was written this was the ONLY option as “tying users” back to LDAP accounts after creating them in Connection first was not possible. Now that is possible but I still consider it less than ideal – nicer to import first and then update user data with a COBRAS import over it.
COBRAS uses the rights of the AvCsMgr service to gain access to the mailstore (either Exchange or Domino) – it’s going through the DOH for this instead of, say, ExMErge with Exchange that DiRT uses – so you need to be logged in as the account associated with AVCsMgr – this is actually mentioned numerous times in the help but notably under the Requirements/Special Notes there’s this note:
“NOTE: When backing up Unity versions, if you select the option to include messages you MUST be logged in as the account associated with the AvCsMgr service. If not COBRAS Export will not allow the export to start until you uncheck the option for message export. There is no exception or work around for this, you have to be logged in as that account to export messages.”

WIC-2am analog module as a back up interface for adsl

dear all
im planning to take adsl link in my branch for vpn connectivity.The router will be 1841 and planning to put wic-1 adsl but in case if my adsl link is down i need connectivity so for that im planning to put one wic-2AM card and connect a PSTN line to it, so that it will dial to the provider and my people in branch can continue working.
this is my plan.so when the adsl come up will this wic-2AM will shut down and adsl will come up? can i configure in that way?
kindly suggest.
regrads
Binoy

If you are using netctl, something like the following may work:
# /etc/systemd/system/eth0_phy.service
[Unit]
Description=Custom phy setting for eth0
Before=[email protected]
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=ethtool -s eth0 speed 100 duplex full autoneg off
ExecStop=ethtool -s eth0 autoneg on
[Install]
RequiredBy=[email protected]
Install the above file, then run
systemctl daemon-reload
netctl reenable eth0
netctl restart eth0
That said, there is probably an underlying hardware problem which will continue to make the link unreliable. Since autonegotiation succeeds with a different link partner, I would suspect the router. Did you try a different port on the router?

"Chassis Temperature" in Analog Input Module for FPGA (cRIO-9201)

I have just gotten my cRIO with a analog module (9201) and a digital output module (9472).
When I place an Analog Input Module on my block diagram and double click it, I can choose from the following inputs:
Channel 0 through Channel 7
AND
Chassis Temperature
I have tried to find any documentation for this "Chassis Temperature" but so far without success.
If I read this input and feed it straight to an indicator, I get values in the range of 120 to 150.. Now, without more information, this number is rather useless. Does anyone know how to transfer this data to a temperature (either in the Celcius scale or the Fahrenheit scale)?
Thank you!
Project Engineer
LabVIEW 2009
Run LabVIEW on WinXP and Vista system.
Used LabVIEW since May 2005
Certifications: CLD and CPI certified
Currently employed.

I still did not find any documentation for this "feature" but I lucked out and found the following:
in the folder: \labview 7.1\examples\FPGA\CompactRIO\cRIO-910x\
you should have a file called:
cRIO-910x support files.llb
in this there is a convert to temperature vi.
To get the raw data as a temperature, it looks like all you have to do is divide the binary data by 4 and the answer will be in Celcius.
Project Engineer
LabVIEW 2009
Run LabVIEW on WinXP and Vista system.
Used LabVIEW since May 2005
Certifications: CLD and CPI certified
Currently employed.

Can I work backward from APO CIF function module to ECC Integration Model

On our APO box, I have activated the "new-style" BAdI which is called by the CIF function module /SAPAPO/CIF_TLANE_INBOUND:
CALL BADI lr_ref_cif_enhance->inbound_tlane
How can I find out what the business analysts have to do in their ECC Integration Model
to make sure that the CIF_TLANE_INBOUND function module is called when the Integration Model is activated (so that the BAdI will also fire)?.
Our current Integration Model does fire the BAdI /SAPAPO/IF_EX_TR_TRANSFER , but not the "enhance inbound tlane" BAdI called by CIF_TLANE_INBOUND.
So ...to restate the question:
How do I figure out what I have to tell the business analysts to do in their Integration Model to make sure that CIF_TLANE_INBOUND is called when the model is actrivated ???

Hi David,
I was away in a long meeting and just came back. A quick check in another R/3 (Enterprise) system showed the following:
There is no FM in the R/3 Enterprise box as CIF_TLANE_SEND and in APO (SCM4.1)
/SAPAPO/CIF_TLANE_INBOUND. This is not surprising esp when I check the other system versions based on which I did the initial research. It was ECC 6.0 with Enterprise Extension DFPS switched on (checked SWF5) and the APO system SCM 5.0.
Lucky me I checked the internal Sandbox systems instead of my client systems otherwise I would have posted there is no FM CIF_TLANE_SEND
Forget the SD Scheduling Agreement object I mentioned in the previous reply. That master data object will not trigger FM CIF_TLANE_SEND. I found the correct FM for it CIF_SDLS_SEND on R/3 side and /SAPAPO/CIF_TPSCO_INBOUND on the APO side.
So you have to necessarily use the BADI or User Exit enhancements for TPSRC and NOT TLANE.
In any case if its a Contract or Scheduling Agreement or Purchasing Inforecord master in R/3 (or ECC any version) then TPSRC is the FM used to create External Procurement Relationships (txn /SAPAPO/PWBSRC1) in APO during CIF transfer. Also a corresponding Transportation Lane (txn /SAPAPO/SCC_TL1) gets created when the Procurement Relationship is added in APO. Otherwise you can always manually create a transportation lane in APO which is an important master data for External Procurement Order / Requisition creation in APO.
Hope this helps. I am logging off for today - so no more further digging. But thanks to you I discovered another small "blackbox" of SAP. Will blog on this some time later - till then you can take a look at the [CIF Wiki|https://wiki.sdn.sap.com/wiki/display/SCM/CIF] page.
Best regards,
Somnath

Can HR Setup Integrator can be used for other module too??

Gurus, Can we create custom integrators for other modules too using HR Setup integrator. say for inventory module.???

I have used it for projects (although the integrator is created against my custom application)

Callmanager and Unity integration

Hello,
I have a CUCM 6.1.2 and Unity 5.0 running and are also integrated. Now I want to upgrade my CUCM6.1.2 to version 8.5 and also convert the device license units (DLUs) to user Connect Licenses (UCLs). The Unity 5.0 remains same.
Will this upgrade affect the already established integration between the Unity and the CUCM? Will I have to do any additional thing to maintain the integration between unity and cucm?
regards,
Peter.

Just make sure to use the right TSP and that should be it
SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified CM, and Cisco Unified CM Express
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cutspmtx.html
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

No video module?

/var/log/Xorg.0.log says, '[EE] Failed to load "fbdev" (module does not exist, 0)', and then on the next line, 'FATAL: Module i810 not found.' 'drm' also failed to open, and 'DRI' failed. 'startx' DOES open the basic X Window environment, although setting a terminal resolution in /boot/grub/menu.lst leads to screwed up terminal display after I exit X.
hwdetect doesn't list a video module.
I have Intel integrated graphics on this computer (an old Dell Dimension L733r), the hardware being a vga-compatible Intel 82810E DC-133 (CGC) chipset, according to lspci. I haved installed both available Intel drivers in the pacman database as well as vesa, and nothing changes.
Can someone at least point me in the right direction? I don't need a complete walkthrough - a few links to relevant info would be enough to give me an idea what to try next.
Thank you!

Xorg log:
[ 1084.614]
X.Org X Server 1.11.4
Release Date: 2012-01-27
[ 1084.614] X Protocol Version 11, Revision 0
[ 1084.615] Build Operating System: Linux 3.2.2-1-ARCH i686
[ 1084.615] Current Operating System: Linux Louise 3.2.7-1-ARCH #1 SMP PREEMPT Tue Feb 21 16:59:04 UTC 2012 i686
[ 1084.615] Kernel command line: root=/dev/disk/by-uuid/66114814-cb1f-4868-bc93-cfab0c21eb06 ro
[ 1084.615] Build Date: 29 January 2012 03:41:53PM
[ 1084.615]
[ 1084.615] Current version of pixman: 0.24.4
[ 1084.616] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 1084.616] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1084.617] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 6 07:58:19 2012
[ 1084.654] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 1084.655] (==) No Layout section. Using the first Screen section.
[ 1084.655] (==) No screen section available. Using defaults.
[ 1084.655] (**) |-->Screen "Default Screen Section" (0)
[ 1084.655] (**) | |-->Monitor "<default monitor>"
[ 1084.672] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 1084.673] (==) Automatically adding devices
[ 1084.673] (==) Automatically enabling devices
[ 1084.716] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 1084.716] Entry deleted from font path.
[ 1084.716] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1084.716] Entry deleted from font path.
[ 1084.716] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1084.716] Entry deleted from font path.
[ 1084.717] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1084.717] Entry deleted from font path.
[ 1084.717] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 1084.717] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1084.717] Entry deleted from font path.
[ 1084.717] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 1084.717] (==) FontPath set to:
/usr/share/fonts/misc/
[ 1084.717] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 1084.717] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 1084.735] (II) Loader magic: 0x8228580
[ 1084.735] (II) Module ABI versions:
[ 1084.735] X.Org ANSI C Emulation: 0.4
[ 1084.735] X.Org Video Driver: 11.0
[ 1084.735] X.Org XInput driver : 13.0
[ 1084.735] X.Org Server Extension : 6.0
[ 1084.737] (--) PCI:*(0:0:1:0) 8086:7125:8086:4332 rev 3, Mem @ 0xf8000000/67108864, 0xffa80000/524288
[ 1084.737] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 1084.738] (II) LoadModule: "extmod"
[ 1084.765] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 1084.793] (II) Module extmod: vendor="X.Org Foundation"
[ 1084.793] compiled for 1.11.4, module version = 1.0.0
[ 1084.793] Module class: X.Org Server Extension
[ 1084.793] ABI class: X.Org Server Extension, version 6.0
[ 1084.793] (II) Loading extension MIT-SCREEN-SAVER
[ 1084.794] (II) Loading extension XFree86-VidModeExtension
[ 1084.794] (II) Loading extension XFree86-DGA
[ 1084.794] (II) Loading extension DPMS
[ 1084.794] (II) Loading extension XVideo
[ 1084.794] (II) Loading extension XVideo-MotionCompensation
[ 1084.794] (II) Loading extension X-Resource
[ 1084.794] (II) LoadModule: "dbe"
[ 1084.794] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 1084.808] (II) Module dbe: vendor="X.Org Foundation"
[ 1084.808] compiled for 1.11.4, module version = 1.0.0
[ 1084.809] Module class: X.Org Server Extension
[ 1084.809] ABI class: X.Org Server Extension, version 6.0
[ 1084.809] (II) Loading extension DOUBLE-BUFFER
[ 1084.809] (II) LoadModule: "glx"
[ 1084.809] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1084.874] (II) Module glx: vendor="X.Org Foundation"
[ 1084.874] compiled for 1.11.4, module version = 1.0.0
[ 1084.874] ABI class: X.Org Server Extension, version 6.0
[ 1084.874] (==) AIGLX enabled
[ 1084.874] (II) Loading extension GLX
[ 1084.874] (II) LoadModule: "record"
[ 1084.875] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 1084.889] (II) Module record: vendor="X.Org Foundation"
[ 1084.889] compiled for 1.11.4, module version = 1.13.0
[ 1084.889] Module class: X.Org Server Extension
[ 1084.889] ABI class: X.Org Server Extension, version 6.0
[ 1084.889] (II) Loading extension RECORD
[ 1084.890] (II) LoadModule: "dri"
[ 1084.890] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 1084.909] (II) Module dri: vendor="X.Org Foundation"
[ 1084.909] compiled for 1.11.4, module version = 1.0.0
[ 1084.909] ABI class: X.Org Server Extension, version 6.0
[ 1084.909] (II) Loading extension XFree86-DRI
[ 1084.909] (II) LoadModule: "dri2"
[ 1084.910] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 1084.911] (II) Module dri2: vendor="X.Org Foundation"
[ 1084.911] compiled for 1.11.4, module version = 1.2.0
[ 1084.911] ABI class: X.Org Server Extension, version 6.0
[ 1084.911] (II) Loading extension DRI2
[ 1084.911] (==) Matched intel as autoconfigured driver 0
[ 1084.911] (==) Matched vesa as autoconfigured driver 1
[ 1084.912] (==) Matched fbdev as autoconfigured driver 2
[ 1084.912] (==) Assigned the driver to the xf86ConfigLayout
[ 1084.912] (II) LoadModule: "intel"
[ 1084.931] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 1085.012] (II) Module intel: vendor="X.Org Foundation"
[ 1085.012] compiled for 1.11.2, module version = 2.17.0
[ 1085.012] Module class: X.Org Video Driver
[ 1085.012] ABI class: X.Org Video Driver, version 11.0
[ 1085.012] (II) LoadModule: "vesa"
[ 1085.013] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 1085.025] (II) Module vesa: vendor="X.Org Foundation"
[ 1085.025] compiled for 1.11.1, module version = 2.3.0
[ 1085.025] Module class: X.Org Video Driver
[ 1085.025] ABI class: X.Org Video Driver, version 11.0
[ 1085.025] (II) LoadModule: "fbdev"
[ 1085.034] (WW) Warning, couldn't open module fbdev
[ 1085.034] (II) UnloadModule: "fbdev"
[ 1085.034] (II) Unloading fbdev
[ 1085.034] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 1085.034] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
[ 1085.035] (II) VESA: driver for VESA chipsets: vesa
[ 1085.036] (--) using VT number 7
[ 1085.217] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 1085.218] (WW) Falling back to old probe method for vesa
[ 1085.240] (II) Loading sub module "vgahw"
[ 1085.240] (II) LoadModule: "vgahw"
[ 1085.241] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 1085.242] (II) Module vgahw: vendor="X.Org Foundation"
[ 1085.242] compiled for 1.11.4, module version = 0.1.0
[ 1085.242] ABI class: X.Org Video Driver, version 11.0
[ 1085.243] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 16/16
[ 1085.243] (==) intel(0): Depth 16, (==) framebuffer bpp 16
[ 1085.243] (==) intel(0): RGB weight 565
[ 1085.243] (==) intel(0): Default visual is TrueColor
[ 1085.243] (II) Loading sub module "xaa"
[ 1085.243] (II) LoadModule: "xaa"
[ 1085.244] (II) Loading /usr/lib/xorg/modules/libxaa.so
[ 1085.281] (II) Module xaa: vendor="X.Org Foundation"
[ 1085.281] compiled for 1.11.4, module version = 1.2.1
[ 1085.281] ABI class: X.Org Video Driver, version 11.0
[ 1085.281] (II) Loading sub module "vbe"
[ 1085.281] (II) LoadModule: "vbe"
[ 1085.281] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 1085.295] (II) Module vbe: vendor="X.Org Foundation"
[ 1085.295] compiled for 1.11.4, module version = 1.1.0
[ 1085.295] ABI class: X.Org Video Driver, version 11.0
[ 1085.295] (II) Loading sub module "int10"
[ 1085.295] (II) LoadModule: "int10"
[ 1085.296] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 1085.309] (II) Module int10: vendor="X.Org Foundation"
[ 1085.310] compiled for 1.11.4, module version = 1.0.0
[ 1085.310] ABI class: X.Org Video Driver, version 11.0
[ 1085.310] (II) intel(0): initializing int10
[ 1085.312] (II) intel(0): Primary V_BIOS segment is: 0xc000
[ 1085.314] (II) intel(0): VESA BIOS detected
[ 1085.314] (II) intel(0): VESA VBE Version 2.0
[ 1085.314] (II) intel(0): VESA VBE Total Mem: 1024 kB
[ 1085.314] (II) intel(0): VESA VBE OEM: Intel810(TM) Graphics Chip Accelerated VGA BIOS
[ 1085.314] (II) intel(0): VESA VBE OEM Software Rev: 3.0
[ 1085.314] (II) intel(0): VESA VBE OEM Vendor: Intel Corporation
[ 1085.314] (II) intel(0): VESA VBE OEM Product: i810 Graphics Controller
[ 1085.314] (II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
[ 1085.314] (II) Loading sub module "ddc"
[ 1085.314] (II) LoadModule: "ddc"
[ 1085.314] (II) Module "ddc" already built-in
[ 1085.340] (II) intel(0): VESA VBE DDC supported
[ 1085.340] (II) intel(0): VESA VBE DDC Level 2
[ 1085.340] (II) intel(0): VESA VBE DDC transfer in appr. 1 sec.
[ 1085.951] (II) intel(0): VESA VBE DDC read successfully
[ 1085.952] (II) intel(0): Manufacturer: DEL Model: a000 Serial#: 842089268
[ 1085.952] (II) intel(0): Year: 2000 Week: 30
[ 1085.952] (II) intel(0): EDID Version: 1.2
[ 1085.952] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 1085.952] (II) intel(0): Sync: Separate
[ 1085.952] (II) intel(0): Max Image Size [cm]: horiz.: 27 vert.: 20
[ 1085.952] (II) intel(0): Gamma: 2.87
[ 1085.952] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 1085.952] (II) intel(0): First detailed timing is preferred mode
[ 1085.952] (II) intel(0): redX: 0.619 redY: 0.350 greenX: 0.305 greenY: 0.600
[ 1085.952] (II) intel(0): blueX: 0.154 blueY: 0.064 whiteX: 0.280 whiteY: 0.311
[ 1085.952] (II) intel(0): Supported established timings:
[ 1085.952] (II) intel(0): 720x400@70Hz
[ 1085.952] (II) intel(0): 640x480@60Hz
[ 1085.952] (II) intel(0): 640x480@75Hz
[ 1085.952] (II) intel(0): 800x600@60Hz
[ 1085.952] (II) intel(0): 800x600@75Hz
[ 1085.952] (II) intel(0): 1024x768@60Hz
[ 1085.952] (II) intel(0): Manufacturer's mask: 0
[ 1085.952] (II) intel(0): Supported standard timings:
[ 1085.953] (II) intel(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
[ 1085.953] (II) intel(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
[ 1085.953] (II) intel(0): Supported detailed timing:
[ 1085.953] (II) intel(0): clock: 49.5 MHz Image Size: 270 x 202 mm
[ 1085.953] (II) intel(0): h_active: 800 h_sync: 816 h_sync_end 896 h_blank_end 1056 h_border: 0
[ 1085.953] (II) intel(0): v_active: 600 v_sync: 601 v_sync_end 604 v_blanking: 625 v_border: 0
[ 1085.953] (II) intel(0): Serial No: 82CGN07J21C4
[ 1085.953] (II) intel(0): Monitor name: DELL E551
[ 1085.953] (II) intel(0): Ranges: V min: 50 V max: 120 Hz, H min: 30 H max: 54 kHz, PixClock max 75 MHz
[ 1085.953] (II) intel(0): EDID (in hex):
[ 1085.953] (II) intel(0): 00ffffffffffff0010ac00a034433132
[ 1085.953] (II) intel(0): 1e0a0102081b14bbeaa2ae9e594e9927
[ 1085.953] (II) intel(0): 10474fa5480031594559010101010101
[ 1085.953] (II) intel(0): 01010101010156132000315819201050
[ 1085.953] (II) intel(0): 13000eca1000001e000000ff00383243
[ 1085.953] (II) intel(0): 474e30374a323143340a000000fc0044
[ 1085.953] (II) intel(0): 454c4c20453535310a202020000000fd
[ 1085.953] (II) intel(0): 0032781e3607000a20202020202000c0
[ 1085.953] (II) intel(0): EDID vendor "DEL", prod id 40960
[ 1085.954] (II) intel(0): Using EDID range info for horizontal sync
[ 1085.954] (II) intel(0): Using EDID range info for vertical refresh
[ 1085.954] (II) intel(0): Printing DDC gathered Modelines:
[ 1085.954] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 1085.954] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 1085.954] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 1085.954] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 1085.954] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 1085.954] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 1085.954] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
[ 1085.954] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
[ 1085.955] (II) intel(0): Integrated Graphics Chipset: Intel(R) i810e
[ 1085.955] (--) intel(0): Chipset: "i810e"
[ 1085.955] (--) intel(0): Linear framebuffer at 0xF8000000
[ 1085.955] (--) intel(0): IO registers at addr 0xFFA80000
[ 1085.955] (II) intel(0): Kernel reported 109056 total, 0 used
[ 1085.955] (II) intel(0): I810CheckAvailableMemory: 436224k available
[ 1085.955] (==) intel(0): Will alloc AGP framebuffer: 24576 kByte
[ 1085.955] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[ 1085.955] (II) intel(0): <default monitor>: Using hsync range of 30.00-54.00 kHz
[ 1085.955] (II) intel(0): <default monitor>: Using vrefresh range of 50.00-120.00 Hz
[ 1085.955] (II) intel(0): <default monitor>: Using maximum pixel clock of 75.00 MHz
[ 1085.955] (II) intel(0): Estimated virtual size for aspect ratio 1.3500 is 1024x768
[ 1085.955] (II) intel(0): Clock range: 9.50 to 163.00 MHz
[ 1085.956] (II) intel(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768i" (unknown reason)
[ 1085.956] (II) intel(0): Not using default mode "512x384i" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768" (hsync out of range)
[ 1085.956] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768" (hsync out of range)
[ 1085.956] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768" (hsync out of range)
[ 1085.957] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1152x864" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x960" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x960" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1792x1344" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1792x1344" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1856x1392" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1856x1392" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1920x1440" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1920x1440" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1920x1440" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "2048x1536" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "2048x1536" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "2048x1536" (width too large for virtual size)
[ 1085.959] (II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 1085.959] (--) intel(0): Virtual size is 1024x768 (pitch 1024)
[ 1085.959] (**) intel(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[ 1085.959] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 1085.959] (**) intel(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[ 1085.959] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 1085.959] (**) intel(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
[ 1085.959] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 1085.959] (**) intel(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 1085.959] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 1085.959] (**) intel(0): *Driver mode "800x600": 56.2 MHz, 53.7 kHz, 85.1 Hz
[ 1085.959] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
[ 1085.959] (**) intel(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 1085.959] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x85.1 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 1085.960] (**) intel(0): *Driver mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
[ 1085.960] (**) intel(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 1085.960] (**) intel(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 1085.960] (**) intel(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 1085.961] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
[ 1085.961] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 1085.961] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 1085.961] (**) intel(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
[ 1085.961] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 1085.961] (**) intel(0): *Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
[ 1085.961] (II) intel(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (37.9 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
[ 1085.961] (II) intel(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
[ 1085.961] (II) intel(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz)
[ 1085.961] (**) intel(0): Display dimensions: (270, 200) mm
[ 1085.961] (**) intel(0): DPI set to (96, 97)
[ 1085.961] (II) Loading sub module "fb"
[ 1085.961] (II) LoadModule: "fb"
[ 1085.962] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1085.972] (II) Module fb: vendor="X.Org Foundation"
[ 1085.972] compiled for 1.11.4, module version = 1.0.0
[ 1085.972] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1085.972] (II) Loading sub module "ramdac"
[ 1085.972] (II) LoadModule: "ramdac"
[ 1085.972] (II) Module "ramdac" already built-in
[ 1085.972] (**) intel(0): page flipping disabled
[ 1085.972] (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to enable.
[ 1085.972] (II) UnloadModule: "vesa"
[ 1085.972] (II) Unloading vesa
[ 1085.988] drmOpenDevice: node name is /dev/dri/card0
[ 1085.993] drmOpenDevice: node name is /dev/dri/card0
[ 1086.005] [drm] failed to load kernel module "i810"
[ 1086.006] (EE) [drm] drmOpen failed.
[ 1086.006] (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
[ 1086.024] (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 1086.088] (II) intel(0): Setting dot clock to 65.0 MHz [ 0x3f 0xa 0x30 ] [ 65 12 3 ]
[ 1086.089] (II) intel(0): chose watermark 0x2210e000: (tab.freq 65.0)
[ 1086.286] (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x00000000 (pgoffset 0)
[ 1086.289] (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01800000 (pgoffset 6144)
[ 1086.289] (WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 1
at offset 0x1800000 failed (Invalid argument)
[ 1086.289] (II) intel(0): Allocation of 4194304 bytes for DCACHE failed
[ 1086.289] (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x01800000 (pgoffset 6144)
[ 1086.290] (II) intel(0): Allocated of 4096 bytes for HW cursor
[ 1086.290] (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x01801000 (pgoffset 6145)
[ 1086.290] (II) intel(0): Allocated of 16384 bytes for ARGB HW cursor
[ 1086.290] (II) intel(0): Adding 768 scanlines for pixmap caching
[ 1086.290] (II) intel(0): Allocated Scratch Memory
[ 1086.291] (II) intel(0): Using XFree86 Acceleration Architecture (XAA)
[ 1086.291] Screen to screen bit blits
[ 1086.291] Solid filled rectangles
[ 1086.291] 8x8 mono pattern filled rectangles
[ 1086.291] Indirect CPU to Screen color expansion
[ 1086.291] Solid Horizontal and Vertical Lines
[ 1086.291] Setting up tile and stipple cache:
[ 1086.291] 24 128x128 slots
[ 1086.291] 6 256x256 slots
[ 1086.291] (==) intel(0): Backing store disabled
[ 1086.291] (==) intel(0): Silken mouse enabled
[ 1086.292] (==) intel(0): DPMS enabled
[ 1086.293] (WW) intel(0): Direct rendering disabled
[ 1086.293] (==) RandR enabled
[ 1086.293] (II) Initializing built-in extension Generic Event Extension
[ 1086.293] (II) Initializing built-in extension SHAPE
[ 1086.293] (II) Initializing built-in extension MIT-SHM
[ 1086.293] (II) Initializing built-in extension XInputExtension
[ 1086.293] (II) Initializing built-in extension XTEST
[ 1086.293] (II) Initializing built-in extension BIG-REQUESTS
[ 1086.293] (II) Initializing built-in extension SYNC
[ 1086.293] (II) Initializing built-in extension XKEYBOARD
[ 1086.293] (II) Initializing built-in extension XC-MISC
[ 1086.293] (II) Initializing built-in extension SECURITY
[ 1086.293] (II) Initializing built-in extension XINERAMA
[ 1086.293] (II) Initializing built-in extension XFIXES
[ 1086.293] (II) Initializing built-in extension RENDER
[ 1086.293] (II) Initializing built-in extension RANDR
[ 1086.293] (II) Initializing built-in extension COMPOSITE
[ 1086.294] (II) Initializing built-in extension DAMAGE
[ 1086.341] (II) AIGLX: Screen 0 is not DRI2 capable
[ 1086.341] (II) AIGLX: Screen 0 is not DRI capable
[ 1086.952] (II) AIGLX: Loaded and initialized swrast
[ 1086.952] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 1087.487] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 1087.487] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 1087.487] (II) LoadModule: "evdev"
[ 1087.488] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.503] (II) Module evdev: vendor="X.Org Foundation"
[ 1087.503] compiled for 1.10.99.902, module version = 2.6.0
[ 1087.503] Module class: X.Org XInput Driver
[ 1087.503] ABI class: X.Org XInput driver, version 13.0
[ 1087.503] (II) Using input driver 'evdev' for 'Power Button'
[ 1087.503] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.503] (**) Power Button: always reports core events
[ 1087.503] (**) Power Button: Device: "/dev/input/event1"
[ 1087.504] (--) Power Button: Found keys
[ 1087.504] (II) Power Button: Configuring as keyboard
[ 1087.504] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 1087.504] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 1087.504] (**) Option "xkb_rules" "evdev"
[ 1087.504] (**) Option "xkb_model" "evdev"
[ 1087.504] (**) Option "xkb_layout" "us"
[ 1087.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 1087.647] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 1087.647] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 1087.647] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.647] (**) AT Translated Set 2 keyboard: always reports core events
[ 1087.647] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 1087.647] (--) AT Translated Set 2 keyboard: Found keys
[ 1087.647] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 1087.647] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 1087.647] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 7)
[ 1087.647] (**) Option "xkb_rules" "evdev"
[ 1087.647] (**) Option "xkb_model" "evdev"
[ 1087.647] (**) Option "xkb_layout" "us"
[ 1087.650] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event3)
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
[ 1087.650] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
[ 1087.650] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event3"
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found relative axes
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
[ 1087.650] (II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
[ 1087.650] (II) ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 1087.651] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input3/event3"
[ 1087.651] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 8)
[ 1087.651] (II) ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
[ 1087.652] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
[ 1087.653] (II) No input driver specified, ignoring this device.
[ 1087.653] (II) This device may have been added with another device file.
[ 1087.654] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 1087.654] (II) No input driver specified, ignoring this device.
[ 1087.654] (II) This device may have been added with another device file.
[ 1094.003] (II) Power Button: Close
[ 1094.003] (II) UnloadModule: "evdev"
[ 1094.003] (II) Unloading evdev
[ 1094.016] (II) AT Translated Set 2 keyboard: Close
[ 1094.016] (II) UnloadModule: "evdev"
[ 1094.016] (II) Unloading evdev
[ 1094.029] (II) ImPS/2 Logitech Wheel Mouse: Close
[ 1094.030] (II) UnloadModule: "evdev"
[ 1094.030] (II) Unloading evdev
[ 1094.102] (II) intel(0): xf86UnbindGARTMemory: unbind key 0
[ 1094.102] (II) intel(0): xf86UnbindGARTMemory: unbind key 2
[ 1094.102] (II) intel(0): xf86UnbindGARTMemory: unbind key 3
[ 1094.208] Server terminated successfully (0). Closing log file.
For some reason I suddenly can't keep my computer logged on to the forums long enough to make a post (cookie issue?), so this is sent from a computer at the library. I failed to notice your asking for the dmesg output...so I'll go home tonight and get that, too.
Thanks for your help so far! I'm still trying things, but not getting anywhere yet.

Unity configuration

Hi All,
We have a running setup on Cisco Call Manager Express along with Unity module plugged into same router.
Now,the customer has purchased separate MCS hardware for Pub & Subscriber.CCM would be implemented on CCM while Unity configuration will remain on earlier CME router.
I had a concern what all we need to configure on CCM so that Unity module on router can be integrated with CCM.
regs,
aman

Hi Aman,
One main thing you will need is a new license to work with CCM;
Say your system came with a License like this for CME (Note the CME at the end of the part#);
Cisco Unified Communications Manager Express
12-mailbox package: SCUE-LIC-12CME=
What you will need is a License like this for CCM (Note the CCM at the end of the part#);
12-mailbox package: SCUE-LIC-12CCM=
You can download this license file here;
http://www.cisco.com/cgi-bin/tablebuild.pl/cue-netmodule
From this good doc;
Upgrading or Downgrading the Cisco Unity Express License in the Same Version
http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel3_2/installation/guide_/upglic32.html
Here is the new config guide;
CallManager for Cisco Unity Express Configuration Example
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_configuration_example09186a0080289ef0.shtml
Hope this helps!
Rob

Unity analog module to harris 20-20Lx integration

Similar Messages

Maybe you are looking for