Bug#282234: marked as done (kernel-source-2.6.9: VesaFB doesn't work if compiled in statically)
Your message dated Mon, 4 Jul 2005 13:29:12 +0900
with message-id <20050704042912.GJ9457@verge.net.au>
and subject line Bug#279648: bug still present in 2.6.11
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Received: (at submit) by bugs.debian.org; 20 Nov 2004 16:42:57 +0000
>From firstname.lastname@example.org Sat Nov 20 08:42:57 2004
Received: from pop.gmx.de (mail.gmx.net) [22.214.171.124]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CVYK8-0000l1-00; Sat, 20 Nov 2004 08:42:57 -0800
Received: (qmail 24158 invoked by uid 65534); 20 Nov 2004 16:42:24 -0000
Received: from dialin-212-144-026-106.arcor-ip.net (EHLO trabant) (126.96.36.199)
by mail.gmx.net (mp020) with SMTP; 20 Nov 2004 17:42:24 +0100
Received: from felix by trabant with local (Exim 3.36 #1 (Debian))
id 1CVYMo-0000cK-00; Sat, 20 Nov 2004 17:45:42 +0100
Content-Type: text/plain; charset="us-ascii"
From: Felix Kuehling <email@example.com>
To: Debian Bug Tracking System <firstname.lastname@example.org>
Subject: kernel-source-2.6.9: VesaFB doesn't work if compiled in statically
X-Mailer: reportbug 2.63
Date: Sat, 20 Nov 2004 17:45:42 +0100
Sender: Felix Kuehling <email@example.com>
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
This is probably related to bug #279648. There are some reports in there
that sound like they are actually this bug.
VesaFB doesn't work (blank screen) if compiled in statically in
version 2.6.9. The same configuration worked with kernel-source-2.6.8.
If I compile VesaFB as a module and load it via /etc/modules (I don't
use initrd) the display works after the module has been loaded. Is there
any more info you need about my kernel or lilo configuration?
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=de_DE, LC_CTYPE=de_DE
Versions of packages kernel-source-2.6.9 depends on:
ii binutils 2.15-4 The GNU assembler, linker and bina
ii bzip2 1.0.2-1 A high-quality block-sorting file
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities
-- no debconf information
Received: (at 282234-done) by bugs.debian.org; 4 Jul 2005 04:54:39 +0000
>From firstname.lastname@example.org Sun Jul 03 21:54:39 2005
Received: from koto.vergenet.net [188.8.131.52]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DpIyd-0004b9-00; Sun, 03 Jul 2005 21:54:39 -0700
Received: by koto.vergenet.net (Postfix, from userid 7100)
id 6E3CD3402B; Mon, 4 Jul 2005 13:24:42 +0900 (JST)
Date: Mon, 4 Jul 2005 13:29:12 +0900
From: Horms <email@example.com>
To: Bastian Venthur <firstname.lastname@example.org>, email@example.com
Cc: firstname.lastname@example.org, email@example.com,
Subject: Re: Bug#279648: bug still present in 2.6.11
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2005_01_02
reassign 279648 kernel-source-2.6.11
reassign 282234 kernel-source-2.6.11
On Fri, Jul 01, 2005 at 03:16:29PM +0200, Bastian Venthur wrote:
> Package: kernel-source-2.6.10
> Followup-For: Bug #279648
> Hi kernel-team,
> this bug is over 1/2year old and still present in 2.6.11.
> Is it possible to upgrade this bug at least to important (if not grave?)
> -- having no display on bootup is in my opinion a really bad bug, and
> not everyone knows, that booting with vga=normal is a workaround.
> Interesting here is also, that this bug is already localized in one file
> (modular-vesafb.dpatch) since over a 1/2 year but not fixed. Is there any
> additional information I could give to help fixing this bug?
> Or is there any progress, the (many) submitters should know?
> Related (if not the same) bugs: #282234 #309682
Lets start by cleaning up the bugs. I am closing 309682 as it is a
duplicate of 279648. I am also closing 28223 as on examining the
kernel-source-2.6.11 source it appears to be fix, if someone has
experience to the contrary, please reopen it. And I am reassigning
279648 and 282234 to kernel-source-2.6.11 as it is currently assigned to
kernel-source-2.6.9 which has not been suported for quite sime time now.
I don't even think it is on d.o anymore. And as to the severity of the
bug, I don't believe the guidlines specify age as a parameter for bug
As for 279648 itself, the bug report seems to indicate that disabling
CONFIG_BLK_DEV_UB (a very green piece of code introduced in 2.6.11 bug
probably not ready for prime time) resolves the problem, and the current
kernel-images (for i386 at least) do just this. Could you take a look
in your kernel config and if CONFIG_BLK_DEV_UB is enabled, please