Your message dated Fri, 28 Feb 2014 20:52:45 +0100 with message-id <20140228195245.GA29086@mraw.org> and subject line Re: Bug#290366: Should this bug be closed ?? has caused the Debian Bug report #290366, regarding bootloader doesn't set VESA mode on x86, so vesafb is never loaded to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 290366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=290366 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: bootloader doesn't set VESA mode on x86, so vesafb is never loaded
- From: Matthew Garrett <mjg59@srcf.ucam.org>
- Date: Thu, 13 Jan 2005 20:00:42 +0000
- Message-id: <E1CpB9E-00033e-00@master.debian.org>
Package: debian-installer Severity: normal For vesafb to work, the kernel bootloader needs to set up a VESA mode. This is typically done by passing something like vga=0x301 (which will set a 256 colour 640x480 display). If this succeeds, vesafb should load and work correctly. Otherwise, the system will fall back to vga16fb when the vesafb modprobe fails. Currently, vga16fb is loaded unconditionally. I have a machine here that works correctly with vesafb but fails with vga16fb. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
- To: 290366-done@bugs.debian.org
- Cc: Attilio Fiandrotti <attilio.fiandrotti@gmail.com>, Matthew Garrett <mjg59@srcf.ucam.org>
- Subject: Re: Bug#290366: Should this bug be closed ??
- From: Cyril Brulebois <kibi@debian.org>
- Date: Fri, 28 Feb 2014 20:52:45 +0100
- Message-id: <20140228195245.GA29086@mraw.org>
- In-reply-to: <200611140616.58693.elendil@planet.nl>
- References: <45588AA2.5060402@gmail.com> <200611140616.58693.elendil@planet.nl>
Frans Pop <elendil@planet.nl> (2006-11-14): > On Monday 13 November 2006 16:09, Attilio Fiandrotti wrote: > > I accidentally ran into this bug. > > We currently set the vesafb fbdev in 800x600@75 in images containing > > the GTK frontend at least: should this bug be closed? > > IMO not as the BR is not about the graphical installer, but about display > problems using the newt frontend. src:debian-installer has: | commit 63d9d35e4d0306ca3c1ae2b4848140782342a2d1 | Author: Frans Pop <fjp@debian.org> | Date: Sat Oct 10 12:01:55 2009 +0000 | | Change default video mode for i386/amd64 to vga=788 for the "newt" frontend so closing this bug report. Mraw, KiBi.Attachment: signature.asc
Description: Digital signature
--- End Message ---