Date: Sat, 8 Apr 2000 14:00:03 -0700 (PDT) From: Peter Wemm <peter@netplex.com.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/17858: pnp isa ed device problem on 4.0-RELEASE Message-ID: <200004082100.OAA72666@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/17858; it has been noted by GNATS.
From: Peter Wemm <peter@netplex.com.au>
To: dmitry@asbaikaltv.ru
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/17858: pnp isa ed device problem on 4.0-RELEASE
Date: Sat, 08 Apr 2000 13:50:26 -0700
dmitry@asbaikaltv.ru wrote:
> >Number: 17858
> >Synopsis: pnp isa ed device problem on 4.0-RELEASE
[..]
> Logical Device ID: CPX1501 0x0115180e #0
> Device powers up active
> Device supports I/O Range Check
> Vendor register funcs 00
> Compatible Device ID: PNP80d6 (d680d041)
^^^^^^^^^^^^^^^^^^
> I/O Range 0x220 .. 0x3e0, alignment 0x20, len 0x20
> [not 16-bit addr]
> IRQ: 5 10 11 12 15 IRQ: High true edge sensitive
Hmm. We check for that specific compatable pnpid, it should have matched
the if_ed driver.
However, can you try a couple of things please? First, try this patch
and see if it makes any difference:
Index: if_ed_isa.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/ed/if_ed_isa.c,v
retrieving revision 1.5
diff -u -r1.5 if_ed_isa.c
--- if_ed_isa.c 1999/11/20 09:28:01 1.5
+++ if_ed_isa.c 2000/04/08 20:41:41
@@ -58,6 +58,7 @@
{ 0x19808c4a, NULL }, /* RTL8019 */
{ 0x0090252a, NULL }, /* JQE9000 */
{ 0x0020832e, NULL }, /* KTC2000 */
+ { 0x0115180e, NULL }, /* CPX1501 */
{ 0, NULL }
};
cd to /sys/dev/ed and apply it with patch and reconfigure/rebuild a kernel
and reboot.
If this makes a difference, then we have a bug in our compatable device
matching code.
Can you please check your kernel config file? You should be able to have
'device ed' in there with no 'at isa? port ...' or anything like that.
Also, if it's still not working, please try a 'boot -v' and see if the
if_ed driver prints any clues about resource conflicts or reasons for the
probe failure.
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004082100.OAA72666>