Skip site navigation (1)Skip section navigation (2)
Date:      17 Feb 2003 19:43:07 -0000
From:      Matt Anderson <mra@malloc.org>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   i386/48385: Can boot, but can't execute any programs on FreeBSD 5.0
Message-ID:  <20030217194307.71787.qmail@eris.discordians.net>

next in thread | raw e-mail | index | archive | help

>Number:         48385
>Category:       i386
>Synopsis:       Can boot, but can't execute any programs on FreeBSD 5.0
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Feb 17 11:50:08 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Matt Anderson
>Release:        FreeBSD 5.0-RELEASE i386
>Organization:
malloc.org
>Environment:
Shuttle SS51 computer with Pentium 4 Northwood (533Mhz)
        The Shuttle system is a small form factor motherboard and case
        combination that uses an SiS 651/962L chipset.  The system is
        using DDR333 ram, the onboard IDE with UltraDMA disabled, and
        a ATI 8500 AIW for video.  Due to needing firewire support I
        previously had linux installed on the system, and it was able
        to run for extended periods of time, so I don't believe there
        is any hardware interoperability issues.

>Description:
        I downloaded the ISOs and checked the MD5s before and after
        writing the data to the CDs.  When I try to install anything
        other than minimal the install fails (usually while trying to
        pkg_add perl.)  If I do the minimal install passwd fails to
        run when trying to set the root password, but the install
        finishes.  When I boot into the system after that I'm forced
        into single user mode, and when I try to run /bin/sh it cannot
        execute it.

>How-To-Repeat:
        Install FreeBSD 5.0 i386 on a SS51 based system.

>Fix:
        None that I know of.  Could it be possible that the kernel is
        somehow misidentifying the processor, activating some processor
        specific extensions, and loading the executables into memory
        in a way that the chip doesn't understand?
>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030217194307.71787.qmail>