Very Computer

Info ...

No IRQ/memory conflicts are left unresolved.  I start with a couple due to
both NICs having the same IRQ.

ata0 uses IRQ 14 & io 0x1F0
ata1 uses IRQ 15 & io 0x170

FDisk partitioning looks like:
da0 use entire disk.  The one slice of sub-type 165 is known as da0s1 and is
flagged C
da1 use entire disk.  The one slice of sub-type 165 is known as da1s1 and is
flagged C

freeBSD partitioning looks like:
part      mount     size          Newfs   Part
da0s1a    /          150MB    UFS        Y
da0s1b   swap    128MB    SWAP
da0s1e   /usr       1769MB  UFS        Y
da1s1b   swap    256MB    SWAP
da0s1e   /tmp      200MB   UFS        Y
da0s1f    /var      1607MB  UFS        Y

I'm now choosing a "user" install, to keep it simple from ...
ftp://ftp2.au.freebsd.org/pub/FreeBSD/releases/i386/4.6-RELEASE/

Everything seems to download ok and I'm congratulated for having chosen BSD
as an operating system.  I then skip through other "post -install" config
options to do with NFS, FTP etc. but then an error message appears ...
"Unable to get packages /INDEX file from selected media."

I am able to continue and add a user account which I make a member of the
"wheel" group and I set a root password.

I'm then taken back to the "stand/sysinstall" main menu which I exit and the
system reboots ... into "missing operating system".  I insert the floppy
containing "kern.flp", reboot, and start over again, and again, and again
...

Any help appreciated.

BernieM

Quote:> Trying to installing freeBSD v4.6, when I reboot it comes up with
> "missing operating system".

> Info ...

> No IRQ/memory conflicts are left unresolved.  I start with a
> couple due to both NICs having the same IRQ.

> ata0 uses IRQ 14 & io 0x1F0
> ata1 uses IRQ 15 & io 0x170

> FDisk partitioning looks like:
> da0 use entire disk.  The one slice of sub-type 165 is known as
> da0s1 and is flagged C
> da1 use entire disk.  The one slice of sub-type 165 is known as
> da1s1 and is flagged C

> freeBSD partitioning looks like:
> part      mount     size          Newfs   Part
> da0s1a    /          150MB    UFS        Y
> da0s1b   swap    128MB    SWAP
> da0s1e   /usr       1769MB  UFS        Y
> da1s1b   swap    256MB    SWAP
> da0s1e   /tmp      200MB   UFS        Y
> da0s1f    /var      1607MB  UFS        Y

> I'm now choosing a "user" install, to keep it simple from ...
> ftp://ftp2.au.freebsd.org/pub/FreeBSD/releases/i386/4.6-RELEASE/

> Everything seems to download ok and I'm congratulated for having
> chosen BSD as an operating system.  I then skip through other
> "post -install" config options to do with NFS, FTP etc. but then
> an error message appears ... "Unable to get packages /INDEX file
> from selected media."

> I am able to continue and add a user account which I make a member
> of the "wheel" group and I set a root password.

> I'm then taken back to the "stand/sysinstall" main menu which I
> exit and the system reboots ... into "missing operating system".
> I insert the floppy containing "kern.flp", reboot, and start over
> again, and again, and again ...

> Any help appreciated.

Dorsai

--
******************************

Stupidity is NOT a survival mechanism.

******************************

BernieM

Is there a virus detection feature in your BIOS? If yes, turn it off. Most
modern BIOSes have this feature. It will stop programs (which are usually
viruses) from writing to your boot sector (as that is where a lot of viruses
like to live). Unfortunately, operating systems need to write to this sector
to complete the install.

You can turn on virus detection again once you have FreeBSD installed and
working.
--
On Persona, and the Differences to One's Mundane Being:

If I'm wearing glasses, I'm David. If I'm not wearing glasses and am awake,
I am probably Cariadoc. Cariadoc lives in a different world than David.
Fuzzier.

Although I've tried many combinations, do you know if specific mount points
MUST be one the *bootable* drive?

BernieM

Quote:> Thanks Loki, but "virus warning" was disabled in the BIOS.

> Although I've tried many combinations, do you know if specific mount
points
> MUST be one the *bootable* drive?

> BernieM

If you have a Win2000 or XP cd, place that in the CD-Drive and reboot.  Once
it reads the CD It will prompt you to "press any key to boot from CD".  Let
that time out, it should then try to boot from the disk, and it may well
work.  I had a problem like this with OpenBSD once, something with the first
stage boot-loader IIRC.

Good luck getting it going.

Kyle

: ata0 uses IRQ 14 & io 0x1F0
: ata1 uses IRQ 15 & io 0x170
:
: freeBSD partitioning looks like:
: part      mount     size          Newfs   Part
: da0s1a    /          150MB    UFS        Y
: da0s1b   swap    128MB    SWAP
: da0s1e   /usr       1769MB  UFS        Y
: da1s1b   swap    256MB    SWAP
: da0s1e   /tmp      200MB   UFS        Y
: da0s1f    /var      1607MB  UFS        Y
:
        Ummm, "da" indicated a SCSI disk. "ad" indicates an ATA
    disk drive.

        Do you have both SCSI and ATA disks, and perhaps not told
    the BIOS to boot off of the SCSI drive?

                                                        Bruce
--
------------------------------------------------------------------------
  "I like bad!"                         Bruce Burden    Austin, TX.
        - Thuganlitha
        The Power and the Prophet
        Robert Don Hughes

Quote:

> > Thanks Loki, but "virus warning" was disabled in the BIOS.

> > Although I've tried many combinations, do you know if specific mount
> points
> > MUST be one the *bootable* drive?

> > BernieM

> The "/" partition must be on the disk marked as bootable I'm pretty sure.
> Have you tried installing the FreeBSD boot manager?  I know I had a system
> that would not boot straight to FreeBSD, but when I installed the boot
> manager, it seemed to like that better.  Another wierd thing to try...

> If you have a Win2000 or XP cd, place that in the CD-Drive and reboot.
Once
> it reads the CD It will prompt you to "press any key to boot from CD".
Let
> that time out, it should then try to boot from the disk, and it may well
> work.  I had a problem like this with OpenBSD once, something with the
first
> stage boot-loader IIRC.

> Good luck getting it going.

> Kyle

BernieM