Database Info

[Partial Solution] Wi-Fi unable to start.

"Wi-Fi unable to start" error appeared couple weeks ago.
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
In a desperate moment I tried something.
Here are the steps:
I made some progress and it seams that is pure software problem.
Currently I'm with G1/black Cyanogen 3.6.8.1, Recovery 1.4 and 8GB SD/class 4.
What I did is reformatting the SD card in 2 partitions 1st FAT32 and 2nd ext2 ~ 460MB.
Wiped before flashing cyanogen build and also I made sure that there is nothing on the ext2 partition.
When flashing finished I waited the phone to fully set up itself on the first boot ~5-7 min.
Then I tried the WiFi - it didn't start
The important and desperate thing I did was to go to su console in /system/lib/modules and tried to load wlan.ko manually (insmod wlan.ko) - it failed the 1st time.
Then I tried 2 times more and it loaded itself successfully (of course wifi connection is not established in that moment, because loading the module is just one step of the process).
I unloaded successfully (rmmod wlan) the module and tried to start WiFi again - gues what - It worked!
That is just partial solution of the problem, but shows that it is just a software problem.
I guess some timeouts appear and WiFi starting procedure is not so patient to wait for the module to start up and it's not retrying to unload and load again the module.
Good luck
Hope it will work on yours G1.
Cheers

this has been up on a google code bug report page for a while now. I had the same result when trying to start the module in the terminal
cyanogen's new 3.9.1 scary experimental build shows that he used a new wifi driver in the changelog but that hasn't helped me with this issue at all. I thought it might be a software conflict so I used a clean sd card, flashed my update.zip, and still had the same problem

I have tried Cyanogen 3.9.1 with the same result - it doesn't work for me.
I can't explain why it started to work again in 3.6.8.1
Anyway, try to copy all your important files (not system/applications created like thumbnails folder) to your PC, put the SD card to card reader connected to a PC and then do a full reformat to FAT32.
Partition the newly formatted SD card to FAT32 and EXT2 partitions.
Reformat partitions again, copy update.zip to your SD card.
Start up your G1 holding home button and do wipe ( I wiped 2-3 times just to be sure )
Do ext2 system repair from the repair menu.
Do not convert it to ext3.
Apply the update.zip and continue to the next steps I wrote above.
Hope that's info is useful for you.

Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.

cssvb94 said:
but shows that it is just a software problem.
Click to expand...
Click to collapse
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.

lbcoder said:
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
Click to expand...
Click to collapse
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...

cyanogen said:
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
Click to expand...
Click to collapse
Is that request for me or airmaxx?
I really don't want to reflash now when it's working.
In the moment when something goes wrong I'll post dmesg.
I've noticed "D/wlan_loader( 228): ConfigMge start rc = -1" couple times in dmesg output when it wasn't working and "D/wlan_loader( 228): ConfigMge start rc = 0" when it works.

after a clean install of cyanogen 3.9.1, i tried to start with in the gui, through settings menu. after it reported "unable to start wifi" this is my dmesg output....
Code:
<6>[ 695.675048] TIWLAN: Driver loading
<4>[ 695.679168] wifi_probe
<4>[ 695.681762] trout_wifi_power: 1
<4>[ 695.888366] trout_wifi_reset: 0
<4>[ 695.943084] trout_wifi_set_carddetect: 1
<7>[ 695.947265] mmc0: card_present 1
<6>[ 695.950744] mmc0: Slot status change detected (0 -> 1)
<3>[ 698.464202] mmc0: Command timeout
<4>[ 698.474548] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 698.484191] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 698.497955] mmc0: new SDIO card at address 0001
<6>[ 698.508758] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 698.517639] tiwlan0 (): not using net_device_ops yet
<6>[ 698.530426] TIWLAN: Driver initialized (rc 0)
<3>[ 698.535705] mmc0: Data CRC error
<3>[ 698.539276] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.544128] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.549621] SDIO_SyncWrite: failed (-84)
<3>[ 698.554016] mmc0: Data CRC error
<3>[ 698.557586] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.562713] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.567718] SDIO_SyncWrite: failed (-84)
<3>[ 701.399383] mmc0: Data timeout
<3>[ 701.403289] SDIO_SyncRead: failed (-110)
<4>[ 701.407623] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 701.412933] TIWLAN: Driver loaded
<4>[ 701.820495] select 226 (app_process), adj 15, size 3301, to kill
<4>[ 701.826873] send sigkill to 226 (app_process), adj 15, size 3301
<3>[ 704.165802] mmc0: Data timeout
<3>[ 704.169311] SDIO_SyncRead: failed (-110)
<3>[ 704.174041] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 710.698730] RPC_TIME_TOD_SET_APPS_BASES:
<6>[ 710.698760] tick = 38620607
<6>[ 710.698760] stamp = 48907518449025024
<4>[ 735.120178] select 480 (app_process), adj 15, size 4338, to kill
<4>[ 735.126464] send sigkill to 480 (app_process), adj 15, size 4338
something i remembered earlier was that long ago, many roms and flashes prior (when I was still chasing after Hero and Rosie) i saw a wpa supplicant file had been installed on my fat32 partition, no system folder or anything just on the root of the card. i remember thinking at the time how odd this was and manually deleting the file prior to my next flash.
My problem may have started shortly thereafter but honestly don't remember, just grasping for straws here

cssvb94 said:
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
Click to expand...
Click to collapse
Really? That's not what you said before...
cssvb94 said:
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
Click to expand...
Click to collapse
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.

lbcoder said:
Really? That's not what you said before...
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
Click to expand...
Click to collapse
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
I'm trying to help and share what I've been through.
If you are offended of something I said then - sorry.
Don't be such arrogant, capital letters don't work on me. =)
----------------------------------------------------------------------
This is cut from my dmesg :
WiFi starting OK
--- cut ---
<6>[ 268.613555] TIWLAN: Driver loading
<4>[ 268.617797] wifi_probe
<4>[ 268.620758] trout_wifi_power: 1
<4>[ 268.830261] trout_wifi_reset: 0
<4>[ 268.884521] trout_wifi_set_carddetect: 1
<7>[ 268.888824] mmc0: card_present 1
<6>[ 268.892303] mmc0: Slot status change detected (0 -> 1)
<3>[ 271.400268] mmc0: Command timeout
<4>[ 271.410339] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 271.419982] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 271.436584] mmc0: new SDIO card at address 0001
<6>[ 271.446960] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 271.455352] tiwlan0 (): not using net_device_ops yet
<6>[ 271.464538] TIWLAN: Driver initialized (rc 0)
<4>[ 271.469909] TIWLAN: 1251 PG 1.2
<6>[ 271.473693] TIWLAN: Driver loaded
<3>[ 271.863403] mmc0: Data CRC error
<3>[ 271.866851] msmsdcc_data_err: opcode 0x00000035
<3>[ 271.871551] msmsdcc_data_err: blksz 512, blocks 1
<4>[ 271.877441] SDIO Write failure (-84)
<3>[ 271.883209] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
<6>[ 689.787445] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 689.795745] tiwlan0 (): not using net_device_ops yet
<6>[ 689.804901] TIWLAN: Driver initialized (rc 0)
<4>[ 689.810150] TIWLAN: 1251 PG 1.2
<6>[ 689.813690] TIWLAN: Driver loaded
<3>[ 690.153045] mmc0: Data CRC error
<3>[ 690.156463] msmsdcc_data_err: opcode 0x00000035
<3>[ 690.161163] msmsdcc_data_err: blksz 4, blocks 1
<4>[ 690.168182] SDIO Write failure (-84)
<3>[ 690.173889] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
Now new case: "Unable to stop Wi-Fi"
rmmod wlan throws back: "rmmod: delete_module 'wlan' failed (errno 11)"
lsmod returns: "wlan 566844 1 - Live 0xbf480000"

lbcoder, was there anything in my dmesg that confirmed it is indeed hardware, or anything useful at all in there?
after reading the reports on googlecode pages, i was leaning to hardware issue only because the problem is so rare and those people sent their g1's back in. I was really hoping this wasn't the case though.
I'd be happy with intermittent at this point, my wifi has not turned on in like 2 months my phone was purchased used (wifi worked fine at the time though) on craigslist so I can't return it to TMO

The CRC errors on mmc0 means that your sdcard is dying. It might seem unrelated but because how the way the G1 hardware works, this could be the problem. Yank your card and try it again.

No more WiFi
"Unable to stop" or "Unable to start" after reboot.
Tried with different SD card - no CRC errors and still no WiFi

for me the wifi turned on but it cant connect with a router... just write obtain ip address.. and after.. no connection
this is my log
<6>[ 175.583831] ept #2 out max:512 head:ffc0c100 bit:2
<6>[ 175.584289] ept #0 in max:64 head:ffc0c040 bit:16
<6>[ 175.585083] ept #1 in max:512 head:ffc0c0c0 bit:17
<6>[ 175.585510] ept #2 in max:512 head:ffc0c140 bit:18
<6>[ 175.586059] usb: notify offline
<6>[ 175.594207] usb: suspend
<6>[ 175.813262] usb: reset
<6>[ 175.815673] usb: portchange USB_SPEED_HIGH
<6>[ 175.967803] usb: reset
<6>[ 175.970092] usb: portchange USB_SPEED_HIGH
<6>[ 176.164825] usb_mass_storage usb_mass_storage: config #1
<6>[ 187.209259] request_suspend_state: wakeup (3->0) at 180968491210 (2009-07-
29 16:16:01.570098877 UTC)
<6>[ 188.333618] TIWLAN: Driver loading
<4>[ 188.334503] wifi_probe
<4>[ 188.334777] trout_wifi_power: 1
<4>[ 188.536346] trout_wifi_reset: 0
<4>[ 188.586914] trout_wifi_set_carddetect: 1
<7>[ 188.587432] mmc0: card_present 1
<6>[ 188.587738] mmc0: Slot status change detected (0 -> 1)
<3>[ 191.095031] mmc0: Command timeout
<4>[ 191.102386] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 191.103210] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 191.112518] mmc0: new SDIO card at address 0001
<6>[ 191.118377] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 191.123901] TIWLAN: Driver initialized (rc 0)
<4>[ 191.125244] TIWLAN: 1251 PG 1.2
<6>[ 191.125701] TIWLAN: Driver loaded
<6>[ 192.657897] snd_set_volume 256 0 5
<6>[ 192.747344] snd_set_volume 256 0 5
<3>[ 198.871185] init: sys_prop: permission denied uid:1000 name:ro.config.noc
heckin
<6>[ 244.551879] TIWLAN: Driver unloading
<4>[ 244.553070] sdio_reset_comm():
<7>[ 244.631011] TIWLAN: Releasing SDIO resources
<7>[ 244.632324] TIWLAN: SDIO resources released
<4>[ 244.634918] wifi_remove
<4>[ 244.635406] trout_wifi_set_carddetect: 0
<7>[ 244.636199] mmc0: card_present 0
<6>[ 244.636627] mmc0: Slot status change detected (1 -> 0)
<6>[ 244.639465] mmc0: card 0002 removed
<4>[ 244.643585] trout_wifi_reset: 1
<4>[ 244.699401] trout_wifi_power: 0
<6>[ 244.905883] TIWLAN: Driver unloaded
<6>[ 246.548492] TIWLAN: Driver loading
<4>[ 246.549377] wifi_probe
<4>[ 246.549652] trout_wifi_power: 1
<4>[ 246.754119] trout_wifi_reset: 0
<4>[ 246.805236] trout_wifi_set_carddetect: 1
<7>[ 246.805786] mmc0: card_present 1
<6>[ 246.806060] mmc0: Slot status change detected (0 -> 1)
<3>[ 249.310638] mmc0: Command timeout
<4>[ 249.318481] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 249.319335] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 249.326782] mmc0: new SDIO card at address 0001
<6>[ 249.332794] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 249.338226] TIWLAN: Driver initialized (rc 0)
<4>[ 249.339141] TIWLAN: 1251 PG 1.2
<6>[ 249.339599] TIWLAN: Driver loaded
<6>[ 994.061614] request_suspend_state: sleep (0->3) at 987820816650 (2009-07-2
9 16:29:28.422424317 UTC)
<4>[ 994.083801] deinit sharp panel
<4>[ 994.762908] save exit: isCheckpointed 1
<4>[ 994.765380] save exit: isCheckpointed 1

If you want help, get your details straight! If you contradict yourself all over the place, then nobody can possibly know what is going on and you won't get anywhere.
cssvb94 said:
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
Click to expand...
Click to collapse

You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.

Went back to stock 1.0 RC29 with original SPL, radio and bootloader and started from scratch.
Also formated SD card - only one partition FAT32.
Now I'm with ADP1.5 JF and WiFi is working most of the time.
So angry lbcoder what's your great verdict now? SOFTWARE or HARDWARE?

lbcoder said:
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Click to expand...
Click to collapse
which is the commands for push the radio and the the adp1-crc1 image via fastboot?
i can t find ADP1-CRC1 images can you give me a url please?

success!!!!!!
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah

rock187 said:
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
Click to expand...
Click to collapse
Great =)
Would you please post full step-by-step what you did.
10x in advance
It didn't work for me. I'm going to return my G1 back to the store I bought it, it's still under warranty.

External optical drive

Anyway to get CD or DVD to play on honeycomb with root at the moment? Driver limitations I believe stop the use on the stock ROM.

I would like to get this working as well... I bought an external CD/DVD burner assuming it would work (was only $26)... When I connect it, I get the "Preparing..." message to pop up, but it insantly goes away and nothing ever gets mounted. So, I did a "dmesg" from the command line afterwards, and you surely see that it knows what kind of device it is and it even looks like it creates some new device files for it, but I have not been able to find a way to mount it. Basically, I just want to be able to read CD's and DVD's with my Transformer in case i need to...
Here is the dmesg output;
<6>[ 2875.321152] usb 1-1.2: new high speed USB device using tegra-ehci and address 3
<6>[ 2875.359359] usb 1-1.2: New USB device found, idVendor=0930, idProduct=0c08
<6>[ 2875.359400] usb 1-1.2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
<6>[ 2875.359432] usb 1-1.2: Product: TOSHIBA SuperMulti Dr
<6>[ 2875.359458] usb 1-1.2: Manufacturer: TOSHIBA <6>[ 2875.359481] usb 1-1.2: SerialNumber: 000000000355
<4>[ 2875.359507] device: '1-1.2': device_add
<4>[ 2875.361676] device: '1-1.2:1.0': device_add
<6>[ 2875.364136] scsi0 : usb-storage 1-1.2:1.0
<4>[ 2875.364411] device: 'host0': device_add
<4>[ 2875.366176] device: 'host0': device_add
<4>[ 2875.367695] device: 'ep_81': device_add
<4>[ 2875.367859] device: 'ep_02': device_add
<4>[ 2875.368073] device: 'usbdev1.3': device_add
<4>[ 2875.370140] device: 'ep_00': device_add
<4>[ 2875.754655] Light sensor: al3000a_interrupt_handler
<4>[ 2875.755235] lux value is : 3
<5>[ 2876.373527] scsi 0:0:0:0: CD-ROM TOSHIBA SuperMultiPA3834 7.5A PQ: 0 ANSI: 0
<4>[ 2876.373551] device: 'target0:0:0': device_add
<4>[ 2876.373729] device: '0:0:0:0': device_add
<4>[ 2876.411891] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
<6>[ 2876.411927] cdrom: Uniform CD-ROM driver Revision: 3.20
<4>[ 2876.411972] device: '11:0': device_add
<4>[ 2876.412337] device: 'sr0': device_add
<7>[ 2876.412974] sr 0:0:0:0: Attached scsi CD-ROM sr0
<4>[ 2876.413015] device: '0:0:0:0': device_add
<4>[ 2876.413335] device: 'sg0': device_add
<5>[ 2876.413750] sr 0:0:0:0: Attached scsi generic sg0 type 5
<6>[ 2888.113412] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
<4>[ 2896.109293] bq20z45_get_psp val->intval =Full ret =e0 charging=0
<4>[ 2896.112566] bq20z45_get_psp voltage_now =8368
<4>[ 2896.113221] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.113971] bq20z45_get_psp temp=305
<4>[ 2896.119207] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.120111] bq20z45_get_psp voltage_now =8368
<4>[ 2896.121006] bq20z45_get_psp temp=305
<4>[ 2896.121890] bq20z45_get_psp val->intval =Full ret =e0 charging=0
Does anyone know if there is any possibility of getting this to work??
Thanks!
Sent from my Transformer TF101 using Tapatalk

jtrosky said:
I would like to get this working as well... I bought an external CD/DVD burner assuming it would work (was only $26)... When I connect it, I get the "Preparing..." message to pop up, but it insantly goes away and nothing ever gets mounted. So, I did a "dmesg" from the command line afterwards, and you surely see that it knows what kind of device it is and it even looks like it creates some new device files for it, but I have not been able to find a way to mount it. Basically, I just want to be able to read CD's and DVD's with my Transformer in case i need to...
Here is the dmesg output;
<6>[ 2875.321152] usb 1-1.2: new high speed USB device using tegra-ehci and address 3
<6>[ 2875.359359] usb 1-1.2: New USB device found, idVendor=0930, idProduct=0c08
<6>[ 2875.359400] usb 1-1.2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
<6>[ 2875.359432] usb 1-1.2: Product: TOSHIBA SuperMulti Dr
<6>[ 2875.359458] usb 1-1.2: Manufacturer: TOSHIBA <6>[ 2875.359481] usb 1-1.2: SerialNumber: 000000000355
<4>[ 2875.359507] device: '1-1.2': device_add
<4>[ 2875.361676] device: '1-1.2:1.0': device_add
<6>[ 2875.364136] scsi0 : usb-storage 1-1.2:1.0
<4>[ 2875.364411] device: 'host0': device_add
<4>[ 2875.366176] device: 'host0': device_add
<4>[ 2875.367695] device: 'ep_81': device_add
<4>[ 2875.367859] device: 'ep_02': device_add
<4>[ 2875.368073] device: 'usbdev1.3': device_add
<4>[ 2875.370140] device: 'ep_00': device_add
<4>[ 2875.754655] Light sensor: al3000a_interrupt_handler
<4>[ 2875.755235] lux value is : 3
<5>[ 2876.373527] scsi 0:0:0:0: CD-ROM TOSHIBA SuperMultiPA3834 7.5A PQ: 0 ANSI: 0
<4>[ 2876.373551] device: 'target0:0:0': device_add
<4>[ 2876.373729] device: '0:0:0:0': device_add
<4>[ 2876.411891] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
<6>[ 2876.411927] cdrom: Uniform CD-ROM driver Revision: 3.20
<4>[ 2876.411972] device: '11:0': device_add
<4>[ 2876.412337] device: 'sr0': device_add
<7>[ 2876.412974] sr 0:0:0:0: Attached scsi CD-ROM sr0
<4>[ 2876.413015] device: '0:0:0:0': device_add
<4>[ 2876.413335] device: 'sg0': device_add
<5>[ 2876.413750] sr 0:0:0:0: Attached scsi generic sg0 type 5
<6>[ 2888.113412] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
<4>[ 2896.109293] bq20z45_get_psp val->intval =Full ret =e0 charging=0
<4>[ 2896.112566] bq20z45_get_psp voltage_now =8368
<4>[ 2896.113221] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.113971] bq20z45_get_psp temp=305
<4>[ 2896.119207] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.120111] bq20z45_get_psp voltage_now =8368
<4>[ 2896.121006] bq20z45_get_psp temp=305
<4>[ 2896.121890] bq20z45_get_psp val->intval =Full ret =e0 charging=0
Does anyone know if there is any possibility of getting this to work??
Thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
It's because honeycomb still doesn't have a decent driver support for optical drivers
in fact it tries to mount the device but in reality it doesn't work
Only a few drives work

But it does see it as a CDROM (one line even says "uniform cdrom driver - version..." - how can it see a device that it has no drivers for? If it is missing from the kernel, is that something that a hacker could add or would that need to be done by ASUS first?
Thanks!

jtrosky said:
But it does see it as a CDROM (one line even says "uniform cdrom driver - version..." - how can it see a device that it has no drivers for? If it is missing from the kernel, is that something that a hacker could add or would that need to be done by ASUS first?
Click to expand...
Click to collapse
I edited the post
actually there is kernel support but it supports only few devices
I think that the patch should be done by google or at least specifically from asus
Obviously an hackr could adapt another linux driver... but i'm not sure how it would work

iMko92 said:
It's because honeycomb still doesn't have a decent driver support for optical drivers
in fact it tries to mount the device but in reality it doesn't work
Only a few drives work
Click to expand...
Click to collapse
Anyone happen to know of a drive that works currently? I was hoping that since it detected my device (and detected it as a CD-ROM), that it would work! I would be willing to return it and buy one that is known to work, since you say that there are some deivices that do work...
What abut the actual devices it creates (/dev/sr0 ad /dev/sg0, I think) - nothing we can do with those?
Thanks!
Sent from my Transformer TF101 using xda premium

jtrosky said:
Anyone happen to know of a drive that works currently? I was hoping that since it detected my device (and detected it as a CD-ROM), that it would work! I would be willing to return it and buy one that is known to work, since you say that there are some deivices that do work...
What abut the actual devices it creates (/dev/sr0 ad /dev/sg0, I think) - nothing we can do with those?
Click to expand...
Click to collapse
mount point is a start (/dev/sr0 ad /dev/sg0), but i dont't think this will help devs to add the support

jtrosky said:
Anyone happen to know of a drive that works currently? I was hoping that since it detected my device (and detected it as a CD-ROM), that it would work! I would be willing to return it and buy one that is known to work, since you say that there are some deivices that do work...
What abut the actual devices it creates (/dev/sr0 ad /dev/sg0, I think) - nothing we can do with those?
Thanks!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Have you tried to mount it manually?
# mkdir /mnt/cdrom
# mount /dev/sg0 /mnt/cdrom
of course you most likely will have to be root for this to work properly.

Yes, I've tried mounting with these commands ( I must specify the filesystm type with -t fstype, but I'm not sure what fstype should be):
# mount -oro -t cdrom /dev/block/sr0 /mnt/cdrom
# mount -oro -t cdrom /dev/sg0 /mnt/cdrom
Both report:
mount: no such device
I have no idea if "-t cdrom" is correct or not - just a guess.... Anyone have any other ideas?
Thanks for the help!!
Sent from my Transformer TF101 using xda premium

Ok, I'm getting closer! I can at least get the mount command to succeed if I specify -t tmpfs. Obviusly, I still couldn't read the CD, but at least I am communicating with the drive now. Now I just need to know what the correct "type" would be for a CD. I tried -t cdrom, -t cd-rom, -t iso9660 - none of those are known types though...
Anyone have any ideas of what the CD filesystem "Type" string woud be in android?? Or maybe there isn't one and that is the problem? So close....
Sent from my Transformer TF101 using xda premium

Ok, here is the problem - apparently, the kernel would need to support "iso9660" filesystem type in order to mount a CD/DVD. Unfortuantly, here is what my verision of Revolver supports (Revolver 2.5):
Looks like no CD-ROM support in the kernel... Oh well, was worth a shot! If you had an ext4 format DVD, I could read it, I guess....
/ #
/ # cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev cifs
nodev fuse
fuseblk
nodev fusectl
nodev mtd_inodefs
tntfs
Sent from my Transformer TF101 using xda premium

ISO support needs to be built into the kernel. When one of the developers builds the kernel, they can add it at that time.

Actually, I got fabio to chime in (Revolver ROM creator) - apparently, they need source code from ASUS before they can add this - but he said he would be glad to add it when the source is released....
Sent from my Transformer TF101 using xda premium

Anyone have any luck with this now that ICS is out?

bump
transformer prime, ziboo zipad: sata harddrive and sata optical enclosure, pc sees harddrive and dvd in slim DVDRW (pulled out my laptop) via usb, tab only sees harddrive (dvd spins but not detected)

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

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...

[Q] T-R42 ethernet problem

Hello,
I have problem with device T-R42.
I cannot enable ethernet - every time I try enable connection it logs to logcat:
dmesg reports:
<6>[ 3.329844] usb 2-1.4: new full speed USB device number 3 using usb20_host
<3>[ 3.409848] usb 2-1.4: device descriptor read/64, error -32
<3>[ 3.599841] usb 2-1.4: device descriptor read/64, error -32
whilest properly operational device has
<6>[ 3.390032] usb 2-1.4: new high speed USB device number 3 using usb20_host
<6>[ 3.502644] usb 2-1.4: New USB device found, idVendor=0b95, idProduct=772b
<6>[ 3.502680] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 3.502716] usb 2-1.4: Product: AX88772C
<6>[ 3.502741] usb 2-1.4: Manufacturer: ASIX Elec. Corp.
<6>[ 3.502766] usb 2-1.4: SerialNumber: 0002B1
<6>[ 4.153134] ASIX USB Ethernet Adapter:v4.1.1 17:50:33 Aug 13 2013
Is there anybody who can help me, please?
Many thanks
Jan