Date: Thu, 17 Jun 2004 12:51:14 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Stephen Jones <smj@cirr.com> Cc: freebsd-alpha@freebsd.org Subject: Re: netbooting an install kernel Message-ID: <20040617105113.GZ68640@cicely12.cicely.de> In-Reply-To: <C5F174A5-C02B-11D8-958B-000393DAF5EC@cirr.com> References: <200406151857.i5FIv5Wu028133@egsner.cirr.com> <20040616074051.GJ32239@interwoven.com> <C5F174A5-C02B-11D8-958B-000393DAF5EC@cirr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 16, 2004 at 11:58:44PM -0700, Stephen Jones wrote: > On Jun 16, 2004, at 12:40 AM, Andrew Elmore wrote: > sym2: <895> port 0x10000-0x100ff mem > 0x1211000-0x1211fff,0x1212000-0x12120ff irq > 36 at device 4.0 on pci1 > sym2: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking > sym2: interrupting at TSUNAMI irq 36 > panic: cpu_initclocks: no clock attached So we have no device.hints in place. Do we already have a way for loading hints in case of netbooting? Otherwise the netbooting kernel needs hardcoded hints. AFAIK my last netbooting alpha was still 4.x so I never run into that problem myself. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040617105113.GZ68640>