From: Ed Sweetman <safemode@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: pci unsupported PM regs version (7), means hardware isn't working?
Date: Thu, 01 Dec 2005 17:58:20 -0500 [thread overview]
Message-ID: <438F800C.1050903@comcast.net> (raw)
I'm getting this warning when i try to load the madwifi drivers on my
WRAP board for the WMIA-166AG mini-pci card using kernel 2.6.13.3 and
the latest trunk of madwifi.
This is the only error that's printed before the HAL driver for madwifi
responds with "no hardware found or unsupported hardware" etc etc. I
had to add the pcid's to madwifi for it to even detect it enough to try
and send it to the HAL module, but the madwifi dev team isn't looking at
any bug reports because of this printk that's being made by the PCI
subsystem in the kernel.
So, does this printk mean anything (i've seen posts where the hardware
producing it was working, the printks were just a nuissance) or does it
indicate some issue the PCI subsystem is having in powering the card up
and communicating with it. In either case, I'd be more than happy with
providing anyone able to patch the pci code with information i have on
the card.
If it's nothing but a harmless warning, i'll forward the response to the
madwifi wiki and mailing list, so something can be done upstream to the
hal module to work the card.
Thanks in advance.
next reply other threads:[~2005-12-01 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 22:58 Ed Sweetman [this message]
2005-12-15 9:25 ` pci unsupported PM regs version (7), means hardware isn't working? Adam Belay
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=438F800C.1050903@comcast.net \
--to=safemode@comcast.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