From: Francois Romieu <francois@fr.zoreil.com>
To: Ploum Ploum <ploum@mitose.net>
Cc: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] Re: GeForce 4 MX have no working frame buffer at all..
Date: Sat, 21 Aug 2004 22:00:07 +0200 [thread overview]
Message-ID: <20040821200007.GA10966@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <41278A27.2070608@mitose.net>
Ploum Ploum <ploum@mitose.net> :
[...]
> I've applied the mm3 patch from kernel.org and the patch supplied by
> François Romieu but there's no change at all.
Bug of mine: I did not notice the lower part of the mask.
> Note, I forget to say that I can enable the framebuffer but only at
> 800x600. If I put vga=ash (video=vesafb), it simply won't recognise any
> number that correspond to a higher resolution. Also, using the
> framebuffer at 800x600 has a grave bug : once that X is started, I
> cannot anymore see a console, only a black screen. those console works
> perfectly (I can "blind" type on it) but I cannot see it. Even if I
> kill X, only a black screen remains.
X messes with the hardware. You do not want to kill it.
> I've put video=rivafb also, but then it simply doesn't work and boot on
> a non-fb console.
Can you reproduce this test without nvidia proprietary module loaded at
startup ?
As a minimum there should be some messages prefixed by "rivafb: xxx".
--
Ueimor
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
prev parent reply other threads:[~2004-08-21 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 10:53 GeForce 4 MX have no working frame buffer at all Ploum Ploum
2004-08-21 11:14 ` [patch] " Francois Romieu
2004-08-21 12:09 ` Antonino A. Daplas
2004-08-21 17:45 ` Ploum Ploum
2004-08-21 20:00 ` Francois Romieu [this message]
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=20040821200007.GA10966@electric-eye.fr.zoreil.com \
--to=francois@fr.zoreil.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=ploum@mitose.net \
/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;
as well as URLs for NNTP newsgroup(s).