From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: Now: Debian issues, WAS: XFS Filesystem not mounting
Date: Wed, 15 Sep 2010 10:44:31 +1000 [thread overview]
Message-ID: <20100915004431.GM15695@dastard> (raw)
In-Reply-To: <4C8FB8D6.6080603@hardwarefreak.com>
On Tue, Sep 14, 2010 at 01:03:02PM -0500, Stan Hoeppner wrote:
> pbrunnen put forth on 9/14/2010 11:35 AM:
> > 3) I understand the ideology and legal reasons debian removes firmware blobs
> > (broadcom anyone) from their kernel modules... but this is always a real
> > pain. I end up monkeying about with the initrd image to get the firmware
> > blobs in... and often I just recompile with the blobs and forget it.
>
> Ran into this long ago, and it's one of the reasons I roll my own. I
> include the big blob in my kernels. For _all_ the driver blobs it only
> adds a couple hundred KB to the kernel image, and it's more than worth
> the memory consumption to gain the reduced PITA factor.
You must be doing it wrong, then.
# apt-cache search "^firmware-"
....
Pick the packages for your hardware, or just install the lot (which
is what I normally do) and remake your initramfs. The firmware
packages have the correct firmware versions the distro kernels
expect.
If you run custom kernels, the after building it without the
firmware built in, just run 'make firmware_install' before building
your new initramfs and everything will just work fine.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-15 0:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:45 XFS Filesystem not mounting pbrunnen
2010-09-14 1:21 ` Dave Chinner
2010-09-14 4:29 ` pbrunnen
2010-09-14 5:40 ` Michael Monnerie
2010-09-14 6:25 ` Emmanuel Florac
2010-09-14 12:32 ` pbrunnen
2010-09-14 14:03 ` Michael Monnerie
2010-09-14 16:09 ` Stan Hoeppner
2010-09-14 16:35 ` pbrunnen
2010-09-14 18:03 ` Now: Debian issues, WAS: " Stan Hoeppner
2010-09-14 20:32 ` Emmanuel Florac
2010-09-15 1:07 ` pbrunnen
2010-09-15 3:51 ` Stan Hoeppner
2010-09-15 13:15 ` pbrunnen
2010-09-15 0:44 ` Dave Chinner [this message]
2010-09-15 2:54 ` Stan Hoeppner
2010-09-15 0:49 ` pbrunnen
2010-09-14 16:25 ` pbrunnen
2010-09-14 4:43 ` pbrunnen
2010-09-14 5:40 ` Dave Chinner
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=20100915004431.GM15695@dastard \
--to=david@fromorbit.com \
--cc=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
/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