Thanks everyone for your help so far. I did have to burn a new CDROM (the
one from the 5.8 set was designed to boot on i386 and not Alpha). Once I did that, I was able to bring up the system (my dmesg is below). Some questions: 1. I'm assuming the "preposterous clock chip time" can be managed in the SRM console so I'll exercise my Google-fu to figure that out. 2. Is the "nvram corrupt" something I need to be concerned about? If so, what should I do here? Is that a hardware issue or can I re-initialize it somehow? 3. Anything I should be concerned about with the "stray irq 3" message? Thanks again! >>>show device dka400.4.0.9.0 DKA400 RRD46 0557 dva0.0.0.0.1 DVA0 ewa0.0.0.6.0 EWA0 00-00-F8-24-E5-03 pka0.7.0.9.0 PKA0 SCSI Bus ID 7 5.57 >>>boot dka4 (boot dka400.4.0.9.0 -flags a) block 0 of dka400.4.0.9.0 is a valid boot block reading 15 blocks from dka400.4.0.9.0 bootstrap code read in base = 156000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 148000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OpenBSD/Alpha Primary Boot OpenBSD/alpha boot 1.10 VMS PAL rev: 0x1000000010114 OSF PAL rev: 0x1000000020116 Switch to OSF PAL code succeeded. cannot open /etc/random.seed: No such file or directory Loading bsd... 7199024+529528=0x75f0f8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2015 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.8 (RAMDISKBIG) #134: Sun Aug 16 07:07:51 MDT 2015 [hidden email]:/usr/src/sys/arch/alpha/compile/RAMDISKBIG Digital AlphaStation 500/400, 400MHz 8192 byte page size, 1 processor. real mem = 67108864 (64MB) rsvd mem = 2359296 (2MB) avail mem = 56008704 (53MB) mainbus0 at root cpu0 at mainbus0: ID 0 (primary), 21164A-0 (unknown minor type 0) cpu0: architecture extensions: 1<BWX> cia0 at mainbus0: DECchip 2117x Core Logic Chipset (ALCOR/ALCOR2), pass 3 cia0: extended capabilities: 21<DWEN,BWEN> cia0: using BWX for PCI config and bus access pci0 at cia0 bus 0 de0 at pci0 dev 6 function 0 "DEC 21040" rev 0x26, DEC 21040 pass 2.6: kn20aa ir q 13, address 00:00:f8:24:e5:03 qlw0 at pci0 dev 9 function 0 "QLogic ISP1020" rev 0x02: kn20aa irq 12 qlw0: nvram corrupt qlw0: firmware rev 4.66.0, attrs 0x0 scsibus0 at qlw0: 16 targets, initiator 7 cd0 at scsibus0 targ 4 lun 0: <DEC, RRD46 (C) DEC, 0557> SCSI2 5/cdrom removable pceb0 at pci0 dev 10 function 0 "Intel 82375EB EISA" rev 0x15 eisa0 at pceb0: DEC5100, 4 slots isa0 at pceb0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 irq 1 irq 12 mcclock0 at isa0 port 0x70/2: mc146818 or compatible stray isa irq 3 softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: preposterous clock chip time -- CHECK AND RESET THE DATE! erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/alpha 5.8 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s # Thanks, Bryan |
> Some questions:
> > 1. I'm assuming the "preposterous clock chip time" can be managed in the > SRM console so I'll exercise my Google-fu to figure that out. It should be nothing to worry about. The installer has noticed that the clock is in the future, compared to its internal filesystem timestamp, which is to be expected since the installation media were built some time ago. > 2. Is the "nvram corrupt" something I need to be concerned about? If so, > what should I do here? Is that a hardware issue or can I re-initialize it > somehow? This is harmless. The NVRAM storing configuration information for the QLogic SCSI controller is optional. The driver only notices by reading data with an incorrect checksum, and mentions it. > 3. Anything I should be concerned about with the "stray irq 3" message? No. Most alpha systems cause a couple stray interrupts for the serial ports while booting multiuser, and none afterwards. |
Thank you for the response! I have some additional RAM coming for
this box and a PCI video card. Can anyone recommend any missing ports for this architecture that are particularly annoying? I'd be happy to dig into some of them now and see what I can make happen. Thanks, Bryan On Nov 7, 2015, at 6:36 AM, Miod Vallat <[hidden email]> wrote: >> Some questions: >> >> 1. I'm assuming the "preposterous clock chip time" can be managed in the >> SRM console so I'll exercise my Google-fu to figure that out. > > It should be nothing to worry about. The installer has noticed that the > clock is in the future, compared to its internal filesystem timestamp, > which is to be expected since the installation media were built some > time ago. > >> 2. Is the "nvram corrupt" something I need to be concerned about? If so, >> what should I do here? Is that a hardware issue or can I re-initialize it >> somehow? > > This is harmless. The NVRAM storing configuration information for the > QLogic SCSI controller is optional. The driver only notices by reading > data with an incorrect checksum, and mentions it. > >> 3. Anything I should be concerned about with the "stray irq 3" message? > > No. Most alpha systems cause a couple stray interrupts for the serial > ports while booting multiuser, and none afterwards. |
On 2015-11-07, Bryan Everly <[hidden email]> wrote:
> Can anyone recommend any missing ports for this architecture that are > particularly annoying? I'd be happy to dig into some of them now and > see what I can make happen. lang/gcc/4.9 Also see the failure logs from landry@'s bulk builds: http://build-failures.rhaalovely.net/alpha/ (Note that "Error: job failed 256" doesn't indicate a problem with the port itself but with the build infrastructure: one of the hosts crashed, etc.) -- Christian "naddy" Weisgerber [hidden email] |
Free forum by Nabble | Edit this page |