Date: Tue, 13 Nov 2001 09:57:24 +0000 From: Mark Blackman <mark.blackman@netscalibur.co.uk> To: freebsd-hardware@freebsd.org Subject: Re: FreeBSD won't reboot this motherboard. Message-ID: <20011113095724.A86199@admin4.dircon.net> In-Reply-To: <200111081304.NAA77699@mailhost2.dircon.co.uk>; from mark.blackman@netscalibur.co.uk on Thu, Nov 08, 2001 at 01:04:44PM %2B0000 References: <200111081304.NAA77699@mailhost2.dircon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
As a final note for the archives, this problem is resolved with the help of the motherboard vendor. A new BIOS must be flashed on to the board. the ID is 6VTXDR-C.F3A, where the F3A refers to the BIOS version number. This BIOS is not currently being distributed on the website, but available through Gigabyte technical support. - Mark On Thu, Nov 08, 2001 at 01:04:44PM +0000, Mark Blackman wrote: > I've got a GA-6VTXDR-C motherboard with 1GHz pentium and > 1Gig of RAM. > > (http://networking.gigabyte.com.tw/Products/Products_ServerBoard_Spec.asp?ProductID=20) > > This uses the Via Apollo Pro Family AGP Set > (North Bridge VT82C694T, South Bridge VT82C686B) > > I've been attempting to reboot this machine via the "/sbin/reboot" > executable. In all the cases I've tried, the full shutdown messages > occur, followed by the "Rebooting" output. After putting this line > to the screen, the machine fails to do anything (for 30 seconds and > more). Reboot is then achieved only with a hard reset or power cycle. > > I've tried CURRENT (cvsup today) and STABLE (cvsup yesterday) and > they both have this behaviour. > > 4.4-STABLE-yesterday > (GENERIC without BROKEN_KEYBOARD_RESET) - hangs after "Rebooting" > > 4.4-STABLE-yesterday > (GENERICE with BROKEN_KEYBOARD_RESET) - hangs after "Rebooting" > > 5.0-CURRENT-today > (without BROKEN_KEYBOARD_RESET) - hangs after "Rebooting" > > 5.0-CURRENT-today > (with BROKEN_KEYBOARD_RESET) - drops into debugger with > double panic after ~5 sec. > > FWIW, Redhat 7.2 does reboot the machine. My reading of the Linux > kernel code suggests that Linux puts the machine into 8086 emulation > mode (real mode) and then calls the BIOS reboot. > > I have 3 identical spec. machines which all exhibit this behaviour. > > Can anyone suggest any other options for forcing a reboot and what > does this imply about the way this hardware works? > > - Mark > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011113095724.A86199>