I just recent got an old T20 and I am attempting to use Debian on it. I am
using a PCMCIA orinoco wireless card. Here is the crazy part. The card is
recognized by the installer. The installer asks me for my essid and my WEP
key. After I input the information, the wireless card get its ip address over
dhcp and then works flawlessly. The trouble comes when I finish the install
and boot the machine. Once the machine comes up, I cannot get the wireless
card to work. iwconfig shows that it has all of the correct information, but
it cannot get an ip address. I have tried both 4.0r1 and a testing snapshot.
Both have the exact same problem.

Can anyone ?

Thanks,
Chris



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Sep 10, 2007 at 07:37:11PM -0600, Chris Brotherton wrote:
> I just recent got an old T20 and I am attempting to use Debian on it. I am
> using a PCMCIA orinoco wireless card. Here is the crazy part. The card is
> recognized by the installer. The installer asks me for my essid and my WEP
> key. After I input the information, the wireless card get its ip address over
> dhcp and then works flawlessly. The trouble comes when I finish the install
> and boot the machine. Once the machine comes up, I cannot get the wireless
> card to work. iwconfig shows that it has all of the correct information, but
> it cannot get an ip address. I have tried both 4.0r1 and a testing snapshot.
> Both have the exact same problem.
>
> Can anyone ?
>
> Thanks,
> Chris
Do you have 'pump' or 'dhcpd' installed?
what does 'route' show?
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keyserver: subkeys.pgp.net | my NPO: cfsg.org |
|join the new debian-community.org to Debian! |
|_______ Unless I ask to be CCd, assume I am subscribed _______|


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Sep 10, 2007 at 10:05:04PM -0400, Kevin Mark wrote:
> On Mon, Sep 10, 2007 at 07:37:11PM -0600, Chris Brotherton wrote:
> > I just recent got an old T20 and I am attempting to use Debian on it. I am
> > using a PCMCIA orinoco wireless card. Here is the crazy part. The card is
> > recognized by the installer. The installer asks me for my essid and my WEP
> > key. After I input the information, the wireless card get its ip address over
> > dhcp and then works flawlessly. The trouble comes when I finish the install
> > and boot the machine. Once the machine comes up, I cannot get the wireless
> > card to work. iwconfig shows that it has all of the correct information, but
> > it cannot get an ip address. I have tried both 4.0r1 and a testing snapshot.
> > Both have the exact same problem.
> >
> > Can anyone ?
> >
> > Thanks,
> > Chris
> Do you have 'pump' or 'dhcpd' installed?
> what does 'route' show?
Neither pump nor dhcpd is installed.

When the machine boots, all of the wireless settings (essid, wep key, etc) are
set correctly. The dhcp client times out. It doesn't get an ip address and
doesn't set any routes.

Thanks,
Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Chris Brotherton wrote:
> I just recent got an old T20 and I am attempting to use Debian on it. I am
> using a PCMCIA orinoco wireless card. Here is the crazy part. The card is
> recognized by the installer. The installer asks me for my essid and my WEP
> key. After I input the information, the wireless card get its ip address over
> dhcp and then works flawlessly. The trouble comes when I finish the install
> and boot the machine. Once the machine comes up, I cannot get the wireless
> card to work. iwconfig shows that it has all of the correct information, but
> it cannot get an ip address. I have tried both 4.0r1 and a testing snapshot.
> Both have the exact same problem.

I have been running wireless PCMCIA cards in Sarge and Etch on my T20 for a
while. Currently I am using an Edimax EW-7108PCg card with the Ralink chipset. I
have documented the process I followed on the NewbieDOC website [1] [2]. You may
find something ful there.

Can you ping your Access Point?

If not, you might need to disable your ethernet interface:
# ifdown eth0
or similar. If this works you can comment out the eth0 entry in
/etc/network/interfaces


[1]
http://newbiedoc.berlios.de/wiki/How..._are_impatient
[2] http://newbiedoc.berlios.de/wiki/Ins...pper_in_Debian


--
Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, Sep 11, 2007 at 11:47:47AM +0100, Chris Lale wrote:
> Chris Brotherton wrote:
> > I just recent got an old T20 and I am attempting to use Debian on it. I am
> > using a PCMCIA orinoco wireless card. Here is the crazy part. The card is
> > recognized by the installer. The installer asks me for my essid and my WEP
> > key. After I input the information, the wireless card get its ip address over
> > dhcp and then works flawlessly. The trouble comes when I finish the install
> > and boot the machine. Once the machine comes up, I cannot get the wireless
> > card to work. iwconfig shows that it has all of the correct information, but
> > it cannot get an ip address. I have tried both 4.0r1 and a testing snapshot.
> > Both have the exact same problem.
>
> I have been running wireless PCMCIA cards in Sarge and Etch on my T20 for a
> while. Currently I am using an Edimax EW-7108PCg card with the Ralink chipset. I
> have documented the process I followed on the NewbieDOC website [1] [2]. You may
> find something ful there.
>
> Can you ping your Access Point?
>
> If not, you might need to disable your ethernet interface:
> # ifdown eth0
> or similar. If this works you can comment out the eth0 entry in
> /etc/network/interfaces
>
>
> [1]
> http://newbiedoc.berlios.de/wiki/How..._are_impatient
> [2] http://newbiedoc.berlios.de/wiki/Ins...pper_in_Debian
>
>
Thanks. I will take a look at those. Any other ideas why the wireless card
would work during installation, but not after? It looks like the kernels used
for the installer and for the system are the same (well -486 vs -686).

No, I am unable to ping my access point.

Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 11 Sep 2007 18:14:46 -0600
Chris Brotherton <chris@protonlab.net> wrote:

> On Tue, Sep 11, 2007 at 11:47:47AM +0100, Chris Lale wrote:
> > Chris Brotherton wrote:
> > > I just recent got an old T20 and I am attempting to use Debian on it. I am
> > > using a PCMCIA orinoco wireless card. Here is the crazy part. The card is
> > > recognized by the installer. The installer asks me for my essid and my WEP
> > > key. After I input the information, the wireless card get its ip address over
> > > dhcp and then works flawlessly. The trouble comes when I finish the install
> > > and boot the machine. Once the machine comes up, I cannot get the wireless
> > > card to work. iwconfig shows that it has all of the correct information, but
> > > it cannot get an ip address. I have tried both 4.0r1 and a testing snapshot.
> > > Both have the exact same problem.
> >
> > I have been running wireless PCMCIA cards in Sarge and Etch on my T20 for a
> > while. Currently I am using an Edimax EW-7108PCg card with the Ralink chipset. I
> > have documented the process I followed on the NewbieDOC website [1] [2]. You may
> > find something ful there.
> >
> > Can you ping your Access Point?
> >
> > If not, you might need to disable your ethernet interface:
> > # ifdown eth0
> > or similar. If this works you can comment out the eth0 entry in
> > /etc/network/interfaces
> >
> >
> > [1]
> > http://newbiedoc.berlios.de/wiki/How..._are_impatient
> > [2] http://newbiedoc.berlios.de/wiki/Ins...pper_in_Debian
> >
> >
> Thanks. I will take a look at those. Any other ideas why the wireless card
> would work during installation, but not after? It looks like the kernels used
> for the installer and for the system are the same (well -486 vs -686).
>
> No, I am unable to ping my access point.

Try the following:

1) unload and reload the driver module
2) check (and post) the iwconfig output
3) do ifconfig xxxx up; iwconfig xxxx essid nnnnnnnn
4) repeat step 2 - if the card is associated, you should see "Access Point: nn:nn:nn:nn:nn:nn"

> Chris.

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Sep 12, 2007 at 10:35:51AM -0400, Celejar wrote:
[snip]
>
> Try the following:
>
> 1) unload and reload the driver module
> 2) check (and post) the iwconfig output
After unloading, reloading and plugging in the network card, my iwconfig
output is:

eth0 IEEE 802.11b ESSID:"" Nickname:"HERMES I"
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:11 Mb/s Sensitivity=1/3
Retry limit:4 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=0/92 Signal level=134/153 Noise level=134/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

> 3) do ifconfig xxxx up; iwconfig xxxx essid nnnnnnnn
After these commands, the iwconfig output is:

eth0 IEEE 802.11b ESSID:"melange" Nickname:"HERMES I"
Mode:Managed Frequency:2.457 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry limit:4 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=0/92 Signal level=134/153 Noise level=134/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Notice that the Bit Rate dropped to 2 Mb/s.

My access point uses wep. So I ran "iwconfig eth0 key s:XXXXXXXX". The
iwconfig output is:


eth0 IEEE 802.11b ESSID:"melange" Nickname:"HERMES I"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:2 Mb/s Sensitivity=1/3
Retry limit:4 RTS thrff Fragment thrff
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security modepen
Power Managementff
Link Quality=40/92 Signal level=-54 dBm Noise level=-94 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I sanitised the output with 0s and Xs.

> 4) repeat step 2 - if the card is associated, you should see "Access Point: nn:nn:nn:nn:nn:nn"

At this point, everything seems normal. Now I try "dhclient eth0" and it times
out without getting an ip address. I don't think this is a hardware problem
since everything works during the debian installer and when I had freebsd
installed.

Any is appreciated.

Thanks,
Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Chris Brotherton wrote:
[...]
> My access point uses wep. So I ran "iwconfig eth0 key s:XXXXXXXX". The
> iwconfig output is:
>
>
> eth0 IEEE 802.11b ESSID:"melange" Nickname:"HERMES I"
> Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
> Bit Rate:2 Mb/s Sensitivity=1/3
> Retry limit:4 RTS thrff Fragment thrff
> Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security modepen
> Power Managementff
> Link Quality=40/92 Signal level=-54 dBm Noise level=-94 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> I sanitised the output with 0s and Xs.
>
>> 4) repeat step 2 - if the card is associated, you should see "Access Point: nn:nn:nn:nn:nn:nn"
>
> At this point, everything seems normal. Now I try "dhclient eth0" and it times
> out without getting an ip address. I don't think this is a hardware problem
> since everything works during the debian installer and when I had freebsd
> installed.

I wonder why your wireless card shows up as eth0 (mine is wlan0)? Presumably its
because you used the wireless card to install Debian and the installer gave it
eth0 as default. But the T20 has a built-in ethernet interface. I wonder if
there is some clash here (that occurs when you boot the system) between the two
interfaces. Try running "ifconfig" as root and inspect the output.

In an earlier post you said that you could not ping the AP. You could
double-check that theT20 and the AP are on the same network. I presume that your
AP also provides the DHCP server. You would have to be on the same network to
access it.

To check whether WEP is the problem you could try turning WEP off at the AP
while you conduct tests.

If you are desperate, you could configure the built-in ethernet interface, set
is as the only interface in /etc/network/interfaces and check that everything
works by ethernet cable connection (including WEP). Then you could install the
wireless card again. (This should then appear as wlan0 rather that eth0.)

--
Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, 12 Sep 2007 18:12:02 -0600
Chris Brotherton <chris@protonlab.net> wrote:

> On Wed, Sep 12, 2007 at 10:35:51AM -0400, Celejar wrote:
> [snip]
> >
> > Try the following:
> >
> > 1) unload and reload the driver module
> > 2) check (and post) the iwconfig output
> After unloading, reloading and plugging in the network card, my iwconfig
> output is:

I meant the kernel module; you probably don't need to physically unplug
and replug the adapter for this kind of troubleshooting. No harm
done, though ...

> eth0 IEEE 802.11b ESSID:"" Nickname:"HERMES I"
> Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
> Bit Rate:11 Mb/s Sensitivity=1/3
> Retry limit:4 RTS thrff Fragment thrff
> Encryption keyff
> Power Managementff
> Link Quality=0/92 Signal level=134/153 Noise level=134/153
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> > 3) do ifconfig xxxx up; iwconfig xxxx essid nnnnnnnn
> After these commands, the iwconfig output is:
>
> eth0 IEEE 802.11b ESSID:"melange" Nickname:"HERMES I"
> Mode:Managed Frequency:2.457 GHz Access Point: None
> Bit Rate:2 Mb/s Sensitivity=1/3
> Retry limit:4 RTS thrff Fragment thrff
> Encryption keyff
> Power Managementff
> Link Quality=0/92 Signal level=134/153 Noise level=134/153
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> Notice that the Bit Rate dropped to 2 Mb/s.

The card isn't yet associated; I suppose that's because you're using
WEP.

> My access point uses wep. So I ran "iwconfig eth0 key s:XXXXXXXX". The
> iwconfig output is:
>
>
> eth0 IEEE 802.11b ESSID:"melange" Nickname:"HERMES I"
> Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
> Bit Rate:2 Mb/s Sensitivity=1/3
> Retry limit:4 RTS thrff Fragment thrff
> Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security modepen
> Power Managementff
> Link Quality=40/92 Signal level=-54 dBm Noise level=-94 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> I sanitised the output with 0s and Xs.

I assume you mean that the output now reads 'Access Point: the actual
MAC address of your AP'?

> > 4) repeat step 2 - if the card is associated, you should see "Access Point: nn:nn:nn:nn:nn:nn"
>
> At this point, everything seems normal. Now I try "dhclient eth0" and it times
> out without getting an ip address. I don't think this is a hardware problem
> since everything works during the debian installer and when I had freebsd
> installed.

I would try without WEP and see what happens (deactivate it on the AP
and omit the 'iwconfig eth0 key s:XXXXXXXX' line). Also, if you can
log into the AP (perhaps from another machine), see if it considers
your Debian machine to be associated.

> Any is appreciated.
>
> Thanks,
> Chris.

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, 13 Sep 2007 11:47:58 +0100
Chris Lale <chrislale@untrammelled.co.uk> wrote:


[snip]

> I wonder why your wireless card shows up as eth0 (mine is wlan0)? Presumably its
> because you used the wireless card to install Debian and the installer gave it

It depends on the drivers. My Broadcom 4318 is eth0 when driven by the
native bcm43xx, but ndiswrapper originally brings it up as wlan0 and
then immediately switches it to eth0.

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org