From owner-freebsd-current Tue Jan 5 17:46:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22408 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:46:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22366 for ; Tue, 5 Jan 1999 17:46:01 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id TAA17845; Tue, 5 Jan 1999 19:45:33 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id TAA19137; Tue, 5 Jan 1999 19:45:32 -0600 (CST) Message-ID: <19990105204532.C16219@rtfm.net> Date: Tue, 5 Jan 1999 20:45:32 -0500 From: Nathan Dorfman To: "Chris D. Faulhaber" , current@FreeBSD.ORG Subject: Re: i386/conf/PCCARD References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chris D. Faulhaber on Tue, Jan 05, 1999 at 07:06:59PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 07:06:59PM -0500, Chris D. Faulhaber wrote: > On 5 Jan 1999, Robert V. Baron wrote: > > > > > I've been wondering, of late, how well/if laptops are supported in > > -current. It seems that the configuration, PCCARD, has recently > > (since mid December) has gone away. Is this the answer? > > > I've been running 3.0-CURRENT on my laptop since 3.0-RELEASE came out > without any problems. Now that you mention it, PCCARD is gone; but I've > been updating my current config since -RELEASE. > > So far, no problems have arisen; apm support is there, XFree86-3.3.3 > supports the NeoMagic chipsets (standard in many models), and as long as > your pcmcia chipset/cards are supported by default, everything should work > ok. > > -Chris 3.0's pcic0 driver doesn't seem to like my PCCARD controller. At all. I get all sorts of problems with it like inserting a card will hang the machine (with the slot access light on) until I eject the card, at which point the driver attach will fail and the machine will resume working fine. There's also no way to tell it which IRQs to use or not to use. I snagged the pao3 sources via cvs from jaz.jp.freebsd.org, and have been running fine with PAO on 3.0-R since then. However, this sticks me at 3.0-R, something I'm not happy at all about. If anyone workong on the pcic code is hearing me, this is dmesg output (with PAO3 kernel): pcic0: rev 0x02 int a irq 9 on pci0.19.0 pcic1: rev 0x02 int b irq 9 on pci0.19.1 pcic0 at 0x3e0-0x3e1 irq 9 on isa pcic0: slot 0 controller I/O address 0x3e0 pcic0: slot 1 controller I/O address 0x3e0 IRQ 09 is what 'doze assigns to the controller as well (and 11 to the NIC card, a combination which works great under FreeBSD). PAO tries to assign 11 by default to the controller but I can change it to 9 so I can set the card to 11 (I can't change this value with 3.0-R's pcic). 3.0-R's pcic tries to assign it values like 3 or 5, does this matter? Anyway, plenty of other people have said that their PCMCIA works fine with -current, so I'm assumming it must be something with support for my controller. Anyone have any ideas? I really hate to be tied to -RELEASE because of PAO. > All the true gurus I've met never claimed they were one, and always > pointed to someone better. > -Anonymous > -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message