Date: Wed, 3 Feb 2010 12:33:58 -0500 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: Marc UBM Bocklet <ubm.freebsd@googlemail.com>, Marc UBM Bocklet <ubm@u-boot-man.de> Subject: Re: vidcontrol / resolution problems with latest current Message-ID: <201002031234.16137.jkim@FreeBSD.org> In-Reply-To: <20100203143801.d83b65ac.ubm@u-boot-man.de> References: <20100201184446.2325c04e.ubm.freebsd@gmail.com> <201002021643.09859.jkim@FreeBSD.org> <20100203143801.d83b65ac.ubm@u-boot-man.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002031234.16137.jkim>