Intel WiFi Link 100 doesn't work

Asked by Andrei Sosnin

I'm using Ubuntu 9.04 on an Acer Aspire 1410 RED laptop with an Intel WiFi Link 100 wireless LAN card.

I would like to ask, if this card is known to work on Linux and in Ubuntu in particular? I've tried several proposed solutions after searching the net, but to no avail.

I've described the problem in more detail here:

http://ubuntuforums.org/showthread.php?p=8071538

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Andrei Sosnin
Solved:
Last query:
Last reply:
Revision history for this message
Andrei Sosnin (deemoowoor) said :
#1

I copy my message from Ubuntu Forums here just in case:

A little Googling led me to a page, where I found out that the driver for this wireless card is "iwlagn", and that I needed firmware for this card to work. I've downloaded iwlwifi-1000-ucode-128.50.3.1.tgz firmware archive from http://www.intellinuxwireless.org/?n=Downloads and extracted it to /lib/kernel/firmware or something like that (dmesg showed that driver module did find the firmware there, but I would then basically get the same issue, as in the following bug: https://bugs.launchpad.net/ubuntu/+s...ux/+bug/439285).

It doesn't work in Karmic's 2.6.31-11, too, according to the above mentioned bug.

Also in that bug report, there are two options reported:

1. Install linux-backports-modules for the kernel in use
2. Install linux-image-2.6.32 from http://kernel.ubuntu.com/~kernel-ppa/mainline

I tried both, with little overall success. First, linux-backports-modules for 2.6.28-11 would not work. It would complain about iwlagn not being able to find EEPROM on the wifi card. (I'm currently away from that laptop, so cannot give you any actual logs, I'll add them later today).

Second option is actually moderately successful -- the card is being correctly detected and even WiFi card's LED is lit up! But I could not connect to my AP to get an IP address using DHCP -- which is a problem I'd leave to be solved later.

Because there's another issue with 2.6.32: for some reason with v2.6.32-RC1 kernel from the above mentioned link, it would not load GNOME. It manages to load XOrg server until black screen with mouse pointer appears and then it stops. I can't change to a console using any of the CTRL+ALT+F1 ... F6 buttons, I can't kill (restart) X using CTRL+ALT+BACKSPACE. Only hard reboot helps.

The video card is Intel GMA 4500 MHD.

I tried to see the X.0.log, dmesg, everything, but it would be almost completely identical to the logs of a successful load of 2.6.28-11, except for timestamps and kernel version, of course, without any errors or warnings... Maybe someone of you knows of any known compatibility issues of Jaunty with that newer kernel?

I can see, that I could try and install the 9.10 Karmic Koala Beta, which has a slightly newer kernel than Jaunty and then install the linux-backports-modules for 2.6.31 on to that...

I'd like to know if anyone had any similar issues (with Acer Aspire 1410 RED, or at least with the WiFi Link 100 wireless LAN card) and if they did, maybe they could point me to a possible solution or lack thereof? Let's investigate this together, because I think my head will explode soon from all these problems...

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#2

Can you provide the output of:

sudo lshw -C network

Thanks

Revision history for this message
Andrei Sosnin (deemoowoor) said :
#3

  *-network UNCLAIMED
       description: Ethernet controller
       product: Attansic Technology Corp.
       vendor: Attansic Technology Corp.
       physical id: 0
       bus info: pci@0000:01:00.0
       version: c0
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vpd bus_master cap_list
       configuration: latency=0
  *-network UNCLAIMED
       description: Network controller
       product: WiFi Link 100 Series
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list
       configuration: latency=0
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: 62:1a:50:e7:dd:b1
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

Revision history for this message
Andrei Sosnin (deemoowoor) said :
#4

Here's also lspci output, just in case:

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 Ethernet controller: Attansic Technology Corp. Device 1063 (rev c0)
02:00.0 Network controller: Intel Corporation WiFi Link 100 Series

Revision history for this message
Andrei Sosnin (deemoowoor) said :
#5

The lshw output is when I used 2.6.28-11 from Jaunty Jackalope. I'm going to follow the example of tudalex from Ubuntu Forums:

http://ubuntuforums.org/showpost.php?p=8075346&postcount=6

and upgrade to Karmic Koala 9.10 with 2.6.31-12 kernel. Maybe it will help me too?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#6

I'd go for this too:

http://dtbaker.com.au/random-bits/ubuntu---ethernet-controller-attansic-technology-corp.-device-1063-rev-c0-.html

You will need to compile the driver if you change kernel so keep the source handy.

Revision history for this message
Andrei Sosnin (deemoowoor) said :
#7

This is the wired LAN driver. It's not a priority for me right now, but I'll do it after I get WiFi to work.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#8

A little Googling led me to a page, where I found out that the driver for this wireless card is "iwlagn", and that I needed firmware for this card to work. I've downloaded iwlwifi-1000-ucode-128.50.3.1.tgz firmware archive from http://www.intellinuxwireless.org/?n=Downloads and extracted it to /lib/kernel/firmware or something like that (dmesg showed that driver module did find the firmware there, but I would then basically get the same issue, as in the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/439285).

From:
http://ubuntuforums.org/showthread.php?t=1284851

Revision history for this message
Andrei Sosnin (deemoowoor) said :
#9

Yes, this is my post. :)

Anyway, installing Karmic Koala 9.10 with an updated 2.6.31-12 kernel image solved the problem. WiFi works now.

But there is seems to be regression in Karmic Koala: bluetooth doesn't work anymore, although it used to in Jaunty Jackalope's 2.6.28-11. I'll try to hunt down the problem and if it is indeed a regression in kernel, will file a bug about it.