From owner-freebsd-questions Fri Feb 5 18:19:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11460 for freebsd-questions-outgoing; Fri, 5 Feb 1999 18:19:04 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11453 for ; Fri, 5 Feb 1999 18:19:02 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (Tambler.infowest.com [207.49.57.143]) by infowest.com (8.8.8/8.8.8) with ESMTP id TAA10380 for ; Fri, 5 Feb 1999 19:19:00 -0700 (MST) Message-ID: <36BBA66F.698F574E@infowest.com> Date: Fri, 05 Feb 1999 19:18:23 -0700 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: questions@FreeBSD.ORG Subject: Obnoxious ethernet and other curious wonders of the world Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Here's a puzzler: My 3.0-STABLE kernel as of 3 Feb. 1999 works wonderfully and the fxp0 ethernet driver for the on-the-motherboard Intel EtherExpress 10/100 works well. Advance 2 days. I add a SoundBlaster card to the box and recompile the kernel to support the voxware stuff (using the SAME sources the other kernel was compiled from, the 3 Feb. 1999 STABLE sources), reboot, and... fxp0: device timeout Error City, Arizona! The device refuses to work. The link light (green LED) on the motherboard still glows a friendly green, as does the green LED link light on the 10baseT hub on my desk. The 'net cable is a known good working cable. Nevertheless, I try swapping cables, wiggling cables, powering down the hub, switching hub ports, etc. to of no avail. I reboot several times as well. Nothing. No network. So, I reboot and use my 3 Feb. kernel again without the sound support. Network works wonderfully again. Here's the ONLY differences between the two kernel configs: The ONLY difference between the two kernels is that the newer (and unnetworkable) kernel adds the following to the config: controller pnp0 controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device awe0 at isa? port 0x620 Also, during boot, I added the /kernel.config PNP stuff so that the AWE64 wavetable MIDI would work (and with the new non-working-network kernel, all the AWE devices are detected wonderfully). Any ideas? Are you as puzzled as I am? Thanks in advance for any/all commentary. Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message