Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13200 - crda is set to default US

Attached to Project: Arch Linux
Opened by Börje Holmberg (linfan) - Wednesday, 11 February 2009, 09:11 GMT
Last edited by Thomas Bächler (brain0) - Thursday, 28 May 2009, 19:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
crda is set to default US

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:pacman -S crda


I am wondering if the crda has a bug? I have set the regdom to SE, but still it starts with configuring US and only after that it changes to SE. Isn't that a rather unnecessary procedure?
This task depends upon

Closed by  Thomas Bächler (brain0)
Thursday, 28 May 2009, 19:14 GMT
Reason for closing:  Not a bug
Comment by Dawid Wróbel (cromo) - Thursday, 26 March 2009, 13:35 GMT
According to crdb manual, we need a new udev rule for setting the correct regulatory domain and COUNTRY environment variable set to a specific ISO / IEC 3166 alpha2 country code.
Comment by Thomas Bächler (brain0) - Thursday, 28 May 2009, 18:59 GMT
crda does not default to the US domain. If you have CONFIG_WIRLESS_OLD_REGULATORY enabled, the kernel will enable US by default. If it is disabled (like in the Arch kernel), then the default will be the "World" (00) domain.

Once cfg80211 is loaded, a udev rule will call "iw reg set ..." according to what is set in /etc/conf.d/wireless-regdom. Then the udev rule mentioned in the documentation will call crda as appropriate.

I don't see any problem or bug here, we cannot override the kernel's default earlier than we do already.
Comment by Börje Holmberg (linfan) - Thursday, 28 May 2009, 19:02 GMT
In fact I have not noticed this happen any more, It was at the time I wrote the question that it occurred. Now it seems to work.
Comment by Thomas Bächler (brain0) - Thursday, 28 May 2009, 19:14 GMT
Okay, it seems this report is rather old, it just got assigned to me today.

Loading...