Introduction

Overview of open issues and things to be done for the ["DebianInstaller/GUI"].

A complete list of bugs affecting the g-i can be found in the [http://bugs.debian.org/cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb] page.

?TableOfContents([2])

Per-architecture issues

We're trying to schematize bugs affecting the g-i on a per-architecture base, architectures considered here are i386, PPC, AMD64 .

i386 specific

AMD64 specific

PPC specific

PPC is the most problematic architecture of the three to be supported because ?DirectFrameBuffer seems particulary willing to crash on those machines (we currently experienced more failures that successes) Right now HW acceleration provided by DFB seems to be broken for almost every suported video chipset on PPCs, so it was forced off by default. Read also this long [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342053 thread] about the g-i on PPC machines.

Test date

Machine

Videocard

fb driver

DFBversion

DFB HW acceleration

result

?

?

Radeon9800 (r300)

radeonfb

0.9.25

off

Crash

?

?

Radeon9200

radeonfb

0.9.25

off

Ok

?

?

unknown

atyfb

0.9.22

off

crash

?

?

unknown

nvidiafb

0.9.22

off

crash

2006-09-26

?PowerBook4,3 MacRISC2 MacRISC Power Macintosh

Mobility 7500

radeonfb

0.9.25

off

crash

TODO

Porting

The graphical version of the installer is currently available for Intel x86, AMD64 and PowerPC. The PowerPC port [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341597 needs work] to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.

Fonts

For font information, please see ["DebianInstaller/GUIFonts"]

Usability

Interface design

Most of the work on the graphical side has been done by Eduardo Silva. He has set up a [http://www.geocities.com/jobezone/d-i_gtk.html webpage] with images he designed and some comments about possible future changes.

Reduce size of initrds

The initrds are currently very large which also results in fairly high memory requirements to run the graphical installer. Size has thus far not been a major concern, our focus has been on getting things working.

Options to reduce initrd size.

Update The size of the initrds is now down to around 10MB. Further reduction would be nice, but it is no longer a major issue.