While traveling outside of the US this can be a real issue.
I have recently upgrade my wife’s Laptop to 12.2 RC2 and it has no issue using networks on channels 12-14.
That made me think, does Opensuse put in some kind of limitation to US downloads of its OS, the same way it does with
media formats?
Things I know at this point, channel 12-14 work on the effected system while using 7, the effected systems seem to
work just fine while using 12.2 RC2.
I have also noticed that iwlist won’t scan higher than 11 on the effected systems when using 12.1.
The question is is there a way to get 12-14 working on my laptop? (Do I have to download the ISO from a EU mirror to get this working?)
On 08/27/2012 01:56 PM, magabooks wrote:
>
> While traveling outside of the US this can be a real issue.
>
> I have recently upgrade my wife’s Laptop to 12.2 RC2 and it has no
> issue using networks on channels 12-14.
> That made me think, does Opensuse put in some kind of limitation to US
> downloads of its OS, the same way it does with
> media formats?
>
> Things I know at this point, channel 12-14 work on the effected system
> while using 7, the effected systems seem to
> work just fine while using 12.2 RC2.
>
> I have also noticed that iwlist won’t scan higher than 11 on the
> effected systems when using 12.1.
>
> The question is is there a way to get 12-14 working on my laptop? (Do I
> have to download the ISO from a EU mirror to get this working?)
The ISO from an EU mirror will not help. All mirrors get the same material.
The available channels are set by the following process: The driver reads the
info in its ROM to determine the country code. That info is sent to cfg80211 and
the regulatory info is obtained from the regulatory database, which is processed
by crda. The allowed channels and power settings are then sent back.
Depending on the vendor of your card, you might be able to get it to work on
channels higher than 11 by creating a file named /etc/init.d/50-cfg80211.conf
containing the single line
options cfg80211 ieee80211_regdom=XX
where XX is the two-character country code such as US, DE, etc. You will only
get channel 14 in Japan.
If the card vendor has encoded the country code, then it is possible that trying
to override the code using the above trick will fail as the firmware will refuse
to set channels outside the allowed range. In that case, there is nothing you
can do.
FWIW
On my sons laptop, HP625, if b43 is blacklisted, more wireless networks are detected
This was notice when trying to connect to a Huawei dongle
Broadcom label the b43 as the problem on their wireless modems for linux users
If you have one, check out their website
On 08/27/2012 09:16 PM, keellambert wrote:
>
> FWIW
>
> On my sons laptop, HP625, if b43 is blacklisted, more wireless networks
> are detected
>
> This was notice when trying to connect to a Huawei dongle
>
> Broadcom label the b43 as the problem on their wireless modems for
> linux users
>
> If you have one, check out their website
Do not tell me that b43 is the problem. That honor is reserved for Broadcom!!
Yes, b43 is less than perfect; however, that is because Broadcom refuses to
reveal specs for the device. All the other major vendors cooperate with Linux
developers, or even supply their own team. Only Broadcom pulls a Microsoft move
and blames b43.
@lwfinger
while booting the following error is seen
b43-phy0 ERROR: FOUND UNSUPPORTED PHY
do you haved a quick solution?
On 08/28/2012 04:16 AM, keellambert wrote:
>
> @lwfinger
>
> while booting the following error is seen
>
> b43-phy0 ERROR: FOUND UNSUPPORTED PHY
>
> do you haved a quick solution?
When Broadcom releases a new PHY type, there is a lot of work needed to support
it. First, the Broadcom driver needs to be reverse engineered to determine how
the device is programmed. This sequence is then posted as specifications that
are used to create the code in b43. At the moment, there is only one person
doing the specifications, and one doing b43 coding. For legal reasons, these two
operations must be done by separate people. The coder is finishing his degree,
and has only limited time for the project.
Your output is a bit too terse. There are also lines in the dmesg output that
say what kind of PHY you have. You can provide that, or post the output of
‘/sbin/lspci -nn | grep 14e4’.
It is possible that your device is supported by b43 in the version of the driver
found in the compat-wireless package. In addition, it may be supported in the
latest version of brcmsmac from c-w. The final option will be to install the
proprietary Broadcom wl package. Once I have the lspci output, I can tell you
which of the alternatives you need to use.
@lwfinger
on Saturday, openSUSE12.2 RC2 LiveCD was installed,
played a bit to establish the wireless interface to an Huewei E585 Modem,
on Scan other networks could be seen but not the dongle
played a bit more and updated kernel and kde
wireless still the same
googled a bit, read the Broadcom page
looked at the kernel modules and saw other wireless models, so did not try to
install any other
Added the following lines to /etc/modprobe.d/50-blacklist.conf
#
blacklist b43
# trying to get wifi to work 26Aug2012
on the next try, the wireless connection was established,
laptop info as follows,
System: Host: linux-qruh.site Kernel: 3.5.2-1-desktop x86_64 (64 bit)
Desktop KDE 4.9.00 Distro: openSUSE 12.2 (x86_64) VERSION = 12.2 CODENAME = Mantis
Machine: System: Hewlett-Packard (portable) product: HP 625
Mobo: Hewlett-Packard model: 1475 version: KBC Version 72.0E
Bios: Hewlett-Packard version: 68DVA Ver. F.01 date: 05/24/2010
CPU: Dual core AMD Athlon II P320 (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4a svm)
Clock Speeds: 1: 2100.00 MHz 2: 800.00 MHz
Network: Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169
IF: eth0 state: up speed: 100 Mbps duplex: full mac: xx:xx:xx:xx:xx:xx
Card-2: Broadcom BCM4313 802.11b/g/n Wireless LAN Controller driver: bcma-pci-bridge
IF: N/A state: N/A mac: N/A
output of the cmd kdesu -c ‘/sbin/lspci -nn | grep 14e4’,
michael@linux-qruh:/etc/modprobe.d> kdesu -c '/sbin/lspci -nn | grep 14e4'
kdesu(3137)/kdesu (kdelibs) KDESu::PtyProcess::exec: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/process.cpp : 293 ] Running "/usr/bin/su"
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line "Password: "
kdesu(3137)/kdesu (kdelibs) KDESu::PtyProcess::exec: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/process.cpp : 293 ] Running "/usr/bin/su"
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line "Password: "
kdesu(3137)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/process.cpp : 379 ] Child pid 3142
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line ""
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line "kdesu_stub"
kdesu(3137)/kdesu (kdelibs) KDESu::PtyProcess::exec: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/process.cpp : 293 ] Running "/usr/bin/su"
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line "Password: "
kdesu(3137)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/process.cpp : 379 ] Child pid 3147
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line ""
kdesu(3137)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: /home/abuild/rpmbuild/BUILD/kdelibs-4.9.0/kdesu/su.cpp : 259 ] Read line "kdesu_stub"
michael@linux-qruh:/etc/modprobe.d>
NB. When updating system I did not allow ndiswrapper to install as
its dependencies led to a kernel version install mis-match.
cheers
On 08/28/2012 12:16 PM, keellambert wrote:
>
> @lwfinger
>
> on Saturday, openSUSE12.2 RC2 LiveCD was installed,
> played a bit to establish the wireless interface to an Huewei E585
> Modem,
> on Scan other networks could be seen but not the dongle
>
> played a bit more and updated kernel and kde
>
> wireless still the same
>
> googled a bit, read the Broadcom page
>
> looked at the kernel modules and saw other wireless models, so did not
> try to
> install any other
>
> Added the following lines to /etc/modprobe.d/50-blacklist.conf
>
>
> Code:
> --------------------
> #
> blacklist b43
> # trying to get wifi to work 26Aug2012
> --------------------
>
>
> on the next try, the wireless connection was established,
>
> laptop info as follows,
>
> Code:
> --------------------
> System: Host: linux-qruh.site Kernel: 3.5.2-1-desktop x86_64 (64 bit)
> Desktop KDE 4.9.00 Distro: openSUSE 12.2 (x86_64) VERSION = 12.2 CODENAME = Mantis
> Machine: System: Hewlett-Packard (portable) product: HP 625
> Mobo: Hewlett-Packard model: 1475 version: KBC Version 72.0E
> Bios: Hewlett-Packard version: 68DVA Ver. F.01 date: 05/24/2010
> CPU: Dual core AMD Athlon II P320 (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4a svm)
> Clock Speeds: 1: 2100.00 MHz 2: 800.00 MHz
> Network: Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169
> IF: eth0 state: up speed: 100 Mbps duplex: full mac: xx:xx:xx:xx:xx:xx
> Card-2: Broadcom BCM4313 802.11b/g/n Wireless LAN Controller driver: bcma-pci-bridge
> IF: N/A state: N/A mac: N/A
> --------------------
>
>
> output of the cmd kdesu -c ‘/sbin/lspci -nn | grep 14e4’,
Who said anything about using kdesu? Use the ‘/sbin/lspci -nn | grep 14e4’
command in a terminal. Do not include the ’ as they are there merely to
delineate the command. All of the kdesu lines you posted are garbage.
If you are going to use wl, then you should blacklist b43, ssb, and bcma, but
the wl installation takes care of that.
@lwfinger
Some clarifications,
- Sorry sent wrong file before
linux-qruh:~ # lspci -nn | grep 14e4
03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
linux-qruh:~ #
- I forget to mention that, as well as blacklisting b43, the following two packages were deleted with yast
b43-fwcutter-012-18.1.2.x86_64
b43legacy-firmware-3.130.20.0-2.2.noarch
- The wireless modules now loaded are :-
michael@linux-qruh:~/Updates/Tumbleweed_12.2/wlan> lsmod |grep brcmsmac
brcmsmac 568774 0
mac80211 599292 1 brcmsmac
brcmutil 14755 1 brcmsmac
cfg80211 214372 2 brcmsmac,mac80211
cordic 12535 1 brcmsmac
bcma 40177 1 brcmsmac
This seems to contradict your last statement. But it still works.
keep smiling
On 08/28/2012 05:26 PM, keellambert wrote:
>
> @lwfinger
>
> Some clarifications,
>
> 1. Sorry sent wrong file before
>
> Code:
> --------------------
> linux-qruh:~ # lspci -nn | grep 14e4
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
> linux-qruh:~ #
> --------------------
>
>
> 2. I forget to mention that, as well as blacklisting b43, the following
> two packages were deleted with yast
>
> Code:
> --------------------
> b43-fwcutter-012-18.1.2.x86_64
> b43legacy-firmware-3.130.20.0-2.2.noarch
> --------------------
>
>
> 3. The wireless modules now loaded are :-
>
> Code:
> --------------------
> michael@linux-qruh:~/Updates/Tumbleweed_12.2/wlan> lsmod |grep brcmsmac
> brcmsmac 568774 0
> mac80211 599292 1 brcmsmac
> brcmutil 14755 1 brcmsmac
> cfg80211 214372 2 brcmsmac,mac80211
> cordic 12535 1 brcmsmac
> bcma 40177 1 brcmsmac
> --------------------
>
>
> This seems to contradict your last statement. But it still works.
Yes, but I had to assume that you were using wl because I did not know what
device you have. Using brcmsmac is different. With it, bcma is absolutely necessary.
@lwfinger
This is the last entry containing b43 from file /var/log/warn
Aug 28 03:15:05 linux-qruh kernel: 10.227239] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8, Revision 1)
Aug 28 03:15:05 linux-qruh kernel: 10.227247] b43: probe of bcma0:0 failed with error -95
Aug 28 03:15:05 linux-qruh kernel: 14.420839] ieee80211 phy1: brcms_ops_bss_info_changed: qos enabled: false (implement)
Aug 28 03:15:05 linux-qruh kernel: 14.420849] ieee80211 phy1: brcms_ops_config: change power-save mode: false (implement)
This is the entry from my last successful wireless connection
Aug 29 09:12:17 linux-qruh kernel: 1164.791478] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Aug 29 09:12:17 linux-qruh kernel: 1164.791487] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement)
Aug 29 09:13:49 linux-qruh kernel: 1257.165472] ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: associated
Aug 29 09:13:49 linux-qruh kernel: 1257.165481] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement)
Aug 29 09:13:49 linux-qruh kernel: 1257.165487] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Aug 29 09:13:50 linux-qruh kernel: 1257.385357] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
Aug 29 09:13:50 linux-qruh kernel: 1257.385368] ll header: 00000000: ff ff ff ff ff ff f4 c7 14 8b 00 ec 08 00 ..............
Aug 29 09:13:54 linux-qruh kernel: 1261.535268] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
Aug 29 09:13:54 linux-qruh kernel: 1261.535273] ll header: 00000000: 00 26 82 b3 4b a7 f4 c7 14 8b 00 ec 08 00 .&..K.........
Aug 29 09:13:56 linux-qruh kernel: 1263.632000] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
Aug 29 09:13:56 linux-qruh kernel: 1263.632012] ll header: 00000000: 00 26 82 b3 4b a7 f4 c7 14 8b 00 ec 08 00 .&..K.........
Aug 29 09:13:56 linux-qruh kernel: 1263.711798] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
Aug 29 09:13:56 linux-qruh kernel: 1263.711809] ll header: 00000000: 00 26 82 b3 4b a7 f4 c7 14 8b 00 ec 08 00 .&..K.........
Aug 29 09:13:56 linux-qruh kernel: 1263.725878] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)
Aug 29 09:16:47 linux-qruh kernel: 1434.361580] ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated
Aug 29 09:16:47 linux-qruh kernel: 1434.361599] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 1 (implement)
Aug 29 09:16:47 linux-qruh kernel: 1434.361605] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Cheers