Re: VESA driver hsync config problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The error that kills the xserver ends up on stderr. This may be a bug
in the xserver or the Xinerama extension and I will pursue that. In
the meantime as an interim solution maybe you could direct me as to
how I could hack the system-config-display to add a HorizSync line to
the xorg.conf file.

On 3/26/07, Adam Jackson <ajackson@xxxxxxxxxx> wrote:
On Mon, 2007-03-26 at 13:58 -0600, Xavier Toth wrote:
> Indeed I do have a log file and I'd greatly appreciate any assistance
> you can give me.

That log appears to be from a successful startup.  Odd.

We can definitely tell if we're running under Parallels though:

(II) VESA(0): VESA VBE OEM Vendor: Parallels Software International,
Inc.

The trick is just knowing what we're supposed to do when we detect
Parallels.  I don't have it, so I don't know.  What _should_ we do?

- ajax

--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Attachment: x.log.para
Description: Binary data

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux