> In the past I've done exactly what you have done with success. The > only difference is that I always made sure my developement host and > target were running the exact same version of libraries. Dunno if > thats the problem here but subtle library issues can cause really > strange behavior.
I'll look into it. They should be based on the same version from what I can tell. Mostly it's statically linked, so there aren't many libraries. > > My only other think I can think of is to try to start with a clean > known working LEM and only upgrade 1 piece at a time until you find > out what change causes the problems. The only upgrade I have done is a 2.4 kernel (there is no kernel provided) and tinylogin, which was done after it was already broken. > > One more thought just occured to me... There was a BUG fix in 2.4.3 > or so that changed the behavior of CREAD and requires a later version > of init. Usually though you don't get any characters at all for the > CREAD issue. > > Perhaps you should try installing a telnet deamon and see what > happens when you telnet to the box. That would let you figure out if > its a remote login deal in general or specifically something with > serial consoles. > Good in theory, but I can't get the box to pull an address from dhcp when it's on the embedded system. On the development system it works fine. Not sure if I've got the wrong netcard drivers or what, that's why I was trying to get the serial console working. If anything ever breaks I need to be able to get on the embedded system serial console. I can log on to the system via the development system console, but the embedded system doesn't have keyboard/mouse/video. -- To unsubscribe from this list, send a message to [EMAIL PROTECTED] with the command "unsubscribe linux-embedded" in the message body. For more information, see <http://waste.org/mail/linux-embedded>.
