From owner-freebsd-current@FreeBSD.ORG  Wed Feb  3 20:06:48 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 857F41065676;
	Wed,  3 Feb 2010 20:06:47 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Marc UBM Bocklet <ubm@u-boot-man.de>
Date: Wed, 3 Feb 2010 15:06:38 -0500
User-Agent: KMail/1.6.2
References: <20100201184446.2325c04e.ubm.freebsd@gmail.com>
	<201002031234.16137.jkim@FreeBSD.org>
	<20100203191126.356d8132.ubm@u-boot-man.de>
In-Reply-To: <20100203191126.356d8132.ubm@u-boot-man.de>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Multipart/Mixed;
  boundary="Boundary-00=_RddaLYHKoXxkOxF"
Message-Id: <201002031506.41531.jkim@FreeBSD.org>
Cc: Marc UBM Bocklet <ubm.freebsd@googlemail.com>, freebsd-current@freebsd.org
Subject: Re: vidcontrol / resolution problems with latest current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 20:06:48 -0000


--Boundary-00=_RddaLYHKoXxkOxF
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Wednesday 03 February 2010 01:11 pm, Marc UBM Bocklet wrote:
> On Wed, 3 Feb 2010 12:33:58 -0500
>
> Jung-uk Kim <jkim@freebsd.org> wrote:
> > On Wednesday 03 February 2010 08:38 am, Marc UBM Bocklet wrote:
> > > On Tue, 2 Feb 2010 16:43:07 -0500
> > >
> > > Jung-uk Kim <jkim@freebsd.org> wrote:
> > > > > > > Can anyone point me to a solution / is more info
> > > > > > > required?
> > > > > >
> > > > > > Hmm...  The attached patch should restore the previous
> > > > > > behavior.
> > > > >
> > > > > No change, unfortunately. Anything I can provide to help?
> > > >
> > > > How about the attached patch, then?
> > >
> > > Thanks for the quick response!
> > >
> > > Unfortunately, no change, even with the new patch. Screen stays
> > > on and lit up, but I see not text. Starting X blindly still
> > > works.
> >
> > What happens if you blindly display screen-full of text ('dmesg'
> > or 'ls -lR /' for example)?  Also, can you show me verbose boot
> > messages and 'vidcontrol -i mode' output?  'vidcontrol -i
> > adapter' output from the mode (VESA_800x600) will be useful as
> > well, e.g., 'vidcontrol -i adapter > vesa.txt' and please send me
> > the vesa.txt.
>
> Textfiles & dmesg are attached, blindly typing dmesg or ls -lR /
> changes nothing, screen stays lit but blank.

I think I got it now.  Please try this patch.

Thanks,

Jung-uk Kim

--Boundary-00=_RddaLYHKoXxkOxF
Content-Type: text/plain;
  charset="iso-8859-1";
  name="vesa.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="vesa.diff"

--- sys/dev/fb/vesa.c	2010-02-02 16:34:30.000000000 -0500
+++ sys/dev/fb/vesa.c	2010-02-03 15:04:35.000000000 -0500
@@ -1293,7 +1293,7 @@
 	} else {
 		vesa_adp->va_buffer = 0;
 		vesa_adp->va_buffer_size = info.vi_buffer_size;
-		vesa_adp->va_window = BIOS_PADDRTOVADDR(info.vi_window);
+		vesa_adp->va_window = (vm_offset_t)x86bios_offset(info.vi_window);
 		vesa_adp->va_window_size = info.vi_window_size;
 		vesa_adp->va_window_gran = info.vi_window_gran;
 	}

--Boundary-00=_RddaLYHKoXxkOxF--