Database Info

USB Ethernet questions/help required

I have a USB Ethernet adapter that I picked up on Ebay for $0.99. I thought it might be a good experiment to see if I can get it to work on my TF but I am stumped. The device works in Ubuntu (on my laptop) and shows the following in DMESG.
[ 55.364166] usb 8-1: new full speed USB device using uhci_hcd and address 2
[ 55.572788] dm9601 8-1:1.0: eth1: register 'dm9601' at usb-0000:00:1d.2-1, Davicom DM9601 USB Ethernet, 00:e0:4c:53:44:58
[ 55.573048] usbcore: registered new interface driver dm9601
[ 55.680218] eth1: link up, 100Mbps, full-duplex, lpa 0xFFFF
When I plug it into my TF (rooted) and look at the DMESG there I see the following:
<6>[ 4407.535596] usb 1-1.1: new full speed USB device using tegra-ehci and address 6
<6>[ 4407.575370] usb 1-1.1: New USB device found, idVendor=0fe6, idProduct=9700
<6>[ 4407.575430] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
<6>[ 4407.575479] usb 1-1.1: Product: USB 2.0 10/100M Ethernet Adaptor
<4>[ 4407.575522] device: '1-1.1': device_add
<4>[ 4407.581027] device: '1-1.1:1.0': device_add
<4>[ 4407.586882] device: 'ep_81': device_add
<4>[ 4407.587159] device: 'ep_02': device_add
<4>[ 4407.587357] device: 'ep_83': device_add
<4>[ 4407.587557] device: 'usbdev1.6': device_add
<4>[ 4407.590505] device: 'ep_00': device_add
At this point I was hoping that I could just do a netcfg eth0 dhcp and be good to go but the TF keeps saying that eth0 is not a valid interface (which lines up with what I see in the DMESG). I did try assigning an IP to usb0 but was unable to get connectivity out and I still am struggling with adding a default route since the 'route' command just keeps saying invalid argument.
Is there something special I need to do to get the OS to at the eth0 interface when the USB Ethernet adapter is connected? I am wondering if there is a driver I need to compile/load? I tried the USB-Ethernet driver pack mentioned in the developer forum but it does not seem to help - I get an error when I type in usb_ethernet indicating eth0 does not exist. Any help would be appreciated.
Thanks
Toby

Galaxy young GT-S35360 OTG driver (usb host mode) help please

Hi,
I am now working on the usb OTG driver for galaxy-y
I almost sure that this device is a OTG capable device, (I found this from its service manual http://forum.xda-developers.com/showthread.php?t=1489767)
After some work I compiled otg supported usb driver as loadable module (dwc_otg.ko).
In the original firm ware this driver is 'in-built' and host support is diabled
and I could load the module
The dmesg is ...
Code:
[hari]#
[hari]# insmod /sdcard/otgg/j/dwc_otg.ko
<6>[ 2688.406677] dwc_otg: version 2.60a 22-NOV-2006
<6>[ 2688.406829] lm_driver_register()
<6>[ 2688.406890] lm_match()
<6>[ 2688.406951] lm_bus_probe()
<3>[ 2688.406982] Debug level= 17
<3>[ 2688.407012] dwc_otg lm-2: dwc_otg_driver_probe, version 020-10-01-09
<6>[ 2688.407318] It is Ok to create charging current work queue...
<4>[ 2688.407592] DWC_otg: 1
<4>[ 2688.407623] DWC_otg: 2
<4>[ 2688.407653] DWC_otg: dwc_otg_core_reset() GRSTCTL=80000000
<4>[ 2688.407684] DWC_otg: dwc_otg_core_reset() value to set=80000001
<4>[ 2688.517852] DWC_otg: b
<4>[ 2688.517913] DWC_otg: dwc_otg_core_reset() HANG! Soft Reset GRSTCTL=80000001
<6>[ 2688.517944] DWC_otg: Core Global Registers
<6>[ 2688.517974] DWC_otg: GOTGCTL @0xD8400000 : 0x00110000
<6>[ 2688.518005] DWC_otg: GOTGINT @0xD8400004 : 0x00000000
<6>[ 2688.518035] DWC_otg: GAHBCFG @0xD8400008 : 0x00000000
<6>[ 2688.518066] DWC_otg: GUSBCFG @0xD840000C : 0x00001400
<6>[ 2688.518096] DWC_otg: GRSTCTL @0xD8400010 : 0x80000001
<6>[ 2688.518127] DWC_otg: GINTSTS @0xD8400014 : 0x04000021
<6>[ 2688.518157] DWC_otg: GINTMSK @0xD8400018 : 0x00000000
<6>[ 2688.518188] DWC_otg: GRXSTSR @0xD840001C : 0xFFFFFFFF
<6>[ 2688.518188] DWC_otg: GRXFSIZ @0xD8400024 : 0x00001000
<6>[ 2688.518218] DWC_otg: GNPTXFSIZ @0xD8400028 : 0x10001000
<6>[ 2688.518615] DWC_otg: GNPTXSTS @0xD840002C : 0x00081000
<6>[ 2688.518646] DWC_otg: GI2CCTL @0xD8400030 : 0x00000000
<6>[ 2688.518676] DWC_otg: GPVNDCTL @0xD8400034 : 0x00000000
<6>[ 2688.518707] DWC_otg: GGPIO @0xD8400038 : 0x00000000
<6>[ 2688.518737] DWC_otg: GUID @0xD840003C : 0x00000000
<6>[ 2688.518768] DWC_otg: GSNPSID @0xD8400040 : 0x4F54281A
<6>[ 2688.518798] DWC_otg: GHWCFG1 @0xD8400044 : 0x00000000
<6>[ 2688.518829] DWC_otg: GHWCFG2 @0xD8400048 : 0x229FFDD0
<6>[ 2688.518859] DWC_otg: GHWCFG3 @0xD840004C : 0x0F8007E8
<6>[ 2688.518859] DWC_otg: GHWCFG4 @0xD8400050 : 0xFFF08030
<6>[ 2688.518890] DWC_otg: HPTXFSIZ @0xD8400100 : 0x02001020
<4>[ 2688.518920] DWC_otg: 3
<4>[ 2688.627838] DWC_otg: 1
<4>[ 2688.627899] DWC_otg: 2
<4>[ 2688.627929] DWC_otg: dwc_otg_core_reset() GRSTCTL=80000001
<4>[ 2688.627960] DWC_otg: dwc_otg_core_reset() value to set=80000001
<4>[ 2688.737762] DWC_otg: b
<4>[ 2688.737823] DWC_otg: dwc_otg_core_reset() HANG! Soft Reset GRSTCTL=80000001
<4>[ 2688.737854] DWC_otg: 3
<4>[ 2688.846557] dwc_otg_pcd_init(d2a03460)
<4>[ 2688.846618] Dedicated Tx FIFOs mode
<4>[ 2688.846740] registering handler for irq21
<6>[ 2688.846832] DWC_otg: pcd->setup_pkt=0xff6b3000, pcd->setup_pkt_dma_handle=0x92985000
<6>[ 2688.846893] DWC_otg: pcd->status_buf=0xff6b4000, pcd->status_buf_dma_handle=0x92984000
<4>[ 2688.846923] pcd->setup_pkt=0xff6b3000, pcd->setup_pkt_dma_handle=0x92985000
<4>[ 2688.846954] pcd->status_buf=0xff6b4000, pcd->status_buf_dma_handle=0x92984000
<6>[ 2688.846984] DWC_otg: Using DMA mode
<6>[ 2688.847015] dwc_otg lm-2: DWC OTG Controller
<6>[ 2688.847076] dwc_otg lm-2: new USB bus registered, assigned bus number 1
<6>[ 2688.847137] dwc_otg lm-2: irq 21, io mem 0x00000000
<6>[ 2688.847198] DWC_otg: Init: Port Power? op_state=1
<6>[ 2688.847229] DWC_otg: Init: Power Port (0)
<7>[ 2688.847351] usb usb1: default language 0x0409
<7>[ 2688.847412] usb usb1: udev 1, busnum 1, minor = 0
<6>[ 2688.847442] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 2688.847473] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 2688.847503] usb usb1: Product: DWC OTG Controller
<6>[ 2688.847534] usb usb1: Manufacturer: Linux 2.6.35.7 dwc_otg_hcd
<6>[ 2688.847564] usb usb1: SerialNumber: lm-2
<7>[ 2688.849395] usb usb1: usb_probe_device
<7>[ 2688.849456] usb usb1: configuration #1 chosen from 1 choice
<7>[ 2688.849517] usb usb1: adding 1-0:1.0 (config #1, interface 0)
<7>[ 2688.850860] hub 1-0:1.0: usb_probe_interface
<7>[ 2688.850891] hub 1-0:1.0: usb_probe_interface - got id
<6>[ 2688.850921] hub 1-0:1.0: USB hub found
<6>[ 2688.850952] hub 1-0:1.0: 1 port detected
<7>[ 2688.850982] hub 1-0:1.0: standalone hub
<7>[ 2688.850982] hub 1-0:1.0: ganged power switching
<7>[ 2688.851013] hub 1-0:1.0: individual port over-current protection
<7>[ 2688.851043] hub 1-0:1.0: power on to power good time: 2ms
<7>[ 2688.851074] hub 1-0:1.0: local power source is good
<7>[ 2688.851074] hub 1-0:1.0: enabling power on all ports
[hari]# <7>[ 2688.948211] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[hari]# cat /sys/devices/lm-2/mode
<1>[ 2760.955230] Unable to handle kernel paging request at virtual address 73656300
<1>[ 2760.955291] pgd = c7640000
<1>[ 2760.955322] [73656300] *pgd=00000000
Connection closed by foreign host.
The problem is that when i tried to view or change the the mode , here (cat /sys/devices/lm-2/mode ), the phone reboots!!!!!!!!
I am a beginner in kernel development and this is my first experiment with kernel modules.
In the current situation I cant get (I dont know how to get) any log or something from the kernel. I dont know how to bug this kernel module
So any one has experience in kernel debugging please help me
In the kernel configuration I found a feature 'KGDB seial debugger' but... I dont know how to get a 'seial port' on my galaxy-y
Any one please help me

Good start,even Im crazy for that .But sorry can't help you.Plz contact Maroc-Os, but he is busy with kernel.

May I know who is Maroc-Os
Please give his details.

wow, i thinking the same think after read that file. and while browsing i find other product from broadcom bcm2153 also have usb otg. i still can't find usb otg cable to try it.
your log, look like memory issue. do you already recompile (and boot) your kernel without dw_otg ?

you may also contact vivekalady. you can find him in vivek kernel post in this section

cool
wow. excellent research. usb host mode would be a kickass feature
raspberry also uses that driver
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DWC OTG Controller usb usb1: Manufacturer: Linux 2.6.35.7 dwc_otg_hcd
usb usb1: SerialNumber: bcm2708_usb
http://www.raspberrypi.se/specifikation
maybe there are some similarities or people have experience with that hardware

How did you connect the hardware ??
the phone does not supply for the device so power must be given separately.so that hardware mechanism must be made.then only we can start.I hope you are doing this way.you can contact DoomLord for OTG supports

To:mai77
Hai,
the source code for product you specified is released???
I just looked the the site and i couldn't find
thanks.....

harish2704 said:
In the kernel configuration I found a feature 'KGDB seial debugger' but... I dont know how to get a 'serial port' on my galaxy-y
Click to expand...
Click to collapse
sounds like kernel debugger,
but I wonder what specialty it would offer at all, if transmit over serial instead of USB or whatever. I am assuming we can run the regular kernel debugger in SGY
http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:debug:kgdb
maybe Maroc can build a debug kernel for us ...

vivekkalady said:
How did you connect the hardware ??
the phone does not supply for the device so power must be given separately.so that hardware mechanism must be made.then only we can start.I hope you are doing this way.you can contact DoomLord for OTG supports
Click to expand...
Click to collapse
hai,
I didn't connected the hardware. I just rmmod'd the module (which doesn't support host mode)
and inserted the new module with host support.
The kmesg is posted in my post
then I tried to view the current mode (whether host or slave) by using
Code:
cat /sys/devices/lm-2/mode
then the phone rebooted suddenly
I run this commands as a remote session using telnetd
Thats how I got this logs
sorry for my language

harish2704 said:
I run this commands as a remote session using telnetd
Click to expand...
Click to collapse
does telnetd offer any advantages over "adb shell" ?

mai77 said:
sounds like kernel debugger,
but I wonder what specialty it would offer at all, if transmit over serial instead of USB or whatever. I am assuming we can run the regular kernel debugger in SGY
http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:debug:kgdb
maybe Maroc can build a debug kernel for us ...
Click to expand...
Click to collapse
I think remote debugging have only two options here
1) through serial interface
2) through ethernet (using wifi)
beacause we are already working with usb driver using usb inerface will not work
I prefer serial interface (i tink it will have more access)
In the service manual I saw some "Master_JTAG_pad"
do you know its usage ?

not that particular one

harish2704 said:
In the service manual I saw some "Master_JTAG_pad"
do you know its usage ?
Click to expand...
Click to collapse
you need jtag programmer, development tools for bcm21553, and doc/datasheet for bcm21553.

harish2704 said:
May I know who is Maroc-Os
Please give his details.
Click to expand...
Click to collapse
You can find him here
forum.xda-developers.com/showthread.php?t=1550065
Even Vivek,Mai is here too.

Unknown symbol __aeabi_uldivmod ARM bit
Hai,
any one knows how to avoid this error while compiling the kernel
this part of code
Code:
#define DIVMOD_WORD(q, r, hi, lo, w) do { \
BignumDblInt n = (((BignumDblInt)hi) << BIGNUM_INT_BITS) | lo; \
q = n / w; \
r = n % w; \
} while (0)
// where BignumDblInt is defined as uint64_t
// "typedef uint64_t BignumDblInt;"
produces this error while loading module
mod post also gives the same
I think its a EABI related issue
Code:
Unknown symbol __aeabi_uldivmod (err 0)

at runtime that symbol / lib is inaccessible. maybe it was excluded by some compiler switch or whatever. is is defined multiple times / files ?

source of dwc_otg driver (not working)
Here I attached source and changed files from which I compiled dwc_otg.ko
This is a part of "GT-S5360_GB_Opensource_Update2.zip" whch was published by samsung at opensource.samsung.com
Added a Patch

?
harish2704 said:
Here I attached source and changed files from which I compiled dwc_otg.ko
This is a part of "GT-S5360_GB_Opensource_Update2.zip" whch was published by samsung at opensource.samsung.com
Added a Patch
Click to expand...
Click to collapse
does it work now?

harish2704 said:
Here I attached source and changed files from which I compiled dwc_otg.ko
This is a part of "GT-S5360_GB_Opensource_Update2.zip" whch was published by samsung at opensource.samsung.com
Added a Patch
Click to expand...
Click to collapse
with all due respect, your patch is really hard to read. 40000+ lines is not small, and i find a lot of them only white space and identifier name changes. so, if possible could you make it better (using options in diff command maybe). if that's too hard just ignore my request. btw it's already work or still wip ?

No WiFi - wlan0 device can't be found. "dhdsdio_probe_attach: si_attach failed!".

No WiFi - wlan0 device can't be found. "dhdsdio_probe_attach: si_attach failed!".
Hi all,
I have a UK Sensation XE that I've had for 18 months. My WiFi has not worked for many months, maybe a year. I am pretty sure the problem first started on GB, because I remember doing an OTA update to stock ICS and hoping it would fix the problem and it didn't.
I just started trying to seriously fix the problem a few days ago. Since then, I have researched on here and Google for hours and hours, and tried every suggestion I could find. I have done lots of diagnostics.
What I've discovered is that the WiFi driver does load, but it reports in dmesg that it can't find the device. Therefore it does not create wlan0. Therefore wpa_supplicant cannot load.
Everything else on the phone works OK - 2G/3G, Bluetooth, USB, etc. Just WiFi is broken.
I am wondering if maybe my WiFi hardware is bust. But then again, I do see the same symptoms on other posts - like this one and this one. The first of those two posts reported it worked for him when he went back to Stock 2.2, suggesting there was some software cause.
dmesg shows the following (I've edited a bit in the middle so to not make this message too long - full dmesg output is in attached txt) :
Code:
gannet_setup
gannet initialized OK
[WLAN] ## wifi_probe
[WLAN][WRN] wifi_set_power = 1
pyramid_wifi_power: 1
EXT4-fs (mmcblk0p22): re-mounted. Opts: user_xattr,barrier=0,data=ordered
[WLAN] wifi_set_carddetect = 1
pyramid_wifi_set_carddetect: 1
mmc2: Slot status change detected (0 -> 1)
[WLAN] Dongle Host Driver, version 5.90.125.120
mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
mmc2: new high speed SDIO card at address 0001
[WLAN] alloc static buf at cf9c0000!
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
EXT4-fs (mmcblk0p22): re-mounted. Opts: user_xattr,barrier=0,data=ordered
mmc2: CMD53: Data timeout
mmc2: SDCC PWR is ON
mmc2: SDCC clks are ON, MCLK rate=48000000
mmc2: SDCC irq is enabled
===== SDCC-CORE: Register Dumps @base=0xd08a6000 =====
.. cut a bunch of Reg= values ..
mmc2: PIO mode
mmc2: xfer_size=4, data_xfered=0, xfer_remain=4
mmc2: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
[COLOR="Red"][WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
[WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
[WLAN][WRN] dhd_module_init: wifi_fail_retry is true
[WLAN] ## wifi_remove
[WLAN][WRN] wifi_set_power = 0
pyramid_wifi_power: 0
[WLAN] wifi_set_carddetect = 0
pyramid_wifi_set_carddetect: 0
mmc2: Slot status change detected (1 -> 0)
mmc2: card 0001 removed
[WLAN] ## wifi_remove leave
[WLAN] module init fail, try again!
[/COLOR]pyramid_wifi_power: 1
pyramid_wifi_set_carddetect: 1
mmc2: Slot status change detected (0 -> 1)
[WLAN] Dongle Host Driver, version 5.90.125.120
I have attached a longer section of dmesg output, starting at boot and going a bit past the last reference to WLAN. The above dmesg snippet starts on line 760 of the attached dmesg txt file. I attached the fuller log in case the dmesg output shows some other error, not tagged WLAN, that I don't recognise as being a problem.
The bcmdhd.ko module is loaded OK:
Code:
# lsmod
tun 14813 0 - Live 0xbf091000
bcmdhd 483764 0 - Live 0xbf005000
kineto_gan 4230 0 - Live 0xbf000000
In logcat, there are various errors from wpa_supplicant and other, which all basically just indicate that it can't find wlan0. Here's a small sample:
Code:
E/wpa_supplicant( 5847): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 5847): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 5847): wlan0: Failed to initialize driver interface
This is confirmed from shell:
Code:
# ip link ls wlan0
ip: can't find device 'wlan0'
The problem started on stock, I think stock GB. I do not know of any trigger for it happening.
Around that time I was playing around with rooting for the first time, and I tried Revolution S-OFF which I recall changed my HBOOT from 1.19 to 1.17 or something. But that's as far as I got at the time, I just ran Revolution S-Off, I remember it changed my HBOOT version on phone startup, and then I never tried anything more with flashing/rooting.
I do not know if the Wifi problem started at the same time I tried that hboot change. I cannot remember exactly when the WiFi broke, I don't know if anything triggered it.
All I am pretty sure of is that the problem started on stock GB, and then it was not resolved when I OTA updated to stock ICS (the stock ICS upgrade then changed my hboot to 1.29).
So I know the problem existed on Stock ICS. I think it happened also on stock GB. Then this is what I have also tried recently, in the last week, since I first started flashing/rooting/customising my phone:
Full phone wipe - used 4Ext to do complete wipe of all partitions, before installing new ROMs
Tried with a) no SD card at all, b) two different SD cards, c) did a complete format of one SD card
Tried without sim-card, also tried WiFix to set country code - doubt this has anything to do with it though as there's not even a wlan0 device.
Stock 3.33 FW, and then XDA-Dev 3.32 FW and XDA-Dev 3.33 FW
Stock HTC ICS release as per OTA update
Android Revolution HD 7.1 ROM 4.0.3 ICS
Elegancia ROM 3.70 ROM 4.0.4 ICS
Stock, Faux, Sebastian and Bricked kernels
Originally HTCDev locked, and now unlocked
Originally S-On, and now S-Off (Hboot 1.27)
Flashing boot.img separately with fastboot flash boot boot.img
Flashing ROM with 4Ext SmartFlash (even though I had S-OFF) - and then turning it off again and re-flashing.
Deleting wpa_supplicant.conf (not that this should work as issue is before supplicant. I've put the conf back now.)
So right now my phone is:
HTCDev unlock
S-Off, HBoot 1.27 (I used Juopunutbear-off with the 'wire trick')
4Ext Flash Recovery
Elegancia Rom 3.70 with Bricked kernel
I have searched so much and tried so many things, so I would be super grateful for any help at all. Maybe it's just a HW fault, but I have seen other people with the same symptoms of dmesg reporting it can't find the device, and some of those people did have the issues caused by SW problems, so I am hoping there is still some chance it's resolvable.
Thanks in advance!

No thoughts from anyone?
Would be great to get any thoughts or feedback - even if it's just to say that the HW is broken.

I've been looking all over for a solution for this problem myself. WiFi 'died' with an OTA a while back, none of the suggestions found all over work.
WiFix (basically changing the region) doesn't apply, wlan0 doesn't even start properly.
You mentioned BT is working, but I can see devices, not connect to them, so for me BT is partially working.
What I tried so far:
Different FWs/RUUs, even going back to Gingerbread!
Different RIL - FW/Radio combos
Different ROMs on Universal 3.33 FW as well as FWs from RUUs
I even put a Z710e RUU on it to see if that might work.
Device:
Sensation XE Z715e, currently on: HBoot 1.27.1100, FW 3.33.401.153 Radio11.76C.3504.00U_11.29A.3504.18_M
Stock Rom lsmod:
Code:
bcm4329 225933 0 - Live 0xbf03c000
kineto_gan 4190 0 - Live 0xbf000000
CM10.1 lsmod:
Code:
bcmdhd 444356 0 - Live 0x00000000
I see the same errors as OP in my logcat and dmesg.
I'm starting to suspect the chip is fritzed and needs to be replaced (I can't heat it as suggested here: http://forum.xda-developers.com/showpost.php?p=38165494&postcount=66 )
My other Z715e is unaffected.

porting kernel + drivers

Hi folks,
I'm hoping someone can help me get my head around loading drivers in android.
I'm very familiar with Linux, so I understand drivers compiled into the kernel vs loading modular drivers. I also understand module versions in that they should match the installed kernel.
I have a cyanogenmod ROM that was built for a device similar to mine except that the wifi/bt drivers do not work. I have a ROM where these DO work.
I have extracted the boot.img from each ROM and I'm trying to combine the kernel that works with the cyanogenmod boot.img to get a working device. But the drivers have me a bit stumped.
On the device that works, here is what I see during boot in dmesg:
Code:
<6>[ 2.273829] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.278272] Bluetooth: HCI H4 protocol initialized
<6>[ 2.283084] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.288045] Bluetooth: HCILL protocol initialized
<7>[ 2.292983] [wifi]: Select sdio wifi: bcm40183 !!
<7>[ 2.297878] [mmc_pm]: SDIO card gpio init is OK !!
<7>[ 2.302753] [mmc]: sunximmc_init
<7>[ 2.306208] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.311762] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.318190] [mmc]: mmc 0 power off !!
<7>[ 2.321978] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.329650] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.336069] [mmc]: mmc 1 power off !!
<7>[ 2.339801] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.347496] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.353876] [mmc]: mmc 3 power off !!
<7>[ 2.357601] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
This is below the line that says
Code:
<7>[ 2.081010] insmod_device_driver
So I'm assuming this is a module that is being loaded. I have however compared the init.sun4i.rc on both and made sure I'm loading the same drivers. I'm also loading the kernel from the working ROM.
This is what I see in the broken setup:
Code:
<6>[ 2.261673] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.266116] Bluetooth: HCI H4 protocol initialized
<6>[ 2.270928] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.275891] Bluetooth: HCILL protocol initialized
<7>[ 2.280811] [mmc_pm]: no sdio card used in configuration
<7>[ 2.286118] [mmc]: sunximmc_init
<7>[ 2.289602] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.295210] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.301688] [mmc]: mmc 0 power off !!
<7>[ 2.305451] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.313150] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.319533] [mmc]: mmc 1 power off !!
<7>[ 2.323293] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.330984] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.337351] [mmc]: mmc 3 power off !!
<7>[ 2.341106] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
So this seems to be complaining about no SD card being available - is this a correct assumption?
I also assume this is a card used for storage, and wifi/bt using the SDIO standard.
Would the wifi driver be being loaded from the SD card? If so, where? It may just be something else I need to add to the zip file for the new ROM.
When I compare dmesg between the two, I don't see anything obvious that loads differently, so it's got me stumped as to what's happening.
Can anyone shed some light on how the working ROM might be loading the bcm40183 driver?

in my android tablet I noticed how the /system folder is actually stored in nandd partition, and refered to by the main nand partition via a symlink. Since /system/vendor/modules (where my bcm40183 module is stored) is a symlink path to a location on a nand partition, I assume the OS reaches that location using a mmc device (maybe because it is flash memory after all). So your problem isn't about a missing SD card, but about a missing nand partition...or a broken link. Apparently, from one android version to the next, the number of partitions varies. On mine, there are 9 partitions!
Since you know about modules and versions, do you know how I could get that bcm40183 module working in linux? I can't find a kernel with that module on offer and I dont know how to add modules on already compiled kernels. I'd love to be able to insmod this bcm40183 version 3.0.8 in my sunxi-3.4 kernel...

[Resolved] [Q] Problem identifying Chinese Tablet

I have been a reader of the forum for a log time but until now need your help to identify a Chinese tablet that a friend of mine received as a gift.
The problem is that it is locked in the boot (it only displays Android on screen) and I need to reinstall it and the only information I have is what dmesg returned when connected via USB
:~$ dmesg | tail
[161396.250396] usb 2-1.1: Product: Android
[161396.250399] usb 2-1.1: Manufacturer: USB Developer
[161396.250401] usb 2-1.1: SerialNumber: 20080411d412e5d
[161401.258415] scsi10 : usb-storage 2-1.1:1.0
[161402.252904] scsi 10:0:0:0: Direct-Access USB 2.0 USB Flash Driver 0100 PQ: 0 ANSI: 2
[161402.253268] scsi 10:0:0:1: Direct-Access USB 2.0 USB Flash Driver 0100 PQ: 0 ANSI: 2
[161402.254146] sd 10:0:0:0: Attached scsi generic sg9 type 0
[161402.254372] sd 10:0:0:1: Attached scsi generic sg10 type 0
[161402.257914] sd 10:0:0:1: [sdh] Attached SCSI removable disk
[161402.260390] sd 10:0:0:0: [sdg] Attached SCSI removable disk
Click to expand...
Click to collapse
I already try to find the serial number and the manufacturer on google but can not find anything related. I took some pictures from the tablet and the box you can find them here -> imgur.com/a/I2k3Y
Thanks for any help
SOLUTION
I posted the same question in StackExchange -> android.stackexchange.com/questions/64892/help-identifying-tablet and it's working now