15 replies to this topic

[macnuts]

The following was observed on the DM8000 box with openpli 2.1 11.11.2011 nightly build. The SSL is v. 84.

The latest image that can be successfully flashed on DM8000 is dated 12.11.2011.

Nightly builds dated 13, 14 and 16 Nov. 2011 are broken.
I was able to flesh them via www (in dm stop mode). But on first reboot:
1. It seems ok at first, the initial message on the DM display with "/flash/vmlinux.gz" and the openpli bootlogo @ 1080i on TV.
2. After some time, the bootlogo disappears, the TV display is black, still "/flash/vmliniux.gz" on DM display.
3. After a second or two, the TV switches to 720p (still black), DM display turns black as well.
4. Nothing more happens till I turn off the DM power switch. While booting the image dated 12.11.2011, after a next second or so, the DM display shows: "Dream Multimedia" and progress bar, and there is a bootlogo @ 720p onTV.

The major update to image from 12.11 to 13.11 was the dreambox-dvb-modules update. Can it be the cause of the problems?

Note, that I can flash 12.11 image and opkg update; opkg upgrade without any problems.

Regards.

[Erik Slagter]

Can you please attach a serial cable, change the console to serial and try again? This looks like something that can be debugged using serial.

Also, do you have any autobackupped settings that are autorestored?

[macnuts]

No autobackup at all.

No serial port on my computers too, unfortunately. I will try to get one today.

Forgot to mention that I was able to flash successfully "DM official" images, both latest release and experimental.Just to check if I can flash anything new.

Edited by Orzes72, 18 November 2011 - 14:04.

[macnuts]

Attached are logs from putty console. Each log has entries for the same actions:
1. Start the DM and put it into STOP mode.
2. Flash the DM via web.
3. Press Reboot button on web page after flashing.
4. Log what happens after reboot.

The logs were generated for the nightly builds with dates: 12.11.2011 (last successful flash) and 18.11.2011 (example of failed boot).

Note, both logs are pretty the same. See the diffs here:

--- 2011.11.12_Flash+boot.log
+++ 2011.11.18_Flash+boot.log
@@ -1,4 +1,4 @@
-
+
BCM97400
AB
FFFFFFFF
@@ -42,9 +42,9 @@
skipping non-DOS partition 0
P 00 0 0 < 3897344
partition 1 is invalid! assuming wholedisk partition
-++++++++++++++++++UUUUUU++++++++++++++++++++++++++++++++
+++++++++++++++++++UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
dreamupd initialized
-Scanning JFFS2 FS:   .  | / - \ | / - \ | / .  .  - .  .  .  \ .  | / - \ | / - \ | / - \  done.
+Scanning JFFS2 FS:   .  | / - \ | / - \  done.
find_inode failed for name=secondstage.conf
load: Failed to find inode
  - failed to open /boot/secondstage.conf

Logs:
[attachment=44715:2011.11.12_Flash+boot.log]
[attachment=44716:2011.11.18_Flash+boot.log]

[littlesat]

I suggest Bad blocks in the flash...

Edited by littlesat, 19 November 2011 - 11:33.

[pieterg]

log is disabled, around the time the problem occurs:

Kernel command line: root=/dev/mtdblock3 rootfstype=jffs2 rw console=null

you need to modify the cmdline (in the bootloader settings screen), to:

root=/dev/mtdblock3 rootfstype=jffs2 rw console=ttyS0,115200

[macnuts]

Silly me.

Here come new logs. For 12.11.2011 nightly buid, I stopped logging while first wizard screen was on TV.

Regards.

[attachment=44718:2011.11.12.log]
[attachment=44719:2011.11.18.log]

[pieterg]

seems to crash just around the time that the drivers are starting to output log messages in the 11.12 version.

I assume it's one of the problems caused by the new drivers.
We've just reverted to the 20110902 version, could you try to flash todays build, and see whether that 'fixes' your problem as well?

[macnuts]

Ok, I will try them but later tonight (I have no control of the box right now ).

The new drivers could be updated to latest version after successful flash of 12.Nov build. I guess that will be no such option now (new drivers removed from the image/feed totally)? I ask because I have such personal feeling that they work better than 02.09 version (nothing I can point at, just my personal feeling).

The logs of successful boot are very consistent about the error in 18.Nov boot. I mean the lines are the same, looks like no concurrency at that stage (or very well serialized console output). I mean, each and every successful boot (regular one, after deep standby) has the same line order in the cosole log.

So I put here the next 10 lines after the 18.Nov stopped logging:

usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
usbcore: registered new driver r871x_usb_drv
4042711 ms:
No valid backup location, aborting auto-restore
VIDEO0: set blank to 0
sync is off so we enable it
playback!

Maybe it is not drivers but the extra usb driver or some change in auto-restore (when no valid backup location). I am just guessing now, please do not shoot at me . I just feel strange that the new drivers are the cause as I can update to them in console using opkg update; opkg upgrade) and can put the box to deep stanby (and switch it off) and reboot successfuly (I know I should change the thread tile somehow then).

Regards.

EDITED:
Corrected the bad image date to 18.11.

Edited by Orzes72, 19 November 2011 - 16:10.

[pieterg]

well, many 8000/800 users report the same thing, since the driver update.
And since we downgraded the drivers again this morning, I've already had 2 confirmations from users for which thing started working again.

So I'm pretty convinced it must have been the driver update.

But they confirm what you said; online update doesn't trigger the problem. Only after you flash the image, the problems occur.
I cannot explain that, but it seems the case.
Fact remains that with the 20110902 drivers, the problem didn't occur. And no longer occurs, in todays image.

[ims]

Could be added update to new drivers 20111109 as downloadable package (from whole package it are 3 .ko file only ) for users, who flashing boxes ?

[pieterg]

no, that's a lot of work (conflicting packages, messy bb files etc), users could simply replace the ko's if they wish.

[macnuts]

I flashed 19.11 build successfully.

After the flash, to get the newest drivers, I downgraded the openpli version with the ipk from dreamboxupdate and set the hold flag on that package. To have it work, I had to copy the /etc/modutils/dreambox into safe place and restore after downgrading. Without that, the reboot failed.

Here are the quick steps for all that love openpli, but would like to have the newest drivers:
1. Go to dreamboxupdate site and download the newest drivers dreambox-dvb-modules_2.6.18-7.4-dm8000-20111109-r0_dm8000.ipk. Put it into /tmp folder of your dreambox.
2. Execute the code:

cp /etc/modutils/dreambox /tmp # need to preserve this, boot failure otherwise
opkg install --force-downgrade /tmp/dreambox-dvb-modules_2.6.18-7.4-dm8000-20111109-r0_dm8000.ipk # returns warnings, but installs anyway
opkg flag hold dreambox-dvb-modules # package will not be updated on next opkg upgrade
cp /tmp/dreambox /etc/modutils/
update-modules

Once the openpli feeds have newest drivers again, just reset the flag to ok and opkg upgrade will do the rest.

One can argue, that simple copy is easier, I agree but you need a spare copy of the latest driver files (which was not my case).

Thank you for your support.

Regards.

Edited by Orzes72, 20 November 2011 - 02:31.

[Happysat]

Holding flags dont work, with the next update it will be overwritten....try it.
What does work is editing opkg-status file and decrease the driver version, so upgrade thinks its allready installed (old clone trick 2 preserve the drivers dito for the shitty 84 ssl )

[macnuts]

What do you mean by next update?

I tried: opkg update; opkg upgrade --noaction and still got the message:
Not upgrading package dreambox-dvb-modules which is marked hold (flags=0x2).

Edited by Orzes72, 20 November 2011 - 10:17.

[Happysat]

Mhh okay must have been my bad last time, gonna try it again.