Re: Better log files . Trying to figure out b43
On Sat, Feb 09, 2008 at 09:07:52PM -0800, Brian Lavender wrote: At one point I had the version 3 firmware working, but now it doesn't seem to be working. I checked the log files and debugging is enabled with firmware version listed. When I was using firware version 3, I unplugged and replugged the card. Seems to be working fine now with the firmware 3. DMA seems to be ok too. brian -- Brian Lavender http://www.brie.com/brian/ [0.00] Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #2 Sat Feb 9 17:38:49 PST 2008 (Ubuntu 2.6.22-14.51-generic) [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 0010 - 3ffae000 (usable) [0.00] BIOS-e820: 3ffae000 - 4000 (reserved) [0.00] BIOS-e820: feda - fee0 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] 127MB HIGHMEM available. [0.00] 896MB LOWMEM available. [0.00] Entering add_active_range(0, 0, 262062) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] Normal 4096 - 229376 [0.00] HighMem229376 - 262062 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 - 262062 [0.00] On node 0 totalpages: 262062 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 1760 pages used for memmap [0.00] Normal zone: 223520 pages, LIFO batch:31 [0.00] HighMem zone: 255 pages used for memmap [0.00] HighMem zone: 32431 pages, LIFO batch:7 [0.00] Movable zone: 0 pages used for memmap [0.00] DMI 2.3 present. [0.00] ACPI: RSDP signature @ 0xC00FDF00 checksum 0 [0.00] ACPI: RSDP 000FDF00, 0014 (r0 DELL ) [0.00] ACPI: RSDT 3FFF, 0028 (r1 DELLCPi R 27D40708 ASL 61) [0.00] ACPI: FACP 3FFF0400, 0074 (r1 DELLCPi R 27D40708 ASL 61) [0.00] ACPI: DSDT 3FFF0C00, 2E04 (r1 INT430 SYSFexxx 1001 MSFT 10E) [0.00] ACPI: FACS 3800, 0040 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] Allocating PCI resources starting at 5000 (gap: 4000:beda) [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260015 [0.00] Kernel command line: root=UUID=37330e16-ef70-48db-b739-fd1487fca15b ro quiet splash [0.00] Enabling fast FPU save and restore... done. [0.00] Enabling unmasked SIMD FPU exception support... done. [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 16384 bytes) [0.00] Detected 1598.693 MHz processor. [ 16.329230] Console: colour VGA+ 80x25 [ 16.329234] console [tty0] enabled [ 16.329857] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 16.330468] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 16.362776] Memory: 995004k/1048248k available (1867k kernel code, 52528k reserved, 880k data, 296k init, 130744k highmem) [ 16.362784] virtual kernel memory layout: [ 16.362785] fixmap : 0xfffe9000 - 0xf000 ( 88 kB) [ 16.362787] pkmap : 0xff80 - 0xffc0 (4096 kB) [ 16.362788] vmalloc : 0xf880 - 0xff7fe000 ( 111 MB) [ 16.362789] lowmem : 0xc000 - 0xf800 ( 896 MB) [ 16.362791] .init : 0xc03b2000 - 0xc03fc000 ( 296 kB) [ 16.362792] .data : 0xc02d2f95 - 0xc03af1a4 ( 880 kB) [ 16.362793] .text : 0xc010 - 0xc02d2f95 (1867 kB) [ 16.362797] Checking if this processor honours the WP bit even in supervisor mode... Ok. [ 16.362831] SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 [ 16.442784] Calibrating delay using timer specific routine.. 3199.38 BogoMIPS (lpj=6398764) [ 16.442809] Security Framework initialized [ 16.442817] SELinux: Disabled at boot. [ 16.442822] Mount-cache hash table entries: 512 [ 16.442932] CPU: After generic identify, caps: afe9f9bf 0180 [ 16.442944] CPU: L1 I cache: 32K, L1 D cache: 32K [ 16.442946] CPU: L2 cache: 2048K [ 16.442949] CPU: After all inits, caps: afe9f9bf 2040 0180 [ 16.442956] Compat vDSO mapped to e000. [ 16.442966] CPU: Intel(R) Pentium(R) M processor 1.60GHz stepping 06 [ 16.442971] Checking 'hlt' instruction... OK. [ 16.459067] Freeing SMP alternatives: 0k freed [ 16.459170] Early unpacking initramfs... done [
Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )
On Sunday 10 February 2008 04:22:06 Pedro P wrote: Hi, My name is Javier and I'm a new in Linux. I have a problem with my wireless card Broadcom (WL-138G V2). The firmware is installed but I can't connect card. Also NetworkManager doesn't detect wireless card. Can You help me? Regards, Javier Specifications of my system: (lsmod and dmesg) - [EMAIL PROTECTED]:~ lsmod Module Size Used by nls_iso8859_1 8192 1 nls_cp437 9856 1 vfat 16128 1 fat52380 1 vfat iptable_filter 6912 0 ip_tables 16324 1 iptable_filter ip6table_filter 6784 0 ip6_tables 17476 1 ip6table_filter x_tables 18308 2 ip_tables,ip6_tables arc46016 2 ipv6 268152 20 ecb 7552 2 blkcipher 10116 1 ecb ieee80211_crypt_wep 9088 1 af_packet 29064 4 cpufreq_conservative11272 0 snd_pcm_oss50432 0 snd_mixer_oss 20096 1 snd_pcm_oss cpufreq_userspace 8704 0 snd_seq54452 0 snd_seq_device 12172 1 snd_seq cpufreq_powersave 5888 0 acpi_cpufreq 13192 0 speedstep_lib 9220 0 microcode 15372 0 apparmor 40736 0 loop 21636 0 dm_mod 56880 0 iTCO_wdt 14372 0 intel_agp 27156 0 i2c_i801 12560 0 iTCO_vendor_support 7812 1 iTCO_wdt usb_storage80780 1 parport_pc 40764 0 agpgart35764 1 intel_agp parport37832 1 parport_pc cdc_ether 9984 0 bcm43xx 419548 0 firmware_class 13568 2 microcode,bcm43xx i2c_core 27520 1 i2c_i801 rtc_cmos 12064 0 snd_hda_intel 272796 1 snd_pcm82564 2 snd_pcm_oss,snd_hda_intel snd_timer 26756 2 snd_seq,snd_pcm snd58164 9 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer soundcore 11460 1 snd snd_page_alloc 13960 2 snd_hda_intel,snd_pcm usbnet 21768 1 cdc_ether rtc_core 23048 1 rtc_cmos sr_mod 19492 0 rtc_lib 7040 1 rtc_core cdrom 37020 1 sr_mod ieee80211softmac 34432 1 bcm43xx button 12432 0 ieee80211 35400 2 bcm43xx,ieee80211softmac ieee80211_crypt 9728 2 ieee80211_crypt_wep,ieee80211 ide_core 122948 1 usb_storage atl1 35980 0 mii 9344 2 usbnet,atl1 sg 37036 0 sd_mod 31104 5 ehci_hcd 34956 0 uhci_hcd 27024 0 usbcore 123372 6 usb_storage,cdc_ether,usbnet,ehci_hcd,uhci_hcd edd12996 0 ext3 131848 1 mbcache12292 1 ext3 jbd68148 1 ext3 fan 9220 0 ata_piix 21380 2 libata136776 1 ata_piix scsi_mod 140376 5 usb_storage,sr_mod,sg,sd_mod,libata thermal19848 0 processor 40744 2 acpi_cpufreq,thermal [EMAIL PROTECTED]:~ dmesg bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243 bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243 bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243 bcm43xx: PHY connected eth1: register 'cdc_ether' at usb-:00:1d.1-1, CDC Ethernet Device, 00:11:e3:b3:50:7a usbcore: registered new interface driver cdc_ether bcm43xx: Detected PHY: Analog: 3, Type 2, Revision 7 bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) bcm43xx: Radio turned off bcm43xx: Radio turned off Linux agpgart interface v0.102 (c) Dave Jones parport_pc 00:06: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] Initializing USB Mass Storage driver... scsi4 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning iTCO_vendor_support: vendor-support=0 scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning usbcore: registered new interface driver usb-storage USB Mass Storage support registered. ACPI: PCI Interrupt :00:1f.3[B] - GSI 19 (level, low) - IRQ 19 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
Re: Not working now. Debugging enabled
On Sunday 10 February 2008 04:31:37 Brian Lavender wrote: Booted kernel with latest firmware and then the older firmware. Debugging enabled, but not working now! See messages output. You installed the wrong firmware. (Man, I should write an answer script for this. ;) ) Second run http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 This is the right one. Install it. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
compat package b43 2.6.24.1
Hi all, tried the compat package. I've run make; make install; depmod -a and then tried to load the b43 driver: Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_disable_device Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_unregister_driver Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_map_mem_page Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_request_window Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_request_configuration Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol ssb_bus_pcmciabus_register Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_register_driver Feb 10 12:50:07 aragorn kernel: b43: Unknown symbol pcmcia_request_irq Kernel:2.6.24.1 The stock driver runs well. grep -i pcmcia .config # CONFIG_PCMCIA_DEBUG is not set # CONFIG_PCMCIA is not set # CONFIG_PCMCIA_XIRCOM is not set # CONFIG_PCMCIA_XIRTULIP is not set 0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) It is a powerbook. Thanks for any hint. Elimar -- Talking much about oneself can also be a means to conceal oneself. -Friedrich Nietzsche ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: compat package b43 2.6.24.1
On Sun, 10 Feb 2008 the mental interface of Michael Buesch told: It makes no sense to run compat on 2.6.24.1. Use the shipped b43 driver instead. --- /usr/src/compat-wireless-2.6/config.mk.orig 2008-02-10 13:53:46.0 +0100 +++ /usr/src/compat-wireless-2.6/config.mk 2008-02-10 13:38:03.0 +0100 @@ -23,7 +23,7 @@ # B43 uses PCMCIA only for Compact Flash. The Cardbus cards uses PCI # Example, bcm4318: # http://www.multicap.biz/wireless-lan/indoor-wlan-hardware/sdc-cf10g-80211g-compact-flash-module -CONFIG_B43_PCMCIA=y +# CONFIG_B43_PCMCIA is not set CONFIG_B43_DMA=y CONFIG_B43_PIO=y CONFIG_B43_DMA_AND_PIO_MODE=y @@ -83,7 +83,7 @@ CONFIG_SSB=m CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y -CONFIG_SSB_PCMCIAHOST=y +# CONFIG_SSB_PCMCIAHOST is not set CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y # These two are for mips works. But anyway, switched back to the shipped one. Thank you Elimar -- .~. /V\ L I N U X /( )\ Phear the Penguin ^^-^^ ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )
Pedro P wrote: Hi, My name is Javier and I'm a new in Linux. I have a problem with my wireless card Broadcom (WL-138G V2). The firmware is installed but I can't connect card. Also NetworkManager doesn't detect wireless card. Can You help me? Regards, Javier Specifications of my system: (lsmod and dmesg) bcm43xx 419548 0 The b43 driver works much better than bcm43xx. Please get and configure kernel version 2.6.24.1. You will need new firmware as well. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Better log files . Trying to figure out b43
On Sunday 10 February 2008 21:43:48 Fernando Toledo wrote: El Dom 10 Feb 2008, Michael Buesch escribió: On Sunday 10 February 2008 09:02:27 Brian Lavender wrote: On Sat, Feb 09, 2008 at 09:07:52PM -0800, Brian Lavender wrote: At one point I had the version 3 firmware working, but now it doesn't seem to be working. I checked the log files and debugging is enabled with firmware version listed. When I was using firware version 3, I unplugged and replugged the card. Seems to be working fine now with the firmware 3. DMA seems to be ok too. You are not using a v3 firmware: [ 37.171422] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) This is some v4 firmware. can help that the log say v3 or v4 like: vv b43-phy1 debug: Loading firmware version 351.126 [v3](2006-07-29 05:54:02) The v3 and v4 stuff is not enough to identify the right firmware, so it's worthless. I just sent patches to introduce a new unique ID for firmwares a few days ago. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Possible problem on b43 driver's init
On Sun, 2008-02-10 at 17:28 -0400, David Cohen wrote: Hi all, I'm here again reporting another possible problem with my wireless card and b43 driver. Please don't bite me this time, I promise I'm sending all useful inputs :D Well, the problem is: - After boot my laptop, the wireless card is not connected to my wifi network. But if I just type sudo iwlist scan, then it connects. - The same problem does not occur if I use ndiswrapper or another laptops. I believe it's a feature of mac80211. It only scans for APs under some circumstances. Setting ESSID triggers scanning. I suggest that you do it in this order: bring the interface up set the WEP key set the ESSID By the way, your AP is set for shared key authentication. It delays authentication because mac80211 tries open system first and fails. Even without that step, shared key authentication needs 4 packets to be sent, rather than 2 for open system authentication. It's believed that shared key is even less secure than open system. See e.g. http://www.networkworld.com/research/2002/0909wepprimer.html -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Possible problem on b43 driver's init
On Feb 10, 2008 9:40 PM, Pavel Roskin [EMAIL PROTECTED] wrote: On Sun, 2008-02-10 at 17:28 -0400, David Cohen wrote: Hi all, I'm here again reporting another possible problem with my wireless card and b43 driver. Please don't bite me this time, I promise I'm sending all useful inputs :D Well, the problem is: - After boot my laptop, the wireless card is not connected to my wifi network. But if I just type sudo iwlist scan, then it connects. - The same problem does not occur if I use ndiswrapper or another laptops. I believe it's a feature of mac80211. It only scans for APs under some circumstances. Setting ESSID triggers scanning. I suggest that you do it in this order: bring the interface up set the WEP key set the ESSID Hi, I tried this, but it didn't work also. By the way, your AP is set for shared key authentication. It delays authentication because mac80211 tries open system first and fails. I can wait for 5 minutes and it still doesn't authenticate. The weird point is it does not occur with ndiswrapper or with other linux laptop. Even without that step, shared key authentication needs 4 packets to be sent, rather than 2 for open system authentication. It's believed that shared key is even less secure than open system. See e.g. http://www.networkworld.com/research/2002/0909wepprimer.html It's just a home network :) . But thanks anyway, it's useful to know. Regards, David Cohen -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
