Bug#622842: brcm80211 not setting correct country code?
Neither I am a programmer nor I am having much time. If it only weren't latter, it wouldn't be fair to ask to other people to fix the problem. Of course, I am ready to test patches (although I did only once, I hope to be able to do it again...). Thank you any way from your suggestion. Whom I should ask for help? Otherwise, waiting till someone (who is programmer, has time and is willing to share drivers) having the same problem could be too long Best regards, Wenceslao El 05/11/11 07:27, Jonathan Nieder escribió: Hi, Wenceslao González-Viñas wrote: From your last post concerning this bug, I did not get what should be the procedure from now on. I would suggest looking at the driver code, adding printk calls to find out what it reads from the NVRAM (to confirm Ben's hypothesis), and if it is blank, coming up with a better behavior and proposing it in the form of a rough patch to the linux-wireless list. If you are not a programmer or lack time, that's okay; in that case the best thing to do is just to be ready to test patches if someone else embarks on that same adventure. Hope that helps, and sorry I don't have anything more helpful to provide. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dca3243.5010...@fisica.unav.es
Bug#622842: brcm80211 not setting correct country code?
Unfortunately I do not control it . Thank you anyway, Wenceslao El 05/11/11 14:28, Uwe Kleine-König escribió: hI, On Wed, May 11, 2011 at 08:52:51AM +0200, Wenceslao González-Viñas wrote: Neither I am a programmer nor I am having much time. If it only weren't latter, it wouldn't be fair to ask to other people to fix the problem. Of course, I am ready to test patches (although I did only once, I hope to be able to do it again...). Thank you any way from your suggestion. Whom I should ask for help? Otherwise, waiting till someone (who is programmer, has time and is willing to share drivers) having the same problem could be too long If you control the access point, switch to a lower channel. 1-11 should work. Best regards Uwe -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dca990e.9050...@fisica.unav.es
Bug#622842: brcm80211 not setting correct country code?
Dear Ben and all, From your last post concerning this bug, I did not get what should be the procedure from now on. Should the bug be reported to another package ? Or, is there something which is lacking that does not depend on you or other debian maintainers (eg. firmware or non-free packages)? I thought that the bug was going to be fixed in next release of kernel (or crda or another package related to the problem), but the fact is that the problem is still there. Is it convenient that I give more information? and in that case, what information ?? Well, thank you for all your help, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110511065548.69663y0hjpa2l...@webmail.unav.es
Bug#622842: brcm80211 not setting correct country code?
After iw reg set EU I do not get any answer in dmesg log. and if I do (after) : iw reg get , I get: country 98: (2402 - 2472 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 17) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5600 @ 40), (N/A, 20), DFS (5650 - 5710 @ 40), (N/A, 20), DFS So, something is not working properly. Thanks and best regards, Wenceslao Arend van Spriel ar...@broadcom.com ha escrito: On 04/30/2011 07:04 AM, Ben Hutchings wrote: I looked at the driver source code and there is certainly an attempt to use a country code from NVRAM. But maybe it hasn't actually been read from NVRAM at the point this is done. 'US' seems to be the default if the country code is blank. Ben. Please refer to the information on wireless.kernel.org: http://wireless.kernel.org/en/users/Drivers/brcm80211#Regulatory_Implementation You could investigate whether the NVRAM/SROM country code is indeed blank or really configured with 'US'. For the driver itself channel 13 can be used as long as your access point is transmitting beacons, because it is regarded as a passive channel. Reading the logs listed in bug #622842 I would suggest running the following command after loading the brcm80211 driver: $ iw set reg EU You should see following in the log: Apr 30 10:05:22 myhost kernel: [ 3967.072332] cfg80211: Calling CRDA for country: EU Gr. AvS Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110430103817.14736hcizu57u...@webmail.unav.es
Bug#622842: brcm80211 not setting correct country code?
I do not understand. I did of course as root. The rule in udev was not defined, though. I defined it , I restarted it , but no change. It does not matter if I use EU, ES or whatever. ?? Anyway, I think that is not iw / udev or similar problem as if I put a ralink stick, it works perfectly with regulatory domains and so. I think is a problem with driver ... (as hardware worked in MSW7) Best and thanks again, Wenceslao Arend van Spriel ar...@broadcom.com ha escrito: On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote: After iw reg set EU I do not get any answer in dmesg log. I assume you did this as root or used sudo. You may have to check whether you have the proper udev rules in place. See http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA and if I do (after) : iw reg get , I get: country 98: (2402 - 2472 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 17) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5600 @ 40), (N/A, 20), DFS (5650 - 5710 @ 40), (N/A, 20), DFS So, something is not working properly. I get country US (after iw reg set EU). I tried 'iw reg set ES' after that and another message showed up in the log: [ 1613.052044] cfg80211: Calling CRDA for country: EU [ 1845.365115] cfg80211: Pending regulatory request, waiting for it to be processed... It seems cfg80211 expects CRDA to respond to the country setting for EU. I am not familiar what modules are involved in this usage scenario. Gr. AvS Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110430154415.97676501ev5ze...@webmail.unav.es
Bug#622842: brcm80211 not setting correct country code?
Dear Ben, If you want, I could try with this modified of wireless-regdb ... Just tell me how to obtain it . Best and thanks again, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sat, 2011-04-30 at 13:30 +0200, Arend van Spriel wrote: On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote: After iw reg set EU I do not get any answer in dmesg log. I assume you did this as root or used sudo. You may have to check whether you have the proper udev rules in place. See http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA They are. and if I do (after) : iw reg get , I get: country 98: (2402 - 2472 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 17) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5600 @ 40), (N/A, 20), DFS (5650 - 5710 @ 40), (N/A, 20), DFS So, something is not working properly. I get country US (after iw reg set EU). I tried 'iw reg set ES' after that and another message showed up in the log: [ 1613.052044] cfg80211: Calling CRDA for country: EU [ 1845.365115] cfg80211: Pending regulatory request, waiting for it to be processed... It seems cfg80211 expects CRDA to respond to the country setting for EU. I am not familiar what modules are involved in this usage scenario. I added 'EU' to wireless-regdb in Debian for backward-compatibility. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110430154823.19371xuwpgd2e...@webmail.unav.es
Bug#622842: brcm80211 not setting correct country code?
So, then this means that the problem is still there ... ... What else could I try? Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sat, 2011-04-30 at 15:48 +0200, Wenceslao González-Viñas wrote: Dear Ben, If you want, I could try with this modified of wireless-regdb ... Just tell me how to obtain it . [...] I did that before uploading the first version, so you already have it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110430161214.1080453b8p5c9...@webmail.unav.es
Bug#622842: firmware-brcm80211: not getting an associated point
Dear all, After installing CRDA I am not able to have regulatory domain = EU in brcm80211 .Consequently, I cannot connect to any 2.472 GHz wifi. The dmesg log is the following (from just before modprobe brcm80211 in a way that you can see the good regulatory domain for cfg80211 !!!; see specially [ 76.098256]): [ 57.916230] cfg80211: Calling CRDA to update world regulatory domain [ 58.003989] cfg80211: World regulatory domain updated: [ 58.003994] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 58.003998] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 58.004021] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 58.004025] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 58.004028] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 58.004031] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 58.004171] cfg80211: Calling CRDA for country: EU [ 58.009303] cfg80211: Regulatory domain changed to country: EU [ 58.009308] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 58.009312] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 58.009315] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 2000 mBm) [ 58.009318] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 58.009321] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 2700 mBm) [ 75.961782] brcm80211: module is from the staging directory, the quality is unknown, you have been warned. [ 75.967427] brcm80211 :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 75.967435] brcm80211 :03:00.0: setting latency timer to 64 [ 76.012899] Found chip type AI (0x13814313) [ 76.016022] Changing max_res_mask to 0x [ 76.016024] Changing min_res_mask to 0x200d [ 76.022133] Applying 4313 WARs [ 76.023030] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x51a macaddr: 88:25:2c:4e:9e:34 [ 76.097426] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 76.098256] wl_set_hint: Sending country code US to MAC80211 [ 76.098263] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver (1.82.8.0) (Compiled at 04:19:31 on Apr 7 2011) [ 76.098566] cfg80211: Calling CRDA for country: US [ 76.110176] cfg80211: Current regulatory domain intersected: [ 76.110180] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 76.110184] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 76.110187] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 1700 mBm) [ 76.110191] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 76.110194] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (N/A, 2000 mBm) [ 76.110197] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (N/A, 2000 mBm) -- Thank you for your help. Wenceslao Wenceslao González-Viñas w...@fisica.unav.es ha escrito: Here it is: result from lspci -vv: - 03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) Subsystem: Broadcom Corporation Device 051a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d030 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME- Capabilities: [58] Vendor Specific Information: Len=78 ? Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 4us, L1 64us ClockPM+ Surprise- LLActRep+ BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk
Bug#622842: firmware-brcm80211: not getting an associated point
In Spain (PC - City company). It is a Dell Inspiron M101z (service tag CHL0SM1) . BTW, in Windows 7, it worked perfectly. But I removed it installing Debian Wheezy. Best and thanks, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Fri, 2011-04-29 at 16:48 +0200, Wenceslao González-Viñas wrote: Dear all, After installing CRDA I am not able to have regulatory domain = EU in brcm80211 .Consequently, I cannot connect to any 2.472 GHz wifi. The dmesg log is the following (from just before modprobe brcm80211 in a way that you can see the good regulatory domain for cfg80211 !!!; see specially [ 76.098256]): [...] It looks like the device has a country code of US. It could be that the driver is not reading the country code correctly, though. Where did you buy this hardware? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- Wenceslao González-Viñas e-mail: w...@fisica.unav.es http://fisica.unav.es/~wens/ (personal) http://fisica.unav.es/gmm/ (group) FAX:+34 948.425.649 phn:+34 948.425.600 ext:6385 / 6603 Depto. Física y Matemática Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea s/n E-31080 Pamplona, Navarra, Spain Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110429173944.10906p14p6bdi...@webmail.unav.es
Bug#622842: firmware-brcm80211: not getting an associated point
Here it is: result from lspci -vv: - 03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) Subsystem: Broadcom Corporation Device 051a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d030 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME- Capabilities: [58] Vendor Specific Information: Len=78 ? Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 4us, L1 64us ClockPM+ Surprise- LLActRep+ BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number 00-00-2c-ff-ff-4e-88-25 Capabilities: [16c v1] Power Budgeting ? --- and result from dmesg: [ 330.205983] brcm80211: module is from the staging directory, the quality is unknown, you have been warned. [ 330.212186] brcm80211 :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 330.212195] brcm80211 :03:00.0: setting latency timer to 64 [ 330.268237] Found chip type AI (0x13814313) [ 330.271328] Changing max_res_mask to 0x [ 330.271330] Changing min_res_mask to 0x200d [ 330.277446] Applying 4313 WARs [ 330.278330] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x51a macaddr: 88:25:2c:4e:9e:34 [ 330.283578] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 330.285363] wl_set_hint: Sending country code US to MAC80211 [ 330.285371] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver (1.82.8.0) (Compiled at 04:19:31 on Apr 7 2011) [ 330.365121] ADDRCONF(NETDEV_UP): wlan0: link is not ready -- By the way, before I used 'modprobe cfg80211 ieee80211_regdom=EU' . Perhaps the problem comes from that and line (dmesg) 330.285363 ? I need channel 13 ... Best regards and thanks, Wenceslao maximilian attems m...@stro.at ha escrito: reassign 622842 linux-2.6 stop On Fri, Apr 15, 2011 at 09:07:30AM +0200, Wenceslao wrote: Package: firmware-brcm80211 Version: 0.29 Severity: important module brcm80211 is not getting the associated point of a wifi, although it is properly detected. With a usb wifi stick (a ralink one) is detecting and attaching properly. so you properly know the module and report against firmware, *woow*. attach relevant dmesg or lspci output unless proven as currently this can be close right away. kind regards -- maks Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian
Bug#622842: firmware-brcm80211: not getting an associated point
Package: firmware-brcm80211 Version: 0.29 Severity: important module brcm80211 is not getting the associated point of a wifi, although it is properly detected. With a usb wifi stick (a ralink one) is detecting and attaching properly. Best regards and thank you, Wenceslao -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.98.8 tools for generating an initramfs ii linux-image-2.6.38-2-amd64 [l 2.6.38-3 Linux 2.6.38 for 64-bit PCs -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110415070730.4178.6175.reportbug@calpurnia
Bug#594561: State of the bug 594561
Ok!, I did more or less the things you told me. I was not able to patch the source in a standard way; but I changed the source code by hand, I recompile the kernel and I used the resulting module with insmod rt2870.ko ieee80211_regdom=EU Please note that I did not reinstall compiled kernel (so I had to use insmod instead your suggested modprobe) and that the module to use was rt2870 (and not 2860). Of course I patched from 2860 folder since the files were common. Now it works perfect ! So, you were right !!! Many thanks! My question now is how, and when this will become automatized in the kernel which comes from the debian distribution ? Thanks again and happy new year! Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Thu, 2010-12-23 at 16:33 +0100, Wenceslao González-Viñas wrote: I patched same file as before and i get the following error. I attach original and rejection file.. patch rt2870sta.ko 0001-rt28x0-Add-ieee80211_regdom-module-parameter-mimicki.patch [...] Why are you trying to patch the module? You need to patch its source code, following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101226154254.11307u238hfdl...@webmail.unav.es
Bug#594561: State of the bug 594561
Ok! I didn't understand this in your last email (I thought it was two step thing and the first was what I did). It does not seem easy. I will try and say ... Thanks, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Thu, 2010-12-23 at 16:33 +0100, Wenceslao González-Viñas wrote: I patched same file as before and i get the following error. I attach original and rejection file.. patch rt2870sta.ko 0001-rt28x0-Add-ieee80211_regdom-module-parameter-mimicki.patch [...] Why are you trying to patch the module? You need to patch its source code, following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101225191600.20922fngfbdvf...@webmail.unav.es
Bug#594561: State of the bug 594561
Dear Ben, Module crc_ccitt was already loaded. (anyway I removed and loaded again). After insmod rt2870sta it gave same error and kern.log gave: rt2870sta: module has no symbols (stripped?) Thanks and sorry not to cc to bug error address in previous email. Best, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: [Please remember to reply-to-all, including the bug address.] On Sun, 2010-11-28 at 10:42 +0100, Wenceslao González-Viñas wrote: Dear Ben, thank you very much! In fact there is some problem: It gives this error: insmod: error inserting 'rt2870sta.ko': -1 Invalid module format There should be some more information in the kernel log; please report that. Actually, first try running 'modprobe crc_ccitt' before the insmod command. Could this be due to that I updated the system. Now, I have kernel: Linux box 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux [...] I don't think so. Whenever we do make an incompatible change, we increase the 'ABI version' which is the number that appears after the upstream version above, i.e. currently 5. We have not made such a change since package version 2.6.32-12 released in May. It's quite possible that I made a mistake here but it worked for me. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101128212040.111324m4u2hvt...@webmail.unav.es
Bug#594561: State of the bug 594561
Here it is the output of dmesg (attached). Best, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-11-28 at 21:20 +0100, Wenceslao González-Viñas wrote: Dear Ben, Module crc_ccitt was already loaded. (anyway I removed and loaded again). After insmod rt2870sta it gave same error and kern.log gave: rt2870sta: module has no symbols (stripped?) Sorry, I ran 'strip' on this file to remove unnecessary data. I forgot that it removes too much from kernel modules. I've put a fixed version up at the same URL. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es [ 4685.815040] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned. [ 4685.821411] rtusb init --- [ 4685.821655] === pAd = c9001149c000, size = 502256 === [ 4685.821658] -- RTMPAllocAdapterBlock, Status=0 [ 4685.823263] usbcore: registered new interface driver rt2870 [ 4685.839920] usb 1-8: firmware: requesting rt3070.bin [ 4686.112855] -- RTMPAllocTxRxRingMemory, Status=0 [ 4686.114489] --RTUSBVenderReset [ 4686.114614] --RTUSBVenderReset [ 4686.393575] 1. Phy Mode = 0 [ 4686.393579] 2. Phy Mode = 0 [ 4686.393582] NVM is Efuse and its size =2d[2d0-2fc] [ 4686.405449] [ 4686.405450] Block 0:3070 0101 2200 a72d [ 4686.407946] Block 0:ddfb [ 4686.410571] Block 1: 0511 0002 [ 4686.413195] Block 1: 0110 0330 [ 4686.415695] Block 2: 0005 [ 4686.418194] Block 2: [ 4686.420694] Block 3: 0707 0707 0707 [ 4686.423194] Block 3:0707 0707 0707 0707 [ 4686.425695] Block 4: [ 4686.428195] Block 4: c5ff [ 4686.430693] Block 5:a5b5 627a 3a50 012a [ 4686.433193] Block 5: [ 4686.435693] Block 6: [ 4686.438192] Block 6: [ 4686.440692] Block 7: 6688 6688 [ 4686.443191] Block 7: 6688 6688 [ 4686.445692] Block 8:0112 0200 4000 [ 4686.448192] Block 8:083a a701 0101 0201 [ 4686.450690] Block 9:0103 060a 0200 [ 4686.453190] Block 9:4000 0001 0209 0043 [ 4686.455690] Block a:0101 8000 09e1 0004 [ 4686.458189] Block a:0700 05ff 0507 [ 4686.460689] Block b:0281 0200 0700 0105 [ 4686.463188] Block b:0002 0002 0507 0202 [ 4686.465688] Block c:0200 0700 0305 0002 [ 4686.468189] Block c:0002 0507 0204 0200 [ 4686.470687] Block d:0700 0505 0002 0002 [ 4686.473187] Block d:0507 0206 0200 [ 4686.475686] Block e:6152 696c 6b6e 2020 [ 4686.478185] Block e:6957 6572 656c 7373 [ 4686.480686] Block f:3120 6e31 2020 2020 [ 4686.483185] Block f:2e31 3030 [ 4686.485685] Block 10:0112 0200 4000 [ 4686.488186] Block 10:148f 3070 0001 0706 [ 4686.490684] Block 11:0108 060a 0200 [ 4686.493184] Block 11:4000 0001 0209 0020 [ 4686.495684] Block 12:0101 8000 09e1 0004 [ 4686.498182] Block 12:0200 0608 0a50 0507 [ 4686.500682] Block 13:0281 0200 0700 0105 [ 4686.503182] Block 13:0002 0002 [ 4686.505682] Block 14: [ 4686.508182] Block 14: [ 4686.510681] Block 15: [ 4686.513181] Block 15: [ 4686.515681] Block 16: 003f [ 4686.518305] Block 16: [ 4686.520805] Block 17:6000 a270 a2ff 7060 [ 4686.523305] Block 17:ffa2 ffa2 [ 4686.525805] Block 18:0304 0409 [ 4686.528305] Block 18: [ 4686.530803] Block 19: [ 4686.533303] Block 19: [ 4686.535803] Block 1a: [ 4686.538302] Block 1a: [ 4686.540802] Block 1b: [ 4686.543302] Block 1b: [ 4686.545802] Block 1c: [ 4686.548302] Block 1c: [ 4686.550801] Block 1d: [ 4686.553300] Block 1d: [ 4686.555800] Block 1e:030e 0052 0061 006c [ 4686.558549] Block 1e:0069 006e 006b [ 4686.561049] Block 1f:031e 0038 0030 0032 [ 4686.563548] Block 1f:002e 0031 0031 0020 [ 4686.566048] Block 20:006e 0020 0057 004c [ 4686.568549] Block 20:0041 004e [ 4686.571047] Block 21:0304 0409 [ 4686.573547] Block 21: [ 4686.576050] Block 22: 0308 0031 002e [ 4686.578546] Block 22:0030 [ 4686.581046] Block 23: [ 4686.583545] Block 23: [ 4686.586046] Block 24: [ 4686.588546] Block 24: [ 4686.591044] Block 25: [ 4686.593545] Block 25: [ 4686.596048] Block 26: [ 4686.598543] Block 26: [ 4686.601043] Block 27: [ 4686.603542] Block 27: [ 4686.606042] Block 28:
Bug#594561: State of the bug 594561
Hereby I attach new output, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-11-28 at 22:38 +0100, Wenceslao González-Viñas wrote: Here it is the output of dmesg (attached). Sorry, but there's something I missed - there are two different ways of reading the ROM. I have put yet another version at the same URL, which will read the ROM in the other way. Please load it and report the new log messages. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- Este mensaje ha sido enviado desde https://webmail.unav.es [ 8695.930670] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned. [ 8695.937697] rtusb init --- [ 8695.937909] === pAd = c90011336000, size = 502256 === [ 8695.937912] -- RTMPAllocAdapterBlock, Status=0 [ 8695.940195] usbcore: registered new interface driver rt2870 [ 8695.948338] usb 1-8: firmware: requesting rt3070.bin [ 8696.220278] -- RTMPAllocTxRxRingMemory, Status=0 [ 8696.221828] --RTUSBVenderReset [ 8696.221953] --RTUSBVenderReset [ 8696.500913] 1. Phy Mode = 0 [ 8696.500917] 2. Phy Mode = 0 [ 8696.500920] NVM is Efuse and its size =2d[2d0-2fc] [ 8696.512787] [ 8696.512789] Block 0:3070 0130 0101 0001 [ 8696.515285] Block 0:2200 2d22 a72d 00a7 [ 8696.517785] Block 1:ddfb 00dd [ 8696.520411] Block 1: [ 8696.522784] Block 2: [ 8696.524783] Block 2: [ 8696.526783] Block 3: [ 8696.528783] Block 3: [ 8696.530783] Block 4: [ 8696.532783] Block 4: [ 8696.534782] Block 5: [ 8696.536782] Block 5: [ 8696.538907] Block 6: [ 8696.541406] Block 6:0511 0205 0002 [ 8696.543906] Block 7: 10ff 0110 0001 [ 8696.546408] Block 7: 3000 0330 0003 [ 8696.548905] Block 8: 00ff [ 8696.551405] Block 8: 0500 0005 [ 8696.553905] Block 9: [ 8696.556404] Block 9: ff00 00ff [ 8696.558904] Block a: 0700 0707 0007 [ 8696.561404] Block a:0707 0707 0707 0007 [ 8696.563903] Block b:0707 0707 0707 0007 [ 8696.566402] Block b:0707 0707 0707 0007 [ 8696.568902] Block c: 00ff [ 8696.571402] Block c: 00ff [ 8696.573902] Block d: 00ff [ 8696.576402] Block d: c5ff 00c5 [ 8696.578901] Block e:a5b5 7aa5 627a 0062 [ 8696.581401] Block e:3a50 2a3a 012a 0001 [ 8696.583901] Block f: 00ff [ 8696.586399] Block f: 00ff [ 8696.588775] Block 10: [ 8696.590774] Block 10: [ 8696.592774] Block 11: [ 8696.594774] Block 11: [ 8696.596773] Block 12: [ 8696.598772] Block 12: [ 8696.600773] Block 13: [ 8696.602773] Block 13: [ 8696.604773] Block 14: [ 8696.606772] Block 14: [ 8696.608771] Block 15: [ 8696.610771] Block 15: [ 8696.612771] Block 16: [ 8696.614771] Block 16: [ 8696.616770] Block 17: [ 8696.618770] Block 17: [ 8696.620894] Block 18: [ 8696.622894] Block 18: [ 8696.624894] Block 19: [ 8696.626894] Block 19: [ 8696.629018] Block 1a: [ 8696.631518] Block 1a: [ 8696.634018] Block 1b: [ 8696.636520] Block 1b: 5500 0055 [ 8696.639017] Block 1c: 88aa 6688 0066 [ 8696.641517] Block 1c: 88aa 6688 0066 [ 8696.644039] Block 1d: 88aa 6688 0066 [ 8696.646516] Block 1d: 88aa 6688 0066 [ 8696.649140] Block 1e: [ 8696.651140] Block 1e: [ 8696.653265] Block 1f: [ 8696.655264] Block 1f: [ 8696.657265] Block 20: [ 8696.659264] Block 20: [ 8696.661264] Block 21: [ 8696.663263] Block 21: [ 8696.665389] Block 22: [ 8696.667388] Block 22: [ 8696.669387] Block 23: [ 8696.671387] Block 23: [ 8696.673387] Block 24: [ 8696.675386] Block 24: [ 8696.677386] Block 25: [ 8696.679386] Block 25: [ 8696.681510] Block 26: [ 8696.683510] Block 26: [ 8696.685510] Block 27: [ 8696.687761] Block 27: [ 8696.689760] Block 28: [ 8696.691759] Block 28: [ 8696.693759] Block 29:
Bug#594561: State of the bug 594561
Could someone tell me what is the state of this bug? What can I do to help to fix the problem? Thank you very much in advanced, best regards, Wenceslao PS: I am using testing (squeeze) Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101124222934.202937akb3vko...@webmail.unav.es
Bug#594561: Fwd: Re: Bug#594561: 594561 should be reopened
Dear Ben, Do you need more information from my side in order to fix the problem? I see that the bug is reopened, but I do not know how I can help to solve it ... Best, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es ---BeginMessage--- I tried in another computer (same kernel and so on ...) and happened the same.. In this case ralink was on wlan1 ls -l /sys/class/net/wlan1/device/*/driver lrwxrwxrwx 1 root root 0 Oct 4 06:35 /sys/class/net/wlan1/device/1-1:1.0/driver - ../../../../../../bus/usb/drivers/rt2870 Best, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-10-03 at 22:29 +0200, Wenceslao González-Viñas wrote: readlink /sys/class/net/wlan0/device/driver ../../../../../bus/usb/drivers/usb Oh, sorry, make that: ls -l /sys/class/net/wlan0/device/*/driver Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es ---End Message---
Bug#594561: 594561 should be reopened
Dear all, Bug n. 594561 is not fixed in version linux-2.6/2.6.32-23 (testing). The kernel detects the Wifi stick , but only same channels as before and nothing about freq. 2.472 ... Sorry for not reporting before, as it was impossible for me to check until now. Best regards, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101003203702.210163800l9xb...@webmail.unav.es
Bug#594561: 594561 should be reopened
In fact, I think that it is a variant (rt3070) of rt2870. But anyway, I just connect the wifi stick to the computer (after updating kernel and rebooting). It starts to blink and detects the wifi signal, but not the needed channel (13). I type: iwlist wlan0 frequency and in the answer there is only frequencies below 2.462 (so same channels as before). BTW, it is a wifi USB stick, not a pci device ... Thanks for everything. Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-10-03 at 20:37 +0200, Wenceslao González-Viñas wrote: Dear all, Bug n. 594561 is not fixed in version linux-2.6/2.6.32-23 (testing). The kernel detects the Wifi stick , but only same channels as before and nothing about freq. 2.472 ... Please explain how you are testing this. Sorry for not reporting before, as it was impossible for me to check until now. I just tested on a Ralink PCI device with the rt2860sta driver, which shares the channel selection code with rt2870sta. I can select channel 13 / frequency 2.472 GHz now. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010100321.2072712hnfzen...@webmail.unav.es
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
*dp*ic*isc*ip* alias: usb:v14B2p3C28d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C06d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0017d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1731d*dc*dsc*dp*ic*isc*ip* alias: usb:v177Fp0302d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0164d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0163d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0162d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7512d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0039d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2770d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2770d*dc*dsc*dp*ic*isc*ip* depends:usbcore,crc-ccitt staging:Y vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: mac:rt28xx: wireless mac addr (charp) dmesg - [ 419.572015] usb 1-7: new high speed USB device using ehci_hcd and address 6 [ 419.721989] usb 1-7: New USB device found, idVendor=083a, idProduct=a701 [ 419.721994] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 419.721998] usb 1-7: Product: 802.11 n WLAN [ 419.722001] usb 1-7: Manufacturer: Ralink [ 419.722004] usb 1-7: SerialNumber: 1.0 [ 419.722140] usb 1-7: configuration #1 chosen from 1 choice [ 419.724643] === pAd = c9001114e000, size = 502256 === [ 419.724647] -- RTMPAllocAdapterBlock, Status=0 [ 419.777871] usb 1-7: firmware: requesting rt3070.bin [ 419.802850] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.802855] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.802858] rt28xx Initialized fail! [ 419.836241] usb 1-7: firmware: requesting rt3070.bin [ 419.839037] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.839042] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.839048] rt28xx Initialized fail! [ 419.839380] usb 1-7: firmware: requesting rt3070.bin [ 419.843020] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.843026] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.843033] rt28xx Initialized fail! [ 419.854873] usb 1-7: firmware: requesting rt3070.bin [ 419.858756] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.858762] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.858768] rt28xx Initialized fail! [ 479.965042] usb 1-7: firmware: requesting rt3070.bin [ 479.968119] usb 1-7: firmware file rt3070.bin request failed (-2) [ 479.968125] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 479.968132] rt28xx Initialized fail! [ 713.978047] usb 1-7: firmware: requesting rt3070.bin [ 713.981339] usb 1-7: firmware file rt3070.bin request failed (-2) [ 713.981345] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 713.981352] rt28xx Initialized fail! THANK YOU for everything. Kind regards, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Fri, 2010-08-27 at 17:28 +0200, Wenceslao González-Viñas wrote: I installed in fact both (without putting them in automatic loading after boot). With both drivers happen the same. I may be wrong, but I tried very much to do in such a way they do not interfere. In the case of Debian compliant was the non-free section of Squeeze (testing), version 0.26. [...] That is the version of the *firmware* package, firmware-ralink. The driver is in the *kernel* package, linux-image-2.6.32-5-686 (and similarly named packages for different processor types). Please ensure you have that kernel package installed and uninstall Ralink's driver. Then reboot and test whether the frequency 2.472 GHz is supported. To confirm that you are using the right driver, please send the output of these commands: readlink /sys/class/net/wlan0/device/driver /sbin/modinfo rt2870sta dmesg Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100828103521.51755puhmi53b...@webmail.unav.es
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz (2)
: usb:v0DF6p002Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0017d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1731d*dc*dsc*dp*ic*isc*ip* alias: usb:v177Fp0302d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0164d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0163d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0162d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7512d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0039d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2770d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2770d*dc*dsc*dp*ic*isc*ip* depends:usbcore,crc-ccitt staging:Y vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: mac:rt28xx: wireless mac addr (charp) dmesg - [ 71.208021] usb 1-7: new high speed USB device using ehci_hcd and address 6 [ 71.358274] usb 1-7: New USB device found, idVendor=083a, idProduct=a701 [ 71.358279] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 71.358283] usb 1-7: Product: 802.11 n WLAN [ 71.358286] usb 1-7: Manufacturer: Ralink [ 71.358289] usb 1-7: SerialNumber: 1.0 [ 71.358428] usb 1-7: configuration #1 chosen from 1 choice Thanks again, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Fri, 2010-08-27 at 17:28 +0200, Wenceslao González-Viñas wrote: I installed in fact both (without putting them in automatic loading after boot). With both drivers happen the same. I may be wrong, but I tried very much to do in such a way they do not interfere. In the case of Debian compliant was the non-free section of Squeeze (testing), version 0.26. [...] That is the version of the *firmware* package, firmware-ralink. The driver is in the *kernel* package, linux-image-2.6.32-5-686 (and similarly named packages for different processor types). Please ensure you have that kernel package installed and uninstall Ralink's driver. Then reboot and test whether the frequency 2.472 GHz is supported. To confirm that you are using the right driver, please send the output of these commands: readlink /sys/class/net/wlan0/device/driver /sbin/modinfo rt2870sta dmesg Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100828111656.34551sie3njvh...@webmail.unav.es
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
*ic*isc*ip* alias: usb:v14B2p3C07d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C11d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pED06d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C28d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C06d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0017d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1731d*dc*dsc*dp*ic*isc*ip* alias: usb:v177Fp0302d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0164d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0163d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0162d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7512d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0039d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2770d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2770d*dc*dsc*dp*ic*isc*ip* depends:usbcore,crc-ccitt staging:Y vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: mac:rt28xx: wireless mac addr (charp) dmesg - [ 1280.308022] usb 1-7: new high speed USB device using ehci_hcd and address 11 [ 1280.457583] usb 1-7: New USB device found, idVendor=083a, idProduct=a701 [ 1280.457588] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1280.457592] usb 1-7: Product: 802.11 n WLAN [ 1280.457595] usb 1-7: Manufacturer: Ralink [ 1280.457598] usb 1-7: SerialNumber: 1.0 [ 1280.457728] usb 1-7: configuration #1 chosen from 1 choice [ 1291.558512] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned. [ 1291.565018] rtusb init --- [ 1291.565073] usbcore: registered new interface driver rt2870 [ 1291.566856] === pAd = c90011223000, size = 502256 === [ 1291.566860] -- RTMPAllocAdapterBlock, Status=0 [ 1291.603487] usb 1-7: firmware: requesting rt3070.bin [ 1291.885517] -- RTMPAllocTxRxRingMemory, Status=0 [ 1291.887041] --RTUSBVenderReset [ 1291.887166] --RTUSBVenderReset [ 1292.169749] 1. Phy Mode = 0 [ 1292.169753] 2. Phy Mode = 0 [ 1292.169756] NVM is Efuse and its size =2d[2d0-2fc] [ 1292.242864] 3. Phy Mode = 0 [ 1292.248738] RTMPSetPhyMode: channel is out of range, use first channel=1 [ 1292.248743] MCS Set = 00 00 00 00 00 [ 1292.309104] rt28xx_init, Status=0 [ 1292.310601] 0x1300 = 00073200 [ 1297.383818] ===rt_ioctl_giwscan. 2(2) BSS returned, data-length = 370 [ 1302.776005] wlan0: no IPv6 routers present [ 1318.108113] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 698 [ 1348.108101] ===rt_ioctl_giwscan. 5(5) BSS returned, data-length = 929 Finally I run this: iwlist wlan0 channel wlan0 11 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Current Frequency:2.412 GHz (Channel 1) So, I cannot get 2.472GHz freq Thanks, Wenceslao Why did you do that? Do you still think firmware-ralink is a driver? It is not. You do need firmware-ralink installed. Reinstall it and run those commands again. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100828172050.25585ua697m5t...@webmail.unav.es
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
Package: firmware-ralink Version: 0.26 Severity: important I recently bought a Wifi stick (SMCWUSBS-N3) which uses the chip Ralink RT3070, because they say it works in Linux. I tried to install the driver (through firmware-ralink package and through compiling the driver ralink offers in their website) and finally it is detected (thanks to posts in internet ... those drivers are not working out of the box). The problem is that I cannot see my AP (which is in 2.472GHz; channel 13). I can see the AP (and connect to it) at the same position in another computer (internal wifi) and, in the same computer and stick with Windows 7 (now completely removed ;-) ). After some days of work, I obtain the following information: the stick is only capable (under my conf. in Debian) to see 11 channels in the 2.4GHz range (NOT including 2.472GHz). Also the APs detected (neighbours) are with signals much weaker than in the same computer and stick and position in Windows 7. Another thing that could help the diagnosis is that iw is not detecting any interface or device. Current conf. of computer: Debian Squeeze Linux Kernel 2.6.32-5 Network-Manager I blacklist in modprobe.d through specific files: rt2800(usb,lib), rt2x00, etc Sorry for not providing all the information, but I am in another computer so I cannot access now the logs. If you think something specific is needed I can put in pendrive and submit here. I checked the internet and although this has been seen some times the solutions they give are not working Thanks a lot for the help !! Wenceslao -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100827072922.19807.12194.report...@telcontar.fisica.unav.es
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
Hello, to tell you the truth I was scared at looking at the http://thread.gmane.org/gmane.linux.debian.devel.kernel/54624/ . The reason is that probably you are right, but unfortunately I am no such an expert to get a solution from the thread. I am looking in the packages repositories of debian an I am not able to find crda. On the other hand in the package contents search the 80211 stuff is related to linux headers, which I have installed. One thing that might help is that when I used iw list before, I got something like nl80211 not found. After that, I thought that one module should be loaded. I loaded mac80211. I checked it was (and I got mac and cfg). Now, when I type iw list, I got nothing (neither error nor result). Everything and what you told me makes me feel that the solution is nearby and easy; but I don't know how to go on ... Thanks a lot, Wenceslao El 08/27/10 10:15, Uwe Kleine-König escribió: Hello, On Fri, Aug 27, 2010 at 09:29:22AM +0200, Wenceslao wrote: Package: firmware-ralink Version: 0.26 Severity: important I recently bought a Wifi stick (SMCWUSBS-N3) which uses the chip Ralink RT3070, because they say it works in Linux. I tried to install the driver (through firmware-ralink package and through compiling the driver ralink offers in their website) and finally it is detected (thanks to posts in internet ... those drivers are not working out of the box). The problem is that I cannot see my AP (which is in 2.472GHz; channel 13). I can see the AP (and connect to it) at the same position in another computer (internal wifi) and, in the same computer and stick with Windows 7 (now completely removed ;-) ). After some days of work, I obtain the following information: the stick is only capable (under my conf. in Debian) to see 11 channels in the 2.4GHz range (NOT including 2.472GHz). Also the APs detected (neighbours) are with signals much weaker than in the same computer and stick and position in Windows 7. Another thing that could help the diagnosis is that iw is not detecting any interface or device. Current conf. of computer: Debian Squeeze Linux Kernel 2.6.32-5 Network-Manager I blacklist in modprobe.d through specific files: rt2800(usb,lib), rt2x00, etc Sorry for not providing all the information, but I am in another computer so I cannot access now the logs. If you think something specific is needed I can put in pendrive and submit here. I checked the internet and although this has been seen some times the solutions they give are not working This might be related to http://thread.gmane.org/gmane.linux.debian.devel.kernel/54624/ ? Any news there? Best regards Uwe -- Wenceslao González-Viñas e-mail: w...@fisica.unav.es http://fisica.unav.es/~wens/ (personal) http://fisica.unav.es/gmm/ (group) FAX:+34 948.425.649 phn:+34 948.425.600 ext:6385 / 6603 Depto. Física y Matemática Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea s/n E-31080 Pamplona, Navarra, Spain -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c777f1e.5000...@fisica.unav.es
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
I installed in fact both (without putting them in automatic loading after boot). With both drivers happen the same. I may be wrong, but I tried very much to do in such a way they do not interfere. In the case of Debian compliant was the non-free section of Squeeze (testing), version 0.26. Wenceslao El 08/27/10 17:20, Ben Hutchings escribió: On Fri, Aug 27, 2010 at 09:29:22AM +0200, Wenceslao wrote: Package: firmware-ralink Version: 0.26 Severity: important I recently bought a Wifi stick (SMCWUSBS-N3) which uses the chip Ralink RT3070, because they say it works in Linux. I tried to install the driver (*through firmware-ralink package* and through compiling the driver ralink offers in their website) and finally it is detected (thanks to posts in internet ... those drivers are not working out of the box). [...] So far as I know, channel limits are imposed by the driver, not the firmware. Since you are using the driver from Ralink, not from Debian, you have not (yet) found a bug in Debian. There is a version of the driver (rt2870sta) included in our packages of Linux 2.6.32, which are available in unstable, testing and lenny-backports. This has combined support for both RT2870 and RT3070 controllers. Please remove Ralink's version of the driver, install one of those packages and test whether the bug exists in this version of the driver. Ben. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c77d993.2010...@fisica.unav.es
