maemo.org - Talk - Diablo not compatibile with my N800

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - Diablo not compatibile with my N800 (https://talk.maemo.org/showthread.php?t=21828)

spirytsick

2008-07-12 13:19

Diablo not compatibile with my N800

Well I just went back to Chinook as Diablo would not work on my device. It would not boot after the flash and when it did it will reboot spontaneously from time to time. Also, when I have finally managed to clone the os to the mmc (unit hanging on me prevented me from completing the process in a reasonable time). The boot menu was corrupted with an additional entry to boot from mmc2 which had N/A next to it. I have tried evertyhing, rd-mode trick, reformatting both cards (and repartitioning again). Tried to reflash probably several times. It still does not work. After reflashing back to Chinook everything is fine again. Seriously I do not know what might the problem be but it either means that my n800 is faulty or there are some n800 devices with some unique characteristics which are not compatible with Diablo. Hard to say. And yes I have used the n800 flash

md5sums below

Code:

786a0150ca29e6688b3dbcbe14bacbd1  RX-34_2008SE_2.2007.51-3_PR_COMBINED_MR0_ARM.bin,

3081bf7fdf8861b541eb26936c5f9e26  RX-34_DIABLO_4.2008.23-14_PR_COMBINED_MR0_ARM.bin,

and the filesizes

Code:

-rw-r--r-- 1 spiryt spiryt 141226447 2008-07-12 13:11 RX-34_2008SE_2.2007.51-3_PR_COMBINED_MR0_ARM.bin,

-rw-r--r-- 1 spiryt spiryt 141697063 2008-06-26 14:56 RX-34_DIABLO_4.2008.23-14_PR_COMBINED_MR0_ARM.bin,

I am using Nokia branded DKE-2 cable for all flashing

Any ideas guys ?

geneven

2008-07-13 16:03

Re: Diablo not compatibile with my N800

Did you.try not restoring anything from backup?

Did you try without mmc cards?

spirytsick

2008-07-13 16:14

Re: Diablo not compatibile with my N800

yes I did try without both cards and no I haven't try to restore anything from backup. I have looked in dmesg after enabling rd-mode and it looks like sapwood server is segfaulting in each case. I did not try to get the core dumps though. In the meantime I have experimented a bit and I got it running somehow although I do not know how long it will last until it goes bonkers again. It looks like internal flash is somehow corrupted on my device. For the moment what I did is to extract rootfs from flashfile, mounted it under linux , cloned the whole os to mmc, flashed the tablet and managed to boot after several attempts, flashed Fanoush's initfs and now it's happily running from mmc.

igor	2008-07-13 16:22

Re: Diablo not compatibile with my N800

Did you try to flash Diablo, plain, to the internal memory, no mods, no cloning, no dual boot?

Just the FIASCO image and nothing else?

spirytsick

2008-07-13 17:46

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by igor (Post 202498)

Did you try to flash Diablo, plain, to the internal memory, no mods, no cloning, no dual boot?

Just the FIASCO image and nothing else?

Yes Igor, it does not work. Or more precisely it does not always work. The flashing itself goes ok. Then the unit reboots, it boots half way and then reboots again. At that point the next boot is either successfull or the unit goes into reboot loop and I have to take battery out for some time for the unit to work again. It is very frustrating as under chinook it does work without a problem.

igor	2008-07-13 18:20

Re: Diablo not compatibile with my N800

What you said about the internal flash being corrupted shouldn't happen.
The fact that it works with the older OS is weird.
I would try to get the unit checked at a service point and replaced, if it still under warranty.

spirytsick

2008-07-13 18:57

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by igor (Post 202565)

That's what I am trying to do right now. However I have bought my N800 off the American EBay seller. The unit itself does not have warranty in EU. I will have to send it back to the US and then get it back which is a pain or as you would have put in Suomi - Vittu....and so on in a similar fashion :)

igor	2008-07-13 19:07

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by spirytsick (Post 202575)

Heh, I don't want to get into a pissing contest, but as italian, I find finnish swearwords not so satisfying ...

Anyway i would check the warranty with some local consumers association: it might be that you still have some rights.

Beyond that, you could try to flash the Diablo rootfs and initfs on top of the old one, after disabling lifeguard reboots.

This will use the old kernel and you probably will not be able to use the modules from the new initfs, but at least should tell you if the user space can boot.

spirytsick

2008-07-13 19:12

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by igor (Post 202578)

Apologies, there is no more expressive language for swearwords than Italian :). I will give it a try with the reflashing initfs from earlier versions. As for the local consumer groups, wish me luck.

igor	2008-07-13 19:29

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by spirytsick (Post 202582)

I will give it a try with the reflashing initfs from earlier versions.

No, what i meant is:
-disable lifeguard reboots

flash:
-old bootloader
-old kernel
-new initfs
-new rootfs

spirytsick

2008-07-13 20:15

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by igor (Post 202588)

No, what i meant is:
-disable lifeguard reboots

flash:
-old bootloader
-old kernel
-new initfs
-new rootfs

you mean --set-rd-flags=no-lifeguard-resets ?

igor	2008-07-13 20:27

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by spirytsick (Post 202601)

you mean --set-rd-flags=no-lifeguard-resets ?

yup

and when i pressed "Submit Reply" i've been presented by what is probably the most stupid message that could have been conceived on a forum: "the message you entered is too short, make it at least 10 characters long"

GeneralAntilles

2008-07-13 20:30

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by igor (Post 202605)

and when i pressed "Submit Reply" i've been presented by what is probably the most stupid message that could have been conceived on a forum: "the message you entered is too short, make it at least 10 characters long"

Dude, you don't even know. . . . :p

spirytsick

2008-07-13 20:37

Re: Diablo not compatibile with my N800

Oh my ...!

spirytsick

2008-07-14 19:47

Re: Diablo not compatibile with my N800

I am still not quite sure what is going on. I have managed to get it running again yesterday, installed a bunch of apps. The tablet worked all right yesterday and the half of the day today. The moment I took it to work it started being temperamental again. I restated it once and then it would not boot. Either from vanilla flash or from the mmc. It would not even restart with the lifeguard-resets on but either hand with the blue progress bar in the middle or funnily enough the bar would go all the width of the screen and then the unit will hang. Pressing the power button would not restart the tablet. Only removal of battery and putting it back would get me at the boot menu again. It would not boot even after that. I gave up and went home. Just for kicks I connected it to my charger and voila, it booted straight away from flash. Then I have tried to boot from mmc card and it worked. I no have absolutely no idea of what the problem might be. Faulty flash ? But then the mmc boot would work. Faulty RAM, a possibility ? Faulty battery ? I am not sure what the battery malfunction effects would be (save from the device going up in flames)... any ideas guys ? Any comments will be appreciated

qwerty12

2008-07-14 19:51

Re: Diablo not compatibile with my N800

If you could, apt-getting sysklogd would be useful. jffs errors are reported in the syslog.

spirytsick

2008-07-14 20:21

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by qwerty12 (Post 202923)

If you could, apt-getting sysklogd would be useful. jffs errors are reported in the syslog.

I will try it at once. I am on diablo know. Would I have to build a deb in the scratchbox ?

btw here's my dmesg when booting from flash

Code:

in ARM MMU, v=0xe0fdf000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fe0000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fd9000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fb0000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fb1000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fb2000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fb3000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fb4000, sz=0x1000

[   22.335937] MMU: unmapping in ARM MMU, v=0xe0fff000, sz=0x1000

[   22.335937] MMU: OMAP mmu:dsp MMU initialized (HW v1.0)

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fff000, p=0x85d1b000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fce000, p=0x48008000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fe2000, p=0x48094000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fdc000, p=0x4807c000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fdd000, p=0x4807e000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fde000, p=0x48080000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fdf000, p=0x48082000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fe0000, p=0x48090000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fd9000, p=0x48068000, sz=0x1000

[   22.335937] MMU: mapping in ARM MMU, v=0xe0fb0000, p=0x54000000, sz=0x1000

[   22.343750] MMU: mapping in ARM MMU, v=0xe0fb1000, p=0x54001000, sz=0x1000

[   22.343750] MMU: mapping in ARM MMU, v=0xe0fb2000, p=0x54002000, sz=0x1000

[   22.343750] MMU: mapping in ARM MMU, v=0xe0fb3000, p=0x54003000, sz=0x1000

[   22.343750] MMU: mapping in ARM MMU, v=0xe0fb4000, p=0x54004000, sz=0x1000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0028000, p=0x85d33000, sz=0x1000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0100000, p=0x85e00000, sz=0x100000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0200000, p=0x85f00000, sz=0x100000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0400000, p=0x85800000, sz=0x100000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0500000, p=0x85d40000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0510000, p=0x85d50000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0520000, p=0x85d60000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0530000, p=0x85d70000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0540000, p=0x85d80000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0550000, p=0x85d90000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0560000, p=0x85da0000, sz=0x10000

[   22.359375] MMU: mapping in ARM MMU, v=0xe0570000, p=0x85db0000, sz=0x10000

[   22.726562] omapdsp: IPBUF configuration

[   22.726562]            512 words * 16 lines at 0xe0200000.

[   22.726562] omapdsp: found 5 task(s)

[   22.726562] omapdsp: task 0: name pcm3

[   22.726562] omapdsp: taskdev pcm3 enabled.

[   22.734375] omapdsp: task 1: name pcm_rec1

[   22.734375] omapdsp: taskdev pcm_rec1 enabled.

[   22.734375] omapdsp: task 2: name pcm1

[   22.734375] omapdsp: taskdev pcm1 enabled.

[   22.734375] omapdsp: task 3: name audiopp

[   22.734375] omapdsp: taskdev audiopp enabled.

[   22.734375] omapdsp: task 4: name pcm0

[   22.734375] omapdsp: taskdev pcm0 enabled.

[   23.359375] EAC mode: play enabled, rec enabled

[   26.000000] EAC mode: play disabled, rec disabled

[   69.500000] EAC mode: play enabled, rec enabled

[   70.929687] g_file_storage gadget: File-backed Storage Gadget, version: 28 November 2005

[   70.929687] g_file_storage gadget: Number of LUNs=2

[   70.929687] musb_hdrc musb_hdrc: MUSB HDRC host driver

[   70.937500] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file 'devices'

[   70.937500] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file '001'

[   70.937500] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

[   70.937500] musb_hdrc musb_hdrc: supports USB remote wakeup

[   70.937500] usb usb1: default language 0x0409

[   70.937500] usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1

[   70.937500] usb usb1: Product: MUSB HDRC host driver

[   70.937500] usb usb1: Manufacturer: Linux 2.6.21-omap1 musb-hcd

[   70.937500] usb usb1: SerialNumber: musb_hdrc

[   70.937500] usb usb1: uevent

[   70.937500] usb usb1: usb_probe_device

[   70.937500] usb usb1: configuration #1 chosen from 1 choice

[   70.937500] usb usb1: adding 1-0:1.0 (config #1, interface 0)

[   70.937500] usb 1-0:1.0: uevent

[   70.937500] hub 1-0:1.0: usb_probe_interface

[   70.937500] hub 1-0:1.0: usb_probe_interface - got id

[   70.937500] hub 1-0:1.0: USB hub found

[   70.937500] hub 1-0:1.0: 1 port detected

[   70.937500] hub 1-0:1.0: standalone hub

[   70.937500] hub 1-0:1.0: individual port power switching

[   70.937500] hub 1-0:1.0: no over-current protection

[   70.937500] hub 1-0:1.0: Single TT

[   70.937500] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)

[   70.937500] hub 1-0:1.0: power on to power good time: 10ms

[   70.937500] hub 1-0:1.0: 200mA bus power budget for each child

[   70.937500] hub 1-0:1.0: local power source is good

[   70.937500] hub 1-0:1.0: enabling power on all ports

[   70.937500] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/musb/tusb6010.c musb_platform_enable: dma not reactivated

[   71.093750] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file '001'

[   71.093750] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000

[   71.914062] EAC mode: play disabled, rec disabled

[   73.093750] hub 1-0:1.0: hub_suspend

[   73.093750] usb usb1: usb auto-suspend

[   75.101562] EAC mode: play enabled, rec enabled

[   82.703125] EAC mode: play disabled, rec disabled

[   86.445312] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[   87.195312] Adding 131064k swap on /media/mmc2/.swap.  Priority:-1 extents:16 across:906532k

[   87.578125] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   90.914062] hci_cmd_task: hci0 command tx timeout

[   90.914062] hci_h4p hci_h4p: Frame for non-running device

Second part will have to be in another post as I got this funny message (Opposite of Igors reply)

Code:

1. The text that you have entered is too long (16258 characters). Please shorten it to 10000 characters long.

I will try to get one when I manage to boot from the mmc again...

spirytsick

2008-07-14 20:21

Re: Diablo not compatibile with my N800

and the continuation

Code:

[   92.656250] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   97.429687] cx3110x: loading 3826.arm firmware.

[   97.671875] (c)opyright 2004 Conexant

[   97.671875] 

[   97.671875] build info: PRISM SoftMAC

[   97.671875]   creator: [kvalo]

[   97.671875]   date: [07/10/05-11:45]

[   97.671875] 

[   97.679687] cx3110x: MAC address.

[   97.687500] cx3110x: libumac version 2.12.0.0.a.9.15-5

[   97.687500] cx3110x: lmac version 2.13.0.0.a.22.8

[   97.687500] cx3110x: PSM disabled.

[   99.070312] cx3110x: scanned 11 channels.

[   99.414062] cx3110x: shut down softmac.

[  100.218750] cx3110x: loading 3826.arm firmware.

[  100.460937] (c)opyright 2004 Conexant

[  100.460937] 

[  100.460937] build info: PRISM SoftMAC

[  100.460937]   creator: [kvalo]

[  100.460937]   date: [07/10/05-11:45]

[  100.460937] 

[  100.468750] cx3110x: MAC address

[  100.476562] cx3110x: libumac version 2.12.0.0.a.9.15-5

[  100.476562] cx3110x: lmac version 2.13.0.0.a.22.8

[  101.882812] cx3110x: scanned 11 channels.

[  104.101562] cx3110x: associated to 00:16:b6:da:58:97 (bcn 100 msec, DTIM 1).

[  106.632812] cx3110x: PSM dynamic with 200 ms CAM timeout.

[  106.820312] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  109.640625] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  109.718750] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  110.179687] EAC mode: play enabled, rec enabled

[  113.625000] EAC mode: play disabled, rec disabled

[  114.656250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  120.507812] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  136.523437] cx3110x: PSM dynamic with 100 ms CAM timeout.

[  163.523437] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  163.578125] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

[  168.578125] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  171.671875] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  176.953125] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  177.507812] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  180.554687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  182.500000] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  212.929687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  213.328125] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  216.585937] EAC mode: play enabled, rec enabled

[  217.867187] cx3110x: PSM dynamic with 200 ms CAM timeout.

[  222.875000] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  228.062500] EAC mode: play disabled, rec disabled

[  228.585937] EAC mode: play enabled, rec enabled

[  231.085937] EAC mode: play disabled, rec disabled

[  270.929687] EAC mode: play enabled, rec enabled

[  276.890625] EAC mode: play disabled, rec disabled

[  278.070312] EAC mode: play enabled, rec enabled

[  280.570312] EAC mode: play disabled, rec disabled

[  280.664062] EAC mode: play enabled, rec enabled

[  287.148437] EAC mode: play disabled, rec disabled

[  287.484375] EAC mode: play enabled, rec enabled

[  288.632812] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  290.718750] EAC mode: play disabled, rec disabled

[  290.875000] EAC mode: play enabled, rec enabled

[  291.367187] Adding 131064k swap on /media/mmc2/.swap.  Priority:-2 extents:16 across:906532k

[  293.398437] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  293.578125] EAC mode: play disabled, rec disabled

[  296.367187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  296.554687] cx3110x: shut down softmac.

[  296.898437] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  298.554687] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  299.882812] hci_h4p hci_h4p: Frame for non-running device

[  307.023437] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  328.617187] EAC mode: play enabled, rec enabled

[  330.984375] EAC mode: play disabled, rec disabled

[  334.234375] EAC mode: play enabled, rec enabled

[  341.835937] EAC mode: play disabled, rec disabled

[  344.875000] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  345.367187] Adding 131064k swap on /media/mmc2/.swap.  Priority:-3 extents:16 across:906532k

[  346.250000] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  348.734375] hci_cmd_task: hci0 command tx timeout

[  348.734375] hci_h4p hci_h4p: Frame for non-running device

[  349.906250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  353.882812] cx3110x: loading 3826.arm firmware.

[  354.125000] (c)opyright 2004 Conexant

[  354.125000] 

[  354.125000] build info: PRISM SoftMAC

[  354.125000]   creator: [kvalo]

[  354.125000]   date: [07/10/05-11:45]

[  354.125000] 

[  354.132812] cx3110x: MAC address 

[  354.140625] cx3110x: libumac version 2.12.0.0.a.9.15-5

[  354.140625] cx3110x: lmac version 2.13.0.0.a.22.8

[  354.140625] cx3110x: PSM disabled.

[  355.445312] cx3110x: scanned 11 channels.

[  355.757812] cx3110x: shut down softmac.

[  356.531250] cx3110x: loading 3826.arm firmware.

[  356.773437] (c)opyright 2004 Conexant

[  356.773437] 

[  356.773437] build info: PRISM SoftMAC

[  356.773437]   creator: [kvalo]

[  356.773437]   date: [07/10/05-11:45]

[  356.773437] 

[  356.781250] cx3110x: MAC address 

[  356.789062] cx3110x: libumac version 2.12.0.0.a.9.15-5

[  356.789062] cx3110x: lmac version 2.13.0.0.a.22.8

[  358.187500] cx3110x: scanned 11 channels.

[  361.757812] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  362.593750] cx3110x: associated to 00:16:b6:da:58:97 (bcn 100 msec, DTIM 1).

[  365.062500] cx3110x: PSM dynamic with 200 ms CAM timeout.

[  369.367187] EAC mode: play enabled, rec enabled

[  372.812500] EAC mode: play disabled, rec disabled

[  394.929687] cx3110x: PSM dynamic with 100 ms CAM timeout.

[  558.429687] musb_stage0_irq 668: BUS RESET as b_idle

[  558.539062] musb_stage0_irq 668: BUS RESET as b_peripheral

[  558.648437] musb_hdrc periph: enabled ep1in for bulk IN, dma, maxpacket 512

[  558.648437] musb_hdrc periph: enabled ep1out for bulk OUT, dma, maxpacket 512

[  558.648437] g_file_storage gadget: high speed config #1

[  561.500000] cx3110x: PSM dynamic with 200 ms CAM timeout.

[  563.664062] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  563.703125] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  569.687500] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  569.734375] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  593.179687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  600.992187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  621.523437] cx3110x: PSM dynamic with 100 ms CAM timeout.

[  627.781250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  633.812500] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  672.781250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  691.765625] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  696.117187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  874.429687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  902.898437] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  909.460937] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1261.203125] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1270.710937] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1305.015625] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1316.703125] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1367.734375] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1428.750000] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1432.921875] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1443.210937] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1482.929687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1488.171875] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1512.742187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[ 1549.023437] cx3110x: WARNING chip requested DMA rx transfer of a zero length frame

[ 1621.851562] cx3110x: WARNING chip requested DMA rx transfer of a zero length frame

[ 1634.320312] cx3110x: WARNING prism_softmac_frame_tx_done() returned an empty frame.

[ 1636.890625] cx3110x: WARNING chip requested DMA rx transfer of a zero length frame

spirytsick

2008-07-14 20:38

Re: Diablo not compatibile with my N800

Here's the content of /var/lib/dsme/lifeguard_resets

Code:

Nokia-N800-23-14:~# cat /var/lib/dsme/stats/lifeguard_resets

/usr/bin/dbus-daemon --system  : 1

/usr/bin/btcond -l  : 1

/usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolisten tcp :  2

/usr/bin/matchbox-window-manager -theme default -use_titlebar yes -use_desktop_mode plain -use_lowlight no -use_cursor yes -use_dialog_mode static -use_super_modal yes :  13 *

/usr/bin/hildon-input-method  : 1

/usr/bin/hildon-desktop  : 1

and the mmc boot dmesg part 1:

Code:

[    1.070312] Disabling unused clock "uart2_ick"

[    1.070312] Disabling unused clock "gpt12_fck"

[    1.070312] Disabling unused clock "gpt12_ick"

[    1.070312] Disabling unused clock "gpt11_fck"

[    1.070312] Disabling unused clock "gpt11_ick"

[    1.070312] Disabling unused clock "gpt8_fck"

[    1.070312] Disabling unused clock "gpt8_ick"

[    1.070312] Disabling unused clock "gpt7_fck"

[    1.070312] Disabling unused clock "gpt7_ick"

[    1.070312] Disabling unused clock "gpt6_fck"

[    1.070312] Disabling unused clock "gpt6_ick"

[    1.070312] Disabling unused clock "gpt5_fck"

[    1.070312] Disabling unused clock "gpt5_ick"

[    1.070312] Disabling unused clock "gpt4_fck"

[    1.070312] Disabling unused clock "gpt4_ick"

[    1.070312] Disabling unused clock "gpt3_fck"

[    1.070312] Disabling unused clock "gpt3_ick"

[    1.070312] Disabling unused clock "gpt2_fck"

[    1.070312] Disabling unused clock "gpt2_ick"

[    1.070312] Disabling unused clock "dss2_fck"

[    1.070312] Bootup reason: pwr_key

[    1.070312] OMAP GPIO switch handler initializing

[    1.070312] headphone (GPIO 107) is now disconnected

[    1.070312] cam_turn (GPIO 12) is now inactive

[    1.070312] cam_act (GPIO 95) is now inactive

[    1.070312] bat_cover (GPIO 110) is now closed

[    1.070312] menelaus 1-0072: Setting voltage 'VMEM' to 1500 mV (reg 0x0a, val 0xb4)

[    1.085937] menelaus 1-0072: Setting voltage 'VIO' to 2500 mV (reg 0x0a, val 0xb8)

[    1.132812] omap24xxcam omap24xxcam: sensor is TCM825x

[    1.156250] mmcblk0: mmc0:9720 SD08G 7864320KiB 

[    1.156250]  mmcblk0: p1 p2

[    1.156250] mmci-omap mmci-omap.1: command timeout (CMD8)

[    1.156250] mmci-omap mmci-omap.1: command timeout (CMD8)

[    1.164062] menelaus 1-0072: Shutting off 'VIO'

[    1.164062] menelaus 1-0072: Setting voltage 'VDCDC3' to 3300 mV (reg 0x07, val 0x39)

[    1.187500] menelaus 1-0072: Shutting off 'VMEM'

[    1.187500] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[    1.203125] omap24xxcam omap24xxcam: registered device video0 [v4l2]

[    1.281250] VFS: Mounted root (jffs2 filesystem) readonly.

[    1.281250] Freeing init memory: 124K

[    1.640625] mmcblk1: mmc1:c113 SD08G 7864320KiB 

[    1.640625]  mmcblk1: p1

[    6.156250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[    6.640625] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[    8.312500] umac: module license 'Proprietary' taints kernel.

[    8.343750] umac: version 2.0.7 loaded.

[    8.484375] cx3110x: chip variant STLC4550.

[    8.578125] cx3110x: firmware version 2.13.0.0.a.22.8.

[    8.593750] cx3110x: driver version 2.0.15 loaded.

[    8.687500] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[    8.875000] tahvo: Registering interrupt 7 for device 

[    8.875000] retu: Registering interrupt 8 for device 

[    8.875000] retu: Registering interrupt 1 for device 

[    8.875000] tahvo: Registering interrupt 1 for device 

[   13.695312] menelaus 1-0072: Setting voltage 'VMEM' to 1500 mV (reg 0x0a, val 0xb8)

[   13.710937] menelaus 1-0072: Setting voltage 'VIO' to 2500 mV (reg 0x0a, val 0xb8)

[   13.757812] tcm825x_find_size(): size 3

[   13.796875] tcm825x_configure(): configuring Image Size 3

[   13.796875] tcm825x_configure(): configuring Pixel Format 1

[   13.828125] menelaus 1-0072: Shutting off 'VIO'

[   13.843750] menelaus 1-0072: Shutting off 'VMEM'

[   14.148437] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   16.648437] MMU: OMAP mmu:dsp MMU initialized (HW v1.0)

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fff000, p=0x866a0000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fce000, p=0x48008000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fe2000, p=0x48094000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fdc000, p=0x4807c000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fdd000, p=0x4807e000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fde000, p=0x48080000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fdf000, p=0x48082000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fe0000, p=0x48090000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fd9000, p=0x48068000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fb0000, p=0x54000000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fb1000, p=0x54001000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fb2000, p=0x54002000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fb3000, p=0x54003000, sz=0x1000

[   16.648437] MMU: mapping in ARM MMU, v=0xe0fb4000, p=0x54004000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fce000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fe2000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fdc000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fdd000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fde000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fdf000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fe0000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fd9000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fb0000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fb1000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fb2000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fb3000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fb4000, sz=0x1000

[   16.757812] MMU: unmapping in ARM MMU, v=0xe0fff000, sz=0x1000

[   16.757812] MMU: OMAP mmu:dsp MMU initialized (HW v1.0)

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fff000, p=0x866a0000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fce000, p=0x48008000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fe2000, p=0x48094000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fdc000, p=0x4807c000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fdd000, p=0x4807e000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fde000, p=0x48080000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fdf000, p=0x48082000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fe0000, p=0x48090000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fd9000, p=0x48068000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fb0000, p=0x54000000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fb1000, p=0x54001000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fb2000, p=0x54002000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fb3000, p=0x54003000, sz=0x1000

[   16.757812] MMU: mapping in ARM MMU, v=0xe0fb4000, p=0x54004000, sz=0x1000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0028000, p=0x862a5000, sz=0x1000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0100000, p=0x86700000, sz=0x100000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0200000, p=0x86300000, sz=0x100000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0400000, p=0x86000000, sz=0x100000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0500000, p=0x862b0000, sz=0x10000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0510000, p=0x862c0000, sz=0x10000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0520000, p=0x862d0000, sz=0x10000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0530000, p=0x862e0000, sz=0x10000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0540000, p=0x862f0000, sz=0x10000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0550000, p=0x86100000, sz=0x10000

[   16.882812] MMU: mapping in ARM MMU, v=0xe0560000, p=0x86110000, sz=0x10000

[   16.890625] MMU: mapping in ARM MMU, v=0xe0570000, p=0x86120000, sz=0x10000

spirytsick

2008-07-14 20:40

Re: Diablo not compatibile with my N800

and the second part of mmc boot dmesg:

Code:

[   17.531250] omapdsp: IPBUF configuration

[   17.531250]            512 words * 16 lines at 0xe0200000.

[   17.531250] omapdsp: found 5 task(s)

[   17.531250] omapdsp: task 0: name pcm3

[   17.531250] omapdsp: taskdev pcm3 enabled.

[   17.546875] omapdsp: task 1: name pcm_rec1

[   17.546875] omapdsp: taskdev pcm_rec1 enabled.

[   17.554687] omapdsp: task 2: name pcm1

[   17.554687] omapdsp: taskdev pcm1 enabled.

[   17.562500] omapdsp: task 3: name audiopp

[   17.562500] omapdsp: taskdev audiopp enabled.

[   17.570312] omapdsp: task 4: name pcm0

[   17.570312] omapdsp: taskdev pcm0 enabled.

[   17.710937] EAC mode: play enabled, rec enabled

[   18.421875] g_file_storage gadget: File-backed Storage Gadget, version: 28 November 2005

[   18.429687] g_file_storage gadget: Number of LUNs=2

[   18.429687] musb_hdrc musb_hdrc: MUSB HDRC host driver

[   18.429687] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file 'devices'

[   18.429687] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file '001'

[   18.429687] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

[   18.429687] musb_hdrc musb_hdrc: supports USB remote wakeup

[   18.429687] usb usb1: default language 0x0409

[   18.429687] usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1

[   18.429687] usb usb1: Product: MUSB HDRC host driver

[   18.429687] usb usb1: Manufacturer: Linux 2.6.21-omap1 musb-hcd

[   18.429687] usb usb1: SerialNumber: musb_hdrc

[   18.429687] usb usb1: uevent

[   18.429687] usb usb1: usb_probe_device

[   18.429687] usb usb1: configuration #1 chosen from 1 choice

[   18.429687] usb usb1: adding 1-0:1.0 (config #1, interface 0)

[   18.429687] usb 1-0:1.0: uevent

[   18.429687] hub 1-0:1.0: usb_probe_interface

[   18.429687] hub 1-0:1.0: usb_probe_interface - got id

[   18.429687] hub 1-0:1.0: USB hub found

[   18.429687] hub 1-0:1.0: 1 port detected

[   18.429687] hub 1-0:1.0: standalone hub

[   18.429687] hub 1-0:1.0: individual port power switching

[   18.429687] hub 1-0:1.0: no over-current protection

[   18.429687] hub 1-0:1.0: Single TT

[   18.429687] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)

[   18.429687] hub 1-0:1.0: power on to power good time: 10ms

[   18.429687] hub 1-0:1.0: 200mA bus power budget for each child

[   18.429687] hub 1-0:1.0: local power source is good

[   18.429687] hub 1-0:1.0: enabling power on all ports

[   18.429687] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/musb/tusb6010.c musb_platform_enable: dma not reactivated

[   18.546875] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file '001'

[   18.546875] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000

[   19.234375] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   20.546875] hub 1-0:1.0: hub_suspend

[   20.546875] usb usb1: usb auto-suspend

[   22.031250] EAC mode: play disabled, rec disabled

[   24.296875] EAC mode: play enabled, rec enabled

[   31.898437] EAC mode: play disabled, rec disabled

[   37.445312] Adding 131064k swap on /media/mmc2/.swap.  Priority:-1 extents:16 across:906532k

[   38.046875] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   43.171875] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   46.414062] cx3110x: loading 3826.arm firmware.

[   46.656250] (c)opyright 2004 Conexant

[   46.656250] 

[   46.656250] build info: PRISM SoftMAC

[   46.656250]   creator: [kvalo]

[   46.656250]   date: [07/10/05-11:45]

[   46.656250] 

[   46.664062] cx3110x: MAC address

[   46.671875] cx3110x: libumac version 2.12.0.0.a.9.15-5

[   46.671875] cx3110x: lmac version 2.13.0.0.a.22.8

[   46.671875] cx3110x: PSM disabled.

[   48.054687] cx3110x: scanned 11 channels.

[   48.578125] cx3110x: shut down softmac.

[   49.632812] cx3110x: loading 3826.arm firmware.

[   49.875000] (c)opyright 2004 Conexant

[   49.875000] 

[   49.875000] build info: PRISM SoftMAC

[   49.875000]   creator: [kvalo]

[   49.875000]   date: [07/10/05-11:45]

[   49.875000] 

[   49.882812] cx3110x: MAC address 

[   49.890625] cx3110x: libumac version 2.12.0.0.a.9.15-5

[   49.890625] cx3110x: lmac version 2.13.0.0.a.22.8

[   51.335937] cx3110x: scanned 11 channels.

[   53.843750] cx3110x: associated to 00:16:b6:da:58:97 (bcn 100 msec, DTIM 1).

[   54.210937] tahvo: Registering interrupt 2 for device 

[   55.257812] EAC mode: play enabled, rec enabled

[   58.898437] EAC mode: play disabled, rec disabled

[   59.218750] cx3110x: PSM dynamic with 200 ms CAM timeout.

[   61.703125] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[   61.937500] EAC mode: play enabled, rec enabled

[   65.382812] EAC mode: play disabled, rec disabled

[   73.554687] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  113.656250] cx3110x: PSM dynamic with 100 ms CAM timeout.

[  114.062500] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  126.429687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  156.617187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  166.531250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  176.812500] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  211.601562] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  216.617187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  271.625000] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  276.640625] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  331.617187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  336.632812] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  391.640625] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  396.656250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  451.632812] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  456.648437] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  571.750000] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  575.796875] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  580.914062] menelaus 1-0072: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)

[  586.531250] EAC mode: play enabled, rec enabled

[  590.140625] EAC mode: play disabled, rec disabled

[  591.531250] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  607.617187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  628.328125] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  647.710937] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  657.867187] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  753.937500] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  754.093750] cx3110x: PSM dynamic with 200 ms CAM timeout.

[  754.398437] EAC mode: play enabled, rec enabled

[  759.242187] EAC mode: play disabled, rec disabled

[  761.929687] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  812.039062] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  816.929687] cx3110x: PSM dynamic with 100 ms CAM timeout.

[  821.125000] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

[  824.320312] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)

qwerty12

2008-07-14 20:48

Re: Diablo not compatibile with my N800

[ 1.281250] VFS: Mounted root (jffs2 filesystem) readonly.

This doesn't look good to me. Partition table is changed in diablo, maybe new locationis corrupt?

Benson

2008-07-14 20:56

Re: Diablo not compatibile with my N800

No, that's fine. It initially mounts read-only, and only remounts read-write later after it determines that the filesystem doesn't need fscked.

Benson

2008-07-14 21:02

Re: Diablo not compatibile with my N800

BTW, bad medicine posting your MAC like that.... it's cool to scrub that sort of info from logs.

Might try booting with no SD cards in? It seems to be flailing around a lot setting the MMC bus voltages; don't know that that's a problem, though.

spirytsick

2008-07-14 21:18

Re: Diablo not compatibile with my N800

was actually thinking of that. I have tried already with or without the cards, does not make the difference.

spirytsick

2008-07-14 21:20

Re: Diablo not compatibile with my N800

now it just rebooted out of the blue. perhaps I should try the fridge treatment.

spirytsick

2008-07-14 21:29

Re: Diablo not compatibile with my N800

Guys, could I ask you a favour? If you have a moment can you take a peek at your dmesg messages to check if your N8x0 is also playing the MMC voltage dance ? I am starting to have a suspicion that all my problems might be related to a faulty battery after all.

Benson

2008-07-14 21:38

Re: Diablo not compatibile with my N800

Not like that, no. I only have one card in ATM. My 16GBer is in the laptop getting files dumped on it, but nothing like that from the 1GBer...

spirytsick

2008-07-14 21:59

Re: Diablo not compatibile with my N800

I have a spare E61 at work. Will swap the batteries yesterday and try it. I think there is a very good possibility that this is battery related as all the power n800 gets is runningh through the battery. That could explain why both and mmc boots fail sometimes (the mmc filesystem was prepared on my linux box, cloned from rootfs.jffs2 extracted from a flash and transferred to the sd card in a card reader - I md5sum'ed the whole lot and compared pc vs card - all checked out fine.

geneven

2008-07-14 22:30

Re: Diablo not compatibile with my N800

If good wishes help -- I hope it's a battery problem :)

spirytsick

2008-07-15 09:08

Re: Diablo not compatibile with my N800

Now i Switched it on and it's saying in red at the bottom of the screen

Rescuing software update, please do not iterrupt. This is with a new battery

spirytsick

2008-07-15 09:20

Re: Diablo not compatibile with my N800

Ok here's what happened.

I have put in a new battery from Nokia E61. The system booted from mmc without a problem. I then restarted and tried booting from flash. The message I mentioned in previous email have appeared. But then the unit booted fine from flash. I have however found those two lines in the dmesg log which are a bit worrying.

Code:

66.929687] JFFS2 warning: (1269) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -108

JFFS2 notice: (401) check_node_data: wrong data CRC in data node at 0x0abcbf70: read 0x72640e4c, calculated 0x455fbce5.

looks like flash to me but I am not an expert on that. Do errors creep up in jffs2 just like in every other filesystem ? Eg if the unit was switched off by taking the battery out ?

spirytsick

2008-07-15 09:24

Re: Diablo not compatibile with my N800

oh, btw, it looks like the "Rescue system update" message wiped off the initfs as I am no longer presented with the boot menu but the unit boots straight from flash. Gosh it's getting creepier and creepier.

igor	2008-07-15 11:27

Re: Diablo not compatibile with my N800

The jffs2 errors are ok, they should be leftovers from some of the previous random resets.

If nothing else shows up, you can forget about them.

The "Rescue system update" is completely new to me.

GeneralAntilles

2008-07-15 18:03

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by igor (Post 203141)

The "Rescue system update" is completely new to me.

Yes, it's apparently something SSU related for Diablo (it was mentioned a couple times on #maemo relating to browser states in recovery mode), but I've seen no real details on what it actually entails.

spirytsick

2008-07-16 14:39

Re: Diablo not compatibile with my N800

Ok I believe I have sorted the problem. It was after all one of the memory cards. I do not know whether one of them was damaged or simply partition table got corrupted but the N800 is running diablo with one card without a problem. As soon as I insert the second one, it starts going maaad. Very strange and very worrying and it should be noted for all those users who think that their device malfunctioned when in fact it was a memory card. Thank God for that! and thank you very much guys for your comments and suggestions. Without those I would have been without ny N800 now. Thanks

spirytsick

2008-07-16 22:01

Re: Diablo not compatibile with my N800

Few other revelations. For some reason my system will not boot if there are more than one partitions on each of the cards. It looks that if I have only single fat32 partition on either of the cards everything works fine. The moment I put in a card with more than one partition the hell breaks loose. Have you managed to successfully clone os to MMC for diablo ?

deeteroderdas

2008-07-25 13:03

Re: Diablo not compatibile with my N800

Quote:

Originally Posted by GeneralAntilles (Post 203257)

I just got this yesterday.

I rebooted for the first time in forever. (Actually, my battery ran down because the charger I plugged it into wasn't actually plugged into the wall outlet).

On reboot, I got the rescue message in red. Now, my multi-boot is gone. I started to restore it, but held off until I read more.

All times are GMT. The time now is 14:54.

vBulletin® Version 3.8.8