This is still a problem in linux-backports-modules version 2.6.28-11.12.
How do I add a task for this?
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of
** Also affects: linux-backports-modules-2.6.28 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
+ Various wireless drivers don't see !US wireless channels on UK laptop
[intrepid
Based on feedback from testers marking this FIx Released.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification
It also worked for me(iwl3945) with the lastest update.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can now access channels beyond 11 with iwlagn driver - Intel Wireless
link 5100 AGN - since the March 12th CRDA updates.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you
After installing Alpha6 and all updates (wireless-crda automatically
installed) the laptop can now connect to channel 13 here in switzerland.
Looks good.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received
@All -- we are expecting that the correct band selection should occur
with the latest CRDA database as released in the wireless-crda 1.7
upload. Could those of you affected by this on Jaunty please confirm
whether this is installed and whether things work as expected with it
installed. If it
** Changed in: linux (Ubuntu)
Status: In Progress = Incomplete
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
CONFIG_WIRELESS_OLD_REGULATORY=y (no CRDA) Thanks Alson, that is
exactly the kernel config change I was referring to. It seems that this
and therefore the CRDA stuff has been implemented before a method of
switching domains has been implemented to support this change!
--
iwl3945 driver doesn't
I am the submitter of bug #331092, this definitely seems related. It
works without manually specifying the regulatory domain with
CONFIG_WIRELESS_OLD_REGULATORY=y (no CRDA), so even a GUI config tool or
guessing based on timezone would be a regression as far as I'm
concerned. My laptop is from the
A kernel config option for cfg80211 has changed in one of the recent
Jaunty alpha kernel or module releases which disabled the legacy
options cfg80211 ieee80211_regdom=EU method. Now that the CRDA method
is in place there is no way of passing the region to the module without
a git version of
This may also be triggering the inability to bind to 8.0.2.11n channels
as reported in bug #331092.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided = High
Status: New = Confirmed
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of
I am on jaunty and have the same problem with iwlagn driver - Intel
Wireless link 5100 AGN driver. I've tried using iw to set to no avail.
At the moment am having to live without channels 12 and 13 until this is
resolved.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
The work-around for Intrepid is to assign the module parameter
ieee80211_regdom as described below:
# /etc/modprobe.d/regdom
options cfg80211 ieee80211_regdom=EU
options lbm_cw_cfg80211 ieee80211_regdom=EU
** Changed in: linux (Ubuntu Intrepid)
Importance: High = Undecided
Assignee:
Jaunty ought to be working correctly with the CRDA udev agent for those
drivers that support regulatory_hint().
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
Status: Confirmed = In Progress
Target: None = jaunty-alpha-6
--
iwl3945 driver
As per the answer I was given on
https://answers.launchpad.net/ubuntu/+question/62114 ,
the only way I currently know to re-enable the channels - on jaunty anyway - is
to get this working was to compile iw from source and manually pass the country
code. The only version of iw that i could see
** Description changed:
The iwl3945 driver in Intrepid doesn't appear to see !US wireless
channels, even on a UK laptop. My home network is on channel 13 and
completely open, but Intrepid couldn't find it until I forced it back to
channel 11. Hardy on the same hardware found and used
I too have the same issue in Europe with the b43 driver in Intrepid.
Should be b43 driver issue be filed as a separate bug?
Creating /etc/modprobe.d/wireless with the following line allows connecting to
all allowed channels(after a reload of modules).
options lbm_cw_cfg80211 ieee80211_regdom=EU
This bug was reported in the Intrepid development cycle; removing
regression-potential and marking as regression-release.
** Tags added: regression-release
** Tags removed: regression-potential
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
This is a complex issue as there clearly has to be a userspace framework
to support the new regulatry infrastructure. This project is the topic
for the Jaunty UDS.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You
Another option to try is to install linux-backports-modules-2.6.27.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
No, linux-backpors-modules also need the patch
lbm_cw_cfg80211 ieee80211_regdom=EU
(On my computer with intrepid at least)
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you
I live in the UK and I had a similar problem to this with the b43
driver. It took me a very long time to work out what the issue was.
There definitely needs to be a GUI to set/override the location (both
for when it is determined wrongly and for when people move from one
geographical location to
@Chris
This Workaround does not work as aspected i tried options cfg80211
ieee80211_regdom=EU
and also options cfg80211 ieee80211_regdom=JP
i can find now non us channel but can´t join them
dmesg says:
WARNING: at /build/buildd/linux-2.6.27/net/mac80211/main.c:987
eth1: IBSS not allowed on
Why did you change the ubuntu-release-notes task to Invalid? Please be
more specific - what doesn't work for you?
** Changed in: ubuntu-release-notes
Status: Invalid = Fix Released
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
the workaround does not work for me.
** Changed in: ubuntu-release-notes
Status: Fix Released = Invalid
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a
Tim Gardner [EMAIL PROTECTED] writes:
@James - if possible it would be interesting to see if the iwl3945 has
problems associating on channels 12 and 13 when other wireless adapters
do work, such as iwl4965.
The WAP in question is my home WAP; so this isn't trivial to test (as
opposed to if it
I've got a similar problem with channel 13.
I can't join ibss networks (ad-hoc) on channel 13, so I
tried to add options cfg80211 ieee80211_regdom=JP and options cfg80211
ieee80211_regdom=EU to /etc/modprobe.d/options,
but it doesn't work.
dmesg says:
WARNING: at
Its likely that older Access Points are not broadcasting a regulatory
domain information element in the beacon, or have not been configured
for operation outside of the US. In either case, I imagine most US
manufacturers of wireless adapters default to the US channel set.
** Changed in: linux
Release notes text added:
== Only US wireless channels enabled by default on Intel 3945 ==
The iwl3945 wireless driver defaults to the US regulatory domain for
wireless, so wireless networks on channels forbidden by US regulations
but permitted by European or Japanese regulations will not work
@James - if possible it would be interesting to see if the iwl3945 has
problems associating on channels 12 and 13 when other wireless adapters
do work, such as iwl4965.
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
https://bugs.launchpad.net/bugs/288401
You received this bug notification
The only proper fix I can see for this is to have some kind of
preference in something like Network Manager. It would have to be a
user configurable setting because many people take their laptops to
other countries which have different channel options. I guess it could
also be possible to link
** Description changed:
The iwl3945 driver in Intrepid doesn't appear to see !US wireless
channels, even on a UK laptop. My home network is on channel 13 and
completely open, but Intrepid couldn't find it until I forced it back to
channel 11. Hardy on the same hardware found and used
Sorry Linuxjedi - I set the importance on the original bug quite early
on, without truly understanding the full impact. In hindsight, it was
not the correct decision
This is a regression because of the new regulatory infrastructure in the
kernel. The regulatory domain should be automatically set,
Ah, thanks for this Chris, yes your interpretation of this document
makes sense. The impact of this bug may be lower than I originally
anticipated then.
It may warrant some documentation somewhere (I would certainly
appreciate it when helping fellow Ubuntu users). I would imagine people
in
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/18827548/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/18827549/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18827550/Dependencies.txt
**
Setting importance to High since wireless cards are a core component and
non-US is a major portion of users.
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
iwl3945 driver doesn't see !US wireless channels on UK laptop [intrepid
regression]
40 matches
Mail list logo
