!! Open-source extension to Kodo released !!
Hello fellow Kodo users,
You guys that are bold enough to want the cutting edge in Kodo software
are my target audience here... (repost from main news group)
I've been working with Kodo since it was created, and my employer has been
generous enough to allow me to open-source my work. My goal was to make
Kodo / JDO easy to use for the other developers on my team, without
sacrificing any of the power of the JDO spec. The result is
http://jstomp.sourceforge.net/. Here you will find a robust bytecode
enhancer which makes working with Kodo a breeze. You think your code is
clean now? Wait until you see what you can do with Stomp.
We've been using this enhancer in production internally for over a year,
with great results. We're using Stomp in an appserver (JBoss), connecting
to multiple legacy databases, and everything is running smoothly. I
convinced my employer to open this code up to the Kodo community, in the
hope that one or two quality developers on this list will adopt this
technology and contribute to it's success.
So... if you are new to Kodo, forget this. If you've been using Kodo for
a while, check this out. It rocks. I'm always open to questions /
comments.
Eric Lindauer
[email protected]
Sorry Romu, but this against the CoC and [Terms of use|http://www.sun.com/termsofuse.jsp#g2_1] here.
Similar Messages
-
[ANN] XINS 2.1 open source Web Services framework release
XINS 2.1 Web Services Framework has been released.
XINS is an open source Web Services Framework based on simple specifications of the Web Service in XML and
generation of code and documentation from the specification.
The generation includes Client JAR with its Javadoc, Server side template with its Javadoc, documentation in OpenDocument Format,
documentation in HTML including the test forms, WSDL file, unit tests (JUnit) and stubs.
The Web Services accept several protocols including REST, SOAP, XML-RPC, XML, JSON Yahoo! and JSON-RPC.
What's new:
* Start the API with java -jar <api name>.war
* Improved generated specification in OpenDocument Format
* Include/exclude calling convention with ACLs
* New calling convention that maps SOAP request and response as the wsdl2api command mapping.
* Smaller generated build.xml
* Added possibility to include other runtime properties files
* The runtime property location can be a URL
* Swing Graphical User Interface
* New tools: emma, glean, webstart
* New target: javadoc-test-<api name>, javadoc-apis
* Bug fixes and small RFEs
Download XINS 2.1:
Windows installer: http://prdownloads.sf.net/xins/xins-2.1.exe?download
TAR GZ archive: http://prdownloads.sf.net/xins/xins-2.1.tgz?download
Resources:
Web site: http://xins.sourceforge.net/
XINS demos: http://xins.sourceforge.net/demo.html
Documentation: http://xins.sourceforge.net/documentation.html
User guide: http://xins.sourceforge.net/docs/index.htmlI recommend you implement your web service with JAX-WS 2.0
Axis (both version) are good but why do you want to use something that is not included in JEE API, when Java provide same thing with better performance.
personally try to prevent non standard technologies despite they can be better than core java implementation sometimes.
I don't know Xfire.
the good:
-JAX-WS performance is better than axis,
- you can create your web service simply with annotation.(this means write class and then make it as a service easily)
- support every kind of service invocation(callback,Asynchronous,...)
- architecture is nice (you can operate on SOAP level)
the Bad:
- It is JEE 5 or JSE 6 dependent.
- there is seriously lack of documentation and examples for it, on java web sites and internet. -
LiveView: Make it 'open source' for the benefit of all
First, let me start by saying LiveView is a great concept. However...
SonyEricsson needs more than just a great concept to make this a useful and successful product.
At present, it is horrendous and they should be embarrassed with releasing this device to the market in its current state.
The hardware is average but the software/firmware is absolutely awful, leading to an extremely unreliable / barely useful device.
My experiences since receiving my LiveView have not been dissimilar to the rest of the users who have seen frequent disconnections / lockups / non-working features.
It is clear that there is interest in this device from the Android Community / Xda-Developers, etc. with many members keen to resolve LiveView's issues themselves - yet they are limited by a closed platform. Given Engadget's review of the LiveView, SonyEricsson's poor track record of providing continued support / updates to their products and their statement that there will be no updates issued for the device - I would think it not inappropriate to demand that an update at least be made to make the software entirely open source, or firmware/code released with a vehicle/drivers for updating.
I'm sure if the community were given the freedom, they could make the software reliable, customisable and perhaps even define innovative new ways to use the hardware.
If that happens, there's increased interest in the community which in turn would lead to more sales.
SonyEricsson, why not leverage the benefit of a willing (and free) workforce that are more interested in improving your device than you are?
(TLDR) In short, SE's failure to provide a fully functioning reliable product combined with their lack of commitment to continued support has paved the way for a global community of very tech savvy individuals and groups, willing to devote their time freely to improving LiveView. I say to SonyEricsson, let them - everyone wins.
To other customers, would you support making LiveView open source?
If so - let SonyEricsson know here and by submitting an e-Mail via their Support site (for UK, where SE's global management team is based):http://www.sonyericsson.com/cws/common/contact/contactusemail/accessories?cc=gb&lc=enOnce there is a successor model, I would welcome it very much if the source code is released, and the owner of the MN800 can finally use their device.
-
Open Sourcing an iPhone Application acceptable under the License Agreement?
I've read through the licensing agreement, but I'm still not convinced either way. I want to make my iPhone application's source code available on the internet and set up a project page and SVN repository on a site such as Google Code. I wouldn't be distributing my signing keys and would be the single source for submitting the app to iTunes. Is this allowed under the License Agreement?
(Disclaimer: IANAL, I'm just a smart guy who's worked on GPL projects.)
That isn't the relevant part of the iPhone license agreement. The GPLv2 (which is probably the most important open source license for this question, as it's both very popular and has restrictions on mixing with proprietary code) does not encompass headers and libraries that are part of the operating system. That's how people can write open source Windows and Mac applications--believe me, Microsoft would not be pleased if someone contacted them and said that since Gaim was open source, they had to release the source code to the Win32 API. So the GPLv2 would not attempt to "annex" anything provided by Apple, and thus it wouldn't violate that section.
What may be relevant is the iPhone license section concerning confidentiality. If the class, method, function and constant names are considered "Apple Confidential Information", you would be in violation of the contract if you distributed code that revealed them. I rather suspect that nothing in the Foundation or Core Foundation frameworks could be considered confidential, as information about them is freely available to anyone who has the Mac OS X Core Library, which is distributed with every copy of Leopard. UIKit, Core Location, etc. are another story; I personally think that the fact that the APIs are included in the free SDK ought to preclude considering them confidential, but Apple might think differently.
In other words: you're definitely safe using LGPLv2 libraries. If the code would also compile with the Mac OS X SDK, you're almost certainly safe releasing it under the GPLv2*. If the code uses UIKit or other frameworks documented in the free SDK, you may be safe releasing it under the GPLv2. If you release any code that uses APIs that only licensed developers have access to under the GPLv2, you're probably totally screwed.
The GPLv3 is much stricter, and so the story there might be different; for example, I think it may have key-releasing requirements that would conflict with the contract. I don't really know much about it, though.
\* Remember, the original copyright holder can create alternate licensing arrangements for specific people. So he can say "anyone can use this code under the GPL, and as a special exception, it can be linked against FooCorp's non-GPL software". But to use anyone else's GPL code, you'd have to get all of the authors of that code to agree to the same exception. Alternately, you can just release your own code under the LGPL instead and then it's all good.
Message was edited by: Brent Royal-Gordon -
Hi everyone,
First post here as I'm not a Java developer, but I'm looking for help in your community. Sorry in advance if it is not the right place to post that, maybe you can redirect me if it is the case.
I'm a flash actionscript developer and I've started an open source project some months ago.
The project is an AS3 flash framework that is meant to be generated, this framewok is an MVC framework and manage the body of a flash site. The idea is generate the body of a flash site through settings.
I'm working with another flash developer who is also a Java beginner. We have started to build a software with SWT. The first version is far from what I'd like to do but will be a very good start as a demo to show the potential. This first version is at the moment half done but unfortunately the other developer doesn't have a lot of time anymore.
I can write myself a bit of java but I clearly don't have time to work on both side, Java and actionscript. I'm using already and successfully the flash framework in real projects and I still have a lot of work on the actionscript part, it makes unable to go further with the software at the moment.
I don't know how things are working in the Java community but in the Flash one there are tons of free open source library/framework/project released. All these people are working freely on their project (probably at night as I'm doing :) ) because the're happy to face challenge, help the community and help developers to go further.
I'm looking for one Java developer (and probably more later, as well as flash developer) interested in the project and willing to help me to finish this first version.
The flash part is working already but not released to the public, you can contact me to join me or just to ask me more information (and see the framework and the application) or help me find someone.
You can contact me on my blog:
www.soundstep.com
Thanks for your time.
RomuSorry Romu, but this against the CoC and [Terms of use|http://www.sun.com/termsofuse.jsp#g2_1] here.
-
New open-source build tool for CS Extensions
I just released a new open-source tool for creating, compiling, debugging, packaging, and deploying extensions:
https://github.com/creativemarket/csxs
At a Glance:
All project settings live in a single JSON file (not multiple XML files).
Compiles CS5 & CS6 versions and packages them as a single ZXP. This is useful for supporting "DarkNormal" and "DarkHover" icons without ditching CS5 compatibility on your extension. It also supports other / more complicated configurations.
Created projects contain boilerplate for re-skinning on UI change along with fixes for platform bugs.
Generates aggregated changelogs.
Automated deploys to S3.
Automated git version tagging.
Conditional compilation variables (CONFIG::debug, CONFIG::release, CONFIG::version).
Usage:
csxs create
csxs debug --cs-product=photoshop --cs-version=5.5
csxs package
csxs deploy
I'd love feedback, suggestions, forks, bug reports, etc!
p.s. I really hope this doesn't come across as spammy—I mean it with the best intentions. I think it could be useful for some out there. More tools for the CS ecosystem is a win for all.
"We encourage you to contribute content, answer questions, or comment with corrections, clarifications, tips, and more. Links to your favorite resources or expert videos could help other community members."
http://forums.adobe.com/docs/DOC-2325Great tool, thanks a lot for sharing it.
Installed it and built "Hello, world" extension, now trying to convert my existing extension project for this. Packaging CS5 / CS6 versions alone is priceless.
Maybe a dumb question, but is it possible to switch .json and output name in command line? I have extension with 5 different versions, they have different licenses etc., so it would be great to type
csxs package config1.json extension1.zxp
csxs package config2.json extension2.zxp
and so on? I'd put it all into one .sh script
sorry if it's all already available and I just missed this part in documentation -
Open Source releasing best practices?
Hello,
When creating open source software, I don't really know what the best way to release it (what kind of makefile, versioning system, etc...) is. It's also hard to find this info online, is there any good online info or book about this?
Here are some of my questions...
-How many operating systems should your makefile support? Should I make special cases for every single Linux distro and other OS in the makefile, or can I just put a generic "g++ *.cpp" in the makefile, and let each OS and distro's own package managers take care of tailoring it to their OS?
-For makefile complexity, I guess there is a scale ranging from a hack like just typing "g++ *.cpp" in it, through having nice sections, groups of files and definitions like "CFLAGS", all the way up to projects which have 20 different makefiles in them like "Makefile.in", "Makefile.pandora", etc.... Where on that scale should you ideally be?
-Makefiles of many projects look incredibly complex, why?
-What versioning system to use? When to make a 1.0.0? When to append "rc" at the end?
-When to tag stable versions? And when you change something in head, do you need to change version number every single time?
-When creating a dynamic library, and you tagged a stable version, and you then change something in head. Should in the makefile the version number of the library name be changed to something? If so, should it be changed to a next minor version, or to something with "-rc" at the end?
-What names should be used for tags of versions?
-Does there need to be both a zipped version of the source code and one under VCS, and if so why is that zipped version needed?
-Are there any naming conventions for output binaries and libraries?
-Are you supposed to let your makefile clean up .o files after compilation or not?
-Are there any conventions for makefiles for names of sections and variables in it? E.g. is it a good idea to have a "clean:" in your makefile to remove everything?
-When depending on another library which is hosted somewhere else, how to handle that? What when statically depending on it?
-Any other things I should know?
Thanks!
Last edited by aardwolf (2013-05-07 12:32:57)aardwolf wrote:Hello,
Many of your questions have no single correct response. I'll reply with my own opinions and experiences, based on my release of two open source projects (GPT fdisk and rEFInd).
-How many operating systems should your makefile support? Should I make special cases for every single Linux distro and other OS in the makefile, or can I just put a generic "g++ *.cpp" in the makefile, and let each OS and distro's own package managers take care of tailoring it to their OS?
Ideally, a Makefile should build a package under every OS on the planet. In practice, this isn't always practical. Many developers use programs like Autotools to create Makefiles that are suited to a particular build environment. Other developers (myself included) create a handful of Makefiles for different environments -- for instance, my GPT fdisk has Makefiles for Linux, FreeBSD, OS X, and Windows. My rEFInd officially supports building only under Linux, although it supports two EFI toolkits (GNU-EFI and TianoCore EDK II) via a cascading set of Makefiles. Any of these Makefiles can require changes depending on the distribution and development environment in use, but that's not really my concern.
If a distribution requires changes, that type of change is generally best left to a build system like Autotools or to the person who builds or packages the program. IMHO, it's unreasonable to ask a developer to make minor tweaks to a static Makefile to support every minor Linux variant on the planet.
-For makefile complexity, I guess there is a scale ranging from a hack like just typing "g++ *.cpp" in it, through having nice sections, groups of files and definitions like "CFLAGS", all the way up to projects which have 20 different makefiles in them like "Makefile.in", "Makefile.pandora", etc.... Where on that scale should you ideally be?
This is very much a matter of personal preference and project complexity. Autotools or something similar will make it easy for users and distribution maintainers, but can be tricky to use for the developer. If your program is a simple single-file C program, you might forego a Makefile completely; but for something on the scale of the Linux kernel, a Makefile (or something equivalent) is absolutely required.
-Makefiles of many projects look incredibly complex, why?
Some projects are very complex, as in the Linux kernel itself. Other times, the Makefiles generated by automated systems like Autotools can be more complex than they might be if they were hand-crafted. In still other cases the developers like complexity or are barely competent at creating Makefiles and so create something that's more complex than it needs to be.
-What versioning system to use? When to make a 1.0.0? When to append "rc" at the end?
AFAIK, there are no standards on this. A 1.0 release denotes that something has moved beyond "beta test" status -- in other words, you think it's stable and usable for the masses. Open source software authors tend to be conservative in making that judgment, so pre-1.0 releases in the open source world are often as good as post-1.0 releases of commercial software. The bottom line, though, is that it is a judgment call -- what I consider "1.0" software you might consider well beyond that point and something else might consider pre-beta.
As to release candidate (RC), not all projects use that designation at all. It seems to me to be more common among large projects as they approach major release milestones, to denote something that is close to being finalized, but not quite -- essentially a sort of very late beta stage, even if the initial 1.0 release was made some time before.
-When to tag stable versions? And when you change something in head, do you need to change version number every single time?
If the code changes, you should definitely change the version number. Most developers accumulate several changes before making a new official release, though. Personally, I make full releases with three-digit numbers (like 0.8.6 or 0.6.10), and I upload minor changes to my project's git repository with four-digit numbers (like 0.8.6.1 or 0.6.10.2), but don't do full releases with tarballs and RPMs and whatnot for these, except in a limited way if I want specific people to test a recent change because they filed a bug report. Others have other systems.
-When creating a dynamic library, and you tagged a stable version, and you then change something in head. Should in the makefile the version number of the library name be changed to something? If so, should it be changed to a next minor version, or to something with "-rc" at the end?
The key difference with dynamic libraries is that the interfaces should not change with minor changes. IIRC, the second digit (like "2" in 1.2.3) is the cutoff point. In other words, a program that uses library version 1.2.3 should continue to work without changes or recompilation with library 1.2.4 or 1.2.2 (assuming no bugs). This enables users to upgrade the library (from 1.2.3 to 1.2.4 or the like) without upgrading every binary that relies on it. With version 1.3.0, though, the interface to the library might change in a way that would require recompilation of the program or even changes to the source code. Thus, changing the library from 1.2.4 to 1.3.0 will require the user to upgrade all the programs that use that dynamic library (or keep the old version around along with the new one). Note that I've never created a publicly-released library, and it's been a while since I've read up on this, so I might be a little off on these details.
-What names should be used for tags of versions?
I'm not sure what you mean by this.
-Does there need to be both a zipped version of the source code and one under VCS, and if so why is that zipped version needed?
You can do it any way you want; but as a general rule, you should provide source code in a tarball or .zip file because that's easier to download. Some package systems, such as RPM, require that a source package filename be specified, and so not providing source in such a package just complicates matters for packagers and therefore makes it less likely that they'll bother packaging your program at all. This in turn makes it harder for your users to use the program.
Note that most Linux programs' source code is provided as tarballs rather than as .zip files. Some cross-platform programs can be exceptions to this rule. For instance, I used .zip for rEFInd (a boot loader) because .zip is a little more common in Windows -- although I'm sure either would have worked fine, in practice.
You should probably provide binary builds of your software -- although in some cases this can be tricky because a binary built for Distribution A may not work on Distribution B because of library differences. The OpenSUSE Build Service (OBS) can help with this, although it's a bit of a pain to use.
-Are there any naming conventions for output binaries and libraries?
Not AFAIK, except of course for filename extensions like .so and .a.
-Are you supposed to let your makefile clean up .o files after compilation or not?
No, except for the "clean" target and anything else that's supposed to do this.
-Are there any conventions for makefiles for names of sections and variables in it? E.g. is it a good idea to have a "clean:" in your makefile to remove everything?
The "all" target builds everything, "clean" cleans up, "install" installs everything, and "uninstall" uninstalls everything. There's no law that says you have to have all of these, but they're common, particularly with big projects.
-When depending on another library which is hosted somewhere else, how to handle that? What when statically depending on it?
This type of thing is generally handled by packaging programs (pacman, rpm, dpkg, etc.), not by developers' Makefiles. That said, Makefile builders like Autotools should check for the relevant development libraries and stop if they aren't present. That will handle the static linking issue, as well as other problems. On another level, when using RPM, a source RPM will include dependencies on the relevant development libraries, and Debian source files have a similar feature. Putting these files together is the responsibility of distribution maintainers, not of program authors.
-Any other things I should know?
There's a huge range of acceptable practices on these issues. As a general rule, though, the smaller the package the more likely you are to find a simple Makefile that builds the whole project. Bigger projects are more likely to rely on multiple Makefiles, Autotools, or other complex pre-build software. More standardization emerges at the distribution level, in the form of source and binary RPMs, Debian packages, etc. You shouldn't need to worry too much about that. So long as your package builds with few or no changes on a variety of distributions, the distribution packagers can handle the rest. Build systems always support patches so that minor changes to Makefiles or whatnot can be incorporated. This frees you up to worry about other things rather than trying to support every minor variant distribution in existence. -
Open Source BI Tool Now Supports Kodo JDO
Folks,
To keep you posted on the latest tools that work with Kodo JDO, we
will try and post notices here on our newsgroups. ObjectVisualizer
is a third party open source querying, reporting and graphing tool that
now supports Kodo JDO. Let us know what you think.
Neelan Choksi
President, SolarMetric
ObjectVisualizer is a business intelligence tool that builds upon
Object Persistence technology to provide easy to use query, reporting,
and charting capabilities.
Features include: Query, filter, and aggregate data using objects,
Interactive Data Table, Report Generation, Chart Creation, and Plugin
Architecture.
ObjectVisualizer now supports KodoJDO! ObjectVisualizer 1.0.1 includes
a KodoJDO plugin along with a number of bug fixes and enhancements.
A new Early Access release of ObjectVisualizer Server Edition is also
available. ObjectVisualizer Server Edition EAP-2 has been upgraded to
work with ObjectVisualizer 1.0.1 and includes a number of performance
enhancements.
For more information visit:
http://objectvisualizer.com
Thank you,
Open Source Software Solutions, LLC
http://opensourcesoft.netFolks,
To keep you posted on the latest tools that work with Kodo JDO, we
will try and post notices here on our newsgroups. ObjectVisualizer
is a third party open source querying, reporting and graphing tool that
now supports Kodo JDO. Let us know what you think.
Neelan Choksi
President, SolarMetric
ObjectVisualizer is a business intelligence tool that builds upon
Object Persistence technology to provide easy to use query, reporting,
and charting capabilities.
Features include: Query, filter, and aggregate data using objects,
Interactive Data Table, Report Generation, Chart Creation, and Plugin
Architecture.
ObjectVisualizer now supports KodoJDO! ObjectVisualizer 1.0.1 includes
a KodoJDO plugin along with a number of bug fixes and enhancements.
A new Early Access release of ObjectVisualizer Server Edition is also
available. ObjectVisualizer Server Edition EAP-2 has been upgraded to
work with ObjectVisualizer 1.0.1 and includes a number of performance
enhancements.
For more information visit:
http://objectvisualizer.com
Thank you,
Open Source Software Solutions, LLC
http://opensourcesoft.net -
What's the Best Open Source DB for use with Kodo?
Hi everyone,
In terms of ease of setup and use, tools to view info in the database, and least difficulty in
running with Kodo, what is the best open source database to use? I'm use to using Oracle and
SQLPlus. I need to use an open source DB for a learning environment, and I'd like your informed
opinion.
Thanks,
David EzzioI have been using postgresql 7.1 with Kodo for a while with mostly positive results, and currently
have it deployed with Kodo 2.2.3. I prefer it to mysql because its feature set is a little richer,
and supports transactions natively. My experience with mysql (without jdo - I haven't tried it with)
is good, but there were little things missing in mysql 3.x, e.g. the ability do do a join in a
DELETE statement.
BTW, there are some severe problems somewhere in the 2.2.4 release with postgresql if you intend to
eventually deploy on it. It also apparently has some problems invoking postgresql's indices, making
it a little less than optimal. But as a learning environment, it's what I'd recommend.
-Mike
Marc Prud'hommeaux wrote:
David-
Here is the rundown of the databases I have experience with:
MySQL: Fairly simple to install (especially if you run Debian Linux), but
configuration, especially adding users, can be a pain. A separate open
source project called "mysql-navigator" makes it fairly easy to do
simple queries, inserts, etc. In most of my tests it outperforms
PostgreSQL, but your mileage will vary. It has a sane CLI that supports
modern features like line history, etc (unlike the horrific SQLPlus).
PostgreSQL: People often say that it is a more "academically
correct" database than MySQL. I've also found it to be quite a bit
easier to set up. Their GUI (called "pgaccess") is simplistic, but does
most things you need. Has a CLI similiar to MySQL's.
HypersonicSQL: By far the easiest to set up (just drop the jar in your
CLASSPATH), but is java only, can be rather slow, and has no GUI tools
available that I know of (except various free vanilla-JDBC GUI tools).
We feel that Kodo works quite well with all these DBs. The MySQL JDBC
driver seems a bit less buggy than Postgres', but their transaction
support is very recent and not very well tested. If I had to pick one or
the other, I would probably go with MySQL.
David Ezzio <[email protected]> wrote:
Hi everyone,
In terms of ease of setup and use, tools to view info in the database, and least difficulty in
running with Kodo, what is the best open source database to use? I'm use to using Oracle and
SQLPlus. I need to use an open source DB for a learning environment, and I'd like your informed
opinion.
Thanks,
David Ezzio--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code--
Mike Bridge -
Skype to release an Open Source linux client
Apparently, Skype will be releasing an open source linux client.
http://share.skype.com/sites/linux/2009 … ource.htmlwonder wrote:http://bbs.archlinux.org/viewtopic.php?id=83856
Yup. -
Hi Abe,
Will only EJB3 be open sourced or JDO as well? Will Kodo continue on JDO2
route?
Thank you
AlexAlex,
Your question and many like it are answered here:
http://dev2dev.bea.com/
Alex Roytman wrote:
Hi Abe,
Will only EJB3 be open sourced or JDO as well? Will Kodo continue on JDO2
route?
Thank you
Alex
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com -
Titan Eclipse plug-ins released in open source
Dear all,
we are happy to announce that the source code of Eclipse plug-ins, after being migrated to ANTLR 4, has been released in github, see https://github.com/eclipse/titan.EclipsePlug-ins,
together with a number of new test ports and protocol modules.
The Eclipse plug-in installable package can be downloaded from https://www.eclipse.org/downloads/download.php?file=/titan/TITAN_Designer_and_Executor_plugin-5.3.pl1-opensource.zip
, and it contains all external dependencies of the plug-ins not available in Eclipse directly (not part of an Orbit package).
It is a zipped update site, which , when downloaded , can be unpacked and used as a local update site to install the plug-ins.
With this, the open sourcing project of Titan can be considered completed.
Eclipse Titan consists of the compilation and execution environment, including native codecs for BER , generic binary, generic text, XML, JSON,
plus a number of utilities for log handling, XML schema conversion etc. (see https://github.com/eclipse/titan.core);
the afore-mentioned set of Eclipse plug-ins (Designer to assist in developing TTCN-3 code; Executor to control execution from Eclipse;
LogViewer to represent logs in a graphical format; Titanium to assist in code refactoring, code smell detection etc.)
plus a tool-box which at the moment consists of 17 test ports and 33 protocol modules with different encodings and a library of external functions.
Depending on requests, more protocol modules and test ports could be released later.
Titan development will continue internally within Ericsson, but we hope for contributors, either for TTCN-3 code,
or for Titan core/plug-ins and test ports/protocol modules respectively, especially for domains not yet covered by Titan.
On behalf of the Ericsson Titan developer team
Elemer LelikNot aware of any open source plugins, though there are lots of sample in the SDK and online from others.
Be aware that Acrobat 8 is no longer supported by Adobe (as of November 3rd).
From: Adobe Forums <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Date: Sun, 6 Nov 2011 22:07:17 -0800
To: Leonard Rosenthol <[email protected]<mailto:[email protected]>>
Subject: Open-source plug-ins to manipulate Bookmarks and Links
Open-source plug-ins to manipulate Bookmarks and Links
created by OALD<http://forums.adobe.com/people/OALD> in Acrobat SDK - View the full discussion<http://forums.adobe.com/message/4011004#4011004 -
[Solved] Slow graphics with RS780M and open source ati driver
EDIT: Well this is embarrasing. Guess this is why there's a new comers forum. I assumed since I installed a couple days ago my system was up to date. However, running pacman -Syu updated my kernal and it works fine now. SOLVED (I'm an idiot)
Hello Arch community. I've been using Ubuntu for a couple years so know that my hardware can work well enough with linux. Almost everything works great with arch with little setup, but I'm stumped as to how to setup the graphics card.
I'm attempting to use the open source drivers, either xf86-video-ati or xf86-video-radeonhd (I don't care which I use in the end). I have both installed so I can try out both, assuming that doesn't cause problems. I've never tried using the catalyst driver in arch, so I know I don't have remenents of that causing problems. Right I have gnome working, but when dragging a window, resizing a window, scrolling, or watching a video I can see the screen slowly refresh. It is definetly not right.
Here's the information that might help:
[jake@myhost ~]$ lspci | grep Radeon
01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics]
I've tried various configurations. Right now I'm running without an xorg.conf. This is /var/log/Xorg.0.log from the setup without an xorg.conf
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH i686
Current Operating System: Linux myhost 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 07:06:02 UTC 2009 i686
Build Date: 28 May 2009 10:40:05PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 23 11:58:06 2009
(II) Loader magic: 0x1a40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0@1:5:0) ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics] rev 0, Mem @ 0x80000000/268435456, 0x92300000/65536, 0x92200000/1048576, I/O @ 0x00005000/256
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default ati Device 0"
Driver "ati"
EndSection
Section "Screen"
Identifier "Builtin Default ati Screen 0"
Device "Builtin Default ati Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default ati Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default ati Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default ati Device 0"
(==) No monitor specified for screen "Builtin Default ati Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[25] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[27] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[29] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[30] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[31] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[32] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[33] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[34] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[35] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 6.12.2
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "radeon"
(II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so
(II) Module radeon: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 6.12.2
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 2.2.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP),
ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP),
ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI FirePro V8750 (FireGL),
ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850,
ATI Mobility RADEON HD 4850 X2, ATI Radeon 4800 Series,
ATI FirePro RV770, AMD FireStream 9270, AMD FireStream 9250,
ATI FirePro V8700 (FireGL), ATI Mobility RADEON HD 4870,
ATI Mobility RADEON M98, ATI Radeon 4800 Series,
ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
ATI Radeon RV730 (AGP), ATI FirePro M5750, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI RV730 PRO [Radeon HD 4650], ATI FirePro V7750 (FireGL),
ATI FirePro V5700 (FireGL), ATI FirePro V3750 (FireGL), ATI RV610,
ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro,
ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI RV610,
ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon HD 4350,
ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
ATI Mobility Radeon 4500 Series, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon RV710,
ATI Radeon HD 3470, ATI Mobility Radeon HD 3430,
ATI Mobility Radeon HD 3400 Series, ATI Radeon HD 3450,
ATI Radeon HD 3450, ATI Radeon HD 3430, ATI Radeon HD 3450,
ATI FirePro V3700, ATI FireMV 2450, ATI FireMV 2260, ATI FireMV 2260,
ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
ATI Radeon HD 3600 PRO, ATI Mobility Radeon HD 3650,
ATI Mobility Radeon HD 3670, ATI Mobility FireGL V5700,
ATI Mobility FireGL V5725, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3300 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3000 Graphics,
ATI Radeon HD Graphics, ATI Radeon Graphics,
ATI Mobility Radeon HD Graphics, ATI Mobility Radeon Graphics,
ATI Radeon Graphics
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 01@00:05:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[25] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[27] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[29] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[30] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[31] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[32] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[33] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[34] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[35] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(WW) Falling back to old probe method for vesa
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[25] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[26] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[27] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[28] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[29] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[30] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[31] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[32] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[33] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[34] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[35] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[36] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[37] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[38] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[39] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[40] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) RADEON(0): TOTO SAYS 0000000092300000
(II) RADEON(0): MMIO registers at 0x0000000092300000: size 64KB
(II) RADEON(0): PCI bus 1 card 5 func 0
(II) RADEON(0): Creating default Display subsection in Screen section
"Builtin Default ati Screen 0" for depth/fbbpp 24/32
(==) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(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 1.6.1.901, module version = 0.1.0
ABI class: X.Org Video Driver, version 5.0
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(==) RADEON(0): RGB weight 888
(II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
(--) RADEON(0): Chipset: "ATI Radeon HD 3200 Graphics" (ChipID = 0x9612)
(WW) RADEON(0): R600 support is mostly incomplete and very experimental
(--) RADEON(0): Linear framebuffer at 0x0000000080000000
(II) RADEON(0): PCI card detected
(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 1.6.1.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(II) RADEON(0): ATOM BIOS detected
(II) RADEON(0): ATOM BIOS Rom:
SubsystemVendorID: 0x103c SubsystemID: 0x30f2
IOBaseAddress: 0x5000
Filename: BR28896C.bin
BIOS Bootup Message:
HP_QT8 RS780M DDR2 200e/500m
(II) RADEON(0): Framebuffer space used by Firmware (kb): 20
(II) RADEON(0): Start of VRAM area used by Firmware: 0xfffb000
(II) RADEON(0): AtomBIOS requests 20kB of VRAM scratch space
(II) RADEON(0): AtomBIOS VRAM scratch base: 0xfffb000
(II) RADEON(0): Cannot get VRAM scratch space. Allocating in main memory instead
(II) RADEON(0): Default Engine Clock: 500000
(II) RADEON(0): Default Memory Clock: 400000
(II) RADEON(0): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEON(0): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEON(0): Maximum Pixel ClockPLL Frequency Input: 13500
(II) RADEON(0): Minimum Pixel ClockPLL Frequency Input: 1000
(II) RADEON(0): Maximum Pixel Clock: 400000
(II) RADEON(0): Reference Clock: 14320
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:01:05.0
drmOpenDevice: node name is /dev/dri/card0
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/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 -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
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
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
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
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
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
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
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
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
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
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
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
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
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
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
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI.
(II) RADEON(0): using shadow framebuffer
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) RADEON(0): Detected total video RAM=262144K, accessible=262144K (PCI BAR=262144K)
(--) RADEON(0): Mapped VideoRAM: 262144 kByte (128 bit DDR SDRAM)
(II) RADEON(0): Color tiling disabled
(II) RADEON(0): Max desktop size set to 2560x1600
(II) RADEON(0): For a larger or smaller max desktop size, add a Virtual line to your xorg.conf
(II) RADEON(0): If you are having trouble with 3D, reduce the desktop size by adjusting the Virtual line to your xorg.conf
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) RADEON(0): ref_freq: 1432, min_out_pll: 64800, max_out_pll: 120000, min_in_pll: 100, max_in_pll: 1350, xclk: 40000, sclk: 500.000000, mclk: 400.000000
(II) RADEON(0): PLL parameters: rf=1432 rd=12 min=64800 max=120000; xclk=40000
(WW) RADEON(0): LVDS Info:
XRes: 1280, YRes: 800, DotClock: 69300
HBlank: 135, HOverPlus: 48, HSyncWidth: 32
VBlank: 16, VOverPlus: 3, VSyncWidth: 6
(II) RADEON(0): Output VGA-0 has no monitor section
(II) RADEON(0): I2C bus "VGA-0" initialized.
(II) RADEON(0): Output LVDS has no monitor section
(II) RADEON(0): I2C bus "LVDS" initialized.
(II) RADEON(0): Output HDMI-0 has no monitor section
(II) RADEON(0): I2C bus "HDMI-0" initialized.
(II) RADEON(0): Port0:
XRANDR name: VGA-0
Connector: VGA
CRT1: INTERNAL_KLDSCP_DAC1
DDC reg: 0x7e40
(II) RADEON(0): Port1:
XRANDR name: LVDS
Connector: LVDS
LCD1: INTERNAL_KLDSCP_LVTMA
DDC reg: 0x7e50
(II) RADEON(0): Port2:
XRANDR name: HDMI-0
Connector: HDMI-B
DFP1: INTERNAL_UNIPHY
DDC reg: 0x7e60
(II) RADEON(0): I2C device "VGA-0:E-EDID segment register" registered at address 0x60.
(II) RADEON(0): I2C device "VGA-0:ddc2" registered at address 0xA0.
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
Dac detection success
finished output detect: 0
(II) RADEON(0): I2C device "LVDS:E-EDID segment register" registered at address 0x60.
(II) RADEON(0): I2C device "LVDS:ddc2" registered at address 0xA0.
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 2
(II) RADEON(0): EDID data from the display on output: LVDS ----------------------
(II) RADEON(0): Manufacturer: AUO Model: 2774 Serial#: 0
(II) RADEON(0): Year: 2007 Week: 1
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 33 vert.: 21
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): No DPMS capabilities specified
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.590 redY: 0.345 greenX: 0.315 greenY: 0.555
(II) RADEON(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 69.3 MHz Image Size: 331 x 207 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1415 h_border: 0
(II) RADEON(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
(WW) RADEON(0): Unknown vendor-specific block f
(II) RADEON(0): AUO
(II) RADEON(0): B154EW02 V7
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00ffffffffffff0006af742700000000
(II) RADEON(0): 01110103802115780a1cf59758508e27
(II) RADEON(0): 27505400000001010101010101010101
(II) RADEON(0): 010101010101121b0087502010303020
(II) RADEON(0): 36004bcf100000180000000f00000000
(II) RADEON(0): 00000000000000000020000000fe0041
(II) RADEON(0): 554f0a202020202020202020000000fe
(II) RADEON(0): 004231353445573032205637200a0071
finished output detect: 1
(II) RADEON(0): I2C device "HDMI-0:E-EDID segment register" registered at address 0x60.
(II) RADEON(0): I2C device "HDMI-0:ddc2" registered at address 0xA0.
(II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
finished output detect: 2
finished all detect
before xf86InitialConfiguration
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
Dac detection success
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 2
(II) RADEON(0): EDID data from the display on output: LVDS ----------------------
(II) RADEON(0): Manufacturer: AUO Model: 2774 Serial#: 0
(II) RADEON(0): Year: 2007 Week: 1
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 33 vert.: 21
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): No DPMS capabilities specified
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.590 redY: 0.345 greenX: 0.315 greenY: 0.555
(II) RADEON(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 69.3 MHz Image Size: 331 x 207 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1415 h_border: 0
(II) RADEON(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
(WW) RADEON(0): Unknown vendor-specific block f
(II) RADEON(0): AUO
(II) RADEON(0): B154EW02 V7
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00ffffffffffff0006af742700000000
(II) RADEON(0): 01110103802115780a1cf59758508e27
(II) RADEON(0): 27505400000001010101010101010101
(II) RADEON(0): 010101010101121b0087502010303020
(II) RADEON(0): 36004bcf100000180000000f00000000
(II) RADEON(0): 00000000000000000020000000fe0041
(II) RADEON(0): 554f0a202020202020202020000000fe
(II) RADEON(0): 004231353445573032205637200a0071
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
(II) RADEON(0): Output VGA-0 disconnected
(II) RADEON(0): Output LVDS connected
(II) RADEON(0): Output HDMI-0 disconnected
(II) RADEON(0): Using exact sizes for initial modes
(II) RADEON(0): Output LVDS using initial mode 1280x800
after xf86InitialConfiguration
(==) RADEON(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(==) RADEON(0): Will attempt to use R6xx/R7xx EXA support if DRI is enabled.
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 2.4.0
ABI class: X.Org Video Driver, version 5.0
(!!) RADEON(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
(!!) RADEON(0): MergedFB support has been removed and replaced with xrandr 1.2 support
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
[25] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
[26] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
[27] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[28] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[29] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[30] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[31] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[32] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[33] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[34] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[35] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[36] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[37] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[38] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[39] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[40] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) RADEON(0): RADEONScreenInit 80000000 0 0
Output DIG0 transmitter setup success
Blank CRTC 0 success
Disable CRTC 0 success
Disable CRTC memreq 0 success
Blank CRTC 1 success
Disable CRTC 1 success
Disable CRTC memreq 1 success
(II) RADEON(0): RADEONInitMemoryMap() :
(II) RADEON(0): mem_size : 0x10000000
(II) RADEON(0): MC_FB_LOCATION : 0x00cf00c0
(II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
(II) RADEON(0): Depth moves disabled by default
(II) RADEON(0): Allocating from a screen of 262144 kb
(II) RADEON(0): Will use 32 kb for hardware cursor 0 at offset 0x00640000
(II) RADEON(0): Will use 32 kb for hardware cursor 1 at offset 0x00644000
(II) RADEON(0): Will use 6400 kb for front buffer at offset 0x00000000
(II) RADEON(0): Will use 255712 kb for X Server offscreen at offset 0x00648000
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0x00cf00c0 0x00cf00c0
(II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
(==) RADEON(0): Backing store disabled
(WW) RADEON(0): Direct rendering disabled
(EE) RADEON(0): Acceleration initialization failed
(II) RADEON(0): Acceleration disabled
(II) RADEON(0): DPMS enabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Textured video requires CP on R5xx/R6xx/R7xx/IGP
Output CRT1 disable success
Output DIG0 transmitter setup success
(II) RADEON(0): DIG0 transmitter: Coherent Mode enabled
Output DIG0 transmitter setup success
Blank CRTC 0 success
Disable CRTC 0 success
Disable CRTC memreq 0 success
Blank CRTC 1 success
Disable CRTC 1 success
Disable CRTC memreq 1 success
Output DIG0 transmitter setup success
Mode 1280x800 - 1415 816 10
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0x00cf00c0 0x00cf00c0
(II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
freq: 69300000
best_freq: 69298571
best_feedback_div: 813
best_ref_div: 14
best_post_div: 12
(II) RADEON(0): crtc(0) Clock: mode 69300, PLL 69290
(II) RADEON(0): crtc(0) PLL : refdiv 14, fbdiv 0x32D(813), pdiv 12
Set CRTC 0 PLL success
Set CRTC Timing success
Set CRTC 0 Overscan success
Not using RMX
scaler 0 setup success
Set CRTC 0 Source success
crtc 0 YUV disable setup success
Output DIG0 transmitter setup success
Output DIG2 encoder setup success
Output DIG2 encoder setup success
Output DIG0 transmitter setup success
Output DIG0 transmitter setup success
Enable CRTC memreq 0 success
Enable CRTC 0 success
Unblank CRTC 0 success
Output DIG0 transmitter setup success
Output CRT1 disable success
(II) RADEON(0): DIG0 transmitter: Coherent Mode enabled
Output DIG0 transmitter setup success
Blank CRTC 1 success
Disable CRTC 1 success
Disable CRTC memreq 1 success
(II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 331 x 207
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 2.2.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.1.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) Synaptics touchpad driver version 1.1.2
(**) Option "Device" "/dev/input/event13"
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
(II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
(II) SynPS/2 Synaptics TouchPad: buttons: left right middle
(**) Option "TapButton1" "1"
(**) Option "TapButton2" "3"
(**) Option "TapButton3" "2"
(--) SynPS/2 Synaptics TouchPad: touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
(**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
(**) SynPS/2 Synaptics TouchPad: (accel) filter chain progression: 2.00
(**) SynPS/2 Synaptics TouchPad: (accel) filter stage 0: 20.00 ms
(**) SynPS/2 Synaptics TouchPad: (accel) set acceleration profile 0
(--) SynPS/2 Synaptics TouchPad: touchpad found
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event6"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
Dac detection success
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1415 800 803 809 816 -hsync -vsync (49.0 kHz)
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 2
(II) RADEON(0): EDID data from the display on output: LVDS ----------------------
(II) RADEON(0): Manufacturer: AUO Model: 2774 Serial#: 0
(II) RADEON(0): Year: 2007 Week: 1
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 33 vert.: 21
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): No DPMS capabilities specified
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.590 redY: 0.345 greenX: 0.315 greenY: 0.555
(II) RADEON(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 69.3 MHz Image Size: 331 x 207 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1415 h_border: 0
(II) RADEON(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
(WW) RADEON(0): Unknown vendor-specific block f
(II) RADEON(0): AUO
(II) RADEON(0): B154EW02 V7
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00ffffffffffff0006af742700000000
(II) RADEON(0): 01110103802115780a1cf59758508e27
(II) RADEON(0): 27505400000001010101010101010101
(II) RADEON(0): 010101010101121b0087502010303020
(II) RADEON(0): 36004bcf100000180000000f00000000
(II) RADEON(0): 00000000000000000020000000fe0041
(II) RADEON(0): 554f0a202020202020202020000000fe
(II) RADEON(0): 004231353445573032205637200a0071
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
Dac detection success
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1415 800 803 809 816 -hsync -vsync (49.0 kHz)
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 2
(II) RADEON(0): EDID data from the display on output: LVDS ----------------------
(II) RADEON(0): Manufacturer: AUO Model: 2774 Serial#: 0
(II) RADEON(0): Year: 2007 Week: 1
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 33 vert.: 21
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): No DPMS capabilities specified
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.590 redY: 0.345 greenX: 0.315 greenY: 0.555
(II) RADEON(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 69.3 MHz Image Size: 331 x 207 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1415 h_border: 0
(II) RADEON(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
(WW) RADEON(0): Unknown vendor-specific block f
(II) RADEON(0): AUO
(II) RADEON(0): B154EW02 V7
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00ffffffffffff0006af742700000000
(II) RADEON(0): 01110103802115780a1cf59758508e27
(II) RADEON(0): 27505400000001010101010101010101
(II) RADEON(0): 010101010101121b0087502010303020
(II) RADEON(0): 36004bcf100000180000000f00000000
(II) RADEON(0): 00000000000000000020000000fe0041
(II) RADEON(0): 554f0a202020202020202020000000fe
(II) RADEON(0): 004231353445573032205637200a0071
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
(II) RADEON(0): Output: VGA-0, Detected Monitor Type: 0
Dac detection success
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1415 800 803 809 816 -hsync -vsync (49.0 kHz)
(II) RADEON(0): Output: LVDS, Detected Monitor Type: 2
(II) RADEON(0): EDID data from the display on output: LVDS ----------------------
(II) RADEON(0): Manufacturer: AUO Model: 2774 Serial#: 0
(II) RADEON(0): Year: 2007 Week: 1
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 33 vert.: 21
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): No DPMS capabilities specified
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.590 redY: 0.345 greenX: 0.315 greenY: 0.555
(II) RADEON(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 69.3 MHz Image Size: 331 x 207 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1360 h_blank_end 1415 h_border: 0
(II) RADEON(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
(WW) RADEON(0): Unknown vendor-specific block f
(II) RADEON(0): AUO
(II) RADEON(0): B154EW02 V7
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00ffffffffffff0006af742700000000
(II) RADEON(0): 01110103802115780a1cf59758508e27
(II) RADEON(0): 27505400000001010101010101010101
(II) RADEON(0): 010101010101121b0087502010303020
(II) RADEON(0): 36004bcf100000180000000f00000000
(II) RADEON(0): 00000000000000000020000000fe0041
(II) RADEON(0): 554f0a202020202020202020000000fe
(II) RADEON(0): 004231353445573032205637200a0071
(II) RADEON(0): EDID vendor "AUO", prod id 10100
(II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
I've also tried it with many xorg.conf files without finding any which give me the same graphics performance I have in ubuntu. Here's the one I was using, with the comments showing some other things I tried.
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "extmod"
Load "dbe"
Load "dri2"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30.0 - 60.0
VertRefresh 55.0 - 70.0
#Option "UseEdidFreqs" "1"
Option "DPMS"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "AccelMethod" # [<str>]
#Option "offscreensize" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "ignoreconnector" # [<str>]
#Option "forcereduced" # [<bool>]
#Option "forcedpi" # <i>
#Option "useconfiguredmonitor" # [<bool>]
#Option "HPD" # <str>
#Option "NoRandr" # [<bool>]
#Option "RROutputOrder" # [<str>]
#Option "DRI" # [<bool>]
#Option "TVMode" # [<str>]
#Option "ScaleType" # [<str>]
#Option "UseAtomBIOS" # [<bool>]
#Option "AtomBIOS" # [<str>]
#Option "UnverifiedFeatures" # [<bool>]
#Option "Audio" # [<bool>]
#Option "HDMI" # [<str>]
#Option "COHERENT" # [<str>]
Identifier "Card0"
#Driver "radeonhd"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RS780M/RS780MN [Radeon HD 3200 Graphics]"
BusID "PCI:1:5:0"
#Added optimizations
Option "AGPMode" "8"
Option "ColorTiling" "on"
Option "AccelMethod" "EXA"
#Option "AccelMethod" "XAA"
#Option "EnablePageFlip" "on"
#Option "AGPFastWrite" "yes"
#Option "XAANoOffScreenPixMaps" "1"
Option "RenderAccel" "true"
Option "DRI" "On"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Extensions"
# Option "Composite" "On"
Option "Composite" "Disable"
EndSection
#Section "ServerFlags"
# Option "AIGLX" "On"
#EndSection
Section "DRI"
Group "video"
Mode 0666
EndSection
Just in case this help:
[jake@myhost ~]$ modinfo radeon
filename: /lib/modules/2.6.29-ARCH/kernel/drivers/gpu/drm/radeon/radeon.ko
license: GPL and additional rights
description: ATI Radeon
author: Gareth Hughes, Keith Whitwell, others.
depends: drm
vermagic: 2.6.29-ARCH SMP preempt mod_unload 686
parm: no_wb:Disable AGP writeback for scratch registers (int)
[jake@myhost ~]$ modinfo drm
filename: /lib/modules/2.6.29-ARCH/kernel/drivers/gpu/drm/drm.ko
license: GPL and additional rights
description: DRM shared core routines
author: Gareth Hughes, Leif Delgass, José Fonseca, Jon Smirl
depends: agpgart,i2c-core
vermagic: 2.6.29-ARCH SMP preempt mod_unload 686
parm: debug:Enable debug output (int)
Any ideas?
Last edited by Coward (2009-06-25 06:40:51)Coward wrote:I can't see a way to mark this thread as solved or anything, but it is solved.
Just click edit on the lower right of your first post and you can edit the subject
http://bbs.archlinux.org/viewtopic.php?id=50161 -
How to open an extension programatically?
Hi,
I would like to open an extension from my cpp code. How can I do it?
Regards
maddy1907I work on the InDesign SDK. I'm not sure exactly which version of InDesign you are developing plug-ins for, but given you are also creating HTML extensions I assume you are using InDesign CC 9.1 or later.
There is no public API in InDesign for you to launch an extension from a plug-in. It is more common for the reverse of what you are talking about: an extension (with menu item and UI) that calls into native plug-in APIs.
However....
In InDesign CC 9.0 we exposed some plugplug APIs for the first time, enabling you to construct and dispatch CSXS events from native InDesign plug-ins. The file is: <sdk>/source/public/interfaces/ui/ICSXSPlugPlugEventHandler.h.
We also added a new sample to the SnippetRunner sample demonstrating how to use the new plugplug APIs (see: <sdk>/source/sdksamples/codesnippets/SnpHelloCSXS.cpp).
More recently I wrote a blog post about communication between native plug-ins and HTML extensions, here: https://blogs.adobe.com/indesignsdk/html-extensions-in-indesign/.
We might consider exposing this functionality in a future release. If you are a member of the pre-release program perhaps you could raise a bug about this? If not I can raise the subject internally. If this did happen, it wouldn't be overnight so I would definitely try an alternative workflow for your plug-in/extension in the mean time. Can you share why you wish to launch the extension from the plug-in and not the other way round? Perhaps we can help you find a workaround.
Tim -
New open source webmail available
This morning AtMail has released a new version, an open source version. This is a true open source project and will be a great improvement over the existing horde and squirrel mail packages. The interface is based off of their existing simple ajax interface and has been under development in the corporate arena for a couple of years now. You can find the full details on the AtMail Blog (http://blog.atmail.com).
Great tool, thanks a lot for sharing it.
Installed it and built "Hello, world" extension, now trying to convert my existing extension project for this. Packaging CS5 / CS6 versions alone is priceless.
Maybe a dumb question, but is it possible to switch .json and output name in command line? I have extension with 5 different versions, they have different licenses etc., so it would be great to type
csxs package config1.json extension1.zxp
csxs package config2.json extension2.zxp
and so on? I'd put it all into one .sh script
sorry if it's all already available and I just missed this part in documentation
Maybe you are looking for
-
Screen Sharing not remembering Dual Monitor preferences
Before I upgraded my my MBP to Snow Leopard, Screen Sharing would remember to connect to only the primary monitor on my G5. In Snow Leopard, I can't get it to remember it, so it connects to both monitors by defualt each time I use it. Anyone have sug
-
Hard drive constantly clicking
The 2TB hard drive of my 2011 iMac is almost constantly clicking like toc-toc....toc-toc....toc-toc, with a frequency of about 30 times per minute, while "at rest" (no activity from keyboard or anything). Funny thing is, it does it too when I'm runni
-
Strange issue while trying to delete files - locked item that I can't find
I am working on clearing off some hard drive space, and my first step was to remove some unneeded items from an external HD to make some space there. When I drag the folder I'm trying to delete to the trash, I first get a message that the items will
-
Hi Guys, hope someone can help. I am trying to create an ODI operator user that can only view Sessions in Operator and cannot make any changes or stop/start. In Security Manager I have created a user and added the Profiles "CONNECT" and "NG REPOSITOR
-
Windows Fax/Scan cannot fax through J4680.
My HP J4680 is connected wirelessly and all functions work fine, including fax. However, I would like to fax from the computer. Is this possible? Do I need additional hardware? Any help would be great. Thanks