Hi.
A number of people have experienced the same problem as I have; the VESA
framebuffer is just..black on boot. I haven't seen any reports on this,
though. dmesg says what it always have said before about the fb.
I boot with vga=791 (as specified in lilo.conf).. Have something changed
or is it just broken? :o)
Thanks.
--
Henrik Persson [email protected] http://nix.badanka.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Hi.
>
> A number of people have experienced the same problem as I have; the VESA
> framebuffer is just..black on boot. I haven't seen any reports on this,
> though. dmesg says what it always have said before about the fb.
>
> I boot with vga=791 (as specified in lilo.conf).. Have something changed
> or is it just broken? :o)
>
> Thanks.
I boot with vga=0x343 (1400x1050) and its working fine (2.6.0-test1)
This is a Dell Latitude C610 laptop, so it may be using the ati framebuffer
stuff, although I get this in dmesg:
vesafb: framebuffer at 0xe0000000, mapped to 0xd8800000, size 16384k
vesafb: mode is 1400x1050x24, linelength=4200, pages=2
vesafb: protected mode interface info at c000:5378
vesafb: scrolling: redraw
vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0
fb0: VESA VGA frame buffer device
Console: switching to colour frame buffer device 175x65
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/FWpyBn4EFUVUIO0RAjqwAJ43U2vmUw7kMFkoeIsdDLyxhAbLBQCgmMST
LO8Pk8CAhCD0Uq/kuPd9hBo=
=W+2A
-----END PGP SIGNATURE-----
I have the same problem. It boots but I have no console. In 2.5 there was
an item 'enable virtual console' (in Character Devices) which I had
enabled, and the boot console was showing. I didn't see this option
displayed when I configured 2.6 from scratch (CONFIG_VT stuff)
TTimo
On Wed, 16 Jul 2003 16:08:34 +0100
Mark Watts <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > Hi.
> >
> > A number of people have experienced the same problem as I have; the VESA
> > framebuffer is just..black on boot. I haven't seen any reports on this,
> > though. dmesg says what it always have said before about the fb.
> >
> > I boot with vga=791 (as specified in lilo.conf).. Have something changed
> > or is it just broken? :o)
> >
> > Thanks.
>
> I boot with vga=0x343 (1400x1050) and its working fine (2.6.0-test1)
>
> This is a Dell Latitude C610 laptop, so it may be using the ati framebuffer
> stuff, although I get this in dmesg:
>
> vesafb: framebuffer at 0xe0000000, mapped to 0xd8800000, size 16384k
> vesafb: mode is 1400x1050x24, linelength=4200, pages=2
> vesafb: protected mode interface info at c000:5378
> vesafb: scrolling: redraw
> vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0
> fb0: VESA VGA frame buffer device
> Console: switching to colour frame buffer device 175x65
>
> Mark.
>
> - --
> Mark Watts
> Senior Systems Engineer
> QinetiQ TIM
> St Andrews Road, Malvern
> GPG Public Key ID: 455420ED
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE/FWpyBn4EFUVUIO0RAjqwAJ43U2vmUw7kMFkoeIsdDLyxhAbLBQCgmMST
> LO8Pk8CAhCD0Uq/kuPd9hBo=
> =W+2A
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Wed, 16 Jul 2003 16:08:34 +0100
Mark Watts <[email protected]> wrote:
*snip*
> vesafb: framebuffer at 0xe0000000, mapped to 0xd8800000, size 16384k
> vesafb: mode is 1400x1050x24, linelength=4200, pages=2
> vesafb: protected mode interface info at c000:5378
> vesafb: scrolling: redraw
> vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0
> fb0: VESA VGA frame buffer device
> Console: switching to colour frame buffer device 175x65
*snip*
This is mine:
vesafb: framebuffer at 0x90000000, mapped to 0xcf807000, size 15296k
vesafb: mode is 1024x768x16, linelength=2048, pages=8
vesafb: protected mode interface info at c000:7926
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
and I don't have the Console: switching to color frame buffer ...thing.
Hrm..
--
Henrik Persson [email protected] http://nix.badanka.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On Wed, 16 Jul 2003 16:08:34 +0100
> Mark Watts <[email protected]> wrote:
>
> *snip*
>
> > vesafb: framebuffer at 0xe0000000, mapped to 0xd8800000, size 16384k
> > vesafb: mode is 1400x1050x24, linelength=4200, pages=2
> > vesafb: protected mode interface info at c000:5378
> > vesafb: scrolling: redraw
> > vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0
> > fb0: VESA VGA frame buffer device
> > Console: switching to colour frame buffer device 175x65
>
> *snip*
>
> This is mine:
>
> vesafb: framebuffer at 0x90000000, mapped to 0xcf807000, size 15296k
> vesafb: mode is 1024x768x16, linelength=2048, pages=8
> vesafb: protected mode interface info at c000:7926
> vesafb: scrolling: redraw
> vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
> fb0: VESA VGA frame buffer device
>
> and I don't have the Console: switching to color frame buffer ...thing.
>
> Hrm..
Attached is my .config if that helps?
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/FmbNBn4EFUVUIO0RAuHwAKCd9g6zcsTApT9OezuoB6dUCD1dxACggRBr
pE6nwVzdy3GhH0Sl47doSx0=
=BV+f
-----END PGP SIGNATURE-----
Just a heads-up for you that made the same mistake in the
menuconfig-jungle as I did:
If you want framebuffer console support, don't forget the
CONFIG_FRAMEBUFFER_CONSOLE ;o)
--
Henrik Persson [email protected] http://nix.badanka.com