Bug 148235

Summary:	Network Manager does not recognize IPW2200 or BCM4401
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Thomas Herzog <thomas.herzog>
Component:	Network	Assignee:	Robert Love <rml>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 3
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Thomas Herzog 2006-02-04 18:00:16 UTC

Hi, I configured my network adapters to use Network Manager in Yast.

However, neither my Centrino IPW2200BG nor my onboard ALI/Broadcom BCM4401 show up in its menu. It says "No network adapters found".

IPW2200BG firmware is in place. when configured "traditional", both adapters work fine as they did in 10.0.

Hardware:

Acer TM4001 WLMI (same hardware can be found in TM4500, TM2300 and Extensa3000 series, as these all use the same barebone).

When you need logfile output, simply ask, I can provide the necessary information.

Comment 1 Christian Boltz 2006-02-04 21:28:45 UTC

Just to exclude the most obvious bugs:
- did you install the kernel-*-nongpl package (from ftp.suse.com)?
- are the required kernel modules loaded? Check with lsmod.

Comment 2 Thomas Herzog 2006-02-05 09:12:17 UTC

What exactly would the kernel-*-nongpl package provide for the NetworkManager? As I said, using ifuo/ifdown both my IPW2200BG WLAN and BCM4401 ethernet are working well.

The kernel modules are loaded when using NetworkManager.

In fact, when using NetworkManager, both interfaces are activated (showing up with ifconfig), yet not DHCP started on them, they are unconfigured but "up".

Comment 3 Thomas Herzog 2006-02-05 09:19:14 UTC

öhm, there seems to be no "kernel-*-nongpl" package on ftp.suse.com/pub/suse/i386/10.1/inst-source-extra

Comment 4 Robert Love 2006-02-06 16:14:20 UTC

NM simply enumerates the network devices dynamically that HAL sees.  So the issue is whether HAL detects your network devices.

What is the output of

    $ hal-device | grep "net\.interface ="

?

If you do not see your devices, I don't think that the problem is with HAL, but that your modules are not loaded or not associating with an interface.

If you do see the device, try restarting NM

    % /etc/init.d/network restart

Does the applet still not see the devices?

Thank you!

Comment 5 Thomas Herzog 2006-02-08 18:43:37 UTC

Sorry to have bothered you, but I just realized that I was actually NOT on beta3, this box was running a beta2 which I just happened to have downloaded a day before the beta3 release.

On beta3 I installed ipw-firmware-6-2.rpm and ALL IS WELL AND ROCKING!