| View previous topic :: View next topic |
| Author |
Message |
nanoo
Apprentice
Joined: 23 Jan 2005
Posts: 150
|
 Posted: Fri Feb 11, 2005 3:44 am Post subject: configuring a second network interface |
 |
|
Hi,
I have just figured out the prism54 driver, and am all set to get my wireless card going, however I can't seem to configure this second network interface (the first being a regular ethernet connection).
Here's what I get when I iwconfig:
| Code: |
morbo init.d # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 NOT READY! ESSID:off/any
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Tx-Power=31 dBm Sensitivity=0/200
Retry min limit:0 RTS thr=0 B Fragment thr=0 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
tunl0 no wireless extensions.
sit0 no wireless extensions.
|
So I think that means that the prism54 driver is up and running, but eth1 isn't configured.
At first I didn't have a net.eth1 in my /etc/init.d directory. Following the instructions in the Gentoo Handbook section on networking, I have set up a symbolic link between net.eth0 (my ethernet connection) and net.eth1. So now net.eth1 shows up in /etc/init.d
However, when I try /etc/init.d/net.eth1 start, it seems to be trying to get an IP address from the DHCP server (I set iface_eth1=dhcp in the /etc/conf.d/net), but unlike net.eth1 it can't seem to get the DHCP to give it an address. This is what I get:
| Code: |
morbo init.d # /etc/init.d/net.eth1 start
* Bringing eth1 up via DHCP ... [ !! ]
|
I don't know how to get more information on what the problem is here... I try:
| Code: |
dmesg | grep net.eth1
|
however that gives no output.
I also tried bringing down eth0, and then starting eth1 - with no results:
| Code: |
morbo init.d # /etc/init.d/net.eth0 stop
* Bringing eth0 down
* Removing inet6 addresses
* eth0 inet6 del fe80::2e0:4cff:fed4:ef19/64 ... [ ok ] * Releasing DHCP lease for eth0 ... [ ok ] * Stopping eth0 ... [ ok ]morbo init.d # /etc/init.d/net.eth1 start
* Bringing eth1 up via DHCP ... [ !! ]
|
Any ideas on what I'm doing wrong? Any help would be greatly appreciated - I can't help but feel that I'm getting close to setting up this wireless card.
Thanks, |
|
| Back to top |
|
 |
thebigslide
l33t
Joined: 23 Dec 2004
Posts: 792
Location: under a car or on top of a keyboard
|
| Posted: Fri Feb 11, 2005 4:16 am Post subject: |
|
|
| Code: | | iwconfig eth1 essid [ssid] channel [channel] |
|
|
| Back to top |
|
|
nanoo
Apprentice
Joined: 23 Jan 2005
Posts: 150
|
| Posted: Fri Feb 11, 2005 5:09 am Post subject: |
|
|
Ok, so that got the ESSID giving the right response. It won't set the channel though.... I used the command you gave, and it didn't bring up any errors, but the channel still registers 0 when I want it to be 6.
I also used the command right from the iwconfig man page:
| Code: |
morbo init.d # iwconfig eth1 channel 6
morbo init.d # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 NOT READY! ESSID:"Chateau"
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Tx-Power=31 dBm Sensitivity=0/200
Retry min limit:0 RTS thr=0 B Fragment thr=0 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
Any idea why that wouldn't work?
Thanks, |
|
| Back to top |
|
|
thebigslide
l33t
Joined: 23 Dec 2004
Posts: 792
Location: under a car or on top of a keyboard
|
| Posted: Fri Feb 11, 2005 4:36 pm Post subject: |
|
|
are there any messages in dmesg or /var/log/messages? It seems the device isn't initializing properly. It should just work. |
|
| Back to top |
|
|
nanoo
Apprentice
Joined: 23 Jan 2005
Posts: 150
|
| Posted: Fri Feb 11, 2005 9:53 pm Post subject: |
|
|
Ok, so I think you're right that the device isn't loading up properly. I think the prism54 driver loads:
| Code: |
morbo zoidberg # dmesg | grep prism54
Loaded prism54 driver, version 1.2 |
And my system does recognize eth1:
| Code: |
orbo zoidberg # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 NOT READY! ESSID:off/any
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Tx-Power=31 dBm Sensitivity=0/200
Retry min limit:0 RTS thr=0 B Fragment thr=0 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
But when I check dmesg for eth1:
| Code: |
morbo zoidberg # dmesg | grep eth1
eth1: islpci_open()
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware uploaded done, now triggering reset...
eth1: device soft reset timed out
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgt_commit has failed. Restart the device
eth1: no IPv6 routers present
eth1: islpci_close ()
|
I have checked that the router is sending wireless - my iBook picks it up just fine.
/var/log/everything/current gives a similar output as dmesg:
| Code: |
Feb 11 16:40:02 [kernel] eth1: device soft reset timed out
Feb 11 16:40:03 [kernel] eth1: timeout waiting for mgmt response
- Last output repeated 3 times -
Feb 11 16:41:01 [dhcpcd] timed out waiting for a valid DHCP server response_
|
Any help with what could be preventing the device from starting up properly would be greatly appreciated.
Thanks very much, |
|
| Back to top |
|
|
thebigslide
l33t
Joined: 23 Dec 2004
Posts: 792
Location: under a car or on top of a keyboard
|
| Posted: Fri Feb 11, 2005 10:04 pm Post subject: |
|
|
From what it looks like, the device either
a) is dead
b) needs different firmware
The firmware can be found in the windows install package and the files normally end in BIN.
First, test the card on a windows computer, or a computer where those cards are known to work to make sure the card works.
Then, if it works, do a search on www.google.com/linux for the model of card you have and see if anyone has a howto posted. You might have to load the firmware. Normally, firmware goes in the /lib/modules/kernelversion/kernel/drivers/where_the_wireless_card_driver_is/ and you specify the filename when loading the module. (can be automated with /etc/modules.d/whatever |
|
| Back to top |
|
|
|
Networking & Security
