cannot set the tx power over 20 dBm, wrong contry code

Bug #604935 reported by Hveem
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

My pc is a Panasonic CF-29

My card is : ENGENIUS EMP-8602+S 802.11a/b/g 600mW ( 28 dbm )

I run Kubuntu 10.4

I cannot set the contry code to NO ( Norway )

iwconfig outputs:

wlan0 IEEE 802.11abg ESSIDff/any Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm Retry long limit:7 RTS thrff Fragment thrff Encryption keyff
Power Managementff

iwconfig wlan0 txpower 600mw Error for wireless request "Set Tx Power" (8B26) :
SET failed on device wlan0 ; Invalid argument.

i have tried: iwpriv wlan0 highpower 1 it puts out : wlan0 no private ioctls.

iwlist wlan0 txpower wlan0 unknown transmit-power information.

    Current Tx-Power=20 dBm (100 mW)

iw list Wiphy phy0

    Band 1:

        Frequencies:

    * 2412 MHz [1] (20.0 dBm)
    * 2417 MHz [2] (20.0 dBm)
    * 2422 MHz [3] (20.0 dBm)
    * 2427 MHz [4] (20.0 dBm)
    * 2432 MHz [5] (20.0 dBm)
    * 2437 MHz [6] (20.0 dBm)
    * 2442 MHz [7] (20.0 dBm)
    * 2447 MHz [8] (20.0 dBm)
    * 2452 MHz [9] (20.0 dBm)
    * 2457 MHz [10] (20.0 dBm)
    * 2462 MHz [11] (20.0 dBm)
    * 2467 MHz [12] (disabled)
    * 2472 MHz [13] (disabled)
    * 2484 MHz [14] (disabled)

        Bitrates (non-HT):

    * 1.0 Mbps
    * 2.0 Mbps (short preamble supported)
    * 5.5 Mbps (short preamble supported)
    * 11.0 Mbps (short preamble supported)
    * 6.0 Mbps
    * 9.0 Mbps
    * 12.0 Mbps
    * 18.0 Mbps
    * 24.0 Mbps
    * 36.0 Mbps
    * 48.0 Mbps
    * 54.0 Mbps

    Band 2:

        Frequencies:

    * 5180 MHz [36] (20.0 dBm) (passive scanning, no IBSS)
    * 5200 MHz [40] (20.0 dBm) (passive scanning, no IBSS)
    * 5220 MHz [44] (20.0 dBm) (passive scanning, no IBSS)
    * 5240 MHz [48] (20.0 dBm) (passive scanning, no IBSS)
    * 5260 MHz [52] (disabled)
    * 5280 MHz [56] (disabled)
    * 5300 MHz [60] (disabled)
    * 5320 MHz [64] (disabled)
    * 5500 MHz [100] (disabled)
    * 5520 MHz [104] (disabled)
    * 5540 MHz [108] (disabled)
    * 5560 MHz [112] (disabled)
    * 5580 MHz [116] (disabled)
    * 5600 MHz [120] (disabled)
    * 5620 MHz [124] (disabled)
    * 5640 MHz [128] (disabled)
    * 5660 MHz [132] (disabled)
    * 5680 MHz [136] (disabled)
    * 5700 MHz [140] (disabled)
    * 5745 MHz [149] (20.0 dBm) (passive scanning, no IBSS)
    * 5765 MHz [153] (20.0 dBm) (passive scanning, no IBSS)
    * 5785 MHz [157] (20.0 dBm) (passive scanning, no IBSS)
    * 5805 MHz [161] (20.0 dBm) (passive scanning, no IBSS)
    * 5825 MHz [165] (20.0 dBm) (passive scanning, no IBSS)

        Bitrates (non-HT):

    * 6.0 Mbps
    * 9.0 Mbps
    * 12.0 Mbps
    * 18.0 Mbps
    * 24.0 Mbps
    * 36.0 Mbps
    * 48.0 Mbps
    * 54.0 Mbps

    max # scan SSIDs: 4 Supported interface modes:

    * IBSS
    * managed
    * AP
    * AP/VLAN
    * monitor
    * mesh point

    Supported commands:

    * new_interface
    * set_interface
    * new_key
    * new_beacon
    * new_station
    * new_mpath
    * set_mesh_params
    * set_bss
    * authenticate
    * associate
    * deauthenticate
    * disassociate
    * join_ibss
    * set_wiphy_netns
    * connect
    * disconnect

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: haaken 1422 F.... knotify4
                      haaken 1446 F.... pulseaudio
                      haaken 1458 F.... kmix
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 9'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 33
   Simple ctrls : 22
Date: Tue Jul 13 10:51:06 2010
HibernationDevice: RESUME=UUID=fcc0955d-16a2-4460-8297-44ca23e62dec
Lsusb:
 Bus 004 Device 002: ID 04fc:0013 Sunplus Technology Co., Ltd ViewMate Desktop Mouse CC2201
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-29HTM50BM
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=61b75668-0109-465b-8461-b098561a98f0 ro quiet splash
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 12/08/2004
dmi.bios.vendor: Phoenix Technologies K.K.
dmi.bios.version: V3.00L11
dmi.board.name: CF29-3
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: dmi:bvnPhoenixTechnologiesK.K.:bvrV3.00L11:bd12/08/2004:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-29HTM50BM:pvr001:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF29-3:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-29HTM50BM
dmi.product.version: 001
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

Revision history for this message
Hveem (krbjhvee) wrote :
Revision history for this message
Gunnar Thielebein (lorem-ipsum) wrote :

This is also the case for setting the mode option. I was used to perform that setting with madwifi to switch from b/g to g mode to gain better wifi stability:

$ iwpriv wlan0 mode 3

With ath5k in Lucid you'll get:

"wlan0 no private ioctls."

Seems there are no flags available at all!

Changed in linux:
status: Unknown → Fix Released
Changed in linux:
importance: Unknown → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Hveem (krbjhvee) wrote :

Still the same in kernel 3.2.0-35-generic .

Revision history for this message
penalvch (penalvch) wrote :

Hveem, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-full-computer-model
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.