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

Quoting pelibali :

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 2/19/06, kai 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