Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 20 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 5 hrs ago - more...
|
2011-07-21
, 17:00
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#92
|
Originally Posted by jvollmann
Okay, then I am remembering correctly - it was saying USER with normal getbootstate, and is saying SHUTDOWN with pali's getbootstate. (I haven't tested Estel-modified getbootstate though.)
When I couldn't boot in normal mode with closed source binary, the getbootstate log showed up that warning (Entering state: SHUTDOWN).
In R&D mode first boot showed: Entering state: ACT DEAD
Now, with Pali's getbootstate modification, I don't get "SHUTDOWN" warning but only "Entering state: USER"
What's odd is that it still boots for me even though it says "Entering state: SHUTDOWN"
| The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
|
|
2011-07-22
, 13:47
|
|
Posts: 63 |
Thanked: 27 times |
Joined on Jul 2011
@ Venezuela
|
#93
|
Mentalist: It's weird that you get the SHUTDOWN warning but the device starts up... Don't know what could be happening there..
--------------
I don't know this is normal and/or it could be cause of problems:
Every time I take the battery out from the device and then start it up, it asks me to enter date and time configuration. Doesn't the n900 has an internal battery to save this configuration?
The boot log shows some lines with warnings about clock (I will try to be more specific about those warnings and try to post them later).
Last edited by jvollmann; 2011-07-22 at 14:05.
--------------
I don't know this is normal and/or it could be cause of problems:
Every time I take the battery out from the device and then start it up, it asks me to enter date and time configuration. Doesn't the n900 has an internal battery to save this configuration?
The boot log shows some lines with warnings about clock (I will try to be more specific about those warnings and try to post them later).
Last edited by jvollmann; 2011-07-22 at 14:05.
 |
|
2011-07-23
, 01:27
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#94
|
[QUOTE=jvollmann;1056156]
Every time I take the battery out from the device and then start it up, it asks me to enter date and time configuration. Doesn't the n900 has an internal battery to save this configuration?
/QUOTE]
This is perfectly normal. If you unplug battery for short time (~5 seconds max) time and date will remain intact. Otherwise, it reset. Ho ever, if You have "auto update time and date" checked and SIM card inserted, + You unlock PIN on turning on, date and time will be automatically set correctly, yet still you'll see enter time/date prompt (with correct date in it already present).
So, it have nothing to do with Your problem. ho ever, warnings about date and time *may* be interesting (most unlikely, but better safe than sorry), so of course post it here.
---
Still, I think You got charging chip damaged. Probably, most convenient way for You is to mod Your cover (or buy mugen cover and mod it) to contain charging port, + buy cheap small Li-Ion charger (most likely, for small AA-like cells) and mod it to have cable fitting into Your cover new plug. Then, of course, You also need to mod battery a little and connect it with plug inside Your cover
This way, you can screw bme readings totally (AFAIU, despite low battery warnings, You can use Your device until battery is empty, right?), charge your battery "as normal" using modified charging system - even with device ON (ho ever, I would not charge it to absolutely 100%, due to device sucking power for operation, that may confuse charger - no big deal, N900 internal charger is also confused by it, anyway just not so-healthy for batteries), so you *almost* don't feel downsides of Your problem.
By the way, You may almost "kill two deer by one spear" and make yourself nice dual-scud mod, aka 3000 mAh battery (or much cheaper 2500 mAh alternative). Check my signature for appropriate thread.
---
By the way, writing this reminded me about some thing. IF Your bme isn't working correctly, how device know when to shut down? It shut down properly (bright white diode fading etc, @ little less than 3200 mV), or is it used to ~2800 mV and just die due to low power?
Every time I take the battery out from the device and then start it up, it asks me to enter date and time configuration. Doesn't the n900 has an internal battery to save this configuration?
/QUOTE]
This is perfectly normal. If you unplug battery for short time (~5 seconds max) time and date will remain intact. Otherwise, it reset. Ho ever, if You have "auto update time and date" checked and SIM card inserted, + You unlock PIN on turning on, date and time will be automatically set correctly, yet still you'll see enter time/date prompt (with correct date in it already present).
So, it have nothing to do with Your problem. ho ever, warnings about date and time *may* be interesting (most unlikely, but better safe than sorry), so of course post it here.
---
Still, I think You got charging chip damaged. Probably, most convenient way for You is to mod Your cover (or buy mugen cover and mod it) to contain charging port, + buy cheap small Li-Ion charger (most likely, for small AA-like cells) and mod it to have cable fitting into Your cover new plug. Then, of course, You also need to mod battery a little and connect it with plug inside Your cover
This way, you can screw bme readings totally (AFAIU, despite low battery warnings, You can use Your device until battery is empty, right?), charge your battery "as normal" using modified charging system - even with device ON (ho ever, I would not charge it to absolutely 100%, due to device sucking power for operation, that may confuse charger - no big deal, N900 internal charger is also confused by it, anyway
just not so-healthy for batteries), so you *almost* don't feel downsides of Your problem.By the way, You may almost "kill two deer by one spear" and make yourself nice dual-scud mod, aka 3000 mAh battery (or much cheaper 2500 mAh alternative). Check my signature for appropriate thread.
---
By the way, writing this reminded me about some thing. IF Your bme isn't working correctly, how device know when to shut down? It shut down properly (bright white diode fading etc, @ little less than 3200 mV), or is it used to ~2800 mV and just die due to low power?
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
| The Following User Says Thank You to Estel For This Useful Post: | ||
|
|
2011-07-23
, 03:27
|
|
Posts: 63 |
Thanked: 27 times |
Joined on Jul 2011
@ Venezuela
|
#95
|
Originally Posted by Estel
I installed power kernel 47 but I haven't found framebuffer/log for this version. Anyone knows how to activate/install framebuffer on power kernel?
So, it have nothing to do with Your problem. ho ever, warnings about date and time *may* be interesting (most unlikely, but better safe than sorry), so of course post it here.
Originally Posted by Estel
If everything fails I will try that!
Still, I think You got charging chip damaged. Probably, most convenient way for You is to mod Your cover (or buy mugen cover and mod it) to contain charging port, + buy cheap small Li-Ion charger (most likely, for small AA-like cells) and mod it to have cable fitting into Your cover new plug...
Originally Posted by Estel
I attached an image of BatteryGraph wich shows that it measures volts right. When I connect charger while running BatteryGraph, it doesn't change any info about "charge" value, it stays the same...
By the way, writing this reminded me about some thing. IF Your bme isn't working correctly, how device know when to shut down? It shut down properly (bright white diode fading etc, @ little less than 3200 mV), or is it used to ~2800 mV and just die due to low power?
| The Following User Says Thank You to jvollmann For This Useful Post: | ||
|
|
2011-07-23
, 03:32
|
|
Posts: 63 |
Thanked: 27 times |
Joined on Jul 2011
@ Venezuela
|
#96
|
Originally Posted by Estel
Yes, that's right.. As soon as the device starts up, the battery life keeps low and some minutes later shows "low battery" warning. However, I can use the phone as usual
This way, you can screw bme readings totally (AFAIU, despite low battery warnings, You can use Your device until battery is empty, right?)....
|
|
2011-07-23
, 04:02
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#97
|
Just FYI, N900's internal battery that preserves time settings gets weaker as time goes on. So while it SHOULD hold enough charge to be certain of correct date, it starts prompting you for date/time confirmation a lot sooner if you compare brand new N900 to an N900 used for a year or two. It does seem to keep the time accurately for a while though, as it takes a while for it to reset the date - usually on my device it prompts you even after a quick pull-in-out of battery, but time and date is the same as it should be if the battery wasn't out for long.
Framebuffer on kernel power v47 (and v48) is enabled by "modprobe fbcon". I personally have it inserted at the (almost) very beginning of /sbin/preinit - I have it inserted after line 28 in that file. Gets framebuffer module loaded early enough to see the getbootstate stuff.
Framebuffer on kernel power v47 (and v48) is enabled by "modprobe fbcon". I personally have it inserted at the (almost) very beginning of /sbin/preinit - I have it inserted after line 28 in that file. Gets framebuffer module loaded early enough to see the getbootstate stuff.
|
|
2011-07-23
, 17:22
|
|
Posts: 63 |
Thanked: 27 times |
Joined on Jul 2011
@ Venezuela
|
#98
|
Thanks to mentalist I could enable framebuffer, these are the lines that showed errors or warnings during boot up (using Estel's getbootstate):
Last edited by jvollmann; 2011-07-23 at 20:02.
Code:
Disabling unused clock "dpll3_m3x2_ck" Disabling unused clock "sys_clckout1" . . . UBIFS: Recovery needed UBIFS: Recovery completed . . . getbootstate: Could not open /dev/twl4030-adc - No suh file or directory . . . radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00-00 Component: 3.0 Chip Rev: unknown . . . smc91x: Component not found (-19) mnci -omap-hs mnci -omap-hs-0: Failed to get debounce clock mnci -omap-hs mnci -omap-hs-1: Failed to get debounce clock . . . waitfordsme: Wait for DSME socket waitfordsme: ERROR: Timeout waiting for DSME socket About to exec dsme in state 'USER' DSME 0.60.48 starting up
Last edited by jvollmann; 2011-07-23 at 20:02.
| The Following 2 Users Say Thank You to jvollmann For This Useful Post: | ||
|
|
2011-07-25
, 02:34
|
|
Posts: 63 |
Thanked: 27 times |
Joined on Jul 2011
@ Venezuela
|
#99
|
I'm attaching the whole boot log...
By the way: I noticed that when the device is turned off and I connect usb cable, getbootstate shows ACT DEAD.. a little later says ACT DEAD: charger (off?)....
Don't know if that's normal output
Last edited by jvollmann; 2011-07-25 at 02:40.
By the way: I noticed that when the device is turned off and I connect usb cable, getbootstate shows ACT DEAD.. a little later says ACT DEAD: charger (off?)....
Don't know if that's normal output
Last edited by jvollmann; 2011-07-25 at 02:40.
 |
|
2011-07-25
, 23:18
|
|
Posts: 35 |
Thanked: 2 times |
Joined on Jul 2010
@ lagos, Nigeria
|
#100
|
hello, can anyone help pls.
i'm having battery issues, rapid drain, reboot loops. i dont exactly know what is wrong. i run dmesg and below is what i got.
can someone pls have a look at it for me pls? the charger/or usb is not connected when i ran this. thanks.
/root$ dmesg
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.28.10-power47 (builder1@wml0226) (gcc version 4.2.1) #1 PREEMPT Tue May 3 20:40:52 EEST 2011
[ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Nokia RX-51 board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 65536
[ 0.000000] free_area_init_node: node 0, pgdat c039864c, node_mem_map c03da000
[ 0.000000] Normal zone: 512 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 65024 pages, LIFO batch:15
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] OMAP3430 ES3.1
[ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
[ 0.000000] VRAM: 5357568 bytes at 0x8f578000. (Detected 868352 at 0x8f9c0000)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: init=/sbin/preinit ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc rw console=ttyMTD,log console=tty0 snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6
[ 0.000000] Clocking rate (Crystal/DPLL/ARM core): 19.2/332/500 MHz
[ 0.000000] Reprogramming SDRC
[ 0.000000] GPMC revision 5.0
[ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
[ 0.000000] Total of 96 interrupts on 1 active controller
[ 0.000000] OMAP34xx GPIO hardware version 2.5
[ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty0] enabled
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] allocated 1310720 bytes of page_cgroup
[ 0.000000] please try cgroup_disable=memory option if you don't want
[ 0.000000] Memory: 128MB 128MB = 256MB total
[ 0.000000] Memory: 244924KB available (3312K code, 445K data, 144K init)
[ 0.000000] SLUB: Genslabs=8, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
[ 0.000000] Security Framework initialized
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] Initializing cgroup subsys memory
[ 0.000000] Initializing cgroup subsys freezer
[ 0.000000] CPU: Testing write buffer coherency: ok
[ 0.000000] net_namespace: 740 bytes
[ 0.000000] regulator: core version 0.5
[ 0.000000] NET: Registered protocol family 16
[ 2.420715] OMAP DMA hardware revision 4.0
[ 2.420837] Reserving DMA channels 0 and 1 for HS ROM code
[ 2.421936] MUX: setup J21_34XX_I2C1_SDA (0xd80021bc): 0x0100 -> 0x0118
[ 2.421997] MUX: setup K21_34XX_I2C1_SCL (0xd80021ba): 0x0100 -> 0x0118
[ 2.422119] MUX: setup AE15_34XX_I2C2_SDA (0xd80021c0): 0x0100 -> 0x0118
[ 2.422180] MUX: setup AF15_34XX_I2C2_SCL (0xd80021be): 0x0100 -> 0x0118
[ 2.422302] MUX: setup AG14_34XX_I2C3_SDA (0xd80021c4): 0x0100 -> 0x0118
[ 2.422363] MUX: setup AF14_34XX_I2C3_SCL (0xd80021c2): 0x0100 -> 0x0118
[ 2.422821] USB: No board-specific platform config found
[ 2.425872] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2200 kHz
[ 2.427276] TWL5030: Enabling workaround for rev 0x1009002F
[ 2.444824] twl4030: PIH (irq 7) chaining IRQs 368..375
[ 2.444885] twl4030: power (irq 373) chaining IRQs 376..383
[ 2.445190] twl4030: gpio (irq 368) chaining IRQs 384..401
[ 2.446319] regulator: VDAC: 1800 mV normal standby
[ 2.446685] regulator: VUSB1V5: 1500 mV normal standby
[ 2.447021] regulator: VUSB1V8: 1800 mV normal standby
[ 2.447357] regulator: VUSB3V1: 3100 mV normal standby
[ 2.447692] i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz
[ 2.448669] i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
[ 2.450225] console [ttyMTD0] enabled
[ 2.453918] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[ 2.453918] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
[ 2.454437] usbcore: registered new interface driver usbfs
[ 2.454620] usbcore: registered new interface driver hub
[ 2.454925] usbcore: registered new device driver usb
[ 2.454956] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
[ 2.458190] HS USB OTG: revision 0x33, sysconfig 0x2010, sysstatus 0x1, intrfsel 0x1, simenable 0x0
[ 2.458251] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine (X), bulk split (X), HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 2.458282] musb_hdrc: MHDRC RTL version 1.400
[ 2.458282] musb_hdrc: setup fifo_mode 5
[ 2.458312] musb_hdrc: 21/31 max ep, 9312/16384 memory
[ 2.458343] musb_hdrc: hw_ep 0shared, max 64
[ 2.458343] musb_hdrc: hw_ep 1tx, max 512
[ 2.458374] musb_hdrc: hw_ep 1rx, max 512
[ 2.458374] musb_hdrc: hw_ep 2tx, max 512
[ 2.458374] musb_hdrc: hw_ep 2rx, max 512
[ 2.458404] musb_hdrc: hw_ep 3tx, max 512
[ 2.458404] musb_hdrc: hw_ep 3rx, max 512
[ 2.458435] musb_hdrc: hw_ep 4tx, max 512
[ 2.458435] musb_hdrc: hw_ep 4rx, max 512
[ 2.458465] musb_hdrc: hw_ep 5tx, max 16
[ 2.458465] musb_hdrc: hw_ep 5rx, max 512
[ 2.458465] musb_hdrc: hw_ep 6tx, max 512
[ 2.458496] musb_hdrc: hw_ep 6rx, max 512
[ 2.458496] musb_hdrc: hw_ep 7tx, max 16
[ 2.458526] musb_hdrc: hw_ep 7rx, max 512
[ 2.458526] musb_hdrc: hw_ep 8tx, max 512
[ 2.458526] musb_hdrc: hw_ep 8rx, max 512
[ 2.458557] musb_hdrc: hw_ep 9tx, max 512
[ 2.458557] musb_hdrc: hw_ep 9rx, max 512
[ 2.458587] musb_hdrc: hw_ep 10tx, max 512
[ 2.458587] musb_hdrc: hw_ep 11tx, max 512
[ 2.458618] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
[ 2.458801] Registered /proc/driver/musb_hdrc
[ 2.483673] NET: Registered protocol family 2
[ 2.490356] Switched to high resolution mode on CPU 0
[ 2.552978] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 2.553344] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 2.553649] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 2.553863] TCP: Hash tables configured (established 8192 bind 8192)
[ 2.553894] TCP reno registered
[ 2.576446] NET: Registered protocol family 1
[ 2.597930] VFS: Disk quotas dquot_6.5.1
[ 2.598083] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.599578] msgmni has been set to 479
[ 2.600250] lowmem: Module initialized.
[ 2.608764] alg: No test for lzo999 (lzo999-generic)
[ 2.609039] alg: No test for stdrng (krng)
[ 2.609161] io scheduler noop registered
[ 2.609558] io scheduler cfq registered (default)
[ 2.609954] OMAP DSS rev 2.0
[ 2.610076] OMAP DISPC rev 3.0
[ 2.610168] OMAP VENC rev 2
[ 2.618011] OMAP3 ROM RNG: initializing
[ 2.620208] Serial: 8250/16550 driver4 ports, IRQ sharing disabled
[ 2.626739] brd: module loaded
[ 2.629089] loop: module loaded
[ 2.629180] i2c /dev entries driver
[ 2.630340] input: triton2-pwrbutton as /class/input/input0
[ 2.654449] triton2 power button driver initialized
[ 2.655059] OneNAND driver initializing
[ 2.656280] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000
[ 2.656372] OneNAND Manufacturer: Samsung (0xec)
[ 2.656402] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
[ 2.656433] OneNAND version = 0x0121
[ 2.656463] Chip support all block unlock
[ 2.656463] Chip has 2 plane
[ 2.657989] Scanning device for bad blocks
[ 2.684814] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.684875] Bad eraseblock 470 at 0x03ac0000
[ 2.723358] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.723419] Bad eraseblock 1148 at 0x08f80000
[ 2.774505] Creating 6 MTD partitions on "omap2-onenand":
[ 2.774536] 0x00000000-0x00020000 : "bootloader"
[ 2.774932] 0x00020000-0x00080000 : "config"
[ 2.775177] 0x00080000-0x000c0000 : "log"
[ 2.777648] mtdoops: Ready 26, 27 (no erase)
[ 2.777679] mtdoops: Attached to MTD device 2
[ 2.777709] 0x000c0000-0x002c0000 : "kernel"
[ 2.777984] 0x002c0000-0x004c0000 : "initfs"
[ 2.778228] 0x004c0000-0x10000000 : "rootfs"
[ 2.780090] UBI: attaching mtd5 to ubi0
[ 2.780120] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 2.780181] UBI: logical eraseblock size: 129024 bytes
[ 2.780212] UBI: smallest flash I/O unit: 2048
[ 2.780242] UBI: sub-page size: 512
[ 2.780273] UBI: VID header offset: 512 (aligned 512)
[ 2.780303] UBI: data offset: 2048
[ 2.913513] UBI: attached mtd5 to ubi0
[ 2.913574] UBI: MTD device name: "rootfs"
[ 2.913635] UBI: MTD device size: 251 MiB
[ 2.913665] UBI: number of good PEBs: 2008
[ 2.913696] UBI: number of bad PEBs: 2
[ 2.913696] UBI: max. allowed volumes: 128
[ 2.913726] UBI: wear-leveling threshold: 4096
[ 2.913757] UBI: number of internal volumes: 1
[ 2.913787] UBI: number of user volumes: 1
[ 2.913818] UBI: available PEBs: 0
[ 2.913848] UBI: total number of reserved PEBs: 2008
[ 2.913879] UBI: number of PEBs reserved for bad PEB handling: 20
[ 2.913909] UBI: max/mean erase counter: 1790/319
[ 2.913940] UBI: image sequence number: 35
[ 2.914367] usbcore: registered new interface driver libusual
[ 2.914489] UBI: background thread "ubi_bgt0d" started, PID 26
[ 2.936248] input: omap_twl4030keypad as /class/input/input1
[ 2.984863] cpuidle: using governor ladder
[ 2.984924] cpuidle: using governor menu
[ 2.985107] Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
[ 2.985351] ASoC version 0.13.2
[ 2.998901] AIC3X Audio Codec 0.2
[ 3.001464] asoc: tlv320aic3x <-> omap-mcbsp-dai-0 mapping ok
[ 3.002960] asoc: Bluetooth codec <-> omap-mcbsp-dai-1 mapping ok
[ 3.054534] input: RX51 (tlv320aic3x) Jack as /class/input/input2
[ 3.078887] ALSA device list:
[ 3.078918] #0: RX51 (tlv320aic3x)
[ 3.079162] TCP cubic registered
[ 3.079193] Initializing XFRM netlink socket
[ 3.079284] NET: Registered protocol family 17
[ 3.079345] NET: Registered protocol family 15
[ 3.079376] ThumbEE CPU extension supported.
[ 3.079437] Power Management for TI OMAP3.
[ 3.082824] pm_dbg_init()
[ 3.083618] SmartReflex driver initialized
[ 3.089782] Disabling unused clock "gpt2_ick"
[ 3.089874] Disabling unused clock "gpt3_ick"
[ 3.089904] Disabling unused clock "gpt4_ick"
[ 3.089965] Disabling unused clock "gpt5_ick"
[ 3.089996] Disabling unused clock "gpt6_ick"
[ 3.090026] Disabling unused clock "gpt7_ick"
[ 3.090057] Disabling unused clock "gpt8_ick"
[ 3.090087] Disabling unused clock "gpt9_ick"
[ 3.090118] Disabling unused clock "uart3_ick"
[ 3.090148] Disabling unused clock "gpio2_dbck"
[ 3.090209] Disabling unused clock "gpio3_dbck"
[ 3.090240] Disabling unused clock "gpio4_dbck"
[ 3.090270] Disabling unused clock "gpio5_dbck"
[ 3.090301] Disabling unused clock "gpio6_dbck"
[ 3.090332] Disabling unused clock "gpt9_fck"
[ 3.090362] Disabling unused clock "gpt8_fck"
[ 3.090393] Disabling unused clock "gpt7_fck"
[ 3.090454] Disabling unused clock "gpt6_fck"
[ 3.090484] Disabling unused clock "gpt5_fck"
[ 3.090515] Disabling unused clock "gpt4_fck"
[ 3.090545] Disabling unused clock "gpt3_fck"
[ 3.090576] Disabling unused clock "gpt2_fck"
[ 3.090606] Disabling unused clock "uart3_fck"
[ 3.090667] Disabling unused clock "wdt2_ick"
[ 3.090698] Disabling unused clock "wdt2_fck"
[ 3.090728] Disabling unused clock "gpio1_dbck"
[ 3.090759] Disabling unused clock "rng_ick"
[ 3.090820] Disabling unused clock "ssi_ick"
[ 3.090850] Disabling unused clock "gpt10_ick"
[ 3.090881] Disabling unused clock "gpt11_ick"
[ 3.090911] Disabling unused clock "uart1_ick"
[ 3.090942] Disabling unused clock "uart2_ick"
[ 3.091003] Disabling unused clock "usbtll_ick"
[ 3.091033] Disabling unused clock "ssi_ssr_fck"
[ 3.091064] Disabling unused clock "uart1_fck"
[ 3.091125] Disabling unused clock "uart2_fck"
[ 3.091156] Disabling unused clock "usbtll_fck"
[ 3.091217] Disabling unused clock "ts_fck"
[ 3.091247] Disabling unused clock "cpefuse_fck"
[ 3.091278] Disabling unused clock "gpt11_fck"
[ 3.091308] Disabling unused clock "gpt10_fck"
[ 3.091369] Disabling unused clock "dpll5_ck"
[ 3.091430] Disabling unused clock "dpll4_m6x2_ck"
[ 3.091461] Disabling unused clock "dpll4_m5x2_ck"
[ 3.091522] Disabling unused clock "dpll3_m3x2_ck"
[ 3.091552] Disabling unused clock "sys_clkout1"
[ 3.091979] Bootup reason: pwr_key
[ 3.092071] OMAP GPIO switch handler initializing
[ 3.094635] slide (GPIO 71) is now closed
[ 3.094696] proximity (GPIO 89) is now open
[ 3.094726] kb_lock (GPIO 113) is now open
[ 3.094757] headphone (GPIO 177) is now disconnected
[ 3.094787] cam_shutter (GPIO 110) is now closed
[ 3.094818] cam_launch (GPIO 69) is now inactive
[ 3.094848] cam_focus (GPIO 68) is now inactive
[ 3.094879] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[ 3.095489] registered taskstats version 1
[ 3.115600] omapfb: acx565akm rev 8d LCD detected
[ 3.147644] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[ 3.167907] UBIFS: recovery needed
[ 3.211578] UBIFS: recovery completed
[ 3.211639] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.211700] UBIFS: file system size: 254564352 bytes (248598 KiB, 242 MiB, 1973 LEBs)
[ 3.211730] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 3.211791] UBIFS: media format: 4 (latest is 4)
[ 3.211822] UBIFS: default compressor: lzo
[ 3.211853] UBIFS: reserved for root: 4384586 bytes (4281 KiB)
[ 3.212249] VFS: Mounted root (ubifs filesystem).
[ 3.212432] Freeing init memory: 144K
[ 5.772033] Registered led device: twl4030:vibrator
[ 5.789062] tsl2563 2-0029: model 7, rev. 0
[ 5.984741] twl4030_rtc twl4030_rtc: rtc core: registered
i'm having battery issues, rapid drain, reboot loops. i dont exactly know what is wrong. i run dmesg and below is what i got.
can someone pls have a look at it for me pls? the charger/or usb is not connected when i ran this. thanks.
/root$ dmesg
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.28.10-power47 (builder1@wml0226) (gcc version 4.2.1) #1 PREEMPT Tue May 3 20:40:52 EEST 2011
[ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Nokia RX-51 board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 65536
[ 0.000000] free_area_init_node: node 0, pgdat c039864c, node_mem_map c03da000
[ 0.000000] Normal zone: 512 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 65024 pages, LIFO batch:15
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] OMAP3430 ES3.1
[ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
[ 0.000000] VRAM: 5357568 bytes at 0x8f578000. (Detected 868352 at 0x8f9c0000)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: init=/sbin/preinit ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc rw console=ttyMTD,log console=tty0 snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6
[ 0.000000] Clocking rate (Crystal/DPLL/ARM core): 19.2/332/500 MHz
[ 0.000000] Reprogramming SDRC
[ 0.000000] GPMC revision 5.0
[ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
[ 0.000000] Total of 96 interrupts on 1 active controller
[ 0.000000] OMAP34xx GPIO hardware version 2.5
[ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty0] enabled
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] allocated 1310720 bytes of page_cgroup
[ 0.000000] please try cgroup_disable=memory option if you don't want
[ 0.000000] Memory: 128MB 128MB = 256MB total
[ 0.000000] Memory: 244924KB available (3312K code, 445K data, 144K init)
[ 0.000000] SLUB: Genslabs=8, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
[ 0.000000] Security Framework initialized
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] Initializing cgroup subsys memory
[ 0.000000] Initializing cgroup subsys freezer
[ 0.000000] CPU: Testing write buffer coherency: ok
[ 0.000000] net_namespace: 740 bytes
[ 0.000000] regulator: core version 0.5
[ 0.000000] NET: Registered protocol family 16
[ 2.420715] OMAP DMA hardware revision 4.0
[ 2.420837] Reserving DMA channels 0 and 1 for HS ROM code
[ 2.421936] MUX: setup J21_34XX_I2C1_SDA (0xd80021bc): 0x0100 -> 0x0118
[ 2.421997] MUX: setup K21_34XX_I2C1_SCL (0xd80021ba): 0x0100 -> 0x0118
[ 2.422119] MUX: setup AE15_34XX_I2C2_SDA (0xd80021c0): 0x0100 -> 0x0118
[ 2.422180] MUX: setup AF15_34XX_I2C2_SCL (0xd80021be): 0x0100 -> 0x0118
[ 2.422302] MUX: setup AG14_34XX_I2C3_SDA (0xd80021c4): 0x0100 -> 0x0118
[ 2.422363] MUX: setup AF14_34XX_I2C3_SCL (0xd80021c2): 0x0100 -> 0x0118
[ 2.422821] USB: No board-specific platform config found
[ 2.425872] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2200 kHz
[ 2.427276] TWL5030: Enabling workaround for rev 0x1009002F
[ 2.444824] twl4030: PIH (irq 7) chaining IRQs 368..375
[ 2.444885] twl4030: power (irq 373) chaining IRQs 376..383
[ 2.445190] twl4030: gpio (irq 368) chaining IRQs 384..401
[ 2.446319] regulator: VDAC: 1800 mV normal standby
[ 2.446685] regulator: VUSB1V5: 1500 mV normal standby
[ 2.447021] regulator: VUSB1V8: 1800 mV normal standby
[ 2.447357] regulator: VUSB3V1: 3100 mV normal standby
[ 2.447692] i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz
[ 2.448669] i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
[ 2.450225] console [ttyMTD0] enabled
[ 2.453918] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[ 2.453918] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
[ 2.454437] usbcore: registered new interface driver usbfs
[ 2.454620] usbcore: registered new interface driver hub
[ 2.454925] usbcore: registered new device driver usb
[ 2.454956] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
[ 2.458190] HS USB OTG: revision 0x33, sysconfig 0x2010, sysstatus 0x1, intrfsel 0x1, simenable 0x0
[ 2.458251] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine (X), bulk split (X), HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 2.458282] musb_hdrc: MHDRC RTL version 1.400
[ 2.458282] musb_hdrc: setup fifo_mode 5
[ 2.458312] musb_hdrc: 21/31 max ep, 9312/16384 memory
[ 2.458343] musb_hdrc: hw_ep 0shared, max 64
[ 2.458343] musb_hdrc: hw_ep 1tx, max 512
[ 2.458374] musb_hdrc: hw_ep 1rx, max 512
[ 2.458374] musb_hdrc: hw_ep 2tx, max 512
[ 2.458374] musb_hdrc: hw_ep 2rx, max 512
[ 2.458404] musb_hdrc: hw_ep 3tx, max 512
[ 2.458404] musb_hdrc: hw_ep 3rx, max 512
[ 2.458435] musb_hdrc: hw_ep 4tx, max 512
[ 2.458435] musb_hdrc: hw_ep 4rx, max 512
[ 2.458465] musb_hdrc: hw_ep 5tx, max 16
[ 2.458465] musb_hdrc: hw_ep 5rx, max 512
[ 2.458465] musb_hdrc: hw_ep 6tx, max 512
[ 2.458496] musb_hdrc: hw_ep 6rx, max 512
[ 2.458496] musb_hdrc: hw_ep 7tx, max 16
[ 2.458526] musb_hdrc: hw_ep 7rx, max 512
[ 2.458526] musb_hdrc: hw_ep 8tx, max 512
[ 2.458526] musb_hdrc: hw_ep 8rx, max 512
[ 2.458557] musb_hdrc: hw_ep 9tx, max 512
[ 2.458557] musb_hdrc: hw_ep 9rx, max 512
[ 2.458587] musb_hdrc: hw_ep 10tx, max 512
[ 2.458587] musb_hdrc: hw_ep 11tx, max 512
[ 2.458618] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
[ 2.458801] Registered /proc/driver/musb_hdrc
[ 2.483673] NET: Registered protocol family 2
[ 2.490356] Switched to high resolution mode on CPU 0
[ 2.552978] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 2.553344] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 2.553649] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 2.553863] TCP: Hash tables configured (established 8192 bind 8192)
[ 2.553894] TCP reno registered
[ 2.576446] NET: Registered protocol family 1
[ 2.597930] VFS: Disk quotas dquot_6.5.1
[ 2.598083] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.599578] msgmni has been set to 479
[ 2.600250] lowmem: Module initialized.
[ 2.608764] alg: No test for lzo999 (lzo999-generic)
[ 2.609039] alg: No test for stdrng (krng)
[ 2.609161] io scheduler noop registered
[ 2.609558] io scheduler cfq registered (default)
[ 2.609954] OMAP DSS rev 2.0
[ 2.610076] OMAP DISPC rev 3.0
[ 2.610168] OMAP VENC rev 2
[ 2.618011] OMAP3 ROM RNG: initializing
[ 2.620208] Serial: 8250/16550 driver4 ports, IRQ sharing disabled
[ 2.626739] brd: module loaded
[ 2.629089] loop: module loaded
[ 2.629180] i2c /dev entries driver
[ 2.630340] input: triton2-pwrbutton as /class/input/input0
[ 2.654449] triton2 power button driver initialized
[ 2.655059] OneNAND driver initializing
[ 2.656280] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000
[ 2.656372] OneNAND Manufacturer: Samsung (0xec)
[ 2.656402] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
[ 2.656433] OneNAND version = 0x0121
[ 2.656463] Chip support all block unlock
[ 2.656463] Chip has 2 plane
[ 2.657989] Scanning device for bad blocks
[ 2.684814] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.684875] Bad eraseblock 470 at 0x03ac0000
[ 2.723358] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.723419] Bad eraseblock 1148 at 0x08f80000
[ 2.774505] Creating 6 MTD partitions on "omap2-onenand":
[ 2.774536] 0x00000000-0x00020000 : "bootloader"
[ 2.774932] 0x00020000-0x00080000 : "config"
[ 2.775177] 0x00080000-0x000c0000 : "log"
[ 2.777648] mtdoops: Ready 26, 27 (no erase)
[ 2.777679] mtdoops: Attached to MTD device 2
[ 2.777709] 0x000c0000-0x002c0000 : "kernel"
[ 2.777984] 0x002c0000-0x004c0000 : "initfs"
[ 2.778228] 0x004c0000-0x10000000 : "rootfs"
[ 2.780090] UBI: attaching mtd5 to ubi0
[ 2.780120] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 2.780181] UBI: logical eraseblock size: 129024 bytes
[ 2.780212] UBI: smallest flash I/O unit: 2048
[ 2.780242] UBI: sub-page size: 512
[ 2.780273] UBI: VID header offset: 512 (aligned 512)
[ 2.780303] UBI: data offset: 2048
[ 2.913513] UBI: attached mtd5 to ubi0
[ 2.913574] UBI: MTD device name: "rootfs"
[ 2.913635] UBI: MTD device size: 251 MiB
[ 2.913665] UBI: number of good PEBs: 2008
[ 2.913696] UBI: number of bad PEBs: 2
[ 2.913696] UBI: max. allowed volumes: 128
[ 2.913726] UBI: wear-leveling threshold: 4096
[ 2.913757] UBI: number of internal volumes: 1
[ 2.913787] UBI: number of user volumes: 1
[ 2.913818] UBI: available PEBs: 0
[ 2.913848] UBI: total number of reserved PEBs: 2008
[ 2.913879] UBI: number of PEBs reserved for bad PEB handling: 20
[ 2.913909] UBI: max/mean erase counter: 1790/319
[ 2.913940] UBI: image sequence number: 35
[ 2.914367] usbcore: registered new interface driver libusual
[ 2.914489] UBI: background thread "ubi_bgt0d" started, PID 26
[ 2.936248] input: omap_twl4030keypad as /class/input/input1
[ 2.984863] cpuidle: using governor ladder
[ 2.984924] cpuidle: using governor menu
[ 2.985107] Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
[ 2.985351] ASoC version 0.13.2
[ 2.998901] AIC3X Audio Codec 0.2
[ 3.001464] asoc: tlv320aic3x <-> omap-mcbsp-dai-0 mapping ok
[ 3.002960] asoc: Bluetooth codec <-> omap-mcbsp-dai-1 mapping ok
[ 3.054534] input: RX51 (tlv320aic3x) Jack as /class/input/input2
[ 3.078887] ALSA device list:
[ 3.078918] #0: RX51 (tlv320aic3x)
[ 3.079162] TCP cubic registered
[ 3.079193] Initializing XFRM netlink socket
[ 3.079284] NET: Registered protocol family 17
[ 3.079345] NET: Registered protocol family 15
[ 3.079376] ThumbEE CPU extension supported.
[ 3.079437] Power Management for TI OMAP3.
[ 3.082824] pm_dbg_init()
[ 3.083618] SmartReflex driver initialized
[ 3.089782] Disabling unused clock "gpt2_ick"
[ 3.089874] Disabling unused clock "gpt3_ick"
[ 3.089904] Disabling unused clock "gpt4_ick"
[ 3.089965] Disabling unused clock "gpt5_ick"
[ 3.089996] Disabling unused clock "gpt6_ick"
[ 3.090026] Disabling unused clock "gpt7_ick"
[ 3.090057] Disabling unused clock "gpt8_ick"
[ 3.090087] Disabling unused clock "gpt9_ick"
[ 3.090118] Disabling unused clock "uart3_ick"
[ 3.090148] Disabling unused clock "gpio2_dbck"
[ 3.090209] Disabling unused clock "gpio3_dbck"
[ 3.090240] Disabling unused clock "gpio4_dbck"
[ 3.090270] Disabling unused clock "gpio5_dbck"
[ 3.090301] Disabling unused clock "gpio6_dbck"
[ 3.090332] Disabling unused clock "gpt9_fck"
[ 3.090362] Disabling unused clock "gpt8_fck"
[ 3.090393] Disabling unused clock "gpt7_fck"
[ 3.090454] Disabling unused clock "gpt6_fck"
[ 3.090484] Disabling unused clock "gpt5_fck"
[ 3.090515] Disabling unused clock "gpt4_fck"
[ 3.090545] Disabling unused clock "gpt3_fck"
[ 3.090576] Disabling unused clock "gpt2_fck"
[ 3.090606] Disabling unused clock "uart3_fck"
[ 3.090667] Disabling unused clock "wdt2_ick"
[ 3.090698] Disabling unused clock "wdt2_fck"
[ 3.090728] Disabling unused clock "gpio1_dbck"
[ 3.090759] Disabling unused clock "rng_ick"
[ 3.090820] Disabling unused clock "ssi_ick"
[ 3.090850] Disabling unused clock "gpt10_ick"
[ 3.090881] Disabling unused clock "gpt11_ick"
[ 3.090911] Disabling unused clock "uart1_ick"
[ 3.090942] Disabling unused clock "uart2_ick"
[ 3.091003] Disabling unused clock "usbtll_ick"
[ 3.091033] Disabling unused clock "ssi_ssr_fck"
[ 3.091064] Disabling unused clock "uart1_fck"
[ 3.091125] Disabling unused clock "uart2_fck"
[ 3.091156] Disabling unused clock "usbtll_fck"
[ 3.091217] Disabling unused clock "ts_fck"
[ 3.091247] Disabling unused clock "cpefuse_fck"
[ 3.091278] Disabling unused clock "gpt11_fck"
[ 3.091308] Disabling unused clock "gpt10_fck"
[ 3.091369] Disabling unused clock "dpll5_ck"
[ 3.091430] Disabling unused clock "dpll4_m6x2_ck"
[ 3.091461] Disabling unused clock "dpll4_m5x2_ck"
[ 3.091522] Disabling unused clock "dpll3_m3x2_ck"
[ 3.091552] Disabling unused clock "sys_clkout1"
[ 3.091979] Bootup reason: pwr_key
[ 3.092071] OMAP GPIO switch handler initializing
[ 3.094635] slide (GPIO 71) is now closed
[ 3.094696] proximity (GPIO 89) is now open
[ 3.094726] kb_lock (GPIO 113) is now open
[ 3.094757] headphone (GPIO 177) is now disconnected
[ 3.094787] cam_shutter (GPIO 110) is now closed
[ 3.094818] cam_launch (GPIO 69) is now inactive
[ 3.094848] cam_focus (GPIO 68) is now inactive
[ 3.094879] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[ 3.095489] registered taskstats version 1
[ 3.115600] omapfb: acx565akm rev 8d LCD detected
[ 3.147644] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[ 3.167907] UBIFS: recovery needed
[ 3.211578] UBIFS: recovery completed
[ 3.211639] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.211700] UBIFS: file system size: 254564352 bytes (248598 KiB, 242 MiB, 1973 LEBs)
[ 3.211730] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 3.211791] UBIFS: media format: 4 (latest is 4)
[ 3.211822] UBIFS: default compressor: lzo
[ 3.211853] UBIFS: reserved for root: 4384586 bytes (4281 KiB)
[ 3.212249] VFS: Mounted root (ubifs filesystem).
[ 3.212432] Freeing init memory: 144K
[ 5.772033] Registered led device: twl4030:vibrator
[ 5.789062] tsl2563 2-0029: model 7, rev. 0
[ 5.984741] twl4030_rtc twl4030_rtc: rtc core: registered
__________________
C. Shirky: Everybody has something strange they are trying to accomplish.
C. Shirky: Everybody has something strange they are trying to accomplish.
In R&D mode first boot showed: Entering state: ACT DEAD
Now, with Pali's getbootstate modification, I don't get "SHUTDOWN" warning but only "Entering state: USER"