[SOLVED] Intel WiFI Link 100 Series

willysr · 11-13-2009, 05:42 AM

Hello again,

I had Asus UL80vt which uses Intel WiFI Link 100 Series[1]. The default kernel on Slackware (2.6.29.6) didn't recognize this chipset (yet), so i upgraded to 2.6.31.6 and it's working as it's detected as wlan0 when i used iwconfig.

The problem now is that i can't use wicd nor command line to scan the network. On my previous laptop, i only need to run

Code:

iwlist eth1 scan

and it will scan the available wireless networking, but on this new one, it says the device does not support scanning.

Any recommendation to fix this problem?

[1]: http://cateee.net/lkddb/web-lkddb/IWLWIFI.html

slackd · 11-13-2009, 09:18 AM

not sure but you could try this:

edit inline:

Code:

/etc/rc.d/rc.inet1.conf

from:

Code:

WLAN_WPADRIVER[4]="ndiswrapper"

to:

Code:

WLAN_WPADRIVER[1]="wext"

onebuck · 11-13-2009, 09:22 AM

Hi,

Quote:

Originally Posted by willysr

Hello again,

I had Asus UL80vt which uses Intel WiFI Link 100 Series[1]. The default kernel on Slackware (2.6.29.6) didn't recognize this chipset (yet), so i upgraded to 2.6.31.6 and it's working as it's detected as wlan0 when i used iwconfig.

The problem now is that i can't use wicd nor command line to scan the network. On my previous laptop, i only need to run

Code:

iwlist eth1 scan

and it will scan the available wireless networking, but on this new one, it says the device does not support scanning.

Any recommendation to fix this problem?

[1]: http://cateee.net/lkddb/web-lkddb/IWLWIFI.html

You state that the device is recognized as 'wlan0'. So why would you issue the 'iwlist eth1 scan' instead of 'iwist wlan0 scan'?

Check your module for the device with lsmod.

willysr · 11-13-2009, 04:16 PM

Quote:

Originally Posted by onebuck

Hi,

You state that the device is recognized as 'wlan0'. So why would you issue the 'iwlist eth1 scan' instead of 'iwist wlan0 scan'?

Check your module for the device with lsmod.

yeah, i have changed that into iwlist wlan0 scan, but still the problem persist

willysr · 11-14-2009, 09:43 AM

solved by downloading the correct microcode for this series and put it on /lib/firmware

tbre · 01-07-2010, 04:06 PM

Quote:

Originally Posted by willysr

solved by downloading the correct microcode for this series and put it on /lib/firmware

It seems I might have the same problem. Can you tell me where to find the correct microcode?

onebuck · 01-07-2010, 04:41 PM

Hi,

Quote:

Originally Posted by tbre

It seems I might have the same problem. Can you tell me where to find the correct microcode?

You hardware is the same?

I suggest that you start a separate thread with details of your hardware, distribution and kernel. What you have done to solve the issue along with any other relative information.

'How to Ask Questions the Smart Way' is a great link to aid you in forming your question/thread.