Bug 178386 - text mode codepage error?
Summary: text mode codepage error?
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-01-19 23:00 UTC by Han-Wen Nienhuys
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-01-24 18:26:13 UTC

Attachments (Terms of Use)

Description Han-Wen Nienhuys 2006-01-19 23:00:54 UTC
Description of problem:


upgrading FC4 to FC5t2 in text mode. All dialog windows look strange, as if the
wrong character set was selected. The first window (check media) is OK, the rest
of them are strange: there are no borders, and the window titles are adorned
with ^J (J with hat) and a black box.   

This on a thinkpad a21m

Comment 1 Thomas M Steenholdt 2006-01-20 09:11:06 UTC
Same on a completely different x86 box... Probably something to do with ncurses
or something

Comment 2 Chris Lumens 2006-01-23 20:43:25 UTC
What language are you installing in?  Did you add a lang= to the boot
parameters?  Also try booting with the nofb option.

Comment 3 Han-Wen Nienhuys 2006-01-23 21:06:37 UTC
Language=English. No lang= parameter. Trying nofb option now.

Comment 4 Han-Wen Nienhuys 2006-01-23 21:09:59 UTC

nofb doesn't change anything. The problems starts before the language selection;
the "Welcome to Fedora Core" already is wrong

Comment 5 Dave Burgess 2006-01-23 23:53:11 UTC
This also happens during a clean install of Core 5 Test 2.

With a nVidia GeForce 6600 GT and an Optiquest V95 Monitor.

x86_64 bit architechure.

Comment 6 Chris Lumens 2006-01-24 15:29:39 UTC
Are you both doing HTTP or FTP installs?  I'm able to reproduce it like that.

Comment 7 Han-Wen Nienhuys 2006-01-24 15:38:50 UTC
CD install.

Comment 8 Thomas M Steenholdt 2006-01-24 16:57:48 UTC
I'm doing FTP install from boot.iso with "linux text"

Didn't try CD or DVD installs for FC5test2

Comment 9 Thomas M Steenholdt 2006-01-24 19:45:33 UTC
Pardon my curiosity, but what caused the problem?

Comment 10 Chris Lumens 2006-01-24 21:11:56 UTC
We use dietlibc instead of the full libc on these network install images to keep
the size down.  This includes some stubs of utf-8 related functions to trick our
interface into working correctly.  We weren't stubbing out enough functions, so
consequently something in the interface was calling a function that didn't exist
and resulting in the junk you were seeing on the screen.

Comment 11 Thomas M Steenholdt 2006-01-24 22:25:34 UTC
makes sense - thanks for the update

Note You need to log in before you can comment on or make changes to this bug.