Menu

#4 jumpstart boot fails on pc164

rel-1.0
open
nobody
aboot (1)
5
2001-08-17
2001-08-17
No

after trying to boot jumpstart on my pc164 i get an
error
the message is:
>>> boot dka400 -fl 0
(boot dka400.4.0.7.0 -flags 0)
block 0 of boot dka400.4.0.7.0 is a
valid boot block
reading 165 blocks from dka400.4.0.7.0
bootstrap code read in
base = 180000, image_start = 0,
image_bytes = 14a00
initializing HWRPB at 2000
initializing page table at 172000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
aboot: Linux/Alpha SRM bootloader
version 0.7

halted CPU 0

halt code = 2
kernel stack not valid halt
PC = 0
>>>

is this a problem of my machine (until
now it was runing NT
and was working fine - now i wanted to
install linux) or is
this a problem of aboot (jumpstart) ?

the configuration is:
System: Digital Alpha PC164 500 MHz
Console V5.5-1
L3-Cache: 1 MB
Memory: 256 MB
VGA-Card: Diamond Fire GL 1000

Discussion

  • HP Admin User

    HP Admin User - 2001-08-17

    Logged In: YES
    user_id=294675

    I tried this on a PC-164 LX, with SRM Console V5.7-1, and it
    worked fine for me. I'll see if I can find information about
    getting
    a newer version of the firmware and get back to you.

    -Mike Lease
    Alpha Solutions and Engineering Group
    mike.lease@compaq.com

     
  • HP Admin User

    HP Admin User - 2001-08-17

    Logged In: YES
    user_id=294675

    I've used to the firmware from

    ftp://ftp.digital.com/pub/DEC/Alpha/firmware/readmes/v5.8/alphapc164/
    which seems to be a v5.5 and not v5.8 - is there a newer
    version
    out there for the pc164?

    i also think it's a problem with aboot starting the kernel,
    cause i wasn't
    able to boot the redhat installation cd either and got the
    same kernel
    stack not valid halt - by the way what does this message
    tell me?
    is there a memory problem or why is it not valid?

     
  • HP Admin User

    HP Admin User - 2001-08-17

    Logged In: YES
    user_id=294675

    Have you tried upgrading your console firmware to the most
    recent version?
    This sounds like an aboot problem to me... have you been
    able to boot any other CDs that have aboot on them, such as
    the Red Hat installation CD?

     

Log in to post a comment.

MongoDB Logo MongoDB