Date: Wed, 30 Apr 1997 21:25:23 -0700 (PDT) From: Wes Santee <wes@bogon.net> To: hackers@freebsd.org Subject: Changes to ie0 broke ix0? Message-ID: <199705010425.VAA00203@kryten.bogon.net>
next in thread | raw e-mail | index | archive | help
'Lo all. The recent changes incorporating the old Intel EE16 driver code (ix0) into the Intel EE Pro/10 driver code (ie0) seems to have put the last nail into the EE16 coffin. I've got a couple boxes with EE16s in them that -- while limping -- perform their duties without troubles running 2.2.1. Recently I recompiled the kernel on those boxes with the post-change code, and now every time an NFS write is initiated from one of those boxes, it locks up the terminal for good. Only way out is to shutdown from another window. Is it time to move EE16 compatibilty on the supported NIC list from "not recommended" to "broken"? Here is the line I'm using in the config file (after seeing that ix0 was completely removed from LINT): device ie0 at isa? port 0x300 net irq 10 iomem 0xcc000 iosiz 32767 vector ieintr And from dmesg: ie0 at 0x300-0x30f irq 10 maddr 0xcc000 msize 32768 on isa ie0: <EtherExpress 16 R1> address 00:aa:00:17:39:cb Cheers, -- ( Wes Santee PGP: e-mail w/Subject: "Send PGP Key" ) ( mailto:wes@bogon.net )
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705010425.VAA00203>