From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "Carlo E. Prelz" <fluido@fluido.as>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Mixing g400 dualhead and old Millennium.
Date: Sun, 13 Oct 2002 16:56:04 +0200 [thread overview]
Message-ID: <20021013145604.GC20348@ppc.vc.cvut.cz> (raw)
In-Reply-To: <20021013141516.GA9973@casa.fluido.as>
On Sun, Oct 13, 2002 at 04:15:16PM +0200, Carlo E. Prelz wrote:
>
> I was having problems in compiling things in kernel. Eventually, it
> seems they were limited to compiling the latest 2.4.20-pre10-ac2
> patch, which contains a more recent version of your material. With
> that, both with modules and included in the kernel, I get the
> following messages (here with modules);
Strange, I'll have to look at 2.4.20-pre10-ac2 then. I do not
remember sending anything special for 2.4.20 to Alan...
> matroxfb_crtc2: secondary head failed to register
> matroxfb_crtc2: CRTC2 framebuffer failed to register
It can only happen if there is not enough memory (uh...) or if
register_framebuffer() fails. And only way I can imagine is
that you run out of possible framebuffers... Can you
verify that /usr/src/linux/include/linux/fb.h contains
'#define FB_MAX 32' and not some small value like '2' ?
> so that I cannot see the second head of the g400. With 2.4.19 and
> module loading, instead of the last two lines I get:
>
> matroxfb_crtc2: secondary head of fb1 was registered as fb2
>
> This is not urgent for me now. I still cannot see if the output is
> present on all outputs (somebody will have to physically check the
> monitor outputs, and that will hopefully happen sometimes tomorrow),
> but now the matroxset output looks very promising.
>
> In all cases, if you want me to do some tests or try some patch to see
> if the 'failed to register' situation can be fixed, just ask.
If you could print return value from register_framebuffer in
matroxfb_dh_regit in matroxfb_crtc2.c, maybe it could reveal
problem. Maybe that using non-ac kernel fixes problem too.
Petr Vandrovec
vandrove@vc.cvut.cz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-13 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 15:36 Mixing g400 dualhead and old Millennium Carlo E. Prelz
2002-10-13 0:13 ` Petr Vandrovec
2002-10-13 14:15 ` Carlo E. Prelz
2002-10-13 14:56 ` Petr Vandrovec [this message]
2002-10-13 15:14 ` Carlo E. Prelz
2002-10-13 16:07 ` Carlo E. Prelz
2002-10-13 22:35 ` Petr Vandrovec
2002-10-14 5:50 ` Carlo E. Prelz
2002-10-14 12:54 ` Petr Vandrovec
2002-10-14 14:53 ` Carlo E. Prelz
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=20021013145604.GC20348@ppc.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=fluido@fluido.as \
--cc=linux-fbdev-devel@lists.sourceforge.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).