On 12/18/2010 11:37 PM, Andrew Burgess wrote: > another tack is to change the baudrate in minicom. try 9600 to start, > it's common. > > the theory (i think) is that your kernel reprogrammed the serial > port baudrate. That would imply that the kernel acquired from here: http://ftp.linux.org.uk/pub/linux/arm/fedora/platforms/sheevaplug/uImage-2.6.30-sheevaplug does that. Surely, if it does, somebody else would have noticed before me? I just tried booting the same kernel off tftp and if I do: setenv bootargs console=ttyS0,115200 tftpboot 0x6400000 uimage.bin bootm 0x6400000 The same thing happens - the server gets as far as decompressing OK, and then the console gets garbaged. If I don't setenv bootargs with the console setting, the console stays silent after the kernel decompresses, which implies that the problem is indeed connected to the kernel doing something wrong with the serial console settings. Is there an alternative kernel I could try? Gordan _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
