Re: Boot from CD is a no-go
Steve Dunham wrote:
[snip death on loading the initrd from CD)
> Should be fine if it loaded the kernel without problem. (It hasn't
> actually started the kernel, has it?)
This is what I get:
1. Welcome message and boot prompt
2. Loading kernel... [spinning cursor]
3. Loading initial RAM disk... [spinning cursor]
4. Data Access Exception
5. OK prompt
So, I dunno. The only thing that would seem to make sense would be if my
memory was bad (it checks out fine with the PROM's diagnostic tool), or
if the kernel for some reason hates some part of my hardware. But I
can't think of a way to figure out what piece of my hardware might be
hate-able, besides using the PROM's diagnostics. Everything checks out
fine there (SCSI bus, memory).
Red Hat Linux 5.2/Sparc's HCL lists the ELC as 'Tier 2' supported. I
don't see a reason for Debian to be any different; my thinking was,
'Okay, the ELC is supported by Sparc Linux; Debian is just one
distribution'. I guess I could try Red Hat, but I don't really feel like
spending $50 or trying to do an fTP install.
> I'm not sure what is going wrong here. I'd recommend trying both the
> linux and linux-2.2.1 kernels.
Yes. I tried both, and got the same thing both times.
> If all else fails you could try booting from the network and then use the
> CD.
But it would still need to load the RAM disk image from the CD-ROM, and
that's what fails. Ultimately, this will be a net-booting machine that
gets its / filesystem via NFS from my Linux/x86 system, but I need a way
to get the distribution off the CD.
Since the initial plan (boot from CD and install to an external HDD,
serve the external HDD from the x86) seems doomed, I wonder if I can
just extract the files I need by hand from the x86 to another disk on
the x86? Has anyone done this before? The readmes on the CD didn't have
anything to say about this.
Thanks again,
-- Chris :)
_____________________________________________________________________________
Christopher Reid Palmer : reid@pconline.com : http://innerfire.visi.com/
Reply to: