public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Colleen Beamer <colleen.beamer@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Another Install Issue
Date: Tue, 18 Oct 2011 14:31:25 -0400	[thread overview]
Message-ID: <4E9DC5FD.9000308@gmail.com> (raw)
In-Reply-To: <201110162323.53864.michaelkintzios@gmail.com>

On 10/16/11 18:23, Mick wrote:
> On Sunday 16 Oct 2011 23:04:00 CJoeB wrote:
>> On 10/16/11 17:24, Neil Bothwick wrote:
>>> On Sun, 16 Oct 2011 17:02:08 +0100, Mick wrote:
>>>> As I said above the kernel ought to manage the order in which the
>>>> modules and dependencies are loaded.
>>> Would building one modules into the kernel and the other as a module
>>> solve (well, kludge) the loading order problem?
>> Tried building tg3 directly into the kernel.  It didn't help.  :-(
> Try building both broadcom and tg3 directly into the kernel.
>
> If upon reboot that doesn't work build broadcom in the kernel and tg3 as a 
> module.
>
> If nothing else works, set up Florian's recommended init.d script and that 
> should sort it out.

Woo hoo!  I did as someone suggested and build all broadcom and tg3
drivers into the kernel.  I had previously build tg3 into the kernel,
but that didn't work.  However, when I was configuring the kernel this
time, I noticed some entries about Broadcom PHY.  On my laptop, when it
boots and gets the the tg3 load, it says something about tg3 and has
libphy in brackets.  The stuff about Broadcom PHY was never built into
the kernel and it wasn't something that I deselected.  I'm not sure
exactly what portion of this fixed the problem, but at least my ethernet
is active when I boot!  :-)

Thanks to everyone who helped on this!

Now, I'm on to working on an audio problem - Can't get audio CD's to
play in either kscd or kaffeine.  Haven't installed amarok yet.

Regards,

Colleen



  parent reply	other threads:[~2011-10-18 18:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15 23:05 [gentoo-user] Another Install Issue CJoeB
2011-10-16  9:59 ` Stroller
2011-10-16 13:27   ` CJoeB
2011-10-16 10:05 ` Florian Philipp
2011-10-16 10:18   ` Mick
2011-10-16 22:35     ` Florian Philipp
2011-10-16 22:46       ` Alex Schuster
2011-10-17  6:03         ` Florian Philipp
2011-10-17  8:15       ` Neil Bothwick
2011-10-17 11:19         ` Mick
2011-10-17 11:30           ` Neil Bothwick
2011-10-17 12:39             ` Florian Philipp
2011-10-17 12:48               ` Neil Bothwick
2011-10-17 12:40       ` J. Roeleveld
2011-10-17 13:09         ` Florian Philipp
2011-10-16 10:43 ` Mick
2011-10-16 12:59   ` Florian Philipp
2011-10-16 15:05     ` CJoeB
2011-10-16 15:29       ` Matthew Finkel
2011-10-16 16:08         ` CJoeB
2011-10-16 17:37           ` Mick
2011-10-16 19:19             ` CJoeB
2011-10-16 20:43               ` Florian Philipp
2011-10-16 14:52   ` CJoeB
2011-10-16 16:02     ` Mick
2011-10-16 21:24       ` Neil Bothwick
2011-10-16 22:03         ` Mick
2011-10-16 22:04         ` CJoeB
2011-10-16 22:23           ` Mick
2011-10-17  0:24             ` CJoeB
2011-10-18 18:31             ` Colleen Beamer [this message]
2011-10-18 18:50               ` Mick
2011-10-16 21:23     ` Neil Bothwick

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=4E9DC5FD.9000308@gmail.com \
    --to=colleen.beamer@gmail.com \
    --cc=gentoo-user@lists.gentoo.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