vidcontrol / resolution problems with latest current

[Jung-uk Kim]

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 at 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 at 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
-------------- next part --------------
--- 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;
 	}