Re: 2.6.23: No text consoles with FRAMEBUFFER_CONSOLE_DETECT_PRIMARY

Re: 2.6.23: No text consoles with FRAMEBUFFER_CONSOLE_DETECT_PRIMARY

[Antonino A. Daplas]

On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
> While running a test with current Linus' git tree, I ran into the following
> issue. The issue is also present in stable 2.6.23.
> 
> System x86_64; Pentium D; Intel 82945G/GZ on-board graphics
> 
> After initial boot messages all output to console stops. The last visible
> messages are:
> checking if image is initramfs...<6>Switched to high resolution mode on CPU 1
> Switched to high resolution mode on CPU 0
> 
> After that, nothing until XOrg starts up and graphical login/desktop on VT7
> are displayed normal.
> Switching back to VT1-VT5 gives nothing: no login prompts, just nothing.
> 

Can you also post your dmesg and /proc/cdmline?

Tony

Re: 2.6.23: No text consoles with FRAMEBUFFER_CONSOLE_DETECT_PRIMARY

[Antonino A. Daplas]

On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:

> I could solve this issue in two ways:
> - boot with VGA=791 parameter (initial boot was without VGA= parameter)
> - compile kernel without FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set (I also
>   unset FB_VIRTUAL, but without its boot param that should be a no-op)

After looking at vfb.c again, it seems the default is for vfb to be
enabled and you have to actively disable vfb either with

video=vfb:disable or video=vfb:off

I have to change this behavior. In the meantime, try one of the above
options.

(I was also under the impression that vfb must be explicitly enabled
with a boot option...I remember now, the option vfb_enable defaults to
false when compiled as a module, and to true if compiled statically.)

Tony

Re: 2.6.23: No text consoles with FRAMEBUFFER_CONSOLE_DETECT_PRIMARY

[Frans Pop]

On Sunday 14 October 2007, Antonino A. Daplas wrote:
> On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
> > I could solve this issue in two ways:
> > - boot with VGA=791 parameter (initial boot was without VGA= parameter)
> > - compile kernel without FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set (I also
> >   unset FB_VIRTUAL, but without its boot param that should be a no-op)
>
> After looking at vfb.c again, it seems the default is for vfb to be
> enabled and you have to actively disable vfb either with
>
> video=vfb:disable or video=vfb:off

Yes, that works as well.

> I have to change this behavior. In the meantime, try one of the above
> options.

No real need. I normally boot with vga=791 (which is also why I did not
see this during my testing of 2.6.23-rc*).

On Sunday 14 October 2007, Antonino A. Daplas wrote:
> Can you also post your dmesg and /proc/cdmline?

Guess that's no longer really needed, but here are the relevant lines from a
dmesg diff between kernels with and without FB_CONSOLE_DETECT_PRIMARY.

<snip>
 Command line: root=/dev/sdb1 ro
[...]
 Console: colour VGA+ 80x25
 console [tty0] enabled
[...]
 checking if image is initramfs...<6>Switched to high resolution mode on CPU 1
 Switched to high resolution mode on CPU 0
[console output stopped here]
  it is
[...] (omitted about 30 lines)
-Console: switching to colour frame buffer device 80x25
-fb0: Virtual frame buffer device, using 1024K of video memory
</snip>

Thanks for quick reaction. Let me know if you'd like a patch tested.

Cheers,
FJP

Re: 2.6.23: No text consoles with FRAMEBUFFER_CONSOLE_DETECT_PRIMARY

[Frans Pop]

On Sunday 14 October 2007, Antonino A. Daplas wrote:
> On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
> > I could solve this issue in two ways:
> > - boot with VGA=791 parameter (initial boot was without VGA= parameter)
> > - compile kernel without FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set (I also
> >   unset FB_VIRTUAL, but without its boot param that should be a no-op)
>
> After looking at vfb.c again, it seems the default is for vfb to be
> enabled and you have to actively disable vfb either with
>
> video=vfb:disable or video=vfb:off
>
> I have to change this behavior. In the meantime, try one of the above
> options.

I'm not sure if there's been any progress on this issue, but to make sure it 
does not get forgotten, I've just filed a BR under drivers/video(other) and 
added that as blocker to #9056 (2.6.23 regressions):
http://bugzilla.kernel.org/show_bug.cgi?id=9310

Cheers,
FJP