From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RFTBb-0000KQ-E3 for garchives@archives.gentoo.org; Sun, 16 Oct 2011 16:03:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6317221C180; Sun, 16 Oct 2011 16:03:24 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 40FE521C17C for ; Sun, 16 Oct 2011 16:02:14 +0000 (UTC) Received: by wwi36 with SMTP id 36so352132wwi.10 for ; Sun, 16 Oct 2011 09:02:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=cH5Xm0SW5gtLcC/H2sigvz5y5gtP/woh7e+ko7c3RWA=; b=Gxl4iV8bqeWJk2i3HrB97s6qhv+7iiWYzgwAr6ABmbFIXhO+szEnHNXZXo+uy6u4P9 BrDm5+5O+/uGOvpzWvVKZZfE2WnX/J4jJ8koLwrjJppodFTF13iiopblTK6wpYuNSJTU qjH4OTJJytQenlLy8ZtaCsx9i44YutimuziK4= Received: by 10.216.230.3 with SMTP id i3mr5389656weq.112.1318780934424; Sun, 16 Oct 2011 09:02:14 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPS id gd6sm26049664wbb.1.2011.10.16.09.02.12 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Oct 2011 09:02:13 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Another Install Issue Date: Sun, 16 Oct 2011 17:02:08 +0100 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo-r3; KDE/4.6.5; x86_64; ; ) References: <4E9A119D.1000501@gmail.com> <201110161143.51308.michaelkintzios@gmail.com> <4E9AEFC3.9020308@gmail.com> In-Reply-To: <4E9AEFC3.9020308@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2726087.cEcBYq0nFM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201110161702.19395.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: e864d8642a557383c8740e6c1f4b1be3 --nextPart2726087.cEcBYq0nFM Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 16 Oct 2011 15:52:51 CJoeB wrote: > On 10/16/11 06:43, Mick wrote: > > On Sunday 16 Oct 2011 00:05:01 CJoeB wrote: > >> Hi everyone, > >>=20 > >>=20 > >> However, now I have a networking issue. > >>=20 > >> 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. > >=20 > > This means that your kernel is not configured with the corresponding > > modules for your network card, or that there is some other configuration > > problem with e.g. firmware loading (if such a thing is necessary for > > your card). >=20 > I use genkernel. Granted, rather than just running genkernel all, I run > genkernel --menuconfig all because I remove stuff that I know I won't > need. However, in the network section, everything related to broadcom > and tg3 is built as a module. I even tried building tg3 directly into > the kernel and it didn't help. I had to do the 'modprobe -r broadcom' > and 'modprobe -r tg3' and then, 'modprobe broadcom' and 'modprobe tg3' > prior to running net-setup even when booted to the install CD. =46rom what your dmesg shows tg3 fails to load. So there should not be a n= eed=20 to remove it. > >> 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. > >>=20 > >> 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. > >>=20 > >> However, when I boot, eth0 does not start. > >=20 > > What does dmesg show? >=20 > On line states: > tg3 0000:03:00.0: Problem fetching invariants of chip, aborting It fails to load. Something is blocking it from accessing the NIC chipset. > > What does cat /var/log/syslog | grep -i tg3 show >=20 > Don't have a syslog file .... however, >=20 > 'cat /var/log/rc.log | grep -i tg3' shows: > *Loading modul tg3 ... >=20 > The line is repeated a total of 7 times. It should only be there once, unless you tried to load it 7 times? > >> I can start it manually by > >> doing 'modprobe -r broadcom' and 'modprobe -r tg3' and then 'modprobe > >> broadcom' and 'modprobe tg3' > >=20 > > So the question is why when you remove and install the module manually > > your NIC driver loads, but at boot time it does not ... >=20 > Good question and I have no idea! :-) I looked into it and the answer seems to be a bug in the kernel (there are= =20 patches out which fix this) that does not make sure that broadcom is loaded= =20 before tg3. > > ifconfig and ifconfig -a (before and after you modprobe the driver) >=20 > Before loading: >=20 > ifconfig just lists: > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:11 errors:0 dropped:0 overruns:0 frame:0 > TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:198 (198.0 B) TX bytes:198 (198.0 B) >=20 > ifconfig -a lists: > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 > TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:324 (324.0 B) TX bytes:324 (324.0 B) The module is not loaded and the kernel has not seen the NIC. > After doing ''modprobe -r broadcom' and 'modprobe -r tg3' and then, > 'modprobe broadcom' and 'modprobe tg3' >=20 > ifconfig lists: >=20 > eth0 Link encap:Ethernet HWaddr 78:2b:cb:ad:9e:47 > inet addr:192.168.2.15 Bcast:192:168.2.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1727 errors:0 dropped:0 overruns:0 frame:0 > TX packets:908 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1826702 (1.7 MiB) TX bytes:67525 (65.9 KiB) >=20 >=20 > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:46 errors:0 dropped:0 overruns:0 frame:0 > TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:828 (828.0 B) TX bytes:828 (828.0 B) >=20 > ifconfig -a lists >=20 > eth0 Link encap:Ethernet HWaddr 78:2b:cb:ad:9e:47 > inet addr:192.168.2.15 Bcast:192:168.2.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2024 errors:0 dropped:0 overruns:0 frame:0 > TX packets:958 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1846649 (1.7 MiB) TX bytes:70725 (69.0 KiB) >=20 >=20 > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:50 errors:0 dropped:0 overruns:0 frame:0 > TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1062 (1.0 KiB) TX bytes:1062 (1.0 KiB) >=20 > > It may also help to know what is your card (lshw and lspci -v). >=20 > Okay, I had to install pciutils before I could get the output so, > obviously, this was done after the drivers loaded. >=20 > lspci -v shows: >=20 > 03:00.0 Ethernet controller: Broadcom Corporation Netlink BCM57788 > Gigabit Ethernet PCIe (rev 01) > Subsystem: Dell Device 04aa > Flags: bus master, fast devsel, latency 0, IRQ 47 > Memory at fe500000 (64-bit, non-prefetchable) [size=3D64K] > Capabilities: [48] Power Management version 3 > Capabilities: [60] Vendor Specific Information: Len=3D6c= > Capabilities: [50] MSI: Enable+ Count=3D1/1 Maskable- 64= bit+ > Capabilities: [cc] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [13c] Virtual Channel > Capabilities: [160] Device Serial Number > 78-2b-cb-ff-fe-ad-9e-47 > Capabilities: [16c] Power Budgeting > Kernel driver in use: tg3 > Kernel modules: tg3 As I said above the kernel ought to manage the order in which the modules a= nd=20 dependencies are loaded. This is a bug. There are patches out to address= =20 this in future kernels. Until then you can try to: 1. Configure your /etc/conf.d/modules as suggested here: http://www.gentoo.org/doc/en/openrc-migration.xml and have broadcom before tg3. 2. Configure broadcom in the kernel and tg3 as module (in case it makes a=20 difference, or swap and see if that helps). 3. Have a custom init script (re)loading them in the right order as Florian= =20 has already suggested. HTH. =2D-=20 Regards, Mick --nextPart2726087.cEcBYq0nFM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk6bAAsACgkQVTDTR3kpaLYvpgCguigYt/B8lsJcPvFULwVqhllC 7fUAoLxqQGeCPrd3i0+FIOg+0kQxlG02 =ta6C -----END PGP SIGNATURE----- --nextPart2726087.cEcBYq0nFM--