maemo.org - Talk - N800 Unable to run Diablo

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

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

- - N800 Unable to run Diablo (https://talk.maemo.org/showthread.php?t=29225)

N800 Unable to run Diablo

I've had this pretty much since diablo was released but I feel I need to upgrade now. The problem is that my N800 tablet will not run diablo correctly. I have flashed the device numerous times to no avail.
Here is what happens.

Flashing always completes successfully.
The Tablets then reboots
The booting process starts as normal
Then most of the time either a lifeguard reset is triggered and the device reboots or..
The desktop loads but either the gui is corrupted or the tablet resets after a while.
Flashing back to chinnok and everything works out of the box.

I am utterly frustrated because I simply cannot find the underlying cause.
I have changed, usb cables, memory cards, batteries but it has no effect whatsoever. I doubt the device hardware is faulty as the chinook works ok. I hope someone will be able to shed light or offer a solution. Thanks a lot in advance.

Additionaly, I have noticed that my N800 will start the flashing process regardles of the home button being held during the power up phase or not. Sadly I do not know if that is normal since I have no other device to compare with.

Re: N800 Unable to run Diablo

Try flashing it with "--enable-rd-mode --set-rd-flags=no-lifeguard-reset". Also (just checking) are you flashing RX-34_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin (from http://tablets-dev.nokia.com/nokia_N800.php) and have you checked that its md5sum matches the published one?

Re: N800 Unable to run Diablo

I did all that, I have also tried to use usb networking and ssh server to monitor the boot process but it did not yield any useful information (random parts of boot process failing). I am not sure, perhaps I need to have the device cold flashed but then again will it change anything ? I don't know.

Re: N800 Unable to run Diablo

If you can get Diablo running long enough, look at the output of dmesg in case it contains any hints. Another thing to try might be to flash a slightly earlier version and if that works do an SSU update to the current one.

Re: N800 Unable to run Diablo

Quote:

Originally Posted by spirytsick (Post 291853)

Additionaly, I have noticed that my N800 will start the flashing process regardles of the home button being held during the power up phase or not. Sadly I do not know if that is normal since I have no other device to compare with.

If I understand you correctly, then I will say this is very not normal.

Re: N800 Unable to run Diablo

Quote:

Originally Posted by Thesandlord (Post 292053)

If I understand you correctly, then I will say this is very not normal.

All guides to flashing say: (linux flasher)

start flasher as root .

Once the flasher is waiting for the usb device.

one need to hold the home button and then power up the device.

The flashing then will start.

In case of my N800 i only need to power up the device. The flasher then begins flashing.

Once again, don't know if this is normal.

Re: N800 Unable to run Diablo

Quote:

Originally Posted by spirytsick (Post 292070)

In case of my N800 i only need to power up the device. The flasher then begins flashing.

Once again, don't know if this is normal.

If the USB cable is in and you power up the tablet, then it will wait in USB mode automatically.
Only thing I can think of (and I may be talking out of my *** here) is that your flash is slightly damaged and it only shows when installing Diablo because the partition tables, for the flash, are modified and 2MB is given to the initfs and the rootfs' space gets decreased by 2MB. By shifting back 2MB, some files are getting installed in an area where the flash is dodgy.

Re: N800 Unable to run Diablo

Quote:

Originally Posted by lma (Post 292052)

I have tried that, there are no error messages, just normal log entries.

I have also done the following:

1. Unpacked rootfs from the flash image
2. Mounted it on ubuntu
3. Cloned it to the memory card (already partitioned)
4. Was able to boot from flash for long enoug to be able to install bootmenu.

booting from the card worked ok but after few restarts it stopped working.

I am attaching the dmesg and 'ps aux' output from the boot attempt (from sd card)

BTW... disable-lifeguard-resets switch does not help. the device will simply stop loading (os still works though as I am able to ssh over wifi but desktop does not work) displaying either nokia screen or white screen.

/var/lib/dsme/lifeguard* files output below:

lifeguard_resets:

Code:

usr/bin/hildon-desktop  :  10 

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

/usr/sbin/ke-recv :  11 

/usr/bi

and lifeguard_restarts:

Code:

/usr/bin/hildon-desktop  :  10 

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

/usr/sbin/ke-recv :  11 

/usr/bin/matchbox-window-manager -theme echo -use_titlebar yes -use_desktop_mode plain -use_lowlight no -use_cursor yes -use_dialog_mode static -use_super_modal yes :  2 

/usr/sbin/multimediad  : 1 

/sbin/mce --force-syslog  : 1 

/usr/bin/systemui :  10 

/usr/bin/mediaplayer-engine :  10 

/usr/bin/metalayer-crawler -F :  2 *

Re: N800 Unable to run Diablo

Quote:

Originally Posted by qwerty12 (Post 292071)

It has crossed my mind too but it does not explain why it runs sometimes and also why it has problem running from the memory card as well.

I might investigate flashing it back to chinook and then prepare a diablo versioned kernel and initfs with enough stuff removed to fit into the smaller initfs and kernel space. But I haven't got too much spare time on my hands atm.

Re: N800 Unable to run Diablo

Quote:

Originally Posted by spirytsick (Post 292074)

I have tried that, there are no error messages, just normal log entries.

That's missing the first second or so, which may contain interesting flash initialisation messages. There's an init script attached to bug 2770 that captures dmesg as early as possible.

This entry looks suspicious however:

Code:

[ 1.250000] Empty flash at 0x001d88e0 ends at 0x001d9000

Never seen that on mine. That area seems to be in the config partition, which you can't flash AFAIK, but 0xFFFF will let you dump it at least.

Do your /proc/partitions & /proc/mtd looks like this?

Code:

major minor  #blocks  name



  31     0        128 mtdblock0

  31     1        384 mtdblock1

  31     2       2048 mtdblock2

  31     3       4096 mtdblock3

  31     4     255488 mtdblock4

Code:

dev:    size   erasesize  name

mtd0: 00020000 00020000 "bootloader"

mtd1: 00060000 00020000 "config"

mtd2: 00200000 00020000 "kernel"

mtd3: 00400000 00020000 "initfs"

mtd4: 0f980000 00020000 "rootfs"

Re: N800 Unable to run Diablo

Quote:

Originally Posted by lma (Post 292083)

Code:

[ 1.250000] Empty flash at 0x001d88e0 ends at 0x001d9000

Never seen that on mine. That area seems to be in the config partition, which you can't flash AFAIK, but 0xFFFF will let you dump it at least.

Do your /proc/partitions & /proc/mtd looks like this?

Code:

major minor  #blocks  name



  31     0        128 mtdblock0

  31     1        384 mtdblock1

  31     2       2048 mtdblock2

  31     3       4096 mtdblock3

  31     4     255488 mtdblock4

Code:

dev:    size   erasesize  name

mtd0: 00020000 00020000 "bootloader"

mtd1: 00060000 00020000 "config"

mtd2: 00200000 00020000 "kernel"

mtd3: 00400000 00020000 "initfs"

mtd4: 0f980000 00020000 "rootfs"

Mine /proc/partitions is:

Code:

 31     0        128 mtdblock0

  31     1        384 mtdblock1

  31     2       2048 mtdblock2

  31     3       4096 mtdblock3

  31     4     255488 mtdblock4

 254     0    8009728 mmcblk0

 254     1    2097151 mmcblk0p1

 254     2    5388288 mmcblk0p2

 254     3     524288 mmcblk0p3

 254     8    7864320 mmcblk1

 254     9    7864312 mmcblk1p1

and /proc/mtd:

Code:

dev:    size   erasesize  name

mtd0: 00020000 00020000 "bootloader"

mtd1: 00060000 00020000 "config"

mtd2: 00200000 00020000 "kernel"

mtd3: 00400000 00020000 "initfs"

mtd4: 0f980000 00020000 "rootfs"

the dump from 0xFFFF below:

Code:

Dumping firmware pieces to disk.

Fiasco version:  2

Name: OSSO UART+USB

Name: 1 RX-34_DIABLO_5.2008.43-7_PR_MR0

 kernel

   offset:  0x0000003b

   size:    1536640 bytes

   hash:    b126

   version-length: 20

   version: 2.6.21-200842maemo1

   sub-version: 2.6.21-200842maemo1

   name: kernel-2.6.21-200842maemo1

   body-at:   0x0000006f

==> ((null)) kernel-2.6.21-200842maemo1

Skipping 36 padding bytes

 initfs

   offset:  0x00177312

   size:    2327808 bytes

   hash:    8f98

   version-length: 26

   version: 0.95.22-200842maemo1w38b3

   sub-version: 0.95.22-200842maemo1w38b3

   name: initfs-0.95.22-200842maemo1w38b3

   body-at:   0x0017734c

==> ((null)) initfs-0.95.22-200842maemo1w38b3

 rootfs

   offset:  0x003af84c

   size:    138149888 bytes

   hash:    382e

   version-length: 44

   version: RX-34+RX-44+RX-48_DIABLO_5.2008.43-7_PR_MR0

   sub-version: RX-34+RX-44+RX-48_DIABLO_5.2008.43-7_PR_MR0

   name: rootfs-RX-34+RX-44+RX-48_DIABLO_5.2008.43-7_PR_MR0

   body-at:   0x003af898

==> ((null)) rootfs-RX-34+RX-44+RX-48_DIABLO_5.2008.43-7_PR_MR0

 2nd

   offset:  0x0876f898

   size:    8192 bytes

   hash:    9c5f

   version-length: 80

   version: RX-34

   sub-version: RX-34

   sub-version: 1301

   sub-version: 1302

   sub-version: 1501

   sub-version: 1502

   sub-version: 1503

   sub-version: 1504

   sub-version: 1601

   sub-version: 1602

   version-length: 20

   version: 1.1.16-200844maemo2

   sub-version: 1.1.16-200844maemo2

   name: 2nd-RX-34,1301,1302,1501,1502,1503,1504,1601,1602-1.1.16-200844maemo2

   body-at:   0x0876f91e

==> ((null)) 2nd-RX-34,1301,1302,1501,1502,1503,1504,1601,1602-1.1.16-200844maemo2

 xloader

   offset:  0x0877191e

   size:    9088 bytes

   hash:    95ac

   version-length: 80

   version: RX-34

   sub-version: RX-34

   sub-version: 1301

   sub-version: 1302

   sub-version: 1501

   sub-version: 1502

   sub-version: 1503

   sub-version: 1504

   sub-version: 1601

   sub-version: 1602

   version-length: 20

   version: 1.1.16-200844maemo2

   sub-version: 1.1.16-200844maemo2

   name: xloader-RX-34,1301,1302,1501,1502,1503,1504,1601,1602-1.1.16-200844maemo2

   body-at:   0x087719a4

==> ((null)) xloader-RX-34,1301,1302,1501,1502,1503,1504,1601,1602-1.1.16-200844maemo2

 secondary

   offset:  0x08773d24

   size:    99072 bytes

   hash:    3715

   version-length: 80

   version: RX-34

   sub-version: RX-34

   sub-version: 1301

   sub-version: 1302

   sub-version: 1501

   sub-version: 1502

   sub-version: 1503

   sub-version: 1504

   sub-version: 1601

   sub-version: 1602

   version-length: 20

   version: 1.1.16-200844maemo2

   sub-version: 1.1.16-200844maemo2

   name: secondary-RX-34,1301,1302,1501,1502,1503,1504,1601,1602-1.1.16-200844maemo2

   body-at:   0x08773daa

==> ((null)) secondary-RX-34,1301,1302,1501,1502,1503,1504,1601,1602-1.1.16-200844maemo2

I will have to compile 0xFFFF for maemo but I have no scratchbox installed atm. Will have to download and try that to dump the hidden bit.

Re: N800 Unable to run Diablo

If this is too stupid, or shows total misunderstanding, just ignore it. But maybe try going to a Windows PC and using the standard Windows automatic Nokia Internet Tablet Software Update Wizard.

Re: N800 Unable to run Diablo

Quote:

Originally Posted by GeraldKo (Post 292221)

If this is too stupid, or shows total misunderstanding, just ignore it. But maybe try going to a Windows PC and using the standard Windows automatic Nokia Internet Tablet Software Update Wizard.

I wish it was so easy. Unfortunately, it does not work either. But thanks for trying to help.

Re: N800 Unable to run Diablo

Keep Chinook and be happy. Get a second n800 for Diablodebianubuntumoblinmerandroid.