SEO

On Sat, 05 Apr 2008 01:16:16 +0000, John F. Morse wrote:

> I bought a Samsung SyncMaster 931B "19") and replaced the ViewSonic A75f
> (17"), which is now on another couple of PCs through a KVM.
>
> I have never changed the xorg.conf though, and the SyncMaster is running
> fine.
>
> Here is the old but still being used xorg.conf monitor section:
>
> Section "Monitor"
> Identifier "A75f"
> Option "DPMS"
> HorizSync 30-70
> VertRefresh 50-160

You are probably running at less than optimum refresh rate. Put the
numbers from Samsung's own site in there:

http://www.samsung.com/cp/products/m...9mebsbdxaa.asp

I didn't bother searching further for an English language site but that one
has numbers you can see.

Thus spake John F. Morse:
<snip>
> I bought a Samsung SyncMaster 931B "19") and replaced the ViewSonic A75f
> (17"), which is now on another couple of PCs through a KVM.
>
> I have never changed the xorg.conf though, and the SyncMaster is running
> fine.
>
> Here is the old but still being used xorg.conf monitor section:
>
> Section "Monitor"
> Identifier "A75f"
> Option "DPMS"
> HorizSync 30-70
> VertRefresh 50-160
>
> You probably have an "Auto" button like mine on the bottom edge of the
> monitor bezel. When it is pushed the monitor seems to know what is best.
>
> Of course it makes me wonder if the signal is not really optimal, could
> it be improved so the monitor doesn't need to (possibly) distort it?
>

I do have that "auto" buton, but when depressed a message reads, "Auto
Adjustment Not Available". Go figure. Just for the heck of it I
uncommented the HSync and VRefesh digits, then restarted X ... nothing
of note. Hmmm? I *guess* for LCD's it's not important.

--
sk8r-365
And all the people were amazed, and said, Is not this the son of
David? -- Matthew 12:23

Dave Uhring wrote:
> On Sat, 05 Apr 2008 01:16:16 +0000, John F. Morse wrote:
>
>
>> I bought a Samsung SyncMaster 931B "19") and replaced the ViewSonic A75f
>> (17"), which is now on another couple of PCs through a KVM.
>>
>> I have never changed the xorg.conf though, and the SyncMaster is running
>> fine.
>>
>> Here is the old but still being used xorg.conf monitor section:
>>
>> Section "Monitor"
>> Identifier "A75f"
>> Option "DPMS"
>> HorizSync 30-70
>> VertRefresh 50-160
>>
>
> You are probably running at less than optimum refresh rate. Put the
> numbers from Samsung's own site in there:
>
> http://www.samsung.com/cp/products/m...9mebsbdxaa.asp
>
> I didn't bother searching further for an English language site but that one
> has numbers you can see.


Thanks, Dave.

I see the info:

Le Samsung SyncMaster 931b est un moniteur ACL TFT analogique et
numérique de 19 po qui offre un rapport de contraste de 700:1, une
luminosité de 300cd/m2, une résolution de 1280 x 1024, un angle de
visionnement de 160/160 et une fréquence de balayage horizontal de 30-81
KHz et vertical de 56-75 Hz avec un temps de réponse rapide de 8 ms. Il
comprend les fonctions MagicTune, MagicBright II et MagicColor, ainsi
qu'un bloc d'alimentation intégré.

I know no French, but like you said, the numbers all speak for
themselves. ;-)

Evidentially a linked server with all the images is down right now, or
the site is unkempt, so I couldn't see whatever else is on that page. I
did some snooping and found this:

http://www.samsung.com/cp/support/pr...vedmonitor.sec

or http://tinyurl.com/44to3x

which has a PDF that is in English for my model.

--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

Thus spake John F. Morse:
<snipped - grrr coming up next>

> http://www.samsung.com/cp/support/pr...ad/FileView.as
> px?cttfileid=876633&type=Monitor&typecode=&subtype =Archived+Monitor&
> subtypecode=&cmssubtypecode=&model=931B&filetype=U M&language=&LSSI=/cp/
> module/ssi/left/lmenu_monitor_archivedmonitor.sec&RSSI=/cp/module/ssi/
> right/rmenu_archivedmonitor.sec
<snip>

Sir, I dunno if you are aware of a *long* standing USENET protocol,
therefore please allow me to bring it to light: at no time is a line of
text to exceed 80 characters, but preferably keep it to 72. The line
above was 312 (I manually wrapped it). Even while using a wide screen
monitor reading that line is unnecessarily long to view and of no
reading value.

http://www.cs.tut.fi/~jkorpela/usenet/dont.html

#2 (in part)

"Plain text means it's text only, with line length under 80 (preferably
under 72) characters; it doesn't mean boring or careless text. Use good
writing style."

> or http://tinyurl.com/44to3x

Having supplied a tinyurl is perfectly correct, readable and useful. If
you will do that _alone_ in the future, people will be grateful.

Here's a useful source on the topic:
http://www.google.com/Top/Computers/Usenet/Etiquette/

Regards,
--
sk8r-365
So the last shall be first, and the first last: for many be called,
but few chosen. -- Matthew 20:16

Thus spake John F. Morse: <snip>
> -- John
>
> No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used
> in the preparation or transmission of this message.
>
> The EULA sounds like it was written by a team of lawyers who want to
> tell me what I can't do. The GPL sounds like it was written by a human
> being, who wants me to know what I can do.

The above message is correct, IMO, but ... while I'm at it - and I'm not
wanting to offend - it needs to be mentioned your sig file is _too_
l-o-n-g and should be no more than the accepted 4 lines, less is OK,
when properly wrapped (I wrapped it). Please.

http://www.faqs.org/faqs/usenet/posting-rules/part1/

"<snip> Please keep your signatures concise, as people do not appreciate
seeing lengthy signatures, nor paying the phone bills to repeatedly
transmit them. 2 or 3 lines are usually plenty. Sometimes it is also
appropriate to add another line or two for addresses on other major
networks where you can be reached (e.g., CompuServ, Bitnet). Long
signatures are definitely frowned upon. DO NOT include drawings,
pictures, maps, or other graphics in your signature -- it is not the
appropriate place for such material and is viewed as rude by other
readers."

Thank you,
--
sk8r-365
So the last shall be first, and the first last: for many be called,
but few chosen. -- Matthew 20:16

sk8r-365 wrote:

> Sir, I dunno if you are aware of a *long* standing USENET protocol,
> therefore please allow me to bring it to light: at no time is a line of
> text to exceed 80 characters, but preferably keep it to 72. The line
> above was 312 (I manually wrapped it). Even while using a wide screen
> monitor reading that line is unnecessarily long to view and of no
> reading value.
>


I'm aware of everything, including the widespread proliferation of net
nannys. I've used USENET for many years and have run my own NNTP news
servers since 2000, with BBSes since 1990.

But don't pop a cork yet! Let me explain a few of my feelings.

I provided a URL, and it was meant to be clicked -- not read. You are
absolutely correct stating it has no reading value. You could click it
on the left end and it would have worked.

I don't wrap text on this end because I have no way of knowing how it
will appear to all of the various newsreaders. If I would have broken
the URL, it would have been, well, broken for everybody. I provided the
TinyURL knowing many people would wrap and break the URL.

If a reader prefers text wrapped to a certain length, then they
certainly are free to do it. I can't format it here or some of the
people will always object. I provide text, and those who are reading
provide formatting in whatever way they desire.

If you believe I should format it, then HTML would be the better option.
I'm sure that is not desired. ;-)

You use slrn. That is your choice, but it, and many readers similar to
it, are from and designed for the past, as you stated ("*long* standing
USENET protocol").

IOW, don't try and make everyone on the Interstate Highway System ride
horses and pull wagons. Time marches on, and only those who refuse to
use what is modern will be left in the dust, hollering and screaming at
those who have better things to do and places to go. Or they will be run
over!

I use many Unix newsreaders, including slrn, Pan, KNode, Sylpheed-Claws,
KLibido, emacs+Gnus, Mozilla and Thunderbird/Icedove. I prefer
Thunderbird/Icedove because I also use it for e-mail, and have years of
archives in the Mozilla-style format for instant reference. I've used
many other news clients under Windows (Agent, Xnews, Gravity, OE <spit>)
and several on the Mac OS for some 22 years, but I still preferred the
Moz-type news clients on those platforms.

Some of the groups on the 11 news servers where I am active will nearly
always post in HTML, and include images. HTML-ready newsreaders just
make better sense than text-only newsreaders for me since I do move
through the groups fast and frequently.


> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
>
> #2 (in part)
>
> "Plain text means it's text only, with line length under 80 (preferably
> under 72) characters; it doesn't mean boring or careless text. Use good
> writing style."
>
>
>> or http://tinyurl.com/44to3x
>>
>
> Having supplied a tinyurl is perfectly correct, readable and useful. If
> you will do that _alone_ in the future, people will be grateful.
>


I provided the TinyURL it as a courtesy because the URL was long. How
long can only be determined by the readers.

Creating a TinyURL does involve a few extra steps and a little
additional time, especially since I do bother to verify that it works as
intended.

I don't believe I should be expected to do all the work, when there are
people who just want to sit back and not bother to use a news client
that can display messages in the format that they choose or desire.

These people have their preferences, and I adjust practically all the
time. But if I should post one long line, or someone thinks my sig has
too many lines (when they wrap it), well it's their privilege to gripe,
not to gripe, plonk, whatever.


> Here's a useful source on the topic:
> http://www.google.com/Top/Computers/Usenet/Etiquette/
>
> Regards,
>


I try to cater to the majority, that's why I bottom post, or post
inline, when I actually prefer top-posting. I also do trim away
non-relevant lines, which many others do not.

I know, many net nannys will say logic dictates the reply should follow
the original text, but my logic says I can remember previous articles,
and it is a big waste of time for me to scroll down to see new material
in nearly every message. Again, this is an old throwback to the past,
and I'm aware that you can't teach old dogs new tricks, so I accommodate
those who believe USENET has unbreakable laws, and I bottom post, and do
a lot of scrolling to read.

Same goes for plain text and no HTML. A throwback to the days of slow
modems and hard-copy printing terminals. A picture is worth a thousand
words, but to keep peace, I don't use HTML where it is not accepted.

I certainly appreciate your politeness in this matter, but I did want to
let you know how I stand on these issues. Some will agree, and some will
disagree, but that is the way life is.

I do try to fit in and do as the newsgroup users prefer. I'll remember
to only use a TinyURL if the normal URL line appears too long -- if I
can catch it since I can only guess. You know I use larger monitors,
normally set at 1280x1024, and 80 columns can be only an educated guess
at best.

Again, thanks for sharing your thoughts, and for listening to mine.


--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

sk8r-365 wrote:
> Thus spake John F. Morse: <snip>
>
>> -- John
>>
>> No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used
>> in the preparation or transmission of this message.
>>
>> The EULA sounds like it was written by a team of lawyers who want to
>> tell me what I can't do. The GPL sounds like it was written by a human
>> being, who wants me to know what I can do.
>>
>
> The above message is correct, IMO, but ... while I'm at it - and I'm not
> wanting to offend - it needs to be mentioned your sig file is _too_
> l-o-n-g and should be no more than the accepted 4 lines, less is OK,
> when properly wrapped (I wrapped it). Please.
>
> http://www.faqs.org/faqs/usenet/posting-rules/part1/
>
> "<snip> Please keep your signatures concise, as people do not appreciate
> seeing lengthy signatures, nor paying the phone bills to repeatedly
> transmit them. 2 or 3 lines are usually plenty. Sometimes it is also
> appropriate to add another line or two for addresses on other major
> networks where you can be reached (e.g., CompuServ, Bitnet). Long
> signatures are definitely frowned upon. DO NOT include drawings,
> pictures, maps, or other graphics in your signature -- it is not the
> appropriate place for such material and is viewed as rude by other
> readers."
>
> Thank you,
>


You don't offend me, and I thank you for your kind remarks.

However, as I mentioned in the previous message, it is impossible for me
to wrap the length of the lines at any certain column that everyone
likes. There are too many different newsreaders and preferences used by
all of the USENET people. Those readers will have to wrap wherever they
want the lines to break.

For instance, the "80" column (or less) idea was devised in the
teletypewriter era when everyone used a hard copy printer or printing
terminal, like a Teletype 33 KSR/ASR, a DECwriter, DEC TP-1000, etc.
More than 80 columns created a big, black blob at the end of the line.
At least until smarter printers came out that could count the characters
and force a carriage return at 78 or 80. The CR is now called "Enter" of
course, but that shows the evolution of things.

With modern computers instead of mechanical terminals, and configurable
software, wrap can occur anywhere. Therefore the "80-column rule" is no
longer needed.

I can see where each and every one of the hot gripes by the net nannys
are based on the available technology from back in the 1990s and
earlier. This is 2008, and people need to get up to speed and use what
is available, and quit holding back those who do want to get ahead.
Mostly, they need to stop the petty picking and nannying. A prime
example is a.o.l.ubuntu, which has turned into a very unpleasant place
to try and give or get help.

Please don't fall into this trap sk8tr, and please try and help others
who somehow feel nannying is more important than providing help on the
newsgroup name subjects. The nannying just causes flames and runs off
the good guys, leaving undesirables behind to kill the groups. Before
long they will have completely killed USENET, and then all that will
remain is mailing lists and IRC, both which I despise.

I know very well what is considered "etiquette," or even "standard
rules" by some in USENET, but maybe if you told me why slrn cannot wrap
the lines wherever you prefer them, I'd have an idea why this is such an
issue with you (and many others obviously).

While you are at it (you didn't object to me about this because I wasn't
guilty of it), what is a reason to never top-post? Is it because some
people hate to pound the spacebar to get through long, boring quoted
material after they have read the new stuff? Perhaps because some lazy
replier said a few words at the top and didn't trim anything?

What about me pounding my spacebar to get down to the relevant new
material? If I really need a refresher, I can always scroll back up.
Can't slrn do that, even when using a non-GUI pseudo TTY terminal
without any GUI scrollbars? Does <Shift><Page Up> work for slrn, nn,
tin, or trn?

Not counting the two blank lines, my sig is actually three lines -- if
you don't wrap them. The delimiter isn't part of the sig, it is a
separator and should cause an automatic trim unless a reader is using
trash like OE. The time to send three lines online is microseconds. The
extra lines aren't wasting anybody's canary yellow teleprinter paper
like when the "rule" was established, and the text is not a big
commercial advertisement in nature.

I ask these questions because using something like Thunderbird, I don't
have any problems with line wrap, long sigs, or even multiple sigs like
one a.o.l.ubuntu user whom I'm sure you know, nor even with useful HTML.
My gripe is the need to scroll past stale material to get to the new,
and mostly, having to read constant nannying by those who are
self-appointed USENET police.

Please don't feel offended because I'm not singling you out. I just felt
you deserved an explanation why I do or prefer these things. Perhaps you
will have a second look and maybe even consider a change in preference,
even if you do not actually make any changes as to how you post.

Again, thanks for sharing your opinions, and for listening to mine.

I have replaced my normal sig on this message for you and me.


--
John

Whoever loves his brother lives in the light, and there is nothing in him to make him stumble. 1 John 2:10

I demand that sk8r-365 may or may not have written...

> Thus spake John F. Morse:
> <snipped - grrr coming up next>
>> http://www.samsung.com/cp/support/pr...ad/FileView.as
>> px?cttfileid=876633&type=Monitor&typecode=&subtype =Archived+Monitor&
>> subtypecode=&cmssubtypecode=&model=931B&filetype=U M&language=&LSSI=/cp/
>> module/ssi/left/lmenu_monitor_archivedmonitor.sec&RSSI=/cp/module/ssi/
>> right/rmenu_archivedmonitor.sec
[snip]
>> or http://tinyurl.com/44to3x

> Having supplied a tinyurl is perfectly correct, readable and useful. If you
> will do that _alone_ in the future, people will be grateful.

Some will; some of us don't want the redirection URL and would rather see the
original.

[snip]
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Interception of this message for advertising purposes is not permitted.

Don't shoot the pianist.

Thus spake John F. Morse:
<snip>
> With modern computers instead of mechanical terminals, and configurable
> software, wrap can occur anywhere. Therefore the "80-column rule" is no
> longer needed.

Not so, for the wrap is based on a break, and your 312 character URL
doesn't have one. I have slrn set to wrap (set wrap_flags 7).

> I can see where each and every one of the hot gripes by the net nannys
> are based on the available technology from back in the 1990s and
> earlier. This is 2008, and people need to get up to speed and use what
> is available, and quit holding back those who do want to get ahead.
<snip>

Grrr ... this is a peeve. That view point is of one who lives in the
States, while neglecting to consider there are millions more not using
large monitors and high speed connections. It leaves out consideration
of the needs and situation even of those in modernized non-US countries,
many in England for example, who have to pay by the minute/bytes for
their dial up. Your attitude neglects there a handicapped readers who
have trouble doing all the simple scrolling, pointy-clicky things.
Slapping people with pictures (ASCII or otherwise), unneeded text, HTML
code, etc. is rude. Seen that thoughtless attitude elsewhere, "If they
would rather die," said Scrooge, "they had better do it, and decrease
the surplus population."

BTW, you said, "people need to get up to speed and use what is
available" - slrn is available, up to speed and of my choosing above all
other options.

> Please don't fall into this trap sk8tr, and please try and help others
> who somehow feel nannying is more important than providing help on the
> newsgroup name subjects.
<snip>

I offer computer related help much more than providing lessons in net
etiquette on USENET - but all of it is help. What I'm trying to do here
is maintain long standing, and useful, guidelines which have served the
world over - the world, as you know, isn't the U.S. only. Your current
cavalier approach is equivalent to Microsoft's treading on the Web with
their own special non-standard page coding, unintelligent top posting
approach and specialized formatting simply due to your having the
capability and software which corrects the laziness and thoughtlessness
of others. In contrast, I suspect that by your replies to my request for
Net-etiquette here you care and you aren't intentionally trying be
bad-mannered... unlike MS.

> I know very well what is considered "etiquette," or even "standard
> rules" by some in USENET, but maybe if you told me why slrn cannot
> wrap the lines wherever you prefer them, I'd have an idea why this is
> such an issue with you (and many others obviously).

slrn is modern and in current development. slrn wraps at a break as
other proggies do. Your URL had no break for 312 characters.

% If you want to wrap long lines automatically, without having to
% press a key, you can set the variable to one of these values:
<snip>
% 7 wrap headers, quoted material and body

set wrap_flags 7

slrn is very configurable and has a powerful scoring method. Another
useful benefit of slrn is that when posting, and there's a Net-etiquette
faux pas, it stops with a message and chance to correct it. I prefer it
to pointy-clicky because I _read_ USENET and very rarely bother with
binaries (I do lurk alt.binaries.pictures.scenic).

> While you are at it (you didn't object to me about this because I wasn't
> guilty of it), what is a reason to never top-post? Is it because some
> people hate to pound the spacebar to get through long, boring quoted
> material after they have read the new stuff? Perhaps because some lazy
> replier said a few words at the top and didn't trim anything?

It's illogical. Most read books from the first page (top) to the last
(bottom). Top posting breaks the intelligent natural order of reading...
it's beginning to end, not end to beginning as MS has it done. Would you
find these messages better reading if posted in reverse order?

As for boring info: snipping unneeded text improves on the problem.

For a complete treatment of the topic read
http://www.caliburn.nl/topposting.html .

About recalling what you wrote in a thread ... I don't recall what you
wrote, nor will the potentially millions of others who might read it
over the years. Be thoughtful.

> What about me pounding my spacebar to get down to the relevant new
> material?

You're suffering from UTS - unsnipped text syndrome. Have you said
anything to that poster? Net-etiquette is your friend.

> If I really need a refresher, I can always scroll back up.
> Can't slrn do that, even when using a non-GUI pseudo TTY terminal
> without any GUI scrollbars? Does <Shift><Page Up> work for slrn, nn,
> tin, or trn?
<snip>

Quit sniping. slrn has back and forward keys. Browse the Web for slrn
information and you'll find all the answers to your questions.

> I ask these questions because using something like Thunderbird, I don't
> have any problems with line wrap, long sigs, or even multiple sigs like
> one a.o.l.ubuntu user whom I'm sure you know, nor even with useful HTML.

TB is a very good email client masquerading as a news client (oh, oh,
here come the flames! <cringe>). slrn does one thing and it does it
properly - it's a newsreader. Also, I don't read *ubuntu.

> My gripe is the need to scroll past stale material to get to the new,
> and mostly, having to read constant nannying by those who are
> self-appointed USENET police.

I'm not the first to ask you to be considerate?

> Please don't feel offended because I'm not singling you out. I just felt
> you deserved an explanation why I do or prefer these things.

I started this off topic thread; not feeling singled out.

> Perhaps you will have a second look and maybe even consider a change
> in preference, even if you do not actually make any changes as to how
> you post.

I've been on the Net before there were GUI tools generally available. It
was all vt and UNIX commands. Have kept regard for, and long supported,
net etiquette that full time. I see net etiquette as a "do unto others"
matter.

> Again, thanks for sharing your opinions, and for listening to mine.

You too. If you want, you can have the last word - but, please, no
questions. Otherwise, I'll feel obligated to respect you but held back
to avoid violating my "last word" offer. 8P

> I have replaced my normal sig on this message for you and me.

I'm especially found of 1 John. Favorite is 1 John 3:1-3

"Behold, what manner of love the Father hath bestowed upon us, that we
should be called the sons of God: therefore the world knoweth us not,
because it knew him not.

Beloved, now are we the sons of God, and it doth not yet appear what we
shall be: but we know that, when he shall appear, we shall be like him;
for we shall see him as he is.

And every man that hath this hope in him purifieth himself, even as he
is pure."

--
sk8r-365
What I tell you in darkness, that speak ye in light: and what ye
hear in the ear, that preach ye upon the housetops. -- Matthew 10:27

On Apr 4, 1:45 am, "John F. Morse" <xanadu....@example.invalid> wrote:
> Most of my GNU/Linux installations use Debian 3.1, with older Ubuntu,
> Fedora Core, Lindows, Mandrake, Red Hat, Slackware, etc. IIRC, these all
> use XFree86, and I had to learn to fine-tune it over the years.
>
> Debian 4.0 uses X.Org.
>
> I presently have a "portable" ViewSonic 21 monitor plugged into one
> Debian box, which I have recently upgraded from Sarge to Etch, and now
> cannot get a higher resolution than 640x480. This is, of course, a
> ridiculous resolution for a 21" screen.
>
> Even trying other multiscan/multifrequency 17" and "dumb" 15" monitors
> will not allow any resolution change.

This is becouse the graphical card has too litle memory. At least it
thinks so.

> To make matters worse, the detected Trident video card causes a failure
> when xorg tries to initialize a screen.
>
> Of course the TTY terminals all work, so I do have access to vi for
> xorg.conf edits. The only method I've found to startx for a GUI DE is to
> manually edit xorg.conf and replace "trident" with "vesa" as the driver.
>
> Running "dpkg-reconfigure -phigh xorg-server" will only rebuild
> xorg.conf back to the detected trident driver.

Try 'dpkg-reconfigure -plow xserver-xorg'

> The monitor frequency rates also makes no difference if I edit xorg.conf
> and change them to the correct values for the monitor.

You shouldn't set values for modern monitors. They tell the graphical
card
all it needs. Only for buggy monitors it's needed.
Try only ' option "DPMS"' as is the default anyway.

> The Trident video card has sufficient memory, and is used in eleven
> other identical PCs which run Debian Sarge fine under XFree86. However
> Sarge support is ending so I must upgrade to Etch as time permits.

No, Xorg can't detect sufficient memory, as you can see in your log.
You should prob. tell Xorg the size.
We really need to also see /etc/X11/xorg.conf

> Below is the total /var/log/Xorg.0.log for examination (the font
> problems are of no concern).

> Perhaps someone has an idea that I might try? The xorg.conf can also be
> posted if requested.

It is needed, as your posted Xorg.0.log (good!)

> These Debian servers all run headless anyway, but at this point in time,
> I'd certainly like to find and resolve this X.Org resolution problem.
>
> TIA.
>
> 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: UNKNOWN
> Current Operating System: Linux optima12 2.6.18-4-486 #1 Mon Mar 26
> 16:39:10 UTC 2007 i586
> Build Date: 24 January 2008
> Before reporting problems, checkhttp://wiki.x.org
> to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 1 01:42:25 2008
> (==) Using config file: "/etc/X11/xorg.conf"
> (==) ServerLayout "Default Layout"
> (**) |-->Screen "Default Screen" (0)
> (**) | |-->Monitor "Generic Monitor"
> (**) | |-->Device "Trident Microsystems TGUI 9660/938x/968x"
> (**) |-->Input Device "Generic Keyboard"
> (**) |-->Input Device "Configured Mouse"
> (WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
> Entry deleted from font path.
> (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
> Entry deleted from font path.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
> Entry deleted from font path.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
> Entry deleted from font path.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
> Entry deleted from font path.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1" does not exist.
> Entry deleted from font path.

You should prob clean your paths. They have changed

> (II) Bus 0: bridge is at (0:0:0), (0,0,0), 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-ISA bridge:
> (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
> (--) PCI:*(0:10:0) Trident Microsystems TGUI 9660/938x/968x rev 211, Mem
> @ 0xff800000/22, 0xffef0000/16, BIOS @ 0xffee0000/16

Found Trident PCI card att PCI 0:10:0

> (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) LoadModule: "trident"
> (II) Loading /usr/lib/xorg/modules/drivers/trident_drv.so
> (II) Module trident: vendor="X.Org Foundation"
> compiled for 7.1.1, module version = 1.2.3
> Module class: X.Org Video Driver
> ABI class: X.Org Video Driver, version 1.0

loading trident Xorg driver

> (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) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c,
> tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397,
> cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi,
> tgui9440agi, tgui9660, tgui9680, providia9682, providia9685,
> cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7,
> cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1,
> cyberbladeAi1d, bladeXP, cyberbladeXPAi1, cyberbladeXP4, XP5
> (II) Primary Device is: PCI 00:0a:0
> (--) Chipset tgui9660 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]

Trident PCI card with tgui9660 found by Xorg trident driver

> (II) Setting vga for screen 0.
> (**) TRIDENT(0): Depth 24, (--) framebuffer bpp 32
> (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
> (II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset
> is 0x0000

Trident found and used

> (WW) System lacks support for changing MTRRs
> (II) TRIDENT(0): VESA BIOS detected
> (II) TRIDENT(0): VESA VBE Version 1.2
> (II) TRIDENT(0): VESA VBE Total Mem: 1024 kB
> (II) TRIDENT(0): VESA VBE OEM: Trident TGUI96xx
> (--) TRIDENT(0): Revision is 1
> (--) TRIDENT(0): Found TGUI9680 chip
> (--) TRIDENT(0): RAM type is EDO Ram
> (--) TRIDENT(0): Using HW cursor
> (--) TRIDENT(0): VideoRAM: 1024 kByte
> (--) TRIDENT(0): Memory Clock is 42.95 MHz
> (==) TRIDENT(0): Min pixel clock is 12 MHz
> (--) TRIDENT(0): Max pixel clock is 40 MHz
> (II) TRIDENT(0): Generic Monitor: Using hsync range of 28.00-80.00 kHz
> (II) TRIDENT(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
> (II) TRIDENT(0): Clock range: 12.00 to 40.00 MHz
> (II) TRIDENT(0): Not using default mode "640x350" (vrefresh out of range)
> (II) TRIDENT(0): Not using default mode "320x175" (bad mode
> clock/interlace/doublescan)
> (II) TRIDENT(0): Not using default mode "640x400" (vrefresh out of range)
> (II) TRIDENT(0): Not using default mode "320x200" (bad mode
> clock/interlace/doublescan)
> (II) TRIDENT(0): Not using default mode "720x400" (insufficient memory
> for mode)

As seen, lots of different resolutions are detected for the monitor,
but not sufficent ram in graphical card to run them.

> (II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory
> for mode)
> (II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
> for mode)
> (WW) TRIDENT(0): Mode pool is empty
> (EE) TRIDENT(0): No valid modes found
> (II) UnloadModule: "trident"
> (II) UnloadModule: "vm86"
> (II) Unloading /usr/lib/xorg/modules/libvm86.so
> (II) UnloadModule: "int10"
> (II) UnloadModule: "vbe"
> (II) UnloadModule: "ramdac"
> (II) Unloading /usr/lib/xorg/modules/libramdac.so
> (II) UnloadModule: "vgahw"
> (II) Unloading /usr/lib/xorg/modules/libvgahw.so
> (EE) Screen(s) found, but none have a usable configuration.
>
> Fatal server error:
> no screens found

Xorg panics and exits when it cant find a suitable resolution for the
card.