Hi all!
I tried to use CentOS5 on an IBM Thinkpad R52 which has an Intel PRO/Wireless 2915ABG Mini-PCI Adapter installed.
I downloaded the firmware from the DAG-Repo (afaik 3.0.0) and added a "alias eth1 ipw2200" to modules.conf. After the module was loaded successfully (including the firmware) I was able to configure the card.
For simplicity I didn't use any encryption. My access point as well is not using any encryption.
I tried to use DHCP, but the card didn't get assigned to any IP address. So I used the manual configuration which seemed to work fine during startup. But unfortunately not network connection could be made. So no ICMP ping packets where reaching the destination.
Using the iwconfig command I could see my SSID from the access point. Playing around with some values didn't have any success.
So I tried using FC8- and it worked fine with fixed address settings. As well as OpenSuSE 10.2.
Anyone an idea what's going wrong here?
Christian Volker
Technical Support Engineer
On Nov 12, 2007 11:02 AM, Christian Volker cvolker@vmware.com wrote:
Hi all!
I tried to use CentOS5 on an IBM Thinkpad R52 which has an Intel PRO/Wireless 2915ABG Mini-PCI Adapter installed.
I downloaded the firmware from the DAG-Repo (afaik 3.0.0) and added a "alias eth1 ipw2200" to modules.conf. After the module was loaded successfully (including the firmware) I was able to configure the card.
For simplicity I didn't use any encryption. My access point as well is not using any encryption.
I tried to use DHCP, but the card didn't get assigned to any IP address. So I used the manual configuration which seemed to work fine during startup. But unfortunately not network connection could be made. So no ICMP ping packets where reaching the destination.
Using the iwconfig command I could see my SSID from the access point. Playing around with some values didn't have any success.
So I tried using FC8- and it worked fine with fixed address settings. As well as OpenSuSE 10.2.
can you compare the iwconfig output on centos5 and FC8 ?
Your was already installed when you installed centos5 ? And for FC8 ?
Can you try to install a FC8 kernel, if you don't suffer dependency problem ? (or with a FC7 kernel)
If static IP is working, are you sure your DHCP is working on the wireless side ?
Regards
Anyone an idea what's going wrong here?
Christian Volker
Technical Support Engineer
Parnell House, Barrack Square, Ballincollig, Co. Cork, Ireland
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yohoo!
I tried to use CentOS5 on an IBM Thinkpad R52 which has an Intel
PRO/Wireless
2915ABG Mini-PCI Adapter installed.
I downloaded the firmware from the DAG-Repo (afaik 3.0.0) and added a
"alias
eth1 ipw2200" to modules.conf. After the module was loaded successfully (including the firmware) I was able to configure the card.
can you compare the iwconfig output on centos5 and FC8 ?
Not in the next two weeks. Sorry for that. As far as I remember it was the same. And I compared the values with the ones stored in /etc/sysconfig/networking/...ifup-eth1
Your was already installed when you installed centos5 ? And for FC8 ?
What do you mean? If the card was already installed? Yes it was. And on all tests it was a fresh installation.
Can you try to install a FC8 kernel, if you don't suffer dependency problem ? (or with a FC7 kernel)
I can try this as well, but not within the next two weeks. So you're assuming it's related to the kernel? On the OpenSuSE it's kernel 2.6.18.8-0.7-default, which seems to be nearly the same as on CentOS5 2.6.18-8.1.15.el5. So I don't believe it will be fixed with a newer kernel.
If static IP is working, are you sure your DHCP is working on the
wireless side ? Yes, I am sure. Another (Windows) laptop is working fine with DHCP in the same WLAN.
Looking forward to hearing from you.
Christian Volker Technical Support Engineer
---------------------------------------- Ballincollig, Co. Cork Ireland
I tried to use DHCP, but the card didn't get assigned to any IP address. So I used the manual configuration which seemed to work fine during startup. But unfortunately not network connection could be made. So no ICMP ping packets where reaching the destination.
I have had a similar experience. After your interface starts, check to see if dhclient is running. It seems that for some reason, even though I have BOOTPROTO=dhcp in the interface configuration file, it doesn't get an address, but if I run dhclient eth1 it gets an address immediately. I differ in the fact that I am using encryption, and am getting my feet wet with wpa_supplicant .. which could be part of my issue, as encryption would have to be finished setting up before I could use that link to get an address.
Barry
Yohoo!
I tried to use DHCP, but the card didn't get assigned to any IP address.
So I
used the manual configuration which seemed to work fine during startup.
But
unfortunately not network connection could be made. So no ICMP ping
packets
where reaching the destination.
I have had a similar experience. After your interface starts, check to see if dhclient is running. It seems that for some reason, even though I have BOOTPROTO=dhcp in the interface configuration file, it doesn't get an address, but if I run dhclient eth1 it gets an address immediately.
Even when I configure it manually, I don't get any connectivity. So it doesn't seem to be related to DHCP here.
But it could be related to the DHCP issue I'm seeing on FC8 and OpenSuSE10.2 Thanks for the hint.
So you have an ipw2200 running in CentOS5 without any issues? How did you do this? ;)
Looking forward to hearing from you.
Christian Volker Technical Support Engineer
---------------------------------------- Ballincollig, Co. Cork Ireland
On Mon, 12 Nov 2007, Christian Volker wrote:
I tried to use DHCP, but the card didn't get assigned to any IP address.
So I
used the manual configuration which seemed to work fine during startup.
But
unfortunately not network connection could be made. So no ICMP ping
packets
where reaching the destination.
I have had a similar experience. After your interface starts, check to see if dhclient is running. It seems that for some reason, even though I have BOOTPROTO=dhcp in the interface configuration file, it doesn't get an address, but if I run dhclient eth1 it gets an address immediately.
Even when I configure it manually, I don't get any connectivity. So it doesn't seem to be related to DHCP here.
But it could be related to the DHCP issue I'm seeing on FC8 and OpenSuSE10.2 Thanks for the hint.
So you have an ipw2200 running in CentOS5 without any issues? How did you do this? ;)
I have an ipw2200 as well in my Thinkpad T43.
I would suggest using NetworkManager instead of messing with iwconfig.
Do this:
service NetworkManager restart chkconfig NetworkManager on
and then you should see a new applet-icon in Gnome. (if not, run nm-applet as user)
NetworkManager works a bit like windows, it will tell you when it connects and disconnects (also for wired) and you can easily select a wireless nework and provide keys.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Nov 12, 2007 at 07:01:05AM -0800, Christian Volker wrote:
So you have an ipw2200 running in CentOS5 without any issues? How did you do this? ;)
I have one. I didn't do anything special here. It just works, but it is a 2200BG chip, not the one you have.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-
Alain Spineux -
Barry Brimer -
Christian Volker -
Dag Wieers -
Rodrigo Barbosa