Hello, I used to use PC with FreeBSD-4.7-STABLE as a firewall. I was connected to ISP via modem. I needed to switch to another com port but it wasn't configured in kernel. So i rebuilt the kernel. Unfortunately, previous admin got kernel sources for FreeBSD 4.8 and I didn't know about that. When I rebooted with new kernel ps command didn't work. So I cvsuped src-all with "*default release=cvs tag=RELENG_4" (my cvsup file is attached bellow, i found it in /usr/share/examples/cvsup). I expected to get stable FreeBSD 4 release. I was surprised after I did `make buildworld', `make buildkernel', `make installkernel' and `make installworld' when I found that it was FreeBSD 4.10-PRERELEASE. It happened about three weeks ago. Well, actually everything went ok during making the world but my modem didn't work with this release. I use US-Robotics Courier V.Everything with V.34. It shows strange behaviour that you can see in the following excerpt from /var/log/ppp.log: <ppp.log> Jun 2 17:25:56 gateway ppp[64]: tun0: Chat: deflink: Redial timer expired. Jun 2 17:25:56 gateway ppp[64]: tun0: Phase: deflink: Connected! Jun 2 17:25:56 gateway ppp[64]: tun0: Phase: deflink: opening -> dial Jun 2 17:25:56 gateway ppp[64]: tun0: Chat: Phone: 15573 Jun 2 17:25:56 gateway ppp[64]: tun0: Chat: deflink: Dial attempt 6 of 25 Jun 2 17:25:56 gateway ppp[64]: tun0: Chat: Send: ATZ^M Jun 2 17:25:56 gateway ppp[64]: tun0: Chat: Expect(3): OK Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Expect timeout Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Send: ATZ^M Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Expect(3): OK Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Received: ATZ^MATZ^M^M Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Received: OK^M Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Send: ATDP15573^M Jun 2 17:25:59 gateway ppp[64]: tun0: Chat: Expect(60): CONNECT Jun 2 17:27:00 gateway ppp[64]: tun0: Chat: Expect timeout Jun 2 17:27:00 gateway ppp[64]: tun0: Warning: Chat script failed Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: deflink: dial -> hangup Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: deflink: Disconnected! Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: deflink: Connect time: 64 secs: 0 octets in, 0 octets out Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: deflink: 0 packets in, 0 packets out Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Wed Jun 2 17:25:56 2004 Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: deflink: hangup -> opening Jun 2 17:27:00 gateway ppp[64]: tun0: Phase: deflink: Enter pause (22) for redialing. </ppp.log> Look what modem replies to "ATZ" command! And it also turns on "TR" LED on the front panel. There are four LEDs constantly turned on "TR", "MR", "RS" and "CS" and nothing happens. When I tried to connect to the modem with "cu" command I found that i need to repeat a command twice to make the modem to execute it. Well, yesterday I cvsupped src-all again and built the world from the beginning. Now it turns to be FreeBSD 4.10-STABLE but my modem still doesn't work. BTW, it works when I boot old 4.7 kernel. Can you help me to fix the problem? Best regards, Alexey -------------- next part -------------- # $FreeBSD: src/share/examples/cvsup/4.x-stable-supfile,v 1.1.4.1 2000/03/13 19:26:08 dcs Exp $ # # This file contains all of the "CVSup collections" that make up the # FreeBSD-stable source tree. # # CVSup (CVS Update Protocol) allows you to download the latest CVS # tree (or any branch of development therefrom) to your system easily # and efficiently (far more so than with sup, which CVSup is aimed # at replacing). If you're running CVSup interactively, and are # currently using an X display server, you should run CVSup as follows # to keep your CVS tree up-to-date: # # cvsup stable-supfile # # If not running X, or invoking cvsup from a non-interactive script, then # run it as follows: # # cvsup -g -L 2 stable-supfile # # You may wish to change some of the settings in this file to better # suit your system: # # host=CHANGE_THIS.FreeBSD.org # This specifies the server host which will supply the # file updates. You must change it to one of the CVSup # mirror sites listed in the FreeBSD Handbook at # http://www.freebsd.org/handbook/mirrors.html. # You can override this setting on the command line # with cvsup's "-h host" option. # # base=/usr # This specifies the root where CVSup will store information # about the collections you have transferred to your system. # A setting of "/usr" will generate this information in # /usr/sup. Even if you are CVSupping a large number of # collections, you will be hard pressed to generate more than # ~1MB of data in this directory. You can override the # "base" setting on the command line with cvsup's "-b base" # option. This directory must exist in order to run CVSup. # # prefix=/usr # This specifies where to place the requested files. A # setting of "/usr" will place all of the files requested # in "/usr/src" (e.g., "/usr/src/bin", "/usr/src/lib"). # The prefix directory must exist in order to run CVSup. # ############################################################################### # # DANGER! WARNING! LOOK OUT! VORSICHT! # # If you add any of the ports collections to this file, be sure to # specify them like this: # # ports-all tag=. # # If you leave out the "tag=." portion, CVSup will delete all of # the files in your ports tree. That is because the ports collections # do not use the same tags as the main part of the FreeBSD source tree. # ############################################################################### # Defaults that apply to all the collections # # IMPORTANT: Change the next line to use one of the CVSup mirror sites # listed at http://www.freebsd.org/handbook/mirrors.html. *default host=cvsup.se.FreeBSD.org *default base=/usr *default prefix=/usr # The following line is for 4-stable. If you want 3.x-stable, change # "RELENG_4" to "RELENG_3". *default release=cvs tag=RELENG_4 *default delete use-rel-suffix # If your network link is a T1 or faster, comment out the following line. *default compress ## Main Source Tree. # # The easiest way to get the main source tree is to use the "src-all" # mega-collection. It includes all of the individual "src-*" collections, # except the export-restricted collections. src-all # These are the individual collections that make up "src-all". If you # use these, be sure to comment out "src-all" above. #src-base #src-bin #src-contrib #src-etc #src-games #src-gnu #src-include #src-kerberos5 #src-kerberosIV #src-lib #src-libexec #src-release #src-sbin #src-share #src-sys #src-tools #src-usrbin #src-usrsbin ## Export-restricted collections. # # Only people in the USA and Canada may fetch these collections. If # you are not in the USA or Canada, please use the collections in the # "secure-stable-supfile" instead. # # The easiest way to get the export-restricted code is to use the # "cvs-crypto" mega-collection. #cvs-crypto # # These are the individual collections that make up "cvs-crypto". If # you use these, be sure to comment out "cvs-crypto" above. #src-crypto #src-secure #src-sys-crypto