Dear everyone, I wonder if anyone has any experience of getting the wireless eth-card in a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel PRO/Wireless 2200BG. It is recognised by the system as such, and I am able to configure it in Yast without any obvious problems. However, it doesn't get an IP-address. This is in contrast with the same laptop in the same location booting the XP partition, in which case it finds the network, gets an IP and chats away happily. The setup is the same for SuSE and XP: DHCP, named ssid, WEP-ASCII-5char encryption. The following may be relevant version numbers Kernel 2.6.8-24 wireless-tools 27pre26-10 ipw-firmware 3.3 During boot I get the following messages (some of which sound a bit omnious, but I am not certain how serious they are) that I interpret as related to the problem <4>ieee80211_crypt: unsupported module, tainting kernel. ("tainting is bad, right?") <7>ieee80211_crypt: registered algorithm 'NULL' <4>ieee80211: unsupported module, tainting kernel. . . <4>ipw2200: unsupported module, tainting kernel. <6>ipw2200: Intel(R) PRO/Wireless 2200 Network Driver, 0.8 <6>ipw2200: Copyright(c) 2003-2004 Intel Corporation . . <6>eth1: Setting MAC to 00:0e:35:ad:e3:81 <3>ipw2200: Calibration and the later on when trying to connect eth1 device: Intel Corp. PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-id-00:0e:35:ad:e3:81 ERROR: command 'iwconfig eth1 mode Managed' returned Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Operation not supported. eth1 (DHCP) . . . . . no IP address yet... backgrounding. waiting If anyone recognise the problem and has a solution to it I would be for ever grateful. Please also be gentle with me if/when replying. I am a bit of a beginner and don't handle jargon very well. Puss Jesper
Le Mercredi 21 Septembre 2005 19:08, Jesper Andersson a écrit :
Dear everyone,
I wonder if anyone has any experience of getting the wireless eth-card in a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel PRO/Wireless 2200BG. ..... During boot I get the following messages (some of which sound a bit omnious, but I am not certain how serious they are) that I interpret as related to the problem
<4>ieee80211_crypt: unsupported module, tainting kernel. ("tainting is bad, right?") <7>ieee80211_crypt: registered algorithm 'NULL' <4>ieee80211: unsupported module, tainting kernel. . . <4>ipw2200: unsupported module, tainting kernel. <6>ipw2200: Intel(R) PRO/Wireless 2200 Network Driver, 0.8 <6>ipw2200: Copyright(c) 2003-2004 Intel Corporation . .......
If anyone recognise the problem and has a solution to it I would be for ever grateful.
Dear Jesper I tried using SuSE 9.3 on a laptop with the same Intel chips and got the same messages. I posted some questions which werer never answered on this list; and I reverted to SuSE 9.2 which does not recognise the damned wireless thing at all and therefore does not taint the kernel with rotten modules. I have too much work on the moment to make more investigations and hope you will be luickier than I was and get an answer. Perhaps if more people experience the same difficulties one of our wise men will find a solution. Best wishes Paul Ollion
Jesper, See in text. Paul Ollion wrote:
Le Mercredi 21 Septembre 2005 19:08, Jesper Andersson a écrit :
Dear everyone,
I wonder if anyone has any experience of getting the wireless eth-card in a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel PRO/Wireless 2200BG.
.....
During boot I get the following messages (some of which sound a bit omnious, but I am not certain how serious they are) that I interpret as related to the problem
<4>ieee80211_crypt: unsupported module, tainting kernel. ("tainting is bad, right?") <snip> If anyone recognise the problem and has a solution to it I would be for ever grateful.
The problem i have with the D600 and networking is that the wireless card conflicts with the ethernet card if both are on dhcp (getting a ip address from the dns server). The symptom is that i cannot get a ip address (the command 'ifconfig' witll not show an ip address) and that
I have a D600 with the wireless working when using SuSE 9.3 be it a bit flaky. This is due to the fact that intels binary driver is supportedin SuSE 9.3. I tried to do the same when i was using SuSE 9.2 by installing the ipw2200 driver myself but never succeeded. Did not even get the tainted messages you receive. See http://ipw2200.sourceforge.net/ The tainted messages are in some respect good news. your ipw2200 driver is loaded (try with lsmod to find it). On the other hand it means this card can only be run by using a proprietary (no open source) binary driver. So it seems to be working. the routing table is empty (enter the command 'route' and wait forever). The reason seems to be that both will want to create a resolv.conf and routing information and are blocking eachother. The only way i managed to solve this is to enable profiles also known as scpm (enable it in YaST -> System -> Profiles). First remove the definition of the wireless network card in YaST and save this as the default profile. Then delete the normal card and enter the definition of the wireless card and save this as the wireless profile. Note: at the moment this problem forces me even to enable both cards but in the details ection of the card i have to switch the 'other' card to keep switched off. HTH Peter Vollebregt
Hi, On Wed, 21 Sep 2005 20:08:42 +0300 (EEST) "Jesper Andersson" <.> wrote:
Dear everyone,
I wonder if anyone has any experience of getting the wireless eth-card in a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel PRO/Wireless 2200BG. It is recognised by the system as such, and I am able to configure it in Yast without any obvious problems. However, it doesn't get an IP-address. This is in contrast with the same laptop in the same location booting the XP partition, in which case it finds the network, gets an IP and chats away happily. The setup is the same for SuSE and XP: DHCP, named ssid, WEP-ASCII-5char encryption.
I think it doesn't help you too much, but please let me tell you my story in brief. I have SUSE 9.1; a system even doesn't recognizing my ipw2200 wireless stuff of my Acer 803LMiB... I had several hours/days spent with attempting to get it work via diffe- rent methods, but at the end only ONE was successful. In fact I down- loaded and self-compiled three "packages" from http://ipw2200.sourceforge.net/ ; please note the exact version- numbers worked in my case: 1) ieee80211-1.0.3.tgz 2) ipw2200-fw-2.3.tgz 3) ipw2200-1.0.6.tgz To be more precise, I removed the orig. 3x ieee80211*.ko and one single ipw2200.ko kernel module-files, rmmod-ded them and then did "depmod -a". Then I compiled and installed the ieee80211-related stuff; later I added the firmware into /lib/firmware and soft-linked all files to /etc/firmware and in addition to /usr/lib/hotplug/firmware. As next, compiled the driver itself and installed the resulted .ko file manually to its respective place. As last you have to "modprobe ipw2200" and everything should work. I repeat that I'm on SUSE 9.1, where I even don't have firmware in rpm form. Probably that you also have to _remove_ for this kind of manual tries... For more details please don't hesitate to contact me, Pelibali Ps. Don't afraid to experiment a little. I'm also just a hyperactive amateur; from diverse online materials and self-experiences I could manage the above. (+Don't think that 9.1 and 9.2 differ too much.)
Quoting pelibali <pelibali@freemail.hu>:
Hi,
On Wed, 21 Sep 2005 20:08:42 +0300 (EEST) "Jesper Andersson" <.> wrote:
Dear everyone,
I wonder if anyone has any experience of getting the wireless eth-card in a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel PRO/Wireless 2200BG. It is recognised by the system as such, and I am able to configure it in Yast without any obvious problems. However, it doesn't get an IP-address. This is in contrast with the same laptop in the same location booting the XP partition, in which case it finds the network, gets an IP and chats away happily. The setup is the same for SuSE and XP: DHCP, named ssid, WEP-ASCII-5char encryption.
I know I'm not answering your question, but FWIW I have an IBM R52 with the same chipset, and the wireless works flawlessly with SuSE Pro 10. -- _________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business" 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com This email was sent from Reliable Networks of Maine LLC. It may contain information that is privileged and confidential. If you suspect that you were not intended to receive it, please delete it and notify us as soon as possible. Thank you.
On Sunday 19 February 2006 04:37 pm, L. Mark Stone wrote:
Quoting pelibali <pelibali@freemail.hu>:
Hi,
On Wed, 21 Sep 2005 20:08:42 +0300 (EEST)
"Jesper Andersson" <.> wrote:
Dear everyone,
I wonder if anyone has any experience of getting the wireless eth-card in a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel PRO/Wireless 2200BG. It is recognised by the system as such, and I am able to configure it in Yast without any obvious problems. However, it doesn't get an IP-address. This is in contrast with the same laptop in the same location booting the XP partition, in which case it finds the network, gets an IP and chats away happily. The setup is the same for SuSE and XP: DHCP, named ssid, WEP-ASCII-5char encryption.
I know I'm not answering your question, but FWIW I have an IBM R52 with the same chipset, and the wireless works flawlessly with SuSE Pro 10.
Though I doubt ANYTHING works in Wintendo (it is just an illusion), you might want to be sure you're setting up your card for DHCP. Check in Control Center( Yast ) > Network Devices (left pane) > Network Card (right pane) > Intel PRO/Wireless 2200 BG. Look under the bottom panel. You should see that the Device Name is listed, then IP Address assigned using DHCP, then Started Automatically at Boot. If any of those are not correct, you'll need to Edit. Now, if they ARE correct, then you may just need to be sure you're attaching. AFAIK, SUSE doesn't auto-attach to WiFi. At least I've never been able to get it working automatically. To attach, you want to have the KInternet tool running in your system tray. (There's also KWiFiManager, but I have no clue what use it is, other than looking cute. Kind of like the Dallas Cheerleaders.) Right-click on KInternet, and select Wireless Connection. It will list your current connection, which will be false. (Don't know why.) Click the Scan for Wireless Networks tab. If your network isn't listed, then click Refresh. If it still isn't listed, then click Start Active Scan. (For some unknown reason, this works better.) Click on the Name/ESSID item you want and select Connect. Enter your WEP password (You DO have one, Right?) and select OK. You should be attached. Oh, if you're using the more-secure WPA encryption, forget about it. You can't attach. Kind of screwed, but that's what we pay for by having a better OS. HTH!!! -- kai www.perfectreign.com linux - genuine windows replacement part
On 2/19/06, kai <kai@perfectreign.com> wrote:
Oh, if you're using the more-secure WPA encryption, forget about it. You can't attach. Kind of screwed, but that's what we pay for by having a better OS.
Seriously? Linux can't use WPA? Or, SUSE can't? Why, pray tell? P
participants (7)
-
Jesper Andersson -
kai -
L. Mark Stone -
Paul Ollion -
pelibali -
Peter Van Lone -
Peter Vollebregt