RTSP over TCP/IP video interleave data missing

I'm writing client code to take streaming video (from an IP camera) over a network and store it on disk.
For some reason (I'm using the TCP/IP Socket class), every now and then, the data coming accross the network never gets to the Socket I've created.
I use EtherReal to look at the packets coming into the computer. The Java program/socket doesn't get all the packet data coming into the computer.
Has anyone experienced this problem and what should I do to fix it?

Here's some of my test code that reads from the socket... I look at the RTP sequence number in the packet as well as in EtherReal to tell what's coming in and what's getting into the socket in code.
The only other thing to note is that I have a buffered reader for the same socket that I don't use while running the code below (could this possibly be interfering?). The code runs in a separate thread from the main thread that created the socket.
static BufferedReader RTSPBufferedReader;
static OutputStreamWriter RTSPBufferedWriter;
static InputStream bufInStream;     
//Establish a TCP connection with the server to exchange RTSP messages
theClient.RTSPsocket = new Socket(ServerHost , RTSP_server_port);
//Set input and output stream filters:
bufInStream = theClient.RTSPsocket.getInputStream();
RTSPBufferedReader = new BufferedReader(new InputStreamReader(bufInStream));
RTSPBufferedWriter = new OutputStreamWrite (theClient.RTSPsocket.getOutputStream());
int i = 0;
firstSeqNo = 0;
while (true) {
       byteRead = bufInStream.read();
       if (byteRead == 36) {     // "$"
               byteRead = bufInStream.read(); // next byte is interleave
               byteRead = bufInStream.read(); // next two bytes is # of bytes
               byteRead2 = bufInStream.read();
               numBytesRTP = (byteRead << 8) | (byteRead2);
               byteRead = bufInStream.read();     // ignore first two byes
               byteRead = bufInStream.read();
               byteRead = bufInStream.read();
               byteRead2 = bufInStream.read();
               lastSeqNo = (unsigned_int(byteRead2) + 256 * unsigned_int(byteRead));
              if (numPackets != 0) {                            if ( (firstSeqNo < lastSeqNo) && (lastSeqNo < (firstSeqNo + 1000))) {                                           System.out.println("lastSeqNo = " + lastSeqNo + "(" + numBytesRTP + ")");                           }                        
               } else {                                numPackets++;                    
                        firstSeqNo = lastSeqNo;    // make non-zero for next time     
       }          // end if "$"
}             // end while true

Similar Messages

  • ACE and RTSP over UDP

    I have a VIP that is not able to stream RTSP over UDP. TCP streaming works fine, but when I configure UDP on the Real client no UDP packets are even processed by the ACE.
    When I configure 'inspect rtsp' on the class, then TCP streaming also breaks. I am using A2.10.
    Anyone got any hints on where I am going wrong ?
    Greg
    class-map match-all stream._rtsp554_vip
    2 match virtual-address 10.216.35.75 tcp eq rtsp
    class-map match-all stream._udp6970_vip
    2 match virtual-address 10.216.35.75 udp eq 6970
    policy-map type loadbalance first-match stream._rtsp554_vip-l7slb
    class class-default
    serverfarm stream._rtsp554_sfarm
    policy-map type loadbalance first-match stream._udp6970_vip-l7slb
    class class-default
    serverfarm stream._UDP_sfarm
    class stream._rtsp554_vip
    loadbalance vip inservice
    loadbalance policy stream._rtsp554_vip-l7slb
    loadbalance vip icmp-reply active
    nat dynamic 1598 vlan 1598
    class stream._tcp8080_vip
    loadbalance vip inservice
    loadbalance policy stream._tcp8080_vip-l7slb
    loadbalance vip icmp-reply active
    nat dynamic 1598 vlan 1598
    class stream._udp6970_vip
    loadbalance vip inservice
    loadbalance policy _udp6970_vip-l7slb
    loadbalance vip icmp-reply active
    nat dynamic 1598 vlan 1598

    I have never got a chance to play with ACE + RTSP over UDP but
    As per
    http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A2/configuration/slb/guide/classlb.html#wp1165238
    ACE supports RTSP over TCP Loadbalanacing only.
    Similarly for RTSP Inspection its clearly stated at
    http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A2/configuration/security/guide/appinsp.html#wp1318637
    For RTSP inspection
    The ACE supports TCP only in conformity with RFC 2326.
    HTH
    Syed Iftekhar Ahmed

  • How to send joystick data over TCP connection

    Hi all,
    I am a long time Labview discussion forum user for learning, but this is my first time posting a question, I hope somebody can help me!
    In the attached VI I am trying to send data from a joystick over a TCP connection. I can send data fine using the TCP examples (in fact the majority of my VI is just a copy of the example). However I am to the point where I do not know how to send all the data necessary (3 axis data, 12 buttons, and the POV data) over TCP. Strings, clusters, and arrays were never my strong suite and converting between them is a nightmare for me.
    Basically I am trying to send each axis data (X,Y, and Z), button data (12 buttons), and POV data (the POV data will be calculated to adjust the position of a camera, so the immediate data is not important, I will add functions to add the change in the button movements to write a standing position for two servos [pan and tilt], for which that I will need to send over the TCP connection) over the TCP connection to control various cameras and motors. I don't know if it is posible to send that much data over a TCP connection in one write VI through a string, and also how to separate the string on the other side in order to control the client VI.
    Again, the actual TCP communication I get, and can operate fine, just formatting all the data into a string (or whatever is required) so that I can unpack on the other side is the issue here.
    Another question I have (not impotant to get the program running just might make it easier on me) is can a TCP server (which sends the data to the client) also recieve data back from the client on the same port ( for example sensor data and digital positions [on,off])? Or do I need to set up two TCP communication loops with the first client acting as the server on a different port than the first, which then sends the data to the original server, which also has a client TCP configuration in another loop? I hope this makes sense...
    One final question.....I already have a solution to this but using labview for the entirety of this project would be nice. I use skype to stream 1080p video from a webcam to my computer so I can view live feed. Can labview do this? This would be awesome if so, I am just not sure if the communication protocols in use could support real time (or as close as possible to streaming) for 1080p video.
    Thanks all in advance for your help,
    Physicsnole
    Attachments:
    cameraserver.vi ‏24 KB
    cameraclient.vi ‏18 KB

    Physicsnole wrote:
    In the attached VI I am trying to send data from a joystick over a TCP connection. I can send data fine using the TCP examples (in fact the majority of my VI is just a copy of the example). However I am to the point where I do not know how to send all the data necessary (3 axis data, 12 buttons, and the POV data) over TCP. Strings, clusters, and arrays were never my strong suite and converting between them is a nightmare for me.
    Well, you cast the axis info cluster to a string, but then you cast it back to an array of DBL. Thatr's not compatible. You should probably cast it back to an "axis info" cluster of exactly the same type. Go the the other VI and right-click the cluster wire to create a constant. Now move that diagram cluster constant to the other VI and use it as type.
    Your default ports don't seem to match. You seem to have client and server roles confused. In the sever you create a listener, but then you start sending packets, even though no connection is established. The connection needs to be initiated by the client.
    Your client stops the loop the first time a timeout is encountered. Shouldn't that be more permanent? Also, please retain code clarity and avoid unecessary complexities. For example, replace the "not or" with a plain "or" and change the loop to "stop if true"
    Physicsnole wrote:
    Basically I am trying to send each axis data (X,Y, and Z), button data (12 buttons), and POV data (the POV data will be calculated to adjust the position of a camera, so the immediate data is not important, I will add functions to add the change in the button movements to write a standing position for two servos [pan and tilt], for which that I will need to send over the TCP connection) over the TCP connection to control various cameras and motors. I don't know if it is posible to send that much data over a TCP connection in one write VI through a string, and also how to separate the string on the other side in order to control the client VI.
    You can send as much as you want. The casting to/from string is the same as described above.
    Physicsnole wrote:
    Another question I have (not impotant to get the program running just might make it easier on me) is can a TCP server (which sends the data to the client) also recieve data back from the client on the same port ( for example sensor data and digital positions [on,off])? Or do I need to set up two TCP communication loops with the first client acting as the server on a different port than the first, which then sends the data to the original server, which also has a client TCP configuration in another loop? I hope this makes sense..
    The primary function of a "server" is to wait for a connection and then communicate with the client once a conenction is established. An established TCP/IP connection is fully two-way and both sides can send and receive.
    LabVIEW Champion . Do more with less code and in less time .

  • How to read data over tcp/ip using labview

    Hi,
    I have a network enabled force transducer (6-axis load cell). I know its IP addr. and the data format it is sending the data out (7 32-bit DWORD, One status and 6 axis force data) . I have been playing around with the simple data client.vi example program. 
    When I executed the program using the devices IP addr. I used to get error 63: TCP/IP connection open. Then I ran the program using localhost in IP addr field, the program executes now indefinetly at one block only. I am attaching the screenshot for ref. 
    Thanks.
    Sasi.
    Attachments:
    TCP-IP.JPG ‏62 KB

    Hello,
    I'm wondering if you can create a rather simple VI that just tries to open and close a TCP connecting to your transducer. All you would need is a TCP Open and a TCP Close wired together with the proper IP address etc. Does this run? I did look to see if there was any NetFT information and I could not find anything. I feel that the problem lies in the communication protocol between your transducer. Another place to see if you can connect to it would be to try hyperterminal. You can access this in Windows XP by clicking Start»All Programs»Accessories»Communications»HypeTermina. Using this, you can try and connect to your instrument with TCP/IP outside of LabVIEW. You might also want to get in contact with the manufacturer to verify that third-party software can indeed communicate with it. There may be a specific set of instructions that need to be sent to the transducer in order to initiate the connection and then read from it. These may be in the form of serial commands that would need to be sent over TCP. What is the make and model of your transducer?
    -Zach
    Certified LabVIEW Developer

  • Can I render a Flash frame as a bitmap and send it over TCP/IP?

    I want to draw some combination of bitmaps, flash shapes, vectors, text etc and draw them programmatically into my movie using ActionScript, and then get every "rendered" pixel of my movie (at 100% view) into an array that I send to another program over TCP/IP. Can anyone help me here?
    The first part of the question is if its possible to render a frame that is a collection of Flash elements as a bitmap? I know that I can iterate through a bitmap and get every pixel using the getPixel method but I'm trying to access the final rendered frame displayed on my screen, including, as I said Flash shapes and text.
    The second question is what would be the best way to send this "video frame" over TCP/IP? Would I use an XML socket connection? That is the only way I know how to send data out of Flash over TCP/IP but I don't know if it is the only way - the help page says the data needs to be formatted as XML, which seems unwieldly for this application.
    I'm doing this now by using Max/MSP/Jitter to do a screen capture the size and location of my Flash movie and then send out the resulting matrix using a "jit.net.send" object (which lets you send frames of video over TCP/IP), but this is too clumsy for the installation I am building.
    Any help would be greatly appreciated!
    -bob

    Thanks! That was exactly what I was looking for in the first half of the question. And I guess the draw() method works in AS2 as well as AS3. I will test it but from what I understand, I can use a Bitmap as kind of my bottom-level container, then create (in ActionScript) a movie clip that can contain other movie clips or drawing API commands or whatever, animate these various elements then finally draw() them into the bitmap. I see that in AS3 I can even use getPixels or getVector to capture the full "video frame" in one line of code.
    Thanks rothrock, for the helpful links. My application is kind of unusual, in that I'm sending "video" data to a proprietary LED controller box for display on a low resolution LED display. I connect to the box over TCP/IP and send it "frames of video" 20 times a second. I got this to work with this other content and software (Max/MSP/Jitter) and I want to see how I could capture all the rendered pixel data in successive frames of Flash animation, format it properly, then send it over TCP/IP to this controller box. Don't really now enough about the various flavors of TCP/IP connections to figure out how to do this in Flash, and I know there are security limitations built in to Flash that have to be worked around. But my movies are small (say 96 pixels by 72 pixels) and I need to send uncompressed data directly to my controller box, so these interesting links showing how to use server-side scripts to create jpgs or pngs are probably not going to help me. I will hopefully find a higher-level programmer than myself to work this out, and I think some of the techniques here will hopefull prove to be helpful.
    Thanks again for your help!

  • HT3819 My iMac had a corrupt seagate HD that had to be replaced my imovie files & itunes video library are missing when I picked up my Mac from Apple?

    I purchased my 27" iMac in October 2010 after attending classes we discovered my computer needed new graphics card, hard drive, and a total rebuild after owning it only 6 months. Apple rebuilt my new computer, several months later same issues began yet again, slowly Apple began replacing defective parts they installed, my computer still hasn't worked as it should and has been in and out of Apple all the time sometimes they keep it for weeks! running tests?? February 10, 2013 I took my imac back in because it has been taking upwards of 6 minutes to make 1 single edit in imovie after 6 days of editing my project I could No Longer save in itunes, external HD, or export my imovie videos (they are 4 min up to 20 min max) Apple informed me that my Hard Drive was corrupt a bad batch of Seagate HD had been installed and my computer was again affected by this and it needed to be replaced and they couldn't get it to respond at all my itunes library was missing, etc. We saved my videos on my external HD I brought in with me. The Genius bar said they would call me in 3-5 days for me to pick up my computer. 9 Days later not hearing back from them I went in to get an update February 19, 2013 No one can tell me what was done except my HD was replaced they can't answer my questions about my itunes library being reinstated or my videos, music is missing, podcasts, etc. I was even using icloud, empty? They tell me IF I find anything wrong or not working again to just bring it back.  My iMovie videos ALL the edits are missing ? I can't find ANY of my videos in my itunes my Library is empty as it is in imovie except for 2 videos? HELP! I can't imagine having to re-edit my entire video with sound effects, fronts, graphics, etc. I spent weeks on this :-( I'm at my wits end with my iMac.... I have searched in my previous itunes library EMPTY ! Waaaah! I want my mommy....

    The Apple Store is not responsible for data loss and generally does not do any backups of your data before performing any repairs, though in some cases, as seems to be the case in yours, they guide you to making your own backup. Here's what they say on the "getting service page" (when I've taken a system in for service a similar statement was presented to me when I agreed to the service):
    Many repairs require Apple to replace or reformat the hard disk, which will result in the loss of your data. Please make sure you back up your data on a regular basis to minimize your data loss. Learn more about backup options. Apple and Apple Authorized Service Providers are not responsible for any damage to or loss of any applications, data, or other information stored on your Mac desktop while performing service.
    Since you say that you backed up your videos before the drive was replaced, why can you not just restore them? And did you not back up anything else?
    If you didn't make any sort of backup of your other data prior to taking the iMac in for service, then sorry but your data is almost certainly gone. Regular reliable backups are a must, particularly when dealing with content you spend a lot of time creating. You may be able to re-download any content you purchased from the iTunes Store or Mac App Store, but anything else you'll have to recreate or re-obtain from the original source.
    Regards.
    Message was edited by: varjak paw

  • Safety of MS Sharing on LAN over TCP/IP via NetBIOS and/or Direct SMB

    Shalini Sampath Kumar at http://answers.microsoft.com/en-us/windows/forum/windows_7-security/ suggested I post this question over
    here:
    What is the safest recommended way to set up MS File and Printer Sharing on a LAN with both Windows 7 Pro and XP Pro machines?  Does "Direct hosting of SMB over TCP/IP," help?  What about setting a "Scope ID" (or did that go out
    with Windows NT)?
    Background:  I've been trained to be paranoid about NetBIOS over TCP/IP.  Right now I have only XP Pro machines on my peer-to-peer workgroup LAN (behind a NAT router and with Simple File Sharing turned off), on which File and Printer Sharing has been
    unbound from TCP/IP and bound to NetBEUI instead, so I feel fairly safe.  Port scanning by ShieldsUp doesn't see any ports through the router, open or closed -- in other words, it appears to be "stealthed," for what that's worth.  With
    NetBIOS disabled on all computers inside the LAN, however, can I perform a valid test of what will happen when File and Printer Sharing is re-bound to TCP/IP?
    My New Problem:  I'm planning to add Window 7 Pro machines, for which NetBEUI isn't an option, and then to transition entirely to Win7 before XP goes off extended support in April.  I will still use a peer-to-peer architecture with password-protected
    sharing turned on (no HomeGroup).  It appears that I can still get rid of NetBIOS (and WINS) in favor of "Direct hosting of SMB over TCP/IP," which sounds safer.  Apparently then only port 445 will be vulnerable instead of ports 137-139. 
    In any case I want to do everything I can to protect my file-sharing port(s) from the Internet (e.g., from anyone who might break into my LAN either by making a wireless connection or by hacking the router itself).  Can anybody give a clear set of steps
    to change sharing from NetBIOS (which I would like to disable entirely) to direct hosting of SMB and to verify that I'm protected as well as possible?
    I will have to completely revamp the network-file-sharing configuration of my XP machines as soon as the first Win7 machine goes on line (and possibly tweak the configuration of Win7 as well), perhaps as early as this week. I want to do this in the way that
    maximizes security to the extent possible.  Thanks in advance more details and guidance on this topic! -- JCW2
    P.S. -- These computers are all laptops and will be used away from my home LAN -- another reason for paranoia about File and Printer Sharing.  I realize that Windows 7 provides an easy way to disable F&PS by selecting any new network location as
    "public," but XP does not (as far as I know).  Fixing that will take more effort and be harder to remember... -- JCW2

    Removing the NetBIOS transport has several advantages compared to NetBIOS over TCP, you can find detailed infromation in the following KB
    Direct hosting of SMB over TCP/IP
    http://support.microsoft.com/kb/204279/en-us
    Yolanda
    TechNet Community Support
    Hi again -- I think I'm slowly catching up with you.  Following from my previous message...
    Somebody on another forum mentioned creating "Hosts" files on each computer to substitute for the DNS server that I don't have on my workgroup.  This is intriguing if I can figure out how to set it up.  (I've heard it said that taking control of
    your "Hosts" file is a good safety precaution anyhow, since it is a frequent target of hackers trying to divert legitimate Web requests to their own malicious sites.)  Does anybody have tips and/or references that would help me accomplish the name resolution
    there?
    Finally, what functionality do I really lose by going the Direct-Hosting-of-SMB-with-Hosts-file (or drive mapping) route as opposed to using NetBIOS over TCP/IP?  Granted, any new machine added to the network would also have to be added to all the "Hosts"
    files (or mapped to a new drive letter) on each machine; but given that I already have to add it to the MAC filter and assign it a DHCP reservation in my router, this isn't a heavy burden for something that doesn't happen often.  Would everything then
    work the same as if NetBIOS were providing the name resolution?
    One missing piece that I see so far -- it's not obvious how this same trick would apply to printer sharing (although I'm not using that feature right now anyhow).  Could this be handled seamlessly through the "Hosts" file as well?
    Thanks and Best Regards to All -- JCW2

  • Video (or Video + Audio) Data Rate

    Wondered if anyone here might know of a software utility that has the ability to scan QuickTime compatible files and either display the video (or video + audio) data rate excursion or, as an alternative, graph the instantaneous variation in the data rate over time.

    Apple +I (show info) in QT player will show you the framerate and bitrate while playing.
    Thanks for your suggestion, Rick. However, I must point out that the data rate so displayed is simply the total average for the entire clip and not the instantaneous (i.e., constantly changing) variance with time. Preliminary observations tend to indicate the single pass H.264 algorithm begings roughly 10% under the requested data rate and quickly settles very near the target. The multipass algorithm, on the other hand, appears to begin in the vicinity of 300% above the targeed data rate and monotonically decreases throughout the remainder of the movie clip. So much for a quick qualitative analysis based on observations during the actualy encoding process.
    What I now wish to do is actually perform a bit of quantitative analysis and, based on those results, correlate actual data rates with the ability of a given H.264 multipass file to sync to an iPod. Basically, I am trying to determine whether or not a user data rate input is used as a comparator during the initial phase of multipass H.264 coding and, if so, how it is implemented. (I.e., how are the delta values handled -- linearly, exponentially, etc.) In addition, I wish to compare QT v7.0.3 with v7.0.4 clips to determine why the latter are less iPod compatible. Too, there remains a question as to whether or not any data rate information is now embedded in the clips themselves since various work arounds tried (i.e., clipping file lengths) have proven unsuccessful.

  • [SOLVED] - Package xf86-video-via is missing from repositories!

    Hi,
    I have a VIA card as follows:
    VGA Compatible Controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)
    My X doesn't work except in VESA mode. But in Vesa mode, when I play videos in mplayer, I can't fullscreen them.
    When I checked the sample xorg.conf files mentioned in the Xorg wiki, I find that I am advised to use the xf86-video-via package.
    But the package xf86-video-via is missing from repositories!
    pacman -Ss xf86-video-via doesn't give results!
    Please help.
    Thanks.
    Last edited by msadiq (2008-12-27 04:18:45)

    Sorry for the long wait, I havent got the time to test but I did uncomment the RenderAccel and that didnt do anything.
    my Xorg.0.log:
    =================================================================
    X.Org X Server 1.5.3
    Release Date: 5 November 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.27-ARCH i686
    Current Operating System: Linux hp-2133 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 25 10:13:11 UTC 2009 i686
    Build Date: 17 December 2008  08:20:05PM
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 27 21:07:16 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Layout0"
    (**) |-->Screen "Screen0" (0)
    (**) |   |-->Monitor "HP LCD"
    (**) |   |-->Device "Via Chrome9"
    (**) |-->Input Device "HP Keyboard"
    (**) |-->Input Device "HP Touchpad"
    (**) Option "AutoAddDevices" "false"
    (**) Not automatically adding devices
    (==) Automatically enabling devices
    (==) No FontPath specified.  Using compiled-in default.
    (==) FontPath set to:
        /usr/share/fonts/misc,
        /usr/share/fonts/100dpi:unscaled,
        /usr/share/fonts/75dpi:unscaled,
        /usr/share/fonts/TTF,
        /usr/share/fonts/Type1
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x81d5fe0
    (II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 4.1
        X.Org XInput driver : 2.1
        X.Org Server Extension : 1.1
        X.Org Font Renderer : 0.6
    (II) Loader running on linux
    (--) using VT number 7
    (--) PCI:*(0@1:0:0) VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] rev 1, Mem @ 0xc0000000/0, 0xfc000000/0, BIOS @ 0x????????/65536
    (II) System resource ranges:
        [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [32] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [33] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [34] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [35] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [48] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [49] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [50] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [51] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [52] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [53] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dri" will be loaded. This was enabled by default and also specified in the config file.
    (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 1.5.3, module version = 2.1.0
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.6
    (II) Loading font FreeType
    (II) LoadModule: "xtt"
    (WW) Warning, couldn't open module xtt
    (II) UnloadModule: "xtt"
    (EE) Failed to load module "xtt" (module does not exist, 0)
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 1.1
    (==) AIGLX enabled
    (==) Exporting typical set of GLX visuals
    (II) Loading extension GLX
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "record"
    (WW) Warning, couldn't open module record
    (II) UnloadModule: "record"
    (EE) Failed to load module "record" (module does not exist, 0)
    (II) LoadModule: "xtrap"
    (II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
    (II) Module xtrap: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension DEC-XTRAP
    (II) LoadModule: "type1"
    (WW) Warning, couldn't open module type1
    (II) UnloadModule: "type1"
    (EE) Failed to load module "type1" (module does not exist, 0)
    (II) LoadModule: "openchrome"
    (II) Loading /usr/lib/xorg/modules/drivers//openchrome_drv.so
    (II) Module openchrome: vendor="http://openchrome.org/"
        compiled for 1.5.3, module version = 0.2.903
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 4.1
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
        compiled for 1.4.2, module version = 1.3.1
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
        compiled for 1.4.2, module version = 1.3.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.0
    (II) OPENCHROME: Driver for VIA Chrome chipsets: CLE266, KM400/KN400,
        K8M800/K8N800, PM800/PM880/CN400, P4M800Pro/VN800/CN700,
        K8M890/K8N890, P4M900/VN896/CN896, CX700/VX700, P4M890, VX800
    (II) Primary Device is: PCI 01@00:00:0
    (!!) VIA Technologies does not support this driver in any way.
    (!!) For support, please refer to http://www.openchrome.org/.
    (!!) (development build, at svn revision 726)
    (II) resource ranges after probing:
        [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [32] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [33] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [34] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [35] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [48] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [49] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [50] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [51] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [52] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [53] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    (II) CHROME(0): VIAPreInit
    (II) Loading sub module "vgahw"
    (II) LoadModule: "vgahw"
    (II) Loading /usr/lib/xorg/modules//libvgahw.so
    (II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 0.1.0
        ABI class: X.Org Video Driver, version 4.1
    (II) CHROME(0): VIAGetRec
    (**) CHROME(0): Depth 24, (--) framebuffer bpp 32
    (==) CHROME(0): RGB weight 888
    (==) CHROME(0): Default visual is TrueColor
    (--) CHROME(0): Chipset: P4M900/VN896/CN896
    (--) CHROME(0): Chipset revision: 0
    (--) CHROME(0): Probed amount of VideoRAM = 262144 kB
    (II) CHROME(0): Setting up default chipset options.
    (II) CHROME(0): VIASetupDefaultOptions
    (II) CHROME(0): Reading config file...
    (**) CHROME(0): Option "AccelMethod" "XAA"
    (**) CHROME(0): Option "PanelSize" "1024x600"
    (**) CHROME(0): Option "EnableAGPDMA" "False"
    (II) CHROME(0): Starting to parse config file options...
    (==) CHROME(0): Shadow framebuffer is disabled.
    (==) CHROME(0): Hardware acceleration is enabled.
    (**) CHROME(0): Using XAA acceleration architecture.
    (==) CHROME(0): Using hardware two-color cursors and software full-color cursors.
    (==) CHROME(0): GPU virtual command queue will be enabled.
    (==) CHROME(0): DRI IRQ will be enabled if DRI is enabled.
    (**) CHROME(0): AGP DMA will be disabled if DRI is enabled.
    (==) CHROME(0): PCI DMA will not be used for XV image transfer if DRI is enabled.
    (==) CHROME(0): Will not enable VBE modes.
    (==) CHROME(0): VBE VGA register save & restore will not be used
        if VBE modes are enabled.
    (==) CHROME(0): Xv Bandwidth check is enabled.
    (==) CHROME(0): Will not impose a limit on video RAM reserved for DRI.
    (==) CHROME(0): Will try to allocate 32768 kB of AGP memory.
    (==) CHROME(0): Digital output bus width is 12 bits.
    (==) CHROME(0): DVI Center is disabled.
    (II) CHROME(0): ViaPanelGetNativeModeFromOption
    (**) CHROME(0): Panel mode index is 13
    (**) CHROME(0): Selected Panel Size is 1024x600
    (==) CHROME(0): Panel will not be forced.
    (==) CHROME(0): TV dotCrawl is disabled.
    (==) CHROME(0): TV deflicker is set to 0.
    (==) CHROME(0): No default TV type is set.
    (==) CHROME(0): No default TV output signal type is set.
    (II) CHROME(0): VIAMapMMIO
    (--) CHROME(0): mapping MMIO @ 0xfc000000 with size 0x9000
    (--) CHROME(0): mapping BitBlt MMIO @ 0xfc200000 with size 0x200000
    (II) CHROME(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (==) CHROME(0): Will not print VGA registers.
    (==) CHROME(0): Will not scan I2C buses.
    (II) CHROME(0): ...Finished parsing config file options.
    (--) CHROME(0): Detected Hewlett Packard 2133 Mini-Note.
    (II) CHROME(0): Detected MemClk 8
    (II) CHROME(0): ViaGetMemoryBandwidth
    (II) CHROME(0): Detected TV standard: PAL.
    (==) CHROME(0): Using gamma correction (1.0, 1.0, 1.0)
    (II) Loading sub module "i2c"
    (II) LoadModule: "i2c"
    (II) Module "i2c" already built-in
    (II) CHROME(0): ViaI2CInit
    (II) CHROME(0): ViaI2CBus1Init
    (II) CHROME(0): I2C bus "I2C bus 1" initialized.
    (II) CHROME(0): ViaI2cBus2Init
    (II) CHROME(0): I2C bus "I2C bus 2" initialized.
    (II) CHROME(0): ViaI2CBus3Init
    (II) CHROME(0): I2C bus "I2C bus 3" initialized.
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) CHROME(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.
    (II) CHROME(0): I2C device "I2C bus 1:ddc2" removed.
    (II) CHROME(0): ViaOutputsDetect
    (II) CHROME(0): Enabling panel from PCI-subsystem ID information.
    (II) CHROME(0): Will not try to detect TV encoder.
    (II) CHROME(0): ViaOutputsSelect
    (II) CHROME(0): ViaOutputsSelect: X Configuration: 0x00
    (II) CHROME(0): ViaOutputsSelect: BIOS Initialised register: 0x07
    (II) CHROME(0): ViaOutputsSelect: Panel.
    (II) CHROME(0): ViaPanelPreInit
    (II) CHROME(0): ViaPanelGetNativeDisplayMode
    (II) CHROME(0): NativeModeIndex: 13
    (II) CHROME(0): ViaModesAttach
    (II) CHROME(0): ViaModesMonitorFixup - Adjusted HSync.lo to 29.677456
    (II) CHROME(0): ViaModesMonitorFixup - Adjusted HSync.hi to 74.904167
    (II) CHROME(0): HP LCD: Using hsync range of 29.68-74.90 kHz
    (II) CHROME(0): HP LCD: Using vrefresh range of 55.00-90.00 Hz
    (II) CHROME(0): Clock range:  20.00 to 230.00 MHz
    (II) CHROME(0): ViaValidMode: Validating 640x350 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x400 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 720x400 (35500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25175)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (50000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (49500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (56300)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (44900)
    (II) CHROME(0): Not using default mode "1024x768" (interlace mode not supported)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (65000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (75000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (78750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (94500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (108000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x960 (108000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x960" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x960 (148500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x960" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (108000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (135000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (157500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (162000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (175500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (189000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (202500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (229500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1792x1344 (204800)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1792x1344" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1856x1392 (218300)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1856x1392" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 832x624 (57284)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "832x624" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (81620)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (96770)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (104990)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (119650)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (121500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (143470)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1360x768 (72000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1360x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "680x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1360x768 (84750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1360x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "680x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (122000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (145060)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (155800)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (179260)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1440x900 (106500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1440x900" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "720x450" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1024 (103125)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (119000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (146250)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (174000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (187000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (214750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1920x1080 (138500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1920x1080" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "960x540" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1920x1200 (154000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1920x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25312)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x480 (26591)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x576 (32663)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x480 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (39822)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 848x480 (33750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 856x480 (31704)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x512 (41164)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x576 (46981)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x600 (48960)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (65028)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (81613)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x768 (81135)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x720 (74600)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x720" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x960 (108280)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x960" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (108280)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1360x768 (85500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1360x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1366x768 (85860)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1366x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (122726)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1440x900 (106470)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1440x900" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (161793)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1920x1080 (172900)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1920x1080" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1024x600 (48960)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x576 (46981)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x512 (41164)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (56300)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (49500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (50000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (39822)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x576 (32663)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 856x480 (31704)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 848x480 (33750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x480 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x480 (26591)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25312)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25175)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x400 (35500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x400 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x350 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (--) CHROME(0): Virtual size is 1024x600 (pitch 1024)
    (**) CHROME(0): *Default mode "1024x600": 49.0 MHz (scaled from 0.0 MHz), 37.3 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "1024x600"x60.0   48.96  1024 1064 1168 1312  600 601 604 622 -hsync +vsync (37.3 kHz)
    (**) CHROME(0):  Default mode "1024x576": 47.0 MHz (scaled from -0.0 MHz), 35.8 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "1024x576"x60.0   46.98  1024 1064 1168 1312  576 576 579 597 -hsync +vsync (35.8 kHz)
    (**) CHROME(0):  Default mode "1024x512": 41.2 MHz (scaled from 0.0 MHz), 31.8 kHz, 59.8 Hz
    (II) CHROME(0): Modeline "1024x512"x59.8   41.16  1024 1056 1160 1296  512 512 515 531 -hsync +vsync (31.8 kHz)
    (**) CHROME(0):  Default mode "800x600": 56.3 MHz (scaled from 0.0 MHz), 53.7 kHz, 85.1 Hz
    (II) CHROME(0): Modeline "800x600"x85.1   56.30  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz)
    (**) CHROME(0):  Default mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    (II) CHROME(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
    (**) CHROME(0):  Default mode "800x600": 50.0 MHz (scaled from -0.0 MHz), 48.1 kHz, 72.2 Hz
    (II) CHROME(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
    (**) CHROME(0):  Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    (II) CHROME(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "800x600": 39.8 MHz (scaled from -0.0 MHz), 37.7 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "800x600"x60.0   39.82  800 840 968 1056  600 600 604 628 +hsync +vsync (37.7 kHz)
    (**) CHROME(0):  Default mode "800x600": 36.0 MHz (scaled from -0.0 MHz), 35.2 kHz, 56.2 Hz
    (II) CHROME(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
    (**) CHROME(0):  Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "720x576"x60.0   32.66  720 744 816 912  576 576 579 597 -hsync +vsync (35.8 kHz)
    (**) CHROME(0):  Default mode "856x480": 31.7 MHz (scaled from -0.0 MHz), 29.8 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "856x480"x60.0   31.70  856 872 960 1064  480 480 483 497 -hsync +vsync (29.8 kHz)
    (**) CHROME(0):  Default mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 485 493 517 +hsync +vsync (31.0 kHz)
    (**) CHROME(0):  Default mode "800x480": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    (II) CHROME(0): Modeline "800x480"x60.3   40.00  800 832 960 1056  480 541 545 628 -hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "720x480": 26.6 MHz (scaled from -0.0 MHz), 29.7 kHz, 59.7 Hz
    (II) CHROME(0): Modeline "720x480"x59.7   26.59  720 736 808 896  480 480 483 497 -hsync +vsync (29.7 kHz)
    (**) CHROME(0):  Default mode "640x480": 36.0 MHz (scaled from -0.0 MHz), 43.3 kHz, 85.0 Hz
    (II) CHROME(0): Modeline "640x480"x85.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz)
    (**) CHROME(0):  Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    (II) CHROME(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
    (**) CHROME(0):  Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
    (II) CHROME(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "640x480": 25.3 MHz (scaled from -0.0 MHz), 31.6 kHz, 60.3 Hz
    (II) CHROME(0): Modeline "640x480"x60.3   25.31  640 656 752 800  480 489 491 525 -hsync -vsync (31.6 kHz)
    (**) CHROME(0):  Default mode "640x480": 25.2 MHz (scaled from -0.0 MHz), 31.5 kHz, 59.9 Hz
    (II) CHROME(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
    (**) CHROME(0):  Default mode "720x400": 35.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.0 Hz
    (II) CHROME(0): Modeline "720x400"x85.0   35.50  720 756 828 936  400 401 404 446 -hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "640x400": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.1 Hz
    (II) CHROME(0): Modeline "640x400"x85.1   31.50  640 672 736 832  400 401 404 445 -hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "640x350": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.1 Hz
    (II) CHROME(0): Modeline "640x350"x85.1   31.50  640 672 736 832  350 382 385 445 +hsync -vsync (37.9 kHz)
    (==) CHROME(0): DPI set to (96, 96)
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "xaa"
    (II) LoadModule: "xaa"
    (II) Loading /usr/lib/xorg/modules//libxaa.so
    (II) Module xaa: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.2.1
        ABI class: X.Org Video Driver, version 4.1
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (II) CHROME(0): VIAUnmapMem
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC?  No, I don't.
    (II) resource ranges after preInit:
        [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [32] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [33] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [34] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [35] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [48] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [49] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [50] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [51] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [52] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [53] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    (II) CHROME(0): VIAScreenInit
    (II) CHROME(0): VIAMapFB
    (--) CHROME(0): mapping framebuffer @ 0xc0000000 with size 0x10000000
    (--) CHROME(0): Frame buffer start: 0xa7771000, free start: 0x258000 end: 0x10000000
    (II) CHROME(0): VIAMapMMIO
    (--) CHROME(0): mapping MMIO @ 0xfc000000 with size 0x9000
    (--) CHROME(0): mapping BitBlt MMIO @ 0xfc200000 with size 0x200000
    (II) CHROME(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (II) CHROME(0): VIASave
    (II) CHROME(0): Primary
    (II) CHROME(0): Crtc...
    (II) CHROME(0): TVSave...
    (II) CHROME(0): VIAWriteMode
    (II) CHROME(0): ViaModeSet
    (II) CHROME(0): Name: 1024x600
    (II) CHROME(0): Clock: 48960
    (II) CHROME(0): VRefresh: 59.995293
    (II) CHROME(0): HSync: 37.317074
    (II) CHROME(0): HDisplay: 1024
    (II) CHROME(0): HSyncStart: 1064
    (II) CHROME(0): HSyncEnd: 1168
    (II) CHROME(0): HTotal: 1312
    (II) CHROME(0): HSkew: 0
    (II) CHROME(0): VDisplay: 600
    (II) CHROME(0): VSyncStart: 601
    (II) CHROME(0): VSyncEnd: 604
    (II) CHROME(0): VTotal: 622
    (II) CHROME(0): VScan: 0
    (II) CHROME(0): Flags: 6
    (II) CHROME(0): CrtcHDisplay: 0x400
    (II) CHROME(0): CrtcHBlankStart: 0x400
    (II) CHROME(0): CrtcHSyncStart: 0x428
    (II) CHROME(0): CrtcHSyncEnd: 0x490
    (II) CHROME(0): CrtcHBlankEnd: 0x520
    (II) CHROME(0): CrtcHTotal: 0x520
    (II) CHROME(0): CrtcHSkew: 0x0
    (II) CHROME(0): CrtcVDisplay: 0x258
    (II) CHROME(0): CrtcVBlankStart: 0x258
    (II) CHROME(0): CrtcVSyncStart: 0x259
    (II) CHROME(0): CrtcVSyncEnd: 0x25c
    (II) CHROME(0): CrtcVBlankEnd: 0x26e
    (II) CHROME(0): CrtcVTotal: 0x26e
    (II) CHROME(0): ViaModeSecondCRTC
    (II) CHROME(0): ViaPanelScale: 1024,600 -> 1024,600
    (II) CHROME(0): mode: 0x8808110
    (II) CHROME(0): mode->name: 0x880a770
    (II) CHROME(0): mode->name: 1024x600
    (II) CHROME(0): ViaSecondCRTCSetMode
    (II) CHROME(0): Setting up 1024x600
    (II) CHROME(0): ViaSetSecondaryFIFO
    (II) CHROME(0): ViaSetSecondaryDotclock to 0x508c01
    (II) CHROME(0): ViaSetUseExternalClock
    (II) CHROME(0): ViaSecondDisplayChannelEnable
    (II) CHROME(0): ViaDisplayDisableCRT
    (II) CHROME(0): ViaDisplayDisableSimultaneous
    (II) CHROME(0): VIAAdjustFrame
    (II) CHROME(0): VIAAdjustFrame
    (II) CHROME(0): - Blanked
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card2
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card3
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card4
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card5
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card6
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card7
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card8
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card9
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card10
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card11
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card12
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card13
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card14
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card2
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card3
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card4
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card5
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card6
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card7
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card8
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card9
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card10
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card11
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card12
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card13
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card14
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    (EE) [drm] drmOpen failed.
    (EE) CHROME(0): [dri] DRIScreenInit failed.  Disabling DRI.
    (II) CHROME(0): - Visuals set up
    (II) CHROME(0): VIAInternalScreenInit
    (II) CHROME(0): - B & W
    (II) CHROME(0): CursorStart: 0xffc0000
    (II) CHROME(0): Using 1800 lines for offscreen memory.
    (II) CHROME(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        8x8 color pattern filled rectangles
        Solid Lines
        Dashed Lines
        Image Writes
        Setting up tile and stipple cache:
            32 128x128 slots
            20 256x256 slots
            32 8x8 color pattern slots
    (==) CHROME(0): Backing store disabled
    (II) CHROME(0): - Backing store set up
    (II) CHROME(0): - SW cursor set up
    (II) CHROME(0): VIAHWCursorInit
    (II) CHROME(0): - Def Color map set up
    (II) CHROME(0): VIALoadPalette
    (II) CHROME(0): VIALoadRgbLut
    (II) CHROME(0): - Palette loaded
    (II) CHROME(0): DPMS enabled
    (II) CHROME(0): - DPMS set up
    (II) CHROME(0): - Color maps etc. set up
    (II) CHROME(0): direct rendering disabled
    (II) CHROME(0): Benchmarking video copy.  Less time is better.
    (--) CHROME(0): Timed   libc YUV420 copy... 1813105. Throughput: 522.2 MiB/s.
    (--) CHROME(0): Timed kernel YUV420 copy... 1789621. Throughput: 529.1 MiB/s.
    (--) CHROME(0): Timed    SSE YUV420 copy... 960929. Throughput: 985.3 MiB/s.
    (--) CHROME(0): Timed    MMX YUV420 copy... 1706519. Throughput: 554.8 MiB/s.
    (--) CHROME(0): Ditching 3DNow! YUV420 copy. Not supported by CPU.
    (--) CHROME(0): Timed   MMX2 YUV420 copy... 1029823. Throughput: 919.4 MiB/s.
    Freed 9834496 (pool 1)
    (--) CHROME(0): Using SSE YUV42X copy for video.
    (WW) CHROME(0): [XvMC] XvMC is not supported on this chipset.
    (WW) CHROME(0): Option "RenderAccel" is not used
    (II) CHROME(0): - Done
    (==) RandR enabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    (II) AIGLX: Screen 0 is not DRI capable
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
    (II) GLX: Initialized DRISWRAST GL provider for screen 0
    (**) Option "CoreKeyboard"
    (**) HP Keyboard: always reports core events
    (**) Option "Protocol" "standard"
    (**) HP Keyboard: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) HP Keyboard: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) HP Keyboard: XkbModel: "pc105"
    (**) Option "XkbLayout" "se"
    (**) HP Keyboard: XkbLayout: "se"
    (**) Option "CustomKeycodes" "off"
    (**) HP Keyboard: CustomKeycodes disabled
    (**) Option "Protocol" "Auto"
    (**) Option "Device" "/dev/input/mice"
    (II) HP Touchpad: Setting mouse protocol to "ExplorerPS/2"
    (**) HP Touchpad: Device: "/dev/input/mice"
    (**) HP Touchpad: Protocol: "Auto"
    (**) Option "CorePointer"
    (**) HP Touchpad: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons"
    (**) HP Touchpad: Emulate3Buttons, Emulate3Timeout: 50
    (**) HP Touchpad: ZAxisMapping: buttons 4 and 5
    (**) HP Touchpad: Buttons: 9
    (**) HP Touchpad: Sensitivity: 1
    (II) evaluating device (HP Keyboard)
    (II) XINPUT: Adding extended input device "HP Keyboard" (type: KEYBOARD)
    (II) evaluating device (HP Touchpad)
    (II) XINPUT: Adding extended input device "HP Touchpad" (type: MOUSE)
    (II) HP Touchpad: Setting mouse protocol to "ExplorerPS/2"
    (II) HP Touchpad: ps2EnableDataReporting: succeeded
    (II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device Video Bus
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device Macintosh mouse button emulation
    (EE) config/hal: NewInputDeviceRequest failed
    ===============================================================
    And my glxinfo:
    ===============================================================
    name of display: :0.0
    display: :0  screen: 0
    direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
    server glx vendor string: SGI
    server glx version string: 1.2
    server glx extensions:
        GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
        GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
        GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
        GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
    client glx vendor string: S3G
    client glx version string: 1.4
    client glx extensions:
        GLX_SGI_make_current_read,  GLX_SGIX_fbconfig,  GLX_SGIX_pbuffer,
         GLX_ARB_get_proc_address, GLX_EXT_texture_from_pixmap,
        GLX_MESA_copy_sub_buffer
    GLX version: 1.2
    GLX extensions:
        GLX_SGI_make_current_read, GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap,
        GLX_MESA_copy_sub_buffer
    OpenGL vendor string: Mesa Project
    OpenGL renderer string: Software Rasterizer
    OpenGL version string: 1.4 (2.1 Mesa 7.2)
    OpenGL extensions:
        GL_EXT_texture_env_add, GL_ARB_multitexture, GL_ARB_transpose_matrix,
        GL_ARB_texture_env_add, GL_ARB_texture_cube_map,
        GL_ARB_texture_compression, GL_ARB_texture_border_clamp,
        GL_ARB_point_parameters, GL_ARB_texture_env_combine,
        GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3,
        GL_ARB_texture_mirrored_repeat, GL_ARB_depth_texture, GL_ARB_shadow,
        GL_ARB_shadow_ambient, GL_ARB_window_pos, GL_ARB_occlusion_query,
        GL_ARB_texture_non_power_of_two, GL_ARB_point_sprite,
        GL_EXT_texture_rectangle, GL_EXT_abgr, GL_EXT_blend_color,
        GL_EXT_texture3D, GL_EXT_packed_pixels, GL_SGIS_texture_lod,
        GL_EXT_rescale_normal, GL_EXT_vertex_array, GL_SGIS_generate_mipmap,
        GL_SGIS_texture_edge_clamp, GL_SGIS_texture_border_clamp,
        GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_point_parameters,
        GL_EXT_draw_range_elements, GL_EXT_bgra, GL_EXT_separate_specular_color,
        GL_EXT_secondary_color, GL_EXT_multi_draw_arrays, GL_EXT_fog_coord,
        GL_EXT_texture_env_combine, GL_EXT_blend_func_separate,
        GL_EXT_stencil_wrap, GL_NV_texgen_reflection, GL_EXT_texture_lod_bias,
        GL_NV_blend_square, GL_NV_texture_rectangle, GL_EXT_shadow_funcs,
        GL_ATI_texture_env_combine3, GL_SGI_color_matrix,
        GL_EXT_texture_edge_clamp
    2 GLX Visuals
       visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
    id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
    0x21 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
    0x3b 32 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
    32 GLXFBConfigs:
       visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
    id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
    0x3c  0 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
    0x3d  0 tc  0 32  0 r  .  .  8  8  8  8  0  0  0 16 16 16 16  0 0 Slow
    0x3e  0 tc  0 32  0 r  y  .  8  8  8  8  0  0  0 

  • When I download a podcast on my iPhone why is the release date missing? This really screws up the sort order.

    when I download a podcast on my iPhone why is the release date missing? This really screws up the sort order.

    Hello yung ron,
    It may be that your iPhone's set to sync automatically, which can potentially remove any music that's been added to the device. It may help to set the device to 'manual mode,' so that you have complete and total control over what content is on the device.
    Managing content manually on iPhone, iPad, and iPod
    http://support.apple.com/kb/HT1535
    Cheers,
    Allen

  • Send Bytes over TCP/IP

    {noformat}I am trying to send an array of bytes over tcp using OutputStream to a chat dispatch server, but few extra bytes are getting added at the begining and
    at the end of the original data I want to send.
    Why is this hapening and how do I overcome this?{noformat}

    ejp wrote:
    byte[] consisted of byte array converted from this hex dumpConverted how?
    If you use a String as a container for this binary data it will be corrupted.I declared the dump as a string like:
    "8A00000000000000000000000B000000476174656B6565706572320F0000004765744C6F67696E536572766572735C0000001800000052656469666620426F6C382E3020206275696C6420323735030000000A00000052424F4C2F312E322E351700000052424F4C2F312E322E352B485454505F434F4E4E4543540F00000052424F4C2F312E322E352B48545450"
    after this what should i do?
    what I am doing is
    1. extract two characters from the string at a time
    2. join them to make a string of two characters
    3. then treat that string as a hex value
    4. convert that hex value to its ascii-char equivalent( so i get an array of characters )
    5. convert the array of characters to array of bytes and send .
    I think that there is a better way to do this. Please suggest. So that no problem occurs.

  • Why is Diadem DAC is slow when reading over TCP/IP?

    Hi,
    I wrote a small VB Script in order to comunicate with a Power Supply over TCP/IP in Diadem DAC, when I first run it, it works perfectly but if I I stop the program and run it again it is suddenly very slow. The only way to make it run normaly again is If I restart Diadem.
    Am I closing my TCP/IP connection correctly? I am not sure what the problem could be.
    thanks for your help
    Attachments:
    PSC_ETH_ReadWrite_Script.txt ‏2 KB

    Hi,
    sorry, but I've no answer to this question but nearly the same problem.
    I wrote a small Qt socket app. which provides a TCP-Server sending every 100 ms.
    I'd like to have Diadem plotting the sent data - I setup a 25 ms refresh rate but
    the actual refresh lasts for about 1 s!! The sent values seem to reach Diadem
    but the processing needs very much time, hence the processor load goes
    directly to 100% which seems to be very strange. I put my code for reading
    the values into the TCP script driver template - SFD_ReadChannel method.
    If comment out the "oUDIM.read()" the refresh is as expected, with the read
    command everything slows down dramatically?
    What's the mistake?
    Best regards and thanks for your help...

  • Buffered streaming over TCP/IP

    Hi!
    I want to transmit a live (with a little delay) video or voice over TCP/IP and stay able to chat with keyboard too. What is the best way to do it?
    Here is the link to my Chat-Project: Chat-Project
    Thank you!
    LabVIEW Portal

    Hi,
    I use Datasocket for this. Never tried TCP/IP functionalities. Have you considered the Datasocket option? Or have you already resolved your task?
    Vaibhav

  • Need help with Modbus RTU over TCP communication

    Hello!
    I'm working with a project that involves communication between a LabView PC, a cRIO-9073 and a few Crouzet PLC's with XN05 modbus extentions. The issue I'm having is to get a stable and reliable connection between the units. The cRIO is communicating with the PLC's by Modbus RTU over TCP and I've created code that read and write to them in a sequential order to avoid possible ModBus conflicts. The LabView PC is sending a "ping" (boolean true) every second to the cRIO over UDP and the cRIO is then sending the "ping" to the PLC over Modbus/TCP. The PLC has a timer that waits for pings, if no ping has been recieved in 7 seconds the emergency brakes are applied and the system shuts down.
    The main problems right now is:
    * After a while I lose the connection between the LabView PC and the cRIO. "Connection with RealTime target cRIO-9073 has been lost".
     - I also get either error code 56 or 66 on the TCP link.
    * The second problem is that if I quickly pull a TP-cable from, let's say, a PLC and then directly plug it back in I want the TCP connection to quickly reestablish. However what happens is that the "pings" from the cRIO stops coming to the PLC for like 5-6 seconds (time to reestablish link?), which means the 7 second timer is almost full. One option would be to raise that timer value, but the drawback is that the system will take longer time to respond to an true error which could be bad.. My question is simply, does it really take 5-6 seconds to establish a TCP connection between a cRIO and a PLC? What affects the time? 
    I would greatly appreciate help or respons on this one. I attach a simplified version of the code I use (all variables and such has been replaced with constants). 
    Is this a good way to do a ModBus communication over TCP with 3 PLC's?  Is there a better, safer, more reliable way? All suggestions on improvment is appreciated
    Thanks!
    /J
    Attachments:
    MB_TCP.vi ‏29 KB
    MB_PLC.vi ‏28 KB

    Dear J,
    Check the state machine Architecture here.
    1. In your acquisition if you got error in any system you close all TCP connections that is not right your other systems are working fine.
    2. You go with parallel loop connection. For each PLC you run separate code with error handlers.
    3. Check the attached VI for TCP Read. Same VI you can modify and use for your ModBUS operations.
    4. In you Sub VI you are passing a constant cluster. I am not able to understand what is the use of case structure inside the subVI, In you code you are passing the constant so its always same.
    As you done previously made 3 loops or VIs to read the data in a main VI. First try to made one VI with one PLC, remove your all bugs and errors and copy it 3-time with different-different configurations.
    Thanks and Regards
    Himanshu Goyal | LabVIEW Engineer- Power System Automation
    Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
    It Only gets BETTER!!!
    Attachments:
    Tcp Host.vi ‏28 KB

  • How do i send an array of clusters with variable size over TCP/IP?

    Hi,
            I'm trying to send an array of clusters with varible size over TCP/IP,. But I'm facing the following problems:
    1) I need to accept the size of array data from the user and increase the size dynamically.
    I'm doing this using the property node but how do I convey the new size to my TCP read?
    2) I need to wire an input to my 'bytes to read' of the TCP read.
    But the number of bytes to read changes dynamically
    How do I ensure  the correct number of bytes are read and reflected on the client side?
    3) Is there anyway I can use global varibles over a network such that their values are updated just as if they would on one computer?
     Will be a great help if someone posts a solution!
    Thank you...

    twilightfan wrote:
    Altenbach,
     ... xml string. ...number of columns that I'm varying using property node s... I solved these problems by using a local variable as the type input ...o TCP read is creating a problem.... second TCP read gets truncated data because
    its no longer just the first four bytes that specify the length of the data, it could be more as my array of cluster can be pretty huge.
    Instead of writing long and complicated sentences that make little sense, why don't you simply show us your code? 
    What does any of this have to do with xml strings???? I don't see how using a local variable as type input changes anything. The user cannot interact with "property nodes", just with controls. Please clarify. Once the array of clusters is flattened to a string you only have one size that describes the size of the data, no matter how huge it is (as long as it is within the limits of I32). Similarly, you read the string of that same defined length and form the array of clusters from it. How big are the strings? What is your definition of "huge"?
    Here's is my earlier code, but now dealing with an array of clusters. Not much of a change. Since you have columns, you want 2D. Add as many diensions you want, but make sure that the control, diagram constant, and indicator all match.
    The snipped shows for a 1D array, while the attached VI shows the same for a 2D array. Same difference.  
    Message Edited by altenbach on 01-31-2010 01:13 AM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    FlattenArrayOfClusters.vi ‏12 KB
    ioclusters3MOD.png ‏25 KB

Maybe you are looking for