[ltp] Netgear FA511 trouble

Wed, 25 May 2005 12:29:04 +0200

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Mike Kershaw wrote:
<blockquote cite="mid20050524151214.GA13694@DRD1812.marist.edu"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">Err? The module is found, so it has to be there. The failure is printed because the module (which is there) cannot be successfully loaded. A quick googling found out, that i82365 is the controller of the PCMCIA bridge. As you have already loaded the yenta drivers I suppose you don't need to load this one. But on the other hand, I've never used a PCMCIA card up to now. :-)

But the problem is definitely not the module not being there, but something else.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
i82365 is for pcmcia bridges, yes, however you almost certianly have a
cardbus bridge -- these are almost always controlled by the yenta_socket
driver.

Your system is probably misconfigured to load the i82365 instead of
yenta_socket, and you don't have anything 82365 can handle.

Once you get the bridge working, there are a few other things to keep in
mind:

In general you'll want pcmcia-cs and hotplug, to handle both pcmcia
cards and cardbus cards.  Hotplugd should be running, if you want to
autoload drivers for cardbus devices.

Think of it as pcmcia == ISA, and carbus == PCI.

Once inserted, a cardbus card will show up in ``lspci'', and uses the
standard pci drivers.  A pcmcia card will show up in ``cardctl ident''
and uses the *_cs drivers.

Hope that helps,

-m
  </pre>
</blockquote>
<br>
Thank you all for you replies. <br>
<br>
1. I am able to get the netcard interface (eth0) up using 'ifconfig',
but
unable to use dhcpcd to fetch an address for it in the 2.6.11 kernel as
oposed to the 2.4.28. Using dhcpcd results in eth0 to shut down and
only leaving 127.0.0.1 when calling 'ifconfig'. The following dmesg is
logged:<br>
<br>
Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)<br>
PCI: Enabling device 0000:01:00.0 (0000 -&gt; 0003)<br>
ACPI: PCI interrupt 0000:01:00.0[A] -&gt; GSI 9 (level, low) -&gt; IRQ 9<br>
PCI: Setting latency timer of device 0000:01:00.0 to 64<br>
tulip0:&nbsp; MII transceiver #1 config 3000 status 7849 advertising 01e1.<br>
eth0: ADMtek Comet rev 17 at c8908000, 00:10:7A:68:7B:9D, IRQ 9.<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
eth0: Setting full-duplex based on MII#1 link partner capability of
45e1.<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
eth0: Setting full-duplex based on MII#1 link partner capability of
45e1.<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
eth0: Setting full-duplex based on MII#1 link partner capability of
45e1.<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
eth0: Setting full-duplex based on MII#1 link partner capability of
45e1.<br>
0000:01:00.0: tulip_stop_rxtx() failed<br>
<br>
2. The reason for trying to load i82365 is that this is what happens on
my 2.4.28-gentoo-r8 setup on which the card works flawlessly. Question:
Are the same modules needed between a 2.4.28 kernel and a 2.6.11?<br>
<br>
3. I have it (i82365) module in my kernel (2.6.11-gentoo-r9), with the
error described. In 2.4.28 boot sequence it says "modprobe yenta_socket
failed" whereafter i82365 loads and initializes the bridge.<br>
<br>
4. The card is now being assigned irq 9<br>
<br>
5. The bridges seem to be working - they report "configuration:
driver=yenta_cardbus". They have the same IRQ - 9.<br>
<br>
6. Is there no way to do in the 2.6.x kernel the same as in the 2.4.x
kernel and disable PCMCIA and using only pcmcia-cs?<br>
<br>
Well any hints and help are greatly appreciated ...<br>
<br>
Regards<br>
<br>
Jacob Klitm&oslash;ller<br>
<br>
<br>
</body>
</html>