Database Develop

Unable to start Wi-Fi

Hallo.
I have problem with enabling Wi-Fi.
I try lots of thing to fix it:
update radio 3 times,spl,software
backup from nandroid from 2 months ago
try with 3 difrent SD cards...
but wifi still don't work.
How to diagnose this problem,it's hardware or software?
it's copy of my issue from CM issues:
Code:
What steps will reproduce the problem?
1.Attempt to enable Wi-Fi
What do you see?
[B]Unable to start Wi-Fi[/B]
What did you expect to see?
[B]Wi-fi was enabled[/B]
Please include the following info from FASTBOOT mode
MODEL? DREA1100 PVT 32B
HBOOT? 0.95.0000
RADIO? 2.22.19.261
Which version of CyanogenMod? 4.1.6
Did you wipe before flashing? yes
Have you tried running fix_permissions? yes
Have you tried rebooting? yes
Please attach a logcat of the issue.
E/WifiService( 2004): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 2443): Received wifi state changed from Unknown to
Enabling
D/SettingsWifiEnabler( 2443): Received wifi state changed from Enabling to
Unknown
Please provide any additional information below.
Wifi Cyanogenmod normally work in 4.1.6, I was connected to a wifi
network, because I moves ,lost my coverage of this network, when I wanted
to re-connect, system wrote to me "Unable
to enable wi-fi", I came home I did wipe, CM Uploader 4.1.9.2, wifi still
does not work, update to 4.1.10.1, I did wipe, fix_permission ... wifi
doesnt work...
<6>[ 212.900848] TIWLAN: Driver loading
<4>[ 212.907043] wifi_probe
<4>[ 212.909759] trout_wifi_power: 1
<4>[ 213.118225] trout_wifi_reset: 0
<4>[ 213.171936] trout_wifi_set_carddetect: 1
<7>[ 213.176422] mmc0: card_present 1
<6>[ 213.179931] mmc0: Slot status change detected (0 -> 1)
<3>[ 215.729705] mmc0: Command timeout
<3>[ 215.740417] mmc0: Command timeout
<3>[ 215.749969] mmc0: Command timeout
<3>[ 215.759490] mmc0: Command timeout
<3>[ 215.769287] mmc0: Command timeout
<3>[ 215.779052] mmc0: Command timeout
<3>[ 215.788818] mmc0: Command timeout
<3>[ 215.798583] mmc0: Command timeout
<3>[ 215.808624] mmc0: Command timeout
<3>[ 215.818969] mmc0: Command timeout
<3>[ 223.187896] tiwlan_module_init: Timed out waiting for device detect
<4>[ 223.195373] wifi_remove
<4>[ 223.198242] trout_wifi_set_carddetect: 0
<7>[ 223.202545] mmc0: card_present 0
<6>[ 223.208404] mmc0: Slot status change detected (1 -> 0)
<4>[ 223.214935] trout_wifi_reset: 1
<4>[ 223.272033] trout_wifi_power: 0
<4>[ 237.738372] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 243.077178] wds: 0021 @ 01
<6>[ 243.080200] qmi: wds: network stopped
<6>[ 243.184936] rmnet_stop()
<4>[ 260.505035] wds: 0020 @ 01
<3>[ 260.508117] qmi: wds: network start failed (000e)
<4>[ 260.513275] wds: 0022 @ ff
<6>[ 260.524932] qmi: wds: DISCONNECTED
<6>[ 274.452270] TIWLAN: Driver loading
<4>[ 274.458374] wifi_probe
<4>[ 274.461273] trout_wifi_power: 1
<4>[ 274.669494] trout_wifi_reset: 0
<4>[ 274.723083] trout_wifi_set_carddetect: 1
<7>[ 274.727508] mmc0: card_present 1
<6>[ 274.730987] mmc0: Slot status change detected (0 -> 1)
<3>[ 277.279205] mmc0: Command timeout
<3>[ 277.288909] mmc0: Command timeout
<3>[ 277.299011] mmc0: Command timeout
<3>[ 277.308959] mmc0: Command timeout
<3>[ 277.319641] mmc0: Command timeout
<3>[ 277.330718] mmc0: Command timeout
<3>[ 277.341583] mmc0: Command timeout
<3>[ 277.352416] mmc0: Command timeout
<3>[ 277.362243] mmc0: Command timeout
<3>[ 277.371734] mmc0: Command timeout
<3>[ 284.735900] tiwlan_module_init: Timed out waiting for device detect
<4>[ 284.743316] wifi_remove
<4>[ 284.749725] trout_wifi_set_carddetect: 0
<7>[ 284.754089] mmc0: card_present 0
<6>[ 284.758148] mmc0: Slot status change detected (1 -> 0)
<4>[ 284.763793] trout_wifi_reset: 1
<4>[ 284.821655] trout_wifi_power: 0

Definitely sounds like hardware. Where did you get your G1?

in Polish operator, brand new one "Era G1"
before the last weekend Wifi work absolutly normal.
ps.
It is a good thread for technical issues??

Flash a different ROM/build... do a wipe and reformat your sd card... post back with results plx

kingklick said:
Flash a different ROM/build... do a wipe and reformat your sd card... post back with results plx
Click to expand...
Click to collapse
Don't post it here if you want to continue on XDA

dan0zone said:
Don't post it here if you want to continue on XDA
Click to expand...
Click to collapse
PM me, sorry forgot

i flashed my old nandroid backup...with difrent rom...still Wifi not work...I also try with 3 diffrent Sd card with ( 1 Fat32 or 1 Fat32 + Ext2 or Fat32 + Ext2 + Swap) stiil the same with wifi...
When i try "busybox insmod wlan.ko" i reciving "device not found"
I scared...that can be hardware problem...but this will be strange becouse , wifi before that issue work perfecly normal,phone never fall...i taking good care with it.
ps.
if i do something wrong with posting please tell me,becouse like You see..i register long time ago,but to today reading was enought to me...but now i first time need help...

Kashue said:
Hallo.
Sorry for posting the same post...in 2 places...but on Q&A wasn't any construtive answers...
I have problem with enabling Wi-Fi.
I try lots of thing to fix it:
update radio 3 times,spl,software
backup from nandroid from 2 months ago
try with 3 difrent SD cards...
but wifi still don't work.
How to diagnose this problem,it's hardware or software?
it's copy of my issue from CM issues:
Code:
What steps will reproduce the problem?
1.Attempt to enable Wi-Fi
What do you see?
[B]Unable to start Wi-Fi[/B]
What did you expect to see?
[B]Wi-fi was enabled[/B]
Please include the following info from FASTBOOT mode
MODEL? DREA1100 PVT 32B
HBOOT? 0.95.0000
RADIO? 2.22.19.261
Which version of CyanogenMod? 4.1.6
Did you wipe before flashing? yes
Have you tried running fix_permissions? yes
Have you tried rebooting? yes
Please attach a logcat of the issue.
E/WifiService( 2004): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 2443): Received wifi state changed from Unknown to
Enabling
D/SettingsWifiEnabler( 2443): Received wifi state changed from Enabling to
Unknown
Please provide any additional information below.
Wifi Cyanogenmod normally work in 4.1.6, I was connected to a wifi
network, because I moves ,lost my coverage of this network, when I wanted
to re-connect, system wrote to me "Unable
to enable wi-fi", I came home I did wipe, CM Uploader 4.1.9.2, wifi still
does not work, update to 4.1.10.1, I did wipe, fix_permission ... wifi
doesnt work...
<6>[ 212.900848] TIWLAN: Driver loading
<4>[ 212.907043] wifi_probe
<4>[ 212.909759] trout_wifi_power: 1
<4>[ 213.118225] trout_wifi_reset: 0
<4>[ 213.171936] trout_wifi_set_carddetect: 1
<7>[ 213.176422] mmc0: card_present 1
<6>[ 213.179931] mmc0: Slot status change detected (0 -> 1)
<3>[ 215.729705] mmc0: Command timeout
<3>[ 215.740417] mmc0: Command timeout
<3>[ 215.749969] mmc0: Command timeout
<3>[ 215.759490] mmc0: Command timeout
<3>[ 215.769287] mmc0: Command timeout
<3>[ 215.779052] mmc0: Command timeout
<3>[ 215.788818] mmc0: Command timeout
<3>[ 215.798583] mmc0: Command timeout
<3>[ 215.808624] mmc0: Command timeout
<3>[ 215.818969] mmc0: Command timeout
<3>[ 223.187896] tiwlan_module_init: Timed out waiting for device detect
<4>[ 223.195373] wifi_remove
<4>[ 223.198242] trout_wifi_set_carddetect: 0
<7>[ 223.202545] mmc0: card_present 0
<6>[ 223.208404] mmc0: Slot status change detected (1 -> 0)
<4>[ 223.214935] trout_wifi_reset: 1
<4>[ 223.272033] trout_wifi_power: 0
<4>[ 237.738372] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 243.077178] wds: 0021 @ 01
<6>[ 243.080200] qmi: wds: network stopped
<6>[ 243.184936] rmnet_stop()
<4>[ 260.505035] wds: 0020 @ 01
<3>[ 260.508117] qmi: wds: network start failed (000e)
<4>[ 260.513275] wds: 0022 @ ff
<6>[ 260.524932] qmi: wds: DISCONNECTED
<6>[ 274.452270] TIWLAN: Driver loading
<4>[ 274.458374] wifi_probe
<4>[ 274.461273] trout_wifi_power: 1
<4>[ 274.669494] trout_wifi_reset: 0
<4>[ 274.723083] trout_wifi_set_carddetect: 1
<7>[ 274.727508] mmc0: card_present 1
<6>[ 274.730987] mmc0: Slot status change detected (0 -> 1)
<3>[ 277.279205] mmc0: Command timeout
<3>[ 277.288909] mmc0: Command timeout
<3>[ 277.299011] mmc0: Command timeout
<3>[ 277.308959] mmc0: Command timeout
<3>[ 277.319641] mmc0: Command timeout
<3>[ 277.330718] mmc0: Command timeout
<3>[ 277.341583] mmc0: Command timeout
<3>[ 277.352416] mmc0: Command timeout
<3>[ 277.362243] mmc0: Command timeout
<3>[ 277.371734] mmc0: Command timeout
<3>[ 284.735900] tiwlan_module_init: Timed out waiting for device detect
<4>[ 284.743316] wifi_remove
<4>[ 284.749725] trout_wifi_set_carddetect: 0
<7>[ 284.754089] mmc0: card_present 0
<6>[ 284.758148] mmc0: Slot status change detected (1 -> 0)
<4>[ 284.763793] trout_wifi_reset: 1
<4>[ 284.821655] trout_wifi_power: 0
Click to expand...
Click to collapse
corp769
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Senior Member
Join Date: Feb 2009
Posts: 196
Definitely sounds like hardware. Where did you get your G1?
Someone did respond to you in a very constructive manner ???? please read the rules ..Q&A is there so therads like these don't get started here !!!!

in normal Polish operator "Era" , the phone was brand new.
if it be necessary i have a guarantee
Q&A are watching 30 people
Development over 300 it's beter chance to get answer

I recently had the same issue an posted my problem here on XDA and got the same answer. "Its probably the hardware" After flashing every rom I could think of even rc29 I decided to take my chances with returning it for a warranty exchange through my provider (T-mobile). I just called them up and acted completely dumb about it. Told them my problem and followed whatever they said they wanted me to do. After 3 calls back to them, they sent me a replacement free of charge. Just don't mention anything about flashing or root etc. Each G1 in under a 1 year warranty from the time of purchase. You should be fine

I had this problem with my phone having wiped it and pushed wpa_supplicant.conf to my phone.
Turns out the permissions of the file were incorrect which stopped the wifi from working.
chmod 777 /data/misc/wifi/wpa_supplicant.conf
fixed it temporarily, but needed to be done again after a reboot. I then tried chown system.wifi /data/misc/wifi/wpa_supplicant.conf
but by the time I rebooted I also had upgraded to the newest
CyanogenMod (4.1.11.1)
So maybe that fixed it instead...

I don't have wpa_suplicant.conf in /data/misc/wifi but i moved it from /system/etc/wifi/
Change permission to but wifi still don't work...on mondey i go to network provider about warianty.,but it's strange...how wifi broken?is fault of software or normal electronic bad manufacter part...

Network error,answer posted 2 times...sry

Kashue said:
in normal Polish operator "Era" , the phone was brand new.
if it be necessary i have a guarantee
Q&A are watching 30 people
Development over 300 it's beter chance to get answer
Click to expand...
Click to collapse
So you knowingly BROKE THE RULES OF THE FORUM?
You know that will get you banned, then you will get ZERO answers, right?

both threads have been merged
next time stick to the rules

problem solved
To bring wifi to work service use somthing like this:
"Rigid-Flex Board ASSY,Daughterboard,Dream" 51H10069-00M
There was no other way...using software...i was hardware problem,but I don't know why that happend...phone newer fall,or nothing similiar.
Mod can close topic,there will not be any more update.

I 've got the same problem with my G1.....
"Error" or "Unable to start Wifi".
It's hardware issue...
I tried to put my G1 at the freeze for about 2-3 hours.
After this, wifi worked for about 20 minutes...
I think Wifi chip on daughter board is burned and it's working only if it's cold...
(...when I mean cold, I mean an icy G1 )
The only solution is daughter's board replacement......
(...or apply some thermal grease on the chip ???????)
What do you think.....???????

[Q] WiFi suddenly stopped working (error state)

Hi, I have been using a stable early version of CM5 on my T-Mobile G1 for about 5 months and one day (about 1 week ago) the WiFi failed while connecting to my home network, and since then, the WiFi has been in an error state; not being able to bee off or on. On the Power Widget, the WiFi indicator has a faded blue bar and even trying to enable it within the Android settings fails and says "error" as the state (as opposed to "Connected" or "Off").
I have tried rebooting, shutting down, removing the battery for a minute, and even wiping completely and re-flashing with CM 6.0 DS stable, yet the issue persists.
Oddly, when I do "netcgf" in the terminal emulator, I don't see a eth0 or wlan0 to tiwlan0 as a device. I only get this:
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
So I though my wlan hardware was not initialized properly, so I went through dmesg and the driver seems to have loaded and encountered an error and then uloaded as seen by the following:
<6>[ 364.669433] TIWLAN: Driver loading
<4>[ 364.669952] wifi_probe
<4>[ 364.672363] trout_wifi_power: 1
<4>[ 364.859588] trout_wifi_reset: 0
<4>[ 364.902343] trout_wifi_set_carddetect: 1
<7>[ 364.902770] mmc0: card_present 1
<6>[ 364.902984] mmc0: Slot status change detected (0 -> 1)
<4>[ 367.466888] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 367.473815] mmc0: new SDIO card at address 0001
<6>[ 367.481750] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 367.495544] TIWLAN: Driver initialized (rc 0)
<4>[ 367.497406] TIWLAN: 1251 PG 1.2
<6>[ 367.497924] TIWLAN: Driver loaded
<4>[ 367.916229] select 611 (android.protips), adj 9, size 3310, to kill
<4>[ 367.916900] send sigkill to 611 (android.protips), adj 9, size 3310
<3>[ 370.497741] mmc0: Data timeout
<3>[ 370.497863] SDIO_SyncRead: failed (-110)
<3>[ 370.498382] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 387.593353] TIWLAN: Driver unloading
<6>[ 389.263336] TIWLAN: 4241.654203: sdio_reset_comm():
<4>[ 389.286865] mmc0: Error resetting SDIO communications (-110)
<7>[ 389.554901] TIWLAN: Releasing SDIO resources
<7>[ 389.557556] TIWLAN: SDIO resources released
<4>[ 389.560882] wifi_remove
<4>[ 389.561370] trout_wifi_set_carddetect: 0
This repeats a few times before the phone just gives up trying to load the driver.
Another instance later on of afailed attempt to load the driver is shown here:
TIWLAN: Driver loading
<4>[ 482.536315] wifi_probe
<4>[ 482.536773] trout_wifi_power: 1
<4>[ 482.767944] trout_wifi_reset: 0
<4>[ 482.815704] trout_wifi_set_carddetect: 1
<7>[ 482.815948] mmc0: card_present 1
<6>[ 482.816345] mmc0: Slot status change detected (0 -> 1)
<4>[ 485.376586] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 485.380371] mmc0: new SDIO card at address 0001
<6>[ 485.387268] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 485.397033] TIWLAN: Driver initialized (rc 0)
<4>[ 485.398773] TIWLAN: 1251 PG 1.2
<6>[ 485.399230] TIWLAN: Driver loaded
<3>[ 487.699493] mmc0: Data timeout
<3>[ 487.699829] SDIO_SyncRead: failed (-110)
<3>[ 487.701110] TIWLAN: TIWLAN: Failed to start config manager
<4>[ 489.264953] select 704 (android.vending), adj 7, size 3865, to kill
<4>[ 489.265380] send sigkill to 704 (android.vending), adj 7, size 3865
<6>[ 505.471527] TIWLAN: Driver unloading
<6>[ 507.093597] TIWLAN: 64.402242: sdio_reset_comm():
<4>[ 507.117187] mmc0: Error resetting SDIO communications (-110)
<7>[ 507.379547] TIWLAN: Releasing SDIO resources
<7>[ 507.382232] TIWLAN: SDIO resources released
<4>[ 507.385589] wifi_remove
<4>[ 507.386077] trout_wifi_set_carddetect: 0
<7>[ 507.386901] mmc0: card_present 0
<6>[ 507.387359] mmc0: Slot status change detected (1 -> 0)
<6>[ 507.388397] mmc0: card 0001 removed
Has anyone experienced this and/or have a fix? It seems like I need to replace a file or two for the TIWLAN driver.
I have attached the entire dmesg from first boot of CM6 to now, which is about 5 minutes worth (not much).
Thanks a lot,
Mike

Sorry to bump this, but I would like some sort of guidance if I can fix this so I don't have to buy a new phone I love my G1. No keyboard compares.
I made some fixes, change some permissions and now I get one and only one error cosistenly in dmesg when trying to start the WiFi, and hence the TIWLAN driver.
<6>[31876.845947] TIWLAN: Driver loading
<4>[31876.846466] wifi_probe
<4>[31876.846832] trout_wifi_power: 1
<4>[31877.008209] trout_wifi_reset: 0
<4>[31877.049407] trout_wifi_set_carddetect: 1
<7>[31877.049682] mmc0: card_present 1
<6>[31877.049896] mmc0: Slot status change detected (0 -> 1)
<4>[31879.608001] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<6>[31879.611785] mmc0: new SDIO card at address 0001
<6>[31879.623321] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[31879.637817] TIWLAN: Driver initialized (rc 0)
<4>[31879.638366] TIWLAN: 1251 PG 1.2
<6>[31879.638610] TIWLAN: Driver loaded
<3>[31880.067932] config_partition: Error writing size
<3>[31880.068664] TIWLAN: TIWLAN: Failed to start config manager
<6>[31899.710571] TIWLAN: Driver unloading
<6>[31901.334014] TIWLAN: 3652.788872: sdio_reset_comm():
<4>[31901.357391] mmc0: Error resetting SDIO communications (-110)
<7>[31901.620971] TIWLAN: Releasing SDIO resources
<7>[31901.627258] TIWLAN: SDIO resources released
<4>[31901.630523] wifi_remove
<4>[31901.631561] trout_wifi_set_carddetect: 0
<7>[31901.632049] mmc0: card_present 0
<6>[31901.632507] mmc0: Slot status change detected (1 -> 0)
<6>[31901.633911] mmc0: card 0001 removed
<4>[31901.639007] trout_wifi_reset: 1
<4>[31901.682708] trout_wifi_power: 0
<6>[31901.848754] TIWLAN: Driver unloaded
The culprits are
<3>[31880.067932] config_partition: Error writing size
<3>[31880.068664] TIWLAN: TIWLAN: Failed to start config manager
I have no idea why the partition size is trying to be written (or perhaps the file size of the config file?) but that is preventing what would otherwise be a smooth loading of the WiFi driver.
If anyone has any suggestions or can provide any help, I would greatly appreciate it!
Thanks in advance,
Mike

Same here
gtabmx said:
Hi, I have been using a stable early version of CM5 on my T-Mobile G1 for about 5 months and one day (about 1 week ago) the WiFi failed while connecting to my home network, and since then, the WiFi has been in an error state; not being able to bee off or on. On the Power Widget, the WiFi indicator has a faded blue bar and even trying to enable it within the Android settings fails and says "error" as the state (as opposed to "Connected" or "Off").
I have tried rebooting, shutting down, removing the battery for a minute, and even wiping completely and re-flashing with CM 6.0 DS stable, yet the issue persists.
Oddly, when I do "netcgf" in the terminal emulator, I don't see a eth0 or wlan0 to tiwlan0 as a device. I only get this:
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
So I though my wlan hardware was not initialized properly, so I went through dmesg and the driver seems to have loaded and encountered an error and then uloaded as seen by the following:
<6>[ 364.669433] TIWLAN: Driver loading
<4>[ 364.669952] wifi_probe
<4>[ 364.672363] trout_wifi_power: 1
<4>[ 364.859588] trout_wifi_reset: 0
<4>[ 364.902343] trout_wifi_set_carddetect: 1
<7>[ 364.902770] mmc0: card_present 1
<6>[ 364.902984] mmc0: Slot status change detected (0 -> 1)
<4>[ 367.466888] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 367.473815] mmc0: new SDIO card at address 0001
<6>[ 367.481750] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 367.495544] TIWLAN: Driver initialized (rc 0)
<4>[ 367.497406] TIWLAN: 1251 PG 1.2
<6>[ 367.497924] TIWLAN: Driver loaded
<4>[ 367.916229] select 611 (android.protips), adj 9, size 3310, to kill
<4>[ 367.916900] send sigkill to 611 (android.protips), adj 9, size 3310
<3>[ 370.497741] mmc0: Data timeout
<3>[ 370.497863] SDIO_SyncRead: failed (-110)
<3>[ 370.498382] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 387.593353] TIWLAN: Driver unloading
<6>[ 389.263336] TIWLAN: 4241.654203: sdio_reset_comm():
<4>[ 389.286865] mmc0: Error resetting SDIO communications (-110)
<7>[ 389.554901] TIWLAN: Releasing SDIO resources
<7>[ 389.557556] TIWLAN: SDIO resources released
<4>[ 389.560882] wifi_remove
<4>[ 389.561370] trout_wifi_set_carddetect: 0
This repeats a few times before the phone just gives up trying to load the driver.
Another instance later on of afailed attempt to load the driver is shown here:
TIWLAN: Driver loading
<4>[ 482.536315] wifi_probe
<4>[ 482.536773] trout_wifi_power: 1
<4>[ 482.767944] trout_wifi_reset: 0
<4>[ 482.815704] trout_wifi_set_carddetect: 1
<7>[ 482.815948] mmc0: card_present 1
<6>[ 482.816345] mmc0: Slot status change detected (0 -> 1)
<4>[ 485.376586] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 485.380371] mmc0: new SDIO card at address 0001
<6>[ 485.387268] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 485.397033] TIWLAN: Driver initialized (rc 0)
<4>[ 485.398773] TIWLAN: 1251 PG 1.2
<6>[ 485.399230] TIWLAN: Driver loaded
<3>[ 487.699493] mmc0: Data timeout
<3>[ 487.699829] SDIO_SyncRead: failed (-110)
<3>[ 487.701110] TIWLAN: TIWLAN: Failed to start config manager
<4>[ 489.264953] select 704 (android.vending), adj 7, size 3865, to kill
<4>[ 489.265380] send sigkill to 704 (android.vending), adj 7, size 3865
<6>[ 505.471527] TIWLAN: Driver unloading
<6>[ 507.093597] TIWLAN: 64.402242: sdio_reset_comm():
<4>[ 507.117187] mmc0: Error resetting SDIO communications (-110)
<7>[ 507.379547] TIWLAN: Releasing SDIO resources
<7>[ 507.382232] TIWLAN: SDIO resources released
<4>[ 507.385589] wifi_remove
<4>[ 507.386077] trout_wifi_set_carddetect: 0
<7>[ 507.386901] mmc0: card_present 0
<6>[ 507.387359] mmc0: Slot status change detected (1 -> 0)
<6>[ 507.388397] mmc0: card 0001 removed
Has anyone experienced this and/or have a fix? It seems like I need to replace a file or two for the TIWLAN driver.
I have attached the entire dmesg from first boot of CM6 to now, which is about 5 minutes worth (not much).
Thanks a lot,
Mike
Click to expand...
Click to collapse
I'm having the same problem. I've done a factory reset and went to wifi settings. As soon as I tried to turn on the wifi again the word "error" came back.
Someone please help

Same here. mine started this sh*t 2 days ago. been runnin cm6.1.1 for bout 3 weeks now.

Hi,
I face the same issue with my developer phone 2..

Okay.. it resumed after factory data reset!
A more detailed survey of this error can be found on the android-tether developer website.. I cannot post links as i am a new member here... But it can be found as the first google link for the search string "google code issue 1124"

Nexus One Reboot Freezes what could be the problem?

So i have two nexus's one is perfect. However I also have my old one (before htc sent me the new one) it has a major problem were the phone will usually not boot and if it does after a few minutes of use will reboot and vibrate a bunch of times.
So what do you guys think could be the problem??? I'm thinking the logic board?
I'm asking because i am thinking about fixing it myself

Do an ADB logcat.
The phone doesn't have to completely boot to start it. This is the best way to determine at what point the phone stops. I use these when I get a boot loop.

K I will try that and post back
Sent from my Nexus One using XDA App

Search the forum using "vibrations" keyword.

Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around. It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Code:
E/CameraInput < 59>: Recording is not ready <iPeer 0x1fc94 iState 2 iWriteState
1 iClockState 0>, frame dropped
I/AudioHardwareQSD< 59>: AudioHardware pcm playback is going to standby.
And that's it thats last thing before it crashed and turned off... Any ideas what means in english? something about audio but i don't know if that is realated
EDIT: And yes it is the seven vibrations problem

What radio are you using?

Jack_R1 said:
What radio are you using?
Click to expand...
Click to collapse
5.12 right now but i have tried all of them. Same problem. Almost all the kernels and roms too. from stock to cyanogen to miui.
Non make a difference. The phone clearly has a hardware problem i just want to identify which piece of hardware

"adb bugreport" will help much more.
Also, "cat /proc/kmsg" and "cat /proc/last_kmsg", too.

Clear cache
Sent from my Nexus One using XDA App

I have cleared cache a hundred times...
I am going to try the other adb commands

Tech_Boy said:
Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around.
It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Click to expand...
Click to collapse
Right click anywhere in the window itself and select: edit, then select all
After everything is highlighted again right click on anywhere on the window and select: edit, then copy
You can then paste this into a notepad to edit it, or whatever.
Also as mentioned, try adb bugreport as well that could help.

Ok this is what i got. I don't understand much of it, so i don't know what i am looking for.
I ran the first two the third gave a file no found error... Also I notice cmd didn't copy the whole thing, like when it reaches a certain amount of lines it cuts off the top stuff
Code:
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #2 Window{44ac0690 SurfaceView paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,38)(480x762) gr=#33 ty=1000 fl=#24218 fmt=-3}
mAttachedWindow=Window{44b7ce48 com.android.launcher/com.android.launcher2.L
auncher paused=false} mLayoutAttached=true
mBaseLayer=21000 mSubLayer=1 mAnimLayer=21010+0=21010 mLastLayer=21010
mToken=WindowToken{44ac0630 [email protected]}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
mPolicyVisibility=true mPolicyVisibilityAfterAnim=true mAttachedHidden=true
Requested w=480 h=762 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,38][480,800] last=[0,38][480,800]
mFrame=[0,38][480,800] last=[0,38][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #1 Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) sim=#20 ty=1 fl=#110100 fmt=-2 wanim
=0x1030001}
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21005+0=21005 mLastLayer=21005
mToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.laun
cher/com.android.launcher2.Launcher}}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=480 h=800 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
Window #0 Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=fa
lse}:
mSession=Session{44a8e370 uid 10029} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) gr=#33 ty=2013 fl=#318 fmt=-1 wanim=
0x1030075}
mIsImWindow=false mIsWallpaper=true mIsFloatingLayer=true mWallpaperVisible=
false
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21000+0=21000 mLastLayer=21000
mSurface=Surface(name=com.android.wallpaper.nexus.NexusWallpaper, identity=4
)
Surface: shown=false layer=21000 alpha=1.0 rect=(0,0) 480 x 800
mToken=WindowToken{449909f0 [email protected]}
mRootToken=WindowToken{449909f0 [email protected]}
mViewVisibility=0x0 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=-1 h=-1 mLayoutSeq=318
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,0][480,800] mVisibleFrame=[0,0][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mAnimating=false mLocalAnimating=false mAnimationIsEntrance=true mAnimation=
null
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
All active sessions:
Session Session{44bcab88 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4a1cd90
Session Session{44b399c8 uid 10028}:
mNumWindow=2 mClientDead=false [email protected]
49a1ed8
Session Session{44a8e370 uid 10029}:
mNumWindow=1 mClientDead=false [email protected]
4960760
Session Session{44ac1528 uid 10018}:
mNumWindow=0 mClientDead=false [email protected]
49c5ee0
Session Session{44af3498 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4af4eb8
All tokens:
Token null:
token=null
windows=[Window{44af4960 StatusBar paused=false}, Window{44b24fa0 TrackingVi
ew paused=false}, Window{44af8488 StatusBarExpanded paused=false}]
windowType=-1 hidden=false hasVisible=true
Token [email protected]:
[email protected]
windows=[]
windowType=2011 hidden=false hasVisible=false
Token HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Launch
er}:
token=HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Laun
cher}
windows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.La
uncher paused=false}, Window{44ac0690 SurfaceView paused=false}]
groupId=5 appFullscreen=true requestedOrientation=5
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=3 numDrawnWindows=3 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Token HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}:
token=HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}
windows=[Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}]
windowType=2 hidden=false hasVisible=true
app=true
allAppWindows=[Window{44b4d8a0 com.android.settings/com.android.settings.Dev
elopmentSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=false clientHidden=false willBeHidden=false reportedVisible=
false
numInterestingWindows=2 numDrawnWindows=2 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44ac0690 SurfaceView paused=false}]
windowType=-1 hidden=false hasVisible=true
Token HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}:
token=HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}
windows=[]
windowType=2 hidden=true hasVisible=true
app=true
groupId=2 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
Token HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}:
token=HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}
windows=[Window{44b446f8 com.android.settings/com.android.settings.Applicati
onSettings paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b446f8 com.android.settings/com.android.settings.App
licationSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token HistoryRecord{44beca80 com.android.settings/.Settings}:
token=HistoryRecord{44beca80 com.android.settings/.Settings}
windows=[Window{44b2c1d8 com.android.settings/com.android.settings.Settings
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b2c1d8 com.android.settings/com.android.settings.Set
tings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
startingWindow=null startingView=null startingDisplayed=true startingMovedfa
lse
Window token list:
#0: WindowToken{44af47b0 token=null}
#1: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setupwiza
rd/.SetupWizardActivity}}
#2: WindowToken{449909f0 [email protected]}
#3: WindowToken{44ae24d0 [email protected]}
#4: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launcher/
com.android.launcher2.Launcher}}
#5: WindowToken{44ac0630 [email protected]}
#6: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.settings/
.Settings}}
#7: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.settings/
.ApplicationSettings}}
#8: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.settings/
.DevelopmentSettings}}
Wallpaper tokens:
Wallpaper #0 WindowToken{449909f0 [email protected]}:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Application tokens in Z order:
App #4: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.setti
ngs/.DevelopmentSettings}}
App #3: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.setti
ngs/.ApplicationSettings}}
App #2: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.setti
ngs/.Settings}}
App #1: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launc
her/com.android.launcher2.Launcher}}
App #0: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setup
wizard/.SetupWizardActivity}}
mCurrentFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Develo
pmentSettings paused=false}
mLastFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}
mFocusedApp=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.s
ettings/.DevelopmentSettings}}
mInputMethodTarget=null
mInputMethodWindow=null
mWallpaperTarget=null
mCurConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 or
ien=1 layout=34 uiMode=17 seq=4}
mInTouchMode=true mLayoutSeq=345
mSystemBooted=true mDisplayEnabled=true
mLayoutNeeded=false mBlurShown=false
mDimShown=true current=0.0 target=0.0 delta=-0.004 lastAnimTime=0
mInputMethodAnimLayerAdjustment=0 mWallpaperAnimLayerAdjustment=0
mLastWallpaperX=0.5 mLastWallpaperY=0.0
mDisplayFrozen=false mWindowsFreezingScreen=false mAppsFreezingScreen=0 mWaiti
ngForConfig=false
mRotation=0, mForcedAppOrientation=-1, mRequestedRotation=0
mAnimationPending=false mWindowAnimationScale=1.0 mTransitionWindowAnimationSc
ale=1.0
mNextAppTransition=0xffffffff, mAppTransitionReady=false, mAppTransitionRunnin
g=false, mAppTransitionTimeout=false
mStartingIconInTransition=false, mSkipAppTransitionAnimation=false
mLastEnterAnimToken=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.a
ndroid.settings/.DevelopmentSettings}}, mLastEnterAnimParams=WM.LayoutParams{(0,
0)(fillxfill) sim=#110 ty=1 fl=#10100 fmt=-1 wanim=0x1030001}
DisplayWidth=480 DisplayHeight=800
KeyWaiter state:
mLastWin=null mLastBinder=null
mFinished=true mGotFirstWindow=true mEventDispatching=true mTimeToSwitch=0
[dumpsys: 3.3s elapsed]
C:\android-sdk-windows\tools>
Code:
<6>[ 5.608520] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.608764] mmc0: Slot eject status = 1
<6>[ 5.608886] mmc0: Power save feature enable = 1
<6>[ 5.609039] mmc0: DM non-cached buffer at ffa04000, dma_addr 0x279bd000
<6>[ 5.609283] mmc0: DM cmd busaddr 0x279bd000, cmdptr busaddr 0x279bd300
<6>[ 5.610229] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
<6>[ 5.610443] mmc1: 4 bit data mode enabled
<6>[ 5.610595] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.610839] mmc1: Slot eject status = 0
<6>[ 5.610961] mmc1: Power save feature enable = 1
<6>[ 5.611206] mmc1: DM non-cached buffer at ffa05000, dma_addr 0x279be000
<6>[ 5.611328] mmc1: DM cmd busaddr 0x279be000, cmdptr busaddr 0x279be300
<6>[ 5.612396] logger: created 64K log 'log_main'
<6>[ 5.612640] logger: created 256K log 'log_events'
<6>[ 5.612945] logger: created 64K log 'log_radio'
<6>[ 5.613128] logger: created 64K log 'log_system'
<4>[ 5.613586] GACT probability NOT on
<4>[ 5.613800] Mirror/redirect action on
<4>[ 5.613952] u32 classifier
<4>[ 5.614074] Actions configured
<4>[ 5.614318] Netfilter messages via NETLINK v0.30.
<4>[ 5.614501] nf_conntrack version 0.5.0 (6171 buckets, 24684 max)
<4>[ 5.614929] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plea
se use
<4>[ 5.615081] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack modu
le option or
<4>[ 5.615295] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<4>[ 5.615570] ctnetlink v0.93: registering with nfnetlink.
<6>[ 5.616058] xt_time: kernel timezone is -0000
<6>[ 5.616394] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 5.616729] arp_tables: (C) 2002 David S. Miller
<6>[ 5.616943] TCP cubic registered
<6>[ 5.617279] NET: Registered protocol family 10
<6>[ 5.617980] lo: Disabled Privacy Extensions
<6>[ 5.618896] Mobile IPv6
<6>[ 5.619049] IPv6 over IPv4 tunneling driver
<6>[ 5.619720] sit0: Disabled Privacy Extensions
<6>[ 5.620330] ip6tnl0: Disabled Privacy Extensions
<6>[ 5.620666] NET: Registered protocol family 17
<6>[ 5.620819] NET: Registered protocol family 15
<6>[ 5.620971] Bluetooth: L2CAP ver 2.14
<6>[ 5.621215] Bluetooth: L2CAP socket layer initialized
<6>[ 5.621337] Bluetooth: SCO (Voice Link) ver 0.6
<6>[ 5.621582] Bluetooth: SCO socket layer initialized
<6>[ 5.621917] Bluetooth: RFCOMM TTY layer initialized
<6>[ 5.622070] Bluetooth: RFCOMM socket layer initialized
<6>[ 5.622314] Bluetooth: RFCOMM ver 1.11
<6>[ 5.622436] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 5.622680] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 5.622894] ThumbEE CPU extension supported.
<6>[ 5.623596] clock_late_init() disabled 18 unused clocks
<4>[ 5.623809] mahimahi_wifi_init: start
<6>[ 5.624206] VFP support v0.3: implementor 51 architecture 0 part 0f varian
t 0 rev 1
<4>[ 5.652435] regulator_init_complete: incomplete constraints, leaving ldo2
on
<4>[ 5.653320] regulator_init_complete: incomplete constraints, leaving ldo1
on
<4>[ 5.654083] regulator_init_complete: incomplete constraints, leaving dcdc3
on
<4>[ 5.654968] regulator_init_complete: incomplete constraints, leaving dcdc2
on
<4>[ 5.655853] regulator_init_complete: incomplete constraints, leaving dcdc1
on
<6>[ 5.657379] rs30000048:00010000 rs30000048:00010000: setting system clock
to 2010-11-23 19:51:55 UTC (1290541915)
<6>[ 5.657714] Freeing init memory: 120K
<4>[ 5.657867] Warning: unable to open an initial console.
<6>[ 5.745422] keychord: using input dev h2w headset for fevent
<6>[ 5.745574] keychord: using input dev mahimahi-keypad for fevent
<6>[ 5.745971] keychord: using input dev mahimahi-nav for fevent
<6>[ 5.748168] yaffs: dev is 32505859 name is "mtdblock3"
<6>[ 5.748443] yaffs: passed flags ""
<4>[ 5.748565] yaffs: Attempting MTD mount on 31.3, "mtdblock3"
<4>[ 5.915313] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 5.915496] mmc1: new high speed SDHC card at address aaaa
<6>[ 5.916229] mmcblk0: mmc1:aaaa SU04G 3.69 GiB
<6>[ 5.916625] mmcblk0: p1
<4>[ 5.956512] yaffs: restored from checkpoint
<4>[ 5.956970] yaffs_read_super: isCheckpointed 1
<6>[ 5.996093] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 5.996337] yaffs: passed flags ""
<4>[ 5.996459] yaffs: Attempting MTD mount on 31.5, "mtdblock5"
<6>[ 6.100860] batt: 83%, 4030 mV, -237 mA (0 avg), 27.0 C, 1128 mAh
<6>[ 6.108581] batt: charging OFF
<4>[ 6.298553] block 164 is bad
<4>[ 6.373718] block 410 is bad
<4>[ 6.429870] block 594 is bad
<4>[ 6.436859] block 617 is bad
<4>[ 6.514953] block 873 is bad
<4>[ 6.581939] block 1092 is bad
<4>[ 6.585266] block 1103 is bad
<4>[ 6.612121] block 1191 is bad
<4>[ 6.626129] block 1237 is bad
<4>[ 7.622741] yaffs_read_super: isCheckpointed 0
<6>[ 7.628631] yaffs: dev is 32505860 name is "mtdblock4"
<6>[ 7.628753] yaffs: passed flags ""
<4>[ 7.628997] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<4>[ 7.773559] block 93 is bad
<4>[ 7.794616] block 162 is bad
<4>[ 7.836578] block 299 is bad
<4>[ 7.836853] block 300 is bad
<4>[ 7.903015] block 519 is bad
<4>[ 7.987426] yaffs_read_super: isCheckpointed 0
<3>[ 8.017700] init: service 'console' requires console
<3>[ 8.062011] init: cannot execve('/system/etc/install-recovery.sh'): Permis
sion denied
<3>[ 8.110382] init: cannot find '/system/bin/dspcrashd', disabling 'dspcrash
d'
<6>[ 8.125823] acpuclk_set_vdd_level got regulator
<6>[ 8.545745] warning: `rild' uses 32-bit capabilities (legacy support in us
e)
<6>[ 8.679840] SMD: ch 0 1 -> 2
<6>[ 8.681640] qmi: smd closed
<6>[ 8.682006] SMD: ch 50 1 -> 2
<6>[ 8.682312] qmi: smd opened
<6>[ 8.683135] qmi: smd closed
<6>[ 8.683471] SMD: ch 51 1 -> 2
<6>[ 8.683807] qmi: smd opened
<6>[ 8.684265] qmi: ctl: wds use client_id 0x01
<6>[ 8.684936] qmi: ctl: wds use client_id 0x01
<6>[ 8.685455] qmi: smd closed
<6>[ 8.685913] SMD: ch 52 1 -> 2
<6>[ 8.686523] qmi: smd opened
<6>[ 8.687438] qmi: ctl: wds use client_id 0x01
<6>[ 9.907592] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 12.805664] a1026_bootup_init: firmware loaded successfully
<6>[ 12.966003] a1026_bootup_init: initialized!
<6>[ 12.968688] htc-acoustic: open
<3>[ 12.969726] smd_alloc_channel() cid 41 does not exist
<3>[ 12.969848] smd_alloc_channel() cid 47 does not exist
<6>[ 12.973327] htc-acoustic: mmap
<6>[ 12.973541] htc-acoustic: ioctl
<6>[ 12.973632] htc-acoustic: ioctl: ACOUSTIC_UPDATE_ADIE called 59.
<6>[ 12.976440] htc-acoustic: ioctl: ONCRPC_UPDATE_ADIE_PROC success.
<6>[ 12.977264] htc-acoustic: release
<6>[ 12.997161] audio: init: codecs
<6>[ 12.997375] SMD: ch 43 1 -> 2
<6>[ 13.109802] dal_attach: status = 0, name = 'DAL_AQ_AUD'
<6>[ 13.109985] audio: init: INIT
<6>[ 13.110290] audio: init: OPEN control
<6>[ 13.495880] audio: init: attach ACDB
<6>[ 13.496215] SMD: ch 48 1 -> 2
<6>[ 13.606018] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 13.606140] audio: init: attach ADIE
<6>[ 13.606628] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 17.041503] lcdc_unblank: ()
<6>[ 17.041748] samsung_oled_panel_unblank: +()
<6>[ 17.256103] msm_kgsl: initilized dev=1 mmu=on
<6>[ 17.256561] misc kgsl: firmware: requesting yamato_pm4.fw
<6>[ 17.263732] misc kgsl: firmware: requesting yamato_pfp.fw
<3>[ 17.265991] init: untracked pid 87 exited
<3>[ 17.271881] init: untracked pid 88 exited
<6>[ 17.325988] samsung_oled_panel_unblank: -()
<6>[ 25.646606] capella_cm3602_open
<6>[ 25.647003] capella_cm3602_ioctl cmd 2
<6>[ 25.647918] capella_cm3602_disable
<6>[ 25.648040] capella_cm3602_disable: already disabled
<6>[ 25.648162] capella_cm3602_ioctl cmd 1
<6>[ 25.655303] request_suspend_state: wakeup (3->0) at 21809722976 (2010-11-2
3 19:52:15.497955355 UTC)
<6>[ 25.672088] capella_cm3602_ioctl cmd 1
<6>[ 32.422729] request_suspend_state: sleep (0->3) at 28577117998 (2010-11-23
19:52:22.265350377 UTC)
<6>[ 32.422851] capella_cm3602_ioctl cmd 1
<7>[ 32.423767] flashlight_control: mode 0 -> 0
<6>[ 32.423767] flashlight_control: off
<6>[ 32.426666] capella_cm3602_ioctl cmd 1
<6>[ 32.439849] lcdc_blank: ()
<6>[ 32.439971] samsung_oled_panel_blank: +()
<6>[ 32.645751] samsung_oled_panel_blank: -()
<6>[ 32.647949] mahimahi_ts_power: power 0
<6>[ 32.655822] lcdc_suspend: suspending
<4>[ 32.701049] save exit: isCheckpointed 1
<4>[ 32.706878] save exit: isCheckpointed 1
<4>[ 32.739654] save exit: isCheckpointed 1
<6>[ 32.763153] active wake lock kgsl
<6>[ 32.763275] active wake lock PowerManagerService
<6>[ 32.763366] wake lock mmc_delayed_work, expired
<6>[ 32.763549] wake lock qmi0, expired
<6>[ 32.763671] wake lock qmi1, expired
<6>[ 32.763763] wake lock qmi2, expired
<6>[ 32.763977] wake lock SMD_DS, expired
<6>[ 33.365203] request_suspend_state: wakeup (3->0) at 29519592363 (2010-11-2
3 19:52:23.207824742 UTC)
<6>[ 33.367401] lcdc_resume: resuming
<6>[ 33.367919] mahimahi_ts_power: power 1
<6>[ 33.369537] capella_cm3602_ioctl cmd 2
<6>[ 33.369750] capella_cm3602_disable
<6>[ 33.369842] capella_cm3602_disable: already disabled
<6>[ 33.369964] capella_cm3602_ioctl cmd 1
<6>[ 33.372253] capella_cm3602_ioctl cmd 1
<6>[ 33.415130] lcdc_unblank: ()
<6>[ 33.415252] samsung_oled_panel_unblank: +()
<6>[ 33.697570] samsung_oled_panel_unblank: -()
<6>[ 33.960021] cable_status_update: status=1
<6>[ 33.985809] msm72k_udc: OFFLINE -> ONLINE
<6>[ 33.986114] hsusb: reset controller
<6>[ 34.045654] msm_hsusb_phy_reset: success
<6>[ 34.195678] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[ 34.195861] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[ 34.195983] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 34.196166] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 34.196929] msm72k_udc: ept #0 out max:64 head:ffa02000 bit:0
<6>[ 34.197143] msm72k_udc: ept #1 out max:512 head:ffa02080 bit:1
<6>[ 34.197235] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.197448] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 34.197540] msm72k_udc: ept #4 out max:512 head:ffa02200 bit:4
<6>[ 34.197753] msm72k_udc: ept #5 out max:512 head:ffa02280 bit:5
<6>[ 34.197845] msm72k_udc: ept #6 out max:512 head:ffa02300 bit:6
<6>[ 34.198059] msm72k_udc: ept #7 out max:512 head:ffa02380 bit:7
<6>[ 34.198150] msm72k_udc: ept #8 out max:512 head:ffa02400 bit:8
<6>[ 34.198364] msm72k_udc: ept #9 out max:512 head:ffa02480 bit:9
<6>[ 34.198547] msm72k_udc: ept #10 out max:512 head:ffa02500 bit:10
<6>[ 34.198760] msm72k_udc: ept #11 out max:512 head:ffa02580 bit:11
<6>[ 34.198883] msm72k_udc: ept #12 out max:512 head:ffa02600 bit:12
<6>[ 34.200134] msm72k_udc: ept #13 out max:512 head:ffa02680 bit:13
<6>[ 34.200225] msm72k_udc: ept #14 out max:512 head:ffa02700 bit:14
<6>[ 34.200439] msm72k_udc: ept #15 out max:512 head:ffa02780 bit:15
<6>[ 34.200531] msm72k_udc: ept #0 in max:64 head:ffa02040 bit:16
<6>[ 34.200744] msm72k_udc: ept #1 in max:512 head:ffa020c0 bit:17
<6>[ 34.200836] msm72k_udc: ept #2 in max:512 head:ffa02140 bit:18
<6>[ 34.201049] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.201141] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 34.201354] msm72k_udc: ept #5 in max:512 head:ffa022c0 bit:21
<6>[ 34.201446] msm72k_udc: ept #6 in max:512 head:ffa02340 bit:22
<6>[ 34.201660] msm72k_udc: ept #7 in max:512 head:ffa023c0 bit:23
<6>[ 34.201751] msm72k_udc: ept #8 in max:512 head:ffa02440 bit:24
<6>[ 34.201965] msm72k_udc: ept #9 in max:512 head:ffa024c0 bit:25
<6>[ 34.202148] msm72k_udc: ept #10 in max:512 head:ffa02540 bit:26
<6>[ 34.202270] msm72k_udc: ept #11 in max:512 head:ffa025c0 bit:27
<6>[ 34.202453] msm72k_udc: ept #12 in max:512 head:ffa02640 bit:28
<6>[ 34.202575] msm72k_udc: ept #13 in max:512 head:ffa026c0 bit:29
<6>[ 34.202758] msm72k_udc: ept #14 in max:512 head:ffa02740 bit:30
<6>[ 34.202880] msm72k_udc: ept #15 in max:512 head:ffa027c0 bit:31
<6>[ 34.203094] usb: notify offline
<6>[ 34.203216] msm_hsusb: enable pullup
<6>[ 34.206329] msm72k_udc: msm72k_udc: suspend
<6>[ 34.226043] batt: charging SLOW
<6>[ 34.312683] msm72k_udc: msm72k_udc: reset
<6>[ 34.314941] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<6>[ 34.473693] msm72k_udc: msm72k_udc: reset
<6>[ 34.475982] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 34.696075] ### notify_usb_connected(1) ###
<6>[ 34.696228] android_usb gadget: high speed config #1: android
<6>[ 34.696716] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.696929] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.985809] binder: release 289:289 transaction 2744 out, still active
<6>[ 35.002349] binder: 79:223 transaction failed 29189, size 4-0
<6>[ 35.002593] binder: send failed reply for transaction 2744, target dead
<6>[ 55.218261] binder: 79:147 transaction failed 29189, size 52-0
<6>[ 59.133666] batt: 83%, 4060 mV, 58 mA (-68 avg), 27.1 C, 1126 mAh
<6>[ 67.028320] enabling adb
<6>[ 67.028472] msm_hsusb: disable pullup
<6>[ 67.045684] msm_hsusb: enable pullup
<6>[ 67.048828] msm72k_udc: msm72k_udc: suspend
<6>[ 67.056182] adb_open
<6>[ 67.206604] msm72k_udc: msm72k_udc: reset
<6>[ 67.206665] usb: notify offline
<6>[ 67.206878] adb_release
<6>[ 67.207946] adb_open
<6>[ 67.208740] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<3>[ 67.209564] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 67.367462] msm72k_udc: msm72k_udc: reset
<6>[ 67.369750] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 67.581878] ### notify_usb_connected(1) ###
<6>[ 67.581970] android_usb gadget: high speed config #1: android
<6>[ 67.582031] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 67.582061] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 67.582763] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 67.582824] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<3>[ 68.069061] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 115.879241] batt: 83%, 4089 mV, 251 mA (230 avg), 27.6 C, 1129 mAh
<6>[ 165.942657] batt: 84%, 4094 mV, 250 mA (254 avg), 28.0 C, 1134 mAh
cat<6>[ 216.020111] batt: 84%, 4099 mV, 248 mA (249 avg), 28.2 C, 1137 mAh
<6>[ 266.188140] batt: 84%, 4104 mV, 248 mA (249 avg), 28.5 C, 1140 mAh
<6>[ 316.250946] batt: 84%, 4104 mV, 246 mA (248 avg), 28.7 C, 1145 mAh

What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.

Ok, I'll spell it out:
ROOT. You need it to see system logs.
Then wait until it crashes with reboot.
Then run:
adb shell cat /proc/last_kmsg > c:\last_kmsg.log
adb shell cat /proc/kmsg > c:\kmsg.log
(here you'll need to stop it after 20-30 sec by Ctrl-C)
adb bugreport > c:\bugreport.log
Then you'll have 3 files in C:\, which you need. Upload here, maybe something will be better understandable from them.

ok thanks i will try to do that

GchildT said:
What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.
Click to expand...
Click to collapse
Hi to all
I didn't want to open a new thread because of the sam problem.
So I have Nexus One, and it restarts randomly after a period of use. When the phone restarts it is stuck on the "X" sign, until it reboots again, and again... and I have to remove battery and wait for a while to turn it back on.
Anybody have any idea what this could be, and could it be this conflict.
Android version: 2.3.3
Baseband version: 32.50.00.32U_5.12.00.08
Kernel version: 2.6.35.7-59423-g008607d4
[email protected]#1
Build number: GRI40
HBOOT: 0.35.0017
Radio-5.12.00.00
Current recovery: RA Recovery V2.2.1

Problem with connection of Usb-Eth-adapter

I am sorry for possible grammatical and stylistic mistakes - I use the translator of google.
Please help.
Samsung Galaxy Note on the Android ICS 4.0.3 (stock firmware (N7000XXLQ2_N7000OXELP6_N7000XXLPT_HOME), kernel CF-Root-SGN_XX_SEB_LQ3-v5.6-CWM5).
Code:
# uname -a
Linux localhost 3.0.15-N7000XXLQ3-CL646962 #3 SMP PREEMPT Wed May 30 21:05:57 KST 2012 armv7l GNU/Linux
It is necessary to connect the adapter USB-Eth adapter (chip ASIX AX88772B). Connected via USB-OTG.
Driver's sources: AX88772B_772A_760_772_178_LINUX_Driver_v4.4.0_Source.zip
Kernel's sources: GT-N7000_ICS_Opensource_Update3.zip
Linked arm-2010q1.
Plug the adapter:
Code:
[ 90.311645] usb_otg_accessory_power: otg power = 1
[ 90.316215] host_notify: ndev name=usb_otg: from state=0 -> to state=1
[ 90.645890] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 90.646018] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 90.646145] usb usb2: Product: S3C OTGHCD
[ 90.646225] usb usb2: Manufacturer: Linux 3.0.15-N7000XXLQ3-CL646962 EMSP_OTGHCD
[ 90.646348] usb usb2: SerialNumber: s3cotg
[ 90.688297] usb usb2: otg host do not enter suspend.
[ 90.688354] OTG s5pc110_start_otg(214): OTG HCD Initialized HCD, bus=C110 OTG Controller, usbbus=2
[ 91.025575] usb 2-1: new high speed USB device number 2 using s3c_otghcd
[ 91.070410] usb 2-1: New USB device found, idVendor=0b95, idProduct=772b
[ 91.070520] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 91.070621] usb 2-1: SerialNumber: 000977
Inserting modules (mii and asix):
Code:
# insmod /system/lib/modules/mii.ko
# insmod /system/lib/modules/asix.ko
# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 1519:0020
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 002: ID 0b95:772b
# lsmod
asix 45984 0 - Live 0xbf080000
mii 4249 1 asix, Live 0xbf007000
dhd 390627 0 - Live 0xbf01f000
j4fs 69431 1 - Live 0xbf00a000 (P)
Si4709_driver 24207 0 - Live 0xbf000000
# dmesg | grep asix
[ 208.068599] eth0: register 'asix' at usb-s3cotg-1, ASIX AX88772B USB 2.0 Ethernet, 1e:c0:f7:bf:6d:77
[ 208.072102] usbcore: registered new interface driver asix
#
There is eth0 and his mac.
But
Code:
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
and then when I try to unload the module asix, or pull out the USB connector have a kernel panic:
Code:
<6>[15424.006991] usb 2-1: USB disconnect, device number 2
<6>[15424.007787] eth0: unregister 'asix' usb-s3cotg-1, ASIX AX88772B USB 2.0 Ethernet
<1>[15424.027392] Unable to handle kernel paging request at virtual address bff7c022
<1>[15424.027503] pgd = c0004000
<1>[15424.027560] [bff7c022] *pgd=6b0b2811, *pte=00000000, *ppte=00000000
<0>[15424.027696] Internal error: Oops: 807 [#1] PREEMPT SMP
<4>[15424.027783] Modules linked in: asix mii dhd j4fs(P) Si4709_driver [last unloaded: dhd]
<4>[15424.027977] CPU: 0 Tainted: P (3.0.15-N7000XXLQ3-CL646962 #3)
<4>[15424.028125] PC is at __hw_addr_flush+0x38/0x68
<4>[15424.028217] LR is at dev_addr_flush+0x18/0x24
<4>[15424.028308] pc : [<c060eb5c>] lr : [<c060ec04>] psr: 20000013
<4>[15424.028394] sp : e5307d78 ip : d64e776d fp : e5307d94
<4>[15424.028487] r10: e563d400 r9 : 0000001f r8 : 00000000
<4>[15424.028581] r7 : d64e6800 r6 : 00200200 r5 : d64e6978 r4 : bff7c01e
<4>[15424.028689] r3 : c742d940 r2 : bff7c01e r1 : 00000030 r0 : c742d970
<4>[15424.028803] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
<4>[15424.028923] Control: 10c5387d Table: 62d9404a DAC: 00000015
<4>[15424.047751] Backtrace:
<4>[15424.047848] [<c060eb24>] (__hw_addr_flush+0x0/0x68) from [<c060ec04>] (dev_addr_flush+0x18/0x24)
<4>[15424.047980] r7:d64e6800 r6:d64e6800 r5:d64e6800 r4:d64e6800
<4>[15424.048162] [<c060ebec>] (dev_addr_flush+0x0/0x24) from [<c0605078>] (free_netdev+0x34/0xc4)
<4>[15424.048289] r5:d64e6800 r4:d64e6c20
<4>[15424.048464] [<c0605044>] (free_netdev+0x0/0xc4) from [<bf033ff0>] (axusbnet_disconnect+0xa8/0xec [asix])
<4>[15424.048605] r7:d64e6800 r6:d6356000 r5:d3a63e00 r4:d64e6c20
<4>[15424.048806] [<bf033f48>] (axusbnet_disconnect+0x0/0xec [asix]) from [<c049c0fc>] (usb_unbind_interface+0x58/0x1d8)
<4>[15424.048956] r7:bf038280 r6:d6356000 r5:d3a63e20 r4:d3a63e00
<4>[15424.049127] [<c049c0a4>] (usb_unbind_interface+0x0/0x1d8) from [<c04508bc>] (__device_release_driver+0x78/0xc8)
<4>[15424.049304] [<c0450844>] (__device_release_driver+0x0/0xc8) from [<c04509e8>] (device_release_driver+0x24/0x30)
<4>[15424.049451] r5:d3a63e20 r4:d3a63e54
<4>[15424.049563] [<c04509c4>] (device_release_driver+0x0/0x30) from [<c044fe20>] (bus_remove_device+0xc4/0xd4)
<4>[15424.049703] r5:d3a63e20 r4:d3a63e20
<4>[15424.049813] [<c044fd5c>] (bus_remove_device+0x0/0xd4) from [<c044e69c>] (device_del+0x100/0x174)
<4>[15424.049943] r7:00000001 r6:e563d400 r5:d6356068 r4:d3a63e20
<4>[15424.050115] [<c044e59c>] (device_del+0x0/0x174) from [<c04990c4>] (usb_disable_device+0xa8/0x1b0)
<4>[15424.050247] r7:00000001 r6:e563d400 r5:00000000 r4:d6356000
<4>[15424.050411] [<c049901c>] (usb_disable_device+0x0/0x1b0) from [<c0493c3c>] (usb_disconnect+0x90/0x12c)
<4>[15424.050577] [<c0493bac>] (usb_disconnect+0x0/0x12c) from [<c04949b4>] (hub_thread+0x350/0x11ac)
<4>[15424.050755] [<c0494664>] (hub_thread+0x0/0x11ac) from [<c029c4c0>] (kthread+0x90/0x98)
<4>[15424.050918] [<c029c430>] (kthread+0x0/0x98) from [<c0283d38>] (do_exit+0x0/0x6e0)
<4>[15424.051033] r7:00000013 r6:c0283d38 r5:c029c430 r4:e5043ef0
<0>[15424.051184] Code: e3406020 e593c004 e2830030 e3a01030 (e582c004)
<4>[15424.051403] ---[ end trace 8b33e0e0e42b3c17 ]---
<0>[15424.051743] Kernel panic - not syncing: Fatal exception
The situation is similar to the adapter D-Link DU-E100 and the module pegasus - kernel panic when unloading the module or disconnect the adapter.
Code:
<6>[ 86.855070] usb 2-1: new full speed USB device number 2 using s3c_otghcd
<6>[ 86.855264] OTG compare_ed(384): update ed 8 (0x8)
<6>[ 86.877747] usb 2-1: New USB device found, idVendor=07b8, idProduct=4102
<6>[ 86.877788] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 86.877827] usb 2-1: Product: USB 10/100 Fast Ethernet
<6>[ 86.877854] usb 2-1: Manufacturer: USBs
<6>[ 86.877876] usb 2-1: SerialNumber: 8f0c6e
<6>[ 386.511487] pegasus 2-1:1.0: eth0, USB 10/100 Fast Ethernet, 4e:01:05:8f:0c:6e
<6>[ 386.512386] usbcore: registered new interface driver pegasus
<6>[ 714.011428] usbcore: deregistering interface driver pegasus
<1>[ 714.030230] Unable to handle kernel paging request at virtual address 8f050152
<1>[ 714.030302] pgd = d6654000
<1>[ 714.030331] [8f050152] *pgd=00000000
<0>[ 714.030373] Internal error: Oops: 805 [#1] PREEMPT SMP
<4>[ 714.030421] Modules linked in: pegasus(-) usbnet mii dhd j4fs(P) Si4709_driver
<4>[ 714.030507] CPU: 0 Tainted: P (3.0.15-N7000XXLQ3-CL646962 #3)
<4>[ 714.030592] PC is at __hw_addr_flush+0x38/0x68
<4>[ 714.030636] LR is at dev_addr_flush+0x18/0x24
<4>[ 714.030680] pc : [<c060eb5c>] lr : [<c060ec04>] psr: 200e0013
<4>[ 714.030734] sp : d5b7fde0 ip : e3a06e0c fp : d5b7fdfc
<4>[ 714.030782] r10: 00000000 r9 : d5b7e000 r8 : 00000000
<4>[ 714.030831] r7 : bf08d1ec r6 : 00200200 r5 : e3a01178 r4 : 8f05014e
<4>[ 714.030890] r3 : d77b06c0 r2 : 8f05014e r1 : 00000030 r0 : d77b06f0
<4>[ 714.030952] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[ 714.031016] Control: 10c5387d Table: 5665404a DAC: 00000015
<4>[ 714.038601] Backtrace:
<4>[ 714.038636] [<c060eb24>] (__hw_addr_flush+0x0/0x68) from [<c060ec04>] (dev_addr_flush+0x18/0x24)
<4>[ 714.038713] r7:bf08d1ec r6:e3a01000 r5:e3a01000 r4:e3a01000
<4>[ 714.038787] [<c060ebec>] (dev_addr_flush+0x0/0x24) from [<c0605078>] (free_netdev+0x34/0xc4)
<4>[ 714.038861] r5:e3a01000 r4:e3a01420
<4>[ 714.038918] [<c0605044>] (free_netdev+0x0/0xc4) from [<bf08a690>] (pegasus_disconnect+0xa4/0xd8 [pegasus])
<4>[ 714.039002] r7:bf08d1ec r6:cee0f020 r5:bf08dd14 r4:e3a01420
<4>[ 714.039070] [<bf08a5ec>] (pegasus_disconnect+0x0/0xd8 [pegasus]) from [<c049c0fc>] (usb_unbind_interface+0x58/0x1d8)
<4>[ 714.039160] r6:d0e76c00 r5:cee0f020 r4:cee0f000 r3:00000003
<4>[ 714.039229] [<c049c0a4>] (usb_unbind_interface+0x0/0x1d8) from [<c04508bc>] (__device_release_driver+0x78/0xc8)
<4>[ 714.039322] [<c0450844>] (__device_release_driver+0x0/0xc8) from [<c04509c0>] (driver_detach+0xb4/0xb8)
<4>[ 714.039403] r5:bf08d224 r4:cee0f020
<4>[ 714.039445] [<c045090c>] (driver_detach+0x0/0xb8) from [<c044fa84>] (bus_remove_driver+0x84/0xc8)
<4>[ 714.039522] r7:d5b7ff34 r6:c09adbcc r5:bf08d224 r4:00000000
<4>[ 714.039585] [<c044fa00>] (bus_remove_driver+0x0/0xc8) from [<c0451318>] (driver_unregister+0x58/0x78)
<4>[ 714.039665] r7:d5b7ff34 r6:bf08d21c r5:bf08d224 r4:00000000
<4>[ 714.039726] [<c04512c0>] (driver_unregister+0x0/0x78) from [<c049be70>] (usb_deregister+0xc4/0xdc)
<4>[ 714.039803] r5:bf08d224 r4:bf08d214
<4>[ 714.039848] [<c049bdac>] (usb_deregister+0x0/0xdc) from [<bf08c6f8>] (pegasus_exit+0x18/0x1c [pegasus])
<4>[ 714.039943] [<bf08c6e0>] (pegasus_exit+0x0/0x1c [pegasus]) from [<c02b6de8>] (sys_delete_module+0x168/0x238)
<4>[ 714.040039] [<c02b6c80>] (sys_delete_module+0x0/0x238) from [<c0244c80>] (ret_fast_syscall+0x0/0x30)
<4>[ 714.040119] r8:c0244e28 r7:00000081 r6:00000001 r5:00000000 r4:be8ec92e
<0>[ 714.040192] Code: e3406020 e593c004 e2830030 e3a01030 (e582c004)
<4>[ 714.041333] ---[ end trace b11a3de5703310e8 ]---
<0>[ 714.041419] Kernel panic - not syncing: Fatal exception
In both cases it is clear that a problem in impossibility of removal of the mac-address (its value = 00:00:00:00:00:00 or uncertain - if I
understood correctly)
Tell me what and where to fix.
Or at least the direction in which to search.

Were you able to solve this? I've run into a very similar issue with a GT-I9100.

[DEV][Kernel] Updated Archos Kernel

Hi!
I've done some work to merge the kernel code from archos into the current one from p-android-omap-3.0, omapzoom git one.
I looked for the base version and I assumed, that this one 45ee6d7c8ae96ca60cb73821414927c1118bbdf8
Date: Wed Jan 18 16:28:16 2012 +0200
was the best. It has only 250~ files changed (~130 where for pvr) compared to the one from omapzoom.
So I took these version and merged the archos kernel into a new branch. After that I made a fast forward and merged (most of) the archos specific changes into the current head.
After some troubles and with the help of scholbert with the serial output cable, I was able get a booting kernel which starts the base system including adb daemon.
Currently some thins are not working yet:
Ducati Binary from archos doesn't load.
I really don't know how to build a new one which fits our device.
I tried the tutorial at http://omappedia.org/wiki/RPMsg_BIOS_Sources
but with no luck. The test_omx_sysm3.xem3 is build but the test_omx_appm3.xem3 is missing. So it is not possible to generate an own ducati-m3.bin file.
PVR libraries are not starting
I took the pvr from the branch android-omap-tuna-3.0 but I'm was not able to test further the SGX drivers.
If some one would like to try it just copy the pvr directory into drivers/gpu/ folder and adapt Makefile and KConfig.
Battery is not working yet
I saw a post on another devices here:
[ROM/KERNEL] UNOFFICIAL CM10 + 3.x Kernel for Kindle Fire [08/17 ALPHA
Maybe we can learn something from Hashcode...
If someone is interested in, my repository is located at:
https://github.com/Quallenauge/kernel-archosg9

Cool stuff!
Hi Quallenauge,
well done, impressive work so far!!
I did a similar attempt to get an idea of the Archos specific stuff compared to the omapzoom kernels.
To get it very close to the essentials, i used the 3.0 Beta branch which is also 3.0.8 kernel version.
I made an old school diff between this branch and the Archos stock one and even stripped off some parts (e.g. documentation & default configs).
Though the patch is quite big, there're much less files affected.
Most of them are not even required for the Gen9 series to work.
By looking into the file you may get a good overview, where most of the work had been done.
My intention was to port this to an even newer kernel code.
Should be possible, but we also have to keep track of the changes in the kernel APIs.
Anyway here's my patch. Maybe it helps to get some of the bugs fixed
Cheers,
scholbert

scholbert said:
I did a similar attempt to get an idea of the Archos specific stuff compared to the omapzoom kernels.
To get it very close to the essentials, i used the 3.0 Beta branch which is also 3.0.8 kernel version.
I made an old school diff between this branch and the Archos stock one and even stripped off some parts (e.g. documentation & default configs).
Click to expand...
Click to collapse
I really appreciate it and I know how much effort this is. I also need some attempts. (Again: Thanks for the tip with the USB serial cable).
My intention was to port this to an even newer kernel code.
Should be possible, but we also have to keep track of the changes in the kernel APIs.
Click to expand...
Click to collapse
Yes, but most of the api changes are not affected by the archos changes.
Currently the version 3.0.31+ is within my repository. I expect major API changes in 3.1, 3.2, .3.X..kernels.
My target is to drive JellyBean with hw acceleration (3d and video) on the Archos G9.
Anyway here's my patch. Maybe it helps to get some of the bugs fixed
Click to expand...
Click to collapse
Thanks (!!!), this will be an good reference book in case of errors. :good:
What could be the next steps?
archos-memory.c has to be rewritten to mach the non-static memory definitions. No need to difference between 512MB/1Gbyte Models because this is done by the latest kernel changes.
I've done that yesterday quick&dirty and it works....sort off. No tiler map but the ducati tablet binary seems to be loading.
Get the graphic drivers working: Source should be taken from here. git.omapzoom.org
I've taken the kernel source from android-omap-tuna-3.0 but these are version 1.8. (Git provides 1.9).
Would someone jump on the bandwagon?

Quallenauge said:
Would someone jump on the bandwagon?
Click to expand...
Click to collapse
I'm in, I'm in, where do I sign! :laugh:
This is the sort of thing I've been looking at for a while. I've had a few failed experiments while poking around with trying to update the goldfish kernel but i'm still getting my head round it all and I still have more questions than answers. Definitely on the wrong side of noob on this subject but we've all got to start somewhere .
Have you got 3.0.31+ booting?
Fantastic Work Everyone!

trevd said:
I'm in, I'm in, where do I sign! :laugh:
Click to expand...
Click to collapse
=) Now you are signed automatically
Others can also signed in if they:
Installed GIT
Installed an IDE, for me it is Eclipse with CDT and E-Git extension, I used this tutorial for setup a kernel project: http://friendlyarm-in-tunisia.blogspot.de/2011/01/configuring-building-and-debugging.html
Installed a toolchain (You can use the guide on: http://forum.xda-developers.com/showpost.php?p=27427105&postcount=8)
Knows how to build a kernel, e.g.:
Code:
export ARCH=arm
export CROSS_COMPILE=<PATH>linaro-toolchain-prebuild/android-toolchain-eabi/bin/arm-linux-androideabi- make
make menuconfig
make
trevd said:
...I still have more questions than answers. Definitely on the wrong side of noob on this subject but we've all got to start somewhere .
Click to expand...
Click to collapse
Just ask the questions. Maybe my repo is a good start.
trevd said:
Have you got 3.0.31+ booting?
Click to expand...
Click to collapse
Yes it is booting. The userspace does have some problems. (no sgx init, some crashes).
Okay, let's start:
I attached a patch (which as to be applied to the HEAD-Version of my kernel repository), which uses the dynamic memory allocation which was introduced for a few months. So there's no need to use the archos memory definitions.
At first I wanted to use the init method of android-display.c, but later I have realized that archos used a completly another structure which means high adaption efforts :-/ So I used my quick&dirty approach which seems to work.
Also included in the patch is are the drivers for PVR 1.8. I know there are a new version 1.9 is out, but I wanted to see if this version is also usable (for the start). I also had updated these binaries within the rom, so that kernel drivers and user space libraries are matching.
The current state is the following:
Graphics drivers are not correctly loaded. I get
Code:
D/libEGL ( 2780): loaded /system/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 2780): loaded /system/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 2780): loaded /system/lib/egl/libGLESv2_POWERVR_SGX540_120.so
W/libEGL ( 2780): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/cat ( 610): <6>[ 411.734649] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4807, drivers/gpu/pvr/bridged_pvr_bridge.c]
and I don't know why (see logcat.txt.gz). Maybe I had forgotten to reserve some SGX memory or else... I don't know :-/
Also yesterday I encountered some troubles at cold boot. Then the rpmsg driver seems to crash! I was able to get the kernel messages over the USB<-Serial->USB cable. See capture.txt:
Code:
[ 12.263916] rproc_da_to_pa: rproc_da_to_pa: matched mem entry no. 0
[ 12.264038] omap-rproc omap-rproc.1: da 0x8054b034 pa 0xb384b034 len 0x56ac
[ 12.264343] omap-rproc omap-rproc.1: section: type 2 da 0x805546e0 len 0x200
[ 12.264495] rproc_da_to_pa: rproc_da_to_pa: matched mem entry no. 0
[ 12.264617] omap-rproc omap-rproc.1: da 0x805546e0 pa 0xb38546e0 len 0x200
[ 12.264831] omap-rproc omap-rproc.1: section: type 2 da 0x9f0e0000 len 0x102f8
[ 12.264984] rproc_da_to_pa: rproc_da_to_pa: matched mem entry no. 0
[ 12.265106] omap-rproc omap-rproc.1: da 0x9f0e0000 pa 0xb2be0000 len 0x102f8
[ 12.336425] omap-rproc omap-rproc.1: remote processor ipu is now up
[ 12.806274] ------------[ cut here ]------------
[ 12.811889] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:135 l3_interrupt_handler+0x280/0x3b4()
[ 12.822387] CUSTOM SRESP error with SOURCE:L4CFG
[ 12.828002] Modules linked in:
[ 12.831878] Backtrace:
[ 12.835144] [<c0087a14>] (dump_backtrace+0x0/0x138) from [<c068cb18>] (dump_stack+0x20/0x24)
[ 12.845214] r7:00000087 r6:c00acd4c r5:00000009 r4:e92f1ba0
[ 12.852691] [<c068caf8>] (dump_stack+0x0/0x24) from [<c00d6410>] (warn_slowpath_common+0x64/0x7c)
[ 12.863372] [<c00d63ac>] (warn_slowpath_common+0x0/0x7c) from [<c00d64e4>] (warn_slowpath_fmt+0x40/0x48)
[ 12.874694] r8:00080003 r7:00000448 r6:f8000000 r5:c007d000 r4:c07c779a
[ 12.883209] r3:00000009
[ 12.886749] [<c00d64a4>] (warn_slowpath_fmt+0x0/0x48) from [<c00acd4c>] (l3_interrupt_handler+0x280/0x3b4)
[ 12.898315] r3:c07c779a r2:c07c7741
[ 12.903015] [<c00acacc>] (l3_interrupt_handler+0x0/0x3b4) from [<c01240b8>] (handle_irq_event_percpu+0xcc/0x2c4)
[ 12.915222] [<c0123fec>] (handle_irq_event_percpu+0x0/0x2c4) from [<c01242fc>] (handle_irq_event+0x4c/0x6c)
[ 12.926910] [<c01242b0>] (handle_irq_event+0x0/0x6c) from [<c0126c60>] (handle_fasteoi_irq+0xf4/0x144)
[ 12.938049] r6:c0883b8c r5:c007d000 r4:c0883b40 r3:00000000
[ 12.945556] [<c0126b6c>] (handle_fasteoi_irq+0x0/0x144) from [<c0123934>] (generic_handle_irq+0x30/0x40)
[ 12.956848] r6:0000002a r5:e92f0000 r4:0000002a r3:c0126b6c
[ 12.964385] [<c0123904>] (generic_handle_irq+0x0/0x40) from [<c007d3cc>] (asm_do_IRQ+0xac/0xe0)
[ 12.974792] r4:c007d000 r3:0000019a
[ 12.979492] [<c007d320>] (asm_do_IRQ+0x0/0xe0) from [<c0083108>] (__irq_svc+0x48/0xe0)
[ 12.989013] Exception stack(0xe92f1cc0 to 0xe92f1d08)
[ 12.995117] 1cc0: 00000000 c0947fe0 00000000 00000000 c007d000 00000282 c12bc040 c007bf80
[ 13.004943] 1ce0: e92f0000 e92f0000 3f77dfbc e92f1d5c c00ddc5c e92f1d08 c00de3d4 c00ddcdc
[ 13.014770] 1d00: 40000113 ffffffff
[ 13.019104] [<c00ddc44>] (__do_softirq+0x0/0x2a0) from [<c00de3d4>] (irq_exit+0x64/0xb8)
[ 13.028839] [<c00de370>] (irq_exit+0x0/0xb8) from [<c0088f64>] (ipi_timer+0x58/0x68)
[ 13.038116] r4:c007b040 r3:00000000
[ 13.042877] [<c0088f0c>] (ipi_timer+0x0/0x68) from [<c007d478>] (do_local_timer+0x78/0x9c)
[ 13.052764] r6:c0892ba8 r5:c007d000 r4:e92f0000 r3:0000055e
[ 13.060302] [<c007d400>] (do_local_timer+0x0/0x9c) from [<c0083108>] (__irq_svc+0x48/0xe0)
[ 13.070251] Exception stack(0xe92f1dc0 to 0xe92f1e08)
[ 13.076385] 1dc0: c089e1d8 c007d000 c08f0cb8 c08f0cb8 00000047 e92f0000 00000001 00000003
[ 13.086273] 1de0: 00000003 60000113 c0927bc6 e92f1eac c00d701c e92f1e08 c00d72e8 c00d7960
[ 13.096099] 1e00: 60000113 ffffffff
[ 13.100433] [<c00d74a4>] (vprintk+0x0/0x590) from [<c068d240>] (printk+0x2c/0x34)
[ 13.109497] [<c068d214>] (printk+0x0/0x34) from [<c04d3ae4>] (thermal_lookup_temp+0x3c/0xa8)
[ 13.119659] r3:e91b9b40 r2:c083c278 r1:c06c352c r0:c083c1ae
[ 13.127227] [<c04d3aa8>] (thermal_lookup_temp+0x0/0xa8) from [<c04d4050>] (hotspot_temp_to_sensor_temp+0x24/0x88)
[ 13.139556] r5:c0aa67ac r4:000061a8
[ 13.144256] [<c04d402c>] (hotspot_temp_to_sensor_temp+0x0/0x88) from [<c04d417c>] (average_cpu_sensor_delayed_work_fn+0xc8/0x130)
[ 13.158203] r4:e91b9b40 r3:e91b9b40
[ 13.162933] [<c04d40b4>] (average_cpu_sensor_delayed_work_fn+0x0/0x130) from [<c00f26bc>] (process_one_work+0x26c/0x46c)
[ 13.176025] r7:c12c0600 r6:c12bc5c0 r5:e91b9b78 r4:e922cb40
[ 13.183563] [<c00f2450>] (process_one_work+0x0/0x46c) from [<c00f2cb8>] (worker_thread+0x210/0x34c)
[ 13.194488] [<c00f2aa8>] (worker_thread+0x0/0x34c) from [<c00f7564>] (kthread+0x9c/0xa8)
[ 13.204223] [<c00f74c8>] (kthread+0x0/0xa8) from [<c00da788>] (do_exit+0x0/0x6fc)
[ 13.213256] r6:c00da788 r5:c00f74c8 r4:e941feb0
[ 13.219360] ---[ end trace 66050ce957e8cabb ]---
[ 13.225006] Master 0x44 DucatiM3
[ 13.229156] L4CFG OPCODE 0x00000002
...
It would be really cool, if we can squash these issues away...

Hi Quallenauge,
i'm sorry but i guess time is lacking to join development on a certain level.
Apart from that i prepare for holiday these days.
Anyway, just some advice... or maybe just a guess.
I had a short look into the patch you made and also looked at the omapzoom repository of your reference kernel.
As you already stated the complete pvr directory is missing in this kernel code.
I have not found out yet, why it had been removed (obviously this is an Android kernel).
Anyway apart from this driver directory there might be some essential parts missing in this code (e.g. internal kernel API stuff).
If you want to step to a higher kernel base, why not use this one:
https://android.googlesource.com/kernel/omap/+/refs/heads/android-omap-panda-3.0/#
You may try to use it as a base (3.0.31 as well) and again implement the archos specific stuff.
This way you might get less trouble to get the pvr part working, i guess.
Might be better than hunting for the tuna implementation, because Pandaboard in fact is very close to our tablet's design.
So i even wonder, if it would be possible some day to use the panda resources as a base to build
the Android OS (e.g. framework) for the Gen 9 as well.
As stated this is more a guess...
Good luck,
scholbert

scholbert said:
Hi Quallenauge,
i'm sorry but i guess time is lacking to join development on a certain level.
Apart from that i prepare for holiday these days.
Click to expand...
Click to collapse
No problem, we have all private things to do .
So i even wonder, if it would be possible some day to use the panda resources as a base to build
the Android OS (e.g. framework) for the Gen 9 as well.
Click to expand...
Click to collapse
For me, I will stuck at the kernel from omapzoom, because activly maintained display for the LCD display.
I guess the changes are not so big compared to the panda board kernel.
(And I also wan't this kind of merging not again, yet).
But others are invited to try it out.
It seems to be not complicated to replace the pvr driver tree with another implementation. From my point of view, it is equal to copy the files into that directory and adapt makefiles/Kconfig files.
Currently I look at the issues that I have with cold boot. Hopefully I get an solution.... Currently I have no idea

Disclaimer: I've built and modified kernels for my android phone a couple of times, but those have only been minor modifications, nothing at all on this scale, so please ignore my comments if they are too noobish.
Anyway, regarding the pvr issues: I found this: https://groups.google.com/forum/#!msg/android-building/feACaqANrAs/NPgF5gbHjSwJ apparently some guy had similar experiences with the panda board when mixing versions for different things. JBQ is then referring to this commit: https://android.googlesource.com/kernel/omap.git/+/52f476403350050beb0dff135a55c06c9e7a82a9 have you seen this already?
I'd love to get my hands dirty, but I think I'll start slowly, much left to learn

ergoen said:
Disclaimer: I've built and modified kernels for my android phone a couple of times, but those have only been minor modifications, nothing at all on this scale, so please ignore my comments if they are too noobish.
Anyway, regarding the pvr issues: I found this: https://groups.google.com/forum/#!msg/android-building/feACaqANrAs/NPgF5gbHjSwJ apparently some guy had similar experiences with the panda board when mixing versions for different things. JBQ is then referring to this commit: https://android.googlesource.com/kernel/omap.git/+/52f476403350050beb0dff135a55c06c9e7a82a9 have you seen this already?
I'd love to get my hands dirty, but I think I'll start slowly, much left to learn
Click to expand...
Click to collapse
Hi!
I made some progress about the pvr issue. I splitted the initialization routines of archos and where able to use the android-display.c routines to get a running graphics system.
I've managed the kernel to boot up. Graphics drivers (1.9) are loaded (A80S model only) - (yeah!!) and they are working.
Battery loading is working!
Current ducati firmaware is loading!
Sound is not working anymore...I have to adapt the archos specific changes.
If you give it a try just use the kernel and image provided at my shared4 account:
http://www.4shared.com/folder/jJrxHmKb/30_online.html
If you want to start, just checkout my kernel repository and compile the kernel.
Note that the pvr driver has to build as module.
Just use my config also in my shared4s folder to build a kernel. Note, that I adapted only my A80S device for this.
If you want to adapt the other devices you're welcome to do so. I will give some hints what should be done.
(It may a good start to get knowledge about how things work together).
Also I builded up my rom using different sources, cyanogenmod and omapzoom to get the extened omap support.
You can download my manifest at my shared4s folder and download all sources. (Don't forget to use my github device/vendor repository).
Then you must apply the patch (also at the shared4s folder) at framework/base to add the needed include files.
After building you get the system folder as usual. HWComposer seems not to work. Strange, that when I delete them
from the rom, it uses a default one - I didn't know that... But at least graphics starts.
I don't know why this isn't working. I will look further.
Also the next manual step is needed: Make a symlink from /system/vendor/lib/hw/gralloc.omap4460.so to /system/vendor/lib/hw/gralloc.archos.so.
I think trevd can give some more instructions...I'm not really available atm.
Just checkout this forum from time to time.

Thanks!
I will check out the kernel sources and try to make proper changes (I have the 101s). Unfortunately I do not have a good enough computer to build the whole rom (I've tries building cyanogenmod before and it takes aaaaages), but the image on your 4shared page includes every necessary change, right?

ergoen said:
Thanks!
I will check out the kernel sources and try to make proper changes (I have the 101s). Unfortunately I do not have a good enough computer to build the whole rom (I've tries building cyanogenmod before and it takes aaaaages), but the image on your 4shared page includes every necessary change, right?
Click to expand...
Click to collapse
It is a snapshot. At least it boots up and the Android GUI is starting up... .
I wanted to build the optimized hwcomposer from the omapzoom repository,
but when I start surfaceflinger, the display became black. So this is the next step when I continue hacking on this.
Maybe it would be also good, to use the ICS release and test this kernel with that.

EDIT : Possible useful documentation, after a quick goolge into the problem described below
http://www.mjmwired.net/kernel/Documentation/arm/OMAP/DSS
I suppose it might be an idea to RTFM that comes in every kernel tree.... Often forget about it because google's so easy just to type in a search term but hours can be lost!!
Hi Folks,
I'm going to have an hack on this tonight..... There was a time when I was in the club on Saturday's but a quiet night in with linux kernel is how I get my kick now-a-days, :laugh: anyway I digress.
Quallenauge said:
I wanted to build the optimized hwcomposer from the omapzoom repository, but when I start surfaceflinger, the display became black. So this is the next step when I continue hacking on this.
Click to expand...
Click to collapse
strace at the ready then ...... Currently on the A101S I've had to disable watchdog_daemon because It could not find the battery path, there may be a slight difference there from the A80's
My surface flinger doesn't want to start because /dev/graphics/fb0 doesn't exist which is slightly confusing in the least, Is ( should ) this device be created by a kernel level code and setup in [device drivers]/[graphics .. ]/[Framebuffer Devices] or whatever the path is in menuconfig . From what I understand it is??? I was getting framebuffer and gralloc not a typewriter , which is a message i've seen before when trying to force in drivers of other devices, but I've stripped it all back to just load the android Open GL Drivers and that is what strace currently reveals....
I'll keep hacking on it, maybe something will click in my brain because it's still blowing my mind a bit...... I think I've got kernel fear, I'll get over it though! :good:
---------- Post added at 11:31 PM ---------- Previous post was at 10:49 PM ----------
Hmmm, Well it's pretty self explantory why I've not got an fb device, the question is why ? Highlighted line is missing from my 3.0.31 bring up
Code:
--------- beginning of /dev/log/main
I/cat ( 418): <6>[ 0.000000] Initializing cgroup subsys cpu
I/cat ( 418): <5>[ 0.000000] Linux version 3.0.8+ ([email protected]) (gcc version 4.4.1 (GCC) ) #4 SMP PREEMPT Thu Jun 7 16:12:27 CEST 2012
I/cat ( 418): <4>[ 0.000000] CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387f
I/cat ( 418): <4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
I/cat ( 418): <4>[ 0.000000] Machine: ARCHOS A101S board
I/cat ( 418): <6>[ 0.000000] fixup_archos: [email protected] from bootloader.
I/cat ( 418): <4>[ 0.000000] fixup_archos: [mem=512M init=/linuxrc debug omapdss.debug=0 omapfb.debug=0]
I/cat ( 418): <6>[ 0.000000] Product Name: A101S
I/cat ( 418): <6>[ 0.000000] DDR type elpida
[B][SIZE="4"]I/cat ( 418): <6>[ 0.000000] Reserving 8388608 bytes SDRAM for VRAM[/SIZE][/B]
I/cat ( 418): <4>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
I/cat ( 418): <6>[ 0.000000] OMAP4430 ES2.3
I/cat ( 418): <6>[ 0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000
I/cat ( 418): <7>[ 0.000000] On node 0 totalpages: 114432
I/cat ( 418): <7>[ 0.000000] free_area_init_node: node 0, pgdat c07eda40, node_mem_map c0977000
I/cat ( 418): <7>[ 0.000000] Normal zone: 1024 pages used for memmap
I/cat ( 418): <7>[ 0.000000] Normal zone: 0 pages reserved
I/cat ( 418): <7>[ 0.000000] Normal zone: 113408 pages, LIFO batch:31
I/cat ( 418): <6>[ 0.000000] PERCPU: Embedded 7 pages/cpu @c0d7d000 s7072 r8192 d13408 u32768
I/cat ( 418): <7>[ 0.000000] pcpu-alloc: s7072 r8192 d13408 u32768 alloc=8*4096
I/cat ( 418): <7>[ 0.000000] pcpu-alloc: [0] 0 [0] 1
I/cat ( 418): <4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 113408
I/cat ( 418): <5>[ 0.000000] Kernel command line: mem=512M init=/linuxrc debug omapdss.debug=0 omapfb.debug=0
I/cat ( 418): <6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
I/cat ( 418): <6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
I/cat ( 418): <6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
I/cat ( 418): <6>[ 0.000000] Memory: 446MB 1MB = 447MB total
I/cat ( 418): <5>[ 0.000000] Memory: 442284k/442284k available, 82004k reserved, 0K highmem
I/cat ( 418): <5>[ 0.000000] Virtual kernel memory layout:
I/cat ( 418): <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
I/cat ( 418): <5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
I/cat ( 418): <5>[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
I/cat ( 418): <5>[ 0.000000] vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB)
I/cat ( 418): <5>[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
I/cat ( 418): <5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
I/cat ( 418): <5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
I/cat ( 418): <5>[ 0.000000] .init : 0xc0008000 - 0xc005a000 ( 328 kB)
I/cat ( 418): <5>[ 0.000000] .text : 0xc005a000 - 0xc0778000 (7288 kB)
I/cat ( 418): <5>[ 0.000000] .data : 0xc0778000 - 0xc07ee5a0 ( 474 kB)
I/cat ( 418): <5>[ 0.000000] .bss : 0xc07ee5c4 - 0xc09768c8 (1569 kB)
I/cat ( 418): <6>[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
I/cat ( 418): <6>[ 0.000000] Preemptible hierarchical RCU implementation.
Code:
--------- beginning of /dev/log/main
I/cat ( 601): <6>[ 0.000000] Initializing cgroup subsys cpu
I/cat ( 601): <5>[ 0.000000] Linux version 3.0.31+ ([email protected]) (gcc version 4.7.1 20120531 (prerelease) (Linaro GCC 4.7-2012.06-1~dev) ) #186 SMP PREEMPT Mon Sep 17 21:23:15 CEST 2012
I/cat ( 601): <7>[ 0.000000] CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387d
I/cat ( 601): <7>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
I/cat ( 601): <7>[ 0.000000] Machine: ARCHOS A101S board
I/cat ( 601): <6>[ 0.000000] fixup_archos: [email protected] from bootloader.
I/cat ( 601): <7>[ 0.000000] fixup_archos: [mem=512M console=ttyO2,115200n8 init=/linuxrc debug omapdss.debug=0 omapfb.debug=0]
I/cat ( 601): <6>[ 0.000000] Product Name: A101S
I/cat ( 601): <3>[ 0.000000] Perform archos reserve...
I/cat ( 601): <3>[ 0.000000] Found 1 memory banks with total size: 536870912
I/cat ( 601): <3>[ 0.000000] Perform omap_ion_init()
I/cat ( 601): <6>[ 0.000000] omap4_total_ram_size = 0x20000000
I/cat ( 601): <6>[ 0.000000] omap4_smc_size = 0x300000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_input_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_ducati_heap_size = 0x5300000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_tiler_mem_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_smc_addr = 0x9fd00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_input_addr = 0x9fd00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_addr = 0x9fd00000
I/cat ( 601): <6>[ 0.000000] omap4_ducati_heap_addr = 0x9aa00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_tiler_mem_addr = 0x9aa00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_addr = 0x9aa00000
I/cat ( 601): <6>[ 0.000000] omap_ion_init: secure_input id=2 [9fd00000-9fd00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: secure_output_wfdhdcp id=5 [9fd00000-9fd00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: tiler id=1 [9aa00000-9aa00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: nonsecure_tiler id=3 [9aa00000-9aa00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: system id=0 [0-0] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: tiler_reservation id=4 [0-0] size=0
I/cat ( 601): <6>[ 0.000000] DDR type elpida
I/cat ( 601): <3>[ 0.000000] omap_ipu_set_static_mempool(start=0x9aa00000, size=0x5300000)
I/cat ( 601): <7>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
I/cat ( 601): <6>[ 0.000000] OMAP4430 ES2.3
I/cat ( 601): <6>[ 0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000
I/cat ( 601): <7>[ 0.000000] On node 0 totalpages: 108544
I/cat ( 601): <7>[ 0.000000] free_area_init_node: node 0, pgdat c085aea0, node_mem_map c0b71000
I/cat ( 601): <7>[ 0.000000] Normal zone: 1024 pages used for memmap
I/cat ( 601): <7>[ 0.000000] Normal zone: 0 pages reserved
I/cat ( 601): <7>[ 0.000000] Normal zone: 107520 pages, LIFO batch:31
I/cat ( 601): <6>[ 0.000000] PERCPU: Embedded 7 pages/cpu @c0f77000 s7328 r8192 d13152 u32768
I/cat ( 601): <7>[ 0.000000] pcpu-alloc: s7328 r8192 d13152 u32768 alloc=8*4096
I/cat ( 601): <7>[ 0.000000] pcpu-alloc: [0] 0 [0] 1
I/cat ( 601): <7>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 107520
I/cat ( 601): <5>[ 0.000000] Kernel command line: mem=512M console=ttyO2,115200n8 init=/linuxrc debug omapdss.debug=0 omapfb.debug=0
I/cat ( 601): <6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
I/cat ( 601): <6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
I/cat ( 601): <6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
I/cat ( 601): <6>[ 0.000000] Memory: 256MB 168MB = 424MB total
I/cat ( 601): <5>[ 0.000000] Memory: 416684k/416684k available, 107604k reserved, 0K highmem
I/cat ( 601): <5>[ 0.000000] Virtual kernel memory layout:
I/cat ( 601): <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
I/cat ( 601): <5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
I/cat ( 601): <5>[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
I/cat ( 601): <5>[ 0.000000] vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB)
I/cat ( 601): <5>[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
I/cat ( 601): <5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
I/cat ( 601): <5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
I/cat ( 601): <5>[ 0.000000] .init : 0xc0008000 - 0xc007c000 ( 464 kB)
I/cat ( 601): <5>[ 0.000000] .text : 0xc007c000 - 0xc082d000 (7876 kB)
I/cat ( 601): <5>[ 0.000000] .data : 0xc082e000 - 0xc085ccc0 ( 188 kB)
I/cat ( 601): <5>[ 0.000000] .bss : 0xc09f5e60 - 0xc0b70c48 (1516 kB)
I/cat ( 601): <6>[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
I/cat ( 601): <6>[ 0.000000] Preemptible hierarchical RCU implementation.
I/cat ( 601): <6>[ 0.000000] NR_IRQS:410
I/cat ( 601): <4>[ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck.
I/cat ( 601): <6>[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
I/cat ( 601): <6>[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
I/cat ( 601): <6>[ 0.000061] Calibrating delay loop... 1990.38 BogoMIPS (lpj=7774208)
I/cat ( 601): <6>[ 0.070312] pid_max: default: 32768 minimum: 301
I/cat ( 601): <6>[ 0.070709] Mount-cache hash table entries: 512
I/cat ( 601): <6>[ 0.071807] Initializing cgroup subsys debug
I/cat ( 601): <6>[ 0.071838] Initializing cgroup subsys cpuacct
I/cat ( 601): <6>[ 0.071899] Initializing cgroup subsys freezer
I/cat ( 601): <6>[ 0.071990] CPU: Testing write buffer coherency: ok
---------- Post added 30th September 2012 at 12:26 AM ---------- Previous post was 29th September 2012 at 11:31 PM ----------
More brain dump..... could well be usefulhttp://omappedia.org/wiki/Android_How-tos#KERNEL_CONFIG
http://omappedia.org/wiki/Android_How-tos#KERNEL_CONFIG

Hi trevd!
For the surfaceflinger thing, you must implement the changes I made in the board specific files.
Just have a look at the end of the file, there should be a struct which contains a function pointer to a reserve function.
I have changed this reference to a board specific function, which also initializes the graphic subsystem.
If it suceed, you should get the framebuffer special files which are provided by the omapfb driver.
For the twl charger logic, I have no clue why it doesn't work. Does it work with the kernel which I have uploaded to 4shared?

Quallenauge said:
Hi trevd!
For the surfaceflinger thing, you must implement the changes I made in the board specific files.
Just have a look at the end of the file, there should be a struct which contains a function pointer to a reserve function.
I have changed this reference to a board specific function, which also initializes the graphic subsystem.
If it suceed, you should get the framebuffer special files which are provided by the omapfb driver.
For the twl charger logic, I have no clue why it doesn't work. Does it work with the kernel which I have uploaded to 4shared?
Click to expand...
Click to collapse
Thanks Quallenauge, Is that board specific file in arch/arm or do they live in some like drivers/video/omapfb ( i'll have a look around anyway and can't remember exact paths off the top of my head ) . For twl , I was using your kernel from 4shared... I'm not too bothered though as I think it's more in the watching daemon and I turned that off in the init.archos.rc. I still get battery change reports reported by my hotplug kernel monitor, which although not written for the purpose has become very useful.

trevd said:
Thanks Quallenauge, Is that board specific file in arch/arm or do they live in some like drivers/video/omapfb ( i'll have a look around anyway and can't remember exact paths off the top of my head ) .
Click to expand...
Click to collapse
It is in arch/arm/... board.*.80S.c file.

progress at Archos...
Hi!
Quallenauge said:
It is in arch/arm/... board.*.80S.c file.
Click to expand...
Click to collapse
Great work so far... so i'm back from holiday.
Seen this already:
https://gitorious.org/archos/archos-gpl-gen9-kernel-ics/trees/linux-ics-3.0.21
It's not 3.0.31 but intersting that G10 upgrades hit the G9 as well :laugh:
EDIT:
Just had a look inside the new "unofficial" firmware file which leaked at archos...
Guess what... included are latest graphics driver [email protected]
Should play nice with JB
Cheers,
scholbert

Hi Folks
I've just given my self a lesson in board bring up on omap arm devices and I'm making progress with the A101S board.
It creates the framebuffer in /dev/graphics/ and shows the boot animation although i've still got an issue with surfaceflinger and gralloc and framebuffer not being typewriter when I try to use the pvr drivers. I presume it something to do with the issue below which happens pretty early in the boot.
Code:
omapfb_calc_addr:892
Backtrace:
[<c008690c>] (dump_backtrace+0x0/0x138) from [<c0650164>] (dump_stack+0x20/0x24)
r7:c0a4f764 r6:d9b9a000 r5:00000000 r4:d931ce90
[<c0650144>] (dump_stack+0x0/0x24) from [<c0322e6c>] (omapfb_setup_overlay+0x158/0x4b8)
[<c0322d14>] (omapfb_setup_overlay+0x0/0x4b8) from [<c03236a0>] (omapfb_apply_changes+0x4d4/0x5c8)
[<c03231cc>] (omapfb_apply_changes+0x0/0x5c8) from [<c03240f4>] (omapfb_probe+0x960/0xda0)
[<c0323794>] (omapfb_probe+0x0/0xda0) from [<c03624f8>] (platform_drv_probe+0x24/0x28)
[<c03624d4>] (platform_drv_probe+0x0/0x28) from [<c0360f00>] (driver_probe_device+0xdc/0x1c8)
[<c0360e24>] (driver_probe_device+0x0/0x1c8) from [<c0361064>] (__driver_attach+0x78/0x9c)
r6:c087e350 r5:c0872d9c r4:c0872d68 r3:00000000
[<c0360fec>] (__driver_attach+0x0/0x9c) from [<c035fb5c>] (bus_for_each_dev+0x58/0xa0)
r6:c0360fec r5:c087e350 r4:00000000 r3:00000000
[<c035fb04>] (bus_for_each_dev+0x0/0xa0) from [<c0360b14>] (driver_attach+0x2c/0x34)
r6:c0880748 r5:d928d0c0 r4:c087e350
[<c0360ae8>] (driver_attach+0x0/0x34) from [<c0360698>] (bus_add_driver+0x138/0x2d8)
[<c0360560>] (bus_add_driver+0x0/0x2d8) from [<c03616cc>] (driver_register+0xd4/0x160)
[<c03615f8>] (driver_register+0x0/0x160) from [<c03629a0>] (platform_driver_register+0x80/0x9c)
[<c0362920>] (platform_driver_register+0x0/0x9c) from [<c0032644>] (omapfb_init+0x40/0x70)
r5:c004d778 r4:c004d7b0
[<c0032604>] (omapfb_init+0x0/0x70) from [<c007c768>] (do_one_initcall+0xb4/0x1b0)
[<c007c6b4>] (do_one_initcall+0x0/0x1b0) from [<c0008b64>] (kernel_init+0xb0/0x16c)
[<c0008ab4>] (kernel_init+0x0/0x16c) from [<c00d99a8>] (do_exit+0x0/0x6fc)
r6:c00d99a8 r5:c0008ab4 r4:00000000 r3:00000000
data_start_v=0xe2000000
rotation_type=0
cannot apply mgr(lcd) on inactive device
omapfb omapfb: failed to apply dispc config
cannot apply mgr(tv) on inactive device
omapfb omapfb: failed to apply dispc config
cannot apply mgr(lcd2) on inactive device
omapfb omapfb: failed to apply dispc config
omapdss DPI: Could not find exact pixel clock. Requested 68930 kHz, got 68929 kHz
panel_enable [wxga10]
I've got myself a Linaro JellyBean to boot all the way on the new kernel as that allows you to disable hardware rendering on the launcher
scholbert said:
It's not 3.0.31 but intersting that G10 upgrades hit the G9 as well
EDIT:
Just had a look inside the new "unofficial" firmware file which leaked at archos...
Guess what... included are latest graphics driver [email protected]
Should play nice with JB
Cheers,
scholbert
Click to expand...
Click to collapse
I'm just having a look at that firmware myself, some very interesting changes...... /system/lib/modules contains the pvrsrvkm_sgx540_120.ko and omaplfb_sgx540_120.ko, I'm just going to play around with some jellybean builds and see if I can get the drivers playing ball.
I assume if archos have created a new kernel in preparation for a JellyBean Rom on either the G10 or G9 then that would make this work kind of redundant for now?

trevd said:
I've got myself a Linaro JellyBean to boot all the way on the new kernel as that allows you to disable hardware rendering on the launcher
Click to expand...
Click to collapse
Great work... so you took the Pandaboard files or built your own?
trevd said:
I'm just having a look at that firmware myself, some very interesting changes...... /system/lib/modules contains the pvrsrvkm_sgx540_120.ko and omaplfb_sgx540_120.ko, I'm just going to play around with some jellybean builds and see if I can get the drivers playing ball.
Click to expand...
Click to collapse
Yeah i also wondered about that.
If you look at the 3.0.21 the known pvr part is missing now.
Guess the whole graphics stuff is changing for new releases, but i'm not a Ducati specialist
trevd said:
I assume if archos have created a new kernel in preparation for a JellyBean Rom on either the G10 or G9 then that would make this work kind of redundant for now?
Click to expand...
Click to collapse
Might get redundant, but don't forget the education :laugh:
Anyway you always give nice information to the community!
Keep on your great work.
Cheers,
scholbert

scholbert said:
Great work... so you took the Pandaboard files or built your own?
Click to expand...
Click to collapse
I acquired this book [ Embedded Android ] and decided to started from scratch, I've been using the Blaze and Panda as references.
I've made some major changes to the archos firmware/images which I will document very soon for everyone as I think we can bring the Archos Roms into line with the rest of Android.
scholbert said:
Yeah i also wondered about that.
If you look at the 3.0.21 the known pvr part is missing now.
Guess the whole graphics stuff is changing for new releases, but i'm not a Ducati specialist
Click to expand...
Click to collapse
I built myself a 3.0.21 kernel this morning and created myself a 4.0.24 rooted firmware ( I presume this number is related to the Gen10 ). The pvr/omaplfb kernel objects do get installed on boot although I still have not located exactly where that is happening. I'm still a little confused by how all this graphics stuff fits together and I seem to be going round in a segfault circle when trying to use the 3.0.21 drivers on a JellyBean Rom. I probably just need to add more method to my madness as I'm probably just repeating things I've already attempted.
I think I may go back to working on the 3.0.31 kernel if I don't make any headway
@Quallenauge : Have you got pvr drivers working on your 3.0.31 Kernel? What Is the "Secret Sauce" I need to Add?
scholbert said:
Might get redundant, but don't forget the education :laugh:
Click to expand...
Click to collapse
It's certainly an education and I think this is worth carrying on with as It it means we can keep the device up to date long after archos has stopped supporting it.
scholbert said:
Anyway you always give nice information to the community!
Keep on your great work.
Click to expand...
Click to collapse
And yourself, Although much of the H/W stuff is over my head at the moment, I'll understand one day :laugh:
Slightly off topic, I was wondering if you had looked into extracting the public keys from Gen10 F/W , It was something I made a naive attempt to do but I got lost in a sea of Hex! :silly:

trevd said:
I acquired this book [ Embedded Android ] and decided to started from scratch, I've been using the Blaze and Panda as references.
I've made some major changes to the archos firmware/images which I will document very soon for everyone as I think we can bring the Archos Roms into line with the rest of Android.
Click to expand...
Click to collapse
Cool, that's great... that's the way i like.
Interesting book as well. Few year ago i purchased "building embedded linux systems" from O'Reilly.
Good basics here, but little old skool in the meantime :angel:
Back on track... started digging around in the project files of the more open platforms in the meantime,
but unfortunately time is lacking to produce some useful output. So it's great you do!!!
trevd said:
I built myself a 3.0.21 kernel this morning and created myself a 4.0.24 rooted firmware ( I presume this number is related to the Gen10 ). The pvr/omaplfb kernel objects do get installed on boot although I still have not located exactly where that is happening. I'm still a little confused by how all this graphics stuff fits together and I seem to be going round in a segfault circle when trying to use the 3.0.21 drivers on a JellyBean Rom. I probably just need to add more method to my madness as I'm probably just repeating things I've already attempted.
Click to expand...
Click to collapse
I must admit, i got no clue right now...
trevd said:
I think I may go back to working on the 3.0.31 kernel if I don't make any headway
Click to expand...
Click to collapse
Always follow the path of least resistance
... at least first.
trevd said:
It's certainly an education and I think this is worth carrying on with as It it means we can keep the device up to date long after archos has stopped supporting it.
Click to expand...
Click to collapse
That'll be really great achievement.
trevd said:
And yourself, Although much of the H/W stuff is over my head at the moment, I'll understand one day :laugh:
Click to expand...
Click to collapse
Thanks alot... but no active hacks for some time now :highfive:
trevd said:
Slightly off topic, I was wondering if you had looked into extracting the public keys from Gen10 F/W , It was something I made a naive attempt to do but I got lost in a sea of Hex! :silly:
Click to expand...
Click to collapse
I would extract them, but in fact i'll need a dump of the first blocks of a Gen10 device. Maybe we should ask cajl for help...
You can't extract the keys from the firmware file because you'll need the key first to extract the bootloader out of the firmware file
We need to dd if=/dev/block/mmcblk0 of=/mnt/sdcard/first-64k.bin bs=512 count=128 or similar from a real device...
Best regards,
scholbert