Re: [CALL FOR TESTERS] VESA High Resolution Console support from DragonFly

From: Alexandre \ (Alex.Kovalenko_at_verizon.net)
Date: 05/22/05

  • Next message: Doug White: "Re: Newest loader from CVS not working" 
    Date: Sun, 22 May 2005 14:43:43 -0400
To: Xin LI <delphij@frontfree.net>

    On Sun, 2005-05-22 at 19:26 +0800, Xin LI wrote:
    > Dear -CURRENT users,
    >
    > I would like to solicit a test of the following patchset which is based
    > on DragonFly's changes, against -CURRENT, to bring high resolution console
    > support to FreeBSD. The current patchset can be considered as "BETA" and
    > I would commit it if there is no complain about this patchset in the next
    > week.
    >
    > The patchset can be found at:
    > http://people.freebsd.org/~delphij/vesa/patchset-highres.20050522
    >
    > To use it, you will need latest -CURRENT code, and apply the patchset at
    > toplevel source tree, i.e. /usr/src for usual cases. Then you need to build
    > and reinstall your kernel, with 'options SC_PIXEL_MODE' compiled in, and
    > optionally options VESA if you don't want to manually load VESA support
    > module. A make buildworld/installworld is recommended, but I believe that
    > just rebuild/reinstall usr.sbin/vidcontrol is enough to get your hands on
    > the support for using something like 'vidcontrol MODE_239' or so, which will
    > switch the current console to that mode. Some mode may not work on certain
    > cards, though.
    >
    > Please let me know if anything strange happens; While I have been running
    > with the patch for a while, I would still be happy if you will report that
    > it works :-)
    >
    > Thanks in advance!
    >
    > Cheers,
    I have observed some odd behavior when X display becomes garbled if USB
    stack is loaded and USB keyboard is attached after user has logged into
    X desktop (Gnome in my case). I am setting MODE_280 (1024x768x32) in
    rc.conf using 'allscreens_flags'.

    I have been playing with it a bit and found out that I can achieve the
    same result by doing 'vidcontrol MODE_280 < /dev/ttyv8 > /dev/ttyv8'
    after logging into Gnome. And ttyv8 is the terminal, occupied by X
    display. Restarting X server cures the problem.

    Neither original scenario, nor the second one are very likely, so I do
    not know whether it is much of a problem.

    I am running -CURRENT from May 14th, video chipset is S3 ProSavage.

    Please, let me know if there is any additional information that I can
    provide. 

    -- 
Alexandre "Sunny" Kovalenko (¾ÛÕÚáÐÝÔà ºÞÒÐÛÕÝÚÞ)
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Doug White: "Re: Newest loader from CVS not working"