Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: johand on November 05, 2015, 03:52:23 AM
-
I have successfully built the driver for rtl8723bu (WIFI) (http://forum.tinycorelinux.net/index.php/topic,19104.0.html)
When I tried on Raspbian I installed the driver with "sudo make install" and it was automaticly loaded. On TC nothing happens.
The module is recognized during boot:
[ 2.611653] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[ 2.712978] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=b720
[ 2.713020] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.713040] usb 1-1.2: Product: 802.11n WLAN Adapter
[ 2.713060] usb 1-1.2: Manufacturer: Realtek
[ 2.713077] usb 1-1.2: SerialNumber: 00e04c000001
On Raspbian I got appr 10 rows of information from this driver in dmesg output after "sudo make install". But on TC nothing happens.
What could be wrong?
BTW, I had to manually create the folder wireless in /lib/modules/4.1.8-piCore+/kernel/drivers/net/ before I could install the driver, any problem with that?
Johan
-
How is your module loaded during boot, is it in the backup or from a .tcz?
Is wireless kernel module tcz installed?
-
wireless-4.1.8-piCore+ is installed.
Right now I don“t load the module during boot, just want to see if it works. I run "sudo make install" in the driver source folder after compilation. Should I do it another way?
Johan
-
Did you try "sudo depmod -a" after "sudo make install"?
-
I tried "sudo depmod -a", nothing happens.
"sudo modprobe 8723bu.ko" adds this:
[ 251.697366] cfg80211: Calling CRDA to update world regulatory domain
[ 251.826876] RTL871X: module init start
[ 251.826922] RTL871X: rtl8723bu v4.3.6.11_12942.20141204_BTCOEX20140507-4E40
[ 251.826938] RTL871X: rtl8723bu BT-Coex version = BTCOEX20140507-4E40
[ 252.146308] RTL871X: rtw_ndev_init(wlan0)
[ 252.154611] usbcore: registered new interface driver rtl8723bu
[ 252.154647] RTL871X: module init ret=0
[ 254.851539] cfg80211: Calling CRDA to update world regulatory domain
[ 258.011540] cfg80211: Calling CRDA to update world regulatory domain
[ 261.171540] cfg80211: Calling CRDA to update world regulatory domain
[ 264.331589] cfg80211: Calling CRDA to update world regulatory domain
[ 267.491559] cfg80211: Calling CRDA to update world regulatory domain
[ 270.651615] cfg80211: Calling CRDA to update world regulatory domain
[ 273.811541] cfg80211: Calling CRDA to update world regulatory domain
[ 276.971536] cfg80211: Calling CRDA to update world regulatory domain
[ 280.131585] cfg80211: Calling CRDA to update world regulatory domain
[ 283.291605] cfg80211: Calling CRDA to update world regulatory domain
[ 286.451531] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
Should I be worried?
But the best thing, IT DOES WORK!!! I am now connected to a WPA-network :)
What is the correct way to load the driver? I guess i should create a tcz, but how should I design the package to load the driver during boot? I cannot find any documentation of best practice for driver tcz.
Johan
-
tce-load will automatically issue the depmod command for an extension - it could be that your driver will load itself.