From owner-freebsd-current Sun Jan 7 14:42:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 9815637B400 for ; Sun, 7 Jan 2001 14:42:11 -0800 (PST) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA10399; Sun, 7 Jan 2001 17:42:08 -0500 (EST) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA17302; Sun, 7 Jan 2001 17:42:08 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA17298; Sun, 7 Jan 2001 17:42:07 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sun, 7 Jan 2001 17:42:07 -0500 (EST) From: Kenneth Wayne Culver To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: cardbus installs on -current In-Reply-To: <200101072156.f07Lu3s39164@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : is installing FreeBSD-CURRENT with sysinstall using a cardbus supported > : card (such as a 3com cardbus 3cfe575 or something) working yet? Just > : wondering because I want to get windows off my laptop, and this will bring > : me one step closer... (with support for my ess maestro3 chip being the > : last step) > > I don't think anybody has ever gone down this path. If you do, please > drop a note to -current and/or -mobile telling about your woes and > wonders. I'd suspect that it would just work *IF* the card probes > before sysinstall's device harvesting mechanism kicks in. > > Of course, pccardd will not start, but don't worry too much about that. > Is the cardbus stuff in the GENERIC kernel, or will I have to change it and build my own release or custom sysinstall? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message