Debian Bug report logs - #279648
kernel-source-2.6.9: Boot : console vga mode problem

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "B. Zhang" <bb.zhang@free.fr>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: kernel-source-2.6.9: Boot : console vga mode problem

Date: Thu, 04 Nov 2004 12:05:48 +0100

Package: kernel-source-2.6.9
Version: 2.6.9-1
Severity: normal

If I boot in vga mode vga=791, the blank screen appears, can't see
anything on the console screen.
The system appears to boot okay, I get a xdm login.

No problem when booting in normal mode.
No problem in mode vga=791 with the same .config for kernel-source-2.6.8-7.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9.20041104
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

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

Message #10 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>

To: Debian Bug Tracking System <279648@bugs.debian.org>

Subject: kernel-source-2.6.9: no console on vga mode

Date: Fri, 05 Nov 2004 00:22:26 +0100

Package: kernel-source-2.6.9
Version: 2.6.9-1
Followup-For: Bug #279648

same problem here with vga=0x318, config is same as from
kernel-image-2.6.9-1-686 exept # CONFIG_BLK_DEV_UB is not set where the
console is OK.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

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

-- no debconf information

Message #15 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Horms <horms@debian.org>

To: "B. Zhang" <bb.zhang@free.fr>, 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: Boot : console vga mode problem

Date: Fri, 5 Nov 2004 13:06:34 +0900

On Thu, Nov 04, 2004 at 12:05:48PM +0100, B. Zhang wrote:
> Package: kernel-source-2.6.9
> Version: 2.6.9-1
> Severity: normal
> 
> If I boot in vga mode vga=791, the blank screen appears, can't see
> anything on the console screen.
> The system appears to boot okay, I get a xdm login.
> 
> No problem when booting in normal mode.
> No problem in mode vga=791 with the same .config for kernel-source-2.6.8-7.

Which frame buffer driver are you using?

-- 
Horms

Message #20 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Horms <horms@debian.org>

To: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>, 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Fri, 5 Nov 2004 16:07:55 +0900

On Fri, Nov 05, 2004 at 12:22:26AM +0100, Klaus Maria Pfeiffer wrote:
> Package: kernel-source-2.6.9
> Version: 2.6.9-1
> Followup-For: Bug #279648
> 
> same problem here with vga=0x318, config is same as from
> kernel-image-2.6.9-1-686 exept # CONFIG_BLK_DEV_UB is not set where the
> console is OK.

Could you please clarify what you wrote above?

Are you saying that when CONFIG_BLK_DEV_UB is disabled the
conslole works fine? Or that the only config change is CONFIG_BLK_DEV_UB
but the console doesn't work anyway.

Thanks

-- 
Horms

Message #25 received at 279648@bugs.debian.org (full text, mbox, reply):

From: "B. Zhang" <bb.zhang@free.fr>

To: Horms <horms@debian.org>

Cc: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: Boot : console vga mode problem

Date: Fri, 05 Nov 2004 10:32:39 +0100

On Fri, 2004-11-05 at 13:06 +0900, Horms wrote:
> On Thu, Nov 04, 2004 at 12:05:48PM +0100, B. Zhang wrote:
> > Package: kernel-source-2.6.9
> > Version: 2.6.9-1
> > Severity: normal
> > 
> > If I boot in vga mode vga=791, the blank screen appears, can't see
> > anything on the console screen.
> > The system appears to boot okay, I get a xdm login.
> > 
> > No problem when booting in normal mode.
> > No problem in mode vga=791 with the same .config for kernel-source-2.6.8-7.
> 
> Which frame buffer driver are you using?
> 
>From my .config
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_MODE_HELPERS is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set

Message #30 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>

To: Horms <horms@debian.org>

Cc: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Fri, 5 Nov 2004 11:07:36 +0100

On Friday 05 November 2004 08:07, Horms wrote:
> On Fri, Nov 05, 2004 at 12:22:26AM +0100, Klaus Maria Pfeiffer wrote:
> > Package: kernel-source-2.6.9
> > Version: 2.6.9-1
> > Followup-For: Bug #279648
> >
> > same problem here with vga=0x318, config is same as from
> > kernel-image-2.6.9-1-686 exept # CONFIG_BLK_DEV_UB is not set where the
> > console is OK.
>
> Could you please clarify what you wrote above?

sorry, I'll clarify.

> Are you saying that when CONFIG_BLK_DEV_UB is disabled the
> conslole works fine? Or that the only config change is CONFIG_BLK_DEV_UB
> but the console doesn't work anyway.

I'm running all kernels with vga=0x318.


o kernel-image-2.6.8-1-686 (2.6.8-4):
console is ok

o kernel-image-2.6.9-1-686 (2.6.9-1):
console is ok
does a kernel panic in timer.c:414 (imho because of the new introduced block 
device UB)

o the selfbuilt kernel with make-kpkg from kernel-source-2.6.9 (2.6.9-1):
console is NOT ok (nothing displaying, but kde is ok)
no problems with UB, because it's disabled.


find the changes between the .config of the original debian 
kernel-image-2.6.9-1-686 and my selfmade kernel from kernel-source-2.6.9:
;===
klaus@ragnarok:/boot$ diff config-2.6.9 config-2.6.9-1-686
3,4c3,4
< # Linux kernel version: 2.6.9
< # Thu Nov  4 23:18:47 2004
---
> # Linux kernel version: 2.6.9-1-686
> # Sun Oct 31 03:39:00 2004
75c75
< # CONFIG_M686 is not set
---
> CONFIG_M686=y
78c78
< CONFIG_MPENTIUMM=y
---
> # CONFIG_MPENTIUMM is not set
93c93
< CONFIG_X86_L1_CACHE_SHIFT=6
---
> CONFIG_X86_L1_CACHE_SHIFT=5
94a95
> CONFIG_X86_PPRO_FENCE=y
100d100
< CONFIG_X86_INTEL_USERCOPY=y
463c463
< # CONFIG_BLK_DEV_UB is not set
---
> CONFIG_BLK_DEV_UB=m
;===

as you can see, I've only changed the architecture (which has imho no 
influence on the bug) and UB devices.

greetings & hth, Klaus

Message #35 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Jens Schmalzing <j.s@lmu.de>

To: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>

Cc: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: 05 Nov 2004 11:32:37 +0100

Hi,

Klaus Maria Pfeiffer writes:

> I'm running all kernels with vga=0x318.

> o the selfbuilt kernel with make-kpkg from kernel-source-2.6.9 (2.6.9-1):
> console is NOT ok (nothing displaying, but kde is ok)

> find the changes between the .config of the original debian 
> kernel-image-2.6.9-1-686 and my selfmade kernel from kernel-source-2.6.9:

> as you can see, I've only changed the architecture (which has imho no 
> influence on the bug) and UB devices.

With the command line argument vga=0x318, you are initially switching
the console into a VESA mode.  So in order to display anything, you
need the vesafb driver.  In the official i386 Debian kernel, vesafb is
a module, and is symlinked into /lib/modules/<version>/initrd.  From
there, it is added to the initrd and loaded right after the initrd
starts.  Your self-compiled kernel also has vesafb built as a module,
since you didn't change the setting, but is probably missing the
symlink.

Regards, Jens.

-- 
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!

Message #40 received at 279648@bugs.debian.org (full text, mbox, reply):

From: "B. Zhang" <bb.zhang@free.fr>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: Boot : console vga mode problem

Date: Fri, 05 Nov 2004 13:52:29 +0100

I have just tested the kernel source 2.6.9 from http://www.kernel.org
with the same .config.
No problem, I can have vga=791 and console.

Message #45 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Fri, 5 Nov 2004 14:38:49 +0100

On Friday 05 November 2004 11:32, Jens Schmalzing wrote:
> Klaus Maria Pfeiffer writes:
> > I'm running all kernels with vga=0x318.
> >
> > o the selfbuilt kernel with make-kpkg from kernel-source-2.6.9 (2.6.9-1):
> > console is NOT ok (nothing displaying, but kde is ok)
> >
> > find the changes between the .config of the original debian
> > kernel-image-2.6.9-1-686 and my selfmade kernel from kernel-source-2.6.9:
> >
> > as you can see, I've only changed the architecture (which has imho no
> > influence on the bug) and UB devices.
>
> With the command line argument vga=0x318, you are initially switching
> the console into a VESA mode.  So in order to display anything, you
> need the vesafb driver.  In the official i386 Debian kernel, vesafb is
> a module, and is symlinked into /lib/modules/<version>/initrd.

why is it symlinked or copied to the location specified by you in the official 
debian kernel but not with make-kpkg. i can't find any parameter of make-kpkg 
for defining this or any other solution, except compiling the vesafb static 
into the kernel instead as module. (see also
Message-ID: <1PYyx-6K2-3@gated-at.bofh.it> and
Message-ID: <ICEs.2ia.7@gated-at.bofh.it> )

> From 
> there, it is added to the initrd and loaded right after the initrd
> starts.  Your self-compiled kernel also has vesafb built as a module,
> since you didn't change the setting, but is probably missing the
> symlink.

ok, the bug was in front of the display, sorry.

from my side, the bug can be closed; I haven't opened the bug.

greetings & thanks, Klaus

Message #50 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Mudrony Laszlo <mudry@mudry.hu>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: Boot : console vga mode problem

Date: Fri, 05 Nov 2004 14:41:05 +0100

B. Zhang wrote:

>I have just tested the kernel source 2.6.9 from http://www.kernel.org
>with the same .config.
>No problem, I can have vga=791 and console.
>
>
>  
>
Sorry about not providing further debug info, I only intendend the 
follwing as a note that might help.
(The affected machines are not ready at hand, but please ask if more 
info is needed)

I did experience this problem using 2.6.9 with a statically built rivafb 
module, and
using 2.6.10-rc1 with a statically compiled viafb driver (from patch).

When the drivers are compiled statically and the vga option is given 
then there IS a video mode
switch at boot time (wich might come from grub as well which is in 
grapnic mode displaying a 640x480 splash)
but the screen remains blank.

If I compile the drivers into a module and boot without the vga option 
the drivers initialize
properly when i load them with insmod. (Although they clear the screen 
with white, wich is
not a problem, but annoying, and as far as I know this artefact is 
present since long time..)

I use vga=0x318, and I give all the explicit mode, depth, refresh, etc
information with a video=viafb:... video=rivafb:... option the driver 
can parse
(I looked them up in the kernel sources). I'm sure these options are OK 
since they work well
when passed to insmod.

Note: both kernels has the DirectFB fusion patch on them, which is 
standalone character device
and im quite sure they do not affect the fb drivers.

Hope this helps. I'm quite fine with using modules, but having the 
display properly set from the start of the boot would be nice.

Message #55 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Jens Schmalzing <j.s@lmu.de>

To: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>

Cc: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: 05 Nov 2004 15:40:42 +0100

Hi,

Klaus Maria Pfeiffer writes:

> why is it symlinked or copied to the location specified by you in
> the official debian kernel but not with make-kpkg.

The official Debian kernel does use make-kpkg, but feeds it a
post-install script that sets the link (actually, it's not symbolic
but hard).  If you want this for your self-built kernel, put the
script from

<URL:http://svn.debian.org/viewcvs/kernel/trunk/kernel/i386/kernel-ima
ge-2.6.9-i386-2.6.9/post-install?view=auto&rev=1770>

into the debian directory of your kernel tree.

> from my side, the bug can be closed; I haven't opened the bug.

Thanks.  Still, the original submitter hasn't replied yet, so I am
leaving the bug open.

Regards, Jens.

-- 
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!

Message #60 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Klaus Maria Pfeiffer <kmp.debian@kmp.or.at>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Fri, 5 Nov 2004 17:18:18 +0100

hi!

On Friday 05 November 2004 15:40, Jens Schmalzing wrote:

> Klaus Maria Pfeiffer writes:
> > why is it symlinked or copied to the location specified by you in
> > the official debian kernel but not with make-kpkg.
>
> The official Debian kernel does use make-kpkg, but feeds it a
> post-install script that sets the link (actually, it's not symbolic
> but hard).

why is this script not in the kernel-source package? is it a good idea to put 
this scripts into the kernel-source package?

where should we discuss this? a bug report is imho not a good place. 

> If you want this for your self-built kernel, put the 
> script from
> <URL:http://svn.debian.org/viewcvs/kernel/trunk/kernel/i386/kernel-ima
> ge-2.6.9-i386-2.6.9/post-install?view=auto&rev=1770>
> into the debian directory of your kernel tree.

thanks a lot, now it's really all ok.

greetings, Klaus

Message #65 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Julien Valroff <julien@kirya.net>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Fri, 5 Nov 2004 17:23:51 +0100

Hi,

I also 'suffer' from this bug, and I still do not understand why the same 
configuration works with a 2.6.8 kernel, and not with a 2.6.9.
Could somebody try and explain?

More over, how do you compile the vesafb driver static into the kernel?
CONFIG_FB_VESA=y is not enough?

Cheers,
Julien

Message #70 received at 279648@bugs.debian.org (full text, mbox, reply):

From: "B. Zhang" <bb.zhang@free.fr>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Fri, 05 Nov 2004 18:37:08 +0100

> I also 'suffer' from this bug, and I still do not understand why the 
> same configuration works with a 2.6.8 kernel, and not with a 2.6.9.
> Could somebody try and explain?

> More over, how do you compile the vesafb driver static into the kernel?
> CONFIG_FB_VESA=y is not enough?

> Cheers,
> Julien

The same config works also with the kernel 2.6.9 from www.kernel.org

Regards, 
Benoit

Message #75 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Maximiliano Pin <mad.max@ya.com>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Sun, 7 Nov 2004 11:08:47 +0100

I have the same problem. I don't use initrd. I compile framebuffer static:
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FB_VESA=y
The same exact configuration worked on 2.6.5.
I also tried setting the new CONFIG_FB_MODE_HELPERS, with the same results.
You talked about closing this bug, but I believe the bug is only closed for
those using initrd. I understand the debian/postinstall you indicated
generates an initrd, which I don't need.
-- 
Maximiliano Pin
Powered by Debian GNU/Linux

Message #80 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Horms <horms@debian.org>

To: Maximiliano Pin <mad.max@ya.com>, 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Mon, 8 Nov 2004 12:47:12 +0900

On Sun, Nov 07, 2004 at 11:08:47AM +0100, Maximiliano Pin wrote:
> I have the same problem. I don't use initrd. I compile framebuffer static:
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_FB_VESA=y
> The same exact configuration worked on 2.6.5.
> I also tried setting the new CONFIG_FB_MODE_HELPERS, with the same results.
> You talked about closing this bug, but I believe the bug is only closed for
> those using initrd. I understand the debian/postinstall you indicated
> generates an initrd, which I don't need.

I would suggest that you are experienceing a differrent problem.
The problem for most people seems to relate to the
vb modules not being inserted and thus the console being blank.
That is trivially fixed by making sure the right modules end
up in the initrd image.

The problem you are seeing would seem to be that the driver is
present but it the console is still not working. Are you sure
that _all_ the drivers you need are compiled in or available as modules?

-- 
Horms

Message #85 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Laurent Vallar <val@linuxfr.org>

To: Debian Bug Tracking System <279648@bugs.debian.org>

Subject: kernel-source-2.6.9: Blank console when using VGA/framebuffer device (compiled in)

Date: Mon, 08 Nov 2004 14:42:54 +0100

Package: kernel-source-2.6.9
Followup-For: Bug #279648

As many reports i got the same problem when enabling VGA console : a
definitly blank screen.

I never use initrd and always add all necessary modules needed for VGA
framebuffer console (using old kernel configuration). Same configuration
works fine with vanilla sources.

You can get my own kernel configuration files at
http://vallar.linuxfr.org/debian

Regards,
Val.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (66, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-586-val-vs1.9.2-orinoco-0.13e-dragorn-lbtouch-0.5.3.1
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (ignored: LC_ALL set to fr_FR@euro)

Message #90 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Maximiliano Pin <mad.max@ya.com>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Mon, 8 Nov 2004 21:40:59 +0100

> I would suggest that you are experienceing a differrent problem.
> The problem for most people seems to relate to the
> vb modules not being inserted and thus the console being blank.
> That is trivially fixed by making sure the right modules end
> up in the initrd image.
> 
> The problem you are seeing would seem to be that the driver is
> present but it the console is still not working. Are you sure
> that _all_ the drivers you need are compiled in or available as modules?

There are maybe two related bugs here, but note than both the original
sender (Zhang, in his second mail) and Mudrony Laszlo, reported to be
compiling framebuffer static, and experiencing this problem (just like me).
Yes, all the drivers I need (the same I used on 2.6.5) are compiled in
(none as module, I have never compiled fb as module).
It looks like now, in 2.6.9, fb initialization only happens when loading it
as a module.
-- 
Maximiliano Pin
Powered by Debian GNU/Linux

Message #95 received at 279648@bugs.debian.org (full text, mbox, reply):

From: James Stark <starkj@uoguelph.ca>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Wed, 10 Nov 2004 01:11:09 -0500

Hi,

I'm experiencing a similar problem, so I'm going to throw what I'm seeing into 
the pot.

I'm running 2.6.9 on two different machines with slightly different 
configurations.  Both have the framebuffer drivers statically compiled into 
the kernel.  One machine uses the VESA frame buffer and with vga=318 I get a 
blank screen as described in the previous posts.  Furthermore looking in 
sysfs there no sign of class/graphics/fb0.  On the other machine where I'm 
using the radeon framebuffer (this is the only change to the graphics config) 
it works fine.  

I'm also seeing a similar problem with the printer driver as with the vesa 
driver.  It is statically compiled into the kernel, however there is no sign 
that it exists.  The sysfs entry under class/printers is missing.  This makes 
me wonder if both of these are symptoms of a different problem.  

I should mention that the same configuration worked for me under kernel 2.6.7 
in both cases.

I'm attaching the graphics section of the kernel configurations for both 
machines for reference.  I'll make the full configuration file(s) available 
if they are needed.

James

Graphics Config for the machine using the VESA framebuffer driver.

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y


Graphics Config for the machine using the radeon framebuffer driver.

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_VIDEO_SELECT is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

Message #100 received at 279648@bugs.debian.org (full text, mbox, reply):

From: toupeira <markus-koller@gmx.ch>

To: 279648@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: no console on vga mode

Date: Sat, 13 Nov 2004 16:51:38 +0100

Hi,

Same problem here, vesafb doesn't work anymore since I upgraded from
2.6.8. I too get a black screen, I tried with and without
CONFIG_FB_MODE_HELPERS, but it didn't help. I also have everything
compiled in.


Here's my config:
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set


greetings,
Markus

Message #105 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Lukas Matasovsky <lumat@gmx.at>

To: Debian Bug Tracking System <279648@bugs.debian.org>

Subject: kernel-source-2.6.9: Rebuild from 2.6.9-1-k7-smp > no FB support

Date: Sat, 13 Nov 2004 19:59:32 +0100

Package: kernel-source-2.6.9
Version: 2.6.9-1
Followup-For: Bug #279648

Hi, run across same / related here:

1. tried to rebuild kernel image from 2.6.9-1 config > vga=791 does not
work

2. tried to build with set:
CONFIG_FB=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

> vga=791 does not work
Compiling it like this since ever worked or did I miss something?

3. built with 2nd config from kernel.org sources > vga=791 works

I do have a nvidia card in my box, therefore I do not set these:
# CONFIG_FB_RIVA is not set
# CONFIG_FB_RIVA_I2C  is not set
# CONFIG_FB_RIVA_DEBUG is not set
... as recommended by nvidia
I build the nvidia module apart from the kernel and a recent nvidia card
should be VESA compatible anyway.

btw., I do not understand *why* this should not be a bug (if its not a
feature).

lg,

Lukas

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-mts-k7-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

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

Message #110 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Sebastian Hoffmann <sebastian.hoffmann@gmail.com>

To: 279648@bugs.debian.org

Subject: vesafb Problems

Date: Sun, 14 Nov 2004 16:51:00 +0100

Hi,
I had the same problem.
My .config runs fine with 2.6.7. Under 2.6.9 with vesafb compiled into
the kernel, I dont saw anything at boot, and in dmesg was nothing
about vesafb.
If you compile it as module and load it with initrd, it work.
After i removed the modular-vesafb.dpatch it work also when i compile
it into the Kernel.

Message #115 received at 279648@bugs.debian.org (full text, mbox, reply):

From: "B. Zhang" <bb.zhang@free.fr>

To: 279648@bugs.debian.org

Subject: vesafb.c

Date: Sat, 20 Nov 2004 01:13:08 +0100

If I replace drivers/video/vesafb.c by that from kernel.org sources, I
see the console. I think the problem is in the debian vesafb.c.

Message #120 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Sebastian Bork <sebi@sebi.org>

To: Debian Bug Tracking System <279648@bugs.debian.org>

Subject: kernel-source-2.6.9: modular-vesafb.dpatch buggy

Date: Wed, 24 Nov 2004 07:52:36 +0100

Package: kernel-source-2.6.9
Version: 2.6.9-2
Followup-For: Bug #279648

This also applies to #282234.

Could it be that line 47 of modular-vesafb.dpatch is the problem?
There's a "charp" where there should be just "char", I think.
Unfortunately, I have no time for testing until somewhen this
evening (CET).

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

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

Message #123 received at 279648-submitter@bugs.debian.org (full text, mbox, reply):

From: Andres Salomon <dilinger@voxel.net>

To: 279648-submitter@bugs.debian.org

Subject: Re: Bug#279648: kernel-source-2.6.9: modular-vesafb.dpatch buggy

Date: Wed, 24 Nov 2004 17:05:52 -0500

On Wed, 24 Nov 2004 07:52:36 +0100, Sebastian Bork wrote:

> Package: kernel-source-2.6.9
> Version: 2.6.9-2
> Followup-For: Bug #279648
> 
> This also applies to #282234.
> 
> Could it be that line 47 of modular-vesafb.dpatch is the problem?
> There's a "charp" where there should be just "char", I think.
> Unfortunately, I have no time for testing until somewhen this
> evening (CET).
> 

I'm pretty sure that should be a charp; options is a char*, and
vesafb_setup() treats it as a string (ie, calling strsep(&options, ",") on
it).

Message #128 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Sebastian Bork <sebi@sebi.org>

To: Debian Bug Tracking System <279648@bugs.debian.org>

Subject: Re: kernel-source-2.6.9: modular-vesafb.dpatch buggy

Date: Fri, 26 Nov 2004 13:16:07 +0100

* Sebastian Bork schrieb am 24.11.04 um 07:52 Uhr:
> Could it be that line 47 of modular-vesafb.dpatch is the problem?

Okay, it was just a wild guess. However, the problem hast to be
somewhere in the patches - everything works fine with the kernel.org
source of vesafb.c, but as soon as I try the Debian version, I get a
blank screen at bootup, just like the others. Even compiling it as a
module and adding a line to /etc/modules did not help.

I use a Nvidia Riva TNT, by the way.

Message #135 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Bastian Venthur <expires-2006@venthur.de>

To: Debian Bug Tracking System <279648@bugs.debian.org>

Subject: bug still present in 2.6.11

Date: Fri, 01 Jul 2005 15:16:29 +0200

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


kind regards

Bastian

PS: I have a savage-card. I've tried  vesafb and savagefb but both
drivers produce the blank screen on bootup. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-laptop
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Message #140 received at submit@bugs.debian.org (full text, mbox, reply):

From: Horms <horms@debian.org>

To: Bastian Venthur <expires-2006@venthur.de>, 279648@bugs.debian.org

Cc: 309682-done@bugs.debian.org, submit@bugs.debian.org, 282234-done@bugs.debian.org

Subject: Re: Bug#279648: bug still present in 2.6.11

Date: Mon, 4 Jul 2005 13:29:12 +0900

reassign 279648 kernel-source-2.6.11
reassign 282234 kernel-source-2.6.11
thanks


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
seveirty.

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
disable it.

Thanks

-- 
Horms

Message #152 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Jurij Smakov <jurij@wooyd.org>

To: 279648@bugs.debian.org, 279648-submitter@bugs.debian.org

Cc: Bastian Venthur <expires-2006@venthur.de>

Subject: Re: Bug#279648: bug still present in 2.6.11

Date: Wed, 12 Apr 2006 21:47:07 -0700 (PDT)

Hi Bastian,

In July 2005 you've reported that Debian bug [0] is still present in 
kernel 2.6.11. In the meantime the kernel team have dropped most of the 
Debian-specific patches, including modular-vesafb.patch which you've 
identified as the source of the problem. I would appreciate if you could 
confirm that the bug is still present in any Debian kernel currently in 
the archive. Otherwise I plan to close this bug in two weeks from today, 
on April 26, 2006.

[0] http://bugs.debian.org/279648

Best regards,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

Message #160 received at 279648@bugs.debian.org (full text, mbox, reply):

From: Bastian Venthur <mail@venthur.de>

To: jurij@wooyd.org

Cc: 279648@bugs.debian.org, 279648-submitter@bugs.debian.org

Subject: Re: Bug#279648: bug still present in 2.6.11

Date: Thu, 13 Apr 2006 07:51:34 +0200

Hi Jurij,

Due this bug, I had to use a self cooked kernel for several months, but
as I returned to the Debian kernels a while ago, I've not noticed this
bug anymore. So I guess this bug can be closed.


Kind regards,

Bastian

Message #168 received at 279648-done@bugs.debian.org (full text, mbox, reply):

From: Jurij Smakov <jurij@wooyd.org>

To: 279648-done@bugs.debian.org

Subject: Re: Bug#279648: bug still present in 2.6.11

Date: Wed, 12 Apr 2006 23:15:49 -0700 (PDT)

On Thu, 13 Apr 2006, Bastian Venthur wrote:

> Hi Jurij,
>
> Due this bug, I had to use a self cooked kernel for several months, but
> as I returned to the Debian kernels a while ago, I've not noticed this
> bug anymore. So I guess this bug can be closed.

Closing as requested, thanks for you feedback.

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

Send a report that this bug log contains spam.