From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: ipfire on a pandaboard
Date: Thu, 25 Jul 2013 16:27:01 +0200 [thread overview]
Message-ID: <1374762421.18293.1.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAJyqC03y5giKK7-poErOGnKSYPaG=aRQBFxEMmmdWwcsgEU3oQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
Hey,
I tried to find out if that version should be supported. I am not very
about that, because I do not know if kernel 3.2 has support for
PandaBoard ES at all.
I hope that Arne will respond to this when he is back.
-Michael
On Tue, 2013-07-23 at 17:36 -0500, Timothy Ehlers wrote:
> I have never gotten ipfire to work on, previously fedora 18 was
> working... barely, there is a kernel bug that forces you to not use
> SMP.
>
>
> I have tried 2.13 core 71/70 and now 68.
>
>
> I have the pandaboard ES revision B.
>
>
> On Tue, Jul 23, 2013 at 3:42 AM, Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
> Hey Tim,
>
> when you see u-boot booting and it loads the kernel, it seems
> that you
> have flashed the image correctly onto the SD card.
>
> What version/revision of the Pandaboard are you using? Do
> other older
> releases of IPFire work?
>
> In general the image is ready for Pandaboard (not the ES
> version AFAIK).
>
> -Michael
>
> On Mon, 2013-07-22 at 21:33 -0500, Timothy Ehlers wrote:
> > Im having a bit of trouble getting ipfire to post on my
> pandaboard.
> >
> >
> > its hanging at this prompt
> >
> >
> > "
> > Starting kernel ...
> >
> >
> > Uncompressing Linux... done, booting the kernel.
> > "
> >
> >
> > At this point i just hangs. ive tried
> > ipfire-2.13.1gb-ext4.armv5tel-full-core70.img
> >
> > and
> > ipfire-2.13.1gb-ext4.armv5tel-full-core71.img
> >
> >
> > Has anybody gotten this to work on a pandaboard?
> > --
> > Tim Ehlers
>
> > _______________________________________________
> > SIG-ARM mailing list
> > SIG-ARM(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/sig-arm
>
>
>
>
>
> --
> Tim Ehlers
next parent reply other threads:[~2013-07-25 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJyqC03y5giKK7-poErOGnKSYPaG=aRQBFxEMmmdWwcsgEU3oQ@mail.gmail.com>
2013-07-25 14:27 ` Michael Tremer [this message]
[not found] <CAJyqC01RV1NyjYDp7t_d=X7mK4K9XfnCRT9Vo4ZDeKF-g+756w@mail.gmail.com>
2013-07-23 8:42 ` Michael Tremer
2013-07-30 18:59 ` Arne Fitzenreiter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1374762421.18293.1.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=sig-arm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox