Layout Editor Does Not Match Generated PDF

We are in the process of upgrading our reports from 6.0 and 6i to 9i. The conversion process seems pretty straight forward with the exception of the layout not matching the PDF created by executing the report. We are currently using Windows to make the conversion, then compiling on a Solaris box for deployment. In the past, we were able to do the development on our window boxes, but now it would appear that we need to do the development and deployment on the Solaris box. Is this a true statement? We currently have on order the 9iDS for Solaris in case it is.
Thanks for any feedback on how we can currently work with what we have.
jim

Jim,
Windows development and Solaris deployment is truely supported with PDF in reports 9i.
This has been successful model for many customers.
If you can detail the issue you are facing, then we should be able to help.
To quickly give some steps here
1. Say if you use arial.ttf in windows for your report
2. use the same ttf for the pdf subser in solaris
3. Additinally convert that ttf to afm and pfa using the utility ttf2pt1 ( freeare in web) and put them in the
solaris oraclehome guicommmon afm directory.
4. Run the same windows rdf file now after specifyng bthe entry in pdf subset section of uifont.ali file
You will not see any font / misallignment issues
Thanks
The Oracle Reports Team

Similar Messages

JNI generated header file does not match the class file

We have had a JNI project for many years and all has been fine. Within our libraries we have several classes that have inner enum classes.
Recently we have moved to JDK1.7. Up to now when JNI generated the methods where the signature used the inner enum class, and it was an oveloaded method, we would get something like the following as the signature:
Java_PackageName_ClassName_methodName_OuterClass_00024InnerEnum_2
And the class file result of the build would look like the following:
methodName(OuterClass$InnerEnum)
Since we have moved to JDK 1.7 the header file looks like the following:
Java_PackageName_ClassName_methodName_OuterClasss_InnerEnum_2
The class file is still the same, and because of that when we run the program we get an UnsatisfiedLinkError. I understand that this error is because the VM cannot find the implementation. So why JDK 1.7 generates a header file that does not match the class file?
Thank you in advance.

I don't have 1.6 to verify but your statements about what is generated for 1.7 for the header appear correct.
The 000024 represents the '$' and for 1.7 the inner class is still named using '$'. So for example after compiling in 1.7 the inner class file is named the following...
MyClass$InnerEnum.class
So a one to one conversion should have kept the 000024 (presuming it does in fact do it that way in 1.6.)
You might want to look at the release notes for 1.7.
If you need a solution you could add a post javah step that renames the file.

IPhoto Calendar Layout does not match preview

When I am selecting a Calendar layout to use, the chose of layout I have for 3 photos and 6 photos does not match what actually shows on the screen. When I go to select my layout, the choices are to have a big photo on top and a two little ones on the bottom. The main choice of this is whether to have text on the bottom or nothing. However, when I select it shows one big photo on the left and two little photos on the left. For the six photo the choice is to have a big photo along the bottom, a medium photo in the top left quadrant, and 4 small photos in the upper right quadrant. However, after I make my selection it shows one big tall photo on the left, one medium photo in the bottom right quadrant and then 4 small photos in the upper right quadrant. The layouts I want are what is displays on the layouts button.
Does anyone have this same problem>

Some layouts in books and calendars change based on what photos you place - and the order you place them - some do not change -- for calendars you just have to experiment - for books Liz Castro has documented how they work for you - http://www.lizcastro.com/iphotobookthemes/pmwiki.php?n=Main.HomePage

Getting error when view - Requested data type does not match with existing

I have the siebel web service
In the BI publisher as mentioned in the 'Siebel_BI_Publisher_Integration_Concepts.pdf', I have imported the siebel web service
BI can recognize the 'Web service' and methods.
I have created the paramters. The data type is 'String'
When I try to view the report using the BI publisher, I am getting teh following error in th UI
"Requested data type does not match with existing data type"
This is the first time I am using BI publisher to call the Siebel web service. I don't know what this error means
I don't know whether any log file generated wit the details of this erro message
Any help is much appriciated
Thanks,
Kavitha

Hi all,
have you find a fix for this issue? Im facing the same situation, using Complex type, and String data type both in the service and Bi publisher. We are consuming CC&B services, and we have noticed this error appears when BIPublisher is running on WebLogic (10.3) but it does not appear when BIPublisher is running on OC4J , of course running the same report on both application servers.
Any idea?
Thanks a lot, regards
Nestor

ERROR ITMS-9000: "File given does not match type JPEG ... Image is likely corrupt

Hi ALl,
On compliing my book get these errors with ITunes producer...I've resaved the files out with photoshop and they seems fine?
Package Summary:
1 package(s) were not uploaded because they had problems:
          /Users/Umran/Music/iTunes Producer/Playlists/9780957408654.itmsp - Error Messages:
                    Apple's web service operation was not successful
                    Unable to authenticate the package: 9780957408654.itmsp
                    ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@1cf629f[userString=An unknown error occured while parsing. Image is likely corrupt. Exception message: null]" at Book (MZItmspBookPackage)
                    ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@1801285[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                    ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@1e056e9[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                    ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@11d58e0[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                    ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@127c00e[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                    ERROR ITMS-5107: "VirtualLandscapesTheModernEra20002012.epub: Fixed-layout books must supply a text or bodymatter starting location in the guide." at Book (MZItmspBookPackage)
Any advice??? Hope someone can help!

iBookstore Publisher Support send me a fast response email which included some helpful info:
Please make sure that all image files inside the ePub end with one of the following: ".tif", ".jpg", or ".png" and that the file itself matches the file extension type. To check if the image file matches the file extension type, please right click on the image then select "Get Info". Once the info tab appears, please make sure that the file extension type of the image file matches the "Kind" found under "General".
For further information regarding embedded images, please refer to the iBookstore Asset Guide, which is available for download in the Deliver Your Content module in iTunes Connect.
And they INCLUDED THE TRANSPORTER LOG (!), the log generated by iTunes Producer as it tries to upload a book. We were able to search for the Validation Error # within the log and find out which image Producer was trying to upload when it encountered an error. Turns out the problem was a corrupted screenshot jpeg.
Grateful!

App Signing Error, Number of Folios Does Not Match the Main Folio File

Hi All;
I have a 250 page standalone app that I am trying to compile for the Apple Store. I read through the forums and enabled "AppBuilderLoggingEnabled.cfg" in my user directory to capture the issue. Here is the snippet of the log that was created that, to me, shows why the app isn't being signed.
46386 ERROR [main] codesign.Signer - Failure during signing
java.lang.RuntimeException: invalid package, number of folios does not match the main folio file (Folio.xml or Issue.xml) 251-250
          at com.adobe.devtech.codesign.IPAOutputHelper.convertFolioProduceFormatToFolio(IPAOutputHelp er.java:272)
          at com.adobe.devtech.codesign.IPAOutputHelper.replacePlaceholderFolio(IPAOutputHelper.java:1 92)
          at com.adobe.devtech.codesign.IPAOutputHelper.execute(IPAOutputHelper.java:82)
          at com.adobe.devtech.codesign.Signer.sign(Signer.java:169)
          at com.adobe.devtech.codesign.Signer.processArgs(Signer.java:106)
          at com.adobe.devtech.codesign.Signer.main(Signer.java:46)
46388 ERROR [main] codesign.Signer - Error: invalid package, number of folios does not match the main folio file (Folio.xml or Issue.xml) 251-250
I've stripped out special characters from the article titles and re-built the app only to face the same error. I went ahead and created a new AppID in the Apple Developer Portal, created new provision files, and the error remains. I am now creating a new folio and importing the articles into the new folio to see if that will solve the "number of folios does not match" issue.
Any help or insight would be amazing. Thank you all.
-matt

I created a new folio and imported all of the articles again. After hitting "Create App" for this new folio, at about 10 pages in a "PDF Export" error stopped the create app process. I went into InDesign to update the layout for the 10th page to see that the PDF export issue was stopping me from updating the layouts as well. Something in the InDesign file wasn't playing nice with the folio creation, so I created two new InDesign files, deleted the article, and built a new article from scratch. I was able to import the new layouts as a new article to the main folio and hit "Create App" again. This time there were no issues with the creation process. I synched up the provision files in App Builder and was able to code sign the application.
I guess the moral of the story is to double and even triple check every article along the way to make sure there are no issues being introduced into the process that will ultimately cause headaches during the distribution phase of app creation!
-matt

Index seen in RoboHelp does not match CHM

I have a project which has conditional text and topics to
enable me to create different CHM Help files for four variations of
an application. I haven't noticed any problems with the indexes in
previous versions of the Help files that I've generated but am
having real problems this time.
The index looks fine in RoboHelp. It's designed so that
parent keywords which have associated sub-keywords do not have
links to help topics. It uses some re-direct topics to avoid
keywords appearing in an index for the wrong product.
When I generate the CHM files the indexes omit some parent
keywords. The sub-keywords for the missing parent keywords are
inserted under other (inappropriate) parent keywords. I've been
struggling with this for days without finding anything obvious that
might be causing the problem. In the end I deleted the index and
re-entered all index entries manually again. Unfortunately, this
didn't fix the problem.
In the end, to enable me to release the Help files I had to
use the following, unsatisfactory workaround. I went through slowly
identifying each missing parent keyword and gave each of them a
link to a topic that was displayed in all versions of the Help. So
I've ended up linking to some topics that are not particularly
appropriate, and having an index which is not consistent (some
parent keywords have links and most don't).
Any suggestions on what's going on here?

Ressucitating this topic as I have a similar issue but I am
not working on a merged project....
I am using RH for HTML X5 and generating HTML Help. I was
working on the index (adding keywords) when RH crashed on me (CPD
issue). I restored my CPD file and for some reason now, the index
from the RH project does not match the index of the compiled CHM
file! I tried opening the project.hhk file and the rhkkeyword.apj
file in a text editor and tried to find the keywords that are in
the compiled help but not in the project. Both files looked like my
index from within the RH project, i.e. they did not have these
extra keywords. Basically, I have got a few keywords stored
somewhere, but not in my hhk or apj files, that I cannot edit.
Any ideas of where these could be stored (CPD?). How can I
get to them? I need to edit the topics linked to one of these
keywords and cannot do this. I tried re-adding the keyword to my
index in RH but the software tells me it already exists (and I
cannot see it)...
Thanks in advance for any assistance,

Job Cancelled with an error "Data does not match the job def: Job terminat"

Dear Friends,
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job   Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?
Edited by: dharmendra gali on Jan 28, 2008 6:06 AM

Dear Friends,
_Urgent : Please work on this ASAP _
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?

[Solved] (WW) fglrx(0): Kernel Module version does *not* match driver.

fglrx has just recently stopped working, and I can't quite pinpoint when that was because I honestly hadn't noticed until checking. I've tried a few reinstalls and different xorg options so far, but had no luck.
glxinfo:
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_SGI_video_sync, GLX_ARB_multisample,
GLX_ATI_pixel_format_float, GLX_ATI_render_texture
GLX version: 1.2
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_multisample
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (1.5 Mesa 6.5.2)
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
Xorg.0.log:
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux yggdrasil 2.6.21-ARCH #1 SMP PREEMPT Mon Jun 11 23:47:51 CEST 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 11 10:14:15 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Xorg"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbRules" "xorg"
(**) XKB: rules: "xorg"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "gb"
(**) XKB: layout: "gb"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "mx518"
(**) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/misc,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/100dpi,
/usr/share/fonts/cyrillic,
/usr/share/fonts/Type1,
/usr/share/fonts/TTF
(**) RgbPath set to "/usr/share/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(**) Option "AllowMouseOpenFail" "true"
(**) Option "AIGLX" "off"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81c44a0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.1
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(++) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,0269 card 1043,8122 rev 80 class 06,00,00 hdr 80
(II) PCI: 00:00:1: chip 1106,1269 card 1043,8122 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:2: chip 1106,2269 card 1043,8122 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:3: chip 1106,3269 card 1043,8122 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:4: chip 1106,4269 card 1043,8122 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:7: chip 1106,7269 card 1043,8122 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,b198 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:0a:0: chip 1102,0004 card 1102,2002 rev 04 class 04,01,00 hdr 80
(II) PCI: 00:0a:1: chip 1102,7003 card 1102,0040 rev 04 class 09,80,00 hdr 80
(II) PCI: 00:0a:2: chip 1102,4001 card 1102,0010 rev 04 class 0c,00,10 hdr 80
(II) PCI: 00:0e:0: chip 1317,0985 card 1317,0574 rev 11 class 02,00,00 hdr 00
(II) PCI: 00:0f:0: chip 1106,3149 card 1043,80ed rev 80 class 01,04,00 hdr 80
(II) PCI: 00:0f:1: chip 1106,0571 card 1043,80ed rev 06 class 01,01,8a hdr 00
(II) PCI: 00:10:0: chip 1106,3038 card 1106,3038 rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:1: chip 1106,3038 card 1106,3038 rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:2: chip 1106,3038 card 1106,3038 rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:3: chip 1106,3038 card 1106,3038 rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:4: chip 1106,3104 card 1106,3104 rev 86 class 0c,03,20 hdr 80
(II) PCI: 00:11:0: chip 1106,3227 card 1043,80ed rev 00 class 06,01,00 hdr 80
(II) PCI: 00:11:5: chip 1106,3059 card 1043,810d rev 60 class 04,01,00 hdr 00
(II) PCI: 00:11:6: chip 1106,3068 card 0000,0000 rev 80 class 07,80,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4e48 card 1002,0002 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4e68 card 1002,0003 rev 00 class 03,80,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000b (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[b]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xfd900000 - 0xfdefffff (0x600000) MX[b]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0x9ff00000 - 0xbfefffff (0x20000000) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] rev 0, Mem @ 0xb0000000/27, 0xfde00000/16, I/O @ 0xd000/8, BIOS @ 0xfdd00000/17
(--) PCI: (1:0:1) ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] (Secondary) rev 0, Mem @ 0xa8000000/27, 0xfdc00000/16
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) PCI Memory resource overlap reduced 0xe0000000 from 0xe7ffffff to 0xdfffffff
(II) Active PCI resource ranges:
[0] -1 0 0xfe600000 - 0xfe6000ff (0x100) MX[b]
[1] -1 0 0xfeb00000 - 0xfeb003ff (0x400) MX[b]
[2] -1 0 0x50000000 - 0x50003fff (0x4000) MX[b]
[3] -1 0 0x50004000 - 0x500047ff (0x800) MX[b]
[4] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[5] -1 0 0xfdc00000 - 0xfdc0ffff (0x10000) MX[b](B)
[6] -1 0 0xa8000000 - 0xafffffff (0x8000000) MX[b](B)
[7] -1 0 0xfdd00000 - 0xfdd1ffff (0x20000) MX[b](B)
[8] -1 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b](B)
[9] -1 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b](B)
[10] -1 0 0x00001400 - 0x000014ff (0x100) IX[b]
[11] -1 0 0x00001000 - 0x000010ff (0x100) IX[b]
[12] -1 0 0x0000ef40 - 0x0000ef5f (0x20) IX[b]
[13] -1 0 0x0000ef20 - 0x0000ef3f (0x20) IX[b]
[14] -1 0 0x0000ef00 - 0x0000ef1f (0x20) IX[b]
[15] -1 0 0x0000eec0 - 0x0000eedf (0x20) IX[b]
[16] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[b]
[17] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[18] -1 0 0x0000eeb0 - 0x0000eebf (0x10) IX[b]
[19] -1 0 0x0000ef80 - 0x0000ef83 (0x4) IX[b]
[20] -1 0 0x0000ef68 - 0x0000ef6f (0x8) IX[b]
[21] -1 0 0x0000ef84 - 0x0000ef87 (0x4) IX[b]
[22] -1 0 0x0000ef88 - 0x0000ef8f (0x8) IX[b]
[23] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[24] -1 0 0x0000efe0 - 0x0000efe7 (0x8) IX[b]
[25] -1 0 0x0000ed80 - 0x0000edbf (0x40) IX[b]
[26] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfe600000 - 0xfe6000ff (0x100) MX[b]
[1] -1 0 0xfeb00000 - 0xfeb003ff (0x400) MX[b]
[2] -1 0 0x50000000 - 0x50003fff (0x4000) MX[b]
[3] -1 0 0x50004000 - 0x500047ff (0x800) MX[b]
[4] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[5] -1 0 0xfdc00000 - 0xfdc0ffff (0x10000) MX[b](B)
[6] -1 0 0xa8000000 - 0xafffffff (0x8000000) MX[b](B)
[7] -1 0 0xfdd00000 - 0xfdd1ffff (0x20000) MX[b](B)
[8] -1 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b](B)
[9] -1 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b](B)
[10] -1 0 0x00001400 - 0x000014ff (0x100) IX[b]
[11] -1 0 0x00001000 - 0x000010ff (0x100) IX[b]
[12] -1 0 0x0000ef40 - 0x0000ef5f (0x20) IX[b]
[13] -1 0 0x0000ef20 - 0x0000ef3f (0x20) IX[b]
[14] -1 0 0x0000ef00 - 0x0000ef1f (0x20) IX[b]
[15] -1 0 0x0000eec0 - 0x0000eedf (0x20) IX[b]
[16] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[b]
[17] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[18] -1 0 0x0000eeb0 - 0x0000eebf (0x10) IX[b]
[19] -1 0 0x0000ef80 - 0x0000ef83 (0x4) IX[b]
[20] -1 0 0x0000ef68 - 0x0000ef6f (0x8) IX[b]
[21] -1 0 0x0000ef84 - 0x0000ef87 (0x4) IX[b]
[22] -1 0 0x0000ef88 - 0x0000ef8f (0x8) IX[b]
[23] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[24] -1 0 0x0000efe0 - 0x0000efe7 (0x8) IX[b]
[25] -1 0 0x0000ed80 - 0x0000edbf (0x40) IX[b]
[26] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfe600000 - 0xfe6000ff (0x100) MX[b]
[5] -1 0 0xfeb00000 - 0xfeb003ff (0x400) MX[b]
[6] -1 0 0x50000000 - 0x50003fff (0x4000) MX[b]
[7] -1 0 0x50004000 - 0x500047ff (0x800) MX[b]
[8] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[9] -1 0 0xfdc00000 - 0xfdc0ffff (0x10000) MX[b](B)
[10] -1 0 0xa8000000 - 0xafffffff (0x8000000) MX[b](B)
[11] -1 0 0xfdd00000 - 0xfdd1ffff (0x20000) MX[b](B)
[12] -1 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b](B)
[13] -1 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b](B)
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[16] -1 0 0x00001400 - 0x000014ff (0x100) IX[b]
[17] -1 0 0x00001000 - 0x000010ff (0x100) IX[b]
[18] -1 0 0x0000ef40 - 0x0000ef5f (0x20) IX[b]
[19] -1 0 0x0000ef20 - 0x0000ef3f (0x20) IX[b]
[20] -1 0 0x0000ef00 - 0x0000ef1f (0x20) IX[b]
[21] -1 0 0x0000eec0 - 0x0000eedf (0x20) IX[b]
[22] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[b]
[23] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[24] -1 0 0x0000eeb0 - 0x0000eebf (0x10) IX[b]
[25] -1 0 0x0000ef80 - 0x0000ef83 (0x4) IX[b]
[26] -1 0 0x0000ef68 - 0x0000ef6f (0x8) IX[b]
[27] -1 0 0x0000ef84 - 0x0000ef87 (0x4) IX[b]
[28] -1 0 0x0000ef88 - 0x0000ef8f (0x8) IX[b]
[29] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[30] -1 0 0x0000efe0 - 0x0000efe7 (0x8) IX[b]
[31] -1 0 0x0000ed80 - 0x0000edbf (0x40) IX[b]
[32] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b](B)
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules//libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(**) AIGLX disabled
(II) Loading extension GLX
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.2.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.38.6
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "fglrx"
(II) Reloading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) LoadModule: "keyboard"
(II) Loading /usr/lib/xorg/modules/input//keyboard_drv.so
(II) Module keyboard: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.38.6
(II) ATI Proprietary Linux Driver Release Identifier: LGDr8.38g1
(II) ATI Proprietary Linux Driver Build Date: Jun 22 2007 13:10:21
(II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.38.1.1.2.3-driver-lnx-x86-x86_64-351593
(--) Assigning device section with no busID to primary device
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset Supported AMD Graphics Processor (0x4E48) found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfe600000 - 0xfe6000ff (0x100) MX[b]
[5] -1 0 0xfeb00000 - 0xfeb003ff (0x400) MX[b]
[6] -1 0 0x50000000 - 0x50003fff (0x4000) MX[b]
[7] -1 0 0x50004000 - 0x500047ff (0x800) MX[b]
[8] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[9] -1 0 0xfdc00000 - 0xfdc0ffff (0x10000) MX[b](B)
[10] -1 0 0xa8000000 - 0xafffffff (0x8000000) MX[b](B)
[11] -1 0 0xfdd00000 - 0xfdd1ffff (0x20000) MX[b](B)
[12] -1 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b](B)
[13] -1 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b](B)
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[16] -1 0 0x00001400 - 0x000014ff (0x100) IX[b]
[17] -1 0 0x00001000 - 0x000010ff (0x100) IX[b]
[18] -1 0 0x0000ef40 - 0x0000ef5f (0x20) IX[b]
[19] -1 0 0x0000ef20 - 0x0000ef3f (0x20) IX[b]
[20] -1 0 0x0000ef00 - 0x0000ef1f (0x20) IX[b]
[21] -1 0 0x0000eec0 - 0x0000eedf (0x20) IX[b]
[22] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[b]
[23] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[24] -1 0 0x0000eeb0 - 0x0000eebf (0x10) IX[b]
[25] -1 0 0x0000ef80 - 0x0000ef83 (0x4) IX[b]
[26] -1 0 0x0000ef68 - 0x0000ef6f (0x8) IX[b]
[27] -1 0 0x0000ef84 - 0x0000ef87 (0x4) IX[b]
[28] -1 0 0x0000ef88 - 0x0000ef8f (0x8) IX[b]
[29] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[30] -1 0 0x0000efe0 - 0x0000efe7 (0x8) IX[b]
[31] -1 0 0x0000ed80 - 0x0000edbf (0x40) IX[b]
[32] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b](B)
(II) fglrx(0): pEnt->device->identifier=0x81e4088
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfe600000 - 0xfe6000ff (0x100) MX[b]
[5] -1 0 0xfeb00000 - 0xfeb003ff (0x400) MX[b]
[6] -1 0 0x50000000 - 0x50003fff (0x4000) MX[b]
[7] -1 0 0x50004000 - 0x500047ff (0x800) MX[b]
[8] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[9] -1 0 0xfdc00000 - 0xfdc0ffff (0x10000) MX[b](B)
[10] -1 0 0xa8000000 - 0xafffffff (0x8000000) MX[b](B)
[11] -1 0 0xfdd00000 - 0xfdd1ffff (0x20000) MX[b](B)
[12] -1 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b](B)
[13] -1 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b](B)
[14] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[15] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[16] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[18] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[19] -1 0 0x00001400 - 0x000014ff (0x100) IX[b]
[20] -1 0 0x00001000 - 0x000010ff (0x100) IX[b]
[21] -1 0 0x0000ef40 - 0x0000ef5f (0x20) IX[b]
[22] -1 0 0x0000ef20 - 0x0000ef3f (0x20) IX[b]
[23] -1 0 0x0000ef00 - 0x0000ef1f (0x20) IX[b]
[24] -1 0 0x0000eec0 - 0x0000eedf (0x20) IX[b]
[25] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[b]
[26] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[27] -1 0 0x0000eeb0 - 0x0000eebf (0x10) IX[b]
[28] -1 0 0x0000ef80 - 0x0000ef83 (0x4) IX[b]
[29] -1 0 0x0000ef68 - 0x0000ef6f (0x8) IX[b]
[30] -1 0 0x0000ef84 - 0x0000ef87 (0x4) IX[b]
[31] -1 0 0x0000ef88 - 0x0000ef8f (0x8) IX[b]
[32] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[33] -1 0 0x0000efe0 - 0x0000efe7 (0x8) IX[b]
[34] -1 0 0x0000ed80 - 0x0000edbf (0x40) IX[b]
[35] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b](B)
[36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin, [x]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.1
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "DPMS" "true"
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(WW) fglrx(0): Bad V_BIOS checksum
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(--) fglrx(0): Chipset: "RADEON 9800 PRO" (Chipset = 0x4e48)
(--) fglrx(0): (PciSubVendor = 0x1002, PciSubDevice = 0x0002)
(--) fglrx(0): board vendor info: original ATI graphics adapter
(--) fglrx(0): Linear framebuffer (phys) at 0xb0000000
(--) fglrx(0): MMIO registers at 0xfde00000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.1
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 2.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI R360
(II) fglrx(0): VESA VBE OEM Software Rev: 1.0
(II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: R360
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.38.6
ABI class: X.Org Server Extension, version 0.3
(--) fglrx(0): VideoRAM: 131072 kByte, Type: DDR SGRAM / SDRAM
(II) fglrx(0): AGP card detected
(II) fglrx(0): board/chipset is supported by this driver (original ATI board)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/lib/xorg/modules//libddc.so
(II) fglrx(0): Connected Display1: DFP on internal TMDS [tmds1]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: AIC Model: 9450 Serial#: 329
(II) fglrx(0): Year: 2006 Week: 33
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 37 vert.: 30
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) fglrx(0): First detailed timing not preferred mode in violation of standard!(II) fglrx(0): redX: 0.647 redY: 0.346 greenX: 0.298 greenY: 0.591
(II) fglrx(0): blueX: 0.150 blueY: 0.118 whiteX: 0.313 whiteY: 0.329
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): #1: hsize: 1280 vsize 1024 refresh: 70 vid: 35457
(II) fglrx(0): #2: hsize: 1280 vsize 1024 refresh: 72 vid: 35969
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 135.0 MHz Image Size: 376 x 301 mm
(II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 25.2 MHz Image Size: 376 x 301 mm
(II) fglrx(0): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 0
(II) fglrx(0): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 0
(II) fglrx(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 80 kHz, PixClock max 140 MHz
(II) fglrx(0): Monitor name: F-419
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff000523509449010000
(II) fglrx(0): 2110010380251e78e8e595a5584c9726
(II) fglrx(0): 1e5054bfef808180818a818c01010101
(II) fglrx(0): 010101010101bc34009851002a403070
(II) fglrx(0): 1300782d1100001ed60980a0205e6310
(II) fglrx(0): 10605208782d1100001a000000fd0032
(II) fglrx(0): 4b1e500e000a202020202020000000fc
(II) fglrx(0): 00462d3431390a2020202020202000ba
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(II) fglrx(0): Primary Controller - DFP on internal TMDS
(II) fglrx(0): Internal Desktop Setting: 0x00000001
(II) fglrx(0): POWERplay not supported on this hardware
(==) fglrx(0): Qbs disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 37 modes found for primary display.
(--) fglrx(0): Virtual size is 1280x1024 (pitch 0)
(**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024" 135.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024" 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync
(**) fglrx(0): *Mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800
(**) fglrx(0): Default mode "1024x768": 78.4 MHz (scaled from 0.0 MHz), 57.7 kHz, 72.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 +hsync
(**) fglrx(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync
(**) fglrx(0): *Mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
(II) fglrx(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625
(**) fglrx(0): Default mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.0 Hz
(II) fglrx(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600" 45.50 800 840 920 1040 600 601 604 625 +hsync
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): Default mode "800x600": 29.6 MHz (scaled from 0.0 MHz), 29.8 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "800x600" 29.60 800 816 896 992 600 601 604 635 interlace +hsync
(**) fglrx(0): *Mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 664 704 832 480 489 492 520 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525 +hsync +vsync
(**) fglrx(0): Default mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864" 96.76 1152 1224 1344 1536 864 865 868 900 +hsync
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 +hsync
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 64.67 1152 1208 1328 1504 864 865 868 915 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 58.28 1152 1200 1320 1488 864 865 868 911 interlace +hsync
(**) fglrx(0): Default mode "1024x480": 38.2 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x480" 38.16 1024 1048 1152 1280 480 481 484 497 +hsync
(**) fglrx(0): Default mode "848x480": 31.5 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "848x480" 31.48 848 864 952 1056 480 481 484 497 +hsync
(**) fglrx(0): Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x576" 32.66 720 744 816 912 576 577 580 597 +hsync
(**) fglrx(0): Default mode "720x480": 26.7 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x480" 26.71 720 736 808 896 480 481 484 497 +hsync
(**) fglrx(0): Default mode "640x400": 28.1 MHz (scaled from 0.0 MHz), 33.7 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x400" 28.07 640 696 736 832 400 413 415 449
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525
(**) fglrx(0): Default mode "640x350": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "640x350" 25.18 640 656 752 800 350 387 389 449 +vsync
(**) fglrx(0): Default mode "512x384": 19.8 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "512x384" 19.81 512 544 624 664 384 451 453 497
(**) fglrx(0): Default mode "400x300": 24.8 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 24.75 400 408 448 528 300 601 602 625 doublescan
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 300 601 605 742 doublescan
(**) fglrx(0): Default mode "320x240": 15.8 MHz (scaled from 0.0 MHz), 37.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 15.75 320 328 360 416 240 481 482 501 doublescan
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 240 491 493 525 doublescan
(**) fglrx(0): Default mode "320x200": 13.1 MHz (scaled from 0.0 MHz), 31.5 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 13.10 320 352 368 416 200 406 407 417 doublescan
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 200 457 459 524 doublescan
(--) fglrx(0): Display dimensions: (370, 300) mm
(--) fglrx(0): DPI set to (87, 86)
(--) fglrx(0): Virtual size is 1280x1024 (pitch 1280)
(**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024" 135.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024" 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync
(**) fglrx(0): *Mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800
(**) fglrx(0): Default mode "1024x768": 78.4 MHz (scaled from 0.0 MHz), 57.7 kHz, 72.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 +hsync
(**) fglrx(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync
(**) fglrx(0): *Mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
(II) fglrx(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625
(**) fglrx(0): Default mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.0 Hz
(II) fglrx(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600" 45.50 800 840 920 1040 600 601 604 625 +hsync
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): Default mode "800x600": 29.6 MHz (scaled from 0.0 MHz), 29.8 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "800x600" 29.60 800 816 896 992 600 601 604 635 interlace +hsync
(**) fglrx(0): *Mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 664 704 832 480 489 492 520 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525 +hsync +vsync
(**) fglrx(0): Default mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864" 96.76 1152 1224 1344 1536 864 865 868 900 +hsync
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 +hsync
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 64.67 1152 1208 1328 1504 864 865 868 915 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 58.28 1152 1200 1320 1488 864 865 868 911 interlace +hsync
(**) fglrx(0): Default mode "1024x480": 38.2 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x480" 38.16 1024 1048 1152 1280 480 481 484 497 +hsync
(**) fglrx(0): Default mode "848x480": 31.5 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "848x480" 31.48 848 864 952 1056 480 481 484 497 +hsync
(**) fglrx(0): Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x576" 32.66 720 744 816 912 576 577 580 597 +hsync
(**) fglrx(0): Default mode "720x480": 26.7 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x480" 26.71 720 736 808 896 480 481 484 497 +hsync
(**) fglrx(0): Default mode "640x400": 28.1 MHz (scaled from 0.0 MHz), 33.7 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x400" 28.07 640 696 736 832 400 413 415 449
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525
(**) fglrx(0): Default mode "640x350": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "640x350" 25.18 640 656 752 800 350 387 389 449 +vsync
(**) fglrx(0): Default mode "512x384": 19.8 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "512x384" 19.81 512 544 624 664 384 451 453 497
(**) fglrx(0): Default mode "400x300": 24.8 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 24.75 400 408 448 528 300 601 602 625 doublescan
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 300 601 605 742 doublescan
(**) fglrx(0): Default mode "320x240": 15.8 MHz (scaled from 0.0 MHz), 37.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 15.75 320 328 360 416 240 481 482 501 doublescan
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 240 491 493 525 doublescan
(**) fglrx(0): Default mode "320x200": 13.1 MHz (scaled from 0.0 MHz), 31.5 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 13.10 320 352 368 416 200 406 407 417 doublescan
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 200 457 459 524 doublescan
(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 7.2.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules//libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.1
(==) fglrx(0): NoAccel = NO
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.2.0
ABI class: X.Org Video Driver, version 1.1
(==) fglrx(0): HPV inactive
(**) fglrx(0): FSAA enabled: NO
(==) fglrx(0): FSAA Gamma enabled
(==) fglrx(0): FSAA Multisample Position is fix
(==) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) fglrx(0): Depth moves disabled by default
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x4000000f
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(==) fglrx(0): EnablePrivateBackZ = NO
(II) LoadModule: "glesx.so" (glesx)
(WW) LoadModule: given non-canonical module name "glesx.so"
(II) Loading /usr/lib/xorg/modules//glesx.so
(II) Module glesx: vendor="X.Org Foundation"
compiled for 7.1.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension GLESX
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b]
[1] 0 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b]
[2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[6] -1 0 0xfe600000 - 0xfe6000ff (0x100) MX[b]
[7] -1 0 0xfeb00000 - 0xfeb003ff (0x400) MX[b]
[8] -1 0 0x50000000 - 0x50003fff (0x4000) MX[b]
[9] -1 0 0x50004000 - 0x500047ff (0x800) MX[b]
[10] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[11] -1 0 0xfdc00000 - 0xfdc0ffff (0x10000) MX[b](B)
[12] -1 0 0xa8000000 - 0xafffffff (0x8000000) MX[b](B)
[13] -1 0 0xfdd00000 - 0xfdd1ffff (0x20000) MX[b](B)
[14] -1 0 0xfde00000 - 0xfde0ffff (0x10000) MX[b](B)
[15] -1 0 0xb0000000 - 0xb7ffffff (0x8000000) MX[b](B)
[16] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
[17] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
[18] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
[19] 0 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[22] -1 0 0x00001400 - 0x000014ff (0x100) IX[b]
[23] -1 0 0x00001000 - 0x000010ff (0x100) IX[b]
[24] -1 0 0x0000ef40 - 0x0000ef5f (0x20) IX[b]
[25] -1 0 0x0000ef20 - 0x0000ef3f (0x20) IX[b]
[26] -1 0 0x0000ef00 - 0x0000ef1f (0x20) IX[b]
[27] -1 0 0x0000eec0 - 0x0000eedf (0x20) IX[b]
[28] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[b]
[29] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[30] -1 0 0x0000eeb0 - 0x0000eebf (0x10) IX[b]
[31] -1 0 0x0000ef80 - 0x0000ef83 (0x4) IX[b]
[32] -1 0 0x0000ef68 - 0x0000ef6f (0x8) IX[b]
[33] -1 0 0x0000ef84 - 0x0000ef87 (0x4) IX[b]
[34] -1 0 0x0000ef88 - 0x0000ef8f (0x8) IX[b]
[35] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[36] -1 0 0x0000efe0 - 0x0000efe7 (0x8) IX[b]
[37] -1 0 0x0000ed80 - 0x0000edbf (0x40) IX[b]
[38] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b](B)
[39] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[40] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.0.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: drmOpenMinor returns 6
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xb4000
(II) fglrx(0): [drm] mapped SAREA 0xb4000 to 0xb7282000
(II) fglrx(0): [drm] framebuffer handle = 0xb5000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.37.6
(II) fglrx(0): Date: May 25 2007
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(WW) fglrx(0): Kernel Module version does *not* match driver.
(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xb4000 at 0xb7282000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xb0000000 FBMappedSize: 0x08000000
(==) fglrx(0): Write-combining range (0xb0000000,0x8000000)
(II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1280 x 7167
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(**) fglrx(0): DPMS enabled
(II) fglrx(0): GLESX enableFlags = 0
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled
(==) fglrx(0): Using hardware cursor
fbarea0->box.x1 0x00000000, fbarea0->box.y1 0x00000404
fbarea0->box.x2 0x00000500, fbarea0->box.y2 0x00000406
icon[0].start=0x505000
fbarea1->box.x1 0x00000000, fbarea1->box.y1 0x00000406
fbarea1->box.x2 0x00000500, fbarea1->box.y2 0x00000408
icon[1].start=0x508000
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(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 built-in extension XEVIE
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
[glesx] __glESXExtensionInit: No GL ES2.0 capable screen found!
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "gb"
(**) Keyboard0: XkbLayout: "gb"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "Protocol" "ExplorerPS/2"
(**) mx518: Device: "/dev/input/mice"
(**) mx518: Protocol: "ExplorerPS/2"
(**) Option "CorePointer"
(**) mx518: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Buttons" "10"
(==) mx518: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) mx518: ZAxisMapping: buttons 4 and 5
(**) Option "ButtonMapping" "1 2 3 6 7"
(**) mx518: Buttons: 14
(**) Option "Resolution" "800"
(**) mx518: Resolution: 800
(II) XINPUT: Adding extended input device "mx518" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) mx518: ps2EnableDataReporting: succeeded
xorg.conf:
Section "ServerLayout"
Identifier "Xorg"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "mx518" "CorePointer"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "AIGLX" "off" # Disable AIGLX
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
# Fonts
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/TTF"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "drm"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
Load "fglrx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
# Options
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
# Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "mx518"
Driver "mouse"
# Options
Option "CorePointer"
Option "Resolution" "800"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "10"
Option "ButtonMapping" "1 2 3 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "AG Neovo"
ModelName "F-419"
HorizSync 24.0 - 80.0
VertRefresh 50.0 - 75.0
# Options
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "Card0"
VendorName "All"
BoardName "All"
Driver "fglrx"
# Options
# Option "XAANoOffscreenPixmaps" "true"
# Option "AGPMode" "8"
# Option "ColorTiling" "on"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
#Section "Extensions"
# Option "XEVIE" "Enable"
# Option "Composite" "Enable"
#Endsection
Would it be possible to explain the other warnings in Xorg.0.log? Rather curious about those apart from the obvious one, too.
Thanks.
Last edited by Newnux (2007-07-11 16:04:15)

Indeed, that seems the end-all error of it all.
I'll summarise my warnings, some for curious reasons:
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) # What's this?
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found # Not a problem.
(WW) fglrx(0): Only one display is connnected,so single mode is enabled # No problem.
(WW) fglrx(0): Kernel Module version does *not* match driver.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
Anyway, I wondered about versions and noticed this:
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xbc000
(II) fglrx(0): [drm] mapped SAREA 0xbc000 to 0xb7285000
(II) fglrx(0): [drm] framebuffer handle = 0xbd000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.37.6
(II) fglrx(0): Date: May 25 2007
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(WW) fglrx(0): Kernel Module version does *not* match driver. # included to show where this was displayed
All versions previous to that show 8.38.6:
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.38.6
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
So I assume I have an old version dotted around somewhere, but I'm not sure about how it's all loaded and such.
Now, quoting something I'd come across a few times and taking it from thinkwiki:
If you lose hardware acceleration after a driver update this can be caused by an old fglrx kernel module being loaded.
Check out /var/log/Xorg.0.log for a message like:
(WW) fglrx(0): Kernel Module version does *not* match driver.
(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
You can verify this yourself by looking at the version message some lines above. It should read something not matching the installed version like:
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.10.19
The cause for this trouble might be that there resist multiple versions of the fglrx module within the kernel module search path.
Go to /lib/modules/<your linux kernel version>/ and type # grep fglrx modules.dep.
If grep finds multiple lines you nailed down the problem. All you have to do now is to delete any versions of the module (look at the filedate) but the most current one. Then run # depmod and you are done.
Hint:
Newer versions (8.21.7) of the fglrx module seem to be installed in the extra/ subdirectory.
Older versions (8.19.10) used to be located in the kernel/drivers/char/drm/ subdirectory.
How does this apply to Arch? I only found one instance of fglrx by using that method.
Edit: Forgot to add that I've tried reinstalling a few times, it doesn't really seem to do anything. Wondering if I should attempt to install an older version or something, but I don't get why the driver numbers don't match for me. Surely others have updated their drivers too.
Last edited by Newnux (2007-07-11 13:28:55)

Error with a PDF document in a BSP App: "File does not begin with '%PDF-'"

Hi All,
I have the following piece of in the layout of a BSP Application in our system.
<%
DATA: LV_PDFSIZE TYPE I,
            LW_PDF     TYPE TLINE,
            LV_XDATA   TYPE XSTRING.
data: LT_PDF type ZGTIS_TAB_TLINE,
      lv_id type zgtis_http_id,
      filename type STRING.
lv_id = session_id.
import lt_pdf to lt_pdf from
       database zgtis_http_indx(in) id lv_id.
RUNTIME->SERVER->RESPONSE->SET_HEADER_FIELD(
    NAME = 'Content-Type'
    VALUE = 'application/pdf').
if w_printall ne 'X'.
CONCATENATE 'display; filename="invoice_' BIL_NUMBER '.pdf"' INTO filename.
else.
CONCATENATE 'display; filename="invoice_' 'ALL' '.pdf"' INTO filename.
endif.
RUNTIME->SERVER->RESPONSE->SET_HEADER_FIELD(
    NAME = 'Content-Disposition'
    VALUE = filename ).
RUNTIME->SERVER->RESPONSE->SET_HEADER_FIELD(
    NAME = 'pragma'
    VALUE = 'no-store').
RUNTIME->SERVER->RESPONSE->SET_HEADER_FIELD(
    NAME = 'cache-control'
    VALUE = 'no-store').
*     Convert to XSTRING
FIELD-SYMBOLS <P> TYPE ANY.
LOOP AT LT_PDF INTO LW_PDF.
ASSIGN LW_PDF TO <P> CASTING TYPE X.
CONCATENATE LV_XDATA <P> INTO LV_XDATA
    IN BYTE MODE.
ENDLOOP.
*     Set the response data
RUNTIME->SERVER->RESPONSE->SET_DATA(
    DATA   = LV_XDATA ).
%>
This piece of code works fine when 'If w_printall ne 'X'.' condition is succesfull and I can see the PDF but when w_printall = 'X' I get the above error on a popup box, the error is "File does not begin with '%PDF-'" and I cant see the PDF.
Does anyone have any suggestions!
Kindly help.
Regards,
Karthik

Check this thread
it is a Big Discussion on that.
In first page and second page you can see solutions.
/thread/747643 [original link is broken]
one with patch and other with setting in Adobe.
Regards
Vijay babu Dudla

Itemization does not match cost component split

Hi,
I need your help or could you please shed some light as to how to fix .
A new Overhead was created, in order to add expenses to the pricing of the product. For it a variant of different pricing to which is used currently was created, and so for maintain a historic one of the information.
In addition, in the cost component Structure an adjustment of the configuration was carried out, this was done because the previous the cost component Structure contained 18 elements of costs, which the most of the elements were specified as fixed and variable costs, therefore the system only permitted the addition of 2 more elements (SAP only permits 20 elements of fixed and variable costs), nevertheless was necessary to create a total of 23 elements of costs. For it the previous elements have to be modified and to change some elements as variable costs, specifically the elements corresponding to the accounts of materials. using tcode OKTZ
The addition of 5 more elements of costs, corresponding to overhead elements, where the type 41 costs classes were configured from the plan of surcharge created.
After carrying out the changes and to transport them the client of production, when i execute the T-code ck13n an inconsistency in the previous pricings was generated, because the cost component Structure was modified and the the following one Nº message was showed: CK869 " Mat.XXX in plant XXX: itemization does not match cost component split, the report of itemization shows different values to the reports of Costed Mutilevel BOM and of Cost Components. Additionally to the error shown by the system, also is observed that to the Cost Components report a cost in the new elements of overhead was added, even when the calculation of previous cost did not contain the determination of overhead.
In order to fix the error, I modified the cost component structure as it was before and the created another cost component structure with the required changes requested by the client specifying that it should start to be current this year. However after that change the error message nºCK869 continue: Mat. XXX in plant XXX: itemization does not match cost component split. Adding to that error message, the cost of the finished product changes with reference to the calculus of the previous product after modified the configuration and that is because the cost of the semifinished product is not being taken the values of the row material, and it is appearing with cost 0 and the only value that is taking on the matter are the costs of the activities types.

If you want the message to go away then you need to mark and releasse the estimate. However, there is no requirement that you do this. The message you are getting is an informational message only. You can continue without re-costing the item. If you do re-cost the material the new cost estimate will reflect and changes you've made to the components, so there is a good chance you will get a different value with the new estimate. So if that's ok, go ahead and mark and release the new estimate.

Regarding "Data does not match the job definition; job terminated"

Dear Friends,
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?

Hi dharmendra
Good Day
How are you
I am facing the same problem which you have posted
By any chance have you got the soultion for this
If so please let me know the solution for this.
Thanks in advance.
Cheers
Vallabhaneni

PO PDF Error - File does not Begin with '%PDF-'

Hi,
I am working on Implementing PO PDF with XML data and RTF Template. I have created a new template in XML Publisher and followed the following set up steps
Setup / Organizations / Purchasing Options / Control TAB / set 'PO Output Format' = 'PDF'
setup / purchasing / document types / select "Standard Purchase Order" / Set the Document Type Layout to your new template.
When I view the document from PO Summary > inquire > View Document, I get an adobe reader error
'File does not begin with '%PDF-', how ever when I preview it from the template definition, it opens fine.
I tried running PO Output for communication with my custom template but I don't see the parameter 'Purchase Order Layout'. The last parameter in the list is 'Include Blanket'.
Am I missing any set up steps? However when I use the standard Purchase Order Layout in Document Types set up, the Inquire > View Document created a PDF output.
Any help is greatly appreciated.
Thanks,
Sharmila

I encountered same error in BPA Invoice Print. I remove a MLS function from the program definition and this error disappeared. Have not fully investigated but maybe this will help. Thanks.

Business partner balance does not match journal entries message

Dear All,
The error message "Business partner balance does not match journal entries" appears in customer receivable report print preview. This is happened While generating the Customer Receivables Aging report by sales documents. What is the main cause ? How to resolve it ? Thanks a lot
Rgds,
Edu

Hello,
I've got solution from SAP notes. From the notes, the problem is probably caused by :
1. Inconsistent Reconciliation
2. Unbalanced Reconciliation
3. Document is closed but the Document Journal Entry is Unreconciled
4. Business Partner Balance is Incorrect
5. Reconciling Part of Split Payment's Journal Entries
There aresome queries need to run in order to solve the problem. If you are not a partner, let me know your e-mail so that I could send.
Rgd,

Cash Disc in pymt advise need to post thr f-28 when doc# does not match

Hi
The below is the scenerio for posting incoming payment following by our client
1) Creation of payment advise (FBE1)
2) Posting through F-28 by giving payment advise no. in f-28
In payment advises amount field will be Gross amount, Payment amount and discount amount.
Customer gives gross amount, payment amount and discount in payment advise.(payment advise generates through IDOCS)
while posting incoming payment based on payment advise, if the document no. matches with customer document no., then system posts automatically discount based on payment terms.
But if the document no. does not match, system will simply credit the customer and debit the customer with payment amount.
Ex:-
Gross amount: 10000
Payment amount:9000
Discount amount: 1000
System will post below entry
DR Bank    9000
CR Customer 9000
i.e., system is ignoring the gross and disc. fields.
Here the requirement is if the document no. does not match, system should generate an entry displaying gross amount, discount amount and payment amount and post to the customer.
i.e.,
DR Bank            9000 (payment amt)
CR customer       10000 (Gross)
DR customer        1000 (Discount)
Request to suggest is there any workaround to meet the above requirement.
Regards
Srinivasa Rao

Hi
The below is the scenerio for posting incoming payment following by our client
1) Creation of payment advise (FBE1)
2) Posting through F-28 by giving payment advise no. in f-28
In payment advises amount field will be Gross amount, Payment amount and discount amount.
Customer gives gross amount, payment amount and discount in payment advise.(payment advise generates through IDOCS)
while posting incoming payment based on payment advise, if the document no. matches with customer document no., then system posts automatically discount based on payment terms.
But if the document no. does not match, system will simply credit the customer and debit the customer with payment amount.
Ex:-
Gross amount: 10000
Payment amount:9000
Discount amount: 1000
System will post below entry
DR Bank    9000
CR Customer 9000
i.e., system is ignoring the gross and disc. fields.
Here the requirement is if the document no. does not match, system should generate an entry displaying gross amount, discount amount and payment amount and post to the customer.
i.e.,
DR Bank            9000 (payment amt)
CR customer       10000 (Gross)
DR customer        1000 (Discount)
Request to suggest is there any workaround to meet the above requirement.
Regards
Srinivasa Rao

Layout Editor Does Not Match Generated PDF

Similar Messages

Maybe you are looking for