I have an embedded Broadcomm 95721 Tigon3. I've compiled <*> tg3 into the kernel with <*> Broadcomm PHY'S. Softlinked net.lo to net.eth0. Tried both in runlevel boot & (currently) runlevel default. .lo comes up and .eth0 hangs @dhcp & ssh fails. After I log-in as root on console and initialize it with '/etc/init.d/net.eth0 start' it brings up the adapter and obtains IP. But not durning boot. I noticed I had to start it (eth0) manually with the LiveDVD 10.1 when I was building it. Let me know if you need any files or output. Reproducible: Always
1) [Relevant] dmesg output would be nice. 2) Please post the output of the relevant `emerge -vpq sys-kernel/?-sources' in a comment. Interestingly, though: To compile this driver as a module, choose M here: the module will be called tg3. This is recommended. What happens if you build it as a module?
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules (user_auxdbmodule, modules_file)) [ebuild R ] sys-kernel/gentoo-sources-3.1.5 USE="-build -deblob -symlink" !!! The following installed packages are masked: - dev-lang/python-3.2.2::gentoo (masked by: package.mask) /etc/portage/package.mask: #=sys-devel/llvm-3.0 #=sys-devel/clang-3.0 For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. * IMPORTANT: 2 news items need reading for repository 'gentoo'. * Use eselect news to read news items. BTW: Not sure what to do about the metadata error in portage. I guess I could erase it and get a new -latest or rsync from scratch
Just rebooted. It's running kernel 3.0.6, It's configured as module by default using the kernel-config off of a minimal installcd from a month or so ago. dmesg|grep tg3 shows the module is in there, tg3.c:v3.119 (May 18, 2011) tg3 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 tg3 0000:04:00.0: setting latency timer to 64 tg3 0000:04:00.0: eth0: Tigon3 [partno(BCM95721) rev 4101] (PCI Express) MAC address 00:15:c5:e2:55:ce tg3 0000:04:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0]) tg3 0000:04:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] tg3 0000:04:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit] tg3 0000:04:00.0: eth0: Link is up at 100 Mbps, full duplex tg3 0000:04:00.0: eth0: Flow control is on for TX and on for RX Running the net.eth0 scripts starts dhcp after I get into a shell, I tried compiling it in after reading a thread on the forum. Is there something else I need to look for in dmesg?
Are you still having issues with later kernels?
