- Discuss - lists.centos.org

centos installation on xserve?
by Mark Quitoriano 12 Jan '08

12 Jan '08

Hi guys, anyone tried to run centos in xserve for production? what architecture do you use? thanks!

1 0

yum hangs when Reading Local RPMDB
by Kai Schaetzl 12 Jan '08

12 Jan '08

All of a sudden yum hangs on a Centos 4.5 (updated to the latest patch before 4.6) when I try to use it. "clean metadata" didn't help. The output of -d5 shows it gets to the point of "Reading Local RPMDB" and then sits there. The process doesn't die, but doesn't seem to do anything from that point on. strace shows this: futex(0xb76dcae8, FUTEX_WAIT, 2, NULL I remember that futex hangs have been mentioned in the past when doing "big" updates from 4.x to 4.y, but this wasn't the case here. python-2.3.4-14.4 python-sqlite-1.1.7-1.2.1 sqlite-3.3.6-2 yum-2.4.3-3.el4.centos Kernel in use is not the latest 4.5 kernel, but one from 4.3. This shouldn't matter in this case, shouldn't it? How can I resolve this? I see that one suggestion is rm /var/lib/rpm/__db*. How do I rebuild it then? I found that cleaning the metadata doesn't remove the sqlite databases, so I removed these from /var/yum/cache as well. The rebuilt databases were different, but it didn't solve the problem. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

Re: [CentOS] yum hangs when Reading Local RPMDB
by David G. Miller 11 Jan '08

11 Jan '08

Kai Schaetzl <maillists(a)conactive.com> wrote: > Before I do this without need I have a question: if the rpm db is > corrupt shouldn't rpm -q or -qa stop working? Kai Not necessarily. A regular user can run rpm -q since it doesn't lock the database (your original posting showed rpm hanging on a FUTEX). I don't know rpm internals but I'd guess that simple queries for a specific package or even a listing of all packages don't go very deep into the rpm database. Also, since the database isn't being updated, there isn't any need to lock the database during the query. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

1 0

Use CentOSplus to carry latest GUI packages
by Ross S. W. Walker 11 Jan '08

11 Jan '08

I don't know if this has been talked about much in the past, but I was wondering if CentOSplus could be used to carry the latest stable versions of the GUI applications KDE/Gnome. These apps often lag behind quite a bit even on the selected stable branch upstream has chosen. For example, would it decrease stability to update KDE from 3.5.4 to 3.5.8? I think it would add to stability as long as you stay within that 3.5 branch, but upstream thinks otherwise and tries to re-invent the wheel by backporting 3.5.5-3.5.8 fixes into 3.5.4 which often don't work completely and have the potential of creating new bugs themselves. Another thing, Xen, the Xen package says it's 3.0.3, but looking at the SRPM it turns out it's the Xen 3.1 kernel with the Xen 3.0.3 'xm' and 'xend' dom0 utilities. In my book that's Xen 3.1, why not just fix the parts of the 3.1 utilities that broke between releases? Anyways Xen may not be a good candidate as others may have environmental dependencies on the upstream version, but upgrading to the latest minor version within a branch for a given application shouldn't break environmental dependencies, ie provide Xen 3.1.4 if it contains the xm and xend fixes that upstream was looking for. What is the consenus on this? -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

3 2

CentOS-announce Digest, Vol 35, Issue 3
by centos-announce-request＠centos.org 11 Jan '08

11 Jan '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEEA-2008:0028 CentOS 5 x86_64 tzdata Update (Karanbir Singh) 2. CEEA-2008:0028 CentOS 5 i386 tzdata Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Jan 2008 01:18:45 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEEA-2008:0028 CentOS 5 x86_64 tzdata Update To: centos-announce(a)centos.org Message-ID: <20080111011845.GA18252(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2008:0028 Upstream details at : https://rhn.redhat.com/errata/RHEA-2008-0028.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: b866fd855849f6a81c1916187f4219ad tzdata-2007k-1.el5.noarch.rpm Source: b20dacb215b1342c2011aed06b61c1cb tzdata-2007k-1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Fri, 11 Jan 2008 01:18:45 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEEA-2008:0028 CentOS 5 i386 tzdata Update To: centos-announce(a)centos.org Message-ID: <20080111011845.GA18235(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2008:0028 Upstream details at : https://rhn.redhat.com/errata/RHEA-2008-0028.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 24d39598f5138eec781afbc3a3cf9a2f tzdata-2007k-1.el5.noarch.rpm Source: b20dacb215b1342c2011aed06b61c1cb tzdata-2007k-1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 35, Issue 3 **********************************************

1 0

CentOS 5.0 /proc Backup/Restore
by Krautkramer, John 11 Jan '08

11 Jan '08

Hi, I've recently switched to CentOS 5.0 from RedHat 9.0 and found a new directory /proc which contains "virtual" files according to the docs. When I try to run my normal backup which uses cpio to create archives, it complains about not being able to access many files in the /proc directory. This is also true of some files in /sys/devices. Searching for something that wouldn't have this problem, I tried mondorescue. One of the first things I noticed is, by default, mondorescue skips the /proc directory. Does anyone know the details of my observations here? Are these files automatically generated at runtime? Thanks is advance for any insight someone can provide here! John

4 3

NFS/NIS and firewalls
by Scott Ehrlich 11 Jan '08

11 Jan '08

I have a few C5 machines on an isolated LAN that connect to a RHEL5 server via NFS and NIS for authentication. I discovered that one of the C5 workstations worked fine for NFS exporting, but refused to collaborate with the EL5 server for NIS user authentication. I had successfully connected other systems to this server without issue, but this machine was finicky. I had initially enabled the EL5 firewall, then later disabled it, including selecting --disable-firewall. Still, this one C5 workstation wouldn't cooperate for user authentication. Then, as a bit of an experiment, I opted to visit the EL5 services and manually highlight IPtables, clicked STOP, and tried the verification again. This time, the C5 system got the NIS data. Now, if I want to enable a firewall on all machines - As a server, EL5 does have an option to select NFS services be run on specific ports. How do I configure the C5 clients to also communicate on those ports, thus allowing full NIS/NFS user authentication and directory exporting, all the while with built-in firewall protection on all systems? These are all out-of-box setups, with no updates, and full package installs from the install media. As time goes on, I will migrate to the OpenLDAP world, but I haven't had the opportunity to experiment with that just yet. Thanks. Scott

2 1

OT -- Flash (.swf file) audio stream separation
by Robert 11 Jan '08

11 Jan '08

Does anyone here know of a utility that will filter a flash stream into its video and audio components? In order of preference -- 1)RPM 2)any open source tool 3)anything that does the job. Thanks for any clues.

2 1

How to PXE Boot
by Oscar Usifer 11 Jan '08

11 Jan '08

Folks, Are there updated instructions on how to set up PXE boot under CentOS 5.x? I found that the system-config-netboot RPM has been absent, and the instructions written reference it, with a bug report not yet closed on Red Hat. Thanks, OSC http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-netboot-pxe-c… http://rhn.redhat.com/errata/RHBA-2006-0380.html -- Are we headed for a recession? Read more on the Money Portal Mail.com Money - http://www.mail.com/Money.aspx?cat=money

2 1

Sun Fire X4200 M2 / CentOS 5 APIC issues
by Ryan Ordway 11 Jan '08

11 Jan '08

I had been running CentOS 5 happily on my Sun Fire X4200 M2 systems, then I upgraded the BIOS and iLOM firmware. Now I'm running into what seems to be a fairly common problem with newer motherboards. I cannot boot unless I use the 'noapic' kernel option. If I try to boot the kernel normally, I get the error: "MP-BIOS bug: 8254 timer not connected to IO-APIC" I can boot using noapic, but interrupts are *HORRIBLE* with noapic on the X4200 M2. Here is a system with the new BIOS running with noapic: [rordway@aphrodite ~]$ uname -a Linux aphrodite 2.6.18-53.1.4.el5.centos.plus #1 SMP Fri Dec 7 07:05:12 EST 2007 x86_64 x86_64 x86_64 GNU/Linux [rordway@aphrodite ~]$ cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 149047419 568805 215848 76392 XT-PIC timer 1: 0 2 0 0 XT-PIC i8042 2: 0 0 0 0 XT-PIC cascade 4: 399 80 58 26 XT-PIC serial 5: 138 19 4 4 XT-PIC ehci_hcd:usb2 7: 16203243 179851060 180334480 180522274 XT-PIC ioc0, eth1 8: 1 0 0 0 XT-PIC rtc 9: 0 0 0 0 XT-PIC acpi 11: 764 64 17 21 XT-PIC ohci_hcd:usb1 12: 2 2 0 0 XT-PIC i8042 14: 77 6 13 3 XT-PIC ide0 15: 15353489 192264 58884 10141 XT-PIC eth0 NMI: 0 0 0 0 LOC: 149884909 149891944 149889634 149890602 ERR: 377601098 MIS: 0 Compare this to an identical system running an identical kernel, but the older BIOS: [rordway@selene ~]$ uname -a Linux selene 2.6.18-53.1.4.el5.centos.plus #1 SMP Fri Dec 7 07:05:12 EST 2007 x86_64 x86_64 x86_64 GNU/Linux [rordway@selene ~]$ cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 415472769 0 0 0 IO-APIC-edge timer 1: 2 0 0 0 IO-APIC-edge i8042 4: 270 0 10 17 IO-APIC-edge serial 8: 1 0 0 0 IO-APIC-edge rtc 9: 0 0 0 0 IO-APIC-level acpi 12: 4 0 0 0 IO-APIC-edge i8042 14: 25 74 0 0 IO-APIC-edge ide0 58: 323 464 0 0 IO-APIC-level ohci_hcd:usb1 66: 26 0 0 0 IO-APIC-level ehci_hcd:usb2 74: 5940 981922 7254 524 IO-APIC-level ioc0 82: 2026 53828037 0 138601 IO-APIC-level eth0 90: 2237 61820570 0 689058 IO-APIC-level eth1 NMI: 0 0 0 0 LOC: 415433007 415433000 415432928 415432856 ERR: 0 MIS: 0 Note the huge ERR count with XT-APIC, and ioc0 and eth1 sharing an interrupt (SAS controller and my private network interface) Does anyone know if this has been fixed in the mainline kernel, and if so if this can be integrated into the CentOS 5.1 kernel (namely the CentOS Plus kernel)? Thanks! Ryan -- Ryan Ordway E-mail: rordway(a)oregonstate.edu Unix Systems Administrator rordway(a)library.oregonstate.edu OSU Libraries, Corvallis, OR 97331 Office: Valley Library #4657

2 3

Samba's winbind and SELinux conflict
by Filipe Brandenburger 11 Jan '08

11 Jan '08

Hi, I was trying to setup winbind on a CentOS 4 host to authenticate to the AD on my network. My smb.conf is very simple, I'm only setting workgroup, realm, security, and I'm setting for winbind: encrypt passwords = yes winbind separator = + idmap uid = 10000-20000 idmap gid = 10000-20000 When trying to start the service with "service winbind start", I'm getting these error messages: Jan 10 16:18:00 myhost kernel: audit(1199999880.483:2): avc: denied { write } for pid=4490 comm="winbindd" name="secrets.tdb" dev=sda2 ino=192690 scontext=root:system_r:winbind_t tcontext=root:object_r:samba_etc_t tclass=file Jan 10 16:18:00 myhost winbindd[4490]: [2008/01/10 16:18:00, 0] passdb/secrets.c:secrets_init(67) Jan 10 16:18:00 myhost winbindd[4490]: Failed to open /etc/samba/secrets.tdb Jan 10 16:18:00 myhost winbindd[4490]: [2008/01/10 16:18:00, 0] nsswitch/winbindd.c:main(1010) Jan 10 16:18:00 myhost winbindd[4490]: Could not initialize domain trust account secrets. Giving up Clearly winbind is violating SELinux's targeted policy by trying to write the secrets.tdb file on /etc/samba directory. I looked at smb.conf's man page that I could set the directory of this file using the "private dir" directive on smb.conf's global section, and that's what I did, I set it to /var/cache/samba/winbindd_privileged, which I found was a directory created by the samba-common package, with 750 permissions and a winbind_var_run_t context. I would like to know if I did the right thing or not. Or if I should have put the secrets.tdb in a directory other than that one. What would be the recommended configuration? Thanks! Filipe

1 0

Citadel pre-built packages?
by Filipe Brandenburger 11 Jan '08

11 Jan '08

Hi, Has someone created RPM packages of citadel for CentOS 4 or 5? I would be interested. If anyone has it in a public repository and would like to share, please tell me. I looked for it in CentOS base repositories and Rpmforge but didn't find anything. Anyway, please let me know. Thanks! Filipe

1 0

Re: [CentOS] How to PXE Boot
by Oscar Usifer 11 Jan '08

11 Jan '08

This is the correct bug report I wanted to share, thanks. https://bugzilla.redhat.com/show_bug.cgi?id=236749 > ----- Original Message ----- > From: "Oscar Usifer" <oscaruser(a)programmer.net> > To: centos(a)centos.org > Subject: [CentOS] How to PXE Boot > Date: Thu, 10 Jan 2008 15:37:09 -0500 > > > Folks, > > Are there updated instructions on how to set up PXE boot under > CentOS 5.x? I found that the system-config-netboot RPM has been > absent, and the instructions written reference it, with a bug > report not yet closed on Red Hat. > > Thanks, > OSC > > http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-netboot-pxe-c… > http://rhn.redhat.com/errata/RHBA-2006-0380.html > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos -- Are we headed for a recession? Read more on the Money Portal Mail.com Money - http://www.mail.com/Money.aspx?cat=money

1 0

NFS problems with CentOS 4.5
by Mark Belanger 11 Jan '08

11 Jan '08

Our large and complex build system is having very sporadic failurs as we try to update to CentOS 4.5. This takes the form of files that exist - and have existed for some time - not being found: file.whatever: No such file: No such file or directory This happens both with source files, .o's - meaning that the errors come from both the compiler and linker. The build storage is on NFS and the errors don't happen when we target local disk. We also have solaris nad Centos 3.x building the same code base in a similar fashion with no problem. We are currently using mount options of: rw,nosuid,bg,timeo=50,retry=1 And have also tried: rw,intr,bg,proto=tcp,nfsvers=3,rsize=32768,wsize=32768 without success. Any suggestions welcome. -Mark

3 4

Re: [CentOS] "find" switch to find files of a certain size?
by techlists＠comcast.net 11 Jan '08

11 Jan '08

I just answered my own question; ignore original post. -------------- Original message ---------------------- From: techlists(a)comcast.net > > Is there a switch in "find" (or some other command besides find) that'll let you > find files larger than a specified size? > > My file system is 88% full and I'd like to see where the biggest space hoggers > are. > > PG > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] "find" switch to find files of a certain size?
by Marko A. Jennings 11 Jan '08

11 Jan '08

On Thu, January 10, 2008 11:21 am, techlists(a)comcast.net wrote: > > Is there a switch in "find" (or some other command besides find) that'll > let you find files larger than a specified size? -size Read the man page.

1 0

Re: [CentOS] yum hangs when Reading Local RPMDB
by David G. Miller 10 Jan '08

10 Jan '08

Kai Schaetzl <maillists(a)conactive.com> wrote: > All of a sudden yum hangs on a Centos 4.5 (updated to the latest patch > before 4.6) when I try to use it. "clean metadata" didn't help. > The output of -d5 shows it gets to the point of "Reading Local RPMDB" and > then sits there. The process doesn't die, but doesn't seem to do anything > from that point on. strace shows this: futex(0xb76dcae8, FUTEX_WAIT, 2, > NULL > > I remember that futex hangs have been mentioned in the past when doing > "big" updates from 4.x to 4.y, but this wasn't the case here. > python-2.3.4-14.4 > python-sqlite-1.1.7-1.2.1 > sqlite-3.3.6-2 > yum-2.4.3-3.el4.centos > Kernel in use is not the latest 4.5 kernel, but one from 4.3. This > shouldn't matter in this case, shouldn't it? > > How can I resolve this? > I see that one suggestion is rm /var/lib/rpm/__db*. How do I rebuild it > then? > I found that cleaning the metadata doesn't remove the sqlite databases, so > I removed these from /var/yum/cache as well. The rebuilt databases were > different, but it didn't solve the problem. > > > Kai From the rpm man page: REBUILD DATABASE OPTIONS The general form of an rpm rebuild database command is rpm {--initdb|--rebuilddb} [-v] [--dbpath DIRECTORY] [--root DIRECTORY] Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers. Remove the __db* files and then "rpm --rebuilddb" is usually sufficient unless you have non-standard locations for the database. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

2 1

FYI: CentOS mailserver on nixspam RBL
by Kai Schaetzl 10 Jan '08

10 Jan '08

In case someone's using the nixspam RBL and wondering why the influx from the CentOS mailing lists has stopped today: http://www.dnsbl.manitu.net/lookup.php?language=en&value=72.21.40.12 Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

Probably OT: Has anyone else seen SeaMonkey 'pop' without warning?
by MHR 10 Jan '08

10 Jan '08

I sent a bug report to Mozilla about this, but I was hoping someone here might have an insight on this. I use SeaMonkey as my default browser (32-bit even though I'm running x86_64 CentOS 5.1), version 1.1.7. Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants to interact with the file system, the SeaMonkey window just closes. If I reopen it and go to the same place and try the same thing, it works just fine (and usually, the second SM window is more stable and doesn't do that again). This frequently happens when I try to save a web page, load an email attachment, print a page, or anything that interacts with the file system. Just now it happened when I tried to switch tabs, but that's unusual. Anyone have a clue? TIA. mhr

9 16

CentOS 5 & sendmail configuration
by Frank M. Ramaekers 10 Jan '08

10 Jan '08

I'm attempting to configure sendmail to relay outgoing mail to an internal smtp server. I found that the commented line in sendfile.mc that starts with 'dnl define(`SMART_HOST'... needed to be uncommented and a valid value inserted. No problem there, but when I attempt to 'make -C /etc/mail', I get WARNING: 'sendmail.mc' is modified. Please install package sendmail-cf to update your configuration. make: Leaving directory `/etc/mail' Researching further, it seems I need to install the 'sendmail-cf' package, which I can't seem to find with yum. What piece of this puzzle am I missing? TIA, Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at PrivacyAct(a)ailife.com.

3 3

Where can I find compress and uncompress?
by Daniel Augusto Martins 10 Jan '08

10 Jan '08

Dear All Utilities compress and uncompress seem to have disapeared when I migrate from CentOS 4 to CentOS 5. Anyone knows where we can find them? Thanks <html> <body> Aviso: "O emitente desta mensagem é responsável por seu conteúdo e endereçamento. Cabe ao destinatário cuidar quanto ao tratamento adequado. Sem a devida autorização, a divulgação, a reprodução, a distribuição ou qualquer outra ação em desconformidade com as normas internas da ELETRONORTE S/A são proibidas e passíveis de sanção disciplinar, cível e criminal. Esta mensagem pode ser monitorada". Notice: "The sender of this message is responsible for its content and addressing. The receiver shall take proper care of it. Without due authorization, the publication, reproduction, distribution or the performance of any other action not conforming to ELETRONORTE S/A internal policies and procedures is forbidden and liable to disciplinary, civil or criminal sanctions. This message can be monitored". </body> </html>

7 9

CentOS-announce Digest, Vol 35, Issue 2
by centos-announce-request＠centos.org 10 Jan '08

10 Jan '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2008:0003 Moderate CentOS 3 i386 e2fsprogs - security update (Tru Huynh) 2. CESA-2008:0003 Moderate CentOS 3 x86_64 e2fsprogs - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 9 Jan 2008 19:11:49 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0003 Moderate CentOS 3 i386 e2fsprogs - security update To: centos-announce(a)centos.org Message-ID: <20080109181149.GA8843(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0003 e2fsprogs security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0003.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/e2fsprogs-1.32-15.4.i386.rpm updates/i386/RPMS/e2fsprogs-devel-1.32-15.4.i386.rpm source: updates/SRPMS/e2fsprogs-1.32-15.4.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update e2fsprogs\* Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Re: Problem accessing my webmail
by Jun Salen 10 Jan '08

10 Jan '08

>I disable firewall and SELinux on mail server machine and the PIX firewall where the machine >connects to outside world allow port 80 and 443 just as before but still the problem persist. >I will try to up later the old machine and will check if the web mail becomes accessible and >then restore the new machine (this is in production only) again. This is to see if DNS is the >culprit, but I doubt it. Any more ideas guys? Sorry for the posting prior to this without the >subject. Tsk tsk.Hi, After trying to restore my old server today and test connecting to my webmail using http://, it also failed but connect using https:// was successful. Probably our PIX firewall has allowing connection to port 443 but not port 80. So in order to solve this, I reconfigure the mail server (Zimbra) to use mode "https" instead of "mixed". This solved my problem. The only way to access my webmail is through https but this was fine and is more secured. By the way, although I will be able to access our PIX, I do not have the guts in configuring it, to avoid problem since I do not know IOS yet. Thanks, junji aisalen.wordpress.com Linux Registered User #253162 CentOS User Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0

Re: Problem accessing my webmail
by Jun Salen 10 Jan '08

10 Jan '08

>Firewall? What have you done to try and find out what the problem is? I disable firewall and SELinux on mail server machine and the PIX firewall where the machine connects to outside world allow port 80 and 443 just as before but still the problem persist. I will try to up later the old machine and will check if the web mail becomes accessible and then restore the new machine (this is in production only) again. This is to see if DNS is the culprit, but I doubt it. Any more ideas guys? Sorry for the posting prior to this without the subject. Tsk tsk. Thanks, junji aisalen.wordpress.com Linux Registered User #253162 CentOS User Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0

(no subject)
by Jun Salen 10 Jan '08

10 Jan '08

>Firewall? What have you done to try and find out what the problem is? I disable firewall and SELinux on mail server machine and the PIX firewall where the machine connects to outside world allow port 80 and 443 just as before but still the problem persist. I will try to up later the old machine and will check if the web mail becomes accessible and then restore the new machine (this is in production only) again. This is to see if DNS is the culprit, but I doubt it. Any more ideas guys? Thanks, junji aisalen.wordpress.com Linux Registered User #253162 CentOS User Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0

[Fwd: Problems with two S3 video devices.]
by ArcosCom Linux User 10 Jan '08

10 Jan '08

Please, I need some type of help with this issue. Thanks!! ---------------------------- Mensaje original ---------------------------- Asunto: Problems with two S3 video devices. De: "ArcosCom Linux User" <linux(a)arcoscom.com> Fecha: Vie, 28 de Diciembre de 2007, 9:48 Para: xorg(a)lists.freedesktop.org -------------------------------------------------------------------------- Hi, I'm having problems in an old PC with 2 S3 video devices. Sorry for the long e-mail, but here is all the config files and log files output. The X's start fine, and gnome too. I have the 2 screens working fine, but when I launch some programs, the xserver restart without any type of screen message. I don't know what is the problem, because VNC extension works fine, screen0 runs fine at 800x600 and screen1 runs fine at 1024x768. The 2 video devices uses the same driver s3virge. The first is a PCI (the principal screen) and the second is an AGP device (the secondary screen). Could anyone help me in diagnose and solve this problem? Thanks!! ========================================================== lspci output: 00:08.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) (prog-if 00 [VGA]) Subsystem: S3 Inc. ViRGE/DX Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at d8000000 (32-bit, non-prefetchable) [size=64M] [virtual] Expansion ROM at 30120000 [disabled] [size=64K] 01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02) (prog-if 00 [VGA]) Subsystem: S3 Inc. Trio3D/2X Flags: bus master, medium devsel, latency 32 Memory at d0000000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at 30000000 [disabled] [size=64K] Capabilities: [dc] Power Management version 1 Capabilities: [80] AGP version 1.0 ================================================================= This is the xorg.conf file content: Section "ServerLayout" Identifier "Multihead layout" Screen 0 "Screen0" LeftOf "Screen1" Screen 1 "Screen1" 0 0 InputDevice "Keyboard0" "CoreKeyboard" Option "Xinerama" "off" Option "Clone" "on" EndSection Section "Module" Load "vnc" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "es" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName "Monitor 1024x768" HorizSync 31.5 - 80.0 VertRefresh 30.0 - 100.0 Option "dpms" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor 1024x768" HorizSync 31.5 - 80.0 VertRefresh 30.0 - 100.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "s3virge" VendorName "Videocard Vendor" BoardName "S3 Inc. ViRGE/DX or /GX" BusID "PCI:0:8:0" Option "pci_burst" "on" Option "pci_retry" "on" EndSection Section "Device" Identifier "Videocard1" Driver "s3virge" VendorName "Videocard Vendor" BoardName "S3 Inc. 86c368 [Trio 3D/2X]" BusID "PCI:1:0:0" Option "pci_burst" "on" Option "pci_retry" "on" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1024x768" "800x600" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1024x768" "800x600" EndSubSection SubSection "Display" Viewport 0 0 Depth 8 Modes "1024x768" "800x600" EndSubSection Option "UserPasswdVerifier" "VncAuth" Option "PasswordFile" "/root/.vnc/passwd" Option "httpd" "/usr/share/vnc/classes/" Option "ClientWaitTimeMillis" "300000" Option "deferUpdate" "100" Option "DisconnectClients" "off" Option "AllwaysShared" "on" Option "IdleTimeout" "300" Option "desktop" "screen0" EndSection Section "Screen" Identifier "Screen1" Device "Videocard1" Monitor "Monitor1" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 16 Modes "1024x768" "800x600" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1024x768" "800x600" EndSubSection SubSection "Display" Viewport 0 0 Depth 8 Modes "1024x768" "800x600" EndSubSection Option "UserPasswdVerifier" "VncAuth" Option "PasswordFile" "/root/.vnc/passwd" Option "httpd" "/usr/share/vnc/classes/" Option "ClientWaitTimeMillis" "300000" Option "deferUpdate" "100" Option "DisconnectClients" "off" Option "AllwaysShared" "on" Option "IdleTimeout" "300" Option "desktop" "screen1" EndSection ============================================================= This is the Xorg.0.log.old output: X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: Linux 2.6.9-42.0.3.ELsmp i686 Red Hat, Inc. Current Operating System: Linux acpc08.arcoscom 2.6.18-53.1.4.1.el5_ArcosCom #1 SMP Wed Dec 5 08:29:14 CET 2007 i686 Build Date: 10 November 2007 Build ID: xorg-x11-server 1.1.1-48.26.el5 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 27 09:56:31 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Multihead layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Videocard0" (**) |-->Screen "Screen1" (1) (**) | |-->Monitor "Monitor1" (**) | |-->Device "Videocard1" (**) |-->Input Device "Keyboard0" (==) |-->Input Device "<default pointer>" (==) The core pointer device wasn't specified explicitly in the layout. Using the default mouse configuration. (==) No FontPath specified. Using compiled-in default. (==) FontPath set to: unix/:7100, built-ins (==) RgbPath set to "/usr/share/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (**) Option "Xinerama" "off" (II) Open ACPI successful (/var/run/acpid.socket) (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0691 card 0000,0000 rev c4 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8598 card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106,0000 rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 0000,0000 rev 40 class 06,00,00 hdr 00 (II) PCI: 00:08:0: chip 5333,8a01 card 5333,8a01 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:09:0: chip 1274,5880 card 1274,2000 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:0a:0: chip 10b7,9055 card 10b7,9055 rev 24 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 5333,8a13 card 5333,8a13 rev 02 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0x30000000 - 0x300fffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:8:0) S3 Inc. ViRGE/DX or /GX rev 1, Mem @ 0xd8000000/26 (--) PCI: (1:0:0) S3 Inc. 86c368 [Trio 3D/2X] rev 2, Mem @ 0xd0000000/26 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xdd000000 from 0xdd7fffff to 0xdcffffff (II) Active PCI resource ranges: [0] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [1] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [2] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [3] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [4] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [5] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [6] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [7] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] (II) Inactive PCI resource ranges: [0] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [1] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [2] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [3] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [4] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [5] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [6] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [7] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] (II) Inactive PCI resource ranges after removing overlaps: [0] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [5] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [6] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [7] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) [8] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [9] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [10] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [11] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [12] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [13] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [14] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] (II) LoadModule: "vnc" (II) Loading /usr/lib/xorg/modules/extensions/libvnc.so (II) Module vnc: vendor="RealVNC Ltd" compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension VNC (II) LoadModule: "s3virge" (II) Loading /usr/lib/xorg/modules/drivers/s3virge_drv.so (II) Module s3virge: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.9.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0 (II) LoadModule: "kbd" (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.1.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) LoadModule: "mouse" (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.1.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) S3VIRGE: driver (version 1.9.1) for S3 ViRGE chipsets: virge, 86C325, virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2, 86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365, trio 3d/2x, 86C362, 86C368 (II) Primary Device is: PCI 00:08:0 (--) Chipset virge dx found (--) Chipset trio 3d/2x found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [5] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [6] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [7] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) [8] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [9] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [10] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [11] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [12] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [13] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [14] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [5] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [6] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [7] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) [8] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [9] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [10] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [11] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [12] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [13] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [14] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [5] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [6] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [7] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) [8] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [9] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [10] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [11] 1 0 0x000a0000 - 0x000affff (0x10000) MS[B] [12] 1 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [13] 1 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [16] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [17] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [18] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [19] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [20] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] [21] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [22] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] [23] 1 0 0x000003b0 - 0x000003bb (0xc) IS[B] [24] 1 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Setting vga for screen 1. (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/lib/xorg/modules/libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 7.1.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 1.0 (**) S3VIRGE(0): Depth 24, (--) framebuffer bpp 24 (==) S3VIRGE(0): RGB weight 888 (==) S3VIRGE(0): Default visual is TrueColor (**) S3VIRGE(0): Option "pci_burst" "on" (**) S3VIRGE(0): Option "pci_retry" "on" (**) S3VIRGE(0): Option: pci_burst - PCI burst read enabled (**) S3VIRGE(0): Option: pci_retry (==) S3VIRGE(0): Using HW Cursor (==) S3VIRGE(0): Using fb. (==) S3VIRGE(0): mx_cr3a_fix. (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/lib/xorg/modules/libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.1.0 ABI class: X.Org Video Driver, version 1.0 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib/xorg/modules/libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (II) S3VIRGE(0): initializing int10 (II) S3VIRGE(0): Primary V_BIOS segment is: 0xc000 (II) S3VIRGE(0): VESA BIOS detected (II) S3VIRGE(0): VESA VBE Version 1.2 (II) S3VIRGE(0): VESA VBE Total Mem: 2048 kB (II) S3VIRGE(0): VESA VBE OEM: S3 Incorporated. 86C375/86C385 (--) S3VIRGE(0): Chipset: "virge dx" (==) S3VIRGE(0): XVideo supported. (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/lib/xorg/modules/libddc.so (II) Module ddc: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (--) S3VIRGE(0): No DDC signal (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/lib/xorg/modules/libi2c.so (II) Module i2c: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.2.0 ABI class: X.Org Video Driver, version 1.0 (II) S3VIRGE(0): I2C bus "I2C bus" initialized. (II) S3VIRGE(0): I2C device "I2C bus:ddc2" registered at address 0xA0. (II) S3VIRGE(0): I2C device "I2C bus:ddc2" removed. (==) S3VIRGE(0): Using gamma correction (1.0, 1.0, 1.0) (--) S3VIRGE(0): videoram: 2048k (--) S3VIRGE(0): Detected current MCLK value of 45.102 MHz (II) S3VIRGE(0): Monitor0: Using hsync range of 31.50-80.00 kHz (II) S3VIRGE(0): Monitor0: Using vrefresh range of 30.00-100.00 Hz (II) S3VIRGE(0): Clock range: 10.00 to 270.00 MHz (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x960" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x960" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "640x480" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "640x512" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "896x672" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "896x672" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "928x696" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "928x696" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1152x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1152x864" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "576x432" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1280x720" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x720" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x720" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x720" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "700x525" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "700x525" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "700x525" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1440x900" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1600x1024" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "840x525" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "840x525" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x540" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x540" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(0): Not using default mode "1280x800" (insufficient memory for mode) (II) S3VIRGE(0): Not using mode "1024x768" (no mode of this name) (II) S3VIRGE(0): Not using default mode "960x600" (width too large for virtual size) (II) S3VIRGE(0): Not using default mode "832x624" (width too large for virtual size) (II) S3VIRGE(0): Not using default mode "960x540" (width too large for virtual size) (II) S3VIRGE(0): Not using default mode "960x540" (width too large for virtual size) (II) S3VIRGE(0): Not using default mode "840x525" (width too large for virtual size) (II) S3VIRGE(0): Not using default mode "840x525" (width too large for virtual size) (--) S3VIRGE(0): Virtual size is 800x600 (pitch 800) (**) S3VIRGE(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) S3VIRGE(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) S3VIRGE(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (II) S3VIRGE(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) S3VIRGE(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "800x600" 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) S3VIRGE(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) S3VIRGE(0): Default mode "700x525": 72.5 MHz, 76.5 kHz, 70.1 Hz (D) (II) S3VIRGE(0): Modeline "700x525" 72.53 700 748 824 948 525 525 527 546 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "700x525": 75.5 MHz, 77.0 kHz, 70.0 Hz (D) (II) S3VIRGE(0): Modeline "700x525" 75.50 700 732 828 980 525 525 527 550 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "700x525" 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D) (II) S3VIRGE(0): Modeline "640x512" 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "640x512" 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "720x450": 53.2 MHz, 55.9 kHz, 59.9 Hz (D) (II) S3VIRGE(0): Modeline "720x450" 53.25 720 760 836 952 450 451 454 467 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) S3VIRGE(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (**) S3VIRGE(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) S3VIRGE(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (**) S3VIRGE(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (II) S3VIRGE(0): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (**) S3VIRGE(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) S3VIRGE(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) S3VIRGE(0): Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "640x480" 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (II) S3VIRGE(0): Modeline "720x400" 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (**) S3VIRGE(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) S3VIRGE(0): Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (**) S3VIRGE(0): Default mode "640x400": 61.7 MHz, 71.4 kHz, 85.0 Hz (D) (II) S3VIRGE(0): Modeline "640x400" 61.69 640 684 752 864 400 400 402 420 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x400": 53.6 MHz, 62.6 kHz, 75.1 Hz (D) (II) S3VIRGE(0): Modeline "640x400" 53.60 640 680 748 856 400 400 402 417 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x400": 49.4 MHz, 58.3 kHz, 70.1 Hz (D) (II) S3VIRGE(0): Modeline "640x400" 49.45 640 676 744 848 400 400 402 416 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x400": 41.7 MHz, 49.7 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "640x400" 41.73 640 672 740 840 400 400 402 414 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "576x432": 60.8 MHz, 77.5 kHz, 85.2 Hz (D) (II) S3VIRGE(0): Modeline "576x432" 60.75 576 608 672 784 432 432 434 455 doublescan +hsync -vsync (**) S3VIRGE(0): Default mode "576x432": 59.8 MHz, 77.1 kHz, 85.1 Hz (D) (II) S3VIRGE(0): Modeline "576x432" 59.83 576 612 676 776 432 432 434 453 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D) (II) S3VIRGE(0): Modeline "576x432" 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "576x432": 52.5 MHz, 67.6 kHz, 75.0 Hz (D) (II) S3VIRGE(0): Modeline "576x432" 52.49 576 612 676 776 432 432 434 451 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "576x432": 48.4 MHz, 63.0 kHz, 70.0 Hz (D) (II) S3VIRGE(0): Modeline "576x432" 48.38 576 612 672 768 432 432 434 450 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "576x432": 40.8 MHz, 53.7 kHz, 60.1 Hz (D) (II) S3VIRGE(0): Modeline "576x432" 40.81 576 608 668 760 432 432 434 447 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x384": 59.3 MHz, 68.6 kHz, 85.1 Hz (D) (II) S3VIRGE(0): Modeline "640x384" 59.27 640 684 752 864 384 384 386 403 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x384": 51.5 MHz, 60.2 kHz, 75.0 Hz (D) (II) S3VIRGE(0): Modeline "640x384" 51.49 640 680 748 856 384 384 386 401 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x384": 47.5 MHz, 56.0 kHz, 70.0 Hz (D) (II) S3VIRGE(0): Modeline "640x384" 47.49 640 676 744 848 384 384 386 400 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x384": 40.1 MHz, 47.7 kHz, 60.1 Hz (D) (II) S3VIRGE(0): Modeline "640x384" 40.07 640 672 740 840 384 384 386 397 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x360": 55.0 MHz, 64.3 kHz, 85.0 Hz (D) (II) S3VIRGE(0): Modeline "640x360" 55.01 640 680 748 856 360 360 362 378 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x360": 47.8 MHz, 56.4 kHz, 75.0 Hz (D) (II) S3VIRGE(0): Modeline "640x360" 47.83 640 676 744 848 360 360 362 376 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x360": 44.5 MHz, 52.5 kHz, 70.0 Hz (D) (II) S3VIRGE(0): Modeline "640x360" 44.52 640 676 744 848 360 360 362 375 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x360": 37.2 MHz, 44.8 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "640x360" 37.24 640 668 736 832 360 360 362 373 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) S3VIRGE(0): Modeline "640x350" 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (**) S3VIRGE(0): Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D) (II) S3VIRGE(0): Modeline "576x384" 32.50 576 589 657 736 384 385 388 403 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "512x384": 47.2 MHz, 68.7 kHz, 85.0 Hz (D) (II) S3VIRGE(0): Modeline "512x384" 47.25 512 536 584 688 384 384 386 404 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "512x384": 39.4 MHz, 60.1 kHz, 75.1 Hz (D) (II) S3VIRGE(0): Modeline "512x384" 39.40 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D) (II) S3VIRGE(0): Modeline "512x384" 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "512x384" 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "512x384": 22.4 MHz, 35.5 kHz, 86.6 Hz (D) (II) S3VIRGE(0): Modeline "512x384" 22.45 512 516 604 632 384 384 388 409 interlace doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D) (II) S3VIRGE(0): Modeline "416x312" 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D) (II) S3VIRGE(0): Modeline "400x300" 28.15 400 416 448 524 300 300 302 315 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D) (II) S3VIRGE(0): Modeline "400x300" 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D) (II) S3VIRGE(0): Modeline "400x300" 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D) (II) S3VIRGE(0): Modeline "400x300" 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D) (II) S3VIRGE(0): Modeline "400x300" 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D) (II) S3VIRGE(0): Modeline "320x240" 18.00 320 348 376 416 240 240 242 254 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D) (II) S3VIRGE(0): Modeline "320x240" 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D) (II) S3VIRGE(0): Modeline "320x240" 15.75 320 332 352 416 240 244 245 260 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) S3VIRGE(0): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (**) S3VIRGE(0): Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D) (II) S3VIRGE(0): Modeline "360x200" 17.75 360 378 414 468 200 200 202 223 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) S3VIRGE(0): Modeline "320x200" 15.75 320 336 368 416 200 200 202 222 doublescan -hsync +vsync (**) S3VIRGE(0): Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) S3VIRGE(0): Modeline "320x175" 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync (==) S3VIRGE(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules/libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/lib/xorg/modules/libxaa.so (II) Module xaa: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.2.0 ABI class: X.Org Video Driver, version 1.0 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/lib/xorg/modules/libramdac.so (II) Module ramdac: vendor="X.Org Foundation" compiled for 7.1.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 1.0 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Reloading /usr/lib/xorg/modules/libvgahw.so (II) S3VIRGE(1): Creating default Display subsection in Screen section "Screen1" for depth/fbbpp 24/24 (**) S3VIRGE(1): Depth 24, (--) framebuffer bpp 24 (==) S3VIRGE(1): RGB weight 888 (==) S3VIRGE(1): Default visual is TrueColor (**) S3VIRGE(1): Option "pci_burst" "on" (**) S3VIRGE(1): Option "pci_retry" "on" (**) S3VIRGE(1): Option: pci_burst - PCI burst read enabled (**) S3VIRGE(1): Option: pci_retry (==) S3VIRGE(1): Using HW Cursor (==) S3VIRGE(1): Using fb. (==) S3VIRGE(1): mx_cr3a_fix. (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Reloading /usr/lib/xorg/modules/libvbe.so (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib/xorg/modules/libint10.so (II) S3VIRGE(1): initializing int10 (II) Attempted to read BIOS 64KB from /sys/bus/pci/devices/0000:01:00.0/rom: got 32KB (II) S3VIRGE(1): VESA BIOS detected (II) S3VIRGE(1): VESA VBE Version 2.0 (II) S3VIRGE(1): VESA VBE Total Mem: 4096 kB (II) S3VIRGE(1): VESA VBE OEM: S3 Incorporated. 86C362 (II) S3VIRGE(1): VESA VBE OEM Software Rev: 1.1 (II) S3VIRGE(1): VESA VBE OEM Vendor: S3 Incorporated. (II) S3VIRGE(1): VESA VBE OEM Product: Trio3D/2X (II) S3VIRGE(1): VESA VBE OEM Product Rev: Rev C (--) S3VIRGE(1): Chipset: "trio 3d/2x" (==) S3VIRGE(1): XVideo supported. (II) S3VIRGE(1): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) S3VIRGE(1): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/lib/xorg/modules/libddc.so (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/lib/xorg/modules/libddc.so (II) S3VIRGE(1): VESA VBE DDC supported (II) S3VIRGE(1): VESA VBE DDC Level 2 (II) S3VIRGE(1): VESA VBE DDC transfer in appr. 1 sec. (II) S3VIRGE(1): VESA VBE DDC read successfully (II) S3VIRGE(1): Manufacturer: TAT Model: 31d7 Serial#: 630247 (II) S3VIRGE(1): Year: 2001 Week: 52 (II) S3VIRGE(1): EDID Version: 1.3 (II) S3VIRGE(1): Analog Display Input, Input Voltage Level: 0.700/0.700 V (II) S3VIRGE(1): Sync: Separate (II) S3VIRGE(1): Max H-Image Size [cm]: horiz.: 32 vert.: 24 (II) S3VIRGE(1): Gamma: 2.77 (II) S3VIRGE(1): DPMS capabilities: StandBy Suspend Off; RGB/Color Display (II) S3VIRGE(1): First detailed timing is preferred mode (II) S3VIRGE(1): redX: 0.630 redY: 0.340 greenX: 0.280 greenY: 0.601 (II) S3VIRGE(1): blueX: 0.145 blueY: 0.061 whiteX: 0.281 whiteY: 0.311 (II) S3VIRGE(1): Supported VESA Video Modes: (II) S3VIRGE(1): 720x400@70Hz (II) S3VIRGE(1): 640x480@60Hz (II) S3VIRGE(1): 640x480@75Hz (II) S3VIRGE(1): 800x600@60Hz (II) S3VIRGE(1): 800x600@75Hz (II) S3VIRGE(1): 1024x768@60Hz (II) S3VIRGE(1): 1024x768@70Hz (II) S3VIRGE(1): 1024x768@75Hz (II) S3VIRGE(1): Manufacturer's mask: 0 (II) S3VIRGE(1): Supported Future Video Modes: (II) S3VIRGE(1): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833 (II) S3VIRGE(1): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) S3VIRGE(1): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881 (II) S3VIRGE(1): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 (II) S3VIRGE(1): Supported additional Video Mode: (II) S3VIRGE(1): clock: 94.5 MHz Image Size: 306 x 230 mm (II) S3VIRGE(1): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376 h_border: 0 (II) S3VIRGE(1): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808 v_border: 0 (II) S3VIRGE(1): Ranges: V min: 50 V max: 120 Hz, H min: 30 H max: 70 kHz, (II) S3VIRGE(1): Serial No: 80H152630247 (II) S3VIRGE(1): Monitor name: TATUNG C7ES (II) S3VIRGE(1): EDID (in hex): (II) S3VIRGE(1): 00ffffffffffff005034d731e79d0900 (II) S3VIRGE(1): 340b0103682018b1ea4f22a157479925 (II) S3VIRGE(1): 0f484fa54e0031594559615981800101 (II) S3VIRGE(1): 010101010101ea240060410028303060 (II) S3VIRGE(1): 130032e61000001e000000fd0032781e (II) S3VIRGE(1): 46ff000a202020202020000000ff0038 (II) S3VIRGE(1): 30483135323633303234370a000000fc (II) S3VIRGE(1): 00544154554e4720433745530a200007 (II) S3VIRGE(1): Using hsync ranges from config file (II) S3VIRGE(1): Using vrefresh ranges from config file (II) S3VIRGE(1): Printing DDC gathered Modelines: (II) S3VIRGE(1): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (II) S3VIRGE(1): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (II) S3VIRGE(1): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (II) S3VIRGE(1): Modeline "720x400" 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (II) S3VIRGE(1): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (II) S3VIRGE(1): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (II) S3VIRGE(1): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (II) S3VIRGE(1): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (II) S3VIRGE(1): Modeline "640x480" 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (II) S3VIRGE(1): Modeline "800x600" 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (II) S3VIRGE(1): Modeline "1024x768" 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (II) S3VIRGE(1): Modeline "1280x1024" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync (II) S3VIRGE(1): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (==) S3VIRGE(1): Using gamma correction (1.0, 1.0, 1.0) (--) S3VIRGE(1): videoram: 4096k (--) S3VIRGE(1): Detected current MCLK value of 100.227 MHz (II) S3VIRGE(1): Monitor1: Using hsync range of 31.50-80.00 kHz (II) S3VIRGE(1): Monitor1: Using vrefresh range of 30.00-100.00 Hz (II) S3VIRGE(1): Estimated virtual size for aspect ratio 1.3333 is 1024x768 (II) S3VIRGE(1): Clock range: 10.00 to 270.00 MHz (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x960" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x960" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "640x480" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1280x1024" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x1024" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x1024" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "640x512" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1600x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "800x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1792x1344" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "896x672" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1792x1344" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "896x672" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1856x1392" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "928x696" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1856x1392" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "928x696" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1152x768" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1152x864" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "576x432" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1280x720" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x720" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x720" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x720" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x768" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x768" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x768" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1280x768" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "700x525" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "700x525" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1400x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "700x525" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1440x900" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "1600x1024" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "840x525" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1680x1050" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "840x525" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x540" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1080" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x540" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1200" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x600" (hsync out of range) (II) S3VIRGE(1): Not using default mode "1920x1440" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "960x720" (hsync out of range) (II) S3VIRGE(1): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1024x768" (hsync out of range) (II) S3VIRGE(1): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1024x768" (hsync out of range) (II) S3VIRGE(1): Not using default mode "2048x1536" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1024x768" (hsync out of range) (II) S3VIRGE(1): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using default mode "2560x1600" (insufficient memory for mode) (II) S3VIRGE(1): Not using default mode "1280x800" (width too large for virtual size) (II) S3VIRGE(1): Not using driver mode "1280x1024" (width too large for virtual size) (--) S3VIRGE(1): Virtual size is 1024x768 (pitch 1024) (**) S3VIRGE(1): *Driver mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (II) S3VIRGE(1): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (**) S3VIRGE(1): *Driver mode "1024x768": 94.5 MHz, 68.7 kHz, 84.9 Hz (II) S3VIRGE(1): Modeline "1024x768" 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (**) S3VIRGE(1): *Driver mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz (II) S3VIRGE(1): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (**) S3VIRGE(1): *Driver mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz (II) S3VIRGE(1): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (**) S3VIRGE(1): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz (II) S3VIRGE(1): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (**) S3VIRGE(1): *Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (II) S3VIRGE(1): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (**) S3VIRGE(1): *Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz (II) S3VIRGE(1): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (**) S3VIRGE(1): *Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz (II) S3VIRGE(1): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (**) S3VIRGE(1): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz (II) S3VIRGE(1): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (**) S3VIRGE(1): *Default mode "1024x768": 44.9 MHz, 35.5 kHz, 86.9 Hz (I) (II) S3VIRGE(1): Modeline "1024x768" 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (**) S3VIRGE(1): *Default mode "960x600": 96.6 MHz, 74.5 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "960x600" 96.58 960 1024 1128 1296 600 600 602 621 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz (II) S3VIRGE(1): Modeline "832x624" 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (**) S3VIRGE(1): *Default mode "960x540": 102.1 MHz, 78.8 kHz, 70.0 Hz (D) (II) S3VIRGE(1): Modeline "960x540" 102.12 960 1028 1128 1296 540 541 544 563 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "960x540": 86.5 MHz, 67.2 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "960x540" 86.50 960 1024 1124 1288 540 541 544 560 doublescan -hsync +vsync (**) S3VIRGE(1): *Driver mode "800x600": 56.8 MHz, 53.7 kHz, 84.9 Hz (II) S3VIRGE(1): Modeline "800x600" 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (**) S3VIRGE(1): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) S3VIRGE(1): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (**) S3VIRGE(1): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) S3VIRGE(1): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) S3VIRGE(1): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) S3VIRGE(1): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (**) S3VIRGE(1): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) S3VIRGE(1): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (**) S3VIRGE(1): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (II) S3VIRGE(1): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (**) S3VIRGE(1): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) S3VIRGE(1): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) S3VIRGE(1): *Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "800x600" 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) S3VIRGE(1): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) S3VIRGE(1): *Default mode "840x525": 87.0 MHz, 76.6 kHz, 69.9 Hz (D) (II) S3VIRGE(1): Modeline "840x525" 87.00 840 900 988 1136 525 526 529 548 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "840x525": 73.1 MHz, 65.3 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "840x525" 73.12 840 892 980 1120 525 526 529 544 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "700x525": 72.5 MHz, 76.5 kHz, 70.1 Hz (D) (II) S3VIRGE(1): Modeline "700x525" 72.53 700 748 824 948 525 525 527 546 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "700x525": 75.5 MHz, 77.0 kHz, 70.0 Hz (D) (II) S3VIRGE(1): Modeline "700x525" 75.50 700 732 828 980 525 525 527 550 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "700x525" 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D) (II) S3VIRGE(1): Modeline "640x512" 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "640x512" 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "720x450": 53.2 MHz, 55.9 kHz, 59.9 Hz (D) (II) S3VIRGE(1): Modeline "720x450" 53.25 720 760 836 952 450 451 454 467 doublescan -hsync +vsync (**) S3VIRGE(1): *Driver mode "640x480": 35.0 MHz, 42.9 kHz, 84.6 Hz (II) S3VIRGE(1): Modeline "640x480" 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (**) S3VIRGE(1): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) S3VIRGE(1): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (**) S3VIRGE(1): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) S3VIRGE(1): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) S3VIRGE(1): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) S3VIRGE(1): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (**) S3VIRGE(1): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) S3VIRGE(1): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (**) S3VIRGE(1): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (II) S3VIRGE(1): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (**) S3VIRGE(1): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) S3VIRGE(1): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) S3VIRGE(1): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "640x480" 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (**) S3VIRGE(1): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz (II) S3VIRGE(1): Modeline "720x400" 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (**) S3VIRGE(1): *Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (II) S3VIRGE(1): Modeline "720x400" 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (**) S3VIRGE(1): *Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) S3VIRGE(1): Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (**) S3VIRGE(1): *Default mode "640x400": 61.7 MHz, 71.4 kHz, 85.0 Hz (D) (II) S3VIRGE(1): Modeline "640x400" 61.69 640 684 752 864 400 400 402 420 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x400": 53.6 MHz, 62.6 kHz, 75.1 Hz (D) (II) S3VIRGE(1): Modeline "640x400" 53.60 640 680 748 856 400 400 402 417 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x400": 49.4 MHz, 58.3 kHz, 70.1 Hz (D) (II) S3VIRGE(1): Modeline "640x400" 49.45 640 676 744 848 400 400 402 416 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x400": 41.7 MHz, 49.7 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "640x400" 41.73 640 672 740 840 400 400 402 414 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "576x432": 60.8 MHz, 77.5 kHz, 85.2 Hz (D) (II) S3VIRGE(1): Modeline "576x432" 60.75 576 608 672 784 432 432 434 455 doublescan +hsync -vsync (**) S3VIRGE(1): *Default mode "576x432": 59.8 MHz, 77.1 kHz, 85.1 Hz (D) (II) S3VIRGE(1): Modeline "576x432" 59.83 576 612 676 776 432 432 434 453 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D) (II) S3VIRGE(1): Modeline "576x432" 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "576x432": 52.5 MHz, 67.6 kHz, 75.0 Hz (D) (II) S3VIRGE(1): Modeline "576x432" 52.49 576 612 676 776 432 432 434 451 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "576x432": 48.4 MHz, 63.0 kHz, 70.0 Hz (D) (II) S3VIRGE(1): Modeline "576x432" 48.38 576 612 672 768 432 432 434 450 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "576x432": 40.8 MHz, 53.7 kHz, 60.1 Hz (D) (II) S3VIRGE(1): Modeline "576x432" 40.81 576 608 668 760 432 432 434 447 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x384": 59.3 MHz, 68.6 kHz, 85.1 Hz (D) (II) S3VIRGE(1): Modeline "640x384" 59.27 640 684 752 864 384 384 386 403 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x384": 51.5 MHz, 60.2 kHz, 75.0 Hz (D) (II) S3VIRGE(1): Modeline "640x384" 51.49 640 680 748 856 384 384 386 401 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x384": 47.5 MHz, 56.0 kHz, 70.0 Hz (D) (II) S3VIRGE(1): Modeline "640x384" 47.49 640 676 744 848 384 384 386 400 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x384": 40.1 MHz, 47.7 kHz, 60.1 Hz (D) (II) S3VIRGE(1): Modeline "640x384" 40.07 640 672 740 840 384 384 386 397 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x360": 55.0 MHz, 64.3 kHz, 85.0 Hz (D) (II) S3VIRGE(1): Modeline "640x360" 55.01 640 680 748 856 360 360 362 378 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x360": 47.8 MHz, 56.4 kHz, 75.0 Hz (D) (II) S3VIRGE(1): Modeline "640x360" 47.83 640 676 744 848 360 360 362 376 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x360": 44.5 MHz, 52.5 kHz, 70.0 Hz (D) (II) S3VIRGE(1): Modeline "640x360" 44.52 640 676 744 848 360 360 362 375 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x360": 37.2 MHz, 44.8 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "640x360" 37.24 640 668 736 832 360 360 362 373 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) S3VIRGE(1): Modeline "640x350" 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (**) S3VIRGE(1): *Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D) (II) S3VIRGE(1): Modeline "576x384" 32.50 576 589 657 736 384 385 388 403 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "512x384": 47.2 MHz, 68.7 kHz, 85.0 Hz (D) (II) S3VIRGE(1): Modeline "512x384" 47.25 512 536 584 688 384 384 386 404 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "512x384": 39.4 MHz, 60.1 kHz, 75.1 Hz (D) (II) S3VIRGE(1): Modeline "512x384" 39.40 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D) (II) S3VIRGE(1): Modeline "512x384" 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D) (II) S3VIRGE(1): Modeline "512x384" 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "512x384": 22.4 MHz, 35.5 kHz, 86.6 Hz (D) (II) S3VIRGE(1): Modeline "512x384" 22.45 512 516 604 632 384 384 388 409 interlace doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D) (II) S3VIRGE(1): Modeline "416x312" 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D) (II) S3VIRGE(1): Modeline "400x300" 28.15 400 416 448 524 300 300 302 315 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D) (II) S3VIRGE(1): Modeline "400x300" 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D) (II) S3VIRGE(1): Modeline "400x300" 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D) (II) S3VIRGE(1): Modeline "400x300" 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D) (II) S3VIRGE(1): Modeline "400x300" 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (**) S3VIRGE(1): *Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D) (II) S3VIRGE(1): Modeline "320x240" 18.00 320 348 376 416 240 240 242 254 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D) (II) S3VIRGE(1): Modeline "320x240" 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D) (II) S3VIRGE(1): Modeline "320x240" 15.75 320 332 352 416 240 244 245 260 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) S3VIRGE(1): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (**) S3VIRGE(1): *Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D) (II) S3VIRGE(1): Modeline "360x200" 17.75 360 378 414 468 200 200 202 223 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) S3VIRGE(1): Modeline "320x200" 15.75 320 336 368 416 200 200 202 222 doublescan -hsync +vsync (**) S3VIRGE(1): *Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) S3VIRGE(1): Modeline "320x175" 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync (**) S3VIRGE(1): Display dimensions: (320, 240) mm (**) S3VIRGE(1): DPI set to (81, 81) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Reloading /usr/lib/xorg/modules/libfb.so (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Reloading /usr/lib/xorg/modules/libxaa.so (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Reloading /usr/lib/xorg/modules/libramdac.so (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? Yes, I do. (II) LoadModule: "rac" (II) Loading /usr/lib/xorg/modules/librac.so (II) Module rac: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (II) resource ranges after preInit: [0] 1 0 0xd0000000 - 0xd3ffffff (0x4000000) MS[B] [1] 0 0 0xd8000000 - 0xdbffffff (0x4000000) MS[B] [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xdd800000 - 0xdd80007f (0x80) MX[B] [7] -1 0 0xdd000000 - 0xdcffffff (0x0) MX[B]O [8] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX[B](B) [9] -1 0 0xd0000000 - 0xd3ffffff (0x4000000) MX[B](B) [10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [13] 1 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [14] 1 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [15] 1 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [18] -1 0 0x0000e000 - 0x0000e07f (0x80) IX[B] [19] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [20] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B] [21] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B] [22] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[B] [23] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [24] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) [25] 1 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [26] 1 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (==) S3VIRGE(0): Write-combining range (0xd8000000,0x200000) (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (**) S3VIRGE(0): Using FB (II) S3VIRGE(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles CPU to Screen color expansion Solid Horizontal and Vertical Lines Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 12 128x128 slots (==) S3VIRGE(0): Backing store disabled (==) S3VIRGE(0): Silken mouse enabled (**) Option "dpms" (**) S3VIRGE(0): DPMS enabled (II) S3VIRGE(0): Using overlay video (WW) S3VIRGE(0): Option "UserPasswdVerifier" is not used (WW) S3VIRGE(0): Option "PasswordFile" is not used (WW) S3VIRGE(0): Option "httpd" is not used (WW) S3VIRGE(0): Option "ClientWaitTimeMillis" is not used (WW) S3VIRGE(0): Option "deferUpdate" is not used (WW) S3VIRGE(0): Option "DisconnectClients" is not used (WW) S3VIRGE(0): Option "AllwaysShared" is not used (WW) S3VIRGE(0): Option "IdleTimeout" is not used (WW) S3VIRGE(0): Option "desktop" is not used (==) RandR enabled (==) S3VIRGE(1): Write-combining range (0xd0000000,0x400000) (II) S3VIRGE(1): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) S3VIRGE(1): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (**) S3VIRGE(1): Using FB (II) S3VIRGE(1): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Solid Horizontal and Vertical Lines Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 16 128x128 slots 4 256x256 slots (==) S3VIRGE(1): Backing store disabled (==) S3VIRGE(1): Silken mouse enabled (**) Option "dpms" (**) S3VIRGE(1): DPMS enabled (II) S3VIRGE(1): Using overlay video (WW) S3VIRGE(1): Option "UserPasswdVerifier" is not used (WW) S3VIRGE(1): Option "PasswordFile" is not used (WW) S3VIRGE(1): Option "httpd" is not used (WW) S3VIRGE(1): Option "ClientWaitTimeMillis" is not used (WW) S3VIRGE(1): Option "deferUpdate" is not used (WW) S3VIRGE(1): Option "DisconnectClients" is not used (WW) S3VIRGE(1): Option "AllwaysShared" is not used (WW) S3VIRGE(1): Option "IdleTimeout" is not used (WW) S3VIRGE(1): Option "desktop" is not used (==) RandR enabled (II) Entity 0 shares no resources (II) Entity 1 shares no resources (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 XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (**) Option "CoreKeyboard" (**) Keyboard0: Core Keyboard (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "es" (**) Keyboard0: XkbLayout: "es" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (WW) <default pointer>: No Device specified, looking for one... (II) <default pointer>: Setting Device option to "/dev/input/mice" (--) <default pointer>: Device: "/dev/input/mice" (==) <default pointer>: Protocol: "Auto" (**) Option "CorePointer" (**) <default pointer>: Core Pointer (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50 (**) <default pointer>: ZAxisMapping: buttons 4 and 5 (**) <default pointer>: Buttons: 9 (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (--) <default pointer>: PnP-detected protocol: "ExplorerPS/2" (II) <default pointer>: ps2EnableDataReporting: succeeded Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80e3fe1] 1: [0x6ed420] 2: /usr/lib/xorg/modules/libxaa.so(XAARemoveAreaCallback+0x17) [0x8f1ae7] 3: /usr/lib/xorg/modules/libxaa.so [0x8d57bd] 4: /usr/bin/Xorg [0x8104b19] 5: /usr/bin/Xorg [0x815b577] 6: /usr/bin/Xorg [0x8156810] 7: /usr/lib/xorg/modules/extensions/libvnc.so [0x2cd32e] 8: /usr/bin/Xorg(ValidateGC+0x25) [0x80961d5] 9: /usr/bin/Xorg [0x815b6ff] 10: /usr/bin/Xorg [0x8156810] 11: /usr/lib/xorg/modules/extensions/libvnc.so [0x2cd32e] 12: /usr/bin/Xorg(ValidateGC+0x25) [0x80961d5] 13: /usr/bin/Xorg(ProcPolyFillRectangle+0xb6) [0x8084526] 14: /usr/bin/Xorg(Dispatch+0x19a) [0x808811a] 15: /usr/bin/Xorg(main+0x485) [0x806fa95] 16: /lib/libc.so.6(__libc_start_main+0xdc) [0xb50dec] 17: /usr/bin/Xorg(FontFileCompleteXLFD+0x1e5) [0x806ed91] Fatal server error: Caught signal 11. Server aborting (II) Screen 0 shares mem & io resources (II) Screen 1 shares mem & io resources ================================================================= This is the /var/log/gdm/\:0.log.1: X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: Linux 2.6.9-42.0.3.ELsmp i686 Red Hat, Inc. Current Operating System: Linux acpc08.arcoscom 2.6.18-53.1.4.1.el5_ArcosCom #1 SMP Wed Dec 5 08:29:14 CET 2007 i686 Build Date: 10 November 2007 Build ID: xorg-x11-server 1.1.1-48.26.el5 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 27 09:56:31 2007 (==) Using config file: "/etc/X11/xorg.conf" Thu Dec 27 09:56:36 2007 vncext: VNC extension running! vncext: Listening for VNC connections on port 5900 vncext: Listening for HTTP connections on port 5800 vncext: created VNC server for screen 0 vncext: Listening for VNC connections on port 6900 vncext: Listening for HTTP connections on port 6800 vncext: created VNC server for screen 1 Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80e3fe1] 1: [0x6ed420] 2: /usr/lib/xorg/modules/libxaa.so(XAARemoveAreaCallback+0x17) [0x8f1ae7] 3: /usr/lib/xorg/modules/libxaa.so [0x8d57bd] 4: /usr/bin/Xorg [0x8104b19] 5: /usr/bin/Xorg [0x815b577] 6: /usr/bin/Xorg [0x8156810] 7: /usr/lib/xorg/modules/extensions/libvnc.so [0x2cd32e] 8: /usr/bin/Xorg(ValidateGC+0x25) [0x80961d5] 9: /usr/bin/Xorg [0x815b6ff] 10: /usr/bin/Xorg [0x8156810] 11: /usr/lib/xorg/modules/extensions/libvnc.so [0x2cd32e] 12: /usr/bin/Xorg(ValidateGC+0x25) [0x80961d5] 13: /usr/bin/Xorg(ProcPolyFillRectangle+0xb6) [0x8084526] 14: /usr/bin/Xorg(Dispatch+0x19a) [0x808811a] 15: /usr/bin/Xorg(main+0x485) [0x806fa95] 16: /lib/libc.so.6(__libc_start_main+0xdc) [0xb50dec] 17: /usr/bin/Xorg(FontFileCompleteXLFD+0x1e5) [0x806ed91] Fatal server error: Caught signal 11. Server aborting

2 2

Problem accessing my webmail
by Jun Salen 10 Jan '08

10 Jan '08

Hi, I just finished replacing my mail server with the new one from CentOS 4.6 to CentOS 5.1. The mail are running smoothly with user able to send/receive mail from Outlook using IMAP or POP3 and Webmail locally. My problem is that when I am outside my network like in home, I cannot able to access the Webmail. In my prior mail server, it is ok. Is there anybody here have clues for me to look for? DNSReport states that my mail server was accessable. Please help. Thanks in advance for your help. junji aisalen.wordpress.com Linux Registered User #253162 CentOS User Send instant messages to your online friends http://uk.messenger.yahoo.com

2 1

Slightly OT: Dual-booting two Linux dists
by Bart Schaefer 10 Jan '08

10 Jan '08

I'd like to set up a machine to dual-boot Ubuntu and CentOS5. Any problems foreseen with this? I'm mostly worried about disk labeling; they each need their own /boot and / filesystems. (Or do they need separate /boot partitions? Obviously there's an issue with boot.* and *.b and what System.map is symlink'd to, etc., but maybe there's a way to work around that.)

5 8

IAXmodem 1.0
by Robert Moskowitz 10 Jan '08

10 Jan '08

Has anyone built an rpm for Centos 5 and IAXmodem 1.0? I need it, and I thought to ask before struggling to get it. The Trixbox people are saying a couple of weeks still on their side...

2 2

Zimbra: To our CentOS users
by Jun Salen 10 Jan '08

10 Jan '08

Hi, There is a new annoucement in Zimbra site (http://www.zimbra.com/forums/announcements/14213-our-centos-users.html) in response to discussion started by Johnny Hughes retorting the first announcement made by Zimbra not supporting CentOS (http://www.zimbra.com/forums/installation/14144-centos-not-supported.html) For your info. junji aisalen.wordpress.com Linux Registered User #253162 Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0

Anyone know of complete hardware solution based IDE Raid Controllers?
by Brett Davidson 10 Jan '08

10 Jan '08

Years ago Accusys made an IDE raid controller that presented itself as one drive to the BIOS, making the unit completely OS agnostic. Anything like that out there, anymore? Cheers, Brett.

5 4

building internal yum / rpmforge repo
by Rogelio 10 Jan '08

10 Jan '08

I am looking to create an internal yum repository on my LAN in order to save on having to constantly go to the internet to download new packages. Where might I look (or what might I search for) to get going in the right direction? (I googled, but I cannot seem to find a good answer. I'm guessing that I'll just need to sync the main RHEL repo, as well as the RPMForge one?)

2 2

Re: [CentOS] Anyone know of complete hardware solution based IDE Raid Controllers?
by Les Bell 10 Jan '08

10 Jan '08

Brett Davidson <brett(a)net24.co.nz> wrote: >> Years ago Accusys made an IDE raid controller that presented itself as one drive to the BIOS, making the unit completely OS agnostic. Anything like that out there, anymore? << Dunno, but if you're desparate to get one, I still have an ACS-7500 IDE RAID kit, new in box, that I never used. It's just sitting on the shelf. Best, --- Les Bell, RHCE, CISSP [http://www.lesbell.com.au] Tel: +61 2 9451 1144 FreeWorldDialup: 800909

1 0

Re: [CentOS] tar bug in CentOS 4.6?
by David G. Miller 10 Jan '08

10 Jan '08

"Nicolas Sahlqvist" <nicco77(a)gmail.com> wrote: > First you have to figure out if the problem occurs in tar or gzip, do you > get the problem if you tar and then gzip or is it combined (make a none > compressed tar archive), in case no is the pipe somehow the problem, same > crash with tar -z option rather then piping to gzip? Finally you need to get > a stack trace why you need to set the core size limit above the default 0 > size with "ulimit -c unlimited" before running the command. You can now use > gdb to make a stack trace "gdb <path to exec file> <path to core file>" and > type where and type "where" in order to get a stack trace that you can > publish in a relevant forum for further examination by developers. > > > - Nicolas and John Hinton <webmaster(a)ew3d.com> wrote > Sounds like your tmp directory isn't big enough to handle the creation > of the tar file. I'm pretty sure it's stored there until it's created > and zipped. Then once done is moved to the destination. If you do a df > from the command line several times while running the script, you can > see if an area is filling up before completion. > > John Hinton When I checked the server this morning it had a kernel panic (in sendbackup) . I got it cleaned up and back running and tried again to recreate the problem. This time my tar command worked just fine (Nicholas, I'm using tar piped to gzip to mimic what amanda does). I tried it again and got a seg fault from a file that had just been tarred and gzipped with no problem. I fired it off again and got the seg fault from a different file. At this point I'm thinking I have an intermittent hardware problem. It just happened to seg fault twice on the same file when I tried it yesterday. After several runs, there appear to be certain files that I preferentially get the seg fault on if I rerun the backup several times. Sometimes it works; sometimes it seg faults. When it seg faults it's frequently on certain specific files. Kind of weird. Hopefully, it's nothing worse than the CPU fan has ingested too much cat hair (http://davenjudy.org/interests/pets/img011.jpeg.medium.jpeg) so the CPU is running hot. Thanks for the help. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

1 0

Log Monitoring Recomendation
by Joseph L. Casale 10 Jan '08

10 Jan '08

Given my experience in Linux is limited currently, what do you guys use to monitor logs such as 'messages' on your centos servers? I had a hardware failure that happened in between me manually looking (of course...). I would hope it might have a some features to email critical issues etc... Thanks! jlc

6 8

Xen clock drift
by Jack Bailey 10 Jan '08

10 Jan '08

Hello All, Consider a CentOS-5.1 Xen server (2.6.18-53.1.4.el5xen) hosting two domains running CentOS-5.1 (2.6.18-53.1.4.el5). One domain has a fairly accurate clock, the other domain has a clock that gains ungodly amounts of time, roughly one minute every two or three minutes. For a fix, one suggestion is to run this command in DomU: echo 1 > /proc/sys/xen/independent_wallclock This didn't change anything. As an experiment, I wrote a script to call ntpd -q, sleep 60, and repeat indefinitely. Here are a couple of snippets of output: goodclock# ksh ./xenclockdrift ntpd: time slew +0.001211s ntpd: time slew +0.001200s ntpd: time slew +0.001855s ntpd: time slew +0.001532s ntpd: time slew +0.001603s ntpd: time slew +0.001320s ntpd: time slew +0.001931s badclock# ksh ./xenclockdrift ntpd: time slew -0.000193s ntpd: time set -57.356377s ntpd: time slew +0.002352s ntpd: time slew +0.003018s ntpd: time set -57.417488s ntpd: time slew +0.012089s ntpd: time slew -0.000985s These domains are fully virtualized and set up identically, except "badclock" is allocated two processors versus one processor for "goodclock". DomU's clock is running normally. Anyone know what's going or know how to fix it? Jack

6 11

After 4.6 update: CUPS (via Samba): "'/printers/printers' no good!"
by Steve Snyder 10 Jan '08

10 Jan '08

Since updating from 4.5 to 4.6 yesterday, I am getting a lot of CUPS errors. The error.log file is filling up with these messages: get_printer_attrs: resource name '/printers/printers' no good! And the access.log seems to be being polled often too, even in the absence of any print jobs submitted. On my network the CUPS-handled printer is exported from Samba. Given that the Samba RPMs were among those upgraded, I have to wonder what printing-related changes might have occurred. The hal-cups-utils was also updated in the course of the upgrade. I also notice that CUP's ppds.dat and cupsd.conf files have modification timestamp from around the time I did the upgrade. Any advice as to how to fix whatever was broken in the course of doing the upgrade? Thanks.

4 4

Switching To Raid1
by Matt 10 Jan '08

10 Jan '08

I have this ASUS M2NBP-VM motherboard http://tinyurl.com/3xby3h running CentOS 4.4 as a web/email server. It has a 500Gb SATA2 drive with about 32Gb in use. The motherboard supports hardware raid. Is there a way to switch to RAID1 without reinstalling or loosing any data? Also, if I am running raid how do I know if there is a failure on one of the drives anyway? Is hardware RAID1 a good idea? Matt

4 3

CentOS and GCC Question
by Clint Dilks 09 Jan '08

09 Jan '08

Hi People I am trying to build a piece of software from source in this case aide 0.13.1 using this config line ./configure --with-zlib --with-selinux. The configure step completes but there is a Warning that concerns me. This is taken from config.log configure:9809: checking for mhash_get_block_size in -lmhash configure:9844: gcc -o conftest -g -O2 -static -static conftest.c -lmhash -lz >&5 /usr/bin/ld: cannot find -lmhash collect2: ld returned 1 exit status The machine I am trying to do this build on is Cent0S 5 with the latest updates. It didn't originally have gcc installed so I have installed that and mhash and mhash-devel are also installed. I know I can ignore the warning and just carry on, or that there are already aide RPMS. But I am doing this as an exercise for myself as I want to up skill in RPM creation. So if anyone can offer incite into why this is happening it would be appreciated. rpm -qa | grep gcc libgcc-4.1.2-14.el5 gcc-4.1.2-14.el5 rpm -qa | grep mhash mhash-0.9.9-1.el5.centos mhash-devel-0.9.9-1.el5.centos Please let me know any other information that would be useful, have a nice day :)

4 4

CentOS-announce Digest, Vol 35, Issue 1
by centos-announce-request＠centos.org 09 Jan '08

09 Jan '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2008:0003 Moderate CentOS 3 ia64 e2fsprogs - security update (Pasi Pirhonen) 2. CESA-2008:0003 Moderate CentOS 3 s390(x) e2fsprogs - security update (Pasi Pirhonen) 3. CESA-2008:0003 Moderate CentOS 4 ia64 e2fsprogs - security update (Pasi Pirhonen) 4. CESA-2008:0002 Critical CentOS 4 ia64 tog-pegasus - security update (Pasi Pirhonen) 5. CESA-2008:0003 Moderate CentOS 4 s390(x) e2fsprogs - security update (Pasi Pirhonen) 6. CESA-2008:0002 Critical CentOS 4 s390(x) tog-pegasus - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Tue, 8 Jan 2008 17:52:54 +0200 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0003 Moderate CentOS 3 ia64 e2fsprogs - security update To: centos-announce(a)centos.org Message-ID: <20080108155253.GA31301(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2008:0003 https://rhn.redhat.com/errata/RHSA-2008-0003.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/e2fsprogs-1.32-15.4.ia64.rpm updates/ia64/RPMS/e2fsprogs-devel-1.32-15.4.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

password aging for openldap in Centos 4.5
by tblader 09 Jan '08

09 Jan '08

Anyone have password aging working in Openldap 2.2.13-7 on Centos? The system continues to prompt for a new password regardless of whether it's been changed or not. Thanks -- Flambeau Inc. Technology Center - Baraboo, WI Email : tblader(a)flambeau.com Keyserver: http://pgp.mit.edu KeyID: 0x00E9EC2C

4 3

kbs-CentOS-testing rsyslog unsigned, yum won't update it on 5.1
by William L. Maltby 09 Jan '08

09 Jan '08

As the subject says. Just an FYI. -- Bill

2 1

max mount count incovenient
by Linux Man 09 Jan '08

09 Jan '08

Hello group I added a new partition in fstab, and works without a problem. I used mkfs.ext3 to create the partition. My problem is that every 26 boots, the system tells that the partition have no been checked since 26 systems boots, ant start to check my new partition. This is a lot of time consuming, and always is in a bad time. There some way to do the check in a controlled time? i.e. do it the check before 26 system boot, when the time is no problem. Thanks a lot Best regards

5 6

Hostap
by robert boardman 09 Jan '08

09 Jan '08

Hi All Is there an easy way to add hostap support to centos 5 without recompiling the kernel, although I have a prism 2.5 card the stock install doesn't seem the allow this to be setup as an AP thanks in advance for the advice Robb

1 0

Error logs where?
by Christopher E 09 Jan '08

09 Jan '08

Hello all, does any one know where the error log for the server would be in what dir? Thanks Christopher

4 3

Fwd: Securing Linux laptops
by Robert Moskowitz 09 Jan '08

09 Jan '08

http://www.linux.com/feature/123579 Feature: Wireless & Mobile Securing Linux laptops By Rick Cook on January 07, 2008 (9:00:00 PM) Print Comments Laptop and notebooks are being stolen at an ever-increasing rate. In 2004, Safeware Insurance which sells computer insurance, estimated 600,000 laptop and notebooks a year were being stolen. In 2006 an estimated 750,000 were being swiped, according to Absolute Software a company that makes computer tracking products -- and does not support Linux. LoJack For Laptops, another computer tracing company -- which also does not support Linux -- says FBI statistics show 2 million laptop and notebook computers were stolen in the US in a recent year. While the figures may not agree in detail, they all show that laptop and notebook theft is a major problem -- and if you're not careful, your Linux laptop might be next. ...... For the rest see the URL. So what options do we have for encrypting partitions. Can you encrypt a LVM that has /home on it (or just the ext3 in the LVM)? What about /boot on a USB dongle. I actually think I know how to do this at install with Disk Druid. But can you unmount /boot after booting up (don't want to walk around with the dongle on the system, wear it around my neck on a lanyard).

5 4

centos 5.1 kernel dump
by Jerry Geis 09 Jan '08

09 Jan '08

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll" option) Jan 8 05:20:00 localhost kernel: Jan 8 05:20:00 localhost kernel: Call Trace: Jan 8 05:20:00 localhost kernel: <IRQ> [<ffffffff800b5d77>] __report_bad_irq+0x30/0x7d Jan 8 05:20:00 localhost kernel: [<ffffffff800b5faa>] note_interrupt+0x1e6/0x227 Jan 8 05:20:00 localhost kernel: [<ffffffff800b54bc>] __do_IRQ+0xc7/0x105 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a3bd>] do_IRQ+0xe7/0xf5 Jan 8 05:20:00 localhost kernel: [<ffffffff8005b615>] ret_from_intr+0x0/0xa Jan 8 05:20:00 localhost kernel: [<ffffffff80011cba>] __do_softirq+0x53/0xd5 Jan 8 05:20:00 localhost kernel: [<ffffffff801515dd>] end_msi_irq_wo_maskbit+0x9/0x16 Jan 8 05:20:00 localhost kernel: [<ffffffff8005c2fc>] call_softirq+0x1c/0x28 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a53a>] do_softirq+0x2c/0x85 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a3c2>] do_IRQ+0xec/0xf5 Jan 8 05:20:00 localhost kernel: [<ffffffff8005b615>] ret_from_intr+0x0/0xa Jan 8 05:20:00 localhost kernel: <EOI> [<ffffffff8000cb74>] bit_waitqueue+0x3c/0xb4 Jan 8 05:20:00 localhost kernel: [<ffffffff8002ce23>] wake_up_bit+0x11/0x22 Jan 8 05:20:00 localhost kernel: [<ffffffff880328ef>] :jbd:do_get_write_access+0x137/0x527 Jan 8 05:20:01 localhost kernel: [<ffffffff800192e9>] __getblk+0x25/0x22c Jan 8 05:20:01 localhost kernel: [<ffffffff88032d01>] :jbd:journal_get_write_access+0x22/0x33 Jan 8 05:20:01 localhost kernel: [<ffffffff8804dc75>] :ext3:ext3_reserve_inode_write+0x38/0x90 Jan 8 05:20:01 localhost kernel: [<ffffffff8804dcee>] :ext3:ext3_mark_inode_dirty+0x21/0x3c Jan 8 05:20:01 localhost kernel: [<ffffffff88050b14>] :ext3:ext3_dirty_inode+0x63/0x7b Jan 8 05:20:01 localhost kernel: [<ffffffff8001349c>] __mark_inode_dirty+0x29/0x16e Jan 8 05:20:01 localhost kernel: [<ffffffff8804b5f5>] :ext3:ext3_new_blocks+0x567/0x693 Jan 8 05:20:01 localhost kernel: [<ffffffff80025273>] __bread+0x6/0x81 Jan 8 05:20:01 localhost kernel: [<ffffffff8804e46b>] :ext3:ext3_get_blocks_handle+0x43a/0x9f1 Jan 8 05:20:01 localhost kernel: [<ffffffff88032ca8>] :jbd:do_get_write_access+0x4f0/0x527 Jan 8 05:20:01 localhost kernel: [<ffffffff8804ed42>] :ext3:ext3_get_block+0xbe/0xe3 Jan 8 05:20:01 localhost kernel: [<ffffffff8000e1b3>] __block_prepare_write+0x1b6/0x4a0 Jan 8 05:20:01 localhost kernel: [<ffffffff8804ec84>] :ext3:ext3_get_block+0x0/0xe3 Jan 8 05:20:01 localhost kernel: [<ffffffff8003c1d4>] block_prepare_write+0x1a/0x25 Jan 8 05:20:01 localhost kernel: [<ffffffff88050260>] :ext3:ext3_prepare_write+0xaf/0x17b Jan 8 05:20:01 localhost kernel: [<ffffffff8000f9cb>] generic_file_buffered_write+0x25a/0x6d8 Jan 8 05:20:01 localhost kernel: [<ffffffff8000cca5>] file_read_actor+0xb9/0x154 Jan 8 05:20:01 localhost kernel: [<ffffffff8000ddd9>] current_fs_time+0x3b/0x40 Jan 8 05:20:01 localhost kernel: [<ffffffff8000cbec>] file_read_actor+0x0/0x154 Jan 8 05:20:01 localhost kernel: [<ffffffff80015dc6>] __generic_file_aio_write_nolock+0x36c/0x3b8 Jan 8 05:20:01 localhost kernel: [<ffffffff8002134b>] generic_file_aio_write+0x65/0xc1 Jan 8 05:20:01 localhost kernel: [<ffffffff8804c192>] :ext3:ext3_file_write+0x16/0x91 Jan 8 05:20:01 localhost kernel: [<ffffffff80017958>] do_sync_write+0xc7/0x104 Jan 8 05:20:01 localhost kernel: [<ffffffff8009b492>] autoremove_wake_function+0x0/0x2e Jan 8 05:20:01 localhost kernel: [<ffffffff8000cbec>] file_read_actor+0x0/0x154 Jan 8 05:20:01 localhost kernel: [<ffffffff800161d8>] vfs_write+0xce/0x174 Jan 8 05:20:01 localhost kernel: [<ffffffff80016a8d>] sys_write+0x2d/0x6e Jan 8 05:20:01 localhost kernel: [<ffffffff80016aa5>] sys_write+0x45/0x6e Jan 8 05:20:01 localhost kernel: [<ffffffff8005b28d>] tracesys+0xd5/0xe0 Jan 8 05:20:01 localhost kernel: Jan 8 05:20:01 localhost kernel: handlers: Jan 8 05:20:01 localhost kernel: [<ffffffff801dadc4>] (usb_hcd_irq+0x0/0x55) Jan 8 05:20:01 localhost kernel: Disabling IRQ #169

3 3

tar bug in CentOS 4.6?
by David G. Miller 09 Jan '08

09 Jan '08

Since upgrading my server from CentOS 4.5 to 4.6 I've been getting the following error from amanda backups: mutilate /home lev 1 FAILED [compress got signal 11, /bin/tar got signal 13] I was away from the house for most of the end of December and had a couple of other issues that came up that could have been related but apparently weren't (why is it that several things all go wrong at once?). After getting these other issues resolved I was still getting the above error. I tried running the following command as root: /bin/tar -X /etc/amanda/exclude-list/exclude.txt -cvf - /home | gzip -v -c > /share/dave/Home.tar.gz Initially tar would die while attempting to back up one of IMAP folders that had quite a few fairly large e-mails (some pictures my brother had sent). I removed the larger e-mails and tar proceeded past the IMAP folder that had been the problem only to die later: ... /home/judy/Judy's Stuff/School/ /home/judy/Judy's Stuff/School/2007 Spring/ /home/judy/Judy's Stuff/School/2007 Spring/Mynametemplate.ppt /home/judy/Judy's Stuff/School/2007 Spring/MyNameSamples.doc /home/judy/Judy's Stuff/School/2007 Spring/Myname105.ppt /home/judy/Judy's Stuff/School/2007 Spring/TYP Types.doc /home/judy/Judy's Stuff/School/2007 Spring/Photoshop_CS2.exe Segmentation fault The copy of PhotoShop is the trial version that my wife had downloaded about a year ago for a class she was taking. This directory has been getting backed up at least every thirty days since then given my tape rotation. If I remove the PhotoShop_CS2.exe file, the backup completes normally. So, is this a tar bug (doesn't like big files now) or is there some other issue like available shared memory that's causing the problem? Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

3 2

Problem with CentOS 5.1/xen/RTL8110
by Chris Gow 09 Jan '08

09 Jan '08

Hello: I'm having issues with my CentOS 5.1/Xen installation. If I run the xen-bridge, I seem to get flaky ethernet. By flaky I mean everything seems fine from the host machine, but if I attempt to contact the host machine from another remote machine (eg. my laptop which is on the same subnet as the xen machine, separated by 10 ft of cable and a router) I either get extremely high ping times or Destination Host Unreachable. Ditto with ssh. I've disabled the firewall and it does not make a difference. If I stop the xen-bridge (/etc/xen/scripts/network-bridge stop) then I get what I would consider normal network access to the xen machine. Hardware: Gigabyte GA-G33M-S2H MB (Realtek R8110SC onboard nic) OS: CentOS 5.1 64bit Xen I installed CentOS last night with the Xen kernel, the stock kernel did not support my nic which I was aware of. So I downloaded the r1000 source rpm from the centos wiki, built and installed it. Once I did that the card was detected (an ifconfig would actually display eth0), but it would never get an IP address (the xen machine is configured for dhcp at the moment). Today, I installed the non-xen kernel, applied the non-xen r1000 kernel module and the onboard nic was found and working. I then grabbed the updates from centos, saw that there were some kernel updates, applied the r1000 kernel modules again, restarted and (the non-xen kernel) eth0 was still happy. Good. Restarted again, but booted into the xen kernel, eth0 was still happy. eth0 would get an IP address, and was able to see the outside world. However, the outside world (eg. my laptop) could not see the xen machine or it could inconsistently. That is, ping times would be extremely high (on the order of 2+ seconds) or I would get Destination Host Unreachable errors. Trying to connect via ssh would also be sporadic. Thinking it might be firewall related, I disabled the firewall. There was no change in behaviour. I then disabled the xen-bridge and was able to ping with reasonable numbers (<200ms) and connect via ssh. Just to note though, after I stopped the bridge I immediately tried to connect via ssh/ping and did not get through, so I ran service iptables stop (again) and then was able to get correct network access. I'm not sure if stopping iptables again did anything (I doubt) or I did not leave enough time from stopping the bridge to letting everything get reconfigured. I'm not sure what the problem is or how exactly to troubleshoot it. The NIC is slightly different than the one specified in the CentOS wiki (the wiki mentions RTL8110 and RTL8169SC and mine is a RTL8110SC) but I'm not familiar enough with the devices to know how much of a big deal that is, if any. Also, just to be clear, the problem is other physical machines have a difficult time accessing the xen host pc when the xen-bridge is running. I have not gotten as far as creating a VM yet. Any assistance would be great. thanks -- chris

5 5

yum update download only?
by Kenneth Porter 08 Jan '08

08 Jan '08

Googling for this feature, I saw reports from the yum developer that it wasn't yet implemented. This was in mailing list posts from a year or more ago. Did it ever make it into the yum code? I want to start downloading the updates for a server going from 5.0 to 5.1 and then do the actual installation once I'm on site. I don't want to have to wait around while there for the download to proceed. I'd rather have all the packages ready in the yum cache when I get there.

4 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss