On Wed, 11 Jul 2007 12:00:48 -0400 Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 11, 2007 at 03:49:40PM +0000, Robert Cates wrote: > > > > Does Etch (i386/i486) with the (standard) 2.6.18 kernel have a problem > > recognizing (some) network cards? > > > > I have a problem ever since apt-get dist-upgrade from Sarge to Etch. Etch > > with the standard 2.6.18 kernel does not find/recognize my network cards. > > Sarge (3.1) did and ran fine, Etch does not, and I even bought a new > > network card (which has a different chip) and it still does not. Not even > > the Debian installer from the CD1 ISO auto-detects the cards, or accepts my > > manual selection. > > > > I have NetGear FA311 adapters - the older one has the National > > Semiconductor chip (DP83816AVNG) which worked fine with Sarge (2.6.8 > > kernel) and the newer one has the Realtek RTL8139D chip. > > > > Oh, what is sit0? When I give >> ifconfig -a I get the loopback and sit0 > > interfaces(?). > > > > I forget what sit0 is, other than that you don't have to worry about it. > I think it has something to do with inter-process comms. > > Send us the output of dmesg | grep -i eth > > Doug. Something like this might be, for example: 86.702027] 8139too Fast Ethernet driver 0.9.28 [ 87.330923] eth0: RealTek RTL8139 at 0xe0f9cc00, 00:30:84:9e:33:fa, IRQ 10 [ 87.361492] eth0: Identified 8139 chip type 'RTL-8139C' [ 87.456627] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [ 87.619198] eth1: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:13:72:3d:67:b8 [ 87.651890] eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] WireSpeed[1] TSOcap[1] [ 87.684644] eth1: dma_rwctrl[76180000] dma_mask[64-bit] [ 110.989077] tg3: eth1: Link is up at 100 Mbps, half duplex. [ 111.023227] tg3: eth1: Flow control is off for TX and off for RX. [ 174.288842] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 250.051487] eth1: no IPv6 routers present [ 250.654961] eth2: no IPv6 routers present -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
