Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
On Fri, Mar 14, 2008 at 07:49:02AM -0700, Larry Finger wrote: > John W. Linville wrote: > > On Fri, Mar 14, 2008 at 05:26:57PM +0530, Abhijit Hoskeri wrote: > > > >> [EMAIL PROTECTED]:~/src/wireless-testing$ git checkout --track -b > >> everything origin/everything > >> git checkout: updating paths is incompatible with switching > >> branches/forcing > >> Did you intend to checkout 'origin/everything' which can not be > >> resolved as commit? > > > > This was the old practice from before the latest tree organization > > (mid-February). > > What is current practice? While I have been on the road, I unsubscribed from > wireless and probably > missed any appropriate messages. Does the master branch of wireless-2.6.git > now have what used to be > in "everything"? No, but the master branch of wireless-testing.git does. Please use that for general development. Check the News page here: http://www.linuxwireless.org/ Hth! John -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
On Fri, 2008-03-14 at 07:49 -0700, Larry Finger wrote: > What is current practice? While I have been on the road, I unsubscribed from > wireless and probably > missed any appropriate messages. Does the master branch of wireless-2.6.git > now have what used to be > in "everything"? wireless-testing/master is what used to be wireless-2.6/everything -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
John W. Linville wrote: > On Fri, Mar 14, 2008 at 05:26:57PM +0530, Abhijit Hoskeri wrote: > >> [EMAIL PROTECTED]:~/src/wireless-testing$ git checkout --track -b >> everything origin/everything >> git checkout: updating paths is incompatible with switching >> branches/forcing >> Did you intend to checkout 'origin/everything' which can not be resolved >> as commit? > > This was the old practice from before the latest tree organization > (mid-February). What is current practice? While I have been on the road, I unsubscribed from wireless and probably missed any appropriate messages. Does the master branch of wireless-2.6.git now have what used to be in "everything"? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
On Fri, Mar 14, 2008 at 05:26:57PM +0530, Abhijit Hoskeri wrote: > [EMAIL PROTECTED]:~/src/wireless-testing$ git checkout --track -b > everything origin/everything > git checkout: updating paths is incompatible with switching > branches/forcing > Did you intend to checkout 'origin/everything' which can not be resolved > as commit? This was the old practice from before the latest tree organization (mid-February). > I am sorry, I do not know enough about git yet to guess what the correct > incantation should be. > > Anyway I just did a git-pull and got 2.6.25-rc5-wl. I have built it but not > had > opportunity to test it yet. Is this new enough to work? This is exactly what you want. John -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
On Fri, Mar 14, 2008 at 05:26:57PM +0530, Abhijit Hoskeri wrote: > On Thu, Mar 13, 2008 at 07:28:13AM -0700, Larry Finger wrote: > > I think your card should be supported. Did you checkout branch > > everything of Linville's tree, or are you running under the master > > branch? Issue the command 'git branch' and see which branch has the > > star. If you have used the master branch, you should issue the command > > 'git checkout --track -b everything origin/everything' to checkout the > > proper branch. It will have the latest code including the fix for your > > 64-bit card. Those devices used to work but a change in the DMA buffer > > handling elsewhere in the kernel broke them. > [EMAIL PROTECTED]:~/src/wireless-testing$ git checkout --track -b > everything origin/everything > git checkout: updating paths is incompatible with switching > branches/forcing > Did you intend to checkout 'origin/everything' which can not be resolved > as commit? > > Anyway I just did a git-pull and got 2.6.25-rc5-wl. I have built it but not > had > opportunity to test it yet. Is this new enough to work? Okay this kernel did not work either and has the same behaviour. Did not really expect this to work, since it may not have the DMA handling fix Larry talked about above. -Abhijit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
On Thu, Mar 13, 2008 at 07:28:13AM -0700, Larry Finger wrote: > I think your card should be supported. Did you checkout branch > everything of Linville's tree, or are you running under the master > branch? Issue the command 'git branch' and see which branch has the > star. If you have used the master branch, you should issue the command > 'git checkout --track -b everything origin/everything' to checkout the > proper branch. It will have the latest code including the fix for your > 64-bit card. Those devices used to work but a change in the DMA buffer > handling elsewhere in the kernel broke them. Thanks a lot! I ran this command, but it did not work: [EMAIL PROTECTED]:~/src/wireless-testing$ git branch * master [EMAIL PROTECTED]:~/src/wireless-testing$ git branch -l * master [EMAIL PROTECTED]:~/src/wireless-testing$ git-branch -r origin/HEAD origin/at76 origin/base origin/extra origin/fixes origin/master origin/merged-fixes origin/merged-upstream origin/upstream origin/upstream-pending [EMAIL PROTECTED]:~/src/wireless-testing$ git checkout --track -b everything origin/everything git checkout: updating paths is incompatible with switching branches/forcing Did you intend to checkout 'origin/everything' which can not be resolved as commit? I am sorry, I do not know enough about git yet to guess what the correct incantation should be. Anyway I just did a git-pull and got 2.6.25-rc5-wl. I have built it but not had opportunity to test it yet. Is this new enough to work? Thanks, Abhijit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 + 2.6.24 + patch gives blinking wireless LED
On Tue, Mar 04, 2008 at 09:44:33AM +, Cédric Caumont wrote: > > I use the git kernel ans the good firmware on my debian and every thinks are > ok!! > > http://linuxwireless.org/en/users/Drivers/b43#firmwareinstallation > > git-clone > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git > cd wireless-testing Thanks for the tip... but it still does not work for me for some strange reason :-( I am running the latest git of the kernel you specified above. I still kept getting the same behaviour and a firmware upgrade warning. I upgraded the firmware. The firmware warning is now gone but the DMA errors keep coming even if the only thing I do is to scan. ( I used to see scan results without errors until yesterday's git update). The new kernel logs after the latest git update is as follows. I am not getting the rc5 kernel if I do a git-pull from the above tree. Isn't it always supposed to be synced with upstream? Is this card officially supported/will be supported in 2.6.25? Thanks, Abhijit. -- uname -r: 2.6.25-rc4-wl dmesg output: kern.info: ACPI: Lid Switch [LID0] kern.info: input: Sleep Button (CM) as /class/input/input7 kern.info: ACPI: Sleep Button (CM) [SLPB] kern.info: b43-phy0: Broadcom 4311 WLAN found kern.debug: b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 9 kern.debug: b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 kern.debug: phy0: Selected rate control algorithm 'pid' kern.info: Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ] kern.info: Adding 2097136k swap on /dev/sda2. Priority:-1 extents:1 across:2097136k kern.info: device-mapper: uevent: version 1.0.3 kern.info: device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: [EMAIL PROTECTED] kern.warn: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011b8000 kern.notice: ReiserFS: sda3: found reiserfs format "3.6" with standard journal kern.notice: ReiserFS: sda3: using ordered data mode kern.notice: ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 kern.notice: ReiserFS: sda3: checking transaction log (sda3) kern.notice: ReiserFS: sda3: Using r5 hash to sort names kern.info: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 kern.info: NET: Registered protocol family 10 kern.info: lo: Disabled Privacy Extensions kern.info: ip_tables: (C) 2000-2006 Netfilter Core Team kern.warn: nf_conntrack version 0.5.0 (16384 buckets, 65536 max) kern.debug: eth0: no IPv6 routers present kern.info: [drm] Initialized drm 1.1.0 20060810 kern.info: ACPI: PCI Interrupt :00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 kern.debug: PCI: Setting latency timer of device :00:02.0 to 64 kern.info: [drm] Initialized i915 1.6.0 20060119 on minor 0 kern.info: input: b43-phy0 as /class/input/input8 kern.info: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) kern.debug: b43-phy0 debug: Chip initialized kern.debug: b43-phy0 debug: 64-bit DMA initialized kern.info: Registered led device: b43-phy0::tx kern.info: Registered led device: b43-phy0::rx kern.info: Registered led device: b43-phy0::radio kern.err: b43-phy0 ERROR: PHY transmission error kern.debug: b43-phy0 debug: Wireless interface started kern.debug: b43-phy0 debug: Adding Interface type 2 kern.info: b43-phy0: Radio hardware status changed to DISABLED kern.info: ADDRCONF(NETDEV_UP): wlan0: link is not ready kern.info: b43-phy0: Radio hardware status changed to ENABLED kern.err: b43-phy0 ERROR: Fatal DMA error: 0x0800, 0x, 0x, 0x, 0x, 0x kern.info: b43-phy0: Controller RESET (DMA error) ... kern.debug: b43-phy0 debug: Wireless interface stopped kern.debug: b43-phy0 debug: DMA-64 rx_ring: Used slots 1/64, Failed frames 0/0 = 0.0%, Average tries 0.00 kern.debug: b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 kern.debug: b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 kern.debug: b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 kern.debug: b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 16/128, Failed frames 0/12 = 0.0%, Average tries 1.00 kern.debug: b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 kern.info: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) kern.debug: b43-phy0 debug: Chip initialized kern.debug: b43-phy0 debug: 64-bit DMA initialized kern.info: Registered led device: b43-phy0::tx kern.info: Registered led device: b43-phy0::rx kern.info: Registered led device: b43-phy0::radio kern.debug: b43-phy0 debug: Wireless interface started kern.info: b43-phy0: Controller restarted kern.err: b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x
bcm4311 + 2.6.24 + patch gives blinking wireless LED
Hi, I have a Broadcom 4311 card that ndiswrapper detects and scans but cannot associate with. The b43 driver that ships with 2.6.24 does not detect anything at all. However If I patch the kernel with this patch http://linuxwireless.org/download/b43/patch_2.6.24_for_4311_2 the b43 driver appears to detect the card, find my access point and try to associate, but then suddenly the wireless LED starts blinking accompanied by some kernel messages from b43, continiously until I manage to reboot. Complete details lspci output (from a 2.6.24 kernel without the patch): 01:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 02) Subsystem: Hewlett-Packard Company Unknown device 1375 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x, 0x, 0x, 0x kern.info: b43-phy0: Controller RESET (DMA error) ... kern.warn: Controller restarted kern.info: Registered led device: b43-phy0:tx kern.info: Registered led device: b43-phy0:rx kern.info: Registered led device: b43-phy0:radio kern.info: b43-phy0: <3>b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x, 0x, 0x, 0x kern.warn: Controller restarted kern.info: Registered led device: b43-phy0:tx kern.info: Registered led device: b43-phy0:rx kern.info: Registered led device: b43-phy0:radio kern.warn: printk: 1 messages suppressed. kern.info: b43-phy0: Controller restarted kern.info: Registered led device: b43-phy0:tx kern.info: Registered led device: b43-phy0:rx kern.info: Registered led device: b43-phy0:radio kern.info: Registered led device: b43-phy0:tx kern.info: Registered led device: b43-phy0:rx kern.info: Registered led device: b43-phy0:radio kern.info: Registered led device: b43-phy0:tx kern.info: Registered led device: b43-phy0:rx kern.info: Registered led device: b43-phy0:radio kern.warn: printk: 8 messages suppressed. ... and so on. Thanks for the help... -Abhijit ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
