From owner-freebsd-newbies Tue Feb 19 16:24:56 2002 Delivered-To: freebsd-newbies@freebsd.org Received: from vwnode4.bs.wa.gov.au (vwnode4.bs.wa.gov.au [167.30.10.84]) by hub.freebsd.org (Postfix) with ESMTP id 8DAD437B416 for ; Tue, 19 Feb 2002 16:24:50 -0800 (PST) Received: from vwnode4.bs.wa.gov.au (localhost [127.0.0.1]) by vwnode4.bs.wa.gov.au (8.10.2+Sun/8.10.2) with ESMTP id g1K0Omo00107 for ; Wed, 20 Feb 2002 08:24:48 +0800 (WST) Received: from mail.sbdc.com.au (mail.sbdc.com.au [167.30.37.235]) by vwnode4.bs.wa.gov.au (8.10.2+Sun/8.10.2) with ESMTP id g1K0Okn00103 for ; Wed, 20 Feb 2002 08:24:47 +0800 (WST) Received: from inet_dom-MTA by mail.sbdc.com.au with Novell_GroupWise; Wed, 20 Feb 2002 08:25:00 +0800 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.1 Date: Wed, 20 Feb 2002 08:24:40 +0800 From: "Aaron deRozario" To: Subject: Post-install networking problem Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org have recently completed my first installation of freeBSD using version 4.4. Unfortunately during the installation phase I did not pay enough attention to the kernel configuration and that has left me with a driver/IRQ conflict between my NE2000(Realtek 8029) ISA NIC driver and the COM2 serial port driver. The result of this is that I am unable to use the NIC. I have entered boot -c at the prompt and entered the visual mode to configure the kernel. I am able to disable the driver for the COM2 port, which I don't use, setup the correct IRQ etc for the NIC save and exit. This gives me access to the NIC and I can configure the ed0 device fine. The problem is on reboot the kernel reverts to the first configuration - resulting in no networking. No doubt there is a way to fix this (I thought the save & exit option would sort this out but it doesn't) but I'm not sure how to do this. Do I need to - a) reinstall - least favoured option b) recompile the kernel - certainly doable, but not favoured or c) is there a config file/command that will enable my hardware/kernel driver settings to be kept over a reboot. In the archives I have come across a similar problem - alas the thread seemed to end before an answer came forward. If anyone can be of assistance in this matter it would be much appreciated. Aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message