Bug 742613

Summary: [PATCH] Anaconda text is cut in half with graphics adapter, ppc64
Product: [Fedora] Fedora Reporter: Brent Baude <bbaude>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, atodorov, gansalmon, ingvar, itamar, jonathan, karsten, kernel-maint, madhu.chinakonda, twoerner, vanmeeuwen+fedora, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: ppc64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-20 10:32:10 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 718272    
Description Flags
screenshot of anaconda
fix for snarffont, fix for alignment problems
screenfont for ppc64
updated fix for snarffont, fix for alignment problems none

Description Brent Baude 2011-09-30 14:57:04 EDT
Description of problem:
When booting the 0929 ISO on a ppc64 system with a graphics card, the text is cut in half (upper half missing -- see attached picture) after Anaconda loads.  initially the text appears fine, but when the anaconda (service?) starts, the screen flashes and all text is cut in half. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. boot 0929 on a graphics capable box

Actual results:

Expected results:

Additional info:
Comment 1 Brent Baude 2011-09-30 14:58:35 EDT
Created attachment 525808 [details]
screenshot of anaconda
Comment 2 Adam Jackson 2011-10-11 11:51:29 EDT
What graphics chip is in use on this machine?
Comment 3 Brent Baude 2011-10-11 11:59:24 EDT
we see this on a matrox g400 warp and ATI Radeon 9600
Comment 4 Karsten Hopp 2011-10-11 12:05:57 EDT
Here's the package repo that was used to create the 0929 install iso:

This is not a new issue and not related to any recent package changes, I've seen this for quite a while now.
Comment 5 Brent Baude 2011-10-18 18:08:44 EDT
Do we think this might be the culprit?

[   14.507812] systemd-vconsole-setup[351]: /bin/loadkeys failed with error code 1.
[   14.509097] systemd-vconsole-setup[351]: /bin/setfont failed with error code 1.
Comment 6 Will Woods 2011-10-18 18:16:11 EDT
Probably not. I'm guessing those errors happen because /bin/loadkeys and /bin/setfont don't exist - which is fine for the moment, because loader is going to set up the keymap/font by itself.

So: this is almost certainly a problem with loading the screenfont. The file that loader wants to load (/etc/screenfont.gz) is some magical, special screenfont file from the anaconda package, specifically for ppc64. Maybe that file is no good anymore? What would be a reasonable font file to try instead?

(Possibly we should just install loadkeys/setfont and let systemd handle it like it does on a normal system, but then we have to figure out how to make systemd change the font/keymap once you've picked a new font/keymap in loader..)
Comment 7 Karsten Hopp 2011-10-20 09:20:12 EDT
several issues here:
- we can't use the 32bit screenfont as there's a pointer to the unipair entries
  that's wrong on 64bit
- snarffont.c writes the cfo structure twice
- desc array in isysLoadFont() in pyanaconda/isys/lang.c was to small
- desc array needs to be 4 byte aligned
Comment 8 Karsten Hopp 2011-10-20 09:21:57 EDT
Created attachment 529270 [details]
fix for snarffont, fix for alignment problems
Comment 9 Karsten Hopp 2011-10-20 09:26:07 EDT
Created attachment 529271 [details]
screenfont for ppc64
Comment 10 Karsten Hopp 2011-10-20 09:35:22 EDT
Created attachment 529277 [details]
updated fix for snarffont, fix for alignment problems
Comment 11 Karsten Hopp 2011-10-20 10:44:49 EDT
Comment on attachment 529277 [details]
updated fix for snarffont, fix for alignment problems

the alignment fix is from Thomas W├Ârner
Comment 12 Karsten Hopp 2011-10-24 05:24:11 EDT
Ignore this comment, the array size is correct:
- desc array in isysLoadFont() in pyanaconda/isys/lang.c was to small
Comment 13 Chris Lumens 2011-10-24 10:46:51 EDT
Thanks for looking into this, everyone.  Ideally, any fix for this problem also involves removing our own screen font crud and just doing whatever the installed system would do, too.  anaconda has had this kind of special environment stuff (and all its associated problems) for far too long.
Comment 14 Chris Lumens 2011-10-24 10:47:21 EDT
See also:  bug 743429
Comment 15 Chris Lumens 2011-10-31 15:00:36 EDT
I've removed our font loading code in favor of just letting systemd load the real font files.  Let me know if there are other problems here.  Thanks.
Comment 16 Ingvar Hagelund 2011-11-22 04:12:38 EST
Just wanted to let you know: This is not a ppc64 specific bug. It also appears when I boot the 32bit F16 Alpha ppc image on my Apple G3 eMac. Graphics card: ATI Radeon RV200 QW [Radeon 7500].

Comment 18 Fedora End Of Life 2013-01-16 20:31:46 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: