From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: nick black <dank@suburbanjihad.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 + matroxfb = unuusable VC
Date: Mon, 21 Jul 2003 20:10:22 +0200 [thread overview]
Message-ID: <7E154527EED@vcnet.vc.cvut.cz> (raw)
On 21 Jul 03 at 17:45, nick black wrote:
> i'm seeing the exact same issues. i use to see similar problems in late
> 2.4's with agp turned on, where turning off agp sorted out the issue.
> using 2.6 (test1-ac2), it happens whether agp is turned on or not.
I do not think that it has anything to do with AGP, as matroxfb does not
initiate any AGP transfers.
> some info: (cmdline, dmesg, config, lspci -v -v for bridge/card):
>
> video=matroxfb:vesa:0x1bb
I think that you are using fbset somewhere in your initscripts. Either
do not do that, or apply
ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/matroxfb-2.5.72.gz.
> PCI: No IRQ known for interrupt pin A of device 01:00.0. Please try
> using pci=biosirq.
And reconfigure your system to assign IRQ to the AGP devices too.
matroxfb uses it for delivering some notifications to the userspace
programs...
> Interrupt: pin A routed to IRQ 0
... if it hooked IRQ0 as MGA interrupt, anything can happen.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2003-07-21 18:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 18:10 Petr Vandrovec [this message]
2003-07-21 18:33 ` 2.6.0-test1 + matroxfb = unuusable VC nick black
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 23:23 Petr Vandrovec
2003-07-23 23:50 Petr Vandrovec
2003-07-24 22:17 ` Michel Eyckmans (MCE)
2003-07-25 0:07 ` James Simmons
2003-07-26 10:33 ` Michel Eyckmans (MCE)
2003-07-25 12:20 ` nick black
2003-07-21 18:44 Petr Vandrovec
2003-07-21 20:02 ` nick black
2003-07-23 23:05 ` Michel Eyckmans (MCE)
2003-07-18 22:39 Michel Eyckmans (MCE)
2003-07-19 6:02 ` Jurriaan
2003-07-21 17:45 ` nick black
2003-07-24 23:39 ` 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=7E154527EED@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=dank@suburbanjihad.net \
--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;
as well as URLs for NNTP newsgroup(s).