From owner-freebsd-mobile Tue May 11 6: 0:54 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id CE6BA14C9C for ; Tue, 11 May 1999 06:00:51 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA04038; Tue, 11 May 1999 08:59:24 -0400 (EDT) From: Mikhail Teterin Message-Id: <199905111259.IAA04038@kot.ne.mediaone.net> Subject: Re: interpreting the ``pccardc dumpcis'' In-Reply-To: <199905110357.MAA26966@afs.ntc.mita.keio.ac.jp> from HOSOKAWA Tatsumi at "May 11, 1999 12:57:29 pm" To: hosokawa@itc.keio.ac.jp (HOSOKAWA Tatsumi) Date: Tue, 11 May 1999 08:59:23 -0400 (EDT) Cc: mobile@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"> The ``config 0x20 "sio2" 11'' combination makes the pccardd report =>> success, but any attempts to use it -- with minicom or with ``cat > =>> /dev/cuaa2' result in a total lock-up of the machine. = =Does 0x20 conflict with internal serial port? How do I know? =Please test 0x21, 0x22, 0x23 instead. config 0x21 "sio2" 11 config 0x22 "sio2" 11 "NULL com in siounload" "driver allocation failed for AT&T Paradyne" 0x20 and 0x23 were not working before. Sio2 is not detected at bootup, but is probed. Should I disable it? Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message