Xylian
October 15th, 2011, 10:17 AM
Hi,
yesterday I've upgraded my Ubuntu 11.04 installation to 11.10 and I'm having troubles with CRDA, since it's flooding the syslog with continuous messages.. I've set the following:
# cat /etc/modprobe.d/cfg80211.conf
options cfg80211 ieee80211_regdom="EU"
But something wrong happens at boot:
cfg80211: Calling CRDA for country: EU
cfg80211: Timeout while waiting for CRDA to reply, restoring regulatory settings
cfg80211: Restoring regulatory settings including user preference
cfg80211: Keeping preference on module parameter ieee80211_regdom: EU
cfg80211: Calling CRDA for country: US
cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[...]
And then udev keeps sending regulatory domain settings for country 97:
cfg80211: Calling CRDA for country: 97
cfg80211: Timeout while waiting for CRDA to reply, restoring regulatory settings
cfg80211: Keeping preference on module parameter ieee80211_regdom: EU
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Kicking the queue
cfg80211: Calling CRDA to update world regulatory domain
[...]
Monitoring UDEV messages to the kernel, I see continuous messages like the following one:
# udevadm monitor --environment kernel
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1950.592767] change /devices/platform/regulatory.0 (platform)
UDEV_LOG=3
ACTION=change
DEVPATH=/devices/platform/regulatory.0
SUBSYSTEM=platform
MODALIAS=platform:regulatory
COUNTRY=00
SEQNUM=2829
Any idea about how to solve the problem? I've seen there was a bug related to kernel 3 here: https://bugzilla.novell.com/show_bug.cgi?id=700159#c0
yesterday I've upgraded my Ubuntu 11.04 installation to 11.10 and I'm having troubles with CRDA, since it's flooding the syslog with continuous messages.. I've set the following:
# cat /etc/modprobe.d/cfg80211.conf
options cfg80211 ieee80211_regdom="EU"
But something wrong happens at boot:
cfg80211: Calling CRDA for country: EU
cfg80211: Timeout while waiting for CRDA to reply, restoring regulatory settings
cfg80211: Restoring regulatory settings including user preference
cfg80211: Keeping preference on module parameter ieee80211_regdom: EU
cfg80211: Calling CRDA for country: US
cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2700 mBm)
[...]
And then udev keeps sending regulatory domain settings for country 97:
cfg80211: Calling CRDA for country: 97
cfg80211: Timeout while waiting for CRDA to reply, restoring regulatory settings
cfg80211: Keeping preference on module parameter ieee80211_regdom: EU
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Adding request for country EU back into the queue
cfg80211: Kicking the queue
cfg80211: Calling CRDA to update world regulatory domain
[...]
Monitoring UDEV messages to the kernel, I see continuous messages like the following one:
# udevadm monitor --environment kernel
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1950.592767] change /devices/platform/regulatory.0 (platform)
UDEV_LOG=3
ACTION=change
DEVPATH=/devices/platform/regulatory.0
SUBSYSTEM=platform
MODALIAS=platform:regulatory
COUNTRY=00
SEQNUM=2829
Any idea about how to solve the problem? I've seen there was a bug related to kernel 3 here: https://bugzilla.novell.com/show_bug.cgi?id=700159#c0