Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Dec 2005 10:23:52 -0800
From:      Derrick Ryalls <ryallsd@gmail.com>
To:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: HP Pavillion laptop can't boot FreeBSD
Message-ID:  <d5eb95fc0512211023o63a493e8n73843c956eb89510@mail.gmail.com>
In-Reply-To: <447j9yo04d.fsf@be-well.ilk.org>
References:  <d5eb95fc0512202101h7ff1bfe5p24fed3d2c5783bf3@mail.gmail.com> <447j9yo04d.fsf@be-well.ilk.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Dec 2005 12:01:22 -0500, Lowell Gilbert <
freebsd-questions-local@be-well.ilk.org> wrote:
>
> Derrick Ryalls <ryallsd@gmail.com> writes:
>
> > I recently purchased an HP Pavillion laptop (dv8000) that has an AMD-64
> CPU,
> > with the intent on running FreeBSD 6.0 (i386) as a dual boot option.  I
> have
> > installed BSD numerous times on various desktops, but this is my first
> > attempt on a laptop.
> >
> > When I boot off the CD, before the boot menu comes up, an error message
> > comes up: elf32_lookup_symbol: corrupt symbol table.  Then the normal
> boot
> > menu comes up, at which point selecting option 1 (normal) or option 2
> > (without ACPI) causes the BTX loader to halt after displaying some hex
> > errors.  I even tried hitting option 6, unsettng acpi_load, then
> booting,
> > but the same error comes up.
> >
> > I tried 6.0 AMD-64 and didn't get as far.  Before the boot menu could
> come
> > up, it continually spews what appears to be the same/similar hex errors
> and
> > didn't even respond to Cntrl-Alt-Delete.  Trying 5.4, I don't get the
> elf32
> > error before the boot menu, but if I select option 1 it has trouble
> loading
> > ACPI and then shuts down.  Selecting option 2 (with the 5.4 cd) does no=
t
> > bring up an error, the system just shuts down.  Out of curiousity, I
> tried a
> > Knoppix 4.0 CD and was able to fully boot and get a functioning system
> up
> > (albeit running off the CD).
> >
> > My bios has painfully few options, such as boot order and disabling the
> > onboard wireless nic, nothing else.
> >
> > Is there something else I should try, or do I have to wait for the time
> > being?
>
> What happens when you boot in "safe mode"?
>

I think I got the same error, but I will double check in a couple hours whe=
n
I get home and can try again.



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