Jeff Garzik said...
> Changing '#undef DEBUG' to '#define DEBUG 1' in
> arch/i386/kernel/pci-i386.h is also very helpful. Can you guys do so,
> and post the 'dmesg -s 16384' results to lkml? This includes the same
> information as dump_pirq, as well as some additional information.
Here's my dmesg output - I tried with both PNP: Yes and PNP: No and the
dmesg outputs were exactly the same modulo a Hz or two in the processor
speed detection.
I do have an IRQ for my VGA since the instructions for my card (a Voodoo 5
5500) specifically say an IRQ is needed.
--
Manuel A. McLure - Unify Corp. Technical Support <[email protected]>
Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What
about-?" M: "It's fixed." SG: "Eh, good. Good."
"Manuel A. McLure" wrote:
> Jeff Garzik said...
> > Changing '#undef DEBUG' to '#define DEBUG 1' in
> > arch/i386/kernel/pci-i386.h is also very helpful. Can you guys do so,
> > and post the 'dmesg -s 16384' results to lkml? This includes the same
> > information as dump_pirq, as well as some additional information.
>
> Here's my dmesg output - I tried with both PNP: Yes and PNP: No and the
> dmesg outputs were exactly the same modulo a Hz or two in the processor
> speed detection.
Thanks. I'm building a database of these. There is definitely an issue
with Via and interrupt routing. Hopefully I can collate this data soon
and figure out what's going on. I need to find some Via hardware for
myself, too, since I only have an old Via-based laptop which works 100%
;-)
> I do have an IRQ for my VGA since the instructions for my card (a Voodoo 5
> 5500) specifically say an IRQ is needed.
I wonder though... In my mind this is a driver not hardware issue. If
the XFree86 and/or Linux console driver do not use the IRQ, you need not
have BIOS assign one. If you are feeling dangerous, try turning the VGA
IRQ assignment off in BIOS and see if things melt/explode/kick ass.
Regards,
Jeff
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
On Tue, Apr 10, 2001 at 05:11:42PM -0400, Jeff Garzik wrote:
> "Manuel A. McLure" wrote:
> > Jeff Garzik said...
> > > Changing '#undef DEBUG' to '#define DEBUG 1' in
> > > arch/i386/kernel/pci-i386.h is also very helpful. Can you guys do so,
> > > and post the 'dmesg -s 16384' results to lkml? This includes the same
> > > information as dump_pirq, as well as some additional information.
> > Here's my dmesg output - I tried with both PNP: Yes and PNP: No and the
> > dmesg outputs were exactly the same modulo a Hz or two in the processor
> > speed detection.
We are having the same observation here, PNP yse or no does not change dmesg
output of 2.4.x.
> Thanks. I'm building a database of these. There is definitely an issue
> with Via and interrupt routing. Hopefully I can collate this data soon and
> figure out what's going on. I need to find some Via hardware for myself,
> too, since I only have an old Via-based laptop which works 100% ;-)
O.K., here are three further dmesg outputs of the same 2.4.3 kernel
configuration (yes ""|make config) [Thanks to Jens and David!].
Two MSI K7T Pro2A boards (my first report was a MSI K7T Turbo board with
KT133A):
dmesg.David.msi-k7t-pro2a.log.gz
dmesg.Silke.msi-k7t-pro2a.log.gz
An Asus A7V Board:
dmesg.a7v.log.gz
Recognizing any pattern?
--
[email protected]