Saturday, December 7, 2002, 12:55:34 AM, you wrote:
>> a) Although your patch fixes the FB oddness for me, it makes booting
>> without using framebuffer fail, IOW the kernel hangs:
>>
>> Video mode to be used for restore is f00
>> BIOS-provided physical RAM map:
>> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
>>
AD> Do you have framebuffer console enabled but with no framebuffer device
AD> enabled at boot time? This will always fail with James' current patch.
AD> The diff I submitted in one of my replies in this thread (fbcon.diff)
AD> might fix that (not sure).
Thanks, that patches fixes it.
>> b) After returning from blanking mode (via APM) to normal mode, no
>> character is drawn. Let's assume I'm using VIM when that happens:
>> After putting any character to return from blank mode, the screen stays
>> blanked apart from the cursor that _is_ shown. Now I'm able to move
>> the cursor, and when the cursor encounters a character, this char
>> is drawn (and keeps drawn). Though when I press Ctrl-L or when I go one line
>> above to the current top-line (i.e. by forcing a redrawn), the
>> whole screen is drawn properly.
>>
AD> Can you try this?
AD> [..diff..]
Yes, it fixes the problem, thanks.
>> c) instruction: | produces:
>> ======================|==================
>> 1. typing abc def | $ abc def
>> | ^ (<- cursor)
>> 2. going three chars | $ abc def
>> ro the left | ^
>> 3. pressing backspace | $ abcddef
>> | ^
>> 4. pressing enter | -bash: abcdef: command not found
>> |
AD> I get this also. Seems to occur only with colored terms. When I do
AD> set TERM=vt100
AD> the problem disappears, so I thought this was an isolated case with my
AD> setup :-). Similar glitches happen also in emacs with syntax
AD> highlighting turned on.
Still there.
AD> Tony
-- cheers, Tobias- 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/