Quote:
Originally Posted by mmihelic
Yes, you can use the "USB Toggle" script and the USBNET with Dropbear should work. But this is the only type of connectivity that will work!
If you try to enable anything else related to USB. I think that the Dropbear will cease to function.
I hate to be the bearer of bad news but there seems to be something wrong in general. My guess would be that some manipulation of the kernel (an incompatible module or an unanticipated change of environment by Nickel) or of the boot scripts messed up part of the low-level functionality.
I think that even pressing of the "suspend" button is not detected correctly or always, if at all.
I didn't notice most of these things because I am only interested in the USBNET and Koreader. I was not exercising anything else. However, now I tried using other functions of the KSM08, with FW4 and the new update included, and I have noticed more problems.
For instance, now I can scan for wireless networks in Nickel, but I cannot connect to any of them. The KSM WLAN scripts always report that the DND module (the second one - I don't have the device here) was not loaded. And no WLAN networks can be seen in the KSM even if the Nickel did show them but was unable to connect to them.
-- Regards, Matej.
|
Thank you for the information. One thing I see is that KSM tries to load the wrong modul, dhd instead of 8189fs. (I will upload the corrected file(s) when I am back at my pc.) But this does still not explain why you cannot connect to any network from within nickel. Did you try to reboot the device and than try to connect to a network from within nickel without touching wifi things first in KSM? You could also try to delete /etc/wpa_supplicant/wpa_supplicant.conf, in order to make a fresh start of the wifi connection business, and try then to connect in nickel.
As for connecting the device as usb mass storage (which is completely unrelated to dropbear), I notice that the FW 4.0.7523 package does not contain /drivers/mx6sl-ntx/usb/gadget/arcotg_udc.ko. I guess, however, this file lives still on the device (as part of the original FW).