Hosted Display Mode issues

I have a .NET portlet with a dropdown list of values. When a user clicks on a value it does a Response.Redirect to another aspx page and show info about that value. The new page is set to be in hosted display mode. i.e. a page showing a big list of values with the portal header and footer.
My portlet keeps on showing these values in the same portlet as the list, instead of in a new hosted page. We are using .NET web controls 3.0 and ALUI G6.1

How are you setting the property - programatically or via the webservice properties?
We did an upgrade and found that if you set this property twice programatically, it fails (J2EE - it was set in the JSP and the action). It used to work with version 5.0.4J but fails with 6.1. The fix is to leave the code as it is and override this property by checking the hosted display mode check box for the web service.
-Dev

Similar Messages

Session Crossing in Hosted Display Mode

Hi!
I'm taking a 3rd party program written in ASP and serving it inside the portal using the gateway (via Hosted Display Mode.) Users that are using the application are using the portal in a guest context.
While testing the integration, we've found that sessions seemed to be getting crossed. A user trying to make a payment suddenly had more items in their cart. The items were added to the cart by a user on a completely seperate terminal. So it's pretty obvious that sessions are getting mixed.
Anybody ever see this?

Hi Kevin
I have experienced a similar issue and it was related to gateway cacheing.
I'm not sure whether it applies to you but in our example we had a portlet which was the entry point into hosted pages. Because the portlet had cacheing configured, we found that cacheing was also applied to the click-through hosted pages. Removing cacheing from the portlet resolved the issue.

Hosted display mode conflict with Siteminder

I'm trying to use hosted display mode on a URL that is protected by Siteminder but it is not working. Even though the Portal Groups and the LDAP Groups that Siteminder uses are synchronized. Is there any way to use the Portal Banner & Footer for a series of static html web pages without using the gateway?
Regards,
Mike BergstromWeb Manager Pratt & Whitney Online Services

Hi there!
Thanks for that reply. I guess I'm somewhat confused about how the whole "hosted display" thing works.
I'm assuming that to display something, I must first create a remote server portlet that displays the initial page of the application. In this case, the initial page is the frameset. When doing what I just described, the page displays with an empty portlet. So obviously I'm doing something wrong.
Any thoughts, hints, etc would be greatly appreciated. Thanks!

Performance Issues with Debugging even in Display Mode

Hi not certain if this would sit in Security, ABAP or Basis, but lets start here as it is security related.
S_DEVELOP with any activity on DEBUG on a production system is a concern, but what are the performance related issues when a super user has to go into debug in display only on a production system because of a really complex issue?
I've heard in the past of a scenario where system performance was impacted, and we have notes around the allocation of S_DEVELOP display DEBUG access to this point. (I've summarised these below)
The risk with debug is associated with the length of time that the actual debugging process is being performed.
u2022 Work processes are dedicated solely to the users for the duration of the debug. If these are being performed for a long time, these can cause issues with not enough work processes being available.
u2022 It can cause DB2 locks. If the debug session last awhile, DB2 locks are not released. This impacts the availability of tablespaces, thus, affecting various transactions running across the system.
Even with these concerns, security will often get asked for debug display access.
As security is about risk identification, assessment and then controlled access what do other organisations do?
Options (not exhaustive) are "No Debug ever" or "Debug display only via a fire fight or super user on a time limited basis".
We are currently in the "debug display only via fire fight" camp, but would like to canvas opinion on this.
As one of the concepts of security is Availability of data (and to an extent ensuring the systems are up and running) do the performance risks push the security function to the "No Debug Ever" stance.

If you need to debug in production, then 9 times out of 10 you need to do root-cause analysis: The developer is the problem.
Writing sloppy code and not testing properly should not be an excuse for debugging in production.
But of course, there are exceptions even when you do try to keep them to a minimum.
To add to Jurjen's comments, also note that the debugger only has a limited capability of doing a rollback. So you can quite easily and unintentionally create inconsistencies in the system - also in display mode - which is an integrity problem, and typically more critical than availability problems or even potential confidentiality concerns.
Cheers,
Julius
Edited by: Julius Bussche on May 15, 2009 10:50 AM

LMS 4.0.1 End Host display issue

Using LMS 4.0.1.
When looking at the Device Centre - Troubleshooting view for a device it will display the number of End Hosts in the Configuration Status>Configuration Details section. If I click on the number of devices a pop-up will appear saying "No end hosts found", however if I go to Reports>Inventory>User Tracking and run the report it displays the end hosts correctly
I would appreciate assistance on what could be causing this issue. It was happening with Lms 4.0 but upgrade to 4.0.1 did not change it.

michel.hegeraat wrote:Try to grab the url it gives. Something like:http://didata:1741/cmapps/utEndHostReport.do?action=Submit&crossLaunch=admindashboard&runTypeOption=Immediate&devName=lab-SW23&devIP=10.170.46.250Check if these to guys are correct and resolvabledevNamedevIPCheers,Michel
Below is the url from a sample device (this problem occurs with all I have checked so far) that appears when I click the numeric End Hosts quantity from the Device Center - Troubleshooting page
http://lmsnetmgr:1741/cmapps/utEndHostReport.do?action=Submit&crossLaunch=admindashboard&runTypeOption=Immediate&devName=Gosford NOC Sw 2&devIP=10.76.152.56
When I use the same Device name or Device IP when running a end host query from Reports>User Tracking>Quick reports I get the correct end hosts displayed. The quantity displayed corresponds with the quantity shown on the Device center - troubleshooting page
So - the problem is not related to using an incorrect device IP or Device Name

Apple Mini DVI to DVI Adapter to connect Win7 tower to iMac / Target Display Mode

I currently run Windows on bootcamp on the iMac (Mid-2011), although the tasks I perform (3D modelling, rendering and such) cause the Mac to get very hot, and as a result hae a slight burn mark on the LED LCD screen.
I am buying a Windows machine, and am to uninstall bootcamp and use the Mac purely for OSX, but use the iMac screen as a monitor for the tower using Target Display Mode. My issue is - the Windows 7 tower only has DVI output. And as I understand, the Mid-2011 iMac only supports Target Display Mode via a thunderbolt cable.
My question is - Will the Apple Mini DVI to DVI adapter allow me to connect the DVI-only tower to the iMac? Thanks in advance x

Oh, I should mention also that the iMac is the 27" model. Mid-2011 3.4Ghz Intel Core i7 with 4GB RAM and 1TB Harddrive. And ATI HD5450 1GB Graphics.

Output types are not getting displayed in Outbound Delivery in Display mode

Hello,
The actual requirement is that output types should get attched to the outbound delivery when we do GI(Good Issue) on the outbound delivery.
So, I have created an outbound delivery and did GI on it through IDoc. But, I can not see output types on the delivery (To see output types, go to Extra -> Output -> Header in VL03N) in the display mode. However, I can see in change mode (VL02N).
Could you please suggest the solution for this?

Hi sreeram,
go to crm -> transactions -> basic settings -> define transaction types
copy default email cx03 and create new zemail.
assign that zemail to bus2000126 business activity.select the business activity and click on customizing header.assign the category email. click on channel. maintain the channels 1)GUI crm webclient UI, 2)ICW Interaction center webclient.
save the changes.
go to crm -> transactions -> basic settings -> settings for activities -> maintain categories, goals, priorities -> click on assign categories to transaction types.
assign the category email(which you have assigned above) to the transaction type zemail.
even check maintain categories as well
click on maintain categories -> check 401 email assigned to class G email.
Regards
Krishna

IMac 27" Target DIsplay Mode + Answer to Windows 7 Boot Camp Install

First, I'd like to address the handful of complaints I've come across about installing Windows 7 via Boot Camp on the new 27"iMac.
The issue of the screen going blank when almost done has an easy albeit annoying answer. Simply connect the iMac to an external display, I used a small vga lcd with the Mini DisplayPort to VGA adapter. When the iMac's screen goes black the external lcd will continue, and when Windows 7 starts up it will download the updated ATI drivers. From there alls well.
Second, my problem.
Target Display Mode is a great feature. It worked great when I first used it, and it works great now except for the fact that the Command+F2 button combination stopped working. I have to manually unplug my MacBook Pro in order to get my iMac's original screen up. At first Command+F2 would allow me to switch back and forth, and now it does nothing.
Any suggestions?

Well, the usual first things to try for a display-related issue are
Reset PRAM
http://support.apple.com/kb/HT1379
and of that does not help, reset SMC
http://support.apple.com/kb/HT1543
which is basically unplugging the iMac from power and reconnecting it following the precise procedure.
Note: After resetting PRAM, you should go to System Preferences +Startup Disk+ pane to make sure your internal drive is selected (highlighted) as the startup disk.

MacBook Air to iMac Target Display Mode not working

I would like to connect my MacBook Air (13") with my iMac (27") to use the latter as an external display with Target Display Mode.
I followed instructions from a number of posts (http://support.apple.com/kb/PH14264), and connected the two with thunderbolt cable and hit Command-F2 -- the iMac goes black and MacBook stays the same. One post suggested dragging windows over to the iMac as an extended display, and I was able to drag Safari totally off-screen, presumably onto the other display, but the iMac still appeared black
Other issue is that hitting Command-F2 again doesn't do anything. I could only get the iMac out of TDM when I unplugged the thunderbolt cord.
I have a brand new Macbook Air and iMac along with new thunderbolt cable (all purchased at Apple Store in 2014). Would appreciate any help, thanks!

Additional twist to this...
Tried to troubleshoot and reset the System Management Controller (SMC) per http://support.apple.com/kb/HT3964
When I hit Command-F2, one window from my MacBook will display on the iMac (it was Safari a few times, Outlook once), but neither keyboard/mouse can DO anything in that screen. That window also disappears from the MacBook. And I can only return after unplugging thunderbolt (not command-F2).
Help please

Use iMac in Target Display Mode with a Power Mac G4

I would like to connect my Power Mac G4 MDD (Model = http://support.apple.com/kb/SP63) to the new iMac (27 inch, Mid 2010) in Target Display Mode. That is, I want the new iMac to be the display for my Power Mac G4. Has anybody done this (including using the iMac 27 inch, Late 2009, which can also do this)? In a general sort of way, this sort of thing is described on this support page: http://support.apple.com/kb/ht3924.
The problem: The iMac requires a Mini Displayport connection. The PowerMac has ADC and DVI-I display connections and also came with an adapter for converting DVI-I to VGA. How can I convert/adapt to get the appropriate Mini Displayport connection?
Gefen makes a converter (http://www.gefen.com/kvm/dproduct.jsp?prod_id=8913) that will convert DVI-D to Mini Displayport, but the description explicitly says that it will work with DVI-D only while my PowerMac has DVI-I. I know that these are two different, incompatible connections.
Is there another converter that works with DVI-I? Or is there a way to adapt from DVI-I to DVI-D? Or how about a VGA or ADC to Mini Displayport converter?
Thanks.

japamac-
Thanks so much for your reply. You're right on target for what I'm looking for and that article is VERY helpful! If you don't mind, I do have a couple more questions/clarifications.
1) First, I think that I didn't read the Wikipedia reference concerning DVI (http://en.wikipedia.org/wiki/DigitalVisualInterface) closely enough. It includes the following paragraph. If I understand it and what you said, it shouldn't be a problem to connect the male DVI-D of the converter into the female DVI-I socket of my Power Mac. Right?
+The long flat pin on a DVI-I connector is wider than the same pin on a DVI-D connector, so it is not possible to connect a male DVI-I to a female DVI-D by removing the 4 analog pins. It is possible, however, to connect a male DVI-D cable to a female DVI-I connector. Many flat panel LCD monitors have only the DVI-D connection so that a DVI-D male to DVI-D male cable will suffice when connecting the monitor to a computer's DVI-I female connector.+
2) I'm not clear on the difference between the Altona AT-DP200 and the Gefen converter. The Gefen converter is somewhat less expensive, so I'm trying to figure out what the downside is. The article you mentioned says that the ATP-DP200 "doesn't scale images", but that seems to only be an issue if I'm trying to connect other devices (PS3, Blu-ray), not if I just want to connect my Power Mac.
The description of the Gefen converter includes the following drawbacks:
+The only major drawback to Gefen's solution is no support for VGA devices or HDCP. A minor gripe would be the fact that the Gefen device only accepts one input resolution and only outputs one resolution (1920 x 1200 at 60 Hz). These limited options aside, the Gefen device looks like it could do the basic trick of transforming a DVI signal to Mini DisplayPort so that you could use your 27" iMac for a few more purposes, provided that the input signal carries the required 1920 x 1200 resolution.+
I'm not clear on what the practical impact of those limitations would be. I don't think the the lack of support for VGA devices or HDCP is an issue for my application. But I'm wondering about the statement that it only accepts one input resolution and outputs only one resolution (1920 x 1200) and the need for the input signal to carry 1920 x 1200. I take it, first of all, that the Power Mac can supply that input resolution. And, what is the impact of the device only having that resolution output to the iMac screen? That is, how would that look on the screen, ugly or okay? Finally, would the Altona device provide a better looking output on the iMac screen because it can apparently handle different resolutions? The manufacturer's description says, "Resolutions: all resolutions up to 1920x1200 (It is Important to select one of the resolutions that display
is capable of displaying, refer to your display’s users manual)."
Thanks again.

Depriciation key and useful life periods in asset master should in display mode only

Hi all
At the time of creation asset master AS01 we are given the Asset class, company code and similar of asset (1) then we click enter button we will get Create asset: master data screen here in general tab we enter the description and in time dependent tab we enter cost center manually
But
When we click on Depreciation tab here the Depreciation key and use life fields are automatically come with Dep.key(ABC) and use life(15) (Because we maintained in OAYZ)
Here user have a chance to change the Dep.key(ABC) and use life(15).so my requirement is these two fields are display with only display mode .
User don’t have chance to modify this.

Hi Anil,
The screen layout for Asset and its depreciation tab are different. You have to make these fields as Display only in the screen layout. This can be done using T-Code AO21. Below are the screenshots for the path and screen layout for your reference. This should solve your issue
Regards
Pankaj Pareek

Conditions not appearing in the display mode of Purchase order

Hi,
We are facing an issue where in the display mode of Purchase order,if I click on the conditions tab in the item details, Iam getting a blank screen. But if I trigger the pricing procedure in the change mode for eg. by changing the quantity or price, the conditions are appearing.
I want to know why the conditions are not being shown in the display mode. All the PO's are using the standard pricing proceduresRM0000.
Also when I trigger the pricing in the change mode for some POs the condition types like PB00, NVAS etc are appearing twice, in some POs the condition types are appearing thrice and in some all the condition types are appearing four times.
I have checked out some OSS notes like 798449, 456690 and 772035 but could not find the solution.
Any pointers to this will be eagerly awaited and highly appreciated.

Hi Ramachandra,
The problem on not being able to see details in condition tab is due to lack of authorizations
prasanna

15 inch early 2011 Macbook Pro to Mid 2010 27 inch Imac Target Display Mode

Hi Guys
I have a early 2011 15" Macbook Pro with thunderpolt port aswell
as a Mid 2010 27" iMac with MiniDisplay port.
I am trying to use the iMac as a second screen for my Macbook.
Both has Mountain Lion on them.
I have both Thunderbolt to Thunderbolt aswell as miniDisplay to MiniDisplay
cables.
I can't get target display mode to work.
The thunderbolt cable doesn't work at all.
The MiniDisplay does seeem to work to an extend but not completeley.
When i plug in the MiniDisplayPort cable to both machines then
the Macbook pro screen becomes blue which means secondary monitor detected.
iMac screen becomes blank. Sometimes i have enough time to see in system preferences that
the Macbook pro actually has a secondary monitor.
But just as it turned blue on the Macbook pro and black on the iMac. It turns blue again
and the iMac returns to it's Desktop.
The exact same happens when i Press Command + F2 on iMac keyboard.
Any help or ideas?

I have a 13"macbook air and a Dec. 2012 iMac 27". Out of the blue it stopped working in Target Display Mode. Switching cables doesn't help, and the iMac and MBair are connect to power. I can see the iMac screen in Share Screen mode on the MB air.
This seems to be an issue, I have encountered eg. in MacRumours:
Jan 11, 2013, 10:17 AM
#5
martinm0
macrumors 6502
Join Date: Feb 2010
I have the same issue with my 2012 27" iMac (3.4, 680MX). When I initiate Target Display mode the iMac goes black and never comes back up. On the laptop I can see the display in Display Preferences, but its as if the backlight doesn't come on in TD mode. (I even did screen sharing into the laptop and can see both displays there.
Anyway, called Apple and they determined its an issue and I have to send in for a replacement.
Anyone else with a 2012 iMac (21.5 or 27), can you please test out Target Display mode and let us know if things are working or not?

Limited to one display mode with new nvidia drivers

I have a problem with nvidia drivers after 8178
I can get any display mode to work as long as i specify only one mode.
If i enter more modes in my xorg.conf, it will ignore all those modes and revert back to nvidia-auto-select (wich is 1024x768 in my case)
Anyway, i'm not able to change resolutions using xrandr for example. I need this for some applications that require to run in a different display mode ( old windows games i run using wine for example)
When i run X -logverbose 5 it becomes clear that all my monitor's supported modes are in the display pool.
I have also put in gtp generated modelines for all the modes i might need.
I really need a solution to this as i will probably no longer be able to use 8178 when xorg7.1 hits current.
This is what i have in my xorg.conf:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "AlwaysCore"
InputDevice "Mouse1" "CorePointer"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/cyrillic/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
SubSection "extmod"
# Option "omit xfree86-dga"
EndSubSection
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
Load "bitmap"
Load "ddc"
Load "int10"
Load "record"
# Load "speedo"
Load "vbe"
# Load "xf8_32bpp.so"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "evdev"
# Option "Protocol" "Explorerps/2"
Option "Device" "/dev/input/mx1000"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "11 12"
Option "Dev Name" "Logitech USB Receiver" # cat /proc/bus/input/devices
Option "Dev Phys" "usb-*/input0" # cat /proc/bus/input/devices
Option "Buttons" "12"
Option "Resolution" "800"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "microsoftinet"
Option "XkbLayout" "us"
Option "XkbVariant" ",qwerty"
EndSection
Section "Monitor"
Identifier "Monitor0"
# VendorName "Iiyama"
# ModelName "A901HT"
ModelName "IVM:0119"
HorizSync 27.0 - 115.0
VertRefresh 50.0 - 160.0
# Option "DPMS"
Modeline "1600x1200_100.00" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
Modeline "1600x1200_85.00" 234.76 1600 1720 1896 2192 1200 1201 1204 1260 -HSync +Vsync
Modeline "1600x1200_75.00" 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -HSync +Vsync
Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync
Modeline "1280x1024_100.00" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
Modeline "1280x1024_85.00" 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -HSync +Vsync
Modeline "1280x1024_75.00" 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync
Modeline "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
Modeline "1152x864_100.00" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
Modeline "1152x864_85.00" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
Modeline "1152x864_75.00" 104.99 1152 1224 1352 1552 864 865 868 902 -HSync +Vsync
Modeline "1152x864_60.00" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
Modeline "1024x768_100.00" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
Modeline "1024x768_85.00" 94.39 1024 1088 1200 1376 768 769 772 807 -HSync +Vsync
Modeline "1024x768_75.00" 81.80 1024 1080 1192 1360 768 769 772 802 -HSync +Vsync
Modeline "1024x768_60.00" 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync
Modeline "800x600_85.00" 56.55 800 840 928 1056 600 601 604 630 -HSync +Vsync
Modeline "800x600_75.00" 48.91 800 840 920 1040 600 601 604 627 -HSync +Vsync
Modeline "800x600_60.00" 38.22 800 832 912 1024 600 601 604 622 -HSync +Vsync
Modeline "640x480_85.00" 35.71 640 672 736 832 480 481 484 505 -HSync +Vsync
Modeline "640x480_75.00" 30.72 640 664 728 816 480 481 484 502 -HSync +Vsync
Modeline "640x480_60.00" 23.86 640 656 720 800 480 481 484 497 -HSync +Vsync
Modeline "320x240_60.00" 5.26 320 304 336 352 240 241 244 249 -HSync +Vsync
Modeline "320x200_60.00" 4.19 320 304 328 336 200 201 204 208 -HSync +Vsync
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NvAGP" "3"
Option "RenderAccel" "TRUE"
Option "NoLogo" "on"
Option "RandRRotation" "TRUE"
# Option "CursorShadow" "FALSE"
# Option "ConnectedMonitor" "CRT"
# Option "UseEDIDFreqs" "FALSE"
# Option "UseEDIDDpi" "FALSE"
# Option "ModeValidation" "NoEdidModes"
# Option "ModeValidation" "AllowNon60HzDFPModes"
# Option "UseEDID" "FALSE"
Option "IgnoreDisplayDevices" "CRT"
Option "DPI" "96 x 96"
Option "Coolbits" "1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 32
Modes "1280x1024"
# Visual StaticGray
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024_85"
# Modes "1280x1024_85 1152x864 1024x768 800x600 640x480 320x240 320x200"
# Visual StaticGray
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024_85"
# Visual StaticGray
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600_75"
# Visual StaticGray
EndSubSection
EndSection
#Section "DRI"
# Mode "0666"
#EndSection
All the EDID specific options i have commented out appeared to be useless.
The following Xorg.0.log was generated using only one mode, resulting in X running in 1280x1024@85hz (logverbose level 5)
[code]
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-ARCH i686
Current Operating System: Linux Orthanc 2.6.17.11 #1 PREEMPT Fri Aug 25 08:31:05 CEST 2006 i686
Build Date: 21 June 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 29 13:57:46 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Mouse1"
(WW) The directory "/usr/share/fonts/local/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/CID/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/PEX" does not exist.
Entry deleted from font path.
(**) FontPath set to "/usr/share/fonts/misc/:unscaled,/usr/share/fonts/100dpi/:unscaled,/usr/share/fonts/75dpi/:unscaled,/usr/share/fonts/misc/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,/usr/share/fonts/cyrillic/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1"
(**) RgbPath set to "/usr/share/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.8
X.Org XInput driver : 0.5
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(--) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2560 card 1043,80b2 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,2561 card 0000,0000 rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,24c2 card 1043,8089 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24c4 card 1043,8089 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24c7 card 1043,8089 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24cd card 1043,8089 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 82 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24c0 card 0000,0000 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24cb card 1043,8089 rev 02 class 01,01,8a hdr 00
(II) PCI: 01:00:0: chip 10de,0312 card 1043,80e7 rev a1 class 03,00,00 hdr 00
(II) PCI: 02:05:0: chip 14e4,4401 card 1043,80a8 rev 01 class 02,00,00 hdr 00
(II) PCI: 02:0c:0: chip 105a,4d69 card 105a,4d68 rev 02 class 01,80,85 hdr 00
(II) PCI: 02:0d:0: chip 1102,0004 card 1102,0051 rev 03 class 04,01,00 hdr 80
(II) PCI: 02:0d:1: chip 1102,7003 card 1102,0040 rev 03 class 09,80,00 hdr 80
(II) PCI: 02:0d:2: chip 1102,4001 card 1102,0010 rev 00 class 0c,00,10 hdr 80
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xde000000 - 0xdfdfffff (0x1e00000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xdff00000 - 0xefffffff (0x10100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[1] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[2] -1 0 0x00009800 - 0x000098ff (0x100) IX[B]
[3] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]
[4] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]
[5] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]
[6] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]
[7] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]
[8] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[9] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[10] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]
[11] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xdb800000 - 0xdd7fffff (0x2000000) MX[B]
(II) Bus 2 prefetchable memory range:
[0] -1 0 0xdfe00000 - 0xdfefffff (0x100000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV31 [GeForce FX 5600] rev 161, Mem @ 0xde000000/24, 0xe0000000/28, BIOS @ 0xdffe0000/17
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf0000000 from 0xf7ffffff to 0xefffffff
(II) Active PCI resource ranges:
[0] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[1] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[2] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[3] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[4] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[5] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[6] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[7] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[8] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[10] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[11] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[12] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[13] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[14] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[15] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[16] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[17] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[18] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[19] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[20] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[21] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[1] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[2] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[3] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[4] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[5] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[6] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[7] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[8] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[10] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[11] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[12] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[13] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[14] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[15] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[16] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[17] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[18] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[19] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[20] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[21] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[6] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[7] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[8] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[9] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[10] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[11] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[12] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[13] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[15] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[18] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[19] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[20] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[21] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[22] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[23] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[24] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[25] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[26] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[27] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Reloading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts/libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.0.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8774
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "bitmap"
(II) Reloading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Loading font Bitmap
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules/libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension RECORD
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8774
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 0.0.0, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.4
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) NVIDIA dlloader X Driver 1.0-8774 Tue Aug 1 20:55:35 PDT 2006
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) Found 1 NVIDIA X Screens
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.8
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[6] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[7] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[8] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[9] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[10] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[11] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[12] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[13] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[15] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[18] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[19] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[20] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[21] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[22] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[23] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[24] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[25] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[26] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[27] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) resource ranges after probing:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[6] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[7] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[8] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[9] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[10] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[11] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[12] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[13] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[15] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[16] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[17] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[18] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[21] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[22] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[23] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[24] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[25] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[26] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[27] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[28] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[29] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[30] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[31] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[32] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[33] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "on"
(**) NVIDIA(0): Option "NvAGP" "3"
(**) NVIDIA(0): Option "RenderAccel" "TRUE"
(**) NVIDIA(0): Option "RandRRotation" "TRUE"
(**) NVIDIA(0): Option "Coolbits" "1"
(**) NVIDIA(0): Option "DPI" "96 x 96"
(==) NVIDIA(0): Using HW cursor
(**) NVIDIA(0): Enabling RENDER acceleration
(==) NVIDIA(0): Video key set to default value of 0x101fe
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5600 at PCI:1:0:0
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(II) NVIDIA(0): GPU Architecture: 0x30
(II) NVIDIA(0): GPU Implementation: 0x31
(II) NVIDIA(0): GPU Revision: 0xa1
(--) NVIDIA(0): VideoBIOS: 04.31.20.28.00
(--) NVIDIA(0): Found 2 CRTCs on board
(II) NVIDIA(0): Supported display device(s): CRT-0, CRT-1, DFP-0, DFP-1, TV-0
(II) NVIDIA(0): Bus detected as AGP
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(II) NVIDIA(0):
(II) NVIDIA(0): Mode timing constraints for : GeForce FX 5600
(II) NVIDIA(0): Maximum mode timing values :
(II) NVIDIA(0): Horizontal Visible Width : 8192
(II) NVIDIA(0): Horizontal Blank Start : 8192
(II) NVIDIA(0): Horizontal Blank Width : 4096
(II) NVIDIA(0): Horizontal Sync Start : 8184
(II) NVIDIA(0): Horizontal Sync Width : 504
(II) NVIDIA(0): Horizontal Total Width : 8224
(II) NVIDIA(0): Vertical Visible Height : 8192
(II) NVIDIA(0): Vertical Blank Start : 8192
(II) NVIDIA(0): Vertical Blank Width : 256
(II) NVIDIA(0): Veritcal Sync Start : 8191
(II) NVIDIA(0): Vertical Sync Width : 15
(II) NVIDIA(0): Vertical Total Height : 8193
(II) NVIDIA(0):
(II) NVIDIA(0): Minimum mode timing values :
(II) NVIDIA(0): Horizontal Total Width : 40
(II) NVIDIA(0): Vertical Total Height : 2
(II) NVIDIA(0):
(II) NVIDIA(0): Mode timing alignment :
(II) NVIDIA(0): Horizontal Visible Width : multiples of 8
(II) NVIDIA(0): Horizontal Blank Start : multiples of 8
(II) NVIDIA(0): Horizontal Blank Width : multiples of 8
(II) NVIDIA(0): Horizontal Sync Start : multiples of 8
(II) NVIDIA(0): Horizontal Sync Width : multiples of 8
(II) NVIDIA(0): Horizontal Total Width : multiples of 8
(II) NVIDIA(0):
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5600 at PCI:1:0:0:
(--) NVIDIA(0): Iiyama (CRT-0)
(--) NVIDIA(0): Iiyama (CRT-0): 350.0 MHz maximum pixel clock
(--) NVIDIA(0):
(--) NVIDIA(0): --- EDID for Iiyama (CRT-0) ---
(--) NVIDIA(0): EDID Version : 1.1
(--) NVIDIA(0): Manufacturer : IVM
(--) NVIDIA(0): Monitor Name : Iiyama
(--) NVIDIA(0): Product ID : 6401
(--) NVIDIA(0): 32-bit Serial Number : 0
(--) NVIDIA(0): Serial Number String :
(--) NVIDIA(0): Manufacture Date : 2000, week 30
(--) NVIDIA(0): DPMS Capabilities : Standby Suspend Active Off
(--) NVIDIA(0): Prefer first detailed timing : No
(--) NVIDIA(0): Supports GTF : No
(--) NVIDIA(0): Maximum Image Size : 360mm x 270mm
(--) NVIDIA(0): Valid HSync Range : 31 kHz - 106 kHz
(--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 85 Hz
(--) NVIDIA(0): EDID maximum pixel clock : 229.5 MHz
(--) NVIDIA(0):
(--) NVIDIA(0): Established Timings:
(--) NVIDIA(0): 640 x 480 @ 60 Hz
(--) NVIDIA(0): 640 x 480 @ 72 Hz
(--) NVIDIA(0): 640 x 480 @ 75 Hz
(--) NVIDIA(0): 800 x 600 @ 56 Hz
(--) NVIDIA(0): 800 x 600 @ 60 Hz
(--) NVIDIA(0): 800 x 600 @ 72 Hz
(--) NVIDIA(0): 800 x 600 @ 75 Hz
(--) NVIDIA(0): 1024 x 768 @ 60 Hz
(--) NVIDIA(0): 1024 x 768 @ 70 Hz
(--) NVIDIA(0): 1024 x 768 @ 75 Hz
(--) NVIDIA(0): 1280 x 1024 @ 75 Hz
(--) NVIDIA(0):
(--) NVIDIA(0): Standard Timings:
(--) NVIDIA(0): 1600 x 1200 @ 60 Hz
(--) NVIDIA(0): 1600 x 1200 @ 70 Hz
(--) NVIDIA(0): 1600 x 1200 @ 75 Hz
(--) NVIDIA(0): 1600 x 1200 @ 85 Hz
(--) NVIDIA(0):
(--) NVIDIA(0): --- End of EDID for Iiyama (CRT-0) ---
(--) NVIDIA(0):
(II) NVIDIA(0): Frequency information for Iiyama (CRT-0):
(II) NVIDIA(0): HorizSync : 31.000-106.000 kHz
(II) NVIDIA(0): VertRefresh : 56.000-85.000 Hz
(II) NVIDIA(0): (HorizSync from EDID)
(II) NVIDIA(0): (VertRefresh from EDID)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Modes in ModePool for Iiyama (CRT-0) ---
(II) NVIDIA(0): "nvidia-auto-select" : 1024 x 768 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1920x1200" : 1920 x 1200 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1920x1200_70" : 1920 x 1200 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1920x1200_60" : 1920 x 1200 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1856x1392" : 1856 x 1392 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1856x1392_60" : 1856 x 1392 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1792x1344" : 1792 x 1344 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1792x1344_60" : 1792 x 1344 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1680x1050" : 1680 x 1050 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_85" : 1680 x 1050 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_75" : 1680 x 1050 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_70" : 1680 x 1050 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_60" : 1680 x 1050 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1600x1200" : 1600 x 1200 @ 85.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_85" : 1600 x 1200 @ 85.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_75" : 1600 x 1200 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_70" : 1600 x 1200 @ 70.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_65" : 1600 x 1200 @ 65.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1600x1200_60" : 1600 x 1200 @ 60.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1024" : 1600 x 1024 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1600x1024_60" : 1600 x 1024 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050" : 1400 x 1050 @ 85.3 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_85" : 1400 x 1050 @ 85.3 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_85_0" : 1400 x 1050 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_75" : 1400 x 1050 @ 74.8 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_70" : 1400 x 1050 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_70_0" : 1400 x 1050 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_60" : 1400 x 1050 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x1024" : 1280 x 1024 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x1024_85.00" : 1280 x 1024 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_75.00" : 1280 x 1024 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_60.00" : 1280 x 1024 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_85_0" : 1280 x 1024 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x1024_85" : 1280 x 1024 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_75" : 1280 x 1024 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1280x1024_75_0" : 1280 x 1024 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_60_0" : 1280 x 1024 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x1024_60" : 1280 x 1024 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x960" : 1280 x 960 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x960_85" : 1280 x 960 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x960_60" : 1280 x 960 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x800" : 1280 x 800 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800_85" : 1280 x 800 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800_75" : 1280 x 800 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800_70" : 1280 x 800 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800d60" : 1280 x 800 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "1280x800_60" : 1280 x 800 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768" : 1280 x 768 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_85" : 1280 x 768 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_75" : 1280 x 768 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_70" : 1280 x 768 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_60" : 1280 x 768 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720" : 1280 x 720 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_85" : 1280 x 720 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_75" : 1280 x 720 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_70" : 1280 x 720 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_60" : 1280 x 720 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864" : 1152 x 864 @ 85.1 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_85.00" : 1152 x 864 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_75.00" : 1152 x 864 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_60.00" : 1152 x 864 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_85_0" : 1152 x 864 @ 85.1 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_85" : 1152 x 864 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_85_1" : 1152 x 864 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_75_0" : 1152 x 864 @ 75.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1152x864_75" : 1152 x 864 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_75_1" : 1152 x 864 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_70" : 1152 x 864 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_60" : 1152 x 864 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_60_0" : 1152 x 864 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1024x768_85.00" : 1024 x 768 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1024x768_75.00" : 1024 x 768 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_60.00" : 1024 x 768 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_85" : 1024 x 768 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_85_0" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1024x768_75_1" : 1024 x 768 @ 75.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1024x768_75" : 1024 x 768 @ 75.0 Hz (from: EDID)
(II) NVIDIA(0): "1024x768_75_0" : 1024 x 768 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_70" : 1024 x 768 @ 70.1 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1024x768d60" : 1024 x 768 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "1024x768_60" : 1024 x 768 @ 60.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1024x768_60_0" : 1024 x 768 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "960x720" : 960 x 720 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x720d60" : 960 x 720 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600" : 960 x 600 @ 75.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d75" : 960 x 600 @ 75.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d73" : 960 x 600 @ 72.8 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d70" : 960 x 600 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d60" : 960 x 600 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "928x696" : 928 x 696 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "928x696d60" : 928 x 696 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "896x672" : 896 x 672 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "896x672d75" : 896 x 672 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "896x672d60" : 896 x 672 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "848x480" : 848 x 480 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "848x480_85" : 848 x 480 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "848x480_75" : 848 x 480 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "848x480_70" : 848 x 480 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "840x525" : 840 x 525 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d85" : 840 x 525 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d75" : 840 x 525 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d70" : 840 x 525 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d60" : 840 x 525 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "832x624" : 832 x 624 @ 74.5 Hz (from: X Server)
(II) NVIDIA(0): "832x624_75" : 832 x 624 @ 74.5 Hz (from: X Server)
(II) NVIDIA(0): "800x600" : 800 x 600 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "800x600_85.00" : 800 x 600 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_75.00" : 800 x 600 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_60.00" : 800 x 600 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_85_0" : 800 x 600 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "800x600_85" : 800 x 600 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600d85" : 800 x 600 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_75_0" : 800 x 600 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_75" : 800 x 600 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x600d75" : 800 x 600 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_72" : 800 x 600 @ 72.2 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x600d70" : 800 x 600 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600d65" : 800 x 600 @ 65.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_60" : 800 x 600 @ 60.3 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x600_60_0" : 800 x 600 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600d60" : 800 x 600 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_56" : 800 x 600 @ 56.2 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x512" : 800 x 512 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x512d60" : 800 x 512 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "720x400" : 720 x 400 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "720x400_85" : 720 x 400 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "700x525" : 700 x 525 @ 85.3 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d85" : 700 x 525 @ 85.3 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d85_0" : 700 x 525 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d75" : 700 x 525 @ 74.8 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d70_0" : 700 x 525 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d70" : 700 x 525 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d60" : 700 x 525 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512" : 640 x 512 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512d85" : 640 x 512 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512d75" : 640 x 512 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512d60" : 640 x 512 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480" : 640 x 480 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480_85.00" : 640 x 480 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480_75.00" : 640 x 480 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480d85" : 640 x 480 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480_85_0" : 640 x 480 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x480_85" : 640 x 480 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480_75" : 640 x 480 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "640x480_75_0" : 640 x 480 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480_73" : 640 x 480 @ 72.8 Hz (from: EDID)
(II) NVIDIA(0): "640x480_73_0" : 640 x 480 @ 72.8 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x480d60" : 640 x 480 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480_60_0" : 640 x 480 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x480_60" : 640 x 480 @ 60.0 Hz (from: EDID)
(II) NVIDIA(0): "640x400" : 640 x 400 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x400_85" : 640 x 400 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x400d85" : 640 x 400 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x400d75" : 640 x 400 @ 75.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x400d70" : 640 x 400 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x400d60" : 640 x 400 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384" : 640 x 384 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d85" : 640 x 384 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d75" : 640 x 384 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d70" : 640 x 384 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d60" : 640 x 384 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360" : 640 x 360 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d85" : 640 x 360 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d75" : 640 x 360 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d70" : 640 x 360 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d60" : 640 x 360 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x350" : 640 x 350 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x350_85" : 640 x 350 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "576x432" : 576 x 432 @ 85.2 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d85" : 576 x 432 @ 85.2 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d85_0" : 576 x 432 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d75" : 576 x 432 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d75_0" : 576 x 432 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0

It turns out it won't do any lower than 640x480. These are my changes:
Modeline "800x600_85.00" 56.55 800 840 928 1056 600 601 604 630 -HSync +Vsync DoubleScan
Modeline "800x600_75.00" 48.91 800 840 920 1040 600 601 604 627 -HSync +Vsync DoubleScan
Modeline "800x600_60.00" 38.22 800 832 912 1024 600 601 604 622 -HSync +Vsync DoubleScan
Modeline "640x480_85.00" 35.71 640 672 736 832 480 481 484 505 -HSync +Vsync DoubleScan
Modeline "640x480_75.00" 30.72 640 664 728 816 480 481 484 502 -HSync +Vsync DoubleScan
Modeline "640x480_60.00" 23.86 640 656 720 800 480 481 484 497 -HSync +Vsync DoubleScan
Modeline "320x240_60.00" 5.26 320 304 336 352 240 241 244 249 -HSync +Vsync DoubleScan
Modeline "320x200_60.00" 4.19 320 304 328 336 200 201 204 208 -HSync +Vsync DoubleScan
and
Modes "1280x1024_85" "1280x1024_75" "1280x1024_60" "1152x864_85" "1152x864_75" "1152x864_60" "1024x768_85" "1024x768_75" "1024x768_60" "800x600_75" "800x600_60" "640x480_75" "640x480_60" "320x240_60" "320x200_60"
I'm not sure if i did that doublescan thingy right, but it gets completely ignored.

Condition Type Values are in display mode during PO amendment

Dear Friends,
I have this issue in import PO.
1. Process is we created an import PO with all necessary values filled under respective condition types to arrive at assessable value but Local freight cost is not known at this point since values are made clearer only after complete clearance of the goods from customs..
2.MIRO for customs done
3. PO amendment needs to be done to fill the values for the local freight & clearing but these condition types are in display mode.
Pls kindly guide me as to what should be done in this case?
thanks
nandu

Hi,
Once you done the MIRO for customs duty, then all the Planned delivery costs will be captured during this MIRO, the condition type will be in display mode in PO.
if you want to amend the PO with local frieght is either you need to reverse the MIRO captured otherwise you need to add the unplanned delivery costs during the MIRO for second time & can pay the same to the Local frieght vendors.
rgds
gsc

Hosted Display Mode issues

Similar Messages

Maybe you are looking for