From owner-freebsd-mobile Wed Apr 21 7:57:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7FF6914BE6 for ; Wed, 21 Apr 1999 07:57:27 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (1982 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Wed, 21 Apr 1999 07:54:59 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Wed, 21 Apr 1999 07:54:59 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Campbell Cc: freebsd-mobile@freebsd.org Subject: Re: pccardd and ep0 (3c589D) References: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Quick overview: > > 3.1-RELEASE kernel with ep0 on a laptop results in 'No buffer > space available' when used with pccardd. 3c589D. Unloads ep0 > right after getting mac address. > > Detail: > > Recently work has deigned to allocate myself with a humble HP Omnibook for > my purposes. The FreeBSD 3.1-RELEASE GENERIC kernel works fine with the > zp0 device, however of course the APM side of things doesn't work. > > Recompiling the kernel with the following added options to GENERIC: > > # APM support > device apm0 at isa? flags 0x31 > > # PCMCIA support > controller card0 > device pcic0 at card? > device pcic1 at card? > options PCIC_RESUME_RESET > > # ep0 driver (3com) to work under pccardd > device ep0 at isa? port 0x300 net irq 10 vector epintr > > # Disable the zp0 driver, we don't need it, use ep0 instead with > # laptops (according to various gnats #s) > # device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 > > # Reset various things after a resume > options PSM_HOOKAPM # Hook the APM resume event, useful for some laptops > options PSM_RESETAFTERSUSPEND # reset the device at the resume event > options "CPU_SUSP_HLT" > > > results in a kernel which can be suspended quite happily, which is the > main thing I want. ep0 can be brought up and down quite happily, but when > any traffic is sent over that link: > > ping: sendto: No buffer space available i am occasionally seeing the "No buffer space available" with zp0 on a sony vaio. have yet to localize, but seems to do with killing rdumps or other rmt processes. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message