[Q] Kernel module for GeneralTouch screen - Android Q&A, Help & Troubleshooting

Hello all,
I have a GeneralTouch monitor with touchscreen (vendor 0x0dfc product 0x0001) and eGalax touchpanel (vendor 0x0eef product 0x0001).
Stock firmware do not have drivers for them. I compiled it (usbtouchscreen.ko for both). eGalax touchpanel works great, but GeneralTouch monitors does not work. In /proc/kmsg I see:
Code:
<6>[90271.801406] usb 2-1.4: new full speed USB device number 46 using sw-ehci
<6>[90274.192316] init: waitpid returned pid 2176, status = 00000000
<3>[90274.198480] init: untracked pid 2176 exited
.
Why the kernel does not see the device? Of course usbtouchscreen.c contains code for GeneralTouch monitor.
What can I do to make it work?

Related

Atrix Webtop USB to Ethernet guide!

Question: How do I get USB to Ethernet to work on webtop? I don't have wifi and AT&T's coverage sucks!​
Answer:
Of course AT&T's coverage sucks! We all know this. At my work I don't have wifi, but I do have a USB port (that is linked to my university, not my work network). AT&T doesn't allow IRC over it's network, and my signal sucks (or doesn't work at all) a lot of the time, so I looked into USB-over-ethernet. Contrary to what moto says, it works. I don't know why they don't try to implement it, since it's pretty easy. You just need a bit of terminal skills.
NOTE: THIS SHOULD WORK ON OTHER MOTO-WEBTOP DEVICES AS WELL SINCE THEY ALL SHARE THE SAME LINUX BASE... SORT OF.
DISCLAIMER: IF THIS SOMEHOW BREAKS YOUR DEVICE, LEG, DOG, OR LIBIDO I AM NOT RESPONSIBLE, ALTHOUGH I'M PRETTY SURE IT WONT UNLESS YOU FUBAR IT.
I had help from Luminary(IRC)/Zxo0oxz and AR_(IRC)/ar31791on this cause I'm kind of a linux noob.
So I purchased a USB-to-Ethernet adapter: http://www.amazon.com/Plugable-Ethe.../B00484IEJS/ref=pd_cp_e_3/180-6608578-4269610 ($15). It has an ASIX AX88772 chipset in it, ASIX chipsets were the first usb-to-ethernet chipsets and they are nearly universally supported , especially on linux.
I am using the lapdock, no idea if this works with usb-otg, but you can try it if you want, but these directions won't work for you.
This guide assumes you have installed webtopmod or webtop2SD! Cause you need terminal access.
Boot to webtop, let it do it's thing. Open up LXTerminal.
Plug in your usb-toethernet device into one of the USB ports. Have it already connected to the router or whatever you are connecting it to via ethernet.
Run 'dmesg'. You should see somewhere recently a new USB device, most likely ASIX chipset. It should have a name with 'eth' in it, mine happened to be usbeth0.
Substitute DEVICENAME with what you just found it's name to be where it says DEVICENAME below.
If you run ifconfig DEVICENAME, it should print out some network related stuff if it finds your device. If it does, great, if not, well you might need to better guess the name, or it might just not be supported.
If you just run ifconfig, you won't see the device cause it is not yet active. eth0 is the atrix's wireless, if you turn wireless off it'll go away (as you can see in dmesg after you turn it off)
[Note: iwconfig doesn't exist on this distro, or it might just not be in PATH, I didn't both to look]
Assuming you found your device, if you do:
sudo ifconfig DEVICENAME up
the device should come up, and should be viewable under the command ifconfig.
Assuming you are using DHCP as a address provider, now run:
sudo dhclient DEVICENAME
and if it 'bounds' to an address, you're good to go! Turn off wifi and you should still be able to connect without AT&T's restrictions. If you make a script, this will run easily on the desktop!
I tried adding this device to webtop's interfaces file, but it ruined XFCE's bottom bar so I have to manually bring it up otherwise it breaks webtop. Also, not sure if this is related, but the wifi menu won't go away anymore either, but I haven't done too much testing.​
So here's an automagic script you can paste if your configuration works the same as mine (it most likely will):
Code:
sudo ifconfig usbeth0 up
sudo dhclient usbeth0
I know it's short, but I'm a noob, and I'm sure many others are noobs too, so I hope this helps.
Your milage may vary, but I hope this helps! If it does, click thanks Also be sure to thank the people who helped me!
Additional google tags:
Webtop USB to Ethernet Droid Bionic Photon Atrix lapdock
Hello,
HERE is an easier way.
Doum
Tried that, if the device isn't plugged in at webtop boot the dock will crash(at least xfce did) . I don't use usb to ethernet all the time.
Trolling from my ATRIX 4G's XDA premium app, still on the gold medal winner of worst customer satisfaction for the second year in a row! Congrats!
It works with the stock webtop as well. You just have to use the terminal app from the phone.
Once you plug in your adapter type netcfg if you have a usbeth0 you're golden, otherwise you probably need a different adapter. I've read where the adapters Apple sells for the MacBook Air work. I know my old ass trendnet 10/100 works, but my Linksys 10/100 doesn't.
Don't have it with me (I leave it at work), but does the phone data connection work if you turn it on airplane mode? I know the phone apps didn't when i turned off my apn, but webtop apps worked. (I didn't turn off cause i want phone calls... doesn't work if in airplane mode though)
Does it work on stock 2.3.4 unrooted
Hi all,
Sorry for digging up an old thread.
As in the title -- does this work on stock a 2.3.4, unrooted, unaltered Atrix?
I have an HD dock with an adapter plugged in. dmesg lists it as AX88x72A. netcfg shows usbeth0 DOWN.
Any pointers?
Thanks
the_ek
Hello, i bought usb ethernet AX88772B chipset.
I have it connected to my HD dock, The icon that appears usb is not defined ... I write in the terminal
$dmesg
shows It ....
[ 159.568498] usb 1-1.3: Product: AX88772B
[ 159.568505] usb 1-1.3: Manufacturer: ASIX Elec. Corp.
[ 159.568512] usb 1-1.3: SerialNumber: 000001
[ 159.569545] usb 1-1.3: configuration #1 chosen from 1 choice
[ 159.654475] usb 1-1.4: new full speed USB device using tegra-ehci and address 5
[ 159.698528] usb 1-1.4: New USB device found, idVendor=046d, idProduct=c52b
[ 159.698541] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 159.698550] usb 1-1.4: Product: USB Receiver
[ 159.698557] usb 1-1.4: Manufacturer: Logitech
[ 159.699546] usb 1-1.4: configuration #1 chosen from 1 choice
[ 159.706079] input: Logitech USB Receiver as /devices/platform/tegra-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input11
[ 159.711373] generic-usb 0003:046D:C52B.0002: input,hidraw1: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-tegra-ehci.0-1.4/input0
[ 159.724949] input: Logitech USB Receiver as /devices/platform/tegra-ehci.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input12
[ 159.731647] generic-usb 0003:046D:C52B.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-tegra-ehci.0-1.4/input1
[ 159.749265] generic-usb 0003:046D:C52B.0004: hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-tegra-ehci.0-1.4/input2
[ 159.835111] cpcap_usb_det cpcap_accy_whisper: ioctl cmd = 0x20000001
[ 160.774804] kxtf9_irq_work_func: status=0x4
[ 160.952127] [ 160.952130] nvmap_open: pid=2424
[ 161.680322] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0x0(0), webtop=0
[ 161.681118] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0x0(0), webtop=0
[ 164.634304] usb 1-1.3: USB disconnect, address 4
[ 164.907459] kxtf9_irq_work_func: status=0x4
[ 168.498157] [ 168.498160] nvmap_open: pid=2492
[ 169.891953] usb_ether_get_stats
[ 171.410448] init: untracked pid 5862 exited
[ 171.412412] init: untracked pid 5866 exited
[ 174.172841] init: untracked pid 5886 exited
[ 175.223813] init: untracked pid 5843 exited
[ 175.332466] [ 175.332469] nvmap_open: pid=5893
[ 175.593724] usb_ether_get_stats[ 175.594964] usb_ether_get_stats
[ 175.774803] init: untracked pid 5904 exited
[ 175.905551] usb_ether_get_stats
[ 175.915405] usb_ether_get_stats
[ 175.930769] usb_ether_get_stats
[ 176.131303] init: untracked pid 5849 exited
[ 176.833385] init: untracked pid 5936 exited
[ 176.966487] init: untracked pid 5932 exited
[ 177.040167] init: untracked pid 5938 exited
[ 177.050725] init: untracked pid 5934 exited
[ 177.116540] init: untracked pid 5941 exited
[ 177.579153] init: untracked pid 5952 exited
[ 177.731212] init: untracked pid 5966 exited
[ 177.906299] [ 177.906302] nvmap_open: pid=5964
[ 178.297521] nvmap_open: pid=5968
[ 178.499540] usb_ether_get_stats
[ 178.508834] init: untracked pid 5975 exited
[ 180.297833] kxtf9_misc_ioctl: SET_DELAY 200
[ 180.384618] kxtf9_misc_ioctl: SET_DELAY 200
[ 180.477737] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0xf(15), webtop=0
[ 182.758270] lm3532_webtop_brightness_set: lcd-backlight-webtop, 0xf(15), webtop=1
[ 186.215847] usb_ether_get_stats
[ 192.261014] CPU0 attaching NULL sched-domain.
[ 192.261038] CPU1 attaching NULL sched-domain.
[ 192.364916] CPU0 attaching NULL sched-domain.
[ 192.365442] CPU1: clean shutdown
[ 204.847261] init: untracked pid 6113 exited
[ 213.561522] [ 213.561525] nvmap_release: pid=3622, org_pid=3622CPU1: Booted secondary processor
[ 214.474831] CPU0 attaching NULL sched-domain.
[ 214.554338] CPU0 attaching sched-domain:
[ 214.554351] domain 0: span 0-1 level CPU
[ 214.554361] groups: 0 1
[ 214.554376] CPU1 attaching sched-domain:
[ 214.554384] domain 0: span 0-1 level CPU
[ 214.554392] groups: 1 0
[ 219.098833] CPU0 attaching NULL sched-domain.
[ 219.098886] CPU1 attaching NULL sched-domain.
[ 219.214408] CPU0 attaching NULL sched-domain.
[ 219.215582] CPU1: clean shutdown
[ 236.235491] lm3532_brightness_set: lcd-backlight, 0x1c(28), webtop=1
[ 733.438025] kxtf9_irq_work_func: status=0x4
[ 733.454909] usb 1-1.3: new high speed USB device using tegra-ehci and address 6
[ 733.508607] usb 1-1.3: New USB device found, idVendor=0b95, idProduct=772b
[ 733.508653] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 733.508692] usb 1-1.3: Product: AX88772B
[ 733.508721] usb 1-1.3: Manufacturer: ASIX Elec. Corp.
[ 733.508751] usb 1-1.3: SerialNumber: 000001
[ 733.513180] usb 1-1.3: configuration #1 chosen from 1 choice
[ 774.880346] usb_ether_get_stats
[ 774.883319] [email protected]:/$
But I can't find anywhere that was eth0 ....
You solve this issue with the usb ethernet?
Might be usb_ether, Im not very good with the linux shell yet so I don't know how to look it up. Mine always showed eth0. Ill look at it more later today and post my dmesg when I get the chance.
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
Apple Macbook Air Ethernet
Has anyone tried to use the Apple Macbook Air Ethernet adapter? I'd love to get that to work.
Mine is an AX88x72A -- not sure if the B in yours makes a difference. Mine is listed as usbeth0 in dmesg and netcfg.
the_ek said:
Mine is an AX88x72A -- not sure if the B in yours makes a difference. Mine is listed as usbeth0 in dmesg and netcfg.
Click to expand...
Click to collapse
I assumed it worked for you, yes?
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
I followed the instructions in
http://forum.xda-developers.com/showthread.php?t=1327165
Webtop seems to work o.k. The phone browser etc. does not automatically recognize it even though netcfg shows that usbeth0 is up and connected.
the_ek said:
Mine is an AX88x72A -- not sure if the B in yours makes a difference. Mine is listed as usbeth0 in dmesg and netcfg.
Click to expand...
Click to collapse
Hi, I tried to enter usb_ether ... Nothing helps. As far as I can see there is no difference between AX88x72A and B.
Maybe it's because of the fact that I connect to the HDDock?
Sorry for not being much help. My set-up is the same (apart from the adapter) --> Atrix in HD-Dock, USB to Ethernet Adapter in USB slot, and RJ45 from there. When I first plugged the adapter into the dock and then put the Atrix in the dock, the leds in the Adapter lit up, netcfg / dmesg showed that I had connected a new device (Asix ...), but that usbeth0 was down. After following the instructions I linked in post 12 above, netcfg showed that usbeth0 was up and had an IP address. Webtop, phone browser, market seem to be working o.k. (phone browser did not work at first, but did after a while).
the_ek said:
Sorry for not being much help. My set-up is the same (apart from the adapter) --> Atrix in HD-Dock, USB to Ethernet Adapter in USB slot, and RJ45 from there. When I first plugged the adapter into the dock and then put the Atrix in the dock, the leds in the Adapter lit up, netcfg / dmesg showed that I had connected a new device (Asix ...), but that usbeth0 was down. After following the instructions I linked in post 12 above, netcfg showed that usbeth0 was up and had an IP address. Webtop, phone browser, market seem to be working o.k. (phone browser did not work at first, but did after a while).
Click to expand...
Click to collapse
Hi,
what's your adapter ? ASIX AX88772 A or B ????????
As stated in posts 6, 10, 11, and the one you quoted yourself in post 13 --> it is an ASIX AX88x72 A
the_ek said:
As stated in posts 6, 10, 11, and the one you quoted yourself in post 13 --> it is an ASIX AX88x72 A
Click to expand...
Click to collapse
Hi,
I will buy third...and i will be collector
@praded2007
Did you get it to work?
Testing out CM7. Not sure if I like it over stock. Miss webtop and real fingerprint scannner...
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
Just in case anyone is interested. The usb ethernet adapter also works via otg cable and hub.

[Q] wifi module problem with faux123 kernel-MB860

I am trying an experiment with my Atrix in which I need to be able to build the kernel and have a working wifi module. I have successfully built the faux123's kernel-MB860 (thanks very much!).
I then downloaded faux123's atrix-wifi-module in order to get wifi working. I have built the module, and pushed it to /system/lib/modules. However, wifi doesn't work. Under settings, it just displays "error". dmesg doesn't show nearly as much as a kernel packaged by faux123. Here is my output:
Code:
<4>[ 24.504982] sdhci_tegra_wlan_detect Detecting WLAN
<4>[ 24.504998] mot_wifi_set_carddetect: Nobody to notify
<4>[ 24.507937]
<4>[ 24.507940] Dongle Host Driver, version 4.218.248.31
<4>[ 24.507944] Compiled in /home/kenny/android/atrix-wifi-module/open-src/src/dhd/linux/../.. on Apr 17 2012 at 06:54:15
<6>[ 24.724025] request_suspend_state: wakeup (3->0) at 13492036210 (2012-04-21 19:25:46.351491984 UTC)
<6>[ 24.725196] lm3532_brightness_set: lcd-backlight, 0x4c(76), webtop=0
<7>[ 25.088713] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 25.088824] mmc1: new SDIO card at address 0001
<6>[ 25.534772] usb_ether_get_stats
Whereas, dmesg from a kernel/module packaged by faux123 displays:
Code:
[ 49.811365] sdhci_tegra_wlan_detect Detecting WLAN
[ 49.811403] mot_wifi_set_carddetect: Nobody to notify
[ 49.812815]
[ 49.812818] Dongle Host Driver, version 4.218.248.31
[ 49.812822] Compiled in /home/paul/Froyo/system/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/../.. on Dec 17 2011 at 19:58:57
[ 50.108317] mmc1: queuing CIS tuple 0x91 length 3
[ 50.108350] mmc1: new SDIO card at address 0001
[ 50.136595] alloc static buf at e9980000!
[ 50.136975] F1 signature read @0x18000000=0x9934329
[ 50.139716] DHD: dongle ram size is set to 294912(orig 294912)
[ 50.143537] wl_iw_attach thr:6d0 started
[ 50.143598] wl_iw_bt_init thr:6d1 started
[ 50.143655] dhd_attach thr:6d2 started
[ 50.143706] dhd_attach thr:6d3 started
[ 50.143749] dhd_attach thr:6d4 started
[ 50.191722] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 50.273753] wifi_get_mac_addr
[ 50.274700] Firmware version = wl0: May 6 2011 13:09:01 version 4.218.248.31
[ 50.442416] eth0: Broadcom Dongle Host Driver mac=40:fc:89:13:a8:83
If I try to do a insmod, I get an invalid argument message.
Code:
# insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Invalid argument)
Can someone suggest what I might be missing or doing wrong?
as far as i've researched this problem, it's hardware related. i get the same error (and an accompanying reboot) every time i try to toggle wifi.
http://forum.xda-developers.com/showthread.php?t=1205775
if you have any more success please let me know.
dLo GSR said:
as far as i've researched this problem, it's hardware related.
Click to expand...
Click to collapse
I'm not convinced it is hardware related (other than maybe having the wrong driver), since wifi works great using a true faux123 kernel/module.
I suspect my problem has something to do with how I compiled module or other files that I need to put on the phone.
How did you build it? A little more background might help
Build process ... it works!?!?
First, the good news...the module now works. But I don't understand what I may have done differently this time other than do the builds consecutively.
I retrieved the source:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel
$ git clone https://github.com/faux123/kernel-MB860.git
$ cd ~/android
$ git clone https://github.com/faux123/atrix-wifi-module.git
Then I built:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm tegra_olympus_cm7_defconfig
$ make ARCH=arm CROSS_COMPILE=/home/kenny/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ cd ../../atrix-wifi-module/open-src/src/dhd/linux/
$ export LINUXSRCDIR=/home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm CROSS_COMPILE=~/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ adb push /home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/dhd.ko /system/lib/modules/dhd.ko
I had kernel built a few days before I had found the wifi module source. I then tried building the wifi module and pushing the module as shown above.
Since then (over last week or so), I have tried a number of things, including copying files (/etc/firmware/wifi/*) from another phone which has a faux123 kernel. Are these files required? Are there steps in here that I missed?

[Q] Android 4.4 on Archos

I have an Archos 80G9 250GB HDD version, in stock FW, now replaced with an Xperia tablet for my regular use. The Archos had low RAM and had started crying for help although it was good as a media device..The Android 4.4 release was mentioned as also suited for units with 512 MB RAM,, so I was wondering if anyone would be able to provide a build for good old Archos ? Clearly Archos has given up on it (and themselves I think) so can anyone throw some light on if we can resurrect this old tablet with Kit Kat?
4.4 (CM 11) was mentioned in the CM 10.2 thread. It will probably happen eventually. But I wouldn't get your hopes up that it might be faster. Google isn't lightening up their OS with each new revision, nor are the apps getting lighter. 512MB just isn't enough RAM for a quality experience.
Hi!
Currently I'm running some early alpha builds
Camera is working. HD Video also.
Sound, thanks to the adapted audio hal (also included in CM10.2) build is also working.
Thanks @Hashcode we have got a fixed rotation and screenshot functionality for our 4430/4460 processors which works really good =) (Without the known artifacts).
But there are some glitches (I have not tested everything) that I found out:
WLAN isn't working right. There are very much
Code:
E/wpa_supplicant( 1017): recvfrom(ctrl_iface): Try again
in the code. So it seems that this isn't working correctly. (Tough, connection is established and working but the blue WLAN icon is white).
The current bug (OOM) is at the easter egg screen, when tapping on the "android version" label on the settings page.
Code:
[0m[38;5;40mI/cat ( 609): <6>[ 99.693603] PVR_K: RA_Alloc FAILED : arena=PDSPixelCodeData, size=0xd000(0xd000), alignment=0x0, offset=0x0
[0m[38;5;40mI/cat ( 609): <6>[ 99.693756] PVR_K:
[0m[38;5;40mI/cat ( 609): <6>[ 99.693756] Command Line of the current process with ID 2749 is com.android.systemui:sweetsweetdesserts
[0m[38;5;40mI/cat ( 609): <6>[ 99.693939] PVR_K: Base Name of the current process with ID 2749 is com.android.systemui:sweetsweetdesserts
[0m[38;5;40mI/cat ( 609): <6>[ 99.694000] PVR_K: Arena 'PDSPixelCodeData':
[0m[38;5;40mI/cat ( 609): <6>[ 99.694122] PVR_K: allocCB=bf1b2240 freeCB= (null) handle=c9966840 quantum=4096
[0m[38;5;40mI/cat ( 609): <6>[ 99.694183] PVR_K: span count 1
[0m[38;5;40mI/cat ( 609): <6>[ 99.694274] PVR_K: live segment count 159
[0m[38;5;40mI/cat ( 609): <6>[ 99.694335] PVR_K: free segment count 4294967295
[0m[38;5;40mI/cat ( 609): <6>[ 99.694396] PVR_K: free resource count 0 (0x0)
[0m[38;5;40mI/cat ( 609): <6>[ 99.694519] PVR_K: total allocs 159
[0m[38;5;40mI/cat ( 609): <6>[ 99.694580] PVR_K: total failed allocs 0
[0m[38;5;40mI/cat ( 609): <6>[ 99.694702] PVR_K: total frees 0
[0m[38;5;40mI/cat ( 609): <6>[ 99.694763] PVR_K: import count 0
[0m[38;5;40mI/cat ( 609): <6>[ 99.694824] PVR_K: export count 0
I have no glue how to fix this error
Maybe other devs jumped in. We should wait a little bit until CM stabilizes. Currently there are so much code changes ongoing, it makes no sense to release a version.
Quallenauge said:
Hi!
Currently I'm running some early alpha builds
Camera is working. HD Video also.
Sound, thanks to the adapted audio hal (also included in CM10.2) build is also working.
Thanks @Hashcode we have got a fixed rotation and screenshot functionality for our 4430/4460 processors which works really good =) (Without the known artifacts).
But there are some glitches (I have not tested everything) that I found out:
WLAN isn't working right. There are very much
Code:
E/wpa_supplicant( 1017): recvfrom(ctrl_iface): Try again
in the code. So it seems that this isn't working correctly. (Tough, connection is established and working but the blue WLAN icon is white).
The current bug (OOM) is at the easter egg screen, when tapping on the "android version" label on the settings page.
Code:
[0m[38;5;40mI/cat ( 609): <6>[ 99.693603] PVR_K: RA_Alloc FAILED : arena=PDSPixelCodeData, size=0xd000(0xd000), alignment=0x0, offset=0x0
[0m[38;5;40mI/cat ( 609): <6>[ 99.693756] PVR_K:
[0m[38;5;40mI/cat ( 609): <6>[ 99.693756] Command Line of the current process with ID 2749 is com.android.systemui:sweetsweetdesserts
[0m[38;5;40mI/cat ( 609): <6>[ 99.693939] PVR_K: Base Name of the current process with ID 2749 is com.android.systemui:sweetsweetdesserts
[0m[38;5;40mI/cat ( 609): <6>[ 99.694000] PVR_K: Arena 'PDSPixelCodeData':
[0m[38;5;40mI/cat ( 609): <6>[ 99.694122] PVR_K: allocCB=bf1b2240 freeCB= (null) handle=c9966840 quantum=4096
[0m[38;5;40mI/cat ( 609): <6>[ 99.694183] PVR_K: span count 1
[0m[38;5;40mI/cat ( 609): <6>[ 99.694274] PVR_K: live segment count 159
[0m[38;5;40mI/cat ( 609): <6>[ 99.694335] PVR_K: free segment count 4294967295
[0m[38;5;40mI/cat ( 609): <6>[ 99.694396] PVR_K: free resource count 0 (0x0)
[0m[38;5;40mI/cat ( 609): <6>[ 99.694519] PVR_K: total allocs 159
[0m[38;5;40mI/cat ( 609): <6>[ 99.694580] PVR_K: total failed allocs 0
[0m[38;5;40mI/cat ( 609): <6>[ 99.694702] PVR_K: total frees 0
[0m[38;5;40mI/cat ( 609): <6>[ 99.694763] PVR_K: import count 0
[0m[38;5;40mI/cat ( 609): <6>[ 99.694824] PVR_K: export count 0
I have no glue how to fix this error
Maybe other devs jumped in. We should wait a little bit until CM stabilizes. Currently there are so much code changes ongoing, it makes no sense to release a version.
Click to expand...
Click to collapse
Hi quallenauge!
I work on Kitkat for our old Gen8. I have trouble with wifi too. Driver is loaded but no firmware.
But for your driver i have ported the V1.8 version (from my pvrversion.h in driver/gpu/pvr/):
Code:
#define PVRVERSION_FAMILY "sgxddk"
#define PVRVERSION_BRANCHNAME "1.8"
#define PVRVERSION_BUILD 789263
#define PVRVERSION_BSCONTROL "blaze_android_sgx_ogles1_ogles2_GPL"
#define PVRVERSION_STRING "blaze_android_sgx_ogles1_ogles2_GPL sgxddk 18 [email protected]" PVR_STR2(PVRVERSION_BUILD)
#define PVRVERSION_STRING_SHORT "[email protected]" PVR_STR2(PVRVERSION_BUILD)
I think/believe that it's compatible with PVR540, i have no problem with it
And used same GPU/Graphics configuration in boardconfig.mk than Quarkx for Defy.
Bizcuite
bizcuite said:
Hi quallenauge!
I work on Kitkat for our old Gen8. I have trouble with wifi too. Driver is loaded but no firmware.
But for your driver i have ported the V1.8 version (from my pvrversion.h in driver/gpu/pvr/):
Code:
#define PVRVERSION_FAMILY "sgxddk"
#define PVRVERSION_BRANCHNAME "1.8"
#define PVRVERSION_BUILD 789263
#define PVRVERSION_BSCONTROL "blaze_android_sgx_ogles1_ogles2_GPL"
#define PVRVERSION_STRING "blaze_android_sgx_ogles1_ogles2_GPL sgxddk 18 [email protected]" PVR_STR2(PVRVERSION_BUILD)
#define PVRVERSION_STRING_SHORT "[email protected]" PVR_STR2(PVRVERSION_BUILD)
I think/believe that it's compatible with PVR540, i have no problem with it
And used same GPU/Graphics configuration in boardconfig.mk than Quarkx for Defy.
Bizcuite
Click to expand...
Click to collapse
Congratulation for your Kitkat effor on Archos G8! I really was surprised when I read your thread (today). :good::good:
Which WLAN driver you are using? I'm using the current one from ol_R5.SP5.01 (which is included in the CM-11.0 repo).
Does the G8 also using the wl127xx ? What is failing?
For the graphics, I'm using the GFX version [email protected] which is also included in other repos such as the KFire repo from @Hashcode . Hm, maybe I should use an older one (the current from prop. common). I will check that out soon.
With no problems, do you mean the easter egg is playing correctly?
Cheers =)
Quallenauge said:
Congratulation for your Kitkat effor on Archos G8! I really was surprised when I read your thread (today). :good::good:
Which WLAN driver you are using? I'm using the current one from ol_R5.SP5.01 (which is included in the CM-11.0 repo).
Does the G8 also using the wl127xx ? What is failing?
For the graphics, I'm using the GFX version [email protected] which is also included in other repos such as the KFire repo from @Hashcode . Hm, maybe I should use an older one (the current from prop. common). I will check that out soon.
With no problems, do you mean the easter egg is playing correctly?
Cheers =)
Click to expand...
Click to collapse
Hi Quallenauge,
Sorry no times to answer.
I didn't know which problem exactly you had like pb with GPU driver. I thunk that you had this logcat at start.
I don't know if i can play correctly any video/others. I have just the launcher ATM (no internal/ext SD, no OMX codecs configured, no sound).
For wifi i use kernel's archos drivers or CM11 drivers.
The driver is loaded, but the logcat says me that it cannot configure the int wlan0, because it doesn't exist.
I think that is a problem of configuration before the compilation.
I must see how work exactly the wifi and work on it, but no times.
Have you progress about your pb of wifi? Have you got a logcat to share about this to see if the problem is same?
Bizcuite

Archos 101 g9 8gb & Huawei modem E173u-1[No driver found]

Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus

Vivo 1901 SP Flash Tools ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142)

Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar

Categories

Resources