public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Another Install Issue
Date: Mon, 17 Oct 2011 00:35:35 +0200	[thread overview]
Message-ID: <4E9B5C37.7060501@binarywings.net> (raw)
In-Reply-To: <201110161118.45443.michaelkintzios@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]

Am 16.10.2011 12:18, schrieb Mick:
> On Sunday 16 Oct 2011 11:05:55 Florian Philipp wrote:
>> Am 16.10.2011 01:05, schrieb CJoeB:
>>> Hi everyone,
>>>
>>> Well, thanks to the help I got from the list, I finally have Gentoo
>>> installed on my new desktop and booting to a command prompt.
>>>
>>> However, now I have a networking issue.
>>>
>>> In past, when I booted to the install CD and my ethernet connection was
>>> not active, I typed net-setup eth0 and was able to set it up.  This
>>> time, when I booted to the install CD and typed net-setup eth0, the
>>> network card was not recognized.  I googled and found a post where
>>> someone said that they had to 'modprobe -r broadcom' and 'modprobe -r
>>> tg3' and then 'modprobe broadcom' and 'modprobe tg3' and then, run
>>> net-setup.  I did this and then ifconfig returned my eth0 connection.
>>>
>>> Of course, later you have to do the cp -L /etc/resolv.conf
>>> /mnt/gentoo/etc/ .... which I did and dhcpcd has been added to my
>>> default runlevel.
>>>
>>> However, when I boot, eth0 does not start.  I can start it manually by
>>> doing 'modprobe -r broadcom' and 'modprobe -r tg3' and then 'modprobe
>>> broadcom' and 'modprobe tg3'
>>>
>>> However, I would like to have my network started automatically.
>>>
>>> I do have config_eth0="dhcp" in my /etc/conf.d/net file
>>>
>>> Any suggestions?
>>>
>>> Colleen
>>
>> Hmm, a workaround would be a custom init script. Copy the following code
>> into a new file in /etc/init.d (let's say /etc/init.d/broadcom-fix):
>>
>> #!/sbin/runscript
>> description="Reload broadcom and tg3 modules to work around kernel bug"
>> depend() {
>>         before net
>> 	after modules
>> }
>> start()
>> {
>> 	ebegin "Reloading broadcom and tg3 modules"
>> 	modprobe -r broadcom tg3 &&
>> 	modprobe broadcom &&
>> 	modprobe tg3
>> 	eend $? "Failed to reload modules"
>> }
>>
>> Make it executable (chmod 755) and add it to the default run level
>> (rc-update add broadcom-fix default).
>>
>> Better try to start it manually before rebooting so you can be sure it
>> works as expected.
>>
>> Hope this helps,
>> Florian Philipp
> 
> This would be a workaround - the question is why does the module need to be 
> removed and reinstalled manually?  Why isn't the kernel loading it at boot 
> time?

I agree that the problem should be solved but just in case Colleen wants
to continue with his installation (I know, he is installing Gentoo for
the first time so I doubt he values his time very high ;-) ), I suggest
he either implements my proposal outlined above or adds similar code to
/etc/conf.d/net:

preup() {
    if [ "$IFACE" = eth0 ]; then
        ebegin "Reloading broadcom and tg3 modules"
        modprobe -r foo bar &&
        modprobe broadcom &&
        modprobe tg3
        ewend $? "Failed to reload modules"
    fi
    return 0
}


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-10-16 22:36 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 [this message]
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
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=4E9B5C37.7060501@binarywings.net \
    --to=lists@binarywings.net \
    --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