Quoting Michael Hope <michael.hope(a)linaro.org>:
On Thu, Jun 9, 2011 at 3:53 AM, <omalleys(a)msu.edu> wrote:
> Quoting Chris Tyler <chris(a)tylers.info>:
>> On Wed, 2011-06-08 at 14:29 +0200, Jan Kratochvil wrote:
>>> On Mon, 06 Jun 2011 10:04:13 +0200, Jaromir Capik wrote:
>>> > In both cases the boot gets frozen once the following line appears:
>>> > Enabling /etc/fstab swaps: [ OK ]
>>> I tried all of the F13 beta1, beta2 and beta3 and all behave the same.
>>> F12 works OK.
>>> In fact I found the F13 beta* system is running perfectly - just no
>>> gettys get
>>> run by default on either console or ttyS0.
>> There seems to be an issue with the default udev getty config on some
>> boards and also with qemu. The armvm RPMs I created have a horrible
>> quick hack around this, but we need to solve it (which is a matter of
>> someone finding some time to poke at it).
> Does the same issue happen with Ubuntu? Im just wondering if you could
> copy the conf files over and test to see if they work, and if so,
> compare them. It might be the fastest way to isolate it.
It's probably unrelated, but keep an eye out for the serial device
name on later OMAP kernels. They added a new OMAP specific driver
which changed the device name from ttyS0 to ttyO0. This also exposed
problems with the QEMU OMAP serial port model.
You might want to try qemu-trunk or qemu-linaro.
It is good information. I haven't tried 13 the recent beta yet. But
the first one I needed to copy the device (/dev ) files from the F12
base image into the F13 base image before console worked at all. I
assume this is what Chris's rpm does.
I was just wondering if it was fixed somewhere already. Or if not
whether it was a udev or qemu serial port issue. Kind of like the
crashing if you allocate too much ram to it. (like >128M )
Are you getting OMAP to work on qemu? If so how? I don't think I tried
OMAP, but I tried several combo's that didn't work. (I was tyring to
give it more ram to speed it up..)