From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Juha <juhis@trinity.is-a-geek.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: matroxfb not working after trying to upgrade to 2.6.3
Date: Mon, 23 Feb 2004 16:13:24 +0200 [thread overview]
Message-ID: <6801343D94@vcnet.vc.cvut.cz> (raw)
On 23 Feb 04 at 12:35, Juha wrote:
> I've got a problem with matroxfb not working in either 2.4.23 or 2.6.3 after
> trying to upgrade to 2.6 series. My videocard is a G400 and it's built as a
> module. Previously, when I modprobed the module, it would register itself in
> /etc/log/syslog, but now nothing is printed in the syslog when inserting the
> modules. And I don't understand, what has changed. These are the parameters I
> give to lilo on boot:
>
> Feb 23 14:06:27 linux kernel: Kernel command line: auto BOOT_IMAGE=Linux ro
> root=303 video=matrox:vesa:0x115
>
> And this is my .config:
>
> CONFIG_FB_MATROX=m
Do not build it as a module. It is not going to work in usual configurations.
Also, did you built CONFIG_FRAMEBUFFER_CONSOLE as a module and insmod-ded it
AFTER matroxfb?
> but when I try to use matroxset, with both 2.4 and 2.6, I get:
>
> bash:# matroxset -f /dev/fb0 -m 2
> ioctl failed: Device or resource busy
Probably output #1 is already used by someone else. Build everything
to the kernel, you'll get much saner defaults then, as it forces
correct order for crtc2 & maven initializations.
What reports 'matroxset -f /dev/fb0 -m' and 'matroxset -f /dev/fb1 -m' ?
Does not second one report that /dev/fb1 is currently displayed on that
output?
Petr
next reply other threads:[~2004-02-23 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 14:13 Petr Vandrovec [this message]
2004-02-23 20:13 ` matroxfb not working after trying to upgrade to 2.6.3 Juha Pahkala
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 12:35 Juha
2004-02-23 12:57 ` Juha Pahkala
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=6801343D94@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=juhis@trinity.is-a-geek.com \
--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