Date: Mon, 21 Jul 2003 21:28:46 +0200 From: Bernd Walter <ticso@cicely8.cicely.de> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: freebsd-alpha@freebsd.org Subject: Re: panic: cpu_initclocks: no clock attached Message-ID: <20030721192845.GI32645@cicely8.cicely.de> In-Reply-To: <20030721191517.GD599@dhcp01.pn.xcllnt.net> References: <20030721180848.GC32645@cicely8.cicely.de> <20030721183151.GB599@dhcp01.pn.xcllnt.net> <20030721184812.GG32645@cicely8.cicely.de> <20030721191517.GD599@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 21, 2003 at 12:15:17PM -0700, Marcel Moolenaar wrote: > On Mon, Jul 21, 2003 at 08:48:12PM +0200, Bernd Walter wrote: > > > > The reason is that eisa bridge support now depends on having eisa > > compiled in. We'd never done this on alpha. > > eisa support needs to be legalized for alpha and added to GENERIC. > > I will commit this in a few minutes because my system now boots fine. > > > > Well theoreticaly - because vinum is broken too :( > > Arglll... > > That's no all: > > Kernels built after the dc(4) newbusification and gcc33 import > fail to work due to NFS hangs (the process blocks on 'nfsfsy'). > The dc(4) driver functions, because when NFS hangs I still have > a functional network. But other than that my Alpha is mostly > useless because I use NFS a lot... I will see - the system is a NFS client too, but it run with a fxp based card. But it's not updated to the latest version - the checkout happend on 17th. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030721192845.GI32645>