https://bugs.freedesktop.org/show_bug.cgi?id=48304

--- Comment #2 from myxol myxolmyxmyx@yopmail.com 2012-04-04 12:55:57 PDT --- fbterm is a framebuffer terminal emulator. code.google.com/p/fbterm/ It works without Xorg -> no xorg log. I see no new messages in dmesg output on loading fbterm.

https://bugs.freedesktop.org/show_bug.cgi?id=48304

Michel Dänzer michel@daenzer.net changed:

What |Removed |Added ---------------------------------------------------------------------------- Summary|r600g: text in fbterm is |text in fbterm is garbled |garbled | Version|XOrg CVS |unspecified

--- Comment #4 from Michel Dänzer michel@daenzer.net 2012-04-04 23:35:53 PDT --- This has nothing to do with r600g.

fbterm works fine here; please also attach the output of fbset -i.

As fbterm does all rendering in software, this could be an fbterm or maybe freetype issue.

https://bugs.freedesktop.org/show_bug.cgi?id=48304

--- Comment #6 from Michel Dänzer michel@daenzer.net 2012-04-05 06:41:58 PDT --- (In reply to comment #5)

I thought if it works with vesafb it should work with radeondrmfb too.

So do I, and as I said it does work for me. Also, the kernel radeon driver isn't actively involved in getting the pixels into the framebuffer, so I'm not sure how it could be responsible for the symptoms you're seeing but am rather leaning towards fbterm or freetype being the culprit.

https://bugs.freedesktop.org/show_bug.cgi?id=48304

Michel Dänzer michel@daenzer.net changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NOTOURBUG

--- Comment #8 from Michel Dänzer michel@daenzer.net 2012-04-06 03:58:59 PDT --- (In reply to comment #7)

You're right. It's Infinality's patches for freetype. Uninstalling them makes fbterm work.

Thanks for the followup, resolving.