[opensuse] Wireless Card
Hi all, I have recently installed OpenSuse 10.2 and as I expected I have problem with my wireless card, however OpenSuse has act more efficient than Ubuntu so far. It actually detects my card but I can not connect to my wireless network. I use a HP Pavilion laptop which has a built-in wireless card. It also has a light which will be on if the card is active. This light is always off on OpenSuse. So I decided to install the Windows drivers using ndiswrapper, but it needs the kernel source. In OpenSuse the kernel folder exists but there is no include folder in it which is needed by ndiswrapper. Can anybody help? Regards, D. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Danesh Daroui <Danesh.D@bredband.net> writes:
Hi all,
I have recently installed OpenSuse 10.2 and as I expected I have problem with my wireless card, however OpenSuse has act more efficient than Ubuntu so far. It actually detects my card but I can not connect to my wireless network. I use a HP Pavilion laptop which has a
Which wireless card do you have? Run hwinfo --wlan as root and show us the output.
built-in wireless card. It also has a light which will be on if the card is active. This light is always off on OpenSuse. So I decided to install the Windows drivers using ndiswrapper, but it needs the kernel source. In OpenSuse the kernel folder exists but there is no include folder in it which is needed by ndiswrapper. Can anybody help?
If you really need that, you have to install the kernel-source package. I suggest you check the opensuse.org wiki for further details, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, 2007-02-15 at 09:21 +0100, Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
Hi all,
I have recently installed OpenSuse 10.2 and as I expected I have problem with my wireless card, however OpenSuse has act more efficient than Ubuntu so far. It actually detects my card but I can not connect to my wireless network. I use a HP Pavilion laptop which has a
Which wireless card do you have?
Run hwinfo --wlan as root and show us the output.
built-in wireless card. It also has a light which will be on if the card is active. This light is always off on OpenSuse. So I decided to install the Windows drivers using ndiswrapper, but it needs the kernel source. In OpenSuse the kernel folder exists but there is no include folder in it which is needed by ndiswrapper. Can anybody help?
If you really need that, you have to install the kernel-source package.
I suggest you check the opensuse.org wiki for further details,
Andreas
I have a Dell D820 with a built-in wireless which is a broadcom. With Suse 10.1, I had to use the ndiswrapper, but with Suse 10.2, the broadcom had been added to the kernel, ipw3945. Also make sure the network card in enabled in BIOS and the hardware switch has it turned on. My dell had a hardware switch on the side that I did not know about that got switched off one time when I put it in its carrying bag, took me a call to dell tech support to find out about the switch (The manual is in Chinese and I don't read Chinese.) Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 14 February 2007, Art Fore wrote:
I have a Dell D820 with a built-in wireless which is a broadcom. With Suse 10.1, I had to use the ndiswrapper, but with Suse 10.2, the broadcom had been added to the kernel, ipw3945.
I've never gotten the kernel one to work. I think it is obsolete for what dell is shipping today. They seem to switch chipsets weekly. I have to use ndiswrapper on my dell 9400. -- _____________________________________ John Andersen
On Thu, 2007-02-15 at 00:09 -0900, John Andersen wrote:
On Wednesday 14 February 2007, Art Fore wrote:
I have a Dell D820 with a built-in wireless which is a broadcom. With Suse 10.1, I had to use the ndiswrapper, but with Suse 10.2, the broadcom had been added to the kernel, ipw3945.
I've never gotten the kernel one to work. I think it is obsolete for what dell is shipping today. They seem to switch chipsets weekly.
I have to use ndiswrapper on my dell 9400.
I ran hwinfo --wlan and the result is: 12: PCI 202.0: 0200 Ethernet controller [Created at pci.286] UDI: /org/freedesktop/Hal/devices/pci_14e4_4320 Unique ID: rBUF._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" Driver Modules: "bcm43xx" Device File: eth0 Features: WLAN Memory Range: 0xd0200000-0xd0201fff (rw,non-prefetchable) IRQ: 201 (no events) HW Address: 00:90:4b:53:b6:21 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 WLAN authentication modes: open sharedkey 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: #8 (PCI bridge) I think it shows that my wireless card is installed successfully but I can not still connect to a network... D. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Danesh Daroui <Danesh.D@bredband.net> writes:
I ran hwinfo --wlan and the result is:
12: PCI 202.0: 0200 Ethernet controller [Created at pci.286] UDI: /org/freedesktop/Hal/devices/pci_14e4_4320 Unique ID: rBUF._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" Driver Modules: "bcm43xx" Device File: eth0 Features: WLAN Memory Range: 0xd0200000-0xd0201fff (rw,non-prefetchable) IRQ: 201 (no events) HW Address: 00:90:4b:53:b6:21 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 WLAN authentication modes: open sharedkey 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: #8 (PCI bridge)
I think it shows that my wireless card is installed successfully but I can not still connect to a network...
Broadcom support is not quite fully working yet :-( Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, 2007-02-15 at 11:59 +0100, Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
I ran hwinfo --wlan and the result is:
12: PCI 202.0: 0200 Ethernet controller [Created at pci.286] UDI: /org/freedesktop/Hal/devices/pci_14e4_4320 Unique ID: rBUF._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" Driver Modules: "bcm43xx" Device File: eth0 Features: WLAN Memory Range: 0xd0200000-0xd0201fff (rw,non-prefetchable) IRQ: 201 (no events) HW Address: 00:90:4b:53:b6:21 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 WLAN authentication modes: open sharedkey 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: #8 (PCI bridge)
I think it shows that my wireless card is installed successfully but I can not still connect to a network...
Broadcom support is not quite fully working yet :-(
Andreas
It may not be fully working but the bcm43xx does, it is also in the Linksys WPC54G which works quite well in my laptop. The OP needs to extract the drivers from the windows .sys file and add them to /lib/firmware. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-02-15 at 07:18 -0500, Kenneth Schneider wrote:
On Thu, 2007-02-15 at 11:59 +0100, Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
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: #8 (PCI bridge)
I think it shows that my wireless card is installed successfully but I can not still connect to a network...
Broadcom support is not quite fully working yet :-(
Andreas
It may not be fully working but the bcm43xx does, it is also in the Linksys WPC54G which works quite well in my laptop. The OP needs to extract the drivers from the windows .sys file and add them to /lib/firmware.
Also the use of ndiswrapper is not needed. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kenneth Schneider wrote:
On Thu, 2007-02-15 at 11:59 +0100, Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
I ran hwinfo --wlan and the result is:
12: PCI 202.0: 0200 Ethernet controller [Created at pci.286] UDI: /org/freedesktop/Hal/devices/pci_14e4_4320 Unique ID: rBUF._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" Driver Modules: "bcm43xx" Device File: eth0 Features: WLAN Memory Range: 0xd0200000-0xd0201fff (rw,non-prefetchable) IRQ: 201 (no events) HW Address: 00:90:4b:53:b6:21 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 WLAN authentication modes: open sharedkey 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: #8 (PCI bridge)
I think it shows that my wireless card is installed successfully but I can not still connect to a network...
Broadcom support is not quite fully working yet :-(
Andreas
It may not be fully working but the bcm43xx does, it is also in the Linksys WPC54G which works quite well in my laptop. The OP needs to extract the drivers from the windows .sys file and add them to /lib/firmware.
I have .sys driver files for Windows. How can I use thin in OpenSuse without ndiswrapper? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-02-15 at 13:23 +0100, Danesh Daroui wrote:
Kenneth Schneider wrote:
On Thu, 2007-02-15 at 11:59 +0100, Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
Broadcom support is not quite fully working yet :-(
Andreas
It may not be fully working but the bcm43xx does, it is also in the Linksys WPC54G which works quite well in my laptop. The OP needs to extract the drivers from the windows .sys file and add them to /lib/firmware.
I have .sys driver files for Windows. How can I use thin in OpenSuse without ndiswrapper?
Use bcm43xx-fwcutter to extract the drivers files and put them in /lib/firmware. The kernel module should use them when you boot. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 February 2007, Kenneth Schneider wrote:
On Thu, 2007-02-15 at 13:23 +0100, Danesh Daroui wrote:
Kenneth Schneider wrote:
On Thu, 2007-02-15 at 11:59 +0100, Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
Broadcom support is not quite fully working yet :-(
Andreas
It may not be fully working but the bcm43xx does, it is also in the Linksys WPC54G which works quite well in my laptop. The OP needs to extract the drivers from the windows .sys file and add them to /lib/firmware.
I have .sys driver files for Windows. How can I use thin in OpenSuse without ndiswrapper?
Use bcm43xx-fwcutter to extract the drivers files and put them in /lib/firmware. The kernel module should use them when you boot.
Are you absolutely certain about this Ken? John Pierce has posted: " The problem I found after quite some snooping is that it is on the pci express bus and not the standard bus. The developers are continuing to work on it but they haven't got there yet." If the OPs machine also has the chipset on the express bus it could be the same problem. I've been down the fwcutter route and it refused to work. Ndiswrapper worked right away. Personally, I see little philosophical difference in hacking out firmware from a windows driver to plug into an open source driver AS OPPOSED TO using ndiswrapper. The latter almost always works, and the former is usually a crap shoot. -- _____________________________________ John Andersen
John Andersen wrote:
John Pierce has posted: " The problem I found after quite some snooping is that it is on the pci express bus and not the standard bus. The developers are continuing to work on it but they haven't got there yet."
If the OPs machine also has the chipset on the express bus it could be the same problem.
I've been down the fwcutter route and it refused to work. Ndiswrapper worked right away.
Personally, I see little philosophical difference in hacking out firmware from a windows driver to plug into an open source driver AS OPPOSED TO using ndiswrapper.
The latter almost always works, and the former is usually a crap shoot.
I've had the exact opposite experience with some Broadcom wifi cards and a Hauppage USB set-top box (the DEC 2000-T). I guess it depends on how well the firmware APIs are documented and implemented vs the NDIS APIs, and how complex they are. I'd also think it's possible to work around firmware bugs in a kernel driver in a way not really practical with a generic NDIS warper. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Pierce has posted: " The problem I found after quite some snooping is that it is on the pci express bus and not the standard bus. The developers are continuing to work on it but they haven't got there yet."
If the OPs machine also has the chipset on the express bus it could be the same problem.
I read on the developers list for the bcm driver that if they had a pci express card to work with they would be able to get it working a lot faster.
Personally, I see little philosophical difference in hacking out firmware from a windows driver to plug into an open source driver AS OPPOSED TO using ndiswrapper.
The latter almost always works, and the former is usually a crap shoot.
Well, to an extent, I agree. But if the native linux driver could be made a solid as the ralink driver for example that would be great. I am writing this on an ancient IBM Thinkpad A21M with a ralink rt2500 based belkin pcmcia card attached and it works flawlessy. -- John Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/15/07, Danesh Daroui <Danesh.D@bredband.net> wrote:
I ran hwinfo --wlan and the result is:
12: PCI 202.0: 0200 Ethernet controller Device: pci 0x4320 "BCM4306 802.11b/g Wireless LAN Controller"
Try using these instructions: <http://en.opensuse.org/SDB:Broadcom_%28BCM4306%29_WLAN_Installation_under_SUSE> Also, take a look at this bug report for the problems I met, and how to solve them: <https://bugzilla.novell.com/show_bug.cgi?id=229430> -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sunny wrote:
On 2/15/07, Danesh Daroui <Danesh.D@bredband.net> wrote:
I ran hwinfo --wlan and the result is:
12: PCI 202.0: 0200 Ethernet controller Device: pci 0x4320 "BCM4306 802.11b/g Wireless LAN Controller"
Try using these instructions:
<http://en.opensuse.org/SDB:Broadcom_%28BCM4306%29_WLAN_Installation_under_SUSE>
Also, take a look at this bug report for the problems I met, and how to solve them: <https://bugzilla.novell.com/show_bug.cgi?id=229430>
It is solved finally. Actually, I didn't want to use "ndiswrapper" and hence Windows drivers, since Windows is not welcomed to my systems at all, but the other approach which is "bcm43xx-fwcutter" workd at first, but it stopped after a while and never worked again. Now, with "ndiswrapper" everything works fine. I also realized (maybe I am just obsessed by OpenSuse) that OpenSuse manages wireless connections much better than Ubuntu. With OpenSuse, I can use my wireless network even when I am in my car (in garage of course) but with Ubuntu I had difficulties to connect to my network even in my room! Can it make sense? Regards, D. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 February 2007, Danesh Daroui wrote:
It is solved finally. Actually, I didn't want to use "ndiswrapper" and hence Windows drivers, since Windows is not welcomed to my systems at all, but the other approach which is "bcm43xx-fwcutter" workd at first, but it stopped after a while and never worked again. Now, with "ndiswrapper" everything works fine. I also realized (maybe I am just obsessed by OpenSuse)
No, Danesh, it is not solved until you post into this thread with a capital SOLVED appended onto the subject. Until you do that the thread will carry on and drift into political issues, soup recipes and solutions involving dead mice and paper bags. ;-) Glad you got it working. -- _____________________________________ John Andersen
On Fri, 2007-02-16 at 00:22 -0900, John Andersen wrote:
On Thursday 15 February 2007, Danesh Daroui wrote:
It is solved finally. Actually, I didn't want to use "ndiswrapper" and hence Windows drivers, since Windows is not welcomed to my systems at all, but the other approach which is "bcm43xx-fwcutter" workd at first, but it stopped after a while and never worked again. Now, with "ndiswrapper" everything works fine. I also realized (maybe I am just obsessed by OpenSuse)
No, Danesh, it is not solved until you post into this thread with a capital SOLVED appended onto the subject. Until you do that the thread will carry on and drift into political issues, soup recipes and solutions involving dead mice and paper bags. ;-)
Glad you got it working.
So, now it is solved. D. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Thursday 15 February 2007, Danesh Daroui wrote:
It is solved finally. Actually, I didn't want to use "ndiswrapper" and hence Windows drivers, since Windows is not welcomed to my systems at all, but the other approach which is "bcm43xx-fwcutter" workd at first, but it stopped after a while and never worked again. Now, with "ndiswrapper" everything works fine. I also realized (maybe I am just obsessed by OpenSuse)
No, Danesh, it is not solved until you post into this thread with a capital SOLVED appended onto the subject. Until you do that the thread will carry on and drift into political issues, soup recipes and solutions involving dead mice and paper bags. ;-)
But I have this really great recipe for dead mouse and wifi card soup... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Quoting John Andersen <jsa@pen.homeip.net>:
On Wednesday 14 February 2007, Art Fore wrote:
I have a Dell D820 with a built-in wireless which is a broadcom. With Suse 10.1, I had to use the ndiswrapper, but with Suse 10.2, the broadcom had been added to the kernel, ipw3945.
I've never gotten the kernel one to work. I think it is obsolete for what dell is shipping today. They seem to switch chipsets weekly.
I have to use ndiswrapper on my dell 9400.
IIRC, ipw is Intel Pro Wireless. Are you sure this is a Broadcom chip? Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-02-15 at 03:25 -0600, Jeffrey Taylor wrote:
Quoting John Andersen <jsa@pen.homeip.net>:
On Wednesday 14 February 2007, Art Fore wrote:
I have a Dell D820 with a built-in wireless which is a broadcom. With Suse 10.1, I had to use the ndiswrapper, but with Suse 10.2, the broadcom had been added to the kernel, ipw3945.
I've never gotten the kernel one to work. I think it is obsolete for what dell is shipping today. They seem to switch chipsets weekly.
I have to use ndiswrapper on my dell 9400.
IIRC, ipw is Intel Pro Wireless. Are you sure this is a Broadcom chip?
Jeffrey
You are right. Guess I was thinking of my old laptop which was a dell 8500. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I've never gotten the kernel one to work. I think it is obsolete for what dell is shipping today. They seem to switch chipsets weekly.
I have to use ndiswrapper on my dell 9400.
It is not obsolete, the chipset in the inspiron 9400 E1705 if the broadcom 4311. The problem I found after quite some snooping is that it is on the pci express bus and not the standard bus. The developers are continuing to work on it but they haven't got there yet. I agree, I have to use the ndiswrapper and windows driver to get mine to work. -- John Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Andreas Jaeger wrote:
Danesh Daroui <Danesh.D@bredband.net> writes:
Hi all,
I have recently installed OpenSuse 10.2 and as I expected I have problem with my wireless card, however OpenSuse has act more efficient than Ubuntu so far. It actually detects my card but I can not connect to my wireless network. I use a HP Pavilion laptop which has a
Which wireless card do you have?
Run hwinfo --wlan as root and show us the output.
built-in wireless card. It also has a light which will be on if the card is active. This light is always off on OpenSuse. So I decided to install the Windows drivers using ndiswrapper, but it needs the kernel source. In OpenSuse the kernel folder exists but there is no include folder in it which is needed by ndiswrapper. Can anybody help?
If you really need that, you have to install the kernel-source package.
I suggest you check the opensuse.org wiki for further details,
Andreas
I could not run "hwinfo --wlan". There is no such command. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-02-15 at 10:01 +0100, Jos van Kan wrote:
Danesh Daroui wrote: (knip)
I could not run "hwinfo --wlan". There is no such command.
/usr/sbin/hwinfo
Shouldn't that be in the path for root? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15-02-2007 at 13:00, Mike McMullin <mwmcmlln@mnsi.net> wrote: On Thu, 2007-02-15 at 10:01 +0100, Jos van Kan wrote: Danesh Daroui wrote: (knip)
I could not run "hwinfo --wlan". There is no such command.
/usr/sbin/hwinfo
Shouldn't that be in the path for root?
It should be. how did you get root? Login on a normal console as root? using 'su -' or Using 'su' The last one is known not to overwrite the environment and thus not setting the path as you expected (and most likely you did it like this). Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-02-15 at 09:04 +0100, Danesh Daroui wrote:
Hi all,
I have recently installed OpenSuse 10.2 and as I expected I have problem with my wireless card, however OpenSuse has act more efficient than Ubuntu so far. It actually detects my card but I can not connect to my wireless network. I use a HP Pavilion laptop which has a built-in wireless card. It also has a light which will be on if the card is active. This light is always off on OpenSuse. So I decided to install the Windows drivers using ndiswrapper, but it needs the kernel source. In OpenSuse the kernel folder exists but there is no include folder in it which is needed by ndiswrapper. Can anybody help?
1 - is there a switch to turn the wireless on/off, and have you tried that? 2 - Install the kernel sources using Yast - Software Management, search for kernel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (12)
-
Andreas Jaeger -
Art Fore -
Danesh Daroui -
Dominique Leuenberger -
Jeffrey Taylor -
John Andersen -
John Pierce -
Jos van Kan -
Kenneth Schneider -
Mike McMullin -
Russell Jones -
Sunny