From: "Frédéric L. W. Meunier" <0@pervalidus.tk>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: matroxfb and 2.6.0-test2
Date: Tue, 29 Jul 2003 16:41:20 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.56.0307291628130.153@pervalidus.dyndns.org> (raw)
In-Reply-To: <89B48AF68E2@vcnet.vc.cvut.cz>
On Tue, 29 Jul 2003, Petr Vandrovec wrote:
> On 29 Jul 03 at 2:14, Frédéric L. W. Meunier wrote:
> > On Tue, 29 Jul 2003, Petr Vandrovec wrote:
> > > On Mon, Jul 28, 2003 at 08:34:40PM -0300, Frédéric L. W. Meunier wrote:
> >
> > Thanks. It worked (and I don't see any screen corruption).
> >
> > Maybe I'm missing something, but is there anything wrong with
> > video=matroxfb:vesa:0x1B5 ? I got
>
> I have no idea...
>
> > Kernel command line: BOOT_IMAGE=3 root=307 acpi=off noapic video=matroxfb:vesa:0x1B5
> > Console: colour VGA+ 80x25
> > matroxfb: Matrox G400 (AGP) detected
> > matroxfb: MTRR's turned on
> > matroxfb: 800x600x24bpp (virtual: 800x65536)
> > matroxfb: framebuffer at 0xD8000000, mapped to 0xe0805000, size 33554432
> > fb0: MATROX frame buffer device
> > fb0: initializing hardware
> > matroxfb: cannot set xres to 800, rounded up to 832
> > Console: switching to colour frame buffer device 100x37
> > /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
> > Console: switching to colour frame buffer device 100x37
>
> ... but it looks strange to me that you have two 'switching to...' lines.
I don't have two with your patch.
> Unless it gets proven that it is bug in kernel's matroxfb and not
> in generic fbcon (== if you'll send me a patch, I'll apply it; but do
> not expect that I'll hunt down bugs which do not occur with matroxfb-2.5.72
> addon), I recommend you applying
> ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/matroxfb-2.5.72.gz.
> It reinstates back fbcon layer I understand & trust...
2 other problems went away with your patch. When I reported no
screen corruption I was wrong since it messed everything
returning from XFree86, including getting a dump of a Windows
reboot. The other is the boot logo, which now appears.
next parent reply other threads:[~2003-07-29 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89B48AF68E2@vcnet.vc.cvut.cz>
2003-07-29 19:41 ` Frédéric L. W. Meunier [this message]
2003-07-30 15:59 Petr Vandrovec
[not found] <8A361F82D2E@vcnet.vc.cvut.cz>
2003-07-30 3:19 ` Frédéric L. W. Meunier
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 12:52 Petr Vandrovec
2003-07-30 15:43 ` Wakko Warner
2003-07-29 11:51 Petr Vandrovec
2003-07-29 12:53 ` Wakko Warner
2003-07-28 23:34 Frédéric L. W. Meunier
2003-07-29 2:13 ` Petr Vandrovec
2003-07-29 5:14 ` Frédéric L. W. Meunier
2003-07-29 11:27 ` Wakko Warner
2003-07-29 17:02 ` James Simmons
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=Pine.LNX.4.56.0307291628130.153@pervalidus.dyndns.org \
--to=0@pervalidus.tk \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®