Ubuntu 10.10 installer no longer detects BCM5906M ethernet adapter

[MegaGumbo]

When running the netboot installation of Ubuntu 10.10 (Maverick Meerkat) on my Lenovo S10e, the installer no longer detects the onboard ethernet (LAN) adapter (BCM5906M). Usually, in the text installer, the (LAN) network adapter I use to connect to my network is detected and DHCP configuration takers place. Now, as of Ubuntu 10.10, the installer stops any further steps as it no longer detects the ethernet adapter and complains about a missing network adapter, rendering any installation efforts via TFTP useless.

[Book 'em Dano (heymrdjd)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

[MegaGumbo (n-haedecke)]

Pleasure to help. Also, I'd really like to provide the missing info (lspci, uname etc.) and am able to run the neccessary commands on the shell once the installer starts. But unfortunately, neither USB nor internal storage devices are available at that early stage of installation. Can you give me any help on getting the output off the ramdisk and onto any USB / internal device while in that early stage of the installation process?

[Book 'em Dano (heymrdjd)]

Are you using a netboot mini.iso for Maverick? Do you have any live CD's available? If so, you could boot up with the live CD, open a terminal and perform the following:

* plug in an flash drive

* watch the kernel messages with "dmesg | tail" and look for the partition on the stick, for instance /dev/sdb1 or check with ls /dev/sd* if you can recognize it

* mkdir /tmp/stick

* mount /dev/sdb1 /tmp/stick

* cp uname -a > /tmp/stick/uname-a.log

* cat /proc/version_signature > /tmp/stick/proc_version_signature.log

* sudo lspci -vvnn > /tmp/stick/lspci-vvnn.log (those are 2 v's not a w)

* dmesg > /tmp/stick/dmesg.log

* umount /tmp/stick

* unplug the flash drive and attach the separate files to the bug report

[MegaGumbo (n-haedecke)]

Lenovo S10e dmesg

[MegaGumbo (n-haedecke)]

lspci-vvnn.log

[MegaGumbo (n-haedecke)]

uname-a.log

[MegaGumbo (n-haedecke)]

proc_version_signature.log

[MegaGumbo (n-haedecke)]

Thanks for the instructions. I've provided all missing files.

[penalvch (penalvch)]

MegaGumbo, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[Launchpad Janitor (janitor)]

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