[opensuse-kernel] intel ipw5300 wireless@5GHz and 2.6.29-rc3-git3-master_20090206202623_68c9d1c2-default
Hi, is there anyone out there, who runs a wireless connection on 2.6.29-rc3-git3- master_20090206202623_68c9d1c2-default using the 5GHz range on for example channel 36. This works with 2.6.27, but on 2.6.29 it is broken ( probably due to the new regulary framework). On 2.6.27 "iw list" shows : -------------------------------{snip]---------------------------------------------------------------------------------- Wiphy phy0 Band 1: Frequencies: * 2412 MHz * 2417 MHz * 2422 MHz * 2427 MHz * 2432 MHz * 2437 MHz * 2442 MHz * 2447 MHz * 2452 MHz * 2457 MHz * 2462 MHz * 2467 MHz (disabled, passive scanning, no IBSS) * 2472 MHz (disabled, passive scanning, no IBSS) Bitrates: * 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 * 60.0 Mbps Band 2: Frequencies: * 5180 MHz (passive scanning, no IBSS) * 5200 MHz (passive scanning, no IBSS) * 5220 MHz (passive scanning, no IBSS) * 5240 MHz (passive scanning, no IBSS) * 5260 MHz (passive scanning, no IBSS, radar detection) * 5280 MHz (passive scanning, no IBSS, radar detection) * 5300 MHz (passive scanning, no IBSS, radar detection) * 5320 MHz (passive scanning, no IBSS, radar detection) * 5500 MHz (disabled, passive scanning, no IBSS, radar detection) * 5520 MHz (disabled, passive scanning, no IBSS, radar detection) * 5540 MHz (disabled, passive scanning, no IBSS, radar detection) * 5560 MHz (disabled, passive scanning, no IBSS, radar detection) * 5580 MHz (disabled, passive scanning, no IBSS, radar detection) * 5600 MHz (disabled, passive scanning, no IBSS, radar detection) * 5620 MHz (disabled, passive scanning, no IBSS, radar detection) * 5640 MHz (disabled, passive scanning, no IBSS, radar detection) * 5660 MHz (disabled, passive scanning, no IBSS, radar detection) * 5680 MHz (disabled, passive scanning, no IBSS, radar detection) * 5700 MHz (disabled, passive scanning, no IBSS, radar detection) * 5745 MHz (passive scanning, no IBSS) * 5765 MHz (passive scanning, no IBSS) * 5785 MHz (passive scanning, no IBSS) * 5805 MHz (passive scanning, no IBSS) * 5825 MHz (passive scanning, no IBSS) Bitrates: * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps * 60.0 Mbps -------------------------------{snip]---------------------------------------------------------------------------------- on 2.6.29-rc3-git3-master_20090206202623_68c9d1c2-default with iw updated to running lastest stable version iw-0.9.9 and doing a "iw reg set DE" before the "iw list" it shows : -------------------------------{snip]---------------------------------------------------------------------------------- Wiphy phy0 Band 1: Frequencies: * 2412 MHz (passive scanning, no IBSS) * 2417 MHz (passive scanning, no IBSS) * 2422 MHz (passive scanning, no IBSS) * 2427 MHz (passive scanning, no IBSS) * 2432 MHz (passive scanning, no IBSS) * 2437 MHz (passive scanning, no IBSS) * 2442 MHz (passive scanning, no IBSS) * 2447 MHz (passive scanning, no IBSS) * 2452 MHz (passive scanning, no IBSS) * 2457 MHz (passive scanning, no IBSS) * 2462 MHz (passive scanning, no IBSS) * 2467 MHz (disabled, passive scanning, no IBSS) * 2472 MHz (disabled, passive scanning, no IBSS) Bitrates: * 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 * 60.0 Mbps Band 2: Frequencies: * 5180 MHz (disabled, passive scanning, no IBSS) * 5200 MHz (disabled, passive scanning, no IBSS) * 5220 MHz (disabled, passive scanning, no IBSS) * 5240 MHz (disabled, passive scanning, no IBSS) * 5260 MHz (disabled, passive scanning, no IBSS, radar detection) * 5280 MHz (disabled, passive scanning, no IBSS, radar detection) * 5300 MHz (disabled, passive scanning, no IBSS, radar detection) * 5320 MHz (disabled, passive scanning, no IBSS, radar detection) * 5500 MHz (disabled, passive scanning, no IBSS, radar detection) * 5520 MHz (disabled, passive scanning, no IBSS, radar detection) * 5540 MHz (disabled, passive scanning, no IBSS, radar detection) * 5560 MHz (disabled, passive scanning, no IBSS, radar detection) * 5580 MHz (disabled, passive scanning, no IBSS, radar detection) * 5600 MHz (disabled, passive scanning, no IBSS, radar detection) * 5620 MHz (disabled, passive scanning, no IBSS, radar detection) * 5640 MHz (disabled, passive scanning, no IBSS, radar detection) * 5660 MHz (disabled, passive scanning, no IBSS, radar detection) * 5680 MHz (disabled, passive scanning, no IBSS, radar detection) * 5700 MHz (disabled, passive scanning, no IBSS, radar detection) * 5745 MHz (disabled, passive scanning, no IBSS) * 5765 MHz (disabled, passive scanning, no IBSS) * 5785 MHz (disabled, passive scanning, no IBSS) * 5805 MHz (disabled, passive scanning, no IBSS) * 5825 MHz (disabled, passive scanning, no IBSS) Bitrates: * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps * 60.0 Mbps -------------------------------{snip]---------------------------------------------------------------------------------- Did I miss something to enable the disabled channels? Or is this just not supposed to work yet? Does it make sense to open a bugreport on bugzilla.novell.com? Or should I report that only upstream (where ?) ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Sat, 7 Feb 2009 16:06:52 +0100, Markus Koßmann wrote:
Did I miss something to enable the disabled channels? Or is this just not supposed to work yet? Does it make sense to open a bugreport on bugzilla.novell.com? Or should I report that only upstream (where ?) ?
Do you have CRDA installed and added into udev rules? See http://wireless.kernel.org/en/developers/Regulatory/CRDA how to do that. I don't think we have a crda package yet, so no, it's not supposed to work out of box yet. Jiri -- Jiri Benc SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Sat, 7 Feb 2009 16:31:48 +0100, Jiri Benc wrote:
I don't think we have a crda package yet, so no, it's not supposed to work out of box yet.
Turned out I was wrong. Helmut has already made the package, it's available in his buildservice repo: http://download.opensuse.org/repositories/home:/hschaa:/CRDA/ Jiri -- Jiri Benc SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Montag, 9. Februar 2009 schrieb Jiri Benc:
On Sat, 7 Feb 2009 16:31:48 +0100, Jiri Benc wrote:
I don't think we have a crda package yet, so no, it's not supposed to work out of box yet.
Turned out I was wrong. Helmut has already made the package, it's available in his buildservice repo: http://download.opensuse.org/repositories/home:/hschaa:/CRDA/
Thanks, I had it allready working with selfbuild rpms. But I now switched to Helmuts repo, because I hope he will provide updates if necessary. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Markus Koßmann wrote:
Hi, is there anyone out there, who runs a wireless connection on 2.6.29-rc3-git3- master_20090206202623_68c9d1c2-default using the 5GHz range on for example channel 36. This works with 2.6.27, but on 2.6.29 it is broken ( probably due to the new regulary framework). On 2.6.27 "iw list" shows :
Did I miss something to enable the disabled channels? Or is this just not supposed to work yet? Does it make sense to open a bugreport on bugzilla.novell.com? Or should I report that only upstream (where ?) ?
At this stage, it would be better to report it upstream. HEAD is definitely a moving target and bugs reported against it are low priority in comparison to SLE11 and openSUSE 11.1. For an upstream report, you should probably reproduce your problem with the -vanilla kernel. We shouldn't have any patches that conflict, but it's best to avoid confusion. There are a few options: 1) LKML <linux-kernel@vger.kernel.org> 2) bugzilla.kernel.org 3) The linux-wireless list, see http://linuxwireless.org/en/developers/MailingLists It's generally ok to post your report to both LKML and the subsystem list. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmNqpEACgkQLPWxlyuTD7ILYQCeKoDnU3AAFpLBuFP7DZd36cl6 u2cAn27VMqlOhYHAte3wrhA1Cnk28693 =s3Z1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Sat, 07 Feb 2009 10:36:50 -0500, Jeff Mahoney wrote:
At this stage, it would be better to report it upstream. HEAD is definitely a moving target and bugs reported against it are low priority in comparison to SLE11 and openSUSE 11.1.
This is not an upstream bug, so there is no point in reporting it upstream, though. Jiri -- Jiri Benc SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Sat, 07 Feb 2009 10:36:50 -0500, Jeff Mahoney wrote:
At this stage, it would be better to report it upstream. HEAD is definitely a moving target and bugs reported against it are low priority in comparison to SLE11 and openSUSE 11.1.
This is not an upstream bug, so there is no point in reporting it upstream, though. Yes that was my fault. But now I have problems to build crda.
Am Samstag, 7. Februar 2009 schrieb Jiri Benc: python-m2crypto is installed : #rpm -q python-m2crypto python-m2crypto-0.17-2.1.4 but the build bails out with at the very beginning : make DESTDIR=/var/tmp/crda-buildroot GEN keys-gcrypt.c ./utils/key2pub.py:7: DeprecationWarning: BaseException.message has been depre cated as of Python 2.6 sys.stderr.write('ERROR: Failed to import the "M2Crypto" module: %s\n' % e.m essage) ERROR: Failed to import the "M2Crypto" module: No module named M2Crypto Please install the "M2Crypto" Python module. On Debian GNU/Linux the package is called "python-m2crypto". ./utils/key2pub.py starts with : -------------------------------[snip]---------------------------------------------------------- #!/usr/bin/env python import sys try: from M2Crypto import RSA except ImportError, e: sys.stderr.write('ERROR: Failed to import the "M2Crypto" module: %s\n' % e.message) sys.stderr.write('Please install the "M2Crypto" Python module.\n') sys.stderr.write('On Debian GNU/Linux the package is called "python- m2crypto".\n') sys.exit(1) [...] Any ideas what's going wrong here ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Sat, 7 Feb 2009, Markus Koßmann wrote:
python-m2crypto is installed : #rpm -q python-m2crypto python-m2crypto-0.17-2.1.4
Hi Markus, out of curiosity, where does the 0.17-2.1.4 version come from? devel:languages:python repository for 11.1 seems to have version python-m2crypto-0.17-1.5
make DESTDIR=/var/tmp/crda-buildroot GEN keys-gcrypt.c ./utils/key2pub.py:7: DeprecationWarning: BaseException.message has been depre cated as of Python 2.6 sys.stderr.write('ERROR: Failed to import the "M2Crypto" module: %s\n' % e.m essage) ERROR: Failed to import the "M2Crypto" module: No module named M2Crypto Please install the "M2Crypto" Python module. On Debian GNU/Linux the package is called "python-m2crypto". ./utils/key2pub.py starts with :
Could you please run the "python" binary, check the output of import sys sys.path command, and compare it with the directory under which python-m2crypto-0.17-1.5 installed its modules, to make sure that python finds them properly? -- Jiri Kosina SUSE Labs
Am Samstag, 7. Februar 2009 schrieben Sie:
On Sat, 7 Feb 2009, Markus Koßmann wrote:
python-m2crypto is installed : #rpm -q python-m2crypto python-m2crypto-0.17-2.1.4
Hi Markus,
out of curiosity, where does the 0.17-2.1.4 version come from? devel:languages:python repository for 11.1 seems to have version python-m2crypto-0.17-1.5
make DESTDIR=/var/tmp/crda-buildroot GEN keys-gcrypt.c ./utils/key2pub.py:7: DeprecationWarning: BaseException.message has been depre cated as of Python 2.6 sys.stderr.write('ERROR: Failed to import the "M2Crypto" module: %s\n' % e.m essage) ERROR: Failed to import the "M2Crypto" module: No module named M2Crypto Please install the "M2Crypto" Python module. On Debian GNU/Linux the package is called "python-m2crypto". ./utils/key2pub.py starts with :
Could you please run the "python" binary, check the output of
import sys sys.path
command, and compare it with the directory under which python-m2crypto-0.17-1.5 installed its modules, to make sure that python finds them properly?
I've found the problem: I just searched in yast for python-m2crypto and installed it. The 0.17-2.1.4 version comes from http://download.opensuse.org/update/11.1/. But this is the i586 variant because there is no x86_64 variant in that repo.. This will not work with a x86_64 python . I have to add the python repo to get 0.17-1.5 x86_64 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Sunday 08 February 2009 08:01:15 Markus Koßmann wrote:
I've found the problem: I just searched in yast for python-m2crypto and installed it. The 0.17-2.1.4 version comes from http://download.opensuse.org/update/11.1/. But this is the i586 variant because there is no x86_64 variant in that repo.. This will not work with a x86_64 python . I have to add the python repo to get 0.17-1.5 x86_64
argh ... good catch. fixed. -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux MacBookRudi 2.6.27.10-2-default #1 SMP 2009-01-13 16:46:43 +0100 x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jiri Benc wrote:
On Sat, 07 Feb 2009 10:36:50 -0500, Jeff Mahoney wrote:
At this stage, it would be better to report it upstream. HEAD is definitely a moving target and bugs reported against it are low priority in comparison to SLE11 and openSUSE 11.1.
This is not an upstream bug, so there is no point in reporting it upstream, though.
After the way you described it in your response, I agree. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmN2FQACgkQLPWxlyuTD7LG+QCgjj3aLqoX8u6Rg+F4GzoB1RNX bwsAnikiNZC/gHawM2S8B5yii9kdEkfY =OsHF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (5)
-
Jeff Mahoney -
Jiri Benc -
Jiri Kosina -
Markus Koßmann -
Ruediger Oertel