Hello, On Sat, Feb 12, 2011 at 05:31:10PM +0100, Sven Radde wrote: > Am 11.02.2011 09:35, schrieb Lluís Batlle i Rossell: > I only have a "plug:green:health" there and it appears that I can use > that to turn off the blue LED (sic!) (meaning that the green one shines > through again, since it is too weak to be really noticed as long as the > blue LED is on). > Since they are software-controlled, does Debian associate any meaning > with them? Or are they all turned on after boot "just because"? I've no idea about Debian.
> The bootcmd looks fine (and works flawlessly when entering "boot"). > > This is the error message when connecting to the plug via serial console > after a "cold" boot: > Unknown command '0`3▒▒~000▒▒0`3▒▒~000▒▒0`3▒▒~000▒▒x▒~x▒~' - try 'help' It may be that the serial line communications program you use is sending things when you start it. If uboot receives anything, it will interrupt the boot sequence. > I noticed that there are quite a lot of error messages in dmesg after > booting Debian: > end_request: I/O error, dev mtdblock0, sector 0 > Sector 0 is by far the most frequent message, but there are also a few > relating to sectors 8, 64 and 128. > > Could there be a connection (i.e., does uboot try reading from mtdblock0 > to get the bootcmd and sometimes receives corrupt data)? I also can't read the mtdblock0 from Linux. I don't think it is any related to your boot problem. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
