Builtin WLAN not found during installation although not a restricted driver

[Martin Wildam]

Binary package hint: installation-report

During installation of Maverick beta a WLAN window is displayed trying to let me choose a WLAN for network connection.
However, the list is empty so I assume that the driver for my WLAN is not found. After installation is finished on the other hand the WLAN is available without the need of installing any restricted driver.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: installation-report 2.39ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Wed Sep 8 20:39:17 2010
Dependencies:

EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: installation-report

[Martin Wildam (mwildam)]

Here is my lshw run with normal user permissions:

[Martin Wildam (mwildam)]

This is my wlan network card:
           *-network
                description: Wireless interface
                product: WiFi Link 5100
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:0c:00.0
                logical name: wlan0
                version: 00
                serial: 00:22:fb:52:22:68
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=iwlagn

Because of Bug #633548 I can't send you the lshw output using sudo.

[Martin Wildam (mwildam)]

Hoppla - there was missing a little rest:
configuration: broadcast=yes driver=iwlagn driverversion=2.6.35-19-generic firmware=8.24.2.12 ip=10.0.0.6 latency=0 multicast=yes wireless=IEEE 802.11abgn
                resources: irq:45 memory:f69fe000-f69fffff

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 633551

and any other logs that are relevant for this particular issue.

[Martin Wildam (mwildam)]

I cannot find out any more what machine that was so many years ago and I am pretty sure that I don't have access to that hardware any more. So cannot retest. I would say, it is obsolete now.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]