From: Glen Cunningham <glen@exemail.com.au>
To: sig-arm@lists.ipfire.org
Subject: Re: Raspberry Pi B+ NO USB Support
Date: Mon, 11 Aug 2014 21:17:50 +1000 [thread overview]
Message-ID: <201408112117.50591.glen@exemail.com.au> (raw)
In-Reply-To: <0ef1441a482f9a008c8db36af391c4a3@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
G'day Arne,
On Monday 11 August 2014 20:31:26 Arne Fitzenreiter wrote:
> On 2014-08-11 03:04, Glen Cunningham wrote:
> > G'day Sig-Arm list,
> > I have just tried the latest release
> > (ipfire-2.15.1gb-ext4.armv5tel-full-core81.img) on my Raspberry Pi
> > B+ (B-Plus). First boot and partition re-size was fine, reboot to
> > the "Select Keyboard" screen looked good but there is no keyboard
> > response - actually no USB device response at all! A 'Pi without
> > USB support has very limited use.
>
> Ack but we have not the resources to change this without help of the
> RPi foundation.
> There are no Firmware and Patches for kernel-3.10.x released yet and
> i think they will
> never released.
>
> > Is there an easy way to get the correct USB driver for this
> > model? The Debian (Raspbian) people have this fixed,
>
> Raspbian simply use the kernel-3.12.x and firmware suplied from the
> RPi foundation.
>
> > can the driver from Raspbian be used on IPFire?
>
> No. It's a wrong kernel version without and it lacks of some needed
> features like IMQ, Layer7 and grsecurity.
>
> Arne
Thanks for the reply. Since I do not have the skills or resources to
setup my own cross-compiler, I will just have to wait. Seems a pity as
the improved hardware in the model B-plus should make it a good
candidate for a firewall/router.
Cheers,
Glen
next prev parent reply other threads:[~2014-08-11 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 1:04 Glen Cunningham
2014-08-11 8:38 ` Michael Tremer
2014-08-11 10:31 ` Arne Fitzenreiter
2014-08-11 11:17 ` Glen Cunningham [this message]
2014-08-11 12:31 ` Michael Tremer
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=201408112117.50591.glen@exemail.com.au \
--to=glen@exemail.com.au \
--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