Downgrade completed today, but I can't say anything yet. Sometimes it happend ten times a night, sometimes two days without error, so it's really random. If I have no image loss in two weeks I can say it should work.

Zitat von kwai

Kommt denn langsam Bewegung in´s Spiel ?

Habe leider auch das Problem, dass mein Samsung völlig unregelmäßig das Signal "verliert" Mal geht es 2 Wochen gut ohne einen Fehler und dann wie gestern 5 mal hintereinander. Das Problem tritt auch auf, wenn ich nur im Radio- oder Dateimodus bin. Auch ein Downgrade auf den besagten DVB Treiber brachte leider keine Abhilfe.

Die genauen Details von meinem TV werde ich heute Abend bekannt geben, da ich z.Z. auf der Arbeit bin.

Alles anzeigen

To test this theory I've hooked up a Aten HDMI Splitter. It had LEDs for: input, output 1, output 2.

When the screen goes black it is not the output 1 that is lost but the input side, so actually the Dreambox doesn't give a signal to the splitter anymore. Turning the DM800 in and out of standby resolves it: LED goes back on and we can watch tv again.

Zitat von Anton.Braun

try this (i told you some posts before):

Code

root@dm800:~# cd /tmp 


root@dm800:/tmp# wget http://dreamboxupdate.com/opendreambox/1.5/dm800/experimental/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk 
Connecting to dreamboxupdate.com[82.149.226.174]:80 
dreambox-dvb-modules 100% |*************************************************************************| 1388 KB00:00 ETA 


root@dm800:/tmp# ar -x dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk 


root@dm800:/tmp# tar xzf data.tar.gz 


root@dm800:/tmp# cp -R var/ / 


root@dm800:/tmp# md5sum /lib/modules/2.6.12-5.1-brcmstb-dm800/extra/bcm7401.ko 
793e8a4f01118605978b5f867054b364 /lib/modules/2.6.12-5.1-brcmstb-dm800/extra/bcm7401.ko 


root@dm800:/tmp# rm -rf control.tar.gz data.tar.gz debian-binary dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk lib/ 


root@dm800:/tmp# reboot

Alles anzeigen

There is no var/ in /tmp, so it won't do this: cp -R var/ /

I have the data.tar.gz

Unpacking it gives me:

. 
./lib 
./lib/modules 
./lib/modules/2.6.12-5.1-brcmstb-dm800 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/alps_bsbe2.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/dreambox_keyboard.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/alps_bsbe1_c01a.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/lcd.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/dreambox_rc2.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/LICENSE 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/fp.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/lnb_ctrl.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/stb-core.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/alps_bsbe1.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/cu1216mk3.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/bcm7401.ko 
./lib/modules/2.6.12-5.1-brcmstb-dm800/extra/tu1216.ko

No var/ directory.

Shouldn't var/ be lib/ ?

Zitat von Homey

you forgot one - infront of force-downgrade ....

do it that way:

Code

ipkg install --force-downgrade http://dreamboxupdate.com/opendreambox/1.5/dm800/experimental/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk

As I also own a Linux webserver I should have known. But that's Debian, so I don't use ipkg.

But now I get this (I did the remove line first):

root@dm800:/tmp# ipkg install --force-downgrade http://dreamboxupdate.com/opendreambox/1.5/dm800/experimental/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk 
Downloading http://dreamboxupdate.com/opendreambox/1.5/dm800/experimental/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk 
Installing dreambox-dvb-modules (2.6.12-5.1-brcmstb-dm800-20100104-r0) to root... 
Downloading http://*************/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20100104-r0_dm800.ipk 
Configuring dreambox-dvb-modules 
Collected errors: 
Multiple packages (dreambox-dvb-modules and dreambox-dvb-modules) providing same name marked HOLD or PREFER. Using latest. 
root@dm800:/tmp#

How about: -force-overwrite ?

--edit: tried that, same result. Even with --nodeps and --force-reinstall it just downloads it again.

Hmmm I think still not good:

mailto:root@dm800:/tmp# ipkg remove dreambox-dvb-modules Removing package dreambox-dvb-modules from root... root@dm800:/tmp# ipkg install -force-downgrade *.ipk Installing dreambox-dvb-modules (2.6.12-5.1-brcmstb-dm800-20100104-r0) to root... Downloading http://*************/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20100104-r0_dm800.ipk Configuring dreambox-dvb-modules Collected errors: Multiple packages (dreambox-dvb-modules and dreambox-dvb-modules) providing same name marked HOLD or PREFER. Using latest. root@dm800:/tmp# [/code]

root@dm800:/tmp# ipkg remove dreambox-dvb-modules Removing package dreambox-dvb-modules from root... root@dm800:/tmp# ipkg install -force-downgrade *.ipk Installing dreambox-dvb-modules (2.6.12-5.1-brcmstb-dm800-20100104-r0) to root... Downloading http://*************/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20100104-r0_dm800.ipk Configuring dreambox-dvb-modules Collected errors: Multiple packages (dreambox-dvb-modules and dreambox-dvb-modules) providing same name marked HOLD or PREFER. Using latest. root@dm800:/tmp#

mailto:root@dm800:/tmp# ipkg remove dreambox-dvb-modules Removing package dreambox-dvb-modules from root... root@dm800:/tmp# ipkg install -force-downgrade *.ipk Installing dreambox-dvb-modules (2.6.12-5.1-brcmstb-dm800-20100104-r0) to root... Downloading http://*************/dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20100104-r0_dm800.ipk Configuring dreambox-dvb-modules Collected errors: Multiple packages (dreambox-dvb-modules and dreambox-dvb-modules) providing same name marked HOLD or PREFER. Using latest. root@dm800:/tmp# [/code]

dreambox-dvb-modules_2.6.12-5.1-brcmstb-dm800-20090907-r0_dm800.ipk is in /tmp ofcourse.

Zitat von Anton.Braun

Direkt noch mal nachgefragt: Wie ist denn der aktuelle Status bei Dream Multimedia? Ist der Fehler eingegrenzt und ist ein Termin absehbar, in der der aktuelle Treiber ohne diesen Bug erscheinen kann?

It can never be the driver alone, as my other DM800 does not have this problem at all. Bought them together, same image, same everything.

Zitat von Anton.Braun

quality: i don´t know, but the quality could be better

howto: i had this problem, too - it seems to be caused by an non-official image. donwload the package manualy, use "ar -x" to unpack it an overwrite the original files of the newest package with these one (unpacked package).

I'll try this. I never used the original image, because it doesn't have the options for cable I need. May be fine for satellite, but I don't have sat.

Zitat von Anton.Braun

Ich kann nochmal ergänzen/bestätigen: Der Treiber von 20090907 läuft bei mir nun seit 5 Tagen ohne Signalverlust.

But with less quality?

And how did you keep that driver in? Mine always downloads the latest when I do the ipkg thingy.

Unfortunatly I have the same problem.

I bought 2 DM800C, one for myself, one for a friend.

Mine was fine all the way, my friend had lots of problems, so we switched cables, DVI > HDMI adapters, we even put HDMI amplifiers between it to test, other images, other drivers (it just downloads the new driver directly so that doesn't help) everything imaginable. He even brought his DM800 to me and I tested it, here it seemed to work just fine, so I thought.

We switched DM800s to test this really good and now: he doesn't have any problems, my DM800 is switching to black. Audio is still running (connected through optical toslink) and I have to switch HDMI channels back and forth so I will get an image again.

When this happens about 1/3 of the screen becomes cluttered with pink/purple stuff for a spilt second, then turns to black and the TV lost the signal all together.

So this is not a cable, tv, connector or any sort of problem: it's a DM800 problem as both DM800s were installed with the exact same image twice (tried 2 totally different images). One has the problem, the other doesn't.

When will this be solved and how?