From owner-freebsd-questions Tue Jul 21 13:11:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29918 for freebsd-questions-outgoing; Tue, 21 Jul 1998 13:11:07 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29906 for ; Tue, 21 Jul 1998 13:10:58 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id PAA00368; Tue, 21 Jul 1998 15:10:28 -0500 (CDT) (envelope-from dan) Message-ID: <19980721151028.A216@emsphone.com> Date: Tue, 21 Jul 1998 15:10:28 -0500 From: Dan Nelson To: john@wilkes.com, freebsd-questions@FreeBSD.ORG Subject: Re: linux emulation and dongle on serial port References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from "John Wilkes" on Tue Jul 21 09:00:59 GMT 1998 X-OS: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jul 21), John Wilkes said: > On Fri, 3 Jul 1998, Julian Elischer wrote: > > On Fri, 3 Jul 1998, John Wilkes wrote: > > > I want to use some Linux software which requires a Rainbow dongle > > > on the serial port. It works fine running native Linux, but with > > > FreeBSD (2.2.5 and 2.2.6) Linux emulation, the hardware dongle is > > > not recognized. Is there any restriction on using the serial > > > ports with linux emulation? > > > > You might try see what it's doing under linux with trace > > I finally did this and here is what it says: > > 329 rbuxid CALL read(0x3,0x280c6000,0x10000) > 329 rbuxid PSIG SIGALRM caught handler=0x8000c40 mask=0x0 code=0x0 > 329 rbuxid RET read -1 errno -4 Unknown error: -4 > 329 rbuxid CALL ioctl(0x3,0x5407 ,0x8003bd8) > 329 rbuxid RET ioctl 0 > > The call to read() apparently fails, but errno -4 is undefined, as > far as I know. Unfortunately, I do not have source to the program. I seem to recall Linux returns negative errno codes from syscalls. If that's the case, 4 == EINTR == Interrupted system call. So, your program sets a timer using the alarm() function, calls read(), the alram times out, gets a SIGALRM, and the read() fails with EINTR. I'd re-run kdump with the -T, and see exactly how much time passes between the read() and the SIGALRM. It looks like nothing's coming out of the serial port. If you try sending that "FINTRONIC#0S81NCAAA..." data stream to the serial port via cu, do you get output? -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message