From owner-freebsd-isp Thu Aug 14 09:05:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26150 for isp-outgoing; Thu, 14 Aug 1997 09:05:41 -0700 (PDT) Received: from mail.cre8tivegroup.com (abt6.bitwise.net [204.97.222.226]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26140; Thu, 14 Aug 1997 09:05:36 -0700 (PDT) Received: from [204.255.227.117] by mail.cre8tivegroup.com (SMTPD32-3.04) id AD5F1C2403BC; Thu, 14 Aug 1997 12:07:59 -0400 Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 14 Aug 1997 11:42:02 -0400 (EDT) Organization: The Creative Group From: Patrick Gardella To: Stefan Molnar Subject: RE: Is ppp compatible with K56flex? Cc: Tim Moony , isp@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It worked just fine in Windows 95. Yes, it was during boot. I added the 0x80 flag to sio3 and saw the phase 3 error. When I commented out the check for phase 3 in /sys/i386/isa/sio.c and remade the kernel, I didn't get the error (of course), but it wouldn't work still. The lines I changed were: /* EXTRA DELAY? */ failures[0] = inb(iobase + com_cfcr) - CFCR_8BITS; failures[1] = inb(iobase + com_ier) - IER_ETXRDY; failures[2] = inb(iobase + com_mcr) - mcr_image; DELAY(10000); /* Some internal modems need this time */ /* if (idev->id_irq != 0) * failures[3] = isa_irq_pending(idev) ? 0 : 1;*/ DELAY(1000); /* XXX */ failures[4] = (inb(iobase + com_iir) & IIR_IMASK) - IIR_TXRDY; The irq was set with a jumper so I know it was correct. From the answers I got from the list archives, I assumed that it was a UART problem. I guessed that the normal 16550 wouldn't work with the 56k line, so they had developed a new 16550? to run it. Either that, or it was a 16550 emulation. (I had posted the UART info in an message to the list, but I can't find it in the archives.) Pat On 14-Aug-97 Stefan Molnar wrote: > >> I was not connected to a K56Flex server. I was trying to use it to connect >> at 28,800 only. I couldn't run cu to even send it an AT string. The error cam e >> up on boot. I edited out the phase 3 check to if it would run then. It didn 't. >> >> I returned the modem, so I have no idea what chipset it had. > >I have not really seen that error before. But during the bootstrap >the error occured, when the kernel was probeing the serial ports? >Have you tried it in a dos environment, or another os. The Hayes >has the rockwell chipset I belive. > >Stefan ---------------------------------- E-Mail: Patrick Gardella Date: 14-Aug-97 Time: 11:42:02 This message was sent by XFMail ----------------------------------