Page 2 of 3 1 2 3
Reply
Thread Tools
hallgreng is offline hallgreng
2006-07-19 , 22:23
Posts: 63 | Thanked: 21 times | Joined on Jan 2006
#11
Well, I noticed today that I cannot play video or audio files any more, so I suppose the problem lies with the aic23 powering up and down.
I think that tomorrow I am going to go ahead and flash the official 2006 root directory onto my 770 and avoid using apt on the command line to upgrade...
 
spycedtx is offline spycedtx
2006-07-20 , 08:06
Posts: 114 | Thanked: 7 times | Joined on Jan 2006
#12
Originally Posted by hallgreng
Well, I noticed today that I cannot play video or audio files any more, so I suppose the problem lies with the aic23 powering up and down.
I think that tomorrow I am going to go ahead and flash the official 2006 root directory onto my 770 and avoid using apt on the command line to upgrade...

I did the upgrade on telepathy and such as posted in the prior messages. This, of course, required using apt-get and fixing the install a few times (as other people noted).

And now that I've mounted remote windows shares, I've noticed audio and video no longer works for me, either. I even did a 'shutdown -r now', and attempted to play a local audio/video before even making a network connection. Always get "unable to perform operation. try again".

I'm wondering what exactly "broke" in updating those libraries.
 
BigBob is offline BigBob
2006-07-20 , 09:57
Posts: 2 | Thanked: 0 times | Joined on Feb 2006
#13
Originally Posted by spycedtx
I did the upgrade on telepathy and such as posted in the prior messages. This, of course, required using apt-get and fixing the install a few times (as other people noted).

And now that I've mounted remote windows shares, I've noticed audio and video no longer works for me, either. I even did a 'shutdown -r now', and attempted to play a local audio/video before even making a network connection. Always get "unable to perform operation. try again".

I'm wondering what exactly "broke" in updating those libraries.
Hi,

Same for me, it's really annoying since i use my time to constantly repair my toy.

That mean we can't use this device properly.

That really sux ...
Last edited by BigBob; 2006-07-20 at 10:20.
 
Kralisec's Avatar
Kralisec is offline Kralisec
2006-07-20 , 13:58
Posts: 25 | Thanked: 0 times | Joined on Mar 2006 @ France
#14
Same things for me: no way to play Discovery internal video,

this is my dmesg | grep aic
Code:
[   22.237487] aic23 powering up
[   22.241394] aic23_init_power() done
[   25.046630] aic23 powering down
[   32.479309] aic23 powering up
[   32.483184] aic23_init_power() done
[   39.046600] aic23 powering down
[   45.193847] aic23 powering up
[   45.197814] aic23_init_power() done
[   47.579681] aic23 powering down
[   66.888153] aic23 powering up
[   66.892089] aic23_init_power() done
[   69.960662] aic23 powering down

dmesg
Code:
ialized vram=1048576 pixclock 21940 kHz hfreq 24.9 kHz vfreq 51.0 Hz
[    1.966705] OMAP Watchdog Timer: initial timeout 60 sec
[    1.967407] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    1.977020] loop: loaded (max 8 devices)
[    1.978271] PPP generic driver version 2.4.2
[    1.978881] PPP Deflate Compression module registered
[    1.979003] PPP BSD Compression module registered
[    1.979095] tun: Universal TUN/TAP device driver, 1.6
[    1.979187] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.981994] Clock enabled to MCBSP1 & 3
[    1.982116] TLV320AIC23 I2C version 1.9 (02-Mar-2006)
[    1.982238] Retu power button driver initialized
[    1.982330] retu: Registering interrupt 0 for device PwrOnX
[    1.983154] input: retu-pwrbutton as /class/input/input0
[    1.984344] retu: Registering interrupt 2 for device RTCS
[    1.984588] retu: Registering interrupt 5 for device RTCA
[    1.985870] Retu watchdog driver initialized
[    1.986358] omap-hw-nand: OMAP NAND Controller rev. 1.1
[    1.986541] NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB 1,8V 8-bit)
[    1.986724] omap-hw-nand: using PSC values 2, 2, 3
[    1.986846] Scanning device for bad blocks
[    1.986968] Bad eraseblock 0 at 0x00000000
[    2.022918] 5 cmdlinepart partitions found on MTD device omap-nand
[    2.023071] Creating 5 MTD partitions on "omap-nand":
[    2.023193] 0x00000000-0x00020000 : "bootloader"
[    2.024780] 0x00020000-0x00080000 : "config"
[    2.026275] 0x00080000-0x00280000 : "kernel"
[    2.027801] 0x00280000-0x00480000 : "initfs"
[    2.029235] 0x00480000-0x08000000 : "root"
[    2.030700] udc: OMAP UDC driver, version: 4 October 2004
[    2.031555] udc: OMAP UDC rev 6.1, Mini-AB
[    2.031677] udc: hmc mode 16, tahvo-usb transceiver
[    2.031829] udc: fifo mode 0, 1832 bytes not used
[    2.032623] mice: PS/2 mouse device common for all mice
[    2.033203] OMAP Keypad Driver
[    2.034454] input: omap-keypad as /class/input/input1
[    2.035705] ads7846 spi2.0: touchscreen, irq 175
[    2.036926] input: ADS784x Touchscreen as /class/input/input2
[    2.041442] Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04 08:57:20 2006 UTC).
[    2.042694] ALSA device list:
[    2.042785]   No soundcards found.
[    2.042877] Netfilter messages via NETLINK v0.30.
[    2.043487] NET: Registered protocol family 2
[    2.101745] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    2.101898] MMC2: Command timeout, CMD0
[    2.103271] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    2.103637] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    2.103973] TCP: Hash tables configured (established 4096 bind 4096)
[    2.104064] TCP reno registered
[    2.104309] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.148773] MMC2: Command timeout, CMD0
[    2.148895] MMC2: Command timeout, CMD0
[    2.171569] TCP bic registered
[    2.171752] NET: Registered protocol family 1
[    2.171905] NET: Registered protocol family 17
[    2.172027] Bluetooth: L2CAP ver 2.8
[    2.172119] Bluetooth: L2CAP socket layer initialized
[    2.172302] Bluetooth: RFCOMM socket layer initialized
[    2.172454] Bluetooth: RFCOMM TTY layer initialized
[    2.172546] Bluetooth: RFCOMM ver 1.7
[    2.172637] Bluetooth: HIDP (Human Interface Emulation) ver 1.1
[    2.172729] Disabling unused clock "uart3_ck"...  done
[    2.172851] Disabling unused clock "uart1_ck"...  done
[    2.172943] FIXME: Clock "tc2_ck" seems unused
[    2.173034] Skipping reset check for DSP domain clock "dsptim_ck"
[    2.173126] Skipping reset check for DSP domain clock "dspxor_ck"
[    2.173248] Skipping reset check for DSP domain clock "dspper_ck"
[    2.173339] FIXME: Clock "ck_dpll1out" seems unused
[    2.174041] Bootup reason: pwr_key
[    2.174194] OMAP GPIO switch handler initializing
[    2.177398] headphone (GPIO 14) is now disconnected
[    2.177551] speaker (GPIO 58) is now disconnected
[    2.177642] prot_shell (GPIO 5) is now open
[    2.177734] bat_cover (GPIO 12) is now closed
[    2.178009] OMAP Random Number Generator ver. 40
[    2.178466] 128 words of entropy generated
[    2.224029] mmcblk0: mmc0:0001 000000 1003520KiB
[    2.224670]  mmcblk0: p1 p2 p3
[    2.453491] Empty flash at 0x001cd7c8 ends at 0x001cd800
[    2.459106] VFS: Mounted root (jffs2 filesystem).
[    2.459594] Freeing init memory: 92K
[    3.839263] tahvo: Registering interrupt 7 for device
[    3.840087] retu: Registering interrupt 8 for device
[    3.842346] retu: Registering interrupt 1 for device
[    3.842803] tahvo: Registering interrupt 1 for device
[    4.205139] Selected PERIPHERAL mode: no gadget driver, powering off.
[    5.681823] umac: module license 'Proprietary' taints kernel.
[    5.901336] CX3110x chip variant: STLC4370
[    6.021453] CX3110x: firmware version: 2.13.0.0.a.13.9
[    6.021667] Loaded CX3110x driver, version 0.8
[    9.762420] JFFS2 notice: (371) read_dnode: header CRC failed on node at 0x7ae97f0: read 0xffffffff, calculated 0x5dc85953
[   20.651489] omapdsp: mapping in ARM MMU, v=0xe0fff000, p=0x13c4a000, sz=0x1000
[   20.690704] omapdsp: mapping in ARM MMU, v=0xe0100000, p=0x12900000, sz=0x100000
[   20.690979] omapdsp: mapping in ARM MMU, v=0xe0200000, p=0x12800000, sz=0x100000
[   20.691314] omapdsp: mapping in ARM MMU, v=0xe0028000, p=0x13167000, sz=0x1000
[   20.691467] omapdsp: frame buffer export
[   20.691528] omapdsp: mapping in ARM MMU, v=0xe0300000, p=0x13d00000, sz=0x100000
[   20.691711] omapfb_notifier_cb(): event = READY
[   20.691772] omapfb_register_client(): success
[   20.692047] omapdsp: mapping in ARM MMU, v=0xe0400000, p=0x12f00000, sz=0x100000
[   20.692260] omapdsp: mapping in ARM MMU, v=0xe0500000, p=0x12e70000, sz=0x10000
[   20.692352] omapdsp: mapping in ARM MMU, v=0xe0510000, p=0x12e60000, sz=0x10000
[   20.692443] omapdsp: mapping in ARM MMU, v=0xe0520000, p=0x12e50000, sz=0x10000
[   20.692504] omapdsp: mapping in ARM MMU, v=0xe0530000, p=0x12e40000, sz=0x10000
[   20.692596] omapdsp: mapping in ARM MMU, v=0xe0540000, p=0x12e30000, sz=0x10000
[   20.692687] omapdsp: mapping in ARM MMU, v=0xe0550000, p=0x12e20000, sz=0x10000
[   20.692779] omapdsp: mapping in ARM MMU, v=0xe0560000, p=0x12e80000, sz=0x10000
[   20.692871] omapdsp: mapping in ARM MMU, v=0xe0570000, p=0x12e90000, sz=0x10000
[   21.109436] omapdsp: IPBUF configuration
[   21.109466]            512 words * 16 lines at 0xe0200000.
[   21.109710] omapdsp: found 4 task(s)
[   21.109985] omapdsp: task 0: name pcm0
[   21.110565] omapdsp: taskdev pcm0 enabled.
[   21.119293] omapdsp: task 1: name pcm1
[   21.119812] omapdsp: taskdev pcm1 enabled.
[   21.128814] omapdsp: task 2: name avsync
[   21.129333] omapdsp: taskdev avsync enabled.
[   21.138305] omapdsp: task 3: name audiopp
[   21.138916] omapdsp: taskdev audiopp enabled.
[   21.558776] hci_cmd_task: hci0 command tx timeout
[   21.558868] brf6150: Frame for non-running device
[   22.237487] aic23 powering up
[   22.241394] aic23_init_power() done
[   22.664733] omapdsp: mmap info: vmadr = 40016000, padr = 12f30000, len = 2000
[   25.046630] aic23 powering down
[   32.479309] aic23 powering up
[   32.483184] aic23_init_power() done
[   39.046600] aic23 powering down
[   45.193847] aic23 powering up
[   45.197814] aic23_init_power() done
[   45.199127] omapdsp: mmap info: vmadr = 40016000, padr = 12f10000, len = 2000
[   47.579681] aic23 powering down
[   66.888153] aic23 powering up
[   66.892089] aic23_init_power() done
[   69.960662] aic23 powering down
[   91.588378] omap-hw-nand: DMA timeout after 1187 ms, max. seen latency 1187 ms
[   93.730346] omap-hw-nand: DMA timeout after 1234 ms, max. seen latency 1234 ms

- I flash back to original 30 June 2006,
- install xterm with maemo-hackers.org/apt mistral main repository,
- update manually libtelepathy only with
dpkg -i ./libtelepathy_0.0.14-0osso1maemo1_armel.deb

Now internal Discovery video is ok, reboot is stable without R&D,
still powering up / powering down with aic like quoted in beginning, (dunno if it's important ...)


result: libtelepathy alone is not the problem


Good day,
Laurent.
 
Kralisec's Avatar
Kralisec is offline Kralisec
2006-07-20 , 16:22
Posts: 25 | Thanked: 0 times | Joined on Mar 2006 @ France
#15
Originally Posted by hallgreng
Looks like your situation was the same as mine, I had apt asking about maemo-launcher during upgrade, though I opted to keep the original config file.

I did not disable R&D mode nor have i cleared the no-lifeguard-reset flag.
I may do that tomorrow if necessary to test.

I looked through dmesg and around the end of bootup and this is all that looks interesting:
Code:
~ $ dmesg | grep -A 11 36.660
[   36.660705] aic23 powering up
[   36.664642] aic23_init_power() done
[   43.419555] aic23 powering down
[   50.039581] aic23 powering up
[   50.043670] aic23_init_power() done
[   50.045440] omapdsp: mmap info: vmadr = 40016000, padr = 12a10000, len = 2000
[   52.419555] aic23 powering down
[   67.910156] aic23 powering up
[   67.914123] aic23_init_power() done
[   68.450836] omap-hw-nand: DMA timeout after 1148 ms, max. seen latency 1148 ms
[   70.974273] aic23 powering down
[  326.545074] Loading 3825.arm firmware
Namely the "aic23 powering up and down (I dont know what this is or if it is normal behavior)
and the DMA timeout.
Does anyone have any knowledge of these two things? Due to the nature of the device, logs are sparce. dmesg is the best I can think of to gather information in this case...
Nop for the powering up / powering down ...

fresh flash: only install xterm, dmesg | grep aic
Code:
[   26.793823] aic23 powering up
[   26.797851] aic23_init_power() done
[   29.591705] aic23 powering down
[   36.857269] aic23 powering up
[   36.861114] aic23_init_power() done
[   43.424804] aic23 powering down
[   49.971679] aic23 powering up
[   49.975769] aic23_init_power() done
[   52.365051] aic23 powering down
[   81.095062] aic23 powering up
[   81.099121] aic23_init_power() done
[   84.185424] aic23 powering down
But no DMA timeout ...

Do you know how to clear "no-lifeguard-reset flag" ?
=> go out from R&D: 770 reboot loop,
go back to R&D: still reboot
no-lifeguard-reset flag set: no reboot loop

=> I expect that to clear this flag: going out from R&D is enough ...
but I don't find an express was to do this.



Good day,
Laurent.
 
spycedtx is offline spycedtx
2006-07-20 , 18:21
Posts: 114 | Thanked: 7 times | Joined on Jan 2006
#16
I've noticed the powerup/down messages a lot in dmesg, even before I noticed a problem with the video / audio. And, that makes me wonder something else.. perhaps the audio/video was broken before this update. Maybe installing Gizmo managed to break it.


I know this is the price we pay for playing on the edge, but I dread the thought of reflashing at this point, and having to reinstall all the apps, all over again.

I was cruising through dmesg -l output, and couldn't help but wonder if maybe something in the gstreamer* is what's been borked, even if -C doesn't report anything broken.
 
hallgreng is offline hallgreng
2006-07-20 , 19:08
Posts: 63 | Thanked: 21 times | Joined on Jan 2006
#17
Originally Posted by Kralisec
Do you know how to clear "no-lifeguard-reset flag" ?
=> go out from R&D: 770 reboot loop,
go back to R&D: still reboot
no-lifeguard-reset flag set: no reboot loop

=> I expect that to clear this flag: going out from R&D is enough ...
but I don't find an express was to do this.
I believe the syntax is:
$./flasher-2.0 --clear-rd-flags=no-lifeguard-reset

I think that today I will spend some time updating my personal 'make dirs, symlinks, and file edits the way i like them after a fresh install'-script and then flash back the official 06 root dir.

Like BigBob said, this is really hurting my ability to use this device.
On the bright side, at least it is easy to go back to a working state! =]
 
Kralisec's Avatar
Kralisec is offline Kralisec
2006-07-20 , 22:10
Posts: 25 | Thanked: 0 times | Joined on Mar 2006 @ France
#18
Originally Posted by hallgreng
I believe the syntax is:
$./flasher-2.0 --clear-rd-flags=no-lifeguard-reset
Very Good ! Exactly what I was looking for ... Thank you !!!


I've play several times to know which package cause the problem,

After lots of test I see that:
Nokia 770 in normal mode, fresh flash, only xterm,
disable R&D, clear no-lifeguard-reset flag,

dpkg -i gst-plugins-farsight_0.10.1-0osso2maemo1_armel.deb goes to reboot loop ...

ok: I reinstall like before, go to 14 packages folders,
remove gst-plugins and do a "dpkg -i *.deb"
unexpected reboot, but looks stable after this,
do it another time "dpkg -i *.deb" to finish previous install, no reboot,
another dpkg -i *.deb" and ... reboot ! no logic for me ...

But after reboot: no loop mode, great I think ...

I go to gst-plugin to install it: dpkg request libstd
(do you remember ? not supposed to be installed ???)
ok ... but dpkg libstd request libgcc (supposely installed !)
and to finish dpkg -i libgcc request to install gcc-3.4

After this 3 updates, I test to see result with reboot ... reboot loop mode come back
(remember: without gst-plugins)

ARGHHH ... it'enough for me ... I understood nothing
I stop playing, my 770 is ok me like that !





Bad day
Laurent.
 
shapr is offline shapr
2006-08-25 , 12:40
Posts: 2 | Thanked: 0 times | Joined on Aug 2006
#19
Two weeks ago I ssh'd into my 770 and did apt-get upgrade
After everything upgraded, I got a reboot loop.
I asked on #maemo and disable the lifeguard reboot

I didn't know that was the problem so I reflashed OS2006 today and did apt-get upgrade again...

The moral of this story is, apt-get on the command line is not supported by Nokia.

Sadly, I don't have time to reflash and reinstall everything again today.
 
hallgreng is offline hallgreng
2006-08-25 , 19:35
Posts: 63 | Thanked: 21 times | Joined on Jan 2006
#20
I find this mostly baffling.
I understand how the application manager can do its own apt without killing stuff (just not showing these destructive packages and installing updates individually), but I dont understand WHY there are destructive packages in the stable repo!
 
Reply
Page 2 of 3 1 2 3

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 02:56.

Contact Us - Home - Archive - Top