Re: Strange video mode output with VESA

2010/9/16 David DEMELIER <demelier.david@xxxxxxxxx>:
2010/7/19 Jung-uk Kim <jkim@xxxxxxxxxxx>:
On Friday 16 July 2010 07:18 pm, Jung-uk Kim wrote:
On Friday 16 July 2010 03:22 pm, Jung-uk Kim wrote:
On Friday 16 July 2010 03:00 pm, David DEMELIER wrote:
2010/6/19 paradox <ddkprog@xxxxxxxxx>:
On Wednesday 02 June 2010 04:25 pm, David DEMELIER wrote:
Hi there,

I was so happy to see that VESA is available for amd64, but
unfortunately it does not work really well for me. Take a
look at this picture :

http://img717.imageshack.us/img717/7311/dsc00399h.jpg

My laptop is a 15,6" so the best resolution is 1366x768, I
tried this

: vidcontrol MODE_496. As you can see on the picture all
: the lines are

completely everywhere, if I mouse the cursor they move away
(I'm not drunk!).

I have SC_PIXEL_MODE in my kernel config.

The console terminal is okay until I don't excess
1280x960x32 video mode.

Do you have any idea to fix this ?

It is kinda known problem. ���������If the mode has larger
bytes per scan line than the minimum, few characters per
line are lost when the screen is scrolled up or down, i.e.,
framebuffer copies of whole screen. ���������When you move
the mouse onto the line, entire line is redrawn and
restored. ���������That's what you are seeing. ���������Ed
might have a better idea how to fix it (CC'ed).

Jung-uk Kim

this is incorrent calculate the scan lines in the vesa driver
Jung-uk Kim should to fix it

But Jung-uk Kim said Ed' should fix it so we are in an infinite
loop :-

No, I didn't say that.  What I meant was "Ed may be a better
qualified person to fix syscons vs. terminal emulator interaction
issues." :-(

Can you please try the attached patch?

FYI, I just went ahead and committed a (slightly better) patch on head
as r210248.  It will be MFC'ed soon.

Jung-uk Kim


Sorry, I completely forgot this thread,

I tried your patch, it didn't solved the problem but the offset is
shorter now, only 2 or 3 characters per line are bad positionned. I
will try the r210248 revision, this revision only applies to the file
scvgarndr.c ?

Thanks.

--
Demelier David


I tried the r210248 revision but it doesn't works, I still have a
little offset but less than without the patch.

Kind regards,

--
Demelier David
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Strange video mode output with VESA
    ... might have a better idea how to fix it. ... this is incorrent calculate the scan lines in the vesa driver ... Jung-uk Kim should to fix it ... I just went ahead and committed a patch on head ...
    (freebsd-stable)
  • Re: Strange video mode output with VESA
    ... As you can see on the picture all the lines ... Do you have any idea to fix this? ... this is incorrent calculate the scan lines in the vesa driver ... Jung-uk Kim should to fix it ...
    (freebsd-stable)
  • Re: Strange video mode output with VESA
    ... video mode. ... might have a better idea how to fix it. ... this is incorrent calculate the scan lines in the vesa driver ... Jung-uk Kim should to fix it ...
    (freebsd-stable)
  • Re: Strange video mode output with VESA
    ... As you can see on the picture all the lines ... Do you have any idea to fix this? ... this is incorrent calculate the scan lines in the vesa driver ... Jung-uk Kim should to fix it ...
    (freebsd-stable)
  • Re: Strange video mode output with VESA
    ... On Friday 16 July 2010 03:22 pm, Jung-uk Kim wrote: ... Do you have any idea to fix this? ... this is incorrent calculate the scan lines in the vesa driver ... int i, j, k; ...
    (freebsd-stable)