[opensuse] Fwd: broadcom (??) wireless on dell latitude D810

first try bounced. Here goes the second try

---------- Forwarded message ----------
From: Peter Van Lone <petervl@xxxxxxxxx>
Date: May 7, 2007 4:11 PM
Subject: broadcom (??) wireless on dell latitude D810
To: Open SuSE mail list <opensuse@xxxxxxxxxxxx>


SLED10/SUSE10.1

No wireless adapter appears in network manager, and none shows when I
do an ifconfig. However, in YAST I see two hardware detected (see
below).

What do I have to do to get this working? What module should be
loaded, how do I understand what YAST is telling me?

From Yast/NetworkDevices/Network Card:

the "name" is:

"Wireless LAN cards using direct PCI Interface". When I
edit/Advanced/Hardware Details is says:

"configuration name: wlan0"
"Hardware name: static-0"
"Kernel Module"
"Hardware Configuration Name: static-0"
"Module Name: orinoco_pci"

from the yast hardware report:

29: PCI 303.0: 0280 Network controller
[Created at pci.305]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4320
Unique ID: 5FRj.ts7Hp0QB3M1
Parent ID: 6NW+.InKz0bgid89
SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:03.0
SysFS BusID: 0000:03:03.0
Hardware Class: network
Model: "Dell Wireless 1350 WLAN Mini-PCI Card"
Vendor: pci 0x14e4 "Broadcom"
Device: pci 0x4320 "BCM4306 802.11b/g Wireless LAN Controller"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x0003 "Wireless 1350 WLAN Mini-PCI Card"
Revision: 0x03
Memory Range: 0xdfbfe000-0xdfbfffff (rw,non-prefetchable)
IRQ: 10 (no events)
Module Alias: "pci:v000014E4d00004320sv00001028sd00000003bc02sc80i00"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #20 (PCI bridge)



63: None 00.0: 10781 Network Interface
[Created at net.115]
Unique ID: wl2P.nfEXJulusj6
SysFS ID: /class/net/sit0
Hardware Class: network interface
Model: "Network Interface"
Device File: sit0
Config Status: cfg=no, avail=yes, need=no, active=unknown





--
"Do not be idolatrous or bound to any doctrine, theory or ideology,
even Buddhist ones. All systems of thought are guiding means, not
absolute truth."
Thich Nhat Hanh, Vietnamese monk.
http://www.seaox.com/thich.html

www.the-brights.net


--
"Do not be idolatrous or bound to any doctrine, theory or ideology,
even Buddhist ones. All systems of thought are guiding means, not
absolute truth."
Thich Nhat Hanh, Vietnamese monk.
http://www.seaox.com/thich.html

www.the-brights.net
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: setting up WiFi adapter (Broadcom BCM4321 14e4:4328 chipset) in latest version of Debian
    ... there is an LED on front for the wireless, ... my pci wifi-chipset should be supported by the 'b43' driver module. ... Using the Wicd network manager applet in Gnome shows: ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Built-in Network Port not detected in Debian
    ... recognized all hardware components including the built in network chipset. ... and none is using IRQ 10 or 11. ... PCI: Discovered primary peer bus 02 ... iface eth0 inet static ...
    (Debian-User)
  • Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
    ... 2.6.23-rc1 I have trouble with my network connection. ... # Bus options (PCI, PCMCIA, EISA, MCA, ISA) ... # PCCARD support ... # Generic Driver Options ...
    (Linux-Kernel)
  • wireless error on AMD64 Lenny
    ... I've been stuck for a few days trying to connect my computer to a wireless ... wireless network controller ... The PCI network controller is a RaLink RT2561/RT61 (I previously used this ...
    (Debian-User)
  • Re: [PATCH RFC v2] net: add PCINet driver
    ... PCI bus as its transport mechanism. ... wait for me to get a driver for your platform, but I hope we can join ... particularly nice to have the network unit grab that of_device. ... I tried to keep the network and uart as seperate as possible ...
    (Linux-Kernel)