From owner-freebsd-isdn Wed Dec 13 12: 8:37 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 12:08:34 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id E325437B400 for ; Wed, 13 Dec 2000 12:08:33 -0800 (PST) Received: from bastion.localhost (pC19F5A73.dip.t-dialin.net [193.159.90.115]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id VAA15649 for ; Wed, 13 Dec 2000 21:08:11 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBDK7nl72815 for ; Wed, 13 Dec 2000 20:07:49 GMT Date: Wed, 13 Dec 2000 21:07:09 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <891752870.20001213210709@x-itec.de> To: freebsd-isdn@FreeBSD.ORG Subject: GRRRRRRRRR COMPILER ERRORS Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello freebsd-isdn, I really DISLIKE the ISDN-DRIVER for *BSD! ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct ion `DELAY' ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct ion `IF_HANDOFF' ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup': ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func tion `mtx_init' ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt x' ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th is function) ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report ed only once ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.) ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt x' *** Error code 1 Any comments? Itīs nearly impossible to compile a new kernel with this driver!!!!!!!!!!!!!!!!!!! -- Best regards, Boris mailto:koester@x-itec.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Dec 13 13:40: 2 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 13:39:59 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 7EEB837B404 for ; Wed, 13 Dec 2000 13:39:58 -0800 (PST) Received: from fwd02.sul.t-online.com by mailout06.sul.t-online.com with smtp id 146Jcy-0006yI-05; Wed, 13 Dec 2000 22:39:56 +0100 Received: from pippin.laverenz.de (340023018074-0001@[62.227.97.190]) by fmrl02.sul.t-online.com with esmtp id 146Jck-043snYC; Wed, 13 Dec 2000 22:39:42 +0100 Received: from laverenz.de (turin.laverenz.de [192.168.100.3]) by pippin.laverenz.de (8.11.1/8.11.1) with ESMTP id eBDLdQq32998 for ; Wed, 13 Dec 2000 22:39:26 +0100 (CET) (envelope-from uwe@laverenz.de) Message-ID: <3A37EBB4.DE342219@laverenz.de> Date: Wed, 13 Dec 2000 22:35:48 +0100 From: Uwe Laverenz Organization: private Unix site (game mode ;-) X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: Re: GRRRRRRRRR COMPILER ERRORS References: <891752870.20001213210709@x-itec.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Sender: 340023018074-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Boris, > I really DISLIKE the ISDN-DRIVER for *BSD! Who cares? Many people are quite happy with i4b and most of us think that it is a very nice piece of software. If you really dislike it, why don't you just write your own ISDN-suite? Remember that you're talking about free software here and that many people are working hard on this! > Any comments? Itīs nearly impossible to compile a new kernel with this > driver!!!!!!!!!!!!!!!!!!! I don't think that this is a general problem with i4b, but since you don't give us any information about what exactly you're trying to do, I can't help you. Uwe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Dec 13 13:48:32 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 13:48:30 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mustang.introweb.nl (mustang.introweb.nl [195.86.14.66]) by hub.freebsd.org (Postfix) with ESMTP id 63FA837B404 for ; Wed, 13 Dec 2000 13:48:29 -0800 (PST) Received: from localhost (edwin@localhost) by mustang.introweb.nl (8.9.3/8.9.3) with ESMTP id WAA21379; Wed, 13 Dec 2000 22:50:29 +0100 (CET) Date: Wed, 13 Dec 2000 22:50:29 +0100 (CET) From: Edwin To: Boris Cc: freebsd-isdn@freebsd.org Subject: Re: GRRRRRRRRR COMPILER ERRORS In-Reply-To: <891752870.20001213210709@x-itec.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some positive sounds: I'm using FreeBSD 4.2. No problems at all with my Teles 16.3 ISA non-PNP. Works like a charm. Multilink automatically picks up and drops the second line (configurable in percentage of load). I guess it's not a general problem. Looks like then driver for your AVM A1 PCI has some compilation-problems.=20 Be sure to define the necessary things for ISDN in your kernel config ! Make clean, make depend, make. On Wed, 13 Dec 2000, Boris wrote: > Hello freebsd-isdn, >=20 > I really DISLIKE the ISDN-DRIVER for *BSD! >=20 > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp= ': > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration o= f funct > ion `DELAY' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration o= f funct > ion `IF_HANDOFF' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup= ': > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration = of func > tion `mtx_init' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named = `ifq_mt > x' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first us= e in th > is function) > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is= report > ed only once > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears i= n.) > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named = `ifq_mt > x' > *** Error code 1 >=20 > Any comments? It=B4s nearly impossible to compile a new kernel with this > driver!!!!!!!!!!!!!!!!!!! >=20 > --=20 > Best regards, > Boris mailto:koester@x-itec.de >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Dec 13 14: 0:28 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 14:00:27 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from gnu.in-berlin.de (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id D653137B400 for ; Wed, 13 Dec 2000 14:00:25 -0800 (PST) Received: from hirsch.in-berlin.de (root@hirsch.colt.in-berlin.de [213.61.118.6]) by gnu.in-berlin.de (8.10.1/8.10.1) with ESMTP id eBDM0Ht24633; Wed, 13 Dec 2000 23:00:17 +0100 (CET) (envelope-from ripley@server.nostromo.in-berlin.de) Received: (from uucp@localhost) by hirsch.in-berlin.de (8.11.1/8.11.1/Debian 8.11.0-6) with UUCP id eBDM0Hv14899; Wed, 13 Dec 2000 23:00:17 +0100 X-Envelope-From: ripley@server.nostromo.in-berlin.de X-Envelope-To: freebsd-isdn@FreeBSD.ORG Received: (from ripley@localhost) by server.nostromo.in-berlin.de (8.9.3/8.9.3) id WAA81092; Wed, 13 Dec 2000 22:53:46 +0100 (CET) (envelope-from ripley) Date: Wed, 13 Dec 2000 22:53:45 +0100 From: "H. Eckert" To: Boris Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: GRRRRRRRRR COMPILER ERRORS Message-ID: <20001213225345.B81016@server.nostromo.in-berlin.de> References: <891752870.20001213210709@x-itec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <891752870.20001213210709@x-itec.de>; from koester@x-itec.de on Wed, Dec 13, 2000 at 09:07:09PM -0800 Sender: ripley@server.nostromo.in-berlin.de Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Boris (koester@x-itec.de): > Any comments? Itīs nearly impossible to compile a new kernel with this > driver!!!!!!!!!!!!!!!!!!! I'd recommend a new keyboard to prevent massive typing errors. When you're done with that, please send us the kernel's config file so we can tell you what you forgot to include. Greetings, Ripley -- H. Eckert, 12051 Berlin ISO 8859-1: Ä=Ae, Ö=Oe, Ü=Ue, ä=ae, ö=oe, ü=ue, ß=sz. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Dec 13 15: 5: 3 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 15:04:55 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 8F7A037B400 for ; Wed, 13 Dec 2000 15:04:53 -0800 (PST) Received: from bastion.localhost (p3E9E170D.dip.t-dialin.net [62.158.23.13]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id AAA14139; Thu, 14 Dec 2000 00:04:50 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBDN50Z00490; Wed, 13 Dec 2000 23:05:00 GMT Date: Thu, 14 Dec 2000 00:04:26 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <1977025592.20001214000426@x-itec.de> To: "H. Eckert" Cc: freebsd-isdn@FreeBSD.ORG Subject: Re[2]: GRRRRRRRRR COMPILER ERRORS In-reply-To: <20001213225345.B81016@server.nostromo.in-berlin.de> References: <891752870.20001213210709@x-itec.de> <20001213225345.B81016@server.nostromo.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello H., Wednesday, December 13, 2000, 1:53:45 PM, you wrote: HE> When you're done with that, please send us the kernel's config HE> file so we can tell you what you forgot to include. Good idea, here it comes and thanks for you help. machine i386 #cpu I386_CPU #cpu I486_CPU cpu I586_CPU #cpu I686_CPU ident GENERICbk maxusers 10 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device amd # AMD 53C974 (Teckram DC-390(T)) device isp # Qlogic family device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured device adv0 at isa? device adw device bt0 at isa? device aha0 at isa? device aic0 at isa? device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device dpt # DPT Smartcache - See LINT for options! device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers device ida # Compaq Smart RAID device amr # AMI MegaRAID device mlx # Mylex DAC960 family device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) device tx # SMC 9432TX (83c170 ``EPIC'') device vx # 3Com 3c590, 3c595 (``Vortex'') device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device pcn # AMD Am79C79x PCI 10/100 NICs device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ex device ep device fe0 at isa? port 0x300 # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA device an # Xircom Ethernet device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 irq 10 drq 0 device cs0 at isa? port 0x300 device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet options CODA pseudo-device vcoda 4 device ifpi0 #fritz pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" pseudo-device "i4bctl" 1 pseudo-device "i4brbch" 4 pseudo-device "i4btel" 4 pseudo-device "i4bipr" 4 pseudo-device "i4bisppp" 4 options IPR_VJ options IPR_LOG=20 options IPFIREWALL options IPDIVERT -- Best regards, Boris mailto:koester@x-itec.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Dec 13 18: 4:37 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 18:04:32 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id E49E337B400 for ; Wed, 13 Dec 2000 18:04:31 -0800 (PST) Received: from rosa.physik.TU-Berlin.DE (rosa.physik.TU-Berlin.DE [130.149.160.209]) by emmi.physik.TU-Berlin.DE (8.11.1/8.9.3) with ESMTP id eBE24TW12854; Thu, 14 Dec 2000 03:04:29 +0100 (CET) (envelope-from jan@emmi.physik.TU-Berlin.DE) From: Jan Riedinger Received: (from jan@localhost) by rosa.physik.TU-Berlin.DE (8.9.3/8.9.2) id DAA65499; Thu, 14 Dec 2000 03:04:29 +0100 (CET) (envelope-from jan@mail.physik.TU-Berlin.DE) Message-Id: <200012140204.DAA65499@rosa.physik.TU-Berlin.DE> Subject: Urgent: Trouble installing AVM Fritz!Card PCI To: freebsd-isdn@freebsd.org Date: Thu, 14 Dec 2000 03:04:29 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: jan@emmi.physik.TU-Berlin.DE Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I can't get running a new AVM Fritz!Card PCI under FreeBSD R4.2. At startup (dmesg) I get isic0: at device 10.0 on pci0 avma1pp0: couldn't map IO port device_probe_and_attach: isic0 attach returned 6 . . i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) . . i4bctl: ISDN system control port attached i4btrc: 4 ISDN trace device(s) attached . i4bisppp: 4 ISDN SyncPPP device(s) attached IPv6 packet filtering initialized, unlimited logging i4b: ISDN call control device attached . . device_probe_and_attach: isic0 attach returned 6 isic0: at device 10.0 on pci0 avma1pp0: couldn't map IO port device_probe_and_attach: isic0 attach returned 6 As expected the trial to start isdnd fails: Dec 14 08:55:09 server isdnd[310]: ERR init_controller: no ISDN controller found! Dec 14 08:55:09 server isdnd[310]: DMN daemon terminating, exitval = 1 What's going on? What could be wrong? It's a system with an Asus A7V mainbord. The same card is running fine on an other system with almost the same kernel configuration under R4.0. You can find the complete dmesg output below. Because I have to deliever the system at Friday far away from me and I urgently need remote access I would be very thankful, if someone could give me a hint quickly. Thank you very much Jan Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Thu Dec 14 04:59:23 CET 2000 root@nw:/usr/src/sys/compile/WITTMANN Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (756.74-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x630 Stepping = 0 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 134135808 (130992K bytes) avail memory = 126390272 (123428K bytes) Preloaded elf kernel "kernel" at 0xc0423000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 9 pci0: at 4.3 irq 9 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x9400-0x947f mem 0xe1000000-0xe100007f irq 9 at device 9.0 on pci0 xl0: Ethernet address: 00:01:02:f0:97:03 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isic0: at device 10.0 on pci0 avma1pp0: couldn't map IO port device_probe_and_attach: isic0 attach returned 6 ahc0: port 0x8800-0x88ff mem 0xe0000000-0xe0000fff irq 11 at device 12.0 on pci0 aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs atapci1: port 0x7000-0x703f,0x7400-0x7403,0x7800-0x7807,0x8000-0x8003,0x8400-0x8407 mem 0xdf800000-0xdf81ffff irq 10 at device 17.0 on pci0 pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) DUMMYNET initialized (000608) i4bctl: ISDN system control port attached i4btrc: 4 ISDN trace device(s) attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default i4bisppp: 4 ISDN SyncPPP device(s) attached IPv6 packet filtering initialized, unlimited logging i4b: ISDN call control device attached BRIDGE 990810, have 18 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.01.02.f0.97.03 IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled ad0: 78167MB [158816/16/63] at ata0-master UDMA66 ad1: 78167MB [158816/16/63] at ata0-slave UDMA66 ad2: 78167MB [158816/16/63] at ata1-master UDMA66 ad3: 78167MB [158816/16/63] at ata1-slave UDMA66 Waiting 2 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers sa1 at ahc0 bus 0 target 5 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) Mounting root from ufs:/dev/ad0s1a vinum: loaded vinum: reading configuration from /dev/ad3s1g vinum: updating configuration from /dev/ad3s1f vinum: updating configuration from /dev/ad3s1e vinum: updating configuration from /dev/ad2s1g vinum: updating configuration from /dev/ad2s1e vinum: updating configuration from /dev/ad2s1f vinum: updating configuration from /dev/ad1s1f vinum: updating configuration from /dev/ad1s1e vinum: updating configuration from /dev/ad1s1d vinum: updating configuration from /dev/ad0s1f vinum: updating configuration from /dev/ad0s1e vinum: updating configuration from /dev/ad0s1d ipr0: not multicast capable, IPv6 not enabled ipr1: not multicast capable, IPv6 not enabled uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 9 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered isic0: at device 10.0 on pci0 avma1pp0: couldn't map IO port device_probe_and_attach: isic0 attach returned 6 isic0: at device 10.0 on pci0 avma1pp0: couldn't map IO port device_probe_and_attach: isic0 attach returned 6 cd0 at ahc0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Dec 13 23:52:17 2000 From owner-freebsd-isdn@FreeBSD.ORG Wed Dec 13 23:52:15 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 4DF7937B400 for ; Wed, 13 Dec 2000 23:52:15 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 9DD0F5D06; Thu, 14 Dec 2000 08:51:53 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id EB6882B3; Thu, 14 Dec 2000 09:00:14 +0100 (MET) Subject: Re: Urgent: Trouble installing AVM Fritz!Card PCI In-Reply-To: <200012140204.DAA65499@rosa.physik.TU-Berlin.DE> "from Jan Riedinger at Dec 14, 2000 03:04:29 am" To: Jan Riedinger Date: Thu, 14 Dec 2000 09:00:14 +0100 (MET) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20001214080014.EB6882B3@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Jan Riedinger: > I can't get running a new AVM Fritz!Card PCI under FreeBSD R4.2. > At startup (dmesg) I get > > isic0: at device 10.0 on pci0 > avma1pp0: couldn't map IO port The driver for the AVM card is not able to allocate an IO port for the card because the address where it wants to allocate it is already occupied by another card. I have no idea whether this is a bug in your BIOS, in the AVM driver or in another driver (or the PCI kernel code) but this should not happen under normal circumstances. The only way i see to solve this is to find out which other card is the reason for the clash and either swap cards, exchange cards, or try using different slots for the/some cards. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 0: 5: 2 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 00:05:00 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 739D937B400 for ; Thu, 14 Dec 2000 00:04:58 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 5356D5D06; Thu, 14 Dec 2000 09:04:37 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id D4DB62B3; Thu, 14 Dec 2000 09:12:58 +0100 (MET) Subject: Re: GRRRRRRRRR COMPILER ERRORS In-Reply-To: <891752870.20001213210709@x-itec.de> "from Boris at Dec 13, 2000 09:07:09 pm" To: Boris Date: Thu, 14 Dec 2000 09:12:58 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20001214081258.D4DB62B3@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Boris: > I really DISLIKE the ISDN-DRIVER for *BSD! I have no idea how you come to the conclusion that being rude in this way on the list will give you polite and fast help back for your problem. Anyway, in case you want to try again in a more polite manner, don't forget to give a complete bug report consisting at least of: the FreeBSD version you are using, the i4b version you are using, whether you use the bundeled i4b version or have overinstalled another i4b version, your kernel config file and the list of steps taken to get i4b installed so far. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 0:38:43 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 00:38:41 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id BF7AB37B400 for ; Thu, 14 Dec 2000 00:38:40 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id JAA26783; Thu, 14 Dec 2000 09:38:27 +0100 (CET) (envelope-from kuku) Date: Thu, 14 Dec 2000 09:38:27 +0100 From: Christoph Kukulies To: Boris Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: GRRRRRRRRR COMPILER ERRORS Message-ID: <20001214093826.C26690@gil.physik.rwth-aachen.de> References: <891752870.20001213210709@x-itec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <891752870.20001213210709@x-itec.de>; from koester@x-itec.de on Wed, Dec 13, 2000 at 09:07:09PM -0800 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Dec 13, 2000 at 09:07:09PM -0800, Boris wrote: > Hello freebsd-isdn, > > I really DISLIKE the ISDN-DRIVER for *BSD! Why? > > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct > ion `DELAY' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct > ion `IF_HANDOFF' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup': > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func > tion `mtx_init' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt > x' > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th > is function) > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report > ed only once > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.) > ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt > x' > *** Error code 1 > > Any comments? Itīs nearly impossible to compile a new kernel with this > driver!!!!!!!!!!!!!!!!!!! Shht. Don't shout. You don't say which version of FreeBSD you are using. > -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 5:27: 4 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 05:27:01 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id E094137B400 for ; Thu, 14 Dec 2000 05:27:00 -0800 (PST) Received: from bastion.localhost (p3EE3FFB6.dip.t-dialin.net [62.227.255.182]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id OAA00811; Thu, 14 Dec 2000 14:26:58 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBEDR9V01235; Thu, 14 Dec 2000 13:27:09 GMT Date: Thu, 14 Dec 2000 14:26:30 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <12758749076.20001214142630@x-itec.de> To: Christoph Kukulies Cc: freebsd-isdn@FreeBSD.ORG Subject: Re[2]: GRRRRRRRRR COMPILER ERRORS In-reply-To: <20001214093826.C26690@gil.physik.rwth-aachen.de> References: <891752870.20001213210709@x-itec.de> <20001214093826.C26690@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Christoph, Thursday, December 14, 2000, 12:38:27 AM, you wrote: CK> On Wed, Dec 13, 2000 at 09:07:09PM -0800, Boris wrote: >> Hello freebsd-isdn, >> >> I really DISLIKE the ISDN-DRIVER for *BSD! CK> Why? Last time i lost a lot of data while recompiling a fresh 4.2 kernel from cvs repository. I made make world (worked), i applied the i4b patch to the kernel, recompiled the kernel -> stop error, i restarted my server and nothing worked anymore because of no new kernel. I lost a week for reinstalling and reconfiguring my freebsd machine only because the i4b driver makes me crazy and nothing works. This you can see is from a fresh installed 4.2 release box after updating with cvs. My current version is as following: uname -a FreeBSD bastion.localhost 4.2-STABLE FreeBSD 4.2-STABLE #1: Tue Dec 12 19:03:586 Try it yourself! update your sources via cvs and try to get the i4b up and running, i wish you a lot of fun -( >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct >> ion `DELAY' >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct >> ion `IF_HANDOFF' >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup': >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func >> tion `mtx_init' >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt >> x' >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th >> is function) >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report >> ed only once >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.) >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt >> x' >> *** Error code 1 >> >> Any comments? Itīs nearly impossible to compile a new kernel with this >> driver!!!!!!!!!!!!!!!!!!! CK> Shht. Don't shout. You don't say which version of FreeBSD you are using. >> currently 4.2 stable #1, downloaded latest sources from cvs yesterday via cvsup. -- Best regards, Boris mailto:koester@x-itec.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 5:48:17 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 05:48:14 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 7C32A37B402 for ; Thu, 14 Dec 2000 05:48:13 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id OAA28034 for freebsd-isdn@freebsd.org; Thu, 14 Dec 2000 14:48:11 +0100 (CET) (envelope-from kuku) Date: Thu, 14 Dec 2000 14:48:11 +0100 From: Christoph Kukulies To: freebsd-isdn@freebsd.org Subject: Re: GRRRRRRRRR COMPILER ERRORS Message-ID: <20001214144811.A28018@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 02:26:30PM -0800, Boris wrote: > Hello Christoph, > > Thursday, December 14, 2000, 12:38:27 AM, you wrote: > > CK> On Wed, Dec 13, 2000 at 09:07:09PM -0800, Boris wrote: >> Hello freebsd-isdn, > >> > >> I really DISLIKE the ISDN-DRIVER for *BSD! > > CK> Why? > > Last time i lost a lot of data while recompiling a fresh 4.2 kernel > from cvs repository. I made make world (worked), i applied the i4b > patch to the kernel, recompiled the kernel -> stop error, i restarted > my server and nothing worked anymore because of no new kernel. I lost > a week for reinstalling and reconfiguring my freebsd machine only > because the i4b driver makes me crazy and nothing works. When you are playing with fire or knocking away the ground under your feet you cannot blame i4b for this. I myself am using i4b on the server which I upgrade now and then. Presentently I'm using 4.2 (RELEASE though) (which I installed from a CD I burned from the iso-image from ftp.freebsd.org, btw.) Anyway, it happened to me last week that I was crazy enough to cvsup -current into that important server I'm using for i4b and I was off the net for two or three days (fortunately over the weekend and I had a parallel access which was still working). Interestingly enough that the problem I had was compiling a kernel and it was the mutex.h code that was currently being worked on that made kernel compilation break in the i4b area. Being aware of the dangers when doing this I don't complain loudly or blame i4b. That's unfair if not foolish. > > This you can see is from a fresh installed 4.2 release box after > updating with cvs. My current version is as following: > > uname -a My box (and I built a special kernel with i4b): FreeBSD isdn-kukulies.dialup.rwth-aachen.de 4.2-RELEASE FreeBSD 4.2-RELEASE #2: Mon Dec 11 10:59:51 CET 2000 kuku@isdn-kukulies.dialup.rwth-aachen.de:/usr/src/sys/compile/MONKAVMIFB i386 > > FreeBSD bastion.localhost 4.2-STABLE FreeBSD 4.2-STABLE #1: Tue Dec 12 19:03:586 > > Try it yourself! update your sources via cvs and try to get the i4b up > and running, i wish you a lot of fun -( Maybe you update (cvsup once more and the problem is gone). > > >> > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct > >> ion `DELAY' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct > >> ion `IF_HANDOFF' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup': > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func > >> tion `mtx_init' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt > >> x' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th > >> is function) > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report > >> ed only once > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.) > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt > >> x' > >> *** Error code 1 > >> > >> Any comments? Itīs nearly impossible to compile a new kernel with this > >> driver!!!!!!!!!!!!!!!!!!! > > CK> Shht. Don't shout. You don't say which version of FreeBSD you are using. > > >> > > currently 4.2 stable #1, downloaded latest sources from cvs yesterday > via cvsup. Do you want me send you a 4.2-RELEASE CD so you can get on your feet again? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 6:13:41 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 06:13:39 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 301F337B402 for ; Thu, 14 Dec 2000 06:13:39 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id PAA28175; Thu, 14 Dec 2000 15:13:37 +0100 (CET) (envelope-from kuku) Date: Thu, 14 Dec 2000 15:13:37 +0100 From: Christoph Kukulies To: Simon Putz Cc: freebsd-isdn@freebsd.org Subject: Re: GRRRRRRRRR COMPILER ERRORS Message-ID: <20001214151337.A28134@gil.physik.rwth-aachen.de> References: <20001214144811.A28018@gil.physik.rwth-aachen.de> <005201c065d5$ad037be0$6300a8c0@putzei> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <005201c065d5$ad037be0$6300a8c0@putzei>; from Simon.Putz@t-online.de on Thu, Dec 14, 2000 at 02:56:36PM +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 02:56:36PM +0100, Simon Putz wrote: > hi ! > > i got 4.2 from ftp and tried to recompile kernel for i4b. > it was not working (probably a config error on my side), > so i cvsuped .. now i4b is compiling but the kernel is giving me > blowfish not found errors.so you see, sometimes its not the best > to have always the latest version.and also i must say that i was not > able to > get any support from -questions or on IRC.its pretty annoying. Do always make depend make Also you have to install ssys.?? sinclude.?? and that all. I believe I installed the whole 4.2-RELEASE src tree and did a cd /usr/src make include first before configuring/compiling the kernel. kernel config file syntax is changing dramatically and it looks that 4.2 is something between two stools. I believe I had to enable the whole NETGRAPH options stuff to get a kernel compiled under 4.2-RELEASE. > > bye > simon putz -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 6:15:43 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 06:15:42 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 480A537B400 for ; Thu, 14 Dec 2000 06:15:41 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id PAA28212; Thu, 14 Dec 2000 15:15:39 +0100 (CET) (envelope-from kuku) Date: Thu, 14 Dec 2000 15:15:39 +0100 From: Christoph Kukulies To: Christoph Kukulies Cc: Simon Putz , freebsd-isdn@FreeBSD.ORG Subject: Re: GRRRRRRRRR COMPILER ERRORS Message-ID: <20001214151539.B28134@gil.physik.rwth-aachen.de> References: <20001214144811.A28018@gil.physik.rwth-aachen.de> <005201c065d5$ad037be0$6300a8c0@putzei> <20001214151337.A28134@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001214151337.A28134@gil.physik.rwth-aachen.de>; from kuku@gilberto.physik.RWTH-Aachen.DE on Thu, Dec 14, 2000 at 03:13:37PM +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 03:13:37PM +0100, Christoph Kukulies wrote: > NETGRAPH options stuff to get a kernel compiled under 4.2-RELEASE. That should read 'to get an i4b kernel compiled under 4.2-RELEASE.' > -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 6:36:18 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 06:36:11 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by hub.freebsd.org (Postfix) with ESMTP id BC1E137B402 for ; Thu, 14 Dec 2000 06:36:10 -0800 (PST) Received: from jaknl by athos.nl.uu.net with UUCP id ; Thu, 14 Dec 2000 15:35:54 +0100 Received: from jak.nl ([192.168.0.30]) by jak.nl (8.8.8/8.8.8) with ESMTP id PAA29842; Thu, 14 Dec 2000 15:38:05 +0100 (CET) (envelope-from arjan@jak.nl) Message-ID: <3A38D935.F4C1C181@jak.nl> Date: Thu, 14 Dec 2000 15:29:09 +0100 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Boris Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: GRRRRRRRRR COMPILER ERRORS References: <891752870.20001213210709@x-itec.de> <20001214093826.C26690@gil.physik.rwth-aachen.de> <12758749076.20001214142630@x-itec.de> Content-Type: multipart/mixed; boundary="------------A2E203886E69D1B750162B82" Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------A2E203886E69D1B750162B82 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Boris wrote: > Hello Christoph, > > Thursday, December 14, 2000, 12:38:27 AM, you wrote: > > CK> On Wed, Dec 13, 2000 at 09:07:09PM -0800, Boris wrote: > >> Hello freebsd-isdn, > >> > >> I really DISLIKE the ISDN-DRIVER for *BSD! > > CK> Why? > > Last time i lost a lot of data while recompiling a fresh 4.2 kernel I always rebuild the GENERIC kernel as first kernel after updating my src-tree from the CVS. In that way I always have a working kernel when my own kernel won't run. > from cvs repository. I made make world (worked), i applied the i4b > patch to the kernel, recompiled the kernel -> stop error, i restarted > my server and nothing worked anymore because of no new kernel. I lost > a week for reinstalling and reconfiguring my freebsd machine only > because the i4b driver makes me crazy and nothing works. I don't understand how you lost you data? Did you try to fix-it with a fix-it floppy?? > This you can see is from a fresh installed 4.2 release box after > updating with cvs. My current version is as following: > > uname -a > > FreeBSD bastion.localhost 4.2-STABLE FreeBSD 4.2-STABLE #1: Tue Dec 12 19:03:586 > > Try it yourself! update your sources via cvs and try to get the i4b up > and running, i wish you a lot of fun -( > > >> > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct > >> ion `DELAY' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct > >> ion `IF_HANDOFF' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup': > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func > >> tion `mtx_init' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt > >> x' > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th > >> is function) > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report > >> ed only once > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.) > >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt > >> x' > >> *** Error code 1 > >> > >> Any comments? Itīs nearly impossible to compile a new kernel with this > >> driver!!!!!!!!!!!!!!!!!!! > > CK> Shht. Don't shout. You don't say which version of FreeBSD you are using. > > >> > > currently 4.2 stable #1, downloaded latest sources from cvs yesterday > via cvsup. > > -- > Best regards, > Boris mailto:koester@x-itec.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message --------------A2E203886E69D1B750162B82 Content-Type: text/x-vcard; charset=us-ascii; name="arjan.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Arjan Knepper Content-Disposition: attachment; filename="arjan.vcf" begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:arjan@jak.nl x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard --------------A2E203886E69D1B750162B82-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 8:25: 0 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 08:24:58 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id 352F937B400 for ; Thu, 14 Dec 2000 08:24:57 -0800 (PST) Received: from rosa.physik.TU-Berlin.DE (rosa.physik.TU-Berlin.DE [130.149.160.209]) by emmi.physik.TU-Berlin.DE (8.11.1/8.9.3) with ESMTP id eBEGOtW64197; Thu, 14 Dec 2000 17:24:55 +0100 (CET) (envelope-from jan@emmi.physik.TU-Berlin.DE) From: Jan Riedinger Received: (from jan@localhost) by rosa.physik.TU-Berlin.DE (8.9.3/8.9.2) id RAA75300; Thu, 14 Dec 2000 17:24:55 +0100 (CET) (envelope-from jan@mail.physik.TU-Berlin.DE) Message-Id: <200012141624.RAA75300@rosa.physik.TU-Berlin.DE> Subject: Re: Urgent: Trouble installing AVM Fritz!Card PCI In-Reply-To: <20001214080014.EB6882B3@hcswork.hcs.de> from Hellmuth Michaelis at "Dec 14, 2000 09:00:14 am" To: hm@hcs.de Date: Thu, 14 Dec 2000 17:24:55 +0100 (CET) Cc: freebsd-isdn@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: jan@emmi.physik.TU-Berlin.DE Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Hellmuth! Thank you for the hints. I was able to found a solution with them. At first I tried it FreeBSD 4.0 on the failed system. It doesn't work too. Then I exchanged the graphic adapter and removed all other cards. No success. At last I looked at the BIOS configuration, because you wrote about a the possibilty of a BIOS bug. Setting the option "PNP OS system" to "No" solved the problem :-). This is strange, because there are no ISA slots at the board (ASUS A7V). Jan > >From the keyboard of Jan Riedinger: > > > I can't get running a new AVM Fritz!Card PCI under FreeBSD R4.2. > > At startup (dmesg) I get > > > > isic0: at device 10.0 on pci0 > > avma1pp0: couldn't map IO port > > The driver for the AVM card is not able to allocate an IO port for the card > because the address where it wants to allocate it is already occupied by > another card. > > I have no idea whether this is a bug in your BIOS, in the AVM driver or in > another driver (or the PCI kernel code) but this should not happen under > normal circumstances. > > The only way i see to solve this is to find out which other card is the > reason for the clash and either swap cards, exchange cards, or try using > different slots for the/some cards. > > hellmuth > -- > Hellmuth Michaelis Tel +49 40 55 97 47-70 > HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 > Oldesloer Strasse 97-99 Mail hm [at] hcs.de > D-22457 Hamburg WWW http://www.hcs.de > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 17:19:29 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 17:19:26 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 98FDE37B402 for ; Thu, 14 Dec 2000 17:19:25 -0800 (PST) Received: from bastion.localhost (p3E9E16FB.dip.t-dialin.net [62.158.22.251]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id CAA19264; Fri, 15 Dec 2000 02:19:22 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBF1JgV09641; Fri, 15 Dec 2000 01:19:42 GMT Date: Fri, 15 Dec 2000 02:18:55 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <2140483542.20001215021855@x-itec.de> To: Arjan Knepper Cc: freebsd-isdn@FreeBSD.ORG Subject: Re[2]: GRRRRRRRRR COMPILER ERRORS In-reply-To: <3A38D935.F4C1C181@jak.nl> References: <891752870.20001213210709@x-itec.de> <20001214093826.C26690@gil.physik.rwth-aachen.de> <12758749076.20001214142630@x-itec.de> <3A38D935.F4C1C181@jak.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Arjan, Thursday, December 14, 2000, 6:29:09 AM, you wrote: AK> Boris wrote: >> >> >> >> I really DISLIKE the ISDN-DRIVER for *BSD! >> >> CK> Why? >> Maybe my reaction was incorrect, sorry. I was angry about the data loss. My lovely BSD Server is still not running with i4b and the latest stable -((( AK> I don't understand how you lost you data? Did you try to fix-it with a fix-it floppy?? No, i made build world, the compiling of the kernel was impossible, i restarted the server and BANG every network functions were disabled, i have tried to backup as much as possible but it took me a week to reconfigure the server (installing/compiling everything i was working with, and *yes* i do manual compiling of some apps). I tried to overwrite the current version (complete reinstall) but they were still problems, so i had to reformat the drive because i have no much time left for my project(s). This was 5 days ago, and now i can slowly begin working again, and i know that i would never again compile the kernel with i4b in the next month. Bah... As I said, just update the src with cvsup and try to compile it with i4b (the rel4-stable branch). HAVE FUN -(((( A suggestion to everyone, just try it ... Still no solution for this: >> >> >> >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct >> >> ion `DELAY' >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr': >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct >> >> ion `IF_HANDOFF' >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup': >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func >> >> tion `mtx_init' >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt >> >> x' >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th >> >> is function) >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report >> >> ed only once >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.) >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt >> >> x' >> >> *** Error code 1 >> >> >> >> Any comments? Itīs nearly impossible to compile a new kernel with this >> >> driver!!!!!!!!!!!!!!!!!!! >> >> CK> Shht. Don't shout. You don't say which version of FreeBSD you are using. >> >> >> >> >> currently 4.2 stable #1, downloaded latest sources from cvs yesterday >> via cvsup. >> >> -- >> Best regards, >> Boris mailto:koester@x-itec.de >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-isdn" in the body of the message -- Best regards, Boris mailto:koester@x-itec.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Dec 14 17:54:43 2000 From owner-freebsd-isdn@FreeBSD.ORG Thu Dec 14 17:54:41 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from bitbucket.extern.uniface.nl (bitbucket.extern.uniface.nl [193.78.88.139]) by hub.freebsd.org (Postfix) with ESMTP id 5CFCA37B400 for ; Thu, 14 Dec 2000 17:54:41 -0800 (PST) Received: from bh2.nl.compuware.com (unknown [172.16.17.82]) by bitbucket.extern.uniface.nl (Postfix) with ESMTP id 7CFF28283 for ; Fri, 15 Dec 2000 02:54:39 +0100 (CET) Received: from trashcan.nl.compuware.com ([172.16.16.52]) by bh2.nl.compuware.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id Y65SQ43W; Fri, 15 Dec 2000 02:54:39 +0100 Received: from c1111.nl.compuware.com (c1111.nl.compuware.com [172.16.16.36]) by trashcan.nl.compuware.com (Postfix) with ESMTP id C76A0145A4; Fri, 15 Dec 2000 02:54:38 +0100 (CET) Date: Fri, 15 Dec 2000 02:54:38 +0100 (CET) From: Bert Driehuis X-Sender: bertd@c1111.nl.compuware.com To: freebsd-isdn@FreeBSD.ORG Subject: Re: Re[2]: GRRRRRRRRR COMPILER ERRORS In-Reply-To: <2140483542.20001215021855@x-itec.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Dec 2000, Boris wrote: > No, i made build world, the compiling of the kernel was impossible, i > restarted the server and BANG every network functions were disabled, i > have tried to backup as much as possible but it took me a week to > reconfigure the server. Maybe I'm old fashioned, but I never ever try to do two things at the same time. If you're updating your kernel to an unreleased version, you should expect breakage, so replacing the kernel with an untested one is asking for trouble. If your complaint boils down to "I expect CVSup to produce a perfectly running system and I'm disappointed", then you are absolutely right (and also very unrealistic). The people that develop the updates to FreeBSD stable are most likely not ISDN users, and if you CVSup you run the risk of encountering breakage. In the greater scheme of things, ISDN is not a central part of FreeBSD, because relatively few people have ISDN (as much as FreeBSD is not the life focus of the ISDN4BSD developers -- matter of fact, my ISDN gateway at home still is an ancient BSD/OS 3.1 system; I've got funnier things to do than spend my life upgrading stuff that works). First of all, you should consider getting a test system if you want to run untested combinations of software. Blaming FreeBSD for the problems you had because you inadvertantly blew away a working system is not the right thing to do. Second, not keeping a copy of a working kernel on your root partition is asking for trouble. The people that develop ISDN4BSD have non booting kernels all the time. It's the price for living on the bleeding edge. However, when that happens, they just boot from the previous kernel, remove the faulty kernel and mv the working one back. I even keep an even older kernel around in case I miss a horrible bug in a kernel that otherwise works. If you prepare right, downtime on your production machines is minimal. Cheers, -- Bert Bert Driehuis -- driehuis@playbeing.org -- +31-20-3116119 If the only tool you've got is an axe, every problem looks like fun! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 0:34: 3 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 00:34:00 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 1A75537B400 for ; Fri, 15 Dec 2000 00:34:00 -0800 (PST) Received: from bastion.localhost (p3E9E1515.dip.t-dialin.net [62.158.21.21]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id JAA04982; Fri, 15 Dec 2000 09:33:14 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBF8XDT23845; Fri, 15 Dec 2000 08:33:13 GMT Date: Fri, 15 Dec 2000 09:32:33 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <10066501434.20001215093233@x-itec.de> To: Bert Driehuis Cc: freebsd-isdn@FreeBSD.ORG Subject: Re[4]: GRRRRRRRRR COMPILER ERRORS In-reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Bert, Thursday, December 14, 2000, 5:54:38 PM, you wrote: BD> On Fri, 15 Dec 2000, Boris wrote: BD> Maybe I'm old fashioned, but I never ever try to do two things at the BD> same time. If you're updating your kernel to an unreleased version, you BD> should expect breakage, so replacing the kernel with an untested one is BD> asking for trouble. hm, ok. BD> If your complaint boils down to "I expect CVSup to produce a perfectly BD> running system and I'm disappointed", then you are absolutely right (and BD> also very unrealistic). The people that develop the updates to FreeBSD BD> stable are most likely not ISDN users, and if you CVSup you run the risk Ahh, i have understand! ok no problem. I thought that a stable commit is tested first by quality-assurance people (?). Hm, however i like to see whatīs going on with freebsd so i like to update the sources nearly daily -) It is a motivation to me if i am developing my litte progs. BD> of encountering breakage. In the greater scheme of things, ISDN is not a BD> central part of FreeBSD, because relatively few people have ISDN (as BD> much as FreeBSD is not the life focus of the ISDN4BSD developers -- Aaaah ok! BD> First of all, you should consider getting a test system if you want to BD> run untested combinations of software. Blaming FreeBSD for the problems not FreeBSD, i4b -) I love FreeBSD BD> you had because you inadvertantly blew away a working system is not the BD> right thing to do. *ggg yes this was my first complete failure on a production server hihi. BD> Second, not keeping a copy of a working kernel on your root partition is BD> asking for trouble. I had a working kernel, but the system was not working anymore after build world. When the trouble begans, i had bsd 4.1.1, updated the sources to the latest cvs, make world (works), i4b patch .. tried to compile the kernel.. after the i4b patch.. BANG -) The old 4.1.1 kernel was alyways available but i had no access to anything anymore after rebooting. Iīve got access denied, the only thing i could do is to log in, thatīs all. Ok iīm sorry for my reaction, it was my first real failure of a very important server and i have never expected this on a stable-branch. Now i know whatīs up and i had a chance to understand why sometimes something is wrong. I will try to get it up and running on my developer server first, before updating a netserver and i have learned to write a backup-script with all neccessary content i need for the next failure *gggg. Another person said to build a GENERIC kernel FIRST, a very good idea. So i will make a GENERIC kernel first after make world, then i try to get my configuration up and running. Thanks to all the people for helping me! -- Best regards, Boris mailto:koester@x-itec.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 5:48:55 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 05:48:52 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 5263137B400 for ; Fri, 15 Dec 2000 05:48:49 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 1A2485D15; Fri, 15 Dec 2000 14:48:26 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id 6BA82294; Fri, 15 Dec 2000 14:56:51 +0100 (MET) Subject: Re: Re[2]: GRRRRRRRRR COMPILER ERRORS In-Reply-To: <2140483542.20001215021855@x-itec.de> "from Boris at Dec 15, 2000 02:18:55 am" To: Boris Date: Fri, 15 Dec 2000 14:56:51 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20001215135651.6BA82294@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Boris: > left for my project(s). This was 5 days ago, and now i can slowly > begin working again, and i know that i would never again compile the > kernel with i4b in the next month. Bah... > > As I said, just update the src with cvsup and try to compile it with > i4b (the rel4-stable branch). HAVE FUN -(((( A suggestion to everyone, > just try it ... Since you still refuse to supply a complete bug report and instead are blaming the FreeBSD-stable developers in general and the i4b developers in special i tried to reproduce your problems here: The machine is FreeBSD hmnote.hcs.de 4.2-STABLE FreeBSD 4.2-STABLE #1: Thu Dec 14 17:34:54 CET 2000 root@hmnote.hcs.de:/usr/src/sys/compile/HMNOTE i386 Running config(8) with your configuration posted earlier with an unmodified FreeBSD-stable results in an unknown ifpi device error. This is expected since the i4b in 4.2-STABLE does not support the ifpi device. Instead of referring to a report from you i have to guess you overinstalled i4b 0.96.00 to the source tree. Overinstalling i4b 0.96.00 shows no errors, all files are setup and patched correctly, your kernel config file configures without problems and the resulting kernel is build without any problems: [...] cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c sh ../../conf/newvers.sh GENERICBK cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel text data bss dec hex filename 2742415 224144 191944 3158503 3031e7 kernel /sys/compile/BORIS uname -a FreeBSD hmnote.hcs.de 4.2-STABLE FreeBSD 4.2-STABLE #1: Thu Dec 14 17:34:54 CET 2000 root@hmnote.hcs.de:/usr/src/sys/compile/HMNOTE i386 /sys/compile/BORIS As you see, there is zero (repeat: Z E R O) problems in getting an 4.2-STABLE kernel configured and compiled with your kernel configuration file. > Still no solution for this: > > >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': Perhaps you might have overread an earlier mail from me, i'm repeating it here for your convenience: Anyway, in case you want to try again in a more polite manner, don't forget to give a complete bug report consisting at least of: the FreeBSD version you are using, the i4b version you are using, whether you use the bundeled i4b version or have overinstalled another i4b version, your kernel config file and the list of steps taken to get i4b installed so far. Please start interacting in a professional manner with people who might be able to help you and stop blaming and insulting others for your inablity to handle situations like the one you have - obviously - put yourself into. Have a nice day, hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 6:41:53 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 06:41:49 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id D987A37B400 for ; Fri, 15 Dec 2000 06:41:47 -0800 (PST) Received: from alvman.IbHaakh.de (pD900DFCC.dip.t-dialin.net [217.0.223.204]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id PAA02571; Fri, 15 Dec 2000 15:41:45 +0100 (MET) Received: from wilma.IbHaakh.de (wilma.IbHaakh.de [192.168.63.21]) by alvman.IbHaakh.de (8.11.1/8.11.1) with SMTP id eBFEd1I80285; Fri, 15 Dec 2000 15:39:01 +0100 (CET) (envelope-from Andreas@Haakh.de) From: Andreas Haakh Date: Fri, 15 Dec 2000 14:38:44 GMT Message-ID: <20001215.14384463@wilma.IbHaakh.de> Subject: Re: GRRRRRRRRR COMPILER ERRORS To: Boris Cc: Bert Driehuis , freebsd-isdn@FreeBSD.ORG In-Reply-To: <10066501434.20001215093233@x-itec.de> References: <10066501434.20001215093233@x-itec.de> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2;Win32) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Bert, I don't know the steps you followed to upgrade your OS. Nevertheless=20= there is a file called UDATING in /usr/src containig lots of important=20= informations... I usually do the following steps (well, if the changes to /usr/src/sys=20= are minor, then I omit some of them) make -i update >Update.log 2>&1 & (bash-syntax) inspect Update.log, search for changes, errors etc. read /usr/src/UPDATING patch some files (some patches to i4b didn't make it into stable ;-) make buildworld >World.log 2>&1 & inspect World.log if there are any errors. Under some circumstances You = need to make clean before make buildworld. save /kernel.old to /kernel.something make kernel KERNEL=3DMYKERNEL (this builds AND installs =84MYKERNEL=93 a= s=20 kernel. You can also do this in two steps: make buildkernel=20 KERNEL=3DMYKERNEL and make installkernel KERNEL=3DMYKERNEL if the=20 buildprocess was fine.) mergemaster (to update /etc) make installworld reboot Andreas >>>>>>>>>>>>>>>>>> Urspr=FCngliche Nachricht <<<<<<<<<<<<<<<<<< Am 15.12.2000, 18:32:33, schrieb Boris zum Thema Re[= 4]:=20 GRRRRRRRRR COMPILER ERRORS: > Hello Bert, > Thursday, December 14, 2000, 5:54:38 PM, you wrote: > BD> On Fri, 15 Dec 2000, Boris wrote: > BD> Maybe I'm old fashioned, but I never ever try to do two things at = the > BD> same time. If you're updating your kernel to an unreleased version= , you > BD> should expect breakage, so replacing the kernel with an untested o= ne is > BD> asking for trouble. > hm, ok. > BD> If your complaint boils down to "I expect CVSup to produce a perfe= ctly > BD> running system and I'm disappointed", then you are absolutely righ= t=20 (and > BD> also very unrealistic). The people that develop the updates to Fre= eBSD > BD> stable are most likely not ISDN users, and if you CVSup you run th= e=20 risk > Ahh, i have understand! ok no problem. I thought that a stable commit= > is tested first by quality-assurance people (?). Hm, however i like to= > see what=B4s going on with freebsd so i like to update the sources > nearly daily -) It is a motivation to me if i am developing my litte > progs. > BD> of encountering breakage. In the greater scheme of things, ISDN is= not=20 a > BD> central part of FreeBSD, because relatively few people have ISDN (= as > BD> much as FreeBSD is not the life focus of the ISDN4BSD developers -= - > Aaaah ok! > BD> First of all, you should consider getting a test system if you wan= t to > BD> run untested combinations of software. Blaming FreeBSD for the pro= blems > not FreeBSD, i4b -) I love FreeBSD > BD> you had because you inadvertantly blew away a working system is no= t the > BD> right thing to do. > *ggg yes this was my first complete failure on a production server > hihi. > BD> Second, not keeping a copy of a working kernel on your root partit= ion=20 is > BD> asking for trouble. > I had a working kernel, but the system was not working anymore after > build world. When the trouble begans, i had bsd 4.1.1, updated the > sources to the latest cvs, make world (works), i4b patch .. tried to > compile the kernel.. after the i4b patch.. BANG -) The old 4.1.1 > kernel was alyways available but i had no access to anything anymore > after rebooting. I=B4ve got access denied, the only thing i could do i= s > to log in, that=B4s all. > Ok i=B4m sorry for my reaction, it was my first real failure of a very= > important server and i have never expected this on a stable-branch. > Now i know what=B4s up and i had a chance to understand why sometimes= > something is wrong. I will try to get it up and running on my > developer server first, before updating a netserver and i have learned= > to write a backup-script with all neccessary content i need for the > next failure *gggg. Another person said to build a GENERIC kernel > FIRST, a very good idea. So i will make a GENERIC kernel first after > make world, then i try to get my configuration up and running. > Thanks to all the people for helping me! > -- > Best regards, > Boris mailto:koester@x-itec.de > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 6:53: 7 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 06:53:06 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 10C8037B400 for ; Fri, 15 Dec 2000 06:53:01 -0800 (PST) Received: from bastion.localhost (p3E9E1515.dip.t-dialin.net [62.158.21.21]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id PAA18959; Fri, 15 Dec 2000 15:52:59 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBFErGT88673; Fri, 15 Dec 2000 14:53:16 GMT Date: Fri, 15 Dec 2000 15:52:31 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <4089299115.20001215155231@x-itec.de> To: hm@hcs.de ((Hellmuth Michaelis)) Cc: freebsd-isdn@FreeBSD.ORG Subject: Re[4]: GRRRRRRRRR COMPILER ERRORS In-reply-To: <20001215135651.6BA82294@hcswork.hcs.de> References: <20001215135651.6BA82294@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Hellmuth, Friday, December 15, 2000, 5:56:51 AM, you wrote: HM> Overinstalling i4b 0.96.00 shows no errors, all files are setup and patched HM> correctly, your kernel config file configures without problems and the HM> resulting kernel is build without any problems: HM> As you see, there is zero (repeat: Z E R O) problems in getting an 4.2-STABLE HM> kernel configured and compiled with your kernel configuration file. Funny, but it was not working on the production server and not on the new, fresh installed 4.2-release with latest cvs stable update. >> Still no solution for this: >> >> >> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp': HM> Please start interacting in a professional manner with people who might HM> be able to help you and stop blaming and insulting others for your inablity HM> to handle situations like the one you have - obviously - put yourself into. You are right, i am no longer interested in finding a solution for this problem. Next time i am using a modem, so i avoid any conflicts. -- Best regards, Boris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 7:22:37 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 07:22:36 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 850E837B400 for ; Fri, 15 Dec 2000 07:22:35 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 5C4015D06; Fri, 15 Dec 2000 16:22:13 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id E442434E; Fri, 15 Dec 2000 16:30:38 +0100 (MET) Subject: Re: Urgent: Trouble installing AVM Fritz!Card PCI In-Reply-To: <200012141624.RAA75300@rosa.physik.TU-Berlin.DE> "from Jan Riedinger at Dec 14, 2000 05:24:55 pm" To: Jan Riedinger Date: Fri, 15 Dec 2000 16:30:38 +0100 (MET) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20001215153038.E442434E@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Jan Riedinger: > At last I looked at the BIOS configuration, because you wrote about a > the possibilty of a BIOS bug. Setting the option "PNP OS system" to > "No" solved the problem :-). This is strange, because there are no > ISA slots at the board (ASUS A7V). No, not that strange. As far as i understand it, setting PNP OS system to no instructs the BIOS to configure all ISA, ISA PnP and PCI cards in the system and resolve the resulting conflicts. Setting it to yes instructs the BIOS to hand this task (or parts of this task) over to the OS which is booted by the BIOS (FreeBSD in this case). Please correct me if i'm wrong. Given that, it is very likely that in your case setting your BIOS to PNP OS system = yes triggered a bug in the kernel autoconfiguration code. I personally run all systems where this option is selectable with settings set to PNP OS system = no. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 7:26:55 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 07:26:54 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id C653437B402 for ; Fri, 15 Dec 2000 07:26:53 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 8159B5D06; Fri, 15 Dec 2000 16:26:31 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id 0C33C34E; Fri, 15 Dec 2000 16:34:56 +0100 (MET) Subject: Re: Re[4]: GRRRRRRRRR COMPILER ERRORS In-Reply-To: <4089299115.20001215155231@x-itec.de> "from Boris at Dec 15, 2000 03:52:31 pm" To: Boris Date: Fri, 15 Dec 2000 16:34:56 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20001215153456.0C33C34E@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Boris: > You are right, i am no longer interested in finding a > solution for this problem. Thanks a lot for wasting our time, it was a pleasure! hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 12:13:46 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 12:13:43 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (Postfix) with ESMTP id C168D37B400 for ; Fri, 15 Dec 2000 12:13:42 -0800 (PST) Received: from nicky.cs.tu-berlin.de (mh@nicky.cs.tu-berlin.de [130.149.17.43]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id VAA23801 for ; Fri, 15 Dec 2000 21:13:10 +0100 (MET) Received: (from mh@localhost) by nicky.cs.tu-berlin.de (8.9.3/8.9.3) id VAA25599 for freebsd-isdn@freebsd.org; Fri, 15 Dec 2000 21:13:08 +0100 (MET) Date: Fri, 15 Dec 2000 21:13:04 +0100 From: Matthias Heidbrink To: freebsd-isdn@freebsd.org Subject: Firewall Problem with i4b 0.90.1 / FreeBSD 4.0 - Sample configuration? Message-ID: <20001215211303.C25371@nicky.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've got problems with getting my i4b working together with a firewall, dynamical IP addresses and NAT (Network Address Translation, "IP Masquerading"). If this sounds well-known to some of you: I asked for help about it half a year ago, but was not able to find a solution and gave up that time. Setup: - i4b 0.90.1, Teles S016.3 card - sppp via kernel ppp - Internet provider with dynamical IP addresses - The FreeBSD 4.0 "standard" firewall - FreeBSD natd - Firewall configuration "simple" from the default "/etc/rc.firewall" The problem seems to have to do with the combination of dynamical IP addresses and NAT. OK, probably it's not exactly i4b-specific, but I hope to find someone here who knows how to handle this problem or has a working sample configuration. When I start natd in verbose mode and start lynx (Ports 53 and 80 should be allowed), I get the following error message: -------- Out [UDP] [UDP] 0.0.0.0:1518 -> 195.88.140.15:53 aliased to [UDP] 0.0.0.0:1518 -> 195.88.140.15:53 natd: failed to write packet back: Permission denied ------- When I switch the firewall off leaving NAT running, everything seems to work like expected. Does someone of you have a similiar combination working and would send me a working example setup (rc.firewall, isdnd.rc and the sppp setup schript)? Ciao, Matthias -- Matthias Heidbrink E-Mail: Bundesratufer 12 Matthias_Heidbrink@b.maus.de 10555 Berlin, Germany mh@cs.tu-berlin.de Tel. +49-30-8536361 Mobil +49-179-3981150 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 12:16:26 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 12:16:18 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 7710437B402 for ; Fri, 15 Dec 2000 12:16:07 -0800 (PST) Received: (qmail 12752 invoked by uid 0); 15 Dec 2000 20:16:05 -0000 Received: from p3ee21663.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.99) by mail.gmx.net (mail07) with SMTP; 15 Dec 2000 20:16:05 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id UAA12123 for freebsd-isdn@freebsd.org; Fri, 15 Dec 2000 20:50:13 +0100 Date: Fri, 15 Dec 2000 20:50:13 +0100 From: Gerhard Sittig To: freebsd-isdn@freebsd.org Subject: Re: Urgent: Trouble installing AVM Fritz!Card PCI Message-ID: <20001215205013.M253@speedy.gsinet> Mail-Followup-To: freebsd-isdn@freebsd.org References: <20001214080014.EB6882B3@hcswork.hcs.de> <200012141624.RAA75300@rosa.physik.TU-Berlin.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200012141624.RAA75300@rosa.physik.TU-Berlin.DE>; from jan@physik.TU-Berlin.DE on Thu, Dec 14, 2000 at 05:24:55PM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 14, 2000 at 17:24 +0100, Jan Riedinger wrote: > > At last I looked at the BIOS configuration, because you wrote > about a the possibilty of a BIOS bug. Setting the option "PNP > OS system" to "No" solved the problem :-). This is strange, > because there are no ISA slots at the board (ASUS A7V). (OT) Watch your dmesg output closely (maybe even boot with "boot -v") and see how much of ISA stuff is still in these machines -- no matter how many visible ISA slots there are ... Almost all peripheral devices should be ISA: sio, ppc, atkbd, psm, sc (sort of), fdc, rtc, etc. AFAIK only ata and maybe onboard pcm (besides NICs and SCSI) made it to the PCI bus. And despite vga is attached to a separate AGP bus (connected to the PCI backbone(?) via another bridge) it still lurks out at the same location as the oldest VGA board did. I still have yet to see a legacy free PC. :) I guess it wouldn't be a PC any longer (no A20-gate, no WD lookalike interface to harddrives invented some sixteen years later, i.e. no Wintel hardware). :> virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 15 12:50:14 2000 From owner-freebsd-isdn@FreeBSD.ORG Fri Dec 15 12:50:12 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 09DD737B400 for ; Fri, 15 Dec 2000 12:50:11 -0800 (PST) Received: from bastion.localhost (p3E9E1515.dip.t-dialin.net [62.158.21.21]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id VAA18181; Fri, 15 Dec 2000 21:50:09 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBFKoTr73838; Fri, 15 Dec 2000 20:50:29 GMT Date: Fri, 15 Dec 2000 21:49:44 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <30110732334.20001215214944@x-itec.de> To: Matthias Heidbrink Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Firewall Problem with i4b 0.90.1 / FreeBSD 4.0 - Sample configuration? In-reply-To: <20001215211303.C25371@nicky.cs.tu-berlin.de> References: <20001215211303.C25371@nicky.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Matthias, Friday, December 15, 2000, 12:13:04 PM, you wrote: MH> Hi, MH> I've got problems with getting my i4b working together with a MH> firewall, dynamical MH> IP addresses and NAT (Network Address Translation, "IP MH> Masquerading"). MH> If this sounds well-known to some of you: I asked for help MH> about it half a year MH> ago, but was not able to find a solution and gave up that time. Maybe i can help you. MH> The problem seems to have to do with the combination of MH> dynamical IP addresses and NAT. MH> OK, probably it's not exactly i4b-specific, but I hope to find MH> someone here who knows how MH> to handle this problem or has a working sample configuration. MH> When I start natd in verbose mode and start lynx (Ports 53 and MH> 80 should be allowed), MH> I get the following error message: MH> -------- MH> Out [UDP] [UDP] 0.0.0.0:1518 -> 195.88.140.15:53 aliased to MH> [UDP] 0.0.0.0:1518 -> 195.88.140.15:53 MH> natd: failed to write packet back: Permission denied MH> ------- At first, what does "ipfw show" gives you for output if everything is enabled and if you get the permission denied? After clearing the rules, we go to step 2, and maybe we need to do a little tricky to reset the nat-daemon, but details later. -- Boris [MCSE, CNA] ................................................................... X-ITEC : Consulting * Programming * Net-Security * Crypto-Research ........: [PRIVATE ADDRESS:] : Boris Köster eMail koester@x-itec.de http://www.x-itec.de : Grüne 33-57368 Lennestadt Germany Tel: +49 (0)2721 989400 : 101 % PERFECTION - SECURITY - STABILITY - FUNCTIONALITY ........:.......................................................... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Dec 16 4:59: 8 2000 From owner-freebsd-isdn@FreeBSD.ORG Sat Dec 16 04:59:06 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (Postfix) with ESMTP id 734E137B400 for ; Sat, 16 Dec 2000 04:59:05 -0800 (PST) Received: from nicky.cs.tu-berlin.de (mh@nicky.cs.tu-berlin.de [130.149.17.43]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id NAA27433; Sat, 16 Dec 2000 13:53:53 +0100 (MET) Received: (from mh@localhost) by nicky.cs.tu-berlin.de (8.9.3/8.9.3) id NAA29943; Sat, 16 Dec 2000 13:53:50 +0100 (MET) Date: Sat, 16 Dec 2000 13:53:49 +0100 From: Matthias Heidbrink To: Boris , freebsd-isdn@freebsd.org Subject: Re: Firewall Problem with i4b 0.90.1 / FreeBSD 4.0 - Sample configuration? Message-ID: <20001216135348.A29752@nicky.cs.tu-berlin.de> References: <20001215211303.C25371@nicky.cs.tu-berlin.de> <31110682042.20001215214854@x-itec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <31110682042.20001215214854@x-itec.de>; from koester@x-itec.de on Fri, Dec 15, 2000 at 09:48:54PM -0800 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Boris, > MH> When I start natd in verbose mode and start lynx (Ports 53 and 80 should be allowed), > MH> I get the following error message: > > MH> -------- > MH> Out [UDP] [UDP] 0.0.0.0:1518 -> 195.88.140.15:53 aliased to > MH> [UDP] 0.0.0.0:1518 -> 195.88.140.15:53 > MH> natd: failed to write packet back: Permission denied > MH> ------- > > At first, what does "ipfw show" gives you for output if everything is > enabled and if you get the permission denied? ----------------------- 00100 13 778 divert 8668 ip from any to any via isp0 00100 60 4200 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 192.168.99.0/24 to any in recv isp0 00400 0 0 deny ip from 0.0.0.0/24 to any in recv rl0 00500 0 0 deny ip from 10.0.0.0/8 to any via isp0 00600 0 0 deny ip from any to 10.0.0.0/8 via isp0 00700 0 0 deny ip from 172.16.0.0/12 to any via isp0 00800 0 0 deny ip from any to 172.16.0.0/12 via isp0 00900 0 0 deny ip from 192.168.0.0/16 to any via isp0 01000 0 0 deny ip from any to 192.168.0.0/16 via isp0 01100 10 598 deny ip from 0.0.0.0/8 to any via isp0 01200 0 0 deny ip from any to 0.0.0.0/8 via isp0 01300 0 0 deny ip from 169.254.0.0/16 to any via isp0 01400 0 0 deny ip from any to 169.254.0.0/16 via isp0 01500 0 0 deny ip from 192.0.2.0/24 to any via isp0 01600 0 0 deny ip from any to 192.0.2.0/24 via isp0 01700 0 0 deny ip from 224.0.0.0/4 to any via isp0 01800 0 0 deny ip from any to 224.0.0.0/4 via isp0 01900 0 0 deny ip from 240.0.0.0/4 to any via isp0 02000 0 0 deny ip from any to 240.0.0.0/4 via isp0 02100 862 40133 allow tcp from any to any established 02200 0 0 allow ip from any to any frag 02300 0 0 allow tcp from any to 0.0.0.1 25 setup 02400 0 0 allow tcp from any to 0.0.0.1 53 setup 02500 0 0 allow udp from any to 0.0.0.1 53 02600 0 0 allow udp from 0.0.0.1 53 to any 02700 0 0 allow tcp from any to 0.0.0.1 80 setup 02800 0 0 deny log logamount 100 tcp from any to any in recv isp0 setup 02900 2 88 allow tcp from any to any setup 03000 0 0 allow udp from any 53 to 0.0.0.1 03100 0 0 allow udp from 0.0.0.1 to any 53 03200 0 0 allow udp from any 123 to 0.0.0.1 03300 0 0 allow udp from 0.0.0.1 to any 123 65535 0 0 allow ip from any to any ----------------------- > After clearing the rules, we go to step 2, and maybe we need to do a > little tricky to reset the nat-daemon, but details later. I'm curious what you'll find out. Ciao, Matthias -- Matthias Heidbrink E-Mail: Bundesratufer 12 Matthias_Heidbrink@b.maus.de 10555 Berlin, Germany mh@cs.tu-berlin.de Tel. +49-30-8536361 Mobil +49-179-3981150 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Dec 16 7:22:51 2000 From owner-freebsd-isdn@FreeBSD.ORG Sat Dec 16 07:22:45 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id B4FEC37B402 for ; Sat, 16 Dec 2000 07:22:44 -0800 (PST) Received: from bastion.localhost (p3E9E16A1.dip.t-dialin.net [62.158.22.161]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id QAA05418; Sat, 16 Dec 2000 16:22:40 +0100 (MET) Received: from masterpc (master [192.168.0.1]) by bastion.localhost (8.11.1/8.11.1) with ESMTP id eBGFN9r98930; Sat, 16 Dec 2000 15:23:09 GMT Date: Sat, 16 Dec 2000 16:22:15 -0800 From: Boris X-Mailer: The Bat! (v1.46d) Personal Reply-To: Boris X-Priority: 3 (Normal) Message-ID: <44177482936.20001216162215@x-itec.de> To: Matthias Heidbrink Cc: freebsd-isdn@FreeBSD.ORG Subject: Re[2]: Firewall Problem with i4b 0.90.1 / FreeBSD 4.0 - Sample configuration? In-reply-To: <20001216135348.A29752@nicky.cs.tu-berlin.de> References: <20001215211303.C25371@nicky.cs.tu-berlin.de> <31110682042.20001215214854@x-itec.de> <20001216135348.A29752@nicky.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Matthias, Saturday, December 16, 2000, 4:53:49 AM, you wrote: Ok, letīs take a look. The ruleset is not bad at all, but I think we should begin with a smaller ruleset first. After that, we will do some enchancements like "Ping protection" and "Traceroute protection", anti spoofing, and so on. There are some entries in your ruleset that may give you some trouble, so we create a basic ruleset first. After that, we will enhance it later if everything works on your machine. MH> I'm curious what you'll find out. Ok, letīs go on -) Maybe i will write a litte IPFW HOWTO for FreeBSD-OS soon, we well see (my personal howto, hosted on my domain, accessible for everyone). I will use this mail as a template for the howto. We are using our own script improving our firewall, we will begin with a litte one to see that everything is working. You should start the following script. If you are starting it remotely, it could be happen that you will be disconnected and you have to relogin (itīs the question how fast are the rules processed). filename: nat.bat ipfw -f flush ipfw add divert natd all from any to any via isp0 ipfw add pass all from any to any ipfw add pass all from any to any ipfw add pass tcp from any to any ipfw add pass udp from any to any ipfw show natd -interface isp0 --------------- The NAT script is fired up by the upcoming isdn script below. Itīs possible that the last line reports something like "natd is already using the address.." or similar. Ignore it. This is your new firewall-script, we will enhance it later. Normally, a server should be well protected first, before applying a firewall script. A ipfw ruleset is the top of the tree. Normally you have to go sure that no one can break into your network first, even without your ipfw script but this is another history -) Well, letīs go. Now, weaponed with our ipfw script we have maybe still the problem that we will get a permission denied if we want to use isdn. Our NAT Daemon is a little bit confused, so we have to do some nice trickys. Here we have a fast and dirty script to establish an ISDN connection. It resets some drivers and so on to be sure that everything works. We have some sleep commands to give enough time for the daemons to reset. The script will produce some "bla not found" or similar things, ignore them. This script can be used to reinitialise the isdn connection, too if neccessary. And remember. Ignore any strange messages, let the script running. ------------------------------------------------------------ filename: isdn.bat echo PID ISDND isp=`cat /var/run/isdnd.pid` echo $isp kill $isp sleep 5 echo Starte ISDN Daemon neu isdnd echo done. sleep 5 echo PID Nat.. pid=`cat /var/run/natd.pid` echo $pid echo Kill NAT kill $pid sleep 10 echo Checke NAT: pid=`cat /var/run/natd.pid` echo $pid sleep 2 echo -n 'Configuring ISPPP to T-Offline:' echo -n ' spppcontrol'; echo "ifconfig down" ifconfig isp0 delete -link1 down sleep 5 route flush sleep 5 echo "ispppcontrol settings..." ispppcontrol isp0 myauthproto=pap ispppcontrol isp0 myauthname="DEINE BENUTZERKENNUNG" ispppcontrol isp0 myauthsecret="DEIN PASSWORT" sleep 5 echo "ifconfig setup" ifconfig isp0 0.0.0.0 0.0.0.1 netmask 255.255.255.255 link1 debug sleep 5 echo -n ' up'; ifconfig isp0 route add 0.0.0.0 0.0.0.1 netstat -nra sleep 5 natd -interface isp0 ./nat.bat ----------------------------------------------------- Some very important entries of this script are - RESETTING THE NAT DAEMON - RESETTING THE ISDN DAEMON - DOING SOME TRICKY WITH ROUTING (route add 0.0.0.0 0.0.0.1) Now, if the isdn connection establishes, we could still have the problem (it is possible, but it must not be) of a "permission denied", because our nat daemon is still not awake. So, we will take a clother look at the isdnd.rc script and we will look at a script that resets the nat-daemon too. ------------------------------ filename: isdnd.rc located in /etc/isdn system ratesfile = /etc/isdn/isdnd.rates # name & location of rates file useacctfile = yes # generate accouting info to file acctall = on # generate info for everything acctfile = /var/log/isdnd.acct # name & location of accounting file rtprio = 25 # modify isdnd's priority regexpr = "call active" # look for matches in log messages regprog = hup_natd # execute program whan match is found entry name = T-Offline usrdevicename = isp usrdeviceunit = 0 isdncontroller = 0 isdnchannel = -1 local-phone-incoming = * remote-phone-incoming = * local-phone-dialout = 4711 (put your phone-number here!completely!) remote-phone-dialout = 0191011 remdial-handling = first dialin-reaction = ignore dialout-type = normal b1protocol = hdlc idletime-incoming = 240 idletime-outgoing = 360 ratetype = 0 unitlength = 90 unitlengthsrc = aocd dialretries = -1 dialrandincr = on recoverytime = 2 usedown = off downtries = 2 downtime = 30 ---------------------------------------------- This is a working script for t-online. Now, we will take a clother look to our nat-reset-script, named "hup_natd", located in /etc/isdn/ (we will create it now). I donīt know if the script above works with your i4b version, try it out. If not, run the hup_natd script manually after establishing an ISDN connection. --------------------------------------- filename: hup_natd located in /etc/isdn #!/bin/sh pid=`cat /var/run/natd.pid` echo Prozess-ID fuer NAT-D: $pid kill -HUP $pid sleep 3 kill -HUP $pid sleep 5 kill -HUP $pid sleep 30 kill -HUP $pid sleep 60 kill -HUP $pid --------------------------- Now, a very interesting question is, why to use these sleeps and why we are doing this several times. If we are sending the HUP signal to the NAT daemon, it needs some time to process. Sometimes, the daemon is still not working, and we have to use fire up the HUP signal again. This will be done in the background if the isdn connection establishes. Now, we have a complete set of scripts to get up and running isdn with NAT. If it works, we will go a step clother to setup your ruleset. -- Boris [MCSE, CNA] ................................................................... X-ITEC : Consulting * Programming * Net-Security * Crypto-Research ........: [PRIVATE ADDRESS:] : Boris Köster eMail koester@x-itec.de http://www.x-itec.de : Grüne 33-57368 Lennestadt Germany Tel: +49 (0)2721 989400 : 101 % PERFECTION - SECURITY - STABILITY - FUNCTIONALITY ........:.......................................................... Everything I am writing is (c) by Boris Köster and may not be rewritten or distributed in any way without my permission. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Dec 16 7:37:55 2000 From owner-freebsd-isdn@FreeBSD.ORG Sat Dec 16 07:37:52 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from server01.bundy.co.uk (user-141-108.jakinternet.co.uk [212.187.141.108]) by hub.freebsd.org (Postfix) with ESMTP id D449E37B400 for ; Sat, 16 Dec 2000 07:37:46 -0800 (PST) Received: from chris.bundy.co.uk (chris.bundy.co.uk [10.10.10.12]) by server01.bundy.co.uk (8.11.1/8.9.3) with SMTP id eBGFaVj06388 for ; Sat, 16 Dec 2000 15:36:32 GMT (envelope-from Chrisbundy@beeb.net) From: CHRISTOPHER BUNDY To: freebsd-isdn@freebsd.org Subject: Make Error i4b .help sought Date: Sat, 16 Dec 2000 15:37:20 +0000 Reply-To: Chris@bundy.co.uk Message-ID: <8k2n3togj7uurf8fqtlf2ca51hbu5hbbcv@4ax.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I get a the following errors when compiling a new kernel which has been upgraded for an ISDN card and the latest i4b 0.96=20 linking kernel i4b_ctl.o: In function `i4bctlioctl': i4b_ctl.o(.text+0x1b2): undefined reference to `l1_sc' i4b_ctl.o(.text+0x232): undefined reference to `l1_sc' i4b_isppp.o: In function `i4bispppattach': i4b_isppp.o(.text+0x171): undefined reference to `sppp_attach' i4b_isppp.o: In function `i4bisppp_ioctl': i4b_isppp.o(.text+0x1bb): undefined reference to `sppp_ioctl' i4b_isppp.o: In function `i4bisppp_start': i4b_isppp.o(.text+0x1df): undefined reference to `sppp_isempty' i4b_isppp.o(.text+0x2c6): undefined reference to `sppp_dequeue' i4b_isppp.o: In function `i4bisppp_dialresponse': i4b_isppp.o(.text+0x64f): undefined reference to `sppp_isempty' i4b_isppp.o(.text+0x667): undefined reference to `sppp_dequeue' i4b_isppp.o: In function `i4bisppp_rx_data_rdy': i4b_isppp.o(.text+0x6ef): undefined reference to `sppp_input' i4b_l4if.o: In function `i4b_mdl_status_ind': i4b_l4if.o(.text+0xb3): undefined reference to `isic_settrace' i4b_l4if.o(.text+0xbd): undefined reference to `isic_gettrace' i4b_l4.o: In function `i4b_get_idletime': i4b_l4.o(.text+0x8d4): undefined reference to `i4bisppp_idletime' *** Error code 1 config and make depend went without a hitch. I have release 4.2 stable and a winbond card.. I added the following lines to my config file=20 device iwic0 pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 4 pseudo-device "i4bctl" pseudo-device "i4brbch" 4 pseudo-device "i4btel" 4 pseudo-device "i4bipr" 4 pseudo-device "i4bisppp" 4 options IPR_VJ options IPR_LOG=3D25 Any help would be much appreciated. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Dec 16 14:17:24 2000 From owner-freebsd-isdn@FreeBSD.ORG Sat Dec 16 14:17:23 2000 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 6EB5A37B402 for ; Sat, 16 Dec 2000 14:17:22 -0800 (PST) Received: from fwd07.sul.t-online.com by mailout00.sul.t-online.com with smtp id 147Pdp-0007ds-04; Sat, 16 Dec 2000 23:17:21 +0100 Received: from xenium (520049982112-0001@[62.225.241.53]) by fwd07.sul.t-online.com with smtp id 147Pde-212qtUC; Sat, 16 Dec 2000 23:17:10 +0100 Message-ID: <002f01c067ad$bd95fb20$6300a8c0@xenium> From: Simon.Putz@t-online.de (Simon Putz) To: Subject: how to get the isdn to work Date: Sat, 16 Dec 2000 23:15:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Sender: 520049982112-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, i got my system to work now, but i cant connect to the internet.i followed the instructions on http://www.freebsd-support.de/i4b/ but this is not working, the shell script gives me an error (SIO... file exists). when i do isdnd -f and then ping the ip , i see it connecting to my isp (t-online flat) for like 1 second and then instantly hanging up. thats in advance for any help. simon putz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message