boot floppy for Umax C600
Adam Russell
Adam Russell wrote:
> Ok, I've tried many boot images (including the most recent ones with
> 1.4.3_ALPHA and the 1.5 snapshot)as well as various bootvar settings and
> nothing seems to get the machine to boot off the floppy.
> I'm using bootvar 1.3 with boot-device fd:0
> boot-comman boot
> and load-base 100000
> all the rest are the default values. I need to set up a serial console
> in order to view OF output which I have not done. The only indication I
> get that the machine is doing anything is that I hear the disk being
> read for awhile and then, I hesitate to even mention this, a slight
> "clicking" sound. Then nothing.
> I have also noticed that the machine reboots itself before starting to
I think I should clarify this. I, of course, reboot the machine to reboot
off of the floppy. As it is starting up after this it reboots itself a
second time.
>
> read the floppy. I'm not sure if this is normal or not.
> Does anyone have any advice?
> Many Thanks,
> Adam Russell
Adam Russell
1.4.3_ALPHA and the 1.5 snapshot)as well as various bootvar settings and
nothing seems to get the machine to boot off the floppy.
I'm using bootvar 1.3 with boot-device fd:0
boot-comman boot
and load-base 100000
all the rest are the default values. I need to set up a serial console
in order to view OF output which I have not done. The only indication I
get that the machine is doing anything is that I hear the disk being
read for awhile and then, I hesitate to even mention this, a slight
"clicking" sound. Then nothing.
I have also noticed that the machine reboots itself before starting to
Matthew Reilly
> I think I should clarify this. I, of course, reboot the machine to reboot
> off of the floppy. As it is starting up after this it reboots itself a
> second time.
When you boot the boot-floppy after being in the Mac OS it sort of boots
again and says "Resetting to change configuration" or something similar and
then starts booting the floppy.
You should hear some clicking from the drive for a good while, it takes a
while to boot.
You could give System Disk a try, it should enable the Screen output device.
It worked on my C600 & my C500 even though it says my machine is not
supported and System disk will not work.
cheers,
Matthew
Adam Russell
> OF ,however I get CLAIM FAILED on all my attempts to boot the floppy. I see
> the FAQ says that this is unsovable and to set up a serial console,
> however, without a serial cable I can't do that(Oh, my kingdom for a serial
> cable!!). So at this point I'm hoping for one of two things to be true.
> One, that the FAQ is wrong and there *is* a way around the CLAIM FAILED
> error ,or , two that I can boot the installer another way, perhaps from my
> Mac68k NetBSD box. Is that possbile?
Other than that I guess I'll just wait until I get a chance to run to the
store and pick up a serial cable.
Many Thanks,
Adam Russell
Adam Russell
apologies if this is redundant.
Bill Studenmund
> Ok, I've tried many boot images (including the most recent ones with
> 1.4.3_ALPHA and the 1.5 snapshot)as well as various bootvar settings and
> nothing seems to get the machine to boot off the floppy.
> I'm using bootvar 1.3 with boot-device fd:0
> boot-comman boot
> and load-base 100000
Where did that number come from?
Take care,
Bill
charlie allom
this reminds me.
is a LOAD-BASE 0x6c0000 necessary for booting anything other than the boot
floppy install kernel?
should i take it back down to 4000 boot from my HDD /netbsd ?
c.
--
cha...@rubberduck.com
Melbourne, Australia
http://rubberduck.com/ - PGP available
Adam Russell
installation guide that the load base on these machines must be set as such
or else it wouldn't boot. True enough, I recall forgetting to set this and
Linux wouldn't boot. Seeing as I was not getting anywhere in trying to coerce
the machine to boot I got a little "superstitious" and tried to rule out the
old loadbase thing. Hey, after struggling to get the thing to boot a little
"electronic voodoo" came into play >:)
Bill Studenmund wrote:
> On Thu, 20 Jul 2000, Adam Russell wrote:
>
> > Ok, I've tried many boot images (including the most recent ones with
> > 1.4.3_ALPHA and the 1.5 snapshot)as well as various bootvar settings and
> > nothing seems to get the machine to boot off the floppy.
> > I'm using bootvar 1.3 with boot-device fd:0
> > boot-comman boot
> > and load-base 100000
>
> Where did that number come from?
>
> Take care,
>
> Bill
Adam Russell
boot yet. I've gone into the archives of last December and March when there was
some discussion of C600s and have done precisly what had been done by those
posting successes to the list.
I went as far as to set up a netbsd/mac68k box toboot from but was then bitten
by the sudden realization that I didn't have onboard ethernet and my NIC didn't
even have an OF ROM(although it is an Asante 10BT PCI and I thought I heard they
did). If I bought a NIC with an OF ROM would this help? or does the NIC have to
be "onboard"? In any event , I've tried everything else I can think of without
succes.
Best Regards,
Adam Russell
Izumi Tsutsui
> floppy install kernel?
I think "load-base" is used only on booting xcoff files
on HFS partitions.
On boot.fs, load address of bootxx is recorded
in (faked) apple partition map entries.
---
Izumi Tsutsui
tsu...@ceres.dti.ne.jp
Bill Studenmund
> The load-base number came from a stern warning in the LinuxPPC R4
> installation guide that the load base on these machines must be set as such
> or else it wouldn't boot. True enough, I recall forgetting to set this and
> Linux wouldn't boot. Seeing as I was not getting anywhere in trying to coerce
> the machine to boot I got a little "superstitious" and tried to rule out the
> old loadbase thing. Hey, after struggling to get the thing to boot a little
> "electronic voodoo" came into play >:)
The reason it is so important is that this number has to match where the
loading program wants to be loaded for some of the loading schemes to
work.
The problem is that NetBSD does not use the same number. We use 6c0000
instead. :-)
The moral of the story is that you should use the number your boot loader
was made for, and be as superstitious as the Linux FAQ says. :-)
Take care,
Bill