From: Timothee Besset <ttimo@idsoftware.com>
To: Mark Watts <m.watts@eris.qinetiq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VESA Framebuffer dead in 2.6.0-test1
Date: Wed, 16 Jul 2003 17:23:31 +0200 [thread overview]
Message-ID: <20030716172331.3bd3610e.ttimo@idsoftware.com> (raw)
In-Reply-To: <200307161608.34637.m.watts@eris.qinetiq.com>
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 <m.watts@eris.qinetiq.com> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-07-16 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 14:06 VESA Framebuffer dead in 2.6.0-test1 Henrik Persson
2003-07-16 15:08 ` Mark Watts
2003-07-16 15:23 ` Timothee Besset [this message]
2003-07-17 14:36 ` Henrik Persson
2003-07-16 15:48 ` Henrik Persson
2003-07-17 9:05 ` Mark Watts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030716172331.3bd3610e.ttimo@idsoftware.com \
--to=ttimo@idsoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.watts@eris.qinetiq.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.