[ltp] NetGear WG511 with fc3
Bert Haskins
linux-thinkpad@linux-thinkpad.org
Mon, 06 Dec 2004 11:35:03 -0500
In-Reply-To: <41B37EEF.3020109@chartermi.net>
Content-Type: multipart/alternative;
boundary="------------050409050405080203040000"
This is a multi-part message in MIME format.
--------------050409050405080203040000
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
I should have mentioned that the hardware browser shows the card properly
but neither of the status leds on the card have come on in any of my
attempts.
Is something like "alias eth0 prism54" necessary in modprobe.conf?
I've rebooted this system so many times I'm beginning to think that it
is a $sloth product.
Thanks for any help or ideas,
Bert
Bert Haskins wrote:
>
>
> Winsley von Spee wrote:
>
>>Am Samstag, den 04.12.2004, 23:24 -0500 schrieb Bert Haskins:
>>
>>
>>>I'm running fc3 on my 390X, and I can't seem to get my NetGear WG511
>>>Wireless 802.11g card to work with it.
>>>It uses the Prism54 Chipset.
>>>The card runs fine under W2K.
>>>
>>>The isl3890 firmware from prism54 is in /lib/firmware.
>>>Lsmod and cat interrupts both show prism54.
>>>Cardctl ident shows both slots empty(?)..
>>>This command under Mepis 2004 shows
>>>
>>>product info: "Intersil", "ISL3890", "-", "-"
>>> manfid: 0x00b, 0x3890
>>> function: 254 ((null))
>>>
>>>The card does not show up under the Internet connection wizard
>>>although it did when I first tried to set it up(?).
>>>
>>>Has anyone else on the list had good results with this card?
>>>Or have and ideas on what I might be missing.
>>>
>>>A MN520 (wireless b) card runs fine in this machine
>>>and shows up under cardctl ident.
>>>This card was very easy to set up.
>>>
>>>Thanks,
>>> Bert
>>>
>>>
>>>
>>
>>
>>I used this card a relative long time. All I did was including support
>>in the Kernel and putting the firmware to /lib/firmware.
>>What does dmesg say after putting in the card
>>
> /// new lines in dmesg
> Loaded prism54 driver, version 1.2
> PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> divert: allocating divert_blk for eth0
> ip_tables: (C) 2000-2002 Netfilter core team
> eth0: islpci_open()
> eth0: resetting device...
> eth0: uploading firmware...
> eth0: firmware uploaded done, now triggering reset...
> eth0: device soft reset timed out
> eth0: timeout waiting for mgmt response 1000, triggering device
> eth0: timeout waiting for mgmt response
> eth0: timeout waiting for mgmt response 1000, triggering device
> eth0: timeout waiting for mgmt response
> eth0: timeout waiting for mgmt response 1000, triggering device
> eth0: timeout waiting for mgmt response
> eth0: timeout waiting for mgmt response 1000, triggering device
> eth0: timeout waiting for mgmt response
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgmt tx queue is still full
> eth0: mgt_commit has failed. Restart the device
> eth0: no IPv6 routers present
> ///////
>
>>and what says lspci ???
>>
> lspci says "2:00.0 Network controller: Intersil Corporation Intersil
> ISL3890 [Prism GT/Prism Duette] (rev 01)"
>
>>If you build the wlan driver as a module also check lsmod.
>>
> lsmod shows the prism54 module.
>
>>Greetz
>>
>>
>
--------------050409050405080203040000
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
I should have mentioned that the hardware browser shows the card
properly<br>
but neither of the status leds on the card have come on in any of my
attempts.<br>
Is something like "alias eth0 prism54" necessary in modprobe.conf?<br>
<br>
I've rebooted this system so many times I'm beginning to think that it
is a $sloth product.<br>
<br>
Thanks for any help or ideas,<br>
Bert<br>
<br>
<br>
Bert Haskins wrote:<br>
<blockquote type="cite" cite="mid41B37EEF.3020109@chartermi.net">
<meta http-equiv="Content-Type" content="text/html;">
<title></title>
<br>
<br>
Winsley von Spee wrote:<br>
<blockquote type="cite"
cite="mid1102256973.7321.2.camel@localhost.localdomain">
<pre wrap="">Am Samstag, den 04.12.2004, 23:24 -0500 schrieb Bert Haskins:
</pre>
<blockquote type="cite">
<pre wrap="">I'm running fc3 on my 390X, and I can't seem to get my NetGear WG511
Wireless 802.11g card to work with it.
It uses the Prism54 Chipset.
The card runs fine under W2K.
The isl3890 firmware from prism54 is in /lib/firmware.
Lsmod and cat interrupts both show prism54.
Cardctl ident shows both slots empty(?)..
This command under Mepis 2004 shows
product info: "Intersil", "ISL3890", "-", "-"
manfid: 0x00b, 0x3890
function: 254 ((null))
The card does not show up under the Internet connection wizard
although it did when I first tried to set it up(?).
Has anyone else on the list had good results with this card?
Or have and ideas on what I might be missing.
A MN520 (wireless b) card runs fine in this machine
and shows up under cardctl ident.
This card was very easy to set up.
Thanks,
Bert
</pre>
</blockquote>
<pre wrap=""><!---->
I used this card a relative long time. All I did was including support
in the Kernel and putting the firmware to /lib/firmware.
What does dmesg say after putting in the card</pre>
</blockquote>
/// new lines in dmesg<br>
Loaded prism54 driver, version 1.2<br>
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)<br>
divert: allocating divert_blk for eth0<br>
ip_tables: (C) 2000-2002 Netfilter core team<br>
eth0: islpci_open()<br>
eth0: resetting device...<br>
eth0: uploading firmware...<br>
eth0: firmware uploaded done, now triggering reset...<br>
eth0: device soft reset timed out<br>
eth0: timeout waiting for mgmt response 1000, triggering device<br>
eth0: timeout waiting for mgmt response<br>
eth0: timeout waiting for mgmt response 1000, triggering device<br>
eth0: timeout waiting for mgmt response<br>
eth0: timeout waiting for mgmt response 1000, triggering device<br>
eth0: timeout waiting for mgmt response<br>
eth0: timeout waiting for mgmt response 1000, triggering device<br>
eth0: timeout waiting for mgmt response<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgmt tx queue is still full<br>
eth0: mgt_commit has failed. Restart the device <br>
eth0: no IPv6 routers present<br>
///////<br>
<br>
<blockquote type="cite"
cite="mid1102256973.7321.2.camel@localhost.localdomain">
<pre wrap="">and what says lspci ???</pre>
</blockquote>
lspci says "2:00.0 Network controller: Intersil Corporation Intersil
ISL3890 [Prism GT/Prism Duette] (rev 01)"<br>
<br>
<blockquote type="cite"
cite="mid1102256973.7321.2.camel@localhost.localdomain">
<pre wrap="">If you build the wlan driver as a module also check lsmod.</pre>
</blockquote>
lsmod shows the prism54 module.<br>
<blockquote type="cite"
cite="mid1102256973.7321.2.camel@localhost.localdomain">
<pre wrap="">
Greetz
</pre>
</blockquote>
<br>
</blockquote>
</body>
</html>
--------------050409050405080203040000--