On 5/3/07, Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:

On Thursday,  3 May 2007 at 11:16:04 +0200, Victor Engmark wrote:
> On 5/3/07, Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
>> On Thursday,  3 May 2007 at  9:25:54 +0200, Victor Engmark wrote:
>>> On 5/3/07, Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
>>>> On Tuesday,  1 May 2007 at  9:01:26 +0200, Victor Engmark wrote:
>>>>> On 4/30/07, Erik Osterholm < [EMAIL PROTECTED]> wrote:
>>>>>> Could you post your Xorg.0.log and xorg.conf?  When Theory !=
>>>>>> Practice, it's often helpful to have information like this to help
>>>>>> determine what went wrong, so that in the future, Theory can ==
>>>>>> Practice.
>>>>> Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this
>>>>> morning.
>>>> I don't see the Xorg.0.log.  Also, it would be interesting to see how
>>>> the xorg.conf differs from the one you got from X -configure.
>>> The xorg.conf differs quite a lot.
>> And how?  Does it work?
> For the currently applicable definition of "work," no. I get a
> warning message from X.org every time I boot.

OK.  Either you give me information on what happens, or I'll drop the
case.  What warning message?

Please read the rest of the thread. I'm getting a warning that the HorizSync
rate is outside the capabilities of my current hardware, whether I use the
default (none), the values from MonitorsDB, or what other people have posted
in their xorg.conf files for other Dell Latitude D610s.

Why when you boot?

Because I run KDE at boot. From /etc/ttys:
ttyv8 "/usr/local/bin/kdm -nodaemon"  xterm on  secure

What does the screen look like?

Fine. That's not the issue, as stated several times in this thread.

 What does the Xorg.0.log look like?

I've sent it twice. What else do you want to know?

I used xorgconfig instead of
>>> X -configure
>>> , but xorgconfig doesn't autodetect any of the ranges, so there were
>>> none in the original file.
>>> Here's a cut'n'paste of the Xorg.0.log sent earlier:
>> You didn't send it.
> According to Gmail, I did.

Here's what arrived here:

> Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this
> ...
> [-- Attachment #2: xorg.conf --]
> [-- Type: application/octet-stream, Encoding: base64, Size: 6.0K --]
> [-- application/octet-stream is unsupported (use 'v' to view this part)
> [-- Attachment #3 --]
> [-- Type: text/plain, Encoding: 7bit, Size: 0.2K --]
> I copied the file from the email I sent >:)

Is it also in the mail you received?  It's definitely not here.

I only see the version which was sent by Gmail. It collates my emails when I
receive one I sent myself. Maybe the attachment was too big for the list,
but I didn't receive any error messages or warnings. Here are the headers
for the attachment:

Content-Type: text/x-log; name=Xorg.0.log; charset=ANSI_X3.4-1968
Content-Transfer-Encoding: base64
X-Attachment-Id: f_f160abdg
Content-Disposition: attachment; filename="Xorg.0.log"

This is a pre-release version of the X server from The X.Org Foundation.
>>> It is not supported in any way.
>> Where did you get this from?  6.2-RELEASE used 6.9.0 release.  Try
>> rebuilding from the Ports Collection.
> I burned the 6.2-RELEASE CD from freebsd.org. After installing a lot
> of software,

From where?

Official FreeBSD mirrors. I don't know where to find the settings, but I
used the first Swiss mirror in sysinstall.

I ran portupgrade -a . Surely, I should have the same or newer than
> the release by then?

Based on your statements, it's hard to say.

Based on me installing from an official CD, and using the default settings
for portupgrade? In that case, I don't understand why.

Also, pkg_version -vIL= right now doesn't list X.org.

This suggests that you installed it from elsewhere.  As I said,

I installed from the official FreeBSD mirrors.

Try rebuilding from the Ports Collection.

I've already done a
portupgrade -a
since I installed.

Victor Engmark
Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds
freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to