Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Aug 2006 01:07:21 -0400
From:      "Rickey Bartlett" <subtexel@gmail.com>
To:        freebsd-ppc@freebsd.org
Subject:   Re: FreeBSD on an external Firewire HD
Message-ID:  <b9220d3f0608062207wf9f20a1g3503eed150ca4b53@mail.gmail.com>
In-Reply-To: <b9220d3f0608062026j3cb6b649w3a699a19b65e123f@mail.gmail.com>
References:  <b9220d3f0608051943s4d641755r9d14dafdd7bf964f@mail.gmail.com> <44D5595C.2060902@freebsd.org> <b9220d3f0608051954o7b11694cle4a3e1fbae5d9f15@mail.gmail.com> <b9220d3f0608052011v6ac9e12am464cba0e28be3b78@mail.gmail.com> <b9220d3f0608061929i27b20e8bx60a6e9218a1249d6@mail.gmail.com> <b9220d3f0608062026j3cb6b649w3a699a19b65e123f@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Well, that didnt fix it. Ideas anyone?

One thing I did notice when it boots is that it mentions that /dev/da0s5 has
been mentioned more than once in fstab, and then it spews out operation not
permitted.  I clicked 'A' for auto label on that particular partition, and
partitioned s3 as swap. Im going to give it a whirl one more time before
bed, if anyone has any ideas Im all ears.

Rickey

On 8/6/06, Rickey Bartlett <subtexel@gmail.com> wrote:
>
> Hold that... I might have found the answer.
>
> http://lists.freebsd.org/pipermail/freebsd-ppc/2006-February/001552.html
>
> Rickey
>
>
> On 8/6/06, Rickey Bartlett <subtexel@gmail.com> wrote:
> >
> > Ok, turns out it was a bad keyboard. That part is fixed. Now here's some
> > more problems...
> >
> > Now when I boot into FreeBSD I get errors about "Operation not
> > permitted" during bootup when it's trying to mount /var /usr and /tmp. I had
> > the same errors during the install after setting them up in Disk labeler (I
> > only created two partitions on the external firewire HD under Mac OSX as
> > Unix File System). It dumps me to the default shell (/usr/bin/sh), and thats
> > it. I can grab an IP for my built in ethernet (pretty sweet!) but thats
> > about all I can do, trying to grab a port tarball with portsnap leaves it
> > hung at extracting. Is this all there is for FreeBSD on PPC? Or did I miss
> > something horribly simple, and bork my install?
> >
> >
> > Rickey
> >
> > On 8/5/06, Rickey Bartlett < subtexel@gmail.com> wrote:
> > >
> > > Still doesnt work... (just to make sure I am doing this correctly,
> > > 'set hint.pcib.1.skipslot=26' and then I issue the command boot).
> > >
> > > Rickey
> > >
> > >
> > > On 8/5/06, Rickey Bartlett < subtexel@gmail.com> wrote:
> > > >
> > > > Gah. don't know where I got that from, let me try it and give an
> > > > update.
> > > >
> > > > Thanks,
> > > >
> > > > Rickey
> > > >
> > > >
> > > > On 8/5/06, Peter Grehan < grehan@freebsd.org> wrote:
> > > > >
> > > > > > I have tried booting with an
> > > > > > external USB keyboard, disabling the bluetooth with hint
> > > > > > pcib.1.slotnumber=26 at the loader portion
> > > > >
> > > > >   Should be: hint.pcib.1.skipslot=26
> > > > >
> > > > > later,
> > > > >
> > > > > Peter.
> > > > >
> > > >
> > > >
> > >
> >
>



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