Date: Mon, 26 Jul 2004 10:10:53 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Wilko Bulte <wb@freebie.xs4all.nl> Cc: Will Andrews <will@csociety.org> Subject: Re: Announcing snapshots.se.freebsd.org - now with AMD64 snapshots Message-ID: <84928.1090829453@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 25 Jul 2004 23:40:04 %2B0200." <20040725214004.GA63752@freebie.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20040725214004.GA63752@freebie.xs4all.nl>, Wilko Bulte writes: >On Sun, Jul 25, 2004 at 11:33:37PM +0200, Poul-Henning Kamp wrote: >> In message <20040725053409.GY2959@sirius.firepipe.net>, Will Andrews writes: >> >> >The site also builds i386 and alpha snapshots every day. >> >Although I admit I haven't been able to figure out what's wrong >> >with the alpha snaps (they haven't worked since March)... >> >> I tried to get my alpha live so I could test tty patches on it >> but gave up. 5.2.1-R gave the same error as a snapshot from >> .jp and it looks to me like the machine doesn't even want to >> recognize the CD as bootable. > >There is some outstanding issue with the loader on alpha (toolchain >related as I understand it) but that should not keep it from getting >to the 1st stage boot. Actually I remembered wrong. The jp snapshot gave this: block 0 of dka100.1.0.2000.0 is not a valid boot block Whereas 5.2.1 gave this: cia0: extended capabilities: 21<DWEN,BWEN> pcib0: <2117x PCI host bus adapter> on cia0 pci0: <PCI bus> on pcib0 eisab0: <PCI-EISA bridge> at device 7.0 on pci0 halted CPU 0 halt code = 7 machine check while in PAL mode PC = 18100 >>> -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84928.1090829453>