From owner-freebsd-current Sun Oct 3 4:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mechv.me.tuns.ca (mechv.me.TUNS.Ca [134.190.50.152]) by hub.freebsd.org (Postfix) with ESMTP id 60CD514C0A for ; Sun, 3 Oct 1999 04:10:03 -0700 (PDT) (envelope-from bbursey@mechv.me.tuns.ca) Received: from localhost (bbursey@localhost) by mechv.me.tuns.ca (8.8.8/8.8.5) with SMTP id IAA21931 for ; Sun, 3 Oct 1999 08:09:49 -0300 (ADT) Date: Sun, 3 Oct 1999 08:09:49 -0300 (ADT) From: Bryan Bursey To: current@FreeBSD.ORG Subject: Issues with xl0 In-Reply-To: <37F6EC46.5C7E4EA4@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I attempted to move from -STABLE to -CURRENT last night, but without any luck. I decided to start with a current snapshot (19990928), but was unable to install using the floppies provided on releng3.freebsd.org. Thinking it might have been a floppy issue, I used my 3.3-STABLE floppies and simply changed the install options so that I'd get 4.0. This worked until I restarted my machine at the end of the install. It came back up ok, but I was again unable to connect to the network. Can anyone tell me if there are known issues with the xl0 driver in 4.0, or if it has been superceded by another driver which works with 3Com 3C900B. Thanks for any help (or other random thoughts). Cheers, Bryan ________________________________ Bryan Bursey, DEng Dept. of Mechanical Engineering DalTech (TUNS) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message