[Solved]CRDA needed
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
[Solved]CRDA needed
Hello everbody
short description:
here in germany it is allowed to use wifi-channels 1-13, but all the usb-wifi you can buy
is internally branded to CN=China or US (world regulatory domain), which only allows you
to use channel 1-11.Unfortunatly the AP to which i have to connect to often switches to
channel 12 or 13 and then i am off
So what i would like to have is an easy to use (GUI) interface to override that.
Just for Information:
I m using Porteus 2.0-XFCE-32 mostly, Slitaz sometimes, but when i m off of that AP
I have to use Pclos-LXDE-mini (and i dont want to) cause there is an option in Network-Manager
to easyly change the World-Regulatory-Domain to DE
and yes, maybe we have it allready here and I didnt find it
greetings from germany donald
short description:
here in germany it is allowed to use wifi-channels 1-13, but all the usb-wifi you can buy
is internally branded to CN=China or US (world regulatory domain), which only allows you
to use channel 1-11.Unfortunatly the AP to which i have to connect to often switches to
channel 12 or 13 and then i am off
So what i would like to have is an easy to use (GUI) interface to override that.
Just for Information:
I m using Porteus 2.0-XFCE-32 mostly, Slitaz sometimes, but when i m off of that AP
I have to use Pclos-LXDE-mini (and i dont want to) cause there is an option in Network-Manager
to easyly change the World-Regulatory-Domain to DE
and yes, maybe we have it allready here and I didnt find it
greetings from germany donald
Last edited by donald on 17 Jun 2013, 21:17, edited 1 time in total.
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: CRDA needed
@hamza
thank you for the quick respose,( and the link of course).
right now i'm on Pclos (channel13) so I will check out tomorrow what I'v got
and how it work's
regards donald
thank you for the quick respose,( and the link of course).
right now i'm on Pclos (channel13) so I will check out tomorrow what I'v got
and how it work's
regards donald
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: CRDA needed
@Hamza
no luck till now
I've copied crda-1.1.1-i486-1.xzm to the module folder ...reboot
iwlist channel = channel 1-11
dmesg=
32.175070] ath9k_htc 1-4:1.0: ath9k_htc: FW Version: 1.3
[ 32.175083] ath: EEPROM regdomain: 0x809c
[ 32.175088] ath: EEPROM indicates we should expect a country code
[ 32.175093] ath: doing EEPROM country->regdmn map search
[ 32.175098] ath: country maps to regdmn code: 0x52
[ 32.175104] ath: Country alpha2 being used: CN
[ 32.175107] ath: Regpair used: 0x52
[ 32.300492] ieee80211 phy0: Atheros AR9271 Rev:1
[ 32.302237] Registered led device: ath9k_htc-phy0
what else have i to do to get it working?
regards donald
no luck till now
I've copied crda-1.1.1-i486-1.xzm to the module folder ...reboot
iwlist channel = channel 1-11
dmesg=
32.175070] ath9k_htc 1-4:1.0: ath9k_htc: FW Version: 1.3
[ 32.175083] ath: EEPROM regdomain: 0x809c
[ 32.175088] ath: EEPROM indicates we should expect a country code
[ 32.175093] ath: doing EEPROM country->regdmn map search
[ 32.175098] ath: country maps to regdmn code: 0x52
[ 32.175104] ath: Country alpha2 being used: CN
[ 32.175107] ath: Regpair used: 0x52
[ 32.300492] ieee80211 phy0: Atheros AR9271 Rev:1
[ 32.302237] Registered led device: ath9k_htc-phy0
what else have i to do to get it working?
regards donald
Re: CRDA needed
Did you copied the dependency present in '/deps' too? I think crda needs some manual settings.
NjVFQzY2Rg==
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: CRDA needed
@Hamza
no i did not ....will do it
manual settings ...where?
regards donald
no i did not ....will do it
manual settings ...where?
regards donald
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: CRDA needed
@Hamza
all is good now
copying libnl-1.1-i486-1.xzm in the module folder did it
iwlist channel 1-13
iwlist scan show me some AP on channel 13,12
unfortunatly is that AP to which i have to connect to
on channel 9 right now LOL so i can't test,but the cli-output looks fine
again,many many thanks
will delete Pclos now
regards donald
all is good now
copying libnl-1.1-i486-1.xzm in the module folder did it
iwlist channel 1-13
iwlist scan show me some AP on channel 13,12
unfortunatly is that AP to which i have to connect to
on channel 9 right now LOL so i can't test,but the cli-output looks fine
again,many many thanks
will delete Pclos now
regards donald
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: [Solved]CRDA needed
@Hamza
now i see
the trick is not to change the Regdomain, dmesg shows still Country=CN,
but to change the values for CN in the regulatory.bin file
smart
now i see
the trick is not to change the Regdomain, dmesg shows still Country=CN,
but to change the values for CN in the regulatory.bin file
smart
-
- Ronin
- Posts: 1
- Joined: 05 Jan 2016, 03:11
- Distribution: Porteus v3.1 XFCE
- Location: London, UK
Re: [Solved]CRDA needed
I'm just posting to confirm that this fix worked for me too. As a new user of Porteus I was puzzled why I couldn't get the WiFi to work. My wireless worked fine with other distros. In the network applet I could see the SSIDs for several of my neighbours' networks but not mine.
After a bit of digging with iwlist and iwconfig I found I had the same problem as the OP. My WiFi adapter had channels 12 and 13 disabled and my home network was using 13.
To see what channels are available run the following command when logged in as root (sudo won't work as it can't find the path).
To fix it I copied the two files that are linked to in the second post. I put them into my /porteus/modules folder and after rebooting everything was fine.
Thanks for a very useful distro. Bob
After a bit of digging with iwlist and iwconfig I found I had the same problem as the OP. My WiFi adapter had channels 12 and 13 disabled and my home network was using 13.
To see what channels are available run the following command when logged in as root (sudo won't work as it can't find the path).
Code: Select all
iwlist wlan0 channel
Thanks for a very useful distro. Bob
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: [Solved]CRDA needed
Hello Bob....welcome to porteus.
Yep, imo; That (crda) should be included by default in the porteus isos.
btw
It's nice to see when someone was not too lazy to search the forum for a solution.
Yep, imo; That (crda) should be included by default in the porteus isos.
btw
It's nice to see when someone was not too lazy to search the forum for a solution.

Re: [Solved]CRDA needed
@donald
necrobump. I found this post by accident and sometimes you learn more by accident
In Nemesis 64 bit....
How did you mod the bin file please?
necrobump. I found this post by accident and sometimes you learn more by accident

In Nemesis 64 bit....
Code: Select all
file /usr/lib/crda/regulatory.bin
/usr/lib/crda/regulatory.bin: CRDA wireless regulatory database file (Version 1)
root /home/guest # strings /usr/lib/crda/regulatory.bin
RGDB
dCO
,IE
LMP
8TH
8YE
$>Nt
x$uI9r
'aX
r1x<<Mz
IoZgxD
I rebooted without seeing this file and changed my /etc/conf.d/wireless-regdom to AU before finding this post, that of course can be easily fixed but bin file I am not so sure ofbut to change the values for CN in the regulatory.bin file
-
- Full of knowledge
- Posts: 2006
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: [Solved]CRDA needed
@aus9
Yep, this was my first post at porteus but it was Hamza who build the regulatory.bin.
The (16:43) post is somehow misleading.It is only my observation of the results.
The wifi dongle is still internally set fixed to CN but the CRDA changes that to DE whereas iw reg set etc. doesn't work.
At that time i read a lot of pages about "how to do it", patch and compile, but failed.
All Credits to Hamza
Yep, this was my first post at porteus but it was Hamza who build the regulatory.bin.
The (16:43) post is somehow misleading.It is only my observation of the results.
The wifi dongle is still internally set fixed to CN but the CRDA changes that to DE whereas iw reg set etc. doesn't work.
Code: Select all
cfg80211: Calling CRDA for country: DE
cfg80211: Regulatory domain changed to country: DE
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5150000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm)
At that time i read a lot of pages about "how to do it", patch and compile, but failed.
All Credits to Hamza