From: Michael Born <michael.born@stud.uni-hannover.de>
To: linux-kernel@vger.kernel.org
Subject: PCI: device 00:09.0 has unknown header type 04, ignoring. What's that?
Date: Thu, 13 Nov 2003 20:40:23 +0100 [thread overview]
Message-ID: <200311132040.23582.michael.born@stud.uni-hannover.de> (raw)
Hi kernel hackers,
I have a problem with a GPIB PCI card from Quancom
( http://quancom.de/qprod01/eng/pb/pci_gpib.htm ).
I wrote a programm to read data <100kByte/sec from the GPIB bus to the RAM.
When the PCI card shares it's IRQ it works for some time and then hardlocks
my computer - the "PCI access LED" of the GPIB card is always ON then.
Now I found a PCI slot where the card doesn't have to share the IRQ - but
linux ignores the card :-(
While booting the kernel says:
---
<6>PCI: Probing PCI hardware
<4>PCI: ACPI tables contain no PCI IRQ routing entries
<4>PCI: Probing PCI hardware (bus 00)
<3>PCI: device 00:09.0 has unknown header type 04, ignoring.
<6>PCI: Using IRQ router VIA [1106/3074] at 00:11.0
---
The BIOS bootscreen reported an "unknown device - IRQ5". But "lspci" doesn't
show up the card!!!
What is "unknown header type 04" ?
Why does "lspci" show the card when IRQ is shared?
How can I know what's wrong with this card?
Somebody please enlighten me.
Please CC me your mail - I'm not subscribed to the list.
Greetings
Michael
PS: I already had trouble with this card spontaneously getting unconfigured
(like before the BIOS talks to the card) in an ECS L7S7A board ...
My system:
Athlon 2000XP
512MB RAM
Epox 8KHA+ (VIA KT266a)
Suse8.2
2.4.22 kernel
3.1.97 linux gpib driver
next reply other threads:[~2003-11-13 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 19:40 Michael Born [this message]
2003-11-13 20:09 ` PCI: device 00:09.0 has unknown header type 04, ignoring. What's that? H. Peter Anvin
2003-11-13 20:29 ` Richard B. Johnson
2003-11-13 20:57 ` Ricky Beam
2003-11-13 21:30 ` Richard B. Johnson
2003-11-14 7:52 ` Michael Born
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=200311132040.23582.michael.born@stud.uni-hannover.de \
--to=michael.born@stud.uni-hannover.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.