Hi,

Unlike Suse v9.3, where I did have a working Wireless Internet connection, Suse v10 had a different outcome during and after installation. Allthough during install, it recognized all my hardware properly (Dell Inspiron laptop, Intel PRO Wireless 2915 ABG adapter, etc.), it failed when it offered to 'test the Internet connection'. Suse did invite me however to view it's logfiles:

eth1 device: Intel Corporation...
eth1 wlanid-00...
eth1 warning: wpa_supplicant already running on interface
DHCP client is already running on eth1

I checked and rechecked the network card settings but the connection never succeeded. After letting the installaton complete, I wasn't able to use WiFi either.

Does this sound familiar to anyone and if so, where should I look? Thanks for your input.

regards,
Erik Coolen

yes, that sound very familiar. I cannot even start my wifi card, nor activate it by Fn-F2. Is your WiFi LED on ???

Joerg

[QUOTE]Originally posted by jschweden
yes, that sound very familiar. I cannot even start my wifi card, nor activate it by Fn-F2. Is your WiFi LED on ???

Hi Joerg,

I can dual-boot to Win XP and then my card behaves as well as can be expected. But when I reboot to SuSe 10 my WiFi problems resurface. Anyway, my card is active since I can see my neighbour's network in Kinternet..

erik

Hi.

I'm going to go out on a limb here and write what worked for my wireless card. (Intel Centrino)

1. Fire up YaST.
2. Click on Network Devices
3. Click on Network Card
4. Click on your Wireless Card (if it's listed) **
5. Click on delete (yes, we're going to delete it)
6. Click on the Next button
7. Repeat Steps 1 through 3
8. Click on the newly found Wireless card (it should be listed)
9. Click on Edit
10. Add all the entries needed to configure the card. DHCP is probably fine for most. Don't foget the router address.

That should do it. (It did for me anyway.)

Hope this helps.

** If your wireless card is not listed in step 4 above then you might want to fire up the terminal application and then issue the command dmesg | more at the prompt. Look for anything related to why your wireless card is not being seen by SUSE.

Hi rgbrock1,

Thanks for reply, I will boot back to Suse in a minute and try it out. Before that, I just want to add some information that I got when I ran 'iwconfig':

eth0 unassociated ESSID:"trueblue2"
Mode:Managed Frequency=2.462 GHz Access Point: 00:13:10:E6:4E:2D
Bit Rate=0 kb/s Tx-Power=20 dBm
Retry limit:7 RTS thrff Fragment thrff
Encryption key:xxx-xxx Security mode:restricted
Power Managementff
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

As you can see, the only thing that seems out of kelter is the 'unassociated ESSID' passage. No idea just yet how to fix that one. And what's even weirder, Kinternet keeps telling me that I 'succesfully connected' allthough there's no real connection. I cannot PING, cannot use a browser, cannot link up with my router..

erik

Hi again,

Unfortunately, your idea doesn't seem to work for me so I'll just have to keep searching..

thanx again,
erik

There was a thread on this -- you'll have to search for it.

What worked for me was to use the SMP kernel (even on a laptop)

Using the non SMP (default) kernel-- I had the problem where I could ping everything in a network and even ping external addresses like www.bbc.co.uk so long as I hadn't started X but whenever I started X my wireless connection was totally LOST as well as all Network connectivity and I couldn't restart the wireless card.

I could never get the ESSID filled in correctly even if the config file was OK --the smp kernel has this fixed. (10.0 RC1 and Final)


I'm using ndiswrapper with a Linksys (Broadcom chipset) wpc54g card.

Just grab the smp kernel with yast --no need to compile or anything. It's on the CD's / DVD.

works fine.

Tip -- NEVER start in Runlevel 5 when testing --especially wireless. You can find a lot of info on the console before starting X --set runlevel to 3.



Cheers

-K

Are you using KDE or Gnome?

On my Tecra M1 I got it working just fine.

Also, i've installed about 4 times and never can I get the initial test wireless thing to work right.

Hi,

Thanks for your answer. I'm using KDE and so far I've installed SuSe 10 twice. So two more tries to go before I get lucky, eh? )

I still want to try the 'SMP kernel' option, as suggested by 1kyle.

thanx anyway,
erik

it sounds like you are using the OSS version. it doesn't have the wifi drivers in the kernal. I have an IBM A21m and had the same trouble, just d/l'd the GM kernel and install it and configure, now all is well. As for the initial test at install, it always goes to eth0 for some reason wene ath0 is what i use.

Hi,

Thanks for your 'SMP' tip. I grabbed it off the DVD with YAST and rebooted but to no avail, still no WiFi connect. Would ndiswrapper be any help, I wonder? My Intel card is nothing out of the ordinary so I'm not sure if ndiswrapper would be helpful. Thanks anyway..

gr.,
erik

Hi,

Thanks for your reply. Your thought had crossed my mind too so I've tried both the Eval and the OSS version but neither worked. Sigh..

gr.,
erik

Again, this "Link Quality:0 Signal level:0 Noise level:0" seems to be your problem. If you can get a signal from your router, it should associate the card with the router and you'll lose the "unassociated" after eth0. I don't know why you're not getting a signal, but make sure you've reset your router, turn your encryption off, and make sure you're in the same room as it for starters.

Hi,
Thanks for your persistent advice, you're a credit to this forum.. Anyway, when I do a 'iwlist eth1 scan' I get to see all the available networks. Mine and the neighbours.. I guess that would mean I do get a signal, right?

erik

Hi again,

After running a number of 'iwconfig' commands, I get the below 'iwconfig' result:

eth0 unassociated ESSID:"trueblue2" Nickname:"linux"
Mode:Managed Frequency=2.462 GHz Access Point: 00:13:10:E6:4E:2D
Bit Rate=0 kb/s Tx-Power=20 dBm
Retry limit:7 RTS thrff Fragment thrff
Encryption key:xxxxxx Security mode:restricted
Power Managementff
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 no connectivity..

When I then try a connect thru Kinternet, I get a 'connected succesfully' message but still no Internet. And wWhen I do a 'ping 192.168.1.1 (the LinkSys router)', I get a 'network unreachable'.

I notice that
1) the card stays 'unassociated' in iwconfig. I haven't seen a 'associated' messaged yet.
2) I've never seen the little 'lightning' coming out of the Kinternet icon on the Taskbar, if you catch my drift. I remember from v9.3 that it always comes up with that little 'flashy' symbol. I know that symbol indicates an attempt to connect and since I haven't seen it yet, I guess that should tell me someting. Right? Hm.. but what? )

erik