From owner-freebsd-stable Sun Mar 19 19:28: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 7C0BB37BA34 for ; Sun, 19 Mar 2000 19:28:00 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for freebsd-stable@freebsd.org id 12WsrH-000A5j-00; Mon, 20 Mar 2000 03:27:59 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id DAA52093 for freebsd-stable@freebsd.org; Mon, 20 Mar 2000 03:27:58 GMT (envelope-from jcm) Date: Mon, 20 Mar 2000 03:27:58 +0000 From: J McKitrick To: freebsd-stable@freebsd.org Subject: Re: serial probs in 4.0 Message-ID: <20000320032758.A48883@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if this will help anyone, but i did 2 things that *might have solved the serial problem on my machine. I just deleted the cuaa devices and remade them. My serial port modem ended up on cuaa4, which was strange, but at least it worked. Then, when i removed everything after sio0 from the kernel config, the modem showed up at cuaa1, where it used to be under 3.4. I don't know if this is what solved my problem, but it's worth a shot if you are still having problems. I had the *exact* same thing... it opened under term, and accepted keystrokes, but didn't answer to AT commands. jm -- -------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org "Doors to the pleasures of heaven or hell, and i didn't care which." -------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message