On Tue, 25 Mar 2003, Martin J. Bligh wrote:
> http://bugme.osdl.org/show_bug.cgi?id=502
>
> Summary: Broken cursor when using neofb
> Kernel Version: 2.5.66
> Status: NEW
> Severity: normal
> Owner: jsimmons@infradead.org
> Submitter: jochen@jochen.org
>
>
> Distribution: Debian sarge
> Hardware Environment: IBM Thinkpad 600
>
> Problem Description:
>
> I use neofb, the boot messages are:
> Mar 25 20:04:58 gswi1164 kernel: neofb: mapped io at c680d000
> Mar 25 20:04:58 gswi1164 kernel: Autodetected internal display
> Mar 25 20:04:58 gswi1164 kernel: Panel is a 1024x768 color TFT display
> Mar 25 20:04:58 gswi1164 kernel: neofb: mapped framebuffer at c6a0e000
> Mar 25 20:04:58 gswi1164 kernel: neofb v0.4.1: 2048kB VRAM, using 1024x768, 48.361kHz, 60Hz
> Mar 25 20:04:58 gswi1164 kernel: fb0: MagicGraph 128XD frame buffer device
> Mar 25 20:04:58 gswi1164 kernel: Console: switching to colour frame buffer device 128x48
>
> On a vc the line cursor looks like
> ****** ** ********
> instead of
> ****************** (the normally continous line is broken).
> Emacs uses a block cursor that is broken similar, the block
> is broken by two vertical bars.
The VESA fbcon does exactly this as well.
I can grab my boot messages if they would help.
-- Alex Goddard agoddard@purdue.edu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:21 EST