Final Release codes shows only 5 levels

Hi Experts,
I am configuring PO Release strategy with 8 release codes. Final release can be done with any release code without any dependecy with other codes.
When I am simulating the Release strategy, I am getting only 5 final release codes are coming, instead of 8 release codes.
Can somebody help me in this issue.
Thanks,
Satya

Hi,
Go to OMGS and check the Release statuses as well as release simulation who many release code is appearing.
regards

Similar Messages

Possible to Have ToC Default to Show Only Top Level (collapse sublevels)?

Howdy!
I'll bet I'm not the only one wishing for this. Let's say you're using Captivate 4's Table of Contents feature with a longish movie of Cp slides, which is chunked into bite-size sections content-wise. In the ToC, though, you can't mimic that same organization scheme; at least, the learner would first need to collapse all the ToC folders you've created so they see only the top-level listing.
This can be a critical issue: keeping the at-first-glance list in the ToC brief enough to be inviting to learners, yet allowing learners to drive which details are currently visible.
A movie's topical hierarchy could be along these lines, for example ...
Section 1 - National Brands
What are National Brands?
Why Are They Important to Our Business?
Working with Nat. Brands
Practice Your Knowledge
Section 2 - International Brands
What are International Brands?
Why Are They Important to Our Business?
Working with Intl. Brands
Practice Your Knowledge
You'd like to organize the ToC to show only the section titles (1st level) and to suppress the 2nd-level detail (slide titles) until the learner chooses to expand the folder to see those details.
I've tried things like grouping the slides into sections in the Storyboard view and organizing the slides into sections strictly within the ToC -- both to no avail.
Has anyone solved for this need yet?
I'm all ears, and you'd be doing learners of the world a huge favor.
Thanks!

Hi, Jim.
Thanks for being 'on the case' and looking into this so quickly. Your
findings are encouraging, although my user base is generally working with
IE 6 and FP8 or 9.
Since the only thing I may influence is getting IT to help push out FP10,
I'm hoping it's more of a player- than a browser-version issue.
I'll test things out by Monday and let you know the results. Wish me luck!
Dave
                                                                                From:       Jim Leichliter <[email protected]>
To:         Dave Tressler <[email protected]>
Date:       03/26/2010 06:02 PM
Subject:    Possible to Have ToC Default to Show Only Top Level (collapse
              sublevels)?
Dave,
I just tested this on my local web server and it worked fine. I created a
blank project with 8 slides. Created my TOC with grouping... 2 slides in
each group. I turned on self paced learning. I tried with and without the
widget and it picked up where I left off in either case. See
https://docs.google.com/leaf?id=0B86WuEq6SVwRNWIwMjhjODctMjE2Yy00MWE2LWI5YzEtMGQxYzNjOWQ0Z mI2&hl=en.
I published using FP10 and IE8 to view. Notice any difference between
your project and this one?
Thanks,
Jim Leichliter

How to make the report shows only top level steps

HI,
I use many subsequences in my tests. I have no interest to see them in the report. How can I force the report to show only top level steps?
Thanks
Rafi

I needed to prevent 'Skipped' steps from appearing in my reports. One way to do this is to override the SequenceFilePostResultListEntry callback in the model. You do this by clicking on Edit and then Sequence File Callbacks and then find SequenceFilePostResultListEntry in the list and click the Add button.
Edit your new callback in your sequence file to check for a pre-condition. In my case I checked for Parameters.Result.Status == "Skipped" since that parameter is set to Skipped, Done, etc. based on the result.
If the condition was true then my only step in the callback was to set Parameters.DiscardResults = True. The TestStand model will then throw that result away when it processes the report. You could add a step for every type of data you wish to discard.
A second method that is easier to implement, but time consuming, is to select each step you DON'T want in your report and bring up the Properties for that step. Under the Run Options tab, deselect the Record Results box. That will keep the results of that step out of the report, but you have to do this for EVERY step you don't want to have reported. The first approach I provided acts to filter the results.
If you aren't sure what the Parameters.Result.Status will be, then set a breakpoint after that step is executed and scan the parameters when the sequence is halted there. You can then detect the actual text used as a result for that step, such as "Done" and can set your pre-condition appropriately.

Hierarchy authorization details show only last level

Hi,
I am facing on a hierarchy problem displayed on the Bex: The hierarchy has 9 levels, e.g. the organisation structure of the company from level 1 to level 9.
I made from the transaction RSSM :
Authorization from the hierarchy i entered for each level from 1 to 9 :
Type of authorisation : 1 (subtree below node)
Hierarchy level       : blank
Validity period       : blank
Node variable default value : blank
I made from the transaction PFCG :
Created a role for the user with the authorization :
Sap Business information warehouse - reporting (RSR)
value : 8055 (company code)
Unique ID for authorization : level_3
I need to authorize the user to execute a querry of his level (exemple level 3) and all the level below him (to the 9th level)
When the query is generated,(the query is using a variable hierarchy ) I get the lowest level displayed and shows only 2 key figures and values.
Any ideas ?
You assistance will be appreciated.
Thong VANNAXAY

Hi,
1007372 wrote:
Hi,
How to get only the last level in Oracle SQL Hierarchy Query?Depending on your requirements:
WHERE   CONNECT_BY_ISLEAF = 1
I hope this answers your question.
If not, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only), and also post the results you want from that data.
Explain, using specific examples, how you get those results from that data.
If you can show what you want to do using commonly available tables (such as scott.emp, which contains a hierarchy), then you don't need to post any sample data; just the results and the explanation.
Always say which version of Oracle you're using (e.g., 11.2.0.2.0). This is always important, but especially so with CONNECT BY queries, because every version since Oracle 7 has had significant improvements in this area.
See the forum FAQ {message:id=9360002}

Modify Chart Legend Data Behaviour to show only lowest level of drill

I have a chart with a legend in OBIEE 11g.
When I click on chart data or legend it drills to the next level of the hierarchy which is what I want.
However the legend show all levels of the hierarchy in the legend data like this:
"Level 1"."Level 2"."Level 3".
This is very cluttered and redundant as Level 1 & Level 2 are the same for all items.
What I want is that it only shows the lowest level of a hierarchy that has been drilled to eg.
"Level 3"
Is it possible to do this? I've already tried the user guide, on this forum or on google search.
Thanks in advance.

Not sure its doable out the box,
You could hack the popchart JS files I guess, John Minkjan's blog describes some changes , in particular on mouse-hover activity but they should show where to start.

Nav pane showing only 2 levels of headings

My top 2 heading levels, which show correctly in the Nav Pane are standard Heading 1 and Heading 2, but my third level is one I made up, Head3. I don't know whether that is responsible for the Nav Pane omitting the third level. I have three TOC's, one for
only level 1, one for levels 1 and 2, and one for all three levels. These look ok.
More clues: 1. Rt-ck on an entry in the Nav Pane and choose Show Heading Levels, set it to All. Makes no difference.
2. If I change some of my Head3's to Heading 3, those do show in the Nav Pane. But until today I had my Head3's showing too.

Modify your Head3 style so that its "Outline level" is set to 3. In the Modify Style dialog box, click Format, Paragraph; you'll find the "Outline level" option on the Indents and Spacing tab.
Stefan Blom, Microsoft Word MVP

Deleted release code appearing in PO

Hi all,
i had a release code SE with PO value limit from 0-10000 and another release code SM with PO value limit from 10001 - 50000.
now the business decided to remove SE from the release process. So i deleted SE and changed PO value limit for SM from 0-50000.
all other charecteristics for both these release codes are same.
now when i create a PO for amount less than 10000 , SE again appears in the release , though it has been deleted and in ME28 , i cant see release code SE using F4
how can this be resolved?
Regards
Mangesh.

Hi,
If the release code is only deleted than all other steps of the strategy need to be redefined again,Like Release prerequisites .Please check
DBehera

Release code - Purchase requisition - Release Procedure

Hello,
In the purchase requisition release procedure with classification, we are defining release codes say K, P etc.
My doubt is , Is this being defined else where based upon the designatin of the person in the organisation, or else, we are defining here straight away?
Best regards,
K.Kumaran.

HI
You are correct, you need to define the release code there only. There is no other place where it is defined. What you have to ensure is make sure that it is of Two character and not single. Assign the codes against the designation of the person as per your requirement.
Regards

Report to Show PR that are not released by release codes

Hello Experts,
I would like to know if there is any report on SAP 6.0 that shows all the purchase requisitions that are not released which shows the releease code (the person's name who has to release the PR). In me55 only could be found by release code, and it is required, I cannot has a report
I think that there is not, but i would like to confirm it.
Thank you in advance,
Best regards

Hello,
1)Go to ME5A t-code & select DYNAMIC SELECTIONS.
2)Select "Purchase Requisition" section and you can make use of parameters like Release Code, Release Indicator , Release Status etc., to fetch the required results.
Hope this helps you in resolving your matter.
Regards
Mahesh

Release Code 99 High Level Release

Hi Guru's
I have a question about release codes in config. It seems as if in the config I am looking at, someone has set release code 99 (High Level Release) on several of the levels. Does High Level Release mean that this code can release any/all amounts? If not, what does "High Level Release" mean.
Thanks in advance. Points will be given.
SW

HI Steven,
Assingning release code as 99 mean, it is not the highest no of SL no.
Release code means uniquely identfication of a certain User login under one Release Group. Based on this release stragey (Approval procedures) will be set.
It doesnt mean that assigning Rel. code as 99 becomes as a Highest release level.
Actually there are only 8 release levels will be there, in that 8 levels sequence 8 is teh highest level of authorization and 1 is the first level authorization., in that we can assign this Release code 99 either as 1 or 3 or even 8.
if it is solved ur problem pls rewards points.
Thanks
Muralidharan

After changing the battery in my iphone 4s, the phone will not boot up. I only see the apple and when it sits for a few minutes, a code shows above it. What is going on? Did I damage the phone by replacing the battery?

My sister gave me her iphone 4s for my son. It needed a new battery so, I bought one and replaced it. after doing so, it will not power up. I can only see the apple on the screen and when left for a few minutes.... 10 lines of numbers and codes show up at the top of the screen. Did I ruin the iphone by replacing the battery? Was a simple switch so I don't understand what is going on. Have never had one of these before.

iPhones are not user servicable.
Take the device to a competent repair person or buy a new one.

Release strategy: User should release only with his highest release code

Hello,
Because of personel absences we want to configure the release strategy so that:
User A or user B releases in the normal case the first level of a PO (with release code 01).
User C (Manager) releases after release code 01 with release code 02.
User A is deputy of user C. In this case user B will release with code 01 and user A will release with code 02.
Because user A can use depending of the case release code 01 or 02 (C deputy) it must be avoided that user B sets release code 01 and 02 for the same purchase order.
Do you know about a solution for this issue
Br
Manuel

Dear W1N,
But the systems knows that A released with code 01 and when A tries to release with code 02 the system knows that the same person of release code 01 is trying with release code 02.
<b>The aim is to avoid the second release from the same person and not to automate the release strategy.</b>
In such a case A has to cancel the release for code 01 (ME28) and wait until B is reachable to do the release of code 01.
When C is absent A knows that his task is to release code 02.
Is this check really not possible?
Best regards
Manuel

Browser shows only codes instead of graphics

Hi,
I've got a problem
When I test out (f12) my design, the window browser showed
only html and my style sheet. Normally, I would see my graphics.
Does this have anything to do with MYSQL and APACHE on ? I am
using Wamp and dreamweaver cs

Post a link to the site if you hope to have someone figure it
out..
gary
"RunRunforest" <[email protected]> wrote in
message
news:gb8ld2$jc1$[email protected]..
> Hi,
>
> I've got a problem
>
> When I test out (f12) my design, the window browser
showed only html and
> my
> style sheet. Normally, I would see my graphics.
>
> Does this have anything to do with MYSQL and APACHE on ?
I am using Wamp
> and
> dreamweaver cs
>
>
>

Dual monitor problem (2nd screen black, shows only "_")

Hi, im trying to configure dual screen, tested lot of configs but stuck with this problem: second monitor shows only "_" in top-left corrnerm.
My current Xorg is:
Section "Monitor"
Identifier "LewyMonitor"
Option "DPMS"
Option "Enable" "true"
EndSection
Section "Monitor"
Identifier "PrawyMonitor"
Option "DPMS"
Option "Enable" "true"
EndSection
Section "Device"
Identifier "LewaKarta"
BusID "PCI:0:9:0"
Driver "mach64"
Screen 0
EndSection
Section "Device"
Identifier "PrawaKarta"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "LewyEkran"
Device "LewaKarta"
Monitor "LewyMonitor"
DefaultDepth 15
EndSection
Section "Screen"
Identifier "PrawyEkran"
Device "PrawaKarta"
Monitor "PrawyMonitor"
DefaultDepth 24
EndSection
Section "DRI"
Mode 0666
EndSection
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "LewyEkran" 0 0
Screen 1 "PrawyEkran" RightOf "LewyEkran"
EndSection
Im using:
00:09.0 VGA compatible controller: ATI Technologies Inc 3D Rage II+ 215GTB [Mach64 GTB] (rev 9a)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1)
Xorg.0.log:
[ 2445.373]
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.
[ 2445.373]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 2445.373] X Protocol Version 11, Revision 0
[ 2445.373] Build Operating System: Linux 2.6.34-ARCH i686
[ 2445.373] Current Operating System: Linux myhost 2.6.34-ARCH #1 SMP PREEMPT Tue Aug 10 21:38:22 CEST 2010 i686
[ 2445.374] Kernel command line: root=/dev/disk/by-uuid/cd43eabd-ff42-4d85-be67-b98bd0d6e27e ro
[ 2445.374] Build Date: 21 June 2010 11:54:27AM
[ 2445.374]
[ 2445.374] Current version of pixman: 0.18.2
[ 2445.374] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2445.374] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2445.374] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 27 04:01:41 2003
[ 2445.374] (==) Using config file: "/etc/X11/xorg.conf"
[ 2445.374] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2445.375] (==) ServerLayout "X.org Configured"
[ 2445.375] (**) |-->Screen "LewyEkran" (0)
[ 2445.375] (**) | |-->Monitor "LewyMonitor"
[ 2445.376] (**) | |-->Device "LewaKarta"
[ 2445.376] (**) |-->Screen "PrawyEkran" (1)
[ 2445.376] (**) | |-->Monitor "PrawyMonitor"
[ 2445.376] (**) | |-->Device "PrawaKarta"
[ 2445.398] (==) Automatically adding devices
[ 2445.398] (==) Automatically enabling devices
[ 2445.398] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2445.398] Entry deleted from font path.
[ 2445.398] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2445.398] Entry deleted from font path.
[ 2445.398] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2445.398] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2445.398] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2445.398] (II) Loader magic: 0x81e9d00
[ 2445.398] (II) Module ABI versions:
[ 2445.398] X.Org ANSI C Emulation: 0.4
[ 2445.398] X.Org Video Driver: 7.0
[ 2445.399] X.Org XInput driver : 9.0
[ 2445.399] X.Org Server Extension : 3.0
[ 2445.419] (--) PCI: (0:0:9:0) 1002:4755:1002:4755 ATI Technologies Inc 3D Rage II+ 215GTB [Mach64 GTB] rev 154, Mem @ 0xcc000000/16777216, 0xcfffd000/4096, I/O @ 0x0000d800/256, BIOS @ 0x????????/131072
[ 2445.437] (--) PCI:*(0:1:0:0) 10de:0110:0000:0000 nVidia Corporation NV11 [GeForce2 MX/MX 400] rev 161, Mem @ 0xce000000/16777216, 0xc0000000/134217728, BIOS @ 0x????????/65536
[ 2445.437] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2445.437] (II) LoadModule: "extmod"
[ 2445.438] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2445.438] (II) Module extmod: vendor="X.Org Foundation"
[ 2445.438] compiled for 1.8.1.902, module version = 1.0.0
[ 2445.438] Module class: X.Org Server Extension
[ 2445.438] ABI class: X.Org Server Extension, version 3.0
[ 2445.438] (II) Loading extension MIT-SCREEN-SAVER
[ 2445.438] (II) Loading extension XFree86-VidModeExtension
[ 2445.438] (II) Loading extension XFree86-DGA
[ 2445.438] (II) Loading extension DPMS
[ 2445.438] (II) Loading extension XVideo
[ 2445.438] (II) Loading extension XVideo-MotionCompensation
[ 2445.438] (II) Loading extension X-Resource
[ 2445.439] (II) LoadModule: "dbe"
[ 2445.439] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2445.439] (II) Module dbe: vendor="X.Org Foundation"
[ 2445.439] compiled for 1.8.1.902, module version = 1.0.0
[ 2445.439] Module class: X.Org Server Extension
[ 2445.439] ABI class: X.Org Server Extension, version 3.0
[ 2445.439] (II) Loading extension DOUBLE-BUFFER
[ 2445.439] (II) LoadModule: "glx"
[ 2445.439] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2445.440] (II) Module glx: vendor="X.Org Foundation"
[ 2445.440] compiled for 1.8.1.902, module version = 1.0.0
[ 2445.440] ABI class: X.Org Server Extension, version 3.0
[ 2445.440] (==) AIGLX enabled
[ 2445.440] (II) Loading extension GLX
[ 2445.440] (II) LoadModule: "record"
[ 2445.440] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2445.440] (II) Module record: vendor="X.Org Foundation"
[ 2445.440] compiled for 1.8.1.902, module version = 1.13.0
[ 2445.441] Module class: X.Org Server Extension
[ 2445.441] ABI class: X.Org Server Extension, version 3.0
[ 2445.441] (II) Loading extension RECORD
[ 2445.441] (II) LoadModule: "dri"
[ 2445.441] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2445.441] (II) Module dri: vendor="X.Org Foundation"
[ 2445.441] compiled for 1.8.1.902, module version = 1.0.0
[ 2445.441] ABI class: X.Org Server Extension, version 3.0
[ 2445.441] (II) Loading extension XFree86-DRI
[ 2445.441] (II) LoadModule: "dri2"
[ 2445.442] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2445.442] (II) Module dri2: vendor="X.Org Foundation"
[ 2445.442] compiled for 1.8.1.902, module version = 1.2.0
[ 2445.442] ABI class: X.Org Server Extension, version 3.0
[ 2445.442] (II) Loading extension DRI2
[ 2445.442] (II) LoadModule: "mach64"
[ 2445.443] (II) Loading /usr/lib/xorg/modules/drivers/mach64_drv.so
[ 2445.443] (II) Module mach64: vendor="X.Org Foundation"
[ 2445.443] compiled for 1.8.0, module version = 6.8.2
[ 2445.443] Module class: X.Org Video Driver
[ 2445.443] ABI class: X.Org Video Driver, version 7.0
[ 2445.443] (II) MACH64: Driver for ATI Mach64 chipsets
[ 2445.443] (++) using VT number 8
[ 2445.448] (II) Primary Device is: PCI 01@00:00:0
[ 2445.449] (II) MACH64(0): Creating default Display subsection in Screen section
"LewyEkran" for depth/fbbpp 15/16
[ 2445.449] (**) MACH64(0): Depth 15, (--) framebuffer bpp 16
[ 2445.449] (==) MACH64(0): Using XAA acceleration architecture
[ 2445.450] (II) MACH64: Mach64 in slot 0:9:0 detected.
[ 2445.450] (II) Loading sub module "int10"
[ 2445.450] (II) LoadModule: "int10"
[ 2445.450] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 2445.450] (II) Module int10: vendor="X.Org Foundation"
[ 2445.451] compiled for 1.8.1.902, module version = 1.0.0
[ 2445.451] ABI class: X.Org Video Driver, version 7.0
[ 2445.580] (II) Loading sub module "ddc"
[ 2445.581] (II) LoadModule: "ddc"
[ 2445.581] (II) Module "ddc" already built-in
[ 2445.581] (II) Loading sub module "vbe"
[ 2445.581] (II) LoadModule: "vbe"
[ 2445.581] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 2445.581] (II) Module vbe: vendor="X.Org Foundation"
[ 2445.581] compiled for 1.8.1.902, module version = 1.1.0
[ 2445.581] ABI class: X.Org Video Driver, version 7.0
[ 2445.582] (II) MACH64(0): VESA BIOS detected
[ 2445.582] (II) MACH64(0): VESA VBE Version 2.0
[ 2445.582] (II) MACH64(0): VESA VBE Total Mem: 1024 kB
[ 2445.582] (II) MACH64(0): VESA VBE OEM: ATI MACH64
[ 2445.582] (II) MACH64(0): VESA VBE OEM Software Rev: 1.0
[ 2445.582] (II) MACH64(0): VESA VBE OEM Vendor: ATI Technologies Inc.
[ 2445.582] (II) MACH64(0): VESA VBE OEM Product: MACH64GT
[ 2445.582] (II) MACH64(0): VESA VBE OEM Product Rev: 01.00
[ 2445.583] (II) MACH64(0): VESA VBE DDC supported
[ 2445.583] (II) MACH64(0): VESA VBE DDC Level 2
[ 2445.583] (II) MACH64(0): VESA VBE DDC transfer in appr. 2 sec.
[ 2445.632] (II) MACH64(0): VESA VBE DDC read successfully
[ 2445.632] (II) MACH64(0): Manufacturer: GSM Model: 4ae0 Serial#: 12170
[ 2445.632] (II) MACH64(0): Year: 2006 Week: 12
[ 2445.632] (II) MACH64(0): EDID Version: 1.3
[ 2445.632] (II) MACH64(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 2445.632] (II) MACH64(0): Sync: Separate SyncOnGreen
[ 2445.632] (II) MACH64(0): Max Image Size [cm]: horiz.: 38 vert.: 30
[ 2445.632] (II) MACH64(0): Gamma: 2.20
[ 2445.632] (II) MACH64(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 2445.632] (II) MACH64(0): First detailed timing is preferred mode
[ 2445.632] (II) MACH64(0): redX: 0.647 redY: 0.346 greenX: 0.292 greenY: 0.602
[ 2445.633] (II) MACH64(0): blueX: 0.149 blueY: 0.130 whiteX: 0.313 whiteY: 0.328
[ 2445.633] (II) MACH64(0): Supported established timings:
[ 2445.633] (II) MACH64(0): 720x400@70Hz
[ 2445.633] (II) MACH64(0): 640x480@60Hz
[ 2445.633] (II) MACH64(0): 640x480@75Hz
[ 2445.633] (II) MACH64(0): 800x600@60Hz
[ 2445.633] (II) MACH64(0): 800x600@75Hz
[ 2445.633] (II) MACH64(0): 832x624@75Hz
[ 2445.633] (II) MACH64(0): 1024x768@60Hz
[ 2445.633] (II) MACH64(0): 1024x768@75Hz
[ 2445.633] (II) MACH64(0): 1280x1024@75Hz
[ 2445.633] (II) MACH64(0): 1152x864@75Hz
[ 2445.633] (II) MACH64(0): Manufacturer's mask: 0
[ 2445.633] (II) MACH64(0): Supported standard timings:
[ 2445.633] (II) MACH64(0): #0: hsize: 640 vsize 480 refresh: 75 vid: 20273
[ 2445.633] (II) MACH64(0): #1: hsize: 800 vsize 600 refresh: 75 vid: 20293
[ 2445.633] (II) MACH64(0): #2: hsize: 1024 vsize 768 refresh: 75 vid: 20321
[ 2445.633] (II) MACH64(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 2445.633] (II) MACH64(0): Supported detailed timing:
[ 2445.633] (II) MACH64(0): clock: 108.0 MHz Image Size: 376 x 301 mm
[ 2445.633] (II) MACH64(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 2445.633] (II) MACH64(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 2445.633] (II) MACH64(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 140 MHz
[ 2445.634] (II) MACH64(0): Monitor name: L1952S
[ 2445.634] (II) MACH64(0): Monitor name:
[ 2445.634] (II) MACH64(0): EDID (in hex):
[ 2445.634] (II) MACH64(0): 00ffffffffffff001e6de04a8a2f0000
[ 2445.634] (II) MACH64(0): 0c1001036a261e78eaec54a5584a9a26
[ 2445.634] (II) MACH64(0): 215054a56b80314f454f614f81800101
[ 2445.634] (II) MACH64(0): 010101010101302a009851002a403070
[ 2445.634] (II) MACH64(0): 1300782d1100001e000000fd00384b1e
[ 2445.634] (II) MACH64(0): 530e000a202020202020000000fc004c
[ 2445.634] (II) MACH64(0): 31393532530a202020202020000000fc
[ 2445.634] (II) MACH64(0): 000a2020202020202020202020200046
[ 2445.634] (II) MACH64(0): EDID vendor "GSM", prod id 19168
[ 2445.634] (II) MACH64(0): Using EDID range info for horizontal sync
[ 2445.634] (II) MACH64(0): Using EDID range info for vertical refresh
[ 2445.634] (II) MACH64(0): Printing DDC gathered Modelines:
[ 2445.634] (II) MACH64(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 2445.634] (II) MACH64(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 2445.634] (II) MACH64(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 2445.634] (II) MACH64(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 2445.634] (II) MACH64(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 2445.634] (II) MACH64(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 2445.634] (II) MACH64(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 2445.635] (II) MACH64(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 2445.635] (II) MACH64(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 2445.635] (II) MACH64(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 2445.635] (II) MACH64(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 2445.635] (II) MACH64(0): BIOS Data: BIOSSize=0x8000, ROMTable=0x00FC.
[ 2445.635] (II) MACH64(0): BIOS Data: ClockTable=0x06AE, FrequencyTable=0x0000.
[ 2445.635] (II) MACH64(0): BIOS Data: LCDTable=0x0000.
[ 2445.635] (II) MACH64(0): BIOS Data: VideoTable=0x0000, HardwareTable=0x0000.
[ 2445.635] (II) MACH64(0): BIOS Data: I2CType=0x00, Tuner=0x00, Decoder=0x00, Audio=0x0F.
[ 2445.635] (--) MACH64(0): ATI 3D Rage II+DVD graphics controller detected.
[ 2445.635] (--) MACH64(0): Chip type 4755 "GU", version 2, foundry UMC, class 0, revision 0x02.
[ 2445.635] (--) MACH64(0): PCI bus interface detected; block I/O base is 0xD800.
[ 2445.635] (--) MACH64(0): ATI Mach64 adapter detected.
[ 2445.636] (!!) MACH64(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
[ 2445.636] (--) MACH64(0): Internal RAMDAC (subtype 1) detected.
[ 2445.636] (==) MACH64(0): RGB weight 555
[ 2445.636] (==) MACH64(0): Default visual is TrueColor
[ 2445.636] (==) MACH64(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2445.636] (II) MACH64(0): Using Mach64 accelerator CRTC.
[ 2445.636] (II) MACH64(0): Storing hardware cursor image at 0xCC0FFC00.
[ 2445.636] (II) MACH64(0): Using 8 MB linear aperture at 0xCC000000.
[ 2445.636] (!!) MACH64(0): Virtual resolutions will be limited to 1023 kB
due to linear aperture size and/or placement of hardware cursor image area.
[ 2445.636] (II) MACH64(0): Using Block 0 MMIO aperture at 0xCFFFD400.
[ 2445.636] (II) MACH64(0): Using Block 1 MMIO aperture at 0xCFFFD000.
[ 2445.637] (II) MACH64(0): MMIO write caching enabled.
[ 2445.637] (--) MACH64(0): 1024 kB of Pseudo-EDO DRAM detected (using 1023 kB).
[ 2445.637] (WW) MACH64(0): Cannot shadow an accelerated frame buffer.
[ 2445.637] (II) MACH64(0): Engine XCLK 59.876 MHz; Refresh rate code 3.
[ 2445.637] (--) MACH64(0): Internal programmable clock generator detected.
[ 2445.637] (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz.
[ 2445.637] (II) MACH64(0): LewyMonitor: Using hsync range of 30.00-83.00 kHz
[ 2445.637] (II) MACH64(0): LewyMonitor: Using vrefresh range of 56.00-75.00 Hz
[ 2445.637] (II) MACH64(0): LewyMonitor: Using maximum pixel clock of 140.00 MHz
[ 2445.637] (II) MACH64(0): Estimated virtual size for aspect ratio 1.2667 is 1280x1024
[ 2445.637] (II) MACH64(0): Maximum clock: 200.00 MHz
[ 2445.637] (II) MACH64(0): Not using default mode "640x350" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "320x175" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "640x400" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "320x200" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "720x400" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "360x200" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "640x480" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "320x240" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "800x600" (vrefresh out of range)
[ 2445.637] (II) MACH64(0): Not using default mode "400x300" (vrefresh out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1024x768i" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "512x384i" (vrefresh out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "512x384" (vrefresh out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1152x864" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1280x960" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1280x960" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "640x480" (hsync out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1280x1024" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1280x1024" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1280x1024" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "640x512" (hsync out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1600x1200" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1600x1200" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1600x1200" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1600x1200" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1600x1200" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "800x600" (hsync out of range)
[ 2445.638] (II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "896x672" (insufficient memory for mode)
[ 2445.638] (II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "896x672" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "928x696" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "928x696" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "960x720" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "960x720" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1400x1050" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1400x1050" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "960x720" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using default mode "1024x768" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using driver mode "1280x1024" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using driver mode "1280x1024" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using driver mode "1024x768" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using driver mode "1024x768" (insufficient memory for mode)
[ 2445.639] (II) MACH64(0): Not using driver mode "1152x864" (insufficient memory for mode)
[ 2445.640] (WW) MACH64(0): Shrinking virtual size estimate from 1280x1024 to 832x624
[ 2445.640] (--) MACH64(0): Virtual size is 832x624 (pitch 832)
[ 2445.640] (**) MACH64(0): *Driver mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
[ 2445.640] (II) MACH64(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 2445.640] (**) MACH64(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
[ 2445.640] (II) MACH64(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 2445.640] (**) MACH64(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 2445.640] (II) MACH64(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 2445.640] (**) MACH64(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 2445.640] (II) MACH64(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 2445.640] (**) MACH64(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 2445.640] (II) MACH64(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 2445.640] (**) MACH64(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
[ 2445.640] (II) MACH64(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 2445.640] (**) MACH64(0): *Default mode "800x600": 87.8 MHz, 81.2 kHz, 65.0 Hz (D)
[ 2445.640] (II) MACH64(0): Modeline "800x600"x65.0 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (81.2 kHz)
[ 2445.640] (**) MACH64(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 2445.640] (II) MACH64(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D)
[ 2445.641] (II) MACH64(0): Modeline "800x600"x60.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
[ 2445.641] (II) MACH64(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "700x525": 77.9 MHz, 81.5 kHz, 74.8 Hz (D)
[ 2445.641] (II) MACH64(0): Modeline "700x525"x74.8 77.90 700 732 892 956 525 526 532 545 doublescan +hsync +vsync (81.5 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D)
[ 2445.641] (II) MACH64(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D)
[ 2445.641] (II) MACH64(0): Modeline "640x512"x75.0 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (80.0 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D)
[ 2445.641] (II) MACH64(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz)
[ 2445.641] (**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 2445.641] (II) MACH64(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 2445.641] (**) MACH64(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 2445.641] (II) MACH64(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 2445.641] (II) MACH64(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 2445.641] (**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
[ 2445.641] (II) MACH64(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 2445.642] (II) MACH64(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 2445.642] (**) MACH64(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
[ 2445.642] (II) MACH64(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "512x384": 39.4 MHz, 60.0 kHz, 75.0 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
[ 2445.642] (II) MACH64(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz)
[ 2445.642] (**) MACH64(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
[ 2445.643] (II) MACH64(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz)
[ 2445.643] (**) MACH64(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
[ 2445.643] (II) MACH64(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz)
[ 2445.643] (**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
[ 2445.643] (II) MACH64(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz)
[ 2445.643] (**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
[ 2445.643] (II) MACH64(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz)
[ 2445.643] (**) MACH64(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
[ 2445.643] (II) MACH64(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz)
[ 2445.643] (**) MACH64(0): Display dimensions: (380, 300) mm
[ 2445.643] (**) MACH64(0): DPI set to (55, 52)
[ 2445.643] (II) Loading sub module "fb"
[ 2445.643] (II) LoadModule: "fb"
[ 2445.644] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2445.644] (II) Module fb: vendor="X.Org Foundation"
[ 2445.644] compiled for 1.8.1.902, module version = 1.0.0
[ 2445.644] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2445.644] (II) Loading sub module "ramdac"
[ 2445.644] (II) LoadModule: "ramdac"
[ 2445.645] (II) Module "ramdac" already built-in
[ 2445.645] (II) Loading sub module "xaa"
[ 2445.645] (II) LoadModule: "xaa"
[ 2445.645] (II) Loading /usr/lib/xorg/modules/libxaa.so
[ 2445.646] (II) Module xaa: vendor="X.Org Foundation"
[ 2445.646] compiled for 1.8.1.902, module version = 1.2.1
[ 2445.646] ABI class: X.Org Video Driver, version 7.0
[ 2445.646] (II) Loading sub module "i2c"
[ 2445.646] (II) LoadModule: "i2c"
[ 2445.646] (II) Module "i2c" already built-in
[ 2445.646] (II) MACH64(0): I2C bus "Mach64" initialized.
[ 2445.646] (--) MACH64(0): ImpacTV chip ID 0x9A detected.
[ 2445.656] (WW) MACH64(0): Direct rendering is not supported for ATI chips earlier than the ATI 3D Rage Pro.
[ 2445.657] (II) MACH64(0): Largest offscreen areas (with overlaps):
[ 2445.657] (II) MACH64(0): 832 x 5 rectangle at 0,624
[ 2445.657] (II) MACH64(0): 448 x 6 rectangle at 0,624
[ 2445.657] (II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
[ 2445.657] Screen to screen bit blits
[ 2445.657] Solid filled rectangles
[ 2445.657] 8x8 mono pattern filled rectangles
[ 2445.657] Indirect CPU to Screen color expansion
[ 2445.657] Solid Lines
[ 2445.658] Setting up tile and stipple cache:
[ 2445.658] Not enough video memory for pixmap cache
[ 2445.658] (==) MACH64(0): Backing store disabled
[ 2445.658] (==) MACH64(0): Silken mouse enabled
[ 2445.659] (**) MACH64(0): DPMS enabled
[ 2445.659] (WW) MACH64(0): Option "Enable" is not used
[ 2445.659] (II) MACH64(0): Direct rendering disabled
[ 2445.659] (==) RandR enabled
[ 2445.659] (II) Initializing built-in extension Generic Event Extension
[ 2445.659] (II) Initializing built-in extension SHAPE
[ 2445.659] (II) Initializing built-in extension MIT-SHM
[ 2445.659] (II) Initializing built-in extension XInputExtension
[ 2445.659] (II) Initializing built-in extension XTEST
[ 2445.659] (II) Initializing built-in extension BIG-REQUESTS
[ 2445.659] (II) Initializing built-in extension SYNC
[ 2445.659] (II) Initializing built-in extension XKEYBOARD
[ 2445.659] (II) Initializing built-in extension XC-MISC
[ 2445.659] (II) Initializing built-in extension SECURITY
[ 2445.659] (II) Initializing built-in extension XINERAMA
[ 2445.659] (II) Initializing built-in extension XFIXES
[ 2445.659] (II) Initializing built-in extension RENDER
[ 2445.659] (II) Initializing built-in extension RANDR
[ 2445.659] (II) Initializing built-in extension COMPOSITE
[ 2445.659] (II) Initializing built-in extension DAMAGE
[ 2445.682] (II) AIGLX: Screen 0 is not DRI2 capable
[ 2445.682] (II) AIGLX: Screen 0 is not DRI capable
[ 2445.687] (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
[ 2445.687] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 2446.130] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 2446.130] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2446.130] (II) LoadModule: "evdev"
[ 2446.131] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2446.138] (II) Module evdev: vendor="X.Org Foundation"
[ 2446.138] compiled for 1.8.0, module version = 2.4.0
[ 2446.138] Module class: X.Org XInput Driver
[ 2446.138] ABI class: X.Org XInput driver, version 9.0
[ 2446.138] (**) Power Button: always reports core events
[ 2446.138] (**) Power Button: Device: "/dev/input/event2"
[ 2446.138] (II) Power Button: Found keys
[ 2446.138] (II) Power Button: Configuring as keyboard
[ 2446.138] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2446.138] (**) Option "xkb_rules" "evdev"
[ 2446.138] (**) Option "xkb_model" "evdev"
[ 2446.139] (**) Option "xkb_layout" "us"
[ 2446.233] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 2446.233] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 2446.234] (**) Sleep Button: always reports core events
[ 2446.234] (**) Sleep Button: Device: "/dev/input/event1"
[ 2446.234] (II) Sleep Button: Found keys
[ 2446.234] (II) Sleep Button: Configuring as keyboard
[ 2446.234] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 2446.234] (**) Option "xkb_rules" "evdev"
[ 2446.234] (**) Option "xkb_model" "evdev"
[ 2446.234] (**) Option "xkb_layout" "us"
[ 2446.243] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 2446.243] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 2446.243] (**) AT Translated Set 2 keyboard: always reports core events
[ 2446.243] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 2446.244] (II) AT Translated Set 2 keyboard: Found keys
[ 2446.244] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 2446.244] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 2446.244] (**) Option "xkb_rules" "evdev"
[ 2446.244] (**) Option "xkb_model" "evdev"
[ 2446.244] (**) Option "xkb_layout" "us"
[ 2446.245] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event4)
[ 2446.245] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
[ 2446.245] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[ 2446.245] (**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event4"
[ 2446.245] (II) ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[ 2446.245] (II) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[ 2446.245] (II) ImExPS/2 Generic Explorer Mouse: Found relative axes
[ 2446.245] (II) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[ 2446.245] (II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[ 2446.245] (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[ 2446.245] (**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2446.246] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE)
[ 2446.246] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[ 2446.246] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[ 2446.246] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[ 2446.246] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[ 2446.246] (II) ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[ 2446.247] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[ 2446.247] (II) No input driver/identifier specified (ignoring)
[ 2446.247] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 2446.247] (II) No input driver/identifier specified (ignoring)
The same effect with Xinerama on. Please, help me.

hume's doona wrote:
Are you configuring for the nvidia card?
#sudo nvidia-settings
and set it to twin view in the gui?
No I think the problem is more basic than that...he's trying to use an ATi card and an Nvidia card simultaneously. Something that I don't think will work.
It also dependent on what drivers he is trying to use, as the (new) Nvidia proprietary driver only supports GeForce4 series chips and up...and the OP has an even older card than that. The legacy Nvidia-96.xx driver does support his chipset, but 96.xx does not work with Xorg1.8 last I knew. see: http://www.archlinux.org/news/502/
Twinview does not exist in the Nouveau drivers, so one has to use xrandr: http://wiki.archlinux.org/index.php/Nouveau
Last edited by Skripka (2010-08-14 14:16:25)

[Announcement: Java server-side web controls] - TICL 1.0 Final Released

Hello JSP developers,
We are pleased to announce the immediate availability of TICL (Tag Interface
Component Library) 1.0 Final Release. TICL is library of server-side user
interface components accessible through JSP tags. Like a conventional
desktop toolkit, the components maintain state and manage interaction logic
with the end-user with little or no assistance from the programmer.
Read more about TICL at http://www.kobrix.com/ticl/ticlmain.jsp.
If you are already a TICL user, check out the release notes at
http://www.kobrix.com/ticl/releasenotes.jsp for the latest changes.
More info
One of the major goals of TICL is to bring RAD-like development to the WEB
platform. Programmers can concentrate on logical functionality and build JSP
pages by placing TICL components through tags and responding to user events.
Every component is self-contained and manages interaction with the end-user.
Visual appearance of components is abstracted into a high-level styles
framework. In fact, TICL is probably the only server-side Java toolkit that
rivals Microsoft ASP.NET's web controls.
The library is tailored more towards WEB application development, rather
than content only oriented sites. It is designed to quickly build clean,
robust, well-structured and therefore highly maintainable code. It
integrates seemlessly into existing JSP applications and it will work on any
standard compliant JSP 1.1 container (e.g. Tomcat 3.2.1 and above, Resin
etc.) and with fairly recent versions of the popular browsers.
Core features are:
- A powerful and extensible server-side event model. Component-end user
interaction is encapsulated into a well defined set of server-side events.
You can of course define event listeners, develop custom events, event
filters etc.
- Predefined components like panels, tabbed panels, tree views, DHTML menus,
table views. Most can perform their interaction with the end-user at the
browser through DHTML or by making a trip back to server on every user
action (like expanding a tree node or minimizing a panel) - that is
components are either "client" or "server" managed.
- Smart browser handling. A complete framework for dealing with browser
(user agent) capabilities, including detection of dynamic properties like
connection speed, screen resolution, available plugins etc.; supporting JSP
tags; on the fly selection of component rendering based on the current user
agent.
- A high-level styles framework for complete customization of the look&feel
of components. Styles can be organized into themes. An inheritence mechanism
of style objects provides for a powerful high-level structuring. The
framework allows for a clean separation between look&feel and functional
behaviour of GUI elements. No more copy&paste, no more code cluttering with
tedious, browser-specific HTML details - consistency of look&feel can be
easily achieved by maintaining a single TICL style sheet, a simple XML file,
that is applied to all pages in your WEB application.
- Full encapsulation of HTML forms, including a file upload component,
augmented with things such as server-side command handlers, labels and DHTML
tooltips. Form fields are typed, true server-side components. Not limited to
the standard HTML form fields, they operate on a high level and custom ones
can be developed and plugged into the framework.
- A very powerful and easy to use declarative form validation mechanism
(both client and server-side). You define validation rules and handlers for
invalid forms in a clean, declarative way. The same rules you define can be
applied at the client (through automatic generation of the necessary
JavaScript) or at the server. Special purpose syntax allows you to easily
handle interdependencies between field values.
- A Data Objects framework integrated with TICL forms. Allows you to
manipulate complex aggregate structures and associate them with forms for
automatic mapping to/from form field values and data object fields (e.g.
Java beans). A type mapping framework allows you to map any form field type
to any Java type.
- An integration module for the popular Struts framework is provided also.
For example, it is possible to use the powerful TICL form tags with Struts'
ActionForms.
TICL is FREE for non-commercial and non-govermental use, and for an
unlimited evaluation period. It comes with an extensive, over 200 pages,
Reference Manual. To download it, please goto http://www.kobrix.com and
select Downloads from the TICL pulldown menu. If you are not already a TICL
user, you may need to register first.
We sincerely hope you will enjoy TICL and are looking forward to your
feedback!
Best Regards,
Borislav Iordanov
[email protected]
Kobrix Software Inc.
http://www.kobrix.com

This looks quite nice. I'm going to evaluate it now, but I wish it was open-source....
Judging from the release notes, it's been around for a while. Has anybody had any experience with this product? Is it reliable? Does it scale well?

Final Release codes shows only 5 levels

Similar Messages

Maybe you are looking for