[opensuse] broadcom (??) wireless on dell latitude D810
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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
first try bounced. Here goes the second try
---------- Forwarded message ----------
From: Peter Van Lone
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Yeah, I had same problem. Install "ndiswrapper" and then copy all ".inf" files (and maybe ".sys" files also) from windows driver. Follow "ndiswrapper" to install driver from Windows drivers and your wireless neteork will then work like a charm! D. Peter Van Lone wrote:
first try bounced. Here goes the second try
---------- Forwarded message ---------- From: Peter Van Lone
Date: May 7, 2007 4:11 PM Subject: broadcom (??) wireless on dell latitude D810 To: Open SuSE mail list 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
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 5/7/07, Danesh Daroui
Yeah, I had same problem. Install "ndiswrapper" and then copy all ".inf" files (and maybe ".sys" files also) from windows driver. Follow "ndiswrapper" to install driver from Windows drivers and your wireless neteork will then work like a charm!
OK, so ndiswrapper should work, huh? This is a freinds laptop ... he says he followed a TID from Novell for using ndiswrapper, and it still did not work. Can I ask WHERE the *.inf and *.sys files should be copied to? Also, do we have to specifiy a particular module in YAST? Thanx for the help! Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Do you have a driver CD for Windows? If yes, you will find a relevant folder which contains driver files for your wireless card. There you will fined .inf and .sys files. If you have not such CD you can download drivers from Broadcom web site. Once you install "ndiswrapper" (you should compile it) and run it it will show you how to install a driver. When installation is done ti will be loaded at boot time and you will not need to do anything else. D. Peter Van Lone wrote:
On 5/7/07, Danesh Daroui
wrote: Yeah, I had same problem. Install "ndiswrapper" and then copy all ".inf" files (and maybe ".sys" files also) from windows driver. Follow "ndiswrapper" to install driver from Windows drivers and your wireless neteork will then work like a charm!
OK, so ndiswrapper should work, huh?
This is a freinds laptop ... he says he followed a TID from Novell for using ndiswrapper, and it still did not work.
Can I ask WHERE the *.inf and *.sys files should be copied to? Also, do we have to specifiy a particular module in YAST?
Thanx for the help!
Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Danesh Daroui wrote:
Yeah, I had same problem. Install "ndiswrapper" and then copy all ".inf" files (and maybe ".sys" files also) from windows driver. Follow "ndiswrapper" to install driver from Windows drivers and your wireless neteork will then work like a charm!
D.
If you go this route, I'd be sure that ndiswrapper gets loaded upon boot. (Yast2->System->/etc/sysconfig editor->System->Kernel->MODULES_LOADED_ON_BOOT has "ndiswrapper") -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Danesh Daroui
-
Peter Van Lone
-
Pueblo Native