[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#604101: installation-reports: Broken textmode installer

Again just my 2 cents but I wouldn't  think text would be for "most computers", graphical install I would see as typical. Text mode would be for the installer cant seem to talk to my hardware let's go basic till we get to the point where I can specify parameters or load non standard drivers. In any case I wasn't trying to start a debate mearly to report that install was failing for same reason in the bug report on the IBM x236 server hardware and I suppose I was venting a little bit because I didn't expect to have graphical issues in a "text mode" install. 

Sent from my iPhone

On 2011-07-13, at 4:32 PM, Christian PERRIER <bubulle@debian.org> wrote:

> Quoting Lennart Sorensen (lsorense@csclub.uwaterloo.ca):
>> On Wed, Jul 13, 2011 at 02:10:03PM -0400, Jeff Arbour wrote:
>>> Same issue applies on IBM x236 server, was about to shelve debian and start
>>> picking a new distro until I found this report. It never once occurred to me
>>> that when choosing a text based install the installer would attempt to use a
>>> graphic mode to do it in. The seems like broken administration of the
>>> installer, rather than a technical mal-function.  The whole purpose of text
>>> mode imo is to give a generic works on any device environment as a fail safe
>>> when graphical install fails or is not feasible. No vga mode should ever be
>>> set for this option, nor anything that even considers a frame buffer. The
>>> issue is very easy to resolve once understood, but this is a never should
>>> have happened in the first place error to rival "No keyboard detected, Press
>>> F1 to continue".
>> And how would you do say japanese text without a framebuffer?
>> A framebuffer running text is not the same as a graphical install (which
>> has windows, and mouse support and such).
>> In fact a none frmaebuffer text mode is a rather unique thing on PCs,
>> and of course on serial consoles. Most other systems have only frame
>> buffers for their console.
> And we should close this bug report, I agree...
> There are instructions in the installation manual about booting the
> installer without framebuffer.....and avoid this bug without giving
> lessons to people who are developing the said installer..:-)

Reply to: