On Wed, 2018-12-19 at 10:37 -0600, Bruce Dubbs via blfs-dev wrote: > On 12/19/2018 10:00 AM, Bruce Dubbs wrote: > > On 12/19/2018 02:55 AM, Xi Ruoyao via blfs-dev wrote: > > > On 2018-12-18 15:11 -0600, Bruce Dubbs via blfs-dev: > > > > I have figured out my original problem with loading the > > > > firmware for > > > > my > > > > wireless and bluetooth. It seems that the drivers for those > > > > were > > > > not > > > > enabled. Evidently I used the wrong base system when building > > > > the > > > > kernel. > > > > > > > > I still do have the message about regulatory.db. Now that the > > > > interface, wlan0, is recognized by the kernel, I can set it up > > > > with > > > > > > > > # ifconfig wlan0 up > > > > > > > > but I also get: > > > > > > > > # iwlist wlan0 scanning > > > > wlan0 Interface doesn't support scanning. > > > > > > > > and I suspect that has to do with the regulatory.db stuff in > > > > cfg80211. > > > > I was able to find: > > > > > > > > https://mirrors.edge.kernel.org/pub/software/network/wireless-r > > > > egdb/wireless-regdb-2018.10.24.tar.xz > > > > > > > > > > > > > > > > Arch has build instructions: > > > > > > > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGB > > > > UILD?h=packages/wireless-regdb > > > > > > > > but it needs the crda package: > > > > > > > > https://www.archlinux.org/packages/core/x86_64/crda/ > > > > > > crda is only used to verify the regulatory.bin file. To keep it > > > simple > > > and stupid we can just install regulatory.db, regulatory.db.p7s, > > > and > > > the man page regulatory.db.5. > > > > > > With regulatory.db directly loaded into the kernel /sbin/crda > > > seems > > > useless. I moved it away and my wpa_supplicant can still change > > > the > > > regdom to CN (automatically, matching my OpenWRT router). > > > > Do you just add regulatory.db to the kernel option > > CONFIG_EXTRA_FIRMWARE > > or is there more to it? > > > > I do have regulatory.db in /lib/firmware and in the kernel source > > directory firmware/. I'm not sure what the .p7s file is. Possibly > > a > > crypto signature. > > I did get the regulatory.db to load by adding both the .db and .p7s > files in CONFIG_EXTRA_FIRMWARE: > > [ 0.568710] microcode: sig=0x306c3, pf=0x10, revision=0x22 > [ 0.568923] microcode: Microcode Update Driver: v2.2. > [ 0.568944] sched_clock: Marking stable (556629458, > 12282386)->(584360640, -15448796) > [ 0.569404] registered taskstats version 1 > [ 0.569406] Loading compiled-in X.509 certificates > [ 0.570431] Magic number: 14:89:490 > [ 0.570664] cfg80211: Loading compiled-in X.509 certificates for > regulatory database > [ 0.571735] cfg80211: Loaded X.509 cert 'sforshee: > 00b28ddf47aef9cea7' > > > Also how do you set the regdom? Do you use iw? > > Adding the db is not enough. I don't know hos to set the regdom > other > than with: > > # iw reg set US > > but I haven't built iw yet. > > -- Bruce
Hi Bruce, Have you looked into the iwd daemon (https://iwd.wiki.kernel.org/). The thing is supposed to replace wpa_supplicant I'll be installing it on the LFS+BLFS setup I'm building at the moment on a linode server (I recently ordered a 8GB 4 core vm from linode which is used to do repeat build of various LFS+BLFS setups). Alain p.s. posting from gmail because mail.vocatus.pub doesn't want me to send any mails. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
