[gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

Hi all,
   I was using kernel 2.6.23 till now and everything was working pretty
well.
 My wireless card is ---0c:00.0 Network controller: Broadcom Corporation
BCM94311MCG wlan mini-PCI (rev 01).
It was working fine with kernel 2.6.23 with ndiswrapper. Yesterday i
upgraded to kernel 2.4.26. And my wireless card
stopped working.  It says that eth1 does not exist.
Some important out are below
-------------------------------------------------------------------------------------------------------
flukebox # ndiswrapper -l
bcmwl5 : driver installed
    device (14E4:4311) present
flukebox # /etc/init.d/net.eth1 start
 * Starting eth1
 *     /etc/conf.d/wireless is deprecated
 *     Please put all settings in /etc/conf.d/net
 *     /etc/conf.d/wireless is deprecated
 *     Please put all settings in /etc/conf.d/net
 *   Configuration not set for eth1 - assuming DHCP
 *   Bringing up eth1
 *     dhcp
 *       network interface eth1 does not exist
 *       Please verify hardware or kernel module
(driver)
[ !! ]
flukebox #
--------------------------------------------------------------------------------------------------------

I didn't have any kernel built-in module for bcmxx .
Can somebody help me here. Any help would be appreciated.

TIA,
flukebox

[-- Attachment #2: Type: text/html, Size: 2090 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Ian Lee]

dell core2duo wrote:
> Hi all,
>    I was using kernel 2.6.23 till now and everything was working
> pretty well.
>  My wireless card is ---0c:00.0 Network controller: Broadcom
> Corporation BCM94311MCG wlan mini-PCI (rev 01).
> It was working fine with kernel 2.6.23 with ndiswrapper. Yesterday i
> upgraded to kernel 2.4.26. And my wireless card
> stopped working.  It says that eth1 does not exist.
> Some important out are below
> -------------------------------------------------------------------------------------------------------
> flukebox # ndiswrapper -l
> bcmwl5 : driver installed
>     device (14E4:4311) present
> flukebox # /etc/init.d/net.eth1 start
>  * Starting eth1
>  *     /etc/conf.d/wireless is deprecated
>  *     Please put all settings in /etc/conf.d/net
>  *     /etc/conf.d/wireless is deprecated
>  *     Please put all settings in /etc/conf.d/net
>  *   Configuration not set for eth1 - assuming DHCP
>  *   Bringing up eth1
>  *     dhcp
>  *       network interface eth1 does not exist
>  *       Please verify hardware or kernel module
> (driver)                                                                          
> [ !! ]
> flukebox #
> --------------------------------------------------------------------------------------------------------
>
> I didn't have any kernel built-in module for bcmxx .
> Can somebody help me here. Any help would be appreciated.
>
> TIA,
> flukebox
>
>
>
>
>
Have u rebuilt the ndiswprapper kernel module for the new kernel?
try reinstalling ndiswrapper
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 3137 bytes --]

Yes,
I have already  rebuild all my drivers through "revdep-rebuild".
More over i am not able to find any eth1/wlan0  interface.
---------------------------------------------------------------------------------------------
flukebox flukebox # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:19:B9:80:97:66
          inet addr:172.24.0.234  Bcast:172.24.7.255  Mask:255.255.248.0
          inet6 addr: fe80::219:b9ff:fe80:9766/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:403919 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66919 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:156546805 (149.2 Mb)  TX bytes:6978869 (6.6 Mb)
          Interrupt:16

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:759 errors:0 dropped:0 overruns:0 frame:0
          TX packets:759 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:833199 (813.6 Kb)  TX bytes:833199 (813.6 Kb)

flukebox flukebox # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.

ip6tnl0   no wireless extensions.

flukebox flukebox #
--------------------------------------------------------------------------------------------

thanks,
flukebox





On Feb 9, 2008 5:02 PM, Ian Lee <ian@leehouse.eclipse.co.uk> wrote:

> dell core2duo wrote:
> > Hi all,
> >    I was using kernel 2.6.23 till now and everything was working
> > pretty well.
> >  My wireless card is ---0c:00.0 Network controller: Broadcom
> > Corporation BCM94311MCG wlan mini-PCI (rev 01).
> > It was working fine with kernel 2.6.23 with ndiswrapper. Yesterday i
> > upgraded to kernel 2.4.26. And my wireless card
> > stopped working.  It says that eth1 does not exist.
> > Some important out are below
> >
> -------------------------------------------------------------------------------------------------------
> > flukebox # ndiswrapper -l
> > bcmwl5 : driver installed
> >     device (14E4:4311) present
> > flukebox # /etc/init.d/net.eth1 start
> >  * Starting eth1
> >  *     /etc/conf.d/wireless is deprecated
> >  *     Please put all settings in /etc/conf.d/net
> >  *     /etc/conf.d/wireless is deprecated
> >  *     Please put all settings in /etc/conf.d/net
> >  *   Configuration not set for eth1 - assuming DHCP
> >  *   Bringing up eth1
> >  *     dhcp
> >  *       network interface eth1 does not exist
> >  *       Please verify hardware or kernel module
> > (driver)
> > [ !! ]
> > flukebox #
> >
> --------------------------------------------------------------------------------------------------------
> >
> > I didn't have any kernel built-in module for bcmxx .
> > Can somebody help me here. Any help would be appreciated.
> >
> > TIA,
> > flukebox
> >
> >
> >
> >
> >
> Have u rebuilt the ndiswprapper kernel module for the new kernel?
> try reinstalling ndiswrapper
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 5059 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Etaoin Shrdlu]

On Saturday 9 February 2008, dell core2duo wrote:

> Hi all,
>    I was using kernel 2.6.23 till now and everything was working
> pretty well.
>  My wireless card is ---0c:00.0 Network controller: Broadcom
> Corporation BCM94311MCG wlan mini-PCI (rev 01).
> It was working fine with kernel 2.6.23 with ndiswrapper. Yesterday i
> upgraded to kernel 2.4.26. And my wireless card
> stopped working.  It says that eth1 does not exist.

IIRC, the drivers for your card are now included in the kernel (bcm43xx).
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

On Feb 9, 2008 5:24 PM, Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:

> On Saturday 9 February 2008, dell core2duo wrote:
>
> > Hi all,
> >    I was using kernel 2.6.23 till now and everything was working
> > pretty well.
> >  My wireless card is ---0c:00.0 Network controller: Broadcom
> > Corporation BCM94311MCG wlan mini-PCI (rev 01).
> > It was working fine with kernel 2.6.23 with ndiswrapper. Yesterday i
> > upgraded to kernel 2.4.26. And my wireless card
> > stopped working.  It says that eth1 does not exist.
>
> IIRC, the drivers for your card are now included in the kernel (bcm43xx).


Does those driver provide the full features as ndiswrappers ??

thanks,
flukebox




>
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1375 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Etaoin Shrdlu]

On Saturday 9 February 2008, dell core2duo wrote:

> > IIRC, the drivers for your card are now included in the kernel
> > (bcm43xx).
>
> Does those driver provide the full features as ndiswrappers ??

Don't know what you mean exactly by "full features". I have used them in 
infrastructure mode with no problems (wpa2). However, here's the 
official page:

http://linuxwireless.org/en/users/Drivers/b43

according to 

http://linuxwireless.org/en/users/Drivers/b43/devices

your card (14E4:4311) is supported.

You need the firmware for the card, and the appropriate *-cutter tool to 
extract the firmware from the driver (it's in portage). 
Detailed info and step-by-step instructions are provided in the 
aforementioned page.
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

Hi
check this link,
http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_1520#Wireless_Network

It says that
<snip>
You should install the Windows driver from Dell if you would like to take
advantage of the full bandwith of your WLAN card (meaning 54 MBit/s).
!!FIXME!! If you would like to use the kernel driver, probably you can but
only with limited (11 MBit/s) bandwith.
</snip>

BTW,
  I am more interested to get things working. Quality would be my second
priority.

Thanks,
flukebox





On Feb 9, 2008 5:42 PM, Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:

> On Saturday 9 February 2008, dell core2duo wrote:
>
> > > IIRC, the drivers for your card are now included in the kernel
> > > (bcm43xx).
> >
> > Does those driver provide the full features as ndiswrappers ??
>
> Don't know what you mean exactly by "full features". I have used them in
> infrastructure mode with no problems (wpa2). However, here's the
> official page:
>
> http://linuxwireless.org/en/users/Drivers/b43
>
> according to
>
> http://linuxwireless.org/en/users/Drivers/b43/devices
>
> your card (14E4:4311) is supported.
>
> You need the firmware for the card, and the appropriate *-cutter tool to
> extract the firmware from the driver (it's in portage).
> Detailed info and step-by-step instructions are provided in the
> aforementioned page.
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 2186 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Etaoin Shrdlu]

On Saturday 9 February 2008, dell core2duo wrote:

> Hi
> check this link,
> http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_1520#Wireless_Network
>
> It says that
> <snip>
> You should install the Windows driver from Dell if you would like to
> take advantage of the full bandwith of your WLAN card (meaning 54
> MBit/s). !!FIXME!! If you would like to use the kernel driver,
> probably you can but only with limited (11 MBit/s) bandwith.
> </snip>

Uhm, the b43 page does not mention this. I guess you just have to try and 
see. Personally, I always prefer in-kernel drivers rather than external 
when possible, especially in this case where the external driver is 
actually a kludge around windows drivers.

> BTW,
>   I am more interested to get things working. Quality would be my
> second priority.

As I said before, I did not have any problem (unfortunately, I cannot 
access the hardware now and check the bandwidth issue).
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Dan Farrell]

On Sat, 9 Feb 2008 13:28:39 +0100
Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:

> > BTW,
> >   I am more interested to get things working. Quality would be my
> > second priority.  
> 
> As I said before, I did not have any problem (unfortunately, I cannot 
> access the hardware now and check the bandwidth issue).

I have not yet gotten the new driver to work, though admittedly I
didn't have much time to try and so went for ndiswrapper pretty
quickly.  

has anyone had luck with this driver recently?
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]

Hi,
  I complied the kernel buitin broadcom drivers. So now,  I have a interface
named "wlan0_rename".
 But things are still not working for me.

------------------------------------------------------------------------------------
flukebox flukebox # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.

ip6tnl0   no wireless extensions.

eth1      no wireless extensions.

wlan0_rename  IEEE 802.11g  ESSID:""
          Mode:Managed  Channel:0  Access Point: Not-Associated
          Tx-Power=0 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B
          Encryption key:off
          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

flukebox flukebox # /etc/init.d/net.wlan0_rename start
 * Starting wlan0_rename
 *     /etc/conf.d/wireless is deprecated
 *     Please put all settings in /etc/conf.d/net
 *     /etc/conf.d/wireless is deprecated
 *     Please put all settings in /etc/conf.d/net
 *   Starting wpa_supplicant on wlan0_rename ...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
supported                                                                  [
ok ]th param 5 value 0x1 -
 *   Starting wpa_cli on wlan0_rename
...
[ ok ]
 *     Backgrounding ...

------------------------------------------------------------------------------------

I guess  "param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported "
this has something to do with wpa_suplicant.
can somebody help me out here ??
Also, is there any way to change my interface name wlan0_rename to wlan0 or
eth1 ??


TIA,
flukebox







On Feb 10, 2008 3:17 AM, Dan Farrell <dan@spore.ath.cx> wrote:

> On Sat, 9 Feb 2008 13:28:39 +0100
> Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
>
> > > BTW,
> > >   I am more interested to get things working. Quality would be my
> > > second priority.
> >
> > As I said before, I did not have any problem (unfortunately, I cannot
> > access the hardware now and check the bandwidth issue).
>
> I have not yet gotten the new driver to work, though admittedly I
> didn't have much time to try and so went for ndiswrapper pretty
> quickly.
>
> has anyone had luck with this driver recently?
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 4726 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 5488 bytes --]

Hi,
  Some updates.
with the help of following links,

http://gentoo-wiki.com/HARDWARE_BCM43xx
http://ubuntuforums.org/showthread.php?t=647273&highlight=b43
http://ubuntuforums.org/showthread.php?t=649038
http://linuxwireless.org/en/users/Drivers/b43?action=show&redirect=en%2Fusers%2FDrivers%2Fbcm43xx

I have successfully built and load b43 driver. Now I can see the "wlan0"
interface.
-------------------------------------------------------------------------------------------------------------
flukebox home # lsmod |grep b43
b43                   130276  0
input_polldev           5784  1 b43

------------------------------------------------------------------------------------------------------------
ouput of iwconfig is below.


flukebox home # iwconfig
wlan0     IEEE 802.11g  ESSID:"iitk"
          Mode:Managed  Frequency:2.442 GHz  Access Point:
00:11:95:D8:E3:33
          Tx-Power=off
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B
          Encryption key:off
          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
----------------------------------------------------------------------------------------------------------
But still I am able to transmit any message. There is some error while
transmission.

flukebox home # dmesg|grep ERROR
[ 2420.327210] b43-phy0 ERROR: PHY transmission error
[ 2420.327622] b43-phy0 ERROR: PHY transmission error
[ 2420.327686] b43-phy0 ERROR: PHY transmission error
[ 2420.527136] b43-phy0 ERROR: PHY transmission error
[ 2420.527201] b43-phy0 ERROR: PHY transmission error
[ 2420.721574] b43-phy0 ERROR: PHY transmission error
[ 2420.721649] b43-phy0 ERROR: PHY transmission error
[ 2425.936058] b43-phy0 ERROR: PHY transmission error
[ 2425.936137] b43-phy0 ERROR: PHY transmission error
[ 2426.001384] b43-phy0 ERROR: PHY transmission error
[ 2429.932210] b43-phy0 ERROR: PHY transmission error
[ 2433.852553] b43-phy0 ERROR: PHY transmission error
[ 2433.910519] b43-phy0 ERROR: PHY transmission error
[ 2437.927955] b43-phy0 ERROR: PHY transmission error
[ 2441.883687] b43-phy0 ERROR: PHY transmission error
[ 2445.890988] b43-phy0 ERROR: PHY transmission error
-----------------------------------------------------------------------------------------------------
but I am still getting WEXT errors.
-----------------------------------------------------------------------------------------------------
 *   Starting wpa_supplicant on wlan0 ...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
supported               [ ok ]
th param 5 value 0x1 -
 *   Starting wpa_cli on wlan0
...
[ ok ]
 *     Backgrounding ...


Please help.

Thanks ,
flukebox




On Feb 12, 2008 10:38 PM, dell core2duo <gentoomail.dell@gmail.com> wrote:

> Hi,
>   I complied the kernel buitin broadcom drivers. So now,  I have a
> interface named "wlan0_rename".
>  But things are still not working for me.
>
>
> ------------------------------------------------------------------------------------
> flukebox flukebox # iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> sit0      no wireless extensions.
>
> ip6tnl0   no wireless extensions.
>
> eth1      no wireless extensions.
>
> wlan0_rename  IEEE 802.11g  ESSID:""
>           Mode:Managed  Channel:0  Access Point: Not-Associated
>           Tx-Power=0 dBm
>           Retry min limit:7   RTS thr:off   Fragment thr=2346 B
>           Encryption key:off
>           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
>
> flukebox flukebox # /etc/init.d/net.wlan0_rename start
>  * Starting wlan0_rename
>  *     /etc/conf.d/wireless is deprecated
>  *     Please put all settings in /etc/conf.d/net
>  *     /etc/conf.d/wireless is deprecated
>  *     Please put all settings in /etc/conf.d/net
>  *   Starting wpa_supplicant on wlan0_rename ...
> ioctl[SIOCSIWAUTH]: Operation not supported
> WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
> supported                                                                  [
> ok ]th param 5 value 0x1 -
>  *   Starting wpa_cli on wlan0_rename
> ...
> [ ok ]
>  *     Backgrounding ...
>
>
> ------------------------------------------------------------------------------------
>
> I guess  "param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
> " this has something to do with wpa_suplicant.
> can somebody help me out here ??
> Also, is there any way to change my interface name wlan0_rename to wlan0
> or eth1 ??
>
>
> TIA,
> flukebox
>
>
>
>
>
>
>
>
> On Feb 10, 2008 3:17 AM, Dan Farrell <dan@spore.ath.cx> wrote:
>
> > On Sat, 9 Feb 2008 13:28:39 +0100
> > Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
> >
> > > > BTW,
> > > >   I am more interested to get things working. Quality would be my
> > > > second priority.
> > >
> > > As I said before, I did not have any problem (unfortunately, I cannot
> > > access the hardware now and check the bandwidth issue).
> >
> > I have not yet gotten the new driver to work, though admittedly I
> > didn't have much time to try and so went for ndiswrapper pretty
> > quickly.
> >
> > has anyone had luck with this driver recently?
> > --
> > gentoo-user@lists.gentoo.org mailing list
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 9903 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Etaoin Shrdlu]

On Tuesday 12 February 2008, dell core2duo wrote:

>but I am still getting WEXT errors.
>Starting wpa_supplicant on wlan0
> ...
> ioctl[SIOCSIWAUTH]: Operation not supported
> WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
> supported               [ ok ]
> th param 5 value 0x1 -
>  *   Starting wpa_cli on wlan0
> ...
> [ ok ]
>  *     Backgrounding ...

WEXT seems to suggest "wireless extensions" (but I might be wrong of 
course). I have the following options enabled in my kernel (some might 
be redundant):

CONFIG_WIRELESS_EXT=y
CONFIG_CFG80211=y
CONFIG_NL80211=y
CONFIG_MAC80211=y
CONFIG_MAC80211_RCSIMPLE=y
CONFIG_MAC80211_DEBUG=y
CONFIG_MAC80211_VERBOSE_DEBUG=y
CONFIG_IEEE80211=y
CONFIG_IEEE80211_DEBUG=y
CONFIG_IEEE80211_CRYPT_WEP=y
CONFIG_IEEE80211_CRYPT_CCMP=y
CONFIG_IEEE80211_CRYPT_TKIP=y
CONFIG_IEEE80211_SOFTMAC=y
CONFIG_IEEE80211_SOFTMAC_DEBUG=y
CONFIG_WLAN_80211=y
CONFIG_B43=y
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_DEBUG=y
CONFIG_B43_DMA=y
CONFIG_B43_PIO=y
CONFIG_B43_DMA_AND_PIO_MODE=y
CONFIG_B43LEGACY=y
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_DEBUG=y
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y

I'm pretty sure some of them are redundant, but I have not had the time 
yet to read about the wireless extensions/*80211 changes and their 
implications. However, my card is working correctly with the above 
config.

Is the firmware in place (the correct one for your driver)? Post the 
relevant sections from /var/log/messages where the wireless card is 
recognized and initialized.
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 10312 bytes --]

Hi all,
 First of all thank you all.
  Finally i  got my wireless card working with b43 drivers. But throughput
is really low :-(.

Below is dmesg output for b43 driver.
<snip>
flukebox flukebox # dmesg|grep b43
[   27.087297] kobject b43: registering. parent: <NULL>, set: module
[   27.087328] kobject holders: registering. parent: b43, set: <NULL>
[   27.087404] fill_kobj_path: path = '/module/b43'
[   27.087501] kobject notes: registering. parent: b43, set: <NULL>
[   27.088021] bus ssb: add driver b43
[   27.088030] kobject b43: registering. parent: <NULL>, set: drivers
[   27.088060] fill_kobj_path: path = '/bus/ssb/drivers/b43'
[   27.088075] ssb: Matched Device ssb0:0 with Driver b43
[   27.088077] ssb: Probing driver b43 with device ssb0:0
[   27.088201] b43-phy0: Broadcom 4311 WLAN found
[   27.124445] b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
[   27.124465] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050,
Revision 2
[   27.163484] bound device 'ssb0:0' to driver 'b43'
[   27.163487] ssb: Bound Device ssb0:0 to Driver b43
[   27.163505] kobject drivers: registering. parent: b43, set: <NULL>
[   74.710234] input: b43-phy0 as /class/input/input11
[   74.936281] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29
05:54:02)
[   76.197406] b43-phy0 debug: Chip initialized
[   76.199682] b43-phy0 debug: 32-bit DMA initialized
[   76.213855] DEV: registering device: ID = 'b43-phy0:tx'
[   76.213863] kobject b43-phy0:tx: registering. parent: leds, set: devices
[   76.213883] PM: Adding info for No Bus:b43-phy0:tx
[   76.213906] fill_kobj_path: path = '/class/leds/b43-phy0:tx'
[   76.213927] Registered led device: b43-phy0:tx
[   76.213939] DEV: registering device: ID = 'b43-phy0:rx'
[   76.213947] kobject b43-phy0:rx: registering. parent: leds, set: devices
[   76.213966] PM: Adding info for No Bus:b43-phy0:rx
[   76.213989] fill_kobj_path: path = '/class/leds/b43-phy0:rx'
[   76.214007] Registered led device: b43-phy0:rx
[   76.214019] DEV: registering device: ID = 'b43-phy0:radio'
[   76.214027] kobject b43-phy0:radio: registering. parent: leds, set:
devices
[   76.214045] PM: Adding info for No Bus:b43-phy0:radio
[   76.214068] fill_kobj_path: path = '/class/leds/b43-phy0:radio'
[   76.214086] Registered led device: b43-phy0:radio
[   76.214183] b43-phy0 debug: Wireless interface started
[   76.253791] b43-phy0 debug: Adding Interface type 2
</snip>


Actually this kernel log lines really help me out.

<snip>

Feb 14 02:29:45 [kernel] [   28.088239] ssb: Matched Device ssb0:0 with
Driver b43
Feb 14 02:29:45 [kernel] [   28.088367] b43-phy0: Broadcom 4311 WLAN found
Feb 14 02:29:45 [kernel] [   28.122350] b43-phy0 debug: Found PHY: Analog 4,
Type 2, Revision 8
Feb 14 02:29:45 [kernel] [   28.122371] b43-phy0 debug: Found Radio: Manuf
0x17F, Version 0x2050, Revision 2
Feb 14 02:29:45 [kernel] [   28.161505] bound device 'ssb0:0' to driver
'b43'
Feb 14 02:29:45 [kernel] [   28.161508] ssb: Bound Device ssb0:0 to Driver
b43
Feb 14 02:29:45 [kernel] [   28.161534] kobject drivers: registering.
parent: b43, set: <NULL>
Feb 14 02:29:45 [kernel] [   98.817654] input: b43-phy0 as
/class/input/input11
Feb 14 02:29:45 [kernel] [   99.063914] b43-phy0 ERROR: YOUR FIRMWARE IS TOO
NEW. Please downgrade your firmware.
Feb 14 02:29:45 [kernel] [   99.063917] b43-phy0 ERROR: Use this firmware
tarball: http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
Feb 14 02:29:45 [kernel] [   99.063920] b43-phy0 ERROR: Use this
b43-fwcutter tarball: http://bu3sch.de/b43/fwcutter/b43-fwcutter-009.tar.bz2
Feb 14 02:29:45 [kernel] [   99.063923] b43-phy0 ERROR: Read, understand and
_do_ what this message says, please.
Feb 14 02:29:45 [kernel] [   99.081093] input: b43-phy0 as
/class/input/input12
Feb 14 02:29:45 [kernel] [   99.218499] b43-phy0 ERROR: Microcode not
responding
Feb 14 02:29:45 [kernel] [   99.218503] b43-phy0 ERROR: You must go to
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download
the correct firmware (version 4).
Feb 14 02:29:45 [kernel] [   99.339472] input: b43-phy0 as
/class/input/input13
Feb 14 02:29:45 [kernel] [   99.475159] b43-phy0 ERROR: YOUR FIRMWARE IS TOO
NEW. Please downgrade your firmware.
Feb 14 02:29:45 [kernel] [   99.475163] b43-phy0 ERROR: Use this firmware
tarball: http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
Feb 14 02:29:45 [kernel] [   99.475166] b43-phy0 ERROR: Use this
b43-fwcutter tarball: http://bu3sch.de/b43/fwcutter/b43-fwcutter-009.tar.bz2
Feb 14 02:29:45 [kernel] [   99.475169] b43-phy0 ERROR: Read, understand and
_do_ what this message says, please.
Feb 14 02:29:45 [kernel] [  100.073085] input: b43-phy0 as
/class/input/input14
Feb 14 02:29:45 [kernel] [  100.211085] b43-phy0 ERROR: Microcode not
responding
Feb 14 02:29:45 [kernel] [  100.211088] b43-phy0 ERROR: You must go to
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download
the correct firmware (version 4).

</snip>

There after i did exactly what these error lines are saying.  I unloaded the
b43 module.  Removed my b43 firmware. Then got firmware and b43-fwcutter
listed in error lines and
installed them. And then modprobe the b43 module again. Thats it.  My
wireless card began to work again.

Now,  Is there anyway i can choose or change the Bit rate ?

Output of iwconfig is as below,

<snip>

flukebox flukebox # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0_rename  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"iitk"
          Mode:Managed  Frequency:2.442 GHz  Access Point:
00:11:95:D8:E3:33
          Bit Rate=1 Mb/s   Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B
          Encryption key:off
          Link Quality=86/100  Signal level=-41 dBm  Noise level=-69 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

</snip>

Output for iwlist wlan0 scan is as below.

<snip>
flukebox flukebox # iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:11:95:D8:E3:33
                    ESSID:"iitk"
                    Mode:Master
                    Channel:7
                    Frequency:2.442 GHz (Channel 7)
                    Quality=83/100  Signal level=-44 dBm  Noise level=-68
dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:tsf=000000011b4e9037
          Cell 02 - Address: 00:0F:B5:96:C6:70
                    ESSID:"iitk"
                    Mode:Master
                    Channel:10
                    Frequency:2.457 GHz (Channel 10)
                    Quality=53/100  Signal level=-71 dBm  Noise level=-68
dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:tsf=0000000ecfc4aabc
          Cell 03 - Address: 00:11:95:D8:E3:46
                    ESSID:"iitk"
                    Mode:Master
                    Channel:12
                    Frequency:2.467 GHz
                    Quality=41/100  Signal level=-82 dBm  Noise level=-68
dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:tsf=0000005e677b0059
          Cell 04 - Address: 00:0F:B5:96:C5:2B
                    ESSID:"iitk"
                    Mode:Master
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=43/100  Signal level=-80 dBm  Noise level=-68
dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:tsf=0000007fa688b18

</snip>

Moreover,  Card was working with 56Mb/s bit rate with ndiswrapper
perfectly.

Anyway to increase that ??


thanks and regards,
flukebox


On Feb 13, 2008 4:41 AM, Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:

> On Tuesday 12 February 2008, dell core2duo wrote:
>
> >but I am still getting WEXT errors.
> >Starting wpa_supplicant on wlan0
> > ...
> > ioctl[SIOCSIWAUTH]: Operation not supported
> > WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
> > supported               [ ok ]
> > th param 5 value 0x1 -
> >  *   Starting wpa_cli on wlan0
> > ...
> > [ ok ]
> >  *     Backgrounding ...
>
> WEXT seems to suggest "wireless extensions" (but I might be wrong of
> course). I have the following options enabled in my kernel (some might
> be redundant):
>
> CONFIG_WIRELESS_EXT=y
> CONFIG_CFG80211=y
> CONFIG_NL80211=y
> CONFIG_MAC80211=y
> CONFIG_MAC80211_RCSIMPLE=y
> CONFIG_MAC80211_DEBUG=y
> CONFIG_MAC80211_VERBOSE_DEBUG=y
> CONFIG_IEEE80211=y
> CONFIG_IEEE80211_DEBUG=y
> CONFIG_IEEE80211_CRYPT_WEP=y
> CONFIG_IEEE80211_CRYPT_CCMP=y
> CONFIG_IEEE80211_CRYPT_TKIP=y
> CONFIG_IEEE80211_SOFTMAC=y
> CONFIG_IEEE80211_SOFTMAC_DEBUG=y
> CONFIG_WLAN_80211=y
> CONFIG_B43=y
> CONFIG_B43_PCI_AUTOSELECT=y
> CONFIG_B43_PCICORE_AUTOSELECT=y
> CONFIG_B43_DEBUG=y
> CONFIG_B43_DMA=y
> CONFIG_B43_PIO=y
> CONFIG_B43_DMA_AND_PIO_MODE=y
> CONFIG_B43LEGACY=y
> CONFIG_B43LEGACY_PCI_AUTOSELECT=y
> CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
> CONFIG_B43LEGACY_DEBUG=y
> CONFIG_B43LEGACY_DMA=y
> CONFIG_B43LEGACY_PIO=y
> CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
>
> I'm pretty sure some of them are redundant, but I have not had the time
> yet to read about the wireless extensions/*80211 changes and their
> implications. However, my card is working correctly with the above
> config.
>
> Is the firmware in place (the correct one for your driver)? Post the
> relevant sections from /var/log/messages where the wireless card is
> recognized and initialized.
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 17678 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Etaoin Shrdlu]

On Wednesday 13 February 2008, dell core2duo wrote:

> Hi all,
>  First of all thank you all.
>   Finally i  got my wireless card working with b43 drivers. But
> throughput is really low :-(.
>[cut]
> flukebox flukebox # iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> wmaster0_rename  no wireless extensions.
>
> wlan0     IEEE 802.11g  ESSID:"iitk"
>           Mode:Managed  Frequency:2.442 GHz  Access Point:
> 00:11:95:D8:E3:33
>           Bit Rate=1 Mb/s   Tx-Power=27 dBm
>           Retry min limit:7   RTS thr:off   Fragment thr=2346 B
>           Encryption key:off
>           Link Quality=86/100  Signal level=-41 dBm  Noise level=-69
> dBm Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx
> excessive retries:0  Invalid misc:0   Missed beacon:0

Uhm, the solution might be as simple as doing "iwconfig wlan0 rate 54M 
fixed". However, I just noticed that the linuxwireless page about b43 
has changed since yesterday; there are new instructions regarding the 
versions of firmware and fwcutter tool to use (011), and specific info 
regarding kernel 2.6.24. Check it out:

http://linuxwireless.org/en/users/Drivers/b43

Tomorrow I too am going to try the new instructions, and read some docs 
to at least try understanding what's going on with the new driver 
architecture (the *80211 stuff).
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]

On Feb 14, 2008 3:48 AM, Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:

> On Wednesday 13 February 2008, dell core2duo wrote:
>
> > Hi all,
> >  First of all thank you all.
> >   Finally i  got my wireless card working with b43 drivers. But
> > throughput is really low :-(.
> >[cut]
> > flukebox flukebox # iwconfig
> > lo        no wireless extensions.
> >
> > eth0      no wireless extensions.
> >
> > wmaster0_rename  no wireless extensions.
> >
> > wlan0     IEEE 802.11g  ESSID:"iitk"
> >           Mode:Managed  Frequency:2.442 GHz  Access Point:
> > 00:11:95:D8:E3:33
> >           Bit Rate=1 Mb/s   Tx-Power=27 dBm
> >           Retry min limit:7   RTS thr:off   Fragment thr=2346 B
> >           Encryption key:off
> >           Link Quality=86/100  Signal level=-41 dBm  Noise level=-69
> > dBm Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx
> > excessive retries:0  Invalid misc:0   Missed beacon:0
>
> Uhm, the solution might be as simple as doing



> "iwconfig wlan0 rate 54Mfixed".


This command set bit rate to 54Mb but card suddenly stopped working :-(.
So,  I revert back to previous mode. Now i can see variable rates. Network
is working
fine. So, i guess bit rate doesn't make much difference(does it ??).




> However, I just noticed that the linuxwireless page about b43
> has changed since yesterday; there are new instructions regarding the
> versions of firmware and fwcutter tool to use (011), and specific info
> regarding kernel 2.6.24. Check it out:
>
> http://linuxwireless.org/en/users/Drivers/b43
>

I just checked, exactly first option suites my conditions and working fine.



>
> Tomorrow I too am going to try the new instructions, and read some docs
> to at least try understanding what's going on with the new driver
> architecture (the *80211 stuff).
>

Good luck for you !


> --
> gentoo-user@lists.gentoo.org mailing list
>
>

Thanks,
Flukebox

[-- Attachment #2: Type: text/html, Size: 3554 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Etaoin Shrdlu]

On Wednesday 13 February 2008, dell core2duo wrote:

> Output for iwlist wlan0 scan is as below.
>
> flukebox flukebox # iwlist wlan0 scan
> wlan0     Scan completed :
>           Cell 01 - Address: 00:11:95:D8:E3:33
>                     ESSID:"iitk"
>                     Channel:7
>           Cell 02 - Address: 00:0F:B5:96:C6:70
>                     ESSID:"iitk"
>                     Channel:10
>           Cell 03 - Address: 00:11:95:D8:E3:46
>                     ESSID:"iitk"
>                     Channel:12
>           Cell 04 - Address: 00:0F:B5:96:C5:2B
>                     ESSID:"iitk"
>                     Channel:11

It seems you are using different APs with the same SSID. 
AFAIK, with 802.11b/g, to avoid confusing the wifi cards, neighboring AP 
channels should not overlap, which means they should be at least 5 
channels apart (eg, 1,6,11 or 1,7,13, etc). APs transmitting on 
overlapping channels may cause interferences and confuse the wifi card, 
which might not be able to sense clearly when it is moving between APs, 
resulting in difficulties in deciding when to roam from one AP to 
another.
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Iain Buchanan]

On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
> On Sat, 9 Feb 2008 13:28:39 +0100
> Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
> 
> > > BTW,
> > >   I am more interested to get things working. Quality would be my
> > > second priority.  
> > 
> > As I said before, I did not have any problem (unfortunately, I cannot 
> > access the hardware now and check the bandwidth issue).
> 
> I have not yet gotten the new driver to work, though admittedly I
> didn't have much time to try and so went for ndiswrapper pretty
> quickly.  

how did you get ndiswrapper to work?  It worked for me for 2.6.23, but
not for 2.6.24.  I have a BCM4306 and I'm having some trouble getting
the kernel driver to work, so I'd like to use ndiswrapper in the mean
time.

When I load ndiswrapper (yes I've rebuilt it :) I get no wlan0 like I
used to.

thanks,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Wash: "Oh my god, it's grotesque! Oh, and there's something in a jar."
				--Episode #12, "The Message"

-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan <iaindb@netspace.net.au>
wrote:

>
> On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
> > On Sat, 9 Feb 2008 13:28:39 +0100
> > Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
> >
> > > > BTW,
> > > >   I am more interested to get things working. Quality would be my
> > > > second priority.
> > >
> > > As I said before, I did not have any problem (unfortunately, I cannot
> > > access the hardware now and check the bandwidth issue).
> >
> > I have not yet gotten the new driver to work, though admittedly I
> > didn't have much time to try and so went for ndiswrapper pretty
> > quickly.
>
> how did you get ndiswrapper to work?  It worked for me for 2.6.23, but
> not for 2.6.24.  I have a BCM4306 and I'm having some trouble getting
> the kernel driver to work, so I'd like to use ndiswrapper in the mean
> time.
>

I guess there are some problems with ndiswrapper on kernel-2.4.26.  I didn't
get ndiswraper worked with kernel-2.4.26.
did you tried kernel b43 module ??  Read below links, these may help you.

http://gentoo-wiki.com/HARDWARE_BCM43xx
http://linuxwireless.org/en/users/Drivers/b43?action=show&redirect=en%2Fusers%2FDrivers%2Fbcm43xx

regards,
flukebox





>
> When I load ndiswrapper (yes I've rebuilt it :) I get no wlan0 like I
> used to.
>
> thanks,
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
>
> Wash: "Oh my god, it's grotesque! Oh, and there's something in a jar."
>                                --Episode #12, "The Message"
>
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 2685 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Iain Buchanan]

On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote:
> 
> 
> On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan
> <iaindb@netspace.net.au> wrote:
>         
>         On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
>         > On Sat, 9 Feb 2008 13:28:39 +0100
>         > Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
>         >
>         > > > BTW,
>         > > >   I am more interested to get things working. Quality
>         would be my
>         > > > second priority.
>         > >
>         > > As I said before, I did not have any problem
>         (unfortunately, I cannot
>         > > access the hardware now and check the bandwidth issue).
>         >
>         > I have not yet gotten the new driver to work, though
>         admittedly I
>         > didn't have much time to try and so went for ndiswrapper
>         pretty
>         > quickly.
>         
>         
>         how did you get ndiswrapper to work?  It worked for me for
>         2.6.23, but
>         not for 2.6.24.  I have a BCM4306 and I'm having some trouble
>         getting
>         the kernel driver to work, so I'd like to use ndiswrapper in
>         the mean
>         time.
> 
> I guess there are some problems with ndiswrapper on kernel-2.4.26.  I
> didn't get ndiswraper worked with kernel-2.4.26.

Oh, I thought you meant ndis with 2.4.26.

> did you tried kernel b43 module ??  Read below links, these may help
> you.

I use b44 for my eth0 (always have).  The problem with ndiswrapper was
that b44 was grabbing wlan0 before ndis could.  I couldn't ping over the
wlan so I assumed b44 didn't work, but I was just playing around with
routes, and I have managed to get both eth0 and wlan0 working with b44
together (no ndis).

If you understood that sentence, congratulations!

so no more ndis it seems!

thanks,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

An engineer is someone who does list processing in FORTRAN.

-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[dell core2duo]

[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]

On Feb 18, 2008 5:59 PM, Iain Buchanan <iaindb@netspace.net.au> wrote:

>
> On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote:
> >
> >
> > On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan
> > <iaindb@netspace.net.au> wrote:
> >
> >         On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
> >         > On Sat, 9 Feb 2008 13:28:39 +0100
> >         > Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
> >         >
> >         > > > BTW,
> >         > > >   I am more interested to get things working. Quality
> >         would be my
> >         > > > second priority.
> >         > >
> >         > > As I said before, I did not have any problem
> >         (unfortunately, I cannot
> >         > > access the hardware now and check the bandwidth issue).
> >         >
> >         > I have not yet gotten the new driver to work, though
> >         admittedly I
> >         > didn't have much time to try and so went for ndiswrapper
> >         pretty
> >         > quickly.
> >
> >
> >         how did you get ndiswrapper to work?  It worked for me for
> >         2.6.23, but
> >         not for 2.6.24.  I have a BCM4306 and I'm having some trouble
> >         getting
> >         the kernel driver to work, so I'd like to use ndiswrapper in
> >         the mean
> >         time.
> >
> > I guess there are some problems with ndiswrapper on kernel-2.4.26.  I
> > didn't get ndiswraper worked with kernel-2.4.26.
>
> Oh, I thought you meant ndis with 2.4.26.


I mean kernel 2.6.24 !!


>
>
> > did you tried kernel b43 module ??  Read below links, these may help
> > you.
>
> I use b44 for my eth0 (always have).  The problem with ndiswrapper was
> that b44 was grabbing wlan0 before ndis could.  I couldn't ping over the
> wlan so I assumed b44 didn't work, but I was just playing around with
> routes, and I have managed to get both eth0 and wlan0 working with b44
> together (no ndis).
>
> If you understood that sentence, congratulations!
>

I understand little bit not fully. I didn't get how you managed without b43
module ? would be great if you could explain that.

thanks,
flukebox




> so no more ndis it seems!
>
> thanks,
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
>
> An engineer is someone who does list processing in FORTRAN.
>
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 4052 bytes --]

Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

[Iain Buchanan]

On Mon, 2008-02-18 at 18:37 +0530, dell core2duo wrote:
> 
> 
> On Feb 18, 2008 5:59 PM, Iain Buchanan <iaindb@netspace.net.au> wrote:
>         
>         
>         On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote:
>         >
>         >
>         > On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan
>         > <iaindb@netspace.net.au> wrote:
>         >
>         >         On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
>         >         > On Sat, 9 Feb 2008 13:28:39 +0100
>         >         > Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
>         >         >
>         >         > > > BTW,
>         >         > > >   I am more interested to get things working. Quality
>         >         would be my
>         >         > > > second priority.
>         >         > >
>         >         > > As I said before, I did not have any problem
>         >         (unfortunately, I cannot
>         >         > > access the hardware now and check the bandwidth issue).
>         >         >
>         >         > I have not yet gotten the new driver to work, though
>         >         admittedly I
>         >         > didn't have much time to try and so went for ndiswrapper
>         >         pretty
>         >         > quickly.
>         >
>         >
>         >         how did you get ndiswrapper to work?  It worked for me for
>         >         2.6.23, but
>         >         not for 2.6.24.  I have a BCM4306 and I'm having some trouble
>         >         getting
>         >         the kernel driver to work, so I'd like to use ndiswrapper in
>         >         the mean
>         >         time.
>         >
>         > I guess there are some problems with ndiswrapper on kernel-2.4.26.  I
>         > didn't get ndiswraper worked with kernel-2.4.26.
>         
>         
>         Oh, I thought you meant ndis with 2.4.26.
> 
> I mean kernel 2.6.24 !! 

Whoops, that's what I meant I thought you meant :S


>         > did you tried kernel b43 module ??  Read below links, these may help
>         > you.
>         
>         
>         I use b44 for my eth0 (always have).  The problem with ndiswrapper was
>         that b44 was grabbing wlan0 before ndis could.  I couldn't ping over the
>         wlan so I assumed b44 didn't work, but I was just playing around with
>         routes, and I have managed to get both eth0 and wlan0 working with b44
>         together (no ndis).
>         
>         If you understood that sentence, congratulations!
> 
> I understand little bit not fully. I didn't get how you managed
> without b43 module ? would be great if you could explain that.

OK, I made a mistake there too.  b44 I use for eth0, *b43* was grabbing
wlan0 before ndiswrapper could.

I tried playing with b43 and the cutter tool, but it didn't work as I
mentioned before.

I had to use the old bcm43xx module.  There were some kernel options to
change, and a different cutter tool.  I followed the instructions here:
http://gentoo-wiki.com/HARDWARE_BCM43xx

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Perl is designed to give you several ways to do anything, so
consider picking the most readable one.
             -- Larry Wall in the perl man page

-- 
gentoo-user@lists.gentoo.org mailing list