Another Kein System

mak11

Inactive User
Joined
Feb 6, 2006
Messages
277
Reaction score
4
Location
In the Pub!!
Hi peeps, sorry but another kein system thread.
I have searched and searched and read and read and then read some more. Been at this for 2 days now.
My mate bought a nokia dbox2 round saying it was working fine then all of a sudden it's started to show "kein system" on boot up.
I've tried different ifa versions including the latest one and I've tried about 6-7 different images but still no good.
Would someone be kind enough to have a look at this log file for me and see if there's anything obvious showing?
I've no reason not to believe my mate that this was working a couple of days ago, so apart from flashing the wrong image on a box what else can cause the Kein System?
Many thanks for reading

MaK
 
Are you sure you are using a 2ximage for the nokia?
 
Are you sure you are using a 2ximage for the nokia?

Yes I am mate, same images has I have on my Nokia.
I've just grabbed another log from a different version of ifa if it helps
Thanks for looking mgb.
If it makes any difference mate when I normally flash my image I get a pic come up on screen showing hallenberg and stuff, with this box all i get is a weird fuzzy picture with mixed up colours everywhere
Regards
MaK
 
i used only an ethernet cable with nokia dbox2 and ifa m8

That's what i normally just use to on my box, but because i couldnt get this one going i got a serial cable off said mate so i could post the log and in the hope that it might work with it.
I'm at a total loss what it could be and am hoping someone can work it out from the logs I've posted.....
Thanks
MaK
 
It looks like a hardware fault.
Either cpu or ram.
Hold down the up arrow button at the box, let it pressed and plugin your box.
Check the results of the memory test in the bootlog.
 
Last edited:
Right mate, the top bit of the log is when i now try ifa after having tried the flash with just the null modem cable on its own.
The bottom bit is the memory test I just done.
Have I made it worse? I'm not getting kein system anymore just the team commando logo and "loading kernel" on lcd??
Thanks
MaK
 
The ram looks ok.
Unplug the box and let the thing cool down. If the box is cold try it again to start the box.
 
Sorry mgb, ignore the first bit of that log file. I forgot to put the xover cable back in sorry.
I'll post the new one in a couple of minutes.
Thanks for all your help thus far mate
Regards
MaK


Edit: added logfile
 
Last edited:
Right this is starting to do my head in.
Wouldn't go past the loading kernel screen so i flashed yet another image on using xover & null, guess what? Yes the bloody thing has gone back to kein system!!

This is the lastest log
 
It seems to me its not loading the full image on .
Were it say's loading o ###############
You should get about ten lines of ##########
Not just 2 as your getting. Could be a knackered intel chip.
 
Right this is starting to do my head in.
Wouldn't go past the loading kernel screen so i flashed yet another image on using xover & null, guess what? Yes the bloody thing has gone back to kein system!!

This is the lastest log
Thats a flashlog you have posted from it
Board: ### No HW ID - assuming TQM8xxL
Does not seem to be recognising its a nokia board to me.
 
Sorry but is there any chance I could have that in plain English lol
Is this box ready for the bin do you think?
Thanks
MaK
 
Sorry but is there any chance I could have that in plain English lol
Is this box ready for the bin do you think?
Thanks
MaK
Thanks to speedy for this.

Board: ### No HW ID - assuming TQM8xxL

The presence of the above line pretty much confirms that the box has a hardware problem, and is not likely to boot (unless its something like a dry solder joint - in which case the box may appear to be 'tempermental').

Failing to detect the board ID means that there is a problem somewhere along the line with the mainboard itself, and nothing like the tuner. It's unlikely to be a problem with the flash chips unless it is blocking a bus that responds to a critical interrupt.

As a secondary confirmation method to my theory you can look at the way the box is processing its bootup - nothing works from internal flash (this could be because the chips are empty or their contents are corrupt (Again, possibly from a mismatch on the motherboard, or something has gone wrong with the I/O)).

However, the box does seem to spring into life when it is attempted to be flashed. The BOOTP and TFTP complete successfully, but upon loading ppcboot into memory the 1st stage bootloader decides to fail, therefore branching back to 0x40000.

If the box is to ever work again without replacing components on the board then it will be a miracle(or like i said, maybe a dry solder joint or something as simple as that).
 
Many thanks for your reply mate, not sure if I understood all of it but I think i get the gist of it.
Can I just say thanks to all the guys who replied and tried to help. I'm just gona give the box back to my mate and let him do what he wants with it.
Thanks again
MaK
 
Back
Top