I am running Suse 10.1 and i have upgraded the kernel to 2.6.17,

Linux linux-ui2z 2.6.17.11-jen33-smp #1 SMP Thu Aug 24 16:14:58 CEST 2006 i686 i686 i386 GNU/Linux

now i am trying to setup the wireless network card on my laptop (HP ZV5000 series (5325ca to be exact)). the good news is the new kernel 2.6.17 has the native driver for the card which is broadcom and here is the result of iwconfig, just in case it might come handy:

eth1 IEEE 802.11b/g ESSIDff/any Nickname:"Broadcom 4306"
Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
RTS thrff Fragment thrff
Encryption keyff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

now i went to yast, (after updating the kernel) and the wireless card was identifyed by the OS, so no more ndiswrapper, but the question is how to get it to work. the network manager which i click on it (right lower corner, the two little monitors) gives me the options of : connect to other wireless network or create a wireless network, so it knows that the card is there but i don't see the available networks and the light on the wireless button does not come on. when i just type in the essid, it seems that it is looking for something, but no luck.

here is the result of the scan command:

# sudo /usr/sbin/iwlist eth1 scan

Warning: Driver for device eth1 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...

eth1 Interface doesn't support scanning : No such device

so no scanning available either. i don't know what to do, or what the next step is... i am stuck, anyidea what is missing?

here is the result of lspci command:

# lspci

00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge (rev 02)
00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge
00:13.0 USB Controller: ATI Technologies Inc OHCI USB Controller #1 (rev 01)
00:13.1 USB Controller: ATI Technologies Inc OHCI USB Controller #2 (rev 01)
00:14.0 SMBus: ATI Technologies Inc ATI SMBus (rev 16)
00:14.1 IDE interface: ATI Technologies Inc ATI Dual Channel Bus Master PCI IDE Controller
00:14.3 ISA bridge: ATI Technologies Inc Unknown device 434c
00:14.4 PCI bridge: ATI Technologies Inc Unknown device 4342
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller
00:14.6 Modem: ATI Technologies Inc IXP AC'97 Modem (rev 01)
01:05.0 VGA compatible controller: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP]
02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) <---- the wireless card BCM4306 HERE!!!
02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01)
02:07.0 USB Controller: NEC Corporation USB (rev 43)
02:07.1 USB Controller: NEC Corporation USB (rev 43)
02:07.2 USB Controller: NEC Corporation USB 2.0 (rev 04)

here is the result of lspci-n scan as well....

# lspci -n

00:00.0 Class 0600: 1002:5833 (rev 02)
00:01.0 Class 0604: 1002:5838
00:13.0 Class 0c03: 1002:4347 (rev 01)
00:13.1 Class 0c03: 1002:4348 (rev 01)
00:14.0 Class 0c05: 1002:4353 (rev 16)
00:14.1 Class 0101: 1002:4349
00:14.3 Class 0601: 1002:434c
00:14.4 Class 0604: 1002:4342
00:14.5 Class 0401: 1002:4341
00:14.6 Class 0703: 1002:434d (rev 01)
01:05.0 Class 0300: 1002:5835
02:00.0 Class 0c00: 104c:8026
02:02.0 Class 0280: 14e4:4320 (rev 03)
02:03.0 Class 0200: 10ec:8139 (rev 10)
02:04.0 Class 0607: 104c:ac54 (rev 01)
02:04.1 Class 0607: 104c:ac54 (rev 01)
02:04.2 Class 0880: 104c:8201 (rev 01)
02:07.0 Class 0c03: 1033:0035 (rev 43)
02:07.1 Class 0c03: 1033:0035 (rev 43)
02:07.2 Class 0c03: 1033:00e0 (rev 04)

I don't know whether or not SuSE 10.X included the hwinfo utility (it was in earlier versions). If you have it, run 'hwinfo --netcard'.

Look for the following in the output:
Model: should correctly identify the network card.
Driver: should tell you which driver is required.
Device file: should tell you if it's eth0, eth1, or something else.
Driver status: is the driver active.
Driver Activation Cmd: the command to run to load the driver.

If you still don't have internet after checking those things, run 'dhcpcd eth0' (or whatever the Device File lists as the correct eth number).

Note: on other distros, it may be dhcpd, but SuSE have set up dhcpcd.

so based on the command, the driver is there, it is active... and i did run the dhcpcd eth1 but i doesn't complain, just goes to the next command line and that is it..... i was trying to update the network manager to the latest version 0.6.4 to see if that helps, but in the installation it is complaining that i am missing some packages, which i trid to find the rpm packages but no luck... the package is libdbus-1.so.3 and i thought may be its not working becuase i don't have it... any idea? and thanks for the network command, but it doesn't change any parameters thought right? it displays them ? i don't know how that works ....

# hwinfo --netcard

20: PCI 202.0: 0200 Ethernet controller
[Created at pci.300]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4320
Unique ID: JNkJ._LuIAhxm4a3
Parent ID: qscc.S+4MMSCCLf5
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:02:02.0
SysFS BusID: 0000:02:02.0
Hardware Class: network
Model: "Hewlett-Packard Company nx9500 Built-in Wireless"
Vendor: pci 0x14e4 "Broadcom"
Device: pci 0x4320 "BCM4306 802.11b/g Wireless LAN Controller"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x12f4 "nx9500 Built-in Wireless"
Revision: 0x03
Driver: "bcm43xx"
Device File: eth1
Features: WLAN
Memory Range: 0xd0204000-0xd0205fff (rw,non-prefetchable)
IRQ: 201 (no events)
HW Address: 00:90:4b:97:dd:ac
Link detected: no
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
WLAN frequencies: 2.412e-05 2.417e-05 2.422e-05 2.427e-05 2.432e-05 2.437e-05 2.442e-05 2.447e-05 2.452e-05 2.457e-05 2.462e-05 2.467e-05 2.472e-05 2.484e-05
WLAN bitrates: 1.2e-05 1.8e-05 2.4e-05 3.6e-05 4.8e-05 7.2e-05 9.6e-05 0.000108 2e-06 4e-06 1.1e-05 2.2e-05
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap wpa-leap
Module Alias: "pci:v000014E4d00004320sv0000103Csd000012F4bc02sc80i00"
Driver Info #0:
Driver Status: bcm43xx is active
Driver Activation Cmd: "modprobe bcm43xx"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #15 (PCI bridge)

21: PCI 203.0: 0200 Ethernet controller
[Created at pci.300]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
Unique ID: rBUF.hFfOY6n6P69
Parent ID: qscc.S+4MMSCCLf5
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:02:03.0
SysFS BusID: 0000:02:03.0
Hardware Class: network
Model: "Hewlett-Packard Company RTL-8139/8139C/8139C+"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8139 "RTL-8139/8139C/8139C+"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x006b
Revision: 0x10
Driver: "8139too"
Device File: eth0
I/O Ports: 0xa000-0xafff (rw)
Memory Range: 0xd0208800-0xd02088ff (rw,non-prefetchable)
IRQ: 193 (542 events)
HW Address: 00:0f:b0:6b:f7:24
Link detected: yes
Module Alias: "pci:v000010ECd00008139sv0000103Csd0000006Bbc02sc00i00"
Driver Info #0:
Driver Status: 8139too is active
Driver Activation Cmd: "modprobe 8139too"
Driver Info #1:
Driver Status: 8139cp is not active
Driver Activation Cmd: "modprobe 8139cp"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #15 (PCI bridge)

Definitely something odd going on. Look at the two groups of info from 'hwinfo --netcard'.

In the first group, 'Link detected = no' for eth1; Link detected = yes for eth0.

I can only suggest you try your netcard through eth0.

well eth0 is my NIC card wired , which i have access to , and eth 1 is the wireless so on the two group the first one is my wireless and the second one is wired, and as it mentions , link is detected for eth0 ... so having set that, u r saying remove the wired nic card and install the wireless one as eth 0 ? i personally don't think that is the case, but let me know ....