Re: [gentoo-user] Another Install Issue

[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?
-- 
Regards,
Mick