From owner-freebsd-questions Thu Sep 19 13:18:23 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04ECC37B41A for ; Thu, 19 Sep 2002 13:18:19 -0700 (PDT) Received: from web10008.mail.yahoo.com (web10008.mail.yahoo.com [216.136.130.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 1EEAD43E6E for ; Thu, 19 Sep 2002 13:18:19 -0700 (PDT) (envelope-from artswan@yahoo.com) Message-ID: <20020919201819.60969.qmail@web10008.mail.yahoo.com> Received: from [63.145.124.153] by web10008.mail.yahoo.com via HTTP; Thu, 19 Sep 2002 13:18:19 PDT Date: Thu, 19 Sep 2002 13:18:19 -0700 (PDT) From: Art Swan Subject: Fixes for modem lockup and cuaa4/KPPP problems To: freebsd-questions-digest@freebsd.org, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG These are fixes I found on the web for a couple of problems I was having. 1. System lockup when I tried to use cuaa0 and 2. How to use cuaa4 on KPPP dialer. For the modem lockup when I tried to use cuaa0, I simply used (as root) /dev/MAKEDEV to create cuaa4, with which my modem worked perfectly. Then I had to find a way to use cuaa4 under KPPP which only allows cuaa0 to cuaa3. Basically it's simple. As root, cd down to /dev and remove (rm) cuaa3. Then form a soft link called /dev/cuaa3 to /dev/cuaa4. It solved the problem fine. KPPP worked like a charm from then on. Here is the article I got the fix from: " This will probably only apply to PCI Modems that are assigned an IRQ out of the range of the normal COM port IRQ's. ( IRQ 4, 3) The problem: ActionTek PCI modem assigned to sio4, I prefer KDE and KPPP as my connection interface. KPPP only provides port selections cuaa0 to cuaa3. My modem is assigned to cuaa4. ( I really like the automated MAKEDEV on bootup, specially since I can't find setserial on my box anymore :^) ) Solution: As root from CLI shell or even a terminal in KDE. cd /dev See what exists: ls -l /dev/cuaa* Should see entries in the table: crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa0 crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa1 crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa2 crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa3 crw-r------ root wheel 28, 132 Dec 7 16:00 cuaa4 NOTE: If your table does not look like the example above you should probably try another method. This worked for me and my setup. rm cuaa3 ln -s /dev/cuaa4 /dev/cuaa3 To Verify: ls -l /dev/cuaa* Should now look like: crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa0 crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa1 crw-r------ uucp dialer 28, 130 Dec 7 16:00 cuaa2 crw-r------ root wheel 10, Dec 7 16:02 cuaa3 -> /dev/cuaa4 crw-r------ root wheel 28, 132 Dec 7 16:00 cuaa4 Finally: In order for me as user to use this I had to assign myself to group wheel in /etc/group file. This is easily done with your favorite editor and adding a comma behind the last entry of group wheel and the the approppriate user name. Do not put a space, white or otherwise between the comma and the new user ID. Written and tested by BSDvault member DonXC " Hope all this helps someone. :) __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message