After upgrading my Debian OS by apt-get, I decided to reboot. Since then, my Kurobox DIAG led flashes 6 times in red.

I have put out my HDD and used a Linux Live CD as to check the filesystem. Apart from messages indicaing that "The last mount time is on the future" for all the 3 partitions, there was no other message. I assume then that the filesystem is clean.

So ppc_uartd is left to be the suspect of that. The thing is, what do I do with that? Is it installed in the original HG's ROM or is it in the Debian installation? Is there any way to replace it, or this is not finally the point?

After upgrading my Debian OS by apt-get, I decided to reboot. Since then, my Kurobox DIAG led flashes 6 times in red.

I have put out my HDD and used a Linux Live CD as to check the filesystem. Apart from messages indicaing that "The last mount time is on the future" for all the 3 partitions, there was no other message. I assume then that the filesystem is clean.

So ppc_uartd is left to be the suspect of that. The thing is, what do I do with that? Is it installed in the original HG's ROM or is it in the Debian installation? Is there any way to replace it, or this is not finally the point?

Thanks a lot in advance.

Indicus

I had exactly the same problem like you on my kuro hg after doing apt-get upgrade. What I done is changed the loader.o to uboot, then upgrading the kernel to sylver's 2.6.20.1(uboot compatible and not loader.o). Then apt-get upgrade.
Everything is running absolutely fine now. If you want, I can post my dmesg.

It is getting really irritating...i managed to reinstall Debian again on the hdd, keeping my data untouched. Ive seen in another post, that loader.o is basically causing problems to booting. Am thinking of migrating to U-Boot. Is the U-Boot linkstation solution installed in the same way as described in the HOW U-Boot article by Sylver?

Andre: If I upgrade the shipped KErnel to 2.6 using your webinstaller, what will contribure to the corrupted loader.o ?

I ran into the same problem as you: I had a perfectly working Debian installation (Kernel 2.6.17 with loader.o) and too much time on my hands so i ran apt-get upgrade... After reboot 1) blinking power light 2) no boot 3) no clue how to fix it I would be still very interested in finding a way to fix it without complet reinstallation. Could I just disable the start-up script that loads the 2.6.20 kernel and stay with the original kernel in flash? If yes, what is the name of the script, I could not find it.

I restarted from scratch with a new HD, but I have again strange problems (apt-get installations hang with segmentation faults, etc.). In the end, I think uboot is the only way to go.

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum