Bug 48304 - text in fbterm is garbled
Summary: text in fbterm is garbled
Status: RESOLVED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-04 10:13 UTC by myxol
Modified: 2012-04-06 03:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
screen cap (14.55 KB, image/png)
2012-04-04 10:13 UTC, myxol
no flags Details
dmesg output (37.43 KB, text/plain)
2012-04-04 13:45 UTC, myxol
no flags Details
fbset -i (412 bytes, text/plain)
2012-04-05 05:56 UTC, myxol
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description myxol 2012-04-04 10:13:03 UTC
Created attachment 59485 [details]
screen cap

Worked for me when I used vesafb and fglrx.
Comment 1 Alex Deucher 2012-04-04 11:04:57 UTC
I'm not familiar with fbterm.  Is it an X app?  How does it render?  GL?  Please attach your xorg log and dmesg output.
Comment 2 myxol 2012-04-04 12:55:57 UTC
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.
Comment 3 myxol 2012-04-04 13:45:17 UTC
Created attachment 59493 [details]
dmesg output

In case you wanted full dmesg output, here it is.
Comment 4 Michel Dänzer 2012-04-04 23:35:53 UTC
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.
Comment 5 myxol 2012-04-05 05:56:17 UTC
Created attachment 59520 [details]
fbset -i

I thought if it works with vesafb it should work with radeondrmfb too. If it's not the case… I'm sorry.
Comment 6 Michel Dänzer 2012-04-05 06:41:58 UTC
(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.
Comment 7 myxol 2012-04-05 12:32:27 UTC
> freetype being the culprit
You're right. It's Infinality's patches for freetype. Uninstalling them makes fbterm work. Ugly fonts in X apps though…
Comment 8 Michel Dänzer 2012-04-06 03:58:59 UTC
(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.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.