ronniepinsky
November 25th, 2014, 04:50 PM
edit:
I wanted to update that I seem to have gotten it working!
Apparently the code hack I referenced did not work in the way I thought. I investigated inside the "virtual folder" of the SDIO device and found the device ID and replaced the one for "CONFIG_RTL8723B" in sdio_intf.c that I referenced earlier. The first address (0x024c) is the vendor ID which should remain the same. The second address (0xB723) is the device ID which should be changed to (for my hardware) 0x0523. I then recompiled and ran insmod and it works. I knew it worked because there was a slight delay when loading the module.
Thanks for encouraging me to press on with this.
-----------
I have a device with an rtl8723bs SDIO wireless card. The rtl8723as driver should support it as seen here: http://ubuntuforums.org/showthread.php?t=2249936&page=3&highlight=rtl8723bs, and on this source code page it seems to show support for all SDIO wireless adapters: https://github.com/hadess/rtl8723as/blob/3dd8594d850502fb76d0170209ef24d93e372753/os_dep/linux/sdio_intf.c .
I see the same lines in dmesg when the driver is loaded that the person on the thread here did:
[ 46.589898] 8723bs: module verification failed: signature and/or required key missing - tainting kernel
[ 46.604071] RTL871X: module init start version:v4.1.3_8883.20130902_v2
[ 46.964685] RTL871X: module init ret=0
Unfortunately for me, the wlan0 device or similar is not created. I have compiled under the shipped 14.10 kernel and the 3.16.2 kernel referenced in the thread here. I do see the device under /sys/bus/sdio/devices like referenced in the thread here. In the past when I have had this happen it was the result of a conflict between wireless drivers. I am unsure how to directly troubleshoot that.
1. Could this be a wireless driver conflict?
2. Could I have a different hardware ID causing problems even though the source code seems set to accept all devices?
3. What troubleshooting steps can I take from here?
I wanted to update that I seem to have gotten it working!
Apparently the code hack I referenced did not work in the way I thought. I investigated inside the "virtual folder" of the SDIO device and found the device ID and replaced the one for "CONFIG_RTL8723B" in sdio_intf.c that I referenced earlier. The first address (0x024c) is the vendor ID which should remain the same. The second address (0xB723) is the device ID which should be changed to (for my hardware) 0x0523. I then recompiled and ran insmod and it works. I knew it worked because there was a slight delay when loading the module.
Thanks for encouraging me to press on with this.
-----------
I have a device with an rtl8723bs SDIO wireless card. The rtl8723as driver should support it as seen here: http://ubuntuforums.org/showthread.php?t=2249936&page=3&highlight=rtl8723bs, and on this source code page it seems to show support for all SDIO wireless adapters: https://github.com/hadess/rtl8723as/blob/3dd8594d850502fb76d0170209ef24d93e372753/os_dep/linux/sdio_intf.c .
I see the same lines in dmesg when the driver is loaded that the person on the thread here did:
[ 46.589898] 8723bs: module verification failed: signature and/or required key missing - tainting kernel
[ 46.604071] RTL871X: module init start version:v4.1.3_8883.20130902_v2
[ 46.964685] RTL871X: module init ret=0
Unfortunately for me, the wlan0 device or similar is not created. I have compiled under the shipped 14.10 kernel and the 3.16.2 kernel referenced in the thread here. I do see the device under /sys/bus/sdio/devices like referenced in the thread here. In the past when I have had this happen it was the result of a conflict between wireless drivers. I am unsure how to directly troubleshoot that.
1. Could this be a wireless driver conflict?
2. Could I have a different hardware ID causing problems even though the source code seems set to accept all devices?
3. What troubleshooting steps can I take from here?