my android device use rtl8192cu usb wifi. I have insmod 8192cu.ko, cfg80211.ko, rfkill.ko.
when i open wifi, the logcat show me:
01-02 00:01:06.660 E/WifiStateMachine( 2297): Failed to load driver!
01-02 00:01:06.660 E/WifiStateMachine( 2297): DriverFailedState
So does anyone know why the driver is loaded but would wrong ?
Beginning an error：
8192cu: Unknown symbol cfg80211_scan_done (err 0)
8192cu: Unknown symbol cfg80211_remain_on_channel_expired (err 0)
8192cu: Unknown symbol cfg80211_new_sta (err 0)
8192cu: Unknown symbol cfg80211_disconnected (err 0)
.......
So i load driver 8192cu.ko, cfg80211.ko and rfkill.ko, but it's also tell me wrong.
I think you had the airplane mode activated.
So, go to the settings/wireless&networks
and ensure that the airplane mode is not activated.
You need to load the kernel modules in the correct order.
Try to load the cfg80211.ko file first, followed by the rfkill and then the 8192cu.ko.
Related
i have an empty Flutter project where i enabled the splash screen, editing the android xml files as usually.
It work on my phone and show the image, on a Lenovo Tablet, it doesn't show the image and in debug console, it show the errors:
E/ion ( 4552): ioctl c0044901 failed with code -1: Invalid argument
D/hw-ProcessState( 4552): Binder ioctl to enable oneway spam detection failed: Invalid argument
The Flutter DevTools debugger and profiler on Lenovo TB125FU is available at: http://127.0.0.1:61763?uri=http://127.0.0.1:61760/0gkQ21ttmhA=/
E/OpenGLRenderer( 4552): fbcNotifyFrameComplete error: undefined symbol: fbcNotifyFrameComplete
E/OpenGLRenderer( 4552): fbcNotifyNoRender error: undefined symbol: fbcNotifyNoRender
Someone face this problem?
I am working with AOSP-Q. When i connect the pendrive to my android device, i am getting prints like :
[ 2955.285052] read strings
[ 2955.288151] init: processing action (sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) from (init.usb.configfs.rc:26)
[ 2955.303196] init: Command 'write /config/usb_gadget/g1/UDC ${sys.usb.controller}' action=sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1 (init.usb.configfs.rc:29) took 0ms and failed: Unable to write to file '/config/usb_gadget/g1/UDC': Unable to write file contents: Device or resource busy
I somewhere found that enabling the CONFIG_USB_CONFIGFS_F_FS config in the kernel causes that prints, so i disabled that config. Now i am not getting that prints when i connect pendrive but ADB over USB is not working for me. can anyone help me to get rid of that prints without effecting the ADB over USB functionality.
I am testing Relatek Wi-Fi Driver in Android LOllipop. The driver is registered as
usbcore: registered new interface driver rtl8192du
And the lsmod shows the output as
8192du 488167 0 - Live 0x00000000
The driver is inserted successfully . And the netcfg output shows that the wlan0 interface is down.
I tried to make the interface active as ifconfig wlan0 up and suddenly the kernel crashes and reboots after 5 seconds.
What are the reasons for the ifconfig to fail especially to crash the kernel?.....Any help would be appreciated
The kernel crash log is provided below
e[<8031bcf4>] (vsnprintf+0x38/0x424) from [<8004b534>] (kthread_create_on_node+0x98/0xdc)
[<8004b534>] (kthread_create_on_node+0x98/0xdc) from [<7f03d05c>] (rtw_start_drv_threads+0x20/0x5c [8192du])
[<80647c24>] (__dev_open+0xa0/0xfc) from [<80647e58>] (__dev_change_flags+0x8c/0x128)
[<80647e58>] (__dev_change_flags+0x8c/0x128) from [<80647f60>] (dev_change_flags+0x10/0x48)
[<80647f60>] (dev_change_flags+0x10/0x48) from [<806d16ac>] (devinet_ioctl+0x780/0x828)
[<806d16ac>] (devinet_ioctl+0x780/0x828) from [<806323c8>] (sock_ioctl+0x68/0x28c)
[<806323c8>] (sock_ioctl+0x68/0x28c) from [<800f09e8>] (do_vfs_ioctl+0x80/0x5bc)
[<800f09e8>] (do_vfs_ioctl+0x80/0x5bc) from [<800f0f94>] (SyS_ioctl+0x70/0x78)
[<800f0f94>] (SyS_ioctl+0x70/0x78) from [<8000e0c0>] (ret_fast_syscall+0x0/0x30)
Code: ba0000ee e59da014 e3a0b020 e59d1018 (e5d23000)
---[ end trace ffb896cf8181c101 ]---
Kernel panic - not syncing: Fatal exception
So many reasons..... but...
1) post backtrace (kernel backtrace) for more information
2) suspect ioctl which is connect to ifconfig - bring up the wlan (if it's not ioctl, then something else like proc, netlink or whatever to communicate kernel)
3) the vap (wlan) enable code itself
I think that we may need crash backtrace and we can understand it better....
I am using Odroid A device, which have bcm4239 wifi hardware(according to Hardkernel's spec. i don't know how to check this programatically). i have attached the log when i try to enable the wifi using
mWifiManager.setWifiEnabled(true).
I want to know the meaning of the log, especially "E/WifiHW(1175): FIRMWARE_LOADER faile" message.
Thank you!!
Below is the error log!!
I/WifiHW(1175): /sys/devices/platform/odroid-sysfs/wifi_enable : write success (on = 1)
I/WifiHW(1175): /sys/devices/platform/odroid-sysfs/wifi_nrst : write success (on = 1)
E/WifiHW(1175): FIRMWARE_LOADER faile
D/SoftapController(1079): Softap fwReload - Ok
D/NetworkManagementService(1175): rsp <213 (mac address here) 0.0.0.0 0 [up broadcast running multicast]>
D/CommandListener(1079): Setting iface cfg
D/CommandListener(1079): Trying to bring down wlan0
D/NetworkManagementService(1175): flags <[up broadcast running multicast]>
D/CommandListener(1079): broadcast flag ignored
E/WifiStateMachine(1175): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down broadcast running multicast]} failed with code 501 : {Flag unsupported}
E/wpa_supplicant(4058): Line 58: WPA-PSK accepted for key management, but no PSK configured.
E/wpa_supplicant(4058): Line 58: failed to parse network block.
I/wpa_supplicant(4058): rfkill: Cannot open RFKILL control device
E/WifiHW(1175): 'GET_NETWORK 0 bssid' fail.
...
I am using ICS 4.0.4..
Thanks in advance
i am getting following errors on starting the android vm (compiled from froyo branch) in virtual-box 4.0.4
D/ALSAModule(1985)open called for devices 00000002 in mode 0...
E/ALSALib (1985)external/alsa-lib/src/pcm/pcm.c:2203:(snd_pcm_open_noupdate) Unknown PCM AndroidPlayback_Speaker_normal
E/ALSALib (1985)external/alsa-lib/src/pcm/pcm.c:2203:(snd_pcm_open_noupdate) Unknown PCM AndroidPlayback_Speaker
E/ALSALib (1985)external/alsa-lib/src/pcm/pcm.c:2203:(snd_pcm_open_noupdate) Unknown PCM AndroidPlayback
D/ (1985)[external/alsa-lib/src/pcm/pcm_hw.c]:snd_pcm_hw_prepare
I/ALSAModule(1985)Initialized ALSA PLAYBACK device default
it seems the problem is with sound device (or ALSA) but I am not sure. Any help is appreciated.
I think that you are missing alsa config in your system image. Check if /system/etc/asound.conf is present or not. Try creating a new config file with default configuration. Check THIS for more details