FreeBSD 5.x-R CDROM Installation Hang

From: Nihilist (e_nihilist_at_yahoo.com)
Date: 11/21/03

  • Next message: olgav: "Information about /dist"
    Date: Fri, 21 Nov 2003 01:50:31 -0800 (PST)
    To: freebsd-questions@freebsd.org
    
    

    Hello,

    I've been trying to install FreeBSD 5.1-R from the official 4 CD set.
    The problem I'm about to describe occurs with 5.0-R too. Incidentally,
    everything is fine with the 4.x-R CDs (no hang, no lsdev problem,
    perfect installation).

    I insert the first CD and the loader kicks in. It doesn't matter
    whether or not ACPI is enabled (which my system supports); I get the
    same result either way: the box hangs after the little spinning bar,
    which appears after the 5.1 menu (or after the 'boot' command from the
    loader prompt), has spun a few times. No error messages, no copyright
    + kernel banner, nothing. This occurs in all boot modes... default, no
    acpi, safe, single user.

    I've tried playing with BIOS settings. I've tried dropping to the
    loader prompt (5.1 menu option 6) and playing with device hints via
    the 'show' and 'set' commands, but all the generic settings (irqs,
    ports, etc.) seem to be fine.

    One thing to note is that issuing 'lsdev' at the loader prompt causes
    a reboot, apparently after it tries to gather information about BIOS
    Disk 2 (which seems to be the CDROM). This is strange because it has
    already reported on the CDROM as cd0.

    BTX reports:

    cd0 = CDROM
    Bios Disk 0 = floppy disk (A)
    Bios Disk 1 = hard disk (C)
    Bios Disk 2 = CDROM (D)

    Notice the overlap for CDROM. The 'lsdev' reboot seems to occur when
    it tries to check the CDROM a second time.

    The parameters 'currdev' and 'loaddev' have the default value 'cd0:'.
    Changing 'currdev' to 'disk2:' and typing 'boot' causes an abrupt
    reboot. This seems to further indicate that the problem lies in the
    drive assignment somewhere.

    I have the hard disk attached to IDE#1 Primary. The ATAPI CDROM is
    attached to IDE#2 Slave.

    I can't boot from floppies and try to install from the CD because I
    get a read error with kern.flp (that was dd'd or fdimage'd).

    I've never encountered problems so early in the installation process
    before.

    Any help in solving this nightmare is appreciated.

    __________________________________
    Do you Yahoo!?
    Free Pop-Up Blocker - Get it now
    http://companion.yahoo.com/
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: olgav: "Information about /dist"

    Relevant Pages

    • FreeBSD 5.x-R CDROM Installation Hang
      ... I've been trying to install FreeBSD 5.1-R from the official 4 CD set. ... Disk 2 (which seems to be the CDROM). ... Bios Disk 0 = floppy disk ...
      (comp.unix.bsd.freebsd.misc)
    • Trouble mounting a cdrom in solaris
      ... vold is the daemon that manages floppy disks and cdroms. ... (You will have to figure out which device is presented for the CDROM.) ... If you installed using the install disk as the boot disk and ... _first_ reboot after install, you are seeing this issue because vold does ...
      (SunManagers)
    • Re: will SUSE do what Red Hat cant?
      ... One initial boot it reads from the cdrom using the ... bios floppy disk code, but then it installs using a linux driver. ... >screen based install mode. ...
      (alt.os.linux.suse)
    • installing from a harddisk prepared in a functional system
      ... How does one make a 'boot' disk - be it cdrom, ... the install cdrom's do. ...
      (freebsd-questions)
    • Re: Partition Magic - Reverse Boot Drives?
      ... Use this to install a complete new operating system on a clean drive. ... onto an unallocated space on your hard drive. ... Select disk 1 to see that partition or disk 2 to see the new hard drive. ...
      (microsoft.public.windowsxp.newusers)