From owner-freebsd-questions Tue May 25 23:19:54 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ginger.kf7nn.com (mti-r1-aptis-4-p2022.cybertrails.com [162.42.15.229]) by hub.freebsd.org (Postfix) with ESMTP id 9E48C153AA for ; Tue, 25 May 1999 23:19:45 -0700 (PDT) (envelope-from root@ginger.kf7nn.com) Received: (from root@localhost) by ginger.kf7nn.com (8.9.3/8.9.2) id XAA01539 for questions@freebsd.org; Tue, 25 May 1999 23:19:42 -0700 (MST) (envelope-from root) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 25 May 1999 23:19:41 -0700 (MST) From: laszlo vagner To: questions@freebsd.org Subject: photopc Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a slight problem, i have modem on cuaa2 irq4 therefore i cannot enable cuaa0 on irq4, i am trying to use the photopc port version 1.6 (and others) but it seems to only work correctly on cuaa0 therefore i cant enable cuaa2 while using it i have to reboot with -c and change it every time i use the photopc. I am able to move the plug from cuaa0 to cuaa1 and it works in windows just fine on com2 but not with freebsd on com2, it gets timeout errors and such. the only thing i can think of is to move the modem to cuaa3 irq 3 so i can use cuaa0 irq 4 for the camera. If i enable cuaa0 and cuaa2 at the same time it errors on boot saying that cuaa2 wasnt probed due to conflict with cuaa0. how about this...can i use the "conflicts" keyword in my kernel config and have it work one at a time? ---------------------------------- Vetex C/O L. Vagner 3600 W. Mountain Drive Flagstaff, AZ 86001 Webpage: nadxa.com E-Mail: laszlo vagner Date: 25-May-99 Time: 23:08:03 Windows Exception Error: noun: Meaning- With the exception of a reboot anything you do will fail to recover the system. ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message