Re: "CU didn't stop" error message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I appreciate your offer. Would the driver be suitable for a production
firewall server?

Brian Lawrence

----- Original Message -----
From: "Rask Ingemann Lambertsen" <rask@sygehus.dk>
To: "Brian Lawrence" <blawrence@qwest.net>; <linux-net@vger.kernel.org>
Sent: Monday, June 02, 2003 9:49 AM
Subject: Re: "CU didn't stop" error message


On Fri, 30 May 2003 15:13:07 -0500, Brian Lawrence wrote
> I've tried to resolve the problem myself through research and the
newsgroups
> but have been unsuccessful. Is there a workaround to this "CU didn't
> stop" error or is there an updated version of the driver that fixes
> this problem? I have tried to contact Philip Blundell but have not
> yet received a reply.

I could write a new driver that uses the 82586 module from my NE3200 driver
project. Would you like me to do that? The only limitation is that the board
needs to run in 16-bit mode.

--
Regards,
Rask Ingemann Lambertsen


-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux