From owner-freebsd-questions@FreeBSD.ORG Sat Oct 13 09:08:04 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92EDC16A418 for ; Sat, 13 Oct 2007 09:08:04 +0000 (UTC) (envelope-from thomas@gielfeldt.com) Received: from pasmtpA.tele.dk (pasmtpa.tele.dk [80.160.77.114]) by mx1.freebsd.org (Postfix) with ESMTP id 3DC4A13C447 for ; Sat, 13 Oct 2007 09:08:04 +0000 (UTC) (envelope-from thomas@gielfeldt.com) Received: from p44902jr (0x57383a5a.slnqu1.broadband.tele.dk [87.56.58.90]) by pasmtpA.tele.dk (Postfix) with SMTP id 1DE14800AF7 for ; Sat, 13 Oct 2007 10:42:22 +0200 (CEST) Message-ID: <001401c80d74$f9c3df30$0111a8c0@berlingske.dk> From: "Thomas Gielfeldt" To: Date: Sat, 13 Oct 2007 10:42:23 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD locks up on J7F4 motherboard X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2007 09:08:04 -0000 Hi Has anyone any experience with the Jetway Motherboards and FreeBSD? My motherboard is a Jetway 7F4K1G2E-PB has dual gigabit lan (realtek) = detected as re0 and re1. I'm trying to install FreeBSD 6.2 Release, but = as soon as it tries to dhcp on re1, it freezes. I have to power off and = on. I've also tried booting an already installed FreeBSD 6.2 stable, but = this also resulted in a freeze when re1 comes up. It just freezes, no = messages or anything.=20 Somewhere on the net, I saw someone who said that it only happens after = a cold-reset. I've been part able to confirm this, but even after = getting freebsd up and running with both nics up, after a while it just = locks up. I've tried changed from auto-sense to e.g. base1000tx full-duplex, but = that did not resolve the issue either. I'm not entirely sure that the = problem are the nics, but it seems to point in that direction. Windows XP runs fine, so it shouldn't be a hardware error. However = running XP is not the solution to my problems :-) Does anyone know this problem, or perhaps (even better) a solution to = it? Thanks. Br, Thomas