Date: Mon, 24 May 1999 14:02:22 -0600 From: Wes Peters <wes@softweyr.com> To: Darren Reed <avalon@coombs.anu.edu.au> Cc: hackers@FreeBSD.ORG Subject: Re: 3c589d and FreeBSD 3.1 Message-ID: <3749B04E.B1D70CC0@softweyr.com> References: <199905241208.WAA04399@cheops.anu.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Darren Reed wrote:
>
> Back when I was running 2.2.8 (and on a different laptop), I used zp0
> with the 3c589D although it sucked with people recommending using ed0.
>
> Does that recommendation hold true for 3.1 ? FWIW, I've tried to boot
> a kernel with both ed0 & zp0 edit'd with "boot -c" but neither seem to
> be able to probe the card at the same `address' that Windows98 sees it
> at (IO 0x1020, IRQ 11). Any hints/tips on how to make it work ?
Have you tried using pccardd? It works just fine for me. I compiled
the ISC DHCP client seperately, since the port was marked broken in
3.1, but I see it's been fixed in 3.2.
I had to add the following section to /etc/pccard.conf for my PCMCIA
ethernet card:
# Wes's D-Link card (works with BeOS)
card "D-Link" "DE-660"
config 0x20 "ed0" 11
insert echo D-Link ethernet card inserted
insert /etc/pccard_ether ed0
remove echo D-Link ethernet card removed
remove /sbin/ifconfig ed0 delete
There is a configuration for the 589D already in /etc/pccard.conf.sample,
so you should have an easy time of it.
This machine wanders back and forth between home and work every day, and
works fine on startup/shutdown. Suspend is a little iffy, but the only
time I use suspend is to take it off the network at lunch and put it back
on the same network after lunch.
Email me if you need any help.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
http://www.softweyr.com/~softweyr wes@softweyr.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3749B04E.B1D70CC0>