Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 3 May 2008 10:46:11 -0400
From:      "Shaun Sabo" <shaun.bsd@gmail.com>
To:        rick-freebsd@kiwi-computer.com
Cc:        Jeremy Chadwick <koitsu@freebsd.org>, freebsd-hardware@freebsd.org
Subject:   Re: FreeBSD 7.0 SATA Controller
Message-ID:  <be79767b0805030746j330c79dkab637f32902ed333@mail.gmail.com>
In-Reply-To: <20080503040930.GB26564@keira.kiwi-computer.com>
References:  <be79767b0805011204r1a7aad67tf4f78d5363684f81@mail.gmail.com> <be79767b0805011918k304e26d0ybd79f2d20e102bf7@mail.gmail.com> <be79767b0805011946p4a49ff7bs51db30652e0736aa@mail.gmail.com> <20080502025657.GA82058@eos.sc1.parodius.com> <be79767b0805012003i72578470x9b568c7cf47fe4b@mail.gmail.com> <20080502184449.GA21226@keira.kiwi-computer.com> <be79767b0805021909y1b8192b9tc7f883730ccaba3e@mail.gmail.com> <20080503024240.GA28006@eos.sc1.parodius.com> <be79767b0805022053h1c02dd4at4d838e8816def158@mail.gmail.com> <20080503040930.GB26564@keira.kiwi-computer.com>

next in thread | previous in thread | raw e-mail | index | archive | help
the livefs cd links are
7.0-RELEASE
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.0/7.0-RELEASE-i386-livefs.iso
7-STABLE
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso
i tried these in vmware and on another computer and neither one drops me
into a shell. they both put me in the sysinstall program and i have to
activate the livefs from the fixit menu then go to virtual terminal 4
(alt+f4). problem is i cant get the livefs shell to start on my system.
works fine in vmware, qemu, and my sisters computer so i know there isnt
something wrong with the cds.

Im really not too concerned about the bios bug. i just figured it might be a
side effect of freebsd not being able access the disks. just out of
curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic
device supposed to do?

as for not being able to mount any media from any freebsd 7.0  system. this
includes when i rebuilt the kernel and world from 6.2 to 7.0 with the
generic kernel. when i tried booting it was not able to find the root
partition. the install and livefs cds can also not find the hard disks nor
can you use the livefs utilities as stated above.

On Sat, May 3, 2008 at 12:09 AM, Rick C. Petty <
rick-freebsd@kiwi-computer.com> wrote:

> On Fri, May 02, 2008 at 11:53:04PM -0400, Shaun Sabo wrote:
> > the livefs cds do not drop you into a shell. they drop you into the same
> > screen you see when you insert an installation cd. try it on qemu or
> another
> > virtualization program or even boot one up if you have a spare cd rom.
> in
> > order to access the livefs shell you need to navigate to the fixit menu
> and
> > then go to the livefs CD/DVD option.
>
> Please explain where you obtained said "livefs" CD.  Every livefs CD I've
> tried (in qemu) has dropped me to a shell.  Every "fixit" CD I've tried
> brings me to sysinstall and from there I drop to the shell after
> navigating
> the menus.
>
> > as for the apic vc acpi that was a typo
> > due to exhaustion, sorry bout that.
>
> Sure, but which one do you mean?  I assume you mean booting with or
> without
> ACPI, which is an option in the boot loader.
>
> > > > motherboard so i couldnt even boot the debian installer cd. i also
> tried
> > > > booting the freebsd installer disks without apic but the same
> problem
> > > occurs
> > > > so i dont think its hanging because of the power managment.
>
> ACPI isn't just power management-- it's advanced _configuration_ and power
> interface.  My understanding is that if present, FreeBSD talks to the ACPI
> on the BIOS to allocate IRQs and other resources.  There have been bugs in
> the past when dealing with ACPI which caused the FreeBSD devs to include a
> boot option to disable it.  If your system breaks w/o ACPI, then there's
> certainly a BIOS firmware problem.
>
> Have you tried the following test?  Cold boot (from power off) to FreeBSD
> CD, disable ACPI from the menu, boot the kernel, then do a warm reboot and
> see if the problem exists.  My sense is that if your first attempt from a
> cold start has ACPI enabled, the problem will persist for every subsequent
> warm reboot.
>
> -- Rick C. Petty
>



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