From owner-freebsd-questions Wed Apr 7 16:37:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from couscous.fortdearborn.com (couscous.fortdearborn.com [204.137.253.195]) by hub.freebsd.org (Postfix) with ESMTP id 46929158DC for ; Wed, 7 Apr 1999 16:37:05 -0700 (PDT) (envelope-from font@couscous.fortdearborn.com) Received: from localhost (font@localhost) by couscous.fortdearborn.com (8.8.8/8.8.8) with SMTP id SAA04528 for ; Wed, 7 Apr 1999 18:32:58 -0500 (CDT) (envelope-from font@couscous.fortdearborn.com) Date: Wed, 7 Apr 1999 18:32:57 -0500 (CDT) From: Font To: freebsd-questions@freebsd.org Subject: Freeze on fxp0 ifconfig (3.1-RELEASE) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've freshly-installed 3.1-RELEASE and have started to set up networking. During the boot process, the ifconfig for fxp0 (the only NIC in the machine) freezes. This same computer also boots 2.2.8-RELEASE without difficulty. There are no IRQ conflicts. Were there significant changes in the fxp driver from 2.2.8-R to 3.1-R? Are there any special flags I need to include in order to get the fxp driver to bring the interface up? This is from my 2.2.8 messages file: Apr 7 17:50:06 kibbeh /kernel: fxp0 rev 2 int a irq 10 on pci0:3:0 This is what 3.1 says on the screen when it detects fxp0: fxp0: rev 2 int a irq 10 on pci0:3:0 fxp0: Ethernet address 00:60:94:b9:99:8e So, they're basically seeing the same thing. I can duplicate the freeze by booting in single-user and issuing the "ifconfig fxp0 192.168.1.151 netmask 255.255.255.0" myself. The only other difference between the configurations is that the 3.1 system recognizes my Adaptec 7895 dual-channel SCSI, while the 2.2.8 mentions it but doesn't use it. I also use "set root_disk_unit=0" since I also have an IDE drive (thanks Greg Lewis for that suggestion!). Would it be unreasonable to snatch the 2.2.8 pci/if_fxp*.[ch] files and try to use them? Is there any way I can help to figure out what the real problem is? dw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message