From owner-freebsd-questions Mon Jul 8 16:34:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA19127 for questions-outgoing; Mon, 8 Jul 1996 16:34:19 -0700 (PDT) Received: from lint.cisco.com (lint.cisco.com [171.68.223.44]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA19118 for ; Mon, 8 Jul 1996 16:34:17 -0700 (PDT) Received: (skrishna@localhost) by lint.cisco.com (8.6.10/CISCO.SERVER.1.1) id QAA12232; Mon, 8 Jul 1996 16:34:37 -0700 Date: Mon, 8 Jul 1996 16:34:37 -0700 (PDT) From: Sridhar Krishnan To: Greg Lehey cc: Gary Chrysler , FreeBSD Questions Subject: Re: FreeBSD 2.1 Help In-Reply-To: <199607070735.JAA15158@allegro.lemis.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have not resolved the problem using the internal modem on COM1. Here is the scenario: I have MWave card on IBM Aptiva system that combines the functions of a Sound Card, some DSP, COM1 Fax/Modem. The COM1 has an i/o address of 02F8h (0x2f8) and uses IRQ 4. I have PS/2 mouse which is working fine. Has anybody heard of the Mwave Card ? I scanned through the FAQ for hardware support and I could not find any. The system also comes with two (extrenal) serial ports A & B which are configured as COM2 (0x3e8, IRQ 3) and COM3 (0x3e8, IRQ 4). I have tried kernel configuration: - sio0 with 0x2f8 and intr. 4 , with/without conflicts clause and commented out sio1, sio2 and sio3. I saw the WIN95 config, it shows COM1 at the above address. During boot, the kernel says that sio0 is not configured because 0x2f8 does not respond. The only way sio0 would work is if I configured my kernel for 0x38h which is actually COM3. That is why my modem is not responding (sincve it is configured as COM3). How do I get the kernel to recognize sio0 ? Does the serial driver only recognize serial port cards and not this multi-function card. If so, any ideas how I can use the built-in modem. I got my fvwm working! I found out that "twm" is configured in the xinitrc (under /usr/X11R6/lib/x11). Do you think this should be part of the handbook ? Thanks for you help. I am enjoying the FreeBSD! > > 1. cu -l cuaa0 > > says "connected". Then when I type "ATDTE1Q0", I am expecting "OK". > > Nothing happens. When I quit out with ~. it takes a minute to disconnect. > > This looks familiar. It's really a bug of sorts in cu. From another > window (or virtual terminal), do: > > # stty -f /dev/cuaa0 -a > speed 9600 baud; 0 rows; 0 columns; > lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl > -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin > -nokerninfo -extproc > iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel -ignbrk > -brkint -inpck -ignpar -parmrk > oflags: -opost -onlcr -oxtabs > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow > ******* > -dtrflow -mdmbuf > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; > eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; > min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ; > stop = ^S; susp = ^Z; time = 0; werase = ^W; > > This shows the complete state of the line. You will probably find > -clocal (i.e. local communications reset, device waiting for an > incoming connection). Next enter: > > # stty -f /dev/cuaa0 clocal > > This sets clocal (in the display you see 'clocal' instead of > '-clocal'). After that, things should work. > > > Yet another person aksed me disable PnP (plug and Play) option. I do not > > know how-to. I'll give it a try. > > I very much doubt that that has anything to do with it. Does it have > a PnP option? > > > 2. On fvwm, I am little confused. I start xdm as explained in the book > > (via init - ttys. Ofcourse I cannot use because a wm is already running. > > I wouldn't have said 'of course'. If you have a window manager > running, you don't need another one. Check your .xinitrc file. Maybe > it already invokes a window manager. You can also enter: > > $ ps aux | grep wm > root 15152 1.0 0.3 224 176 p5 S+ 9:33AM 0:00.03 grep wm > grog 201 0.0 0.8 384 520 co S Fri06PM 0:08.53 fvwm > > You will probably see some other window manager, but it might be that > you already have fvwm. > > > If I do startx, then whole bunch of X sessions start > > That sounds like fvwm. > > > but I am unable to bring up fvwm. > > I wouldn't be so sure :-) > > Greg >