Console Image Questions

I will explain a problem I am having. I've been anxious to boot my own build (that is, bitbaked on my own machine) on the Beagle. And I also want to play with different images to see how they work and how I should work with them. I didn't want to use X with this particular try. I decided on the console image:

-rw-rw-r--. 1 rlc rlc 9182489 2010-01-30 20:39 Angstrom-console-image-glibc-ipk-2009.X-stable-beagleboard.rootfs.tar.bz2

and the modules

-rw-rw-r--. 1 rlc rlc 7156055 2010-01-30 20:44 modules-2.6.29-r46-beagleboard.tgz

I'm using a boot script file. These are the boot arguments I'm using:

  setenv bootargs 'console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait'

I don't really understand what the effect of the 'console=ttyS2' will be. Here is why:

To test my console image, first I start minicom running on the serial port. I have the HDMI cable connected from the Beagle to the DVI-D input on my monitor. The boot process seems to move along just fine. On my minicom screen, when booting finishes, the minicom screen shows this:

The Angstrom Distribution beagleboard ttyS2

Angstrom 2009.X-stable beagleboard ttyS2

and then when I switch the monitor to the DVI input from the Beagle, I see the Angstrom logo there and it is listed as ttyS1. But I can't log into this console. (I have a USB keyboard plugged into the hub.) I seem to have two consoles, ttyS2 on the minicom over the serial port and ttyS1 on my monitor over HDMI, but I'd really like to work with both, or if I don't use the serial port, then ttyS1. What am I doing wrong?




Make sure that your defconfig has HID drivers enabled. Without them, the USB keyboard doesn't have a driver (defconfig items - CONFIG_HID=y and CONFIG_HID_SUPPORT=y).

In your console log, you should see the keyboard detected, and a message that it's a HID device.


Hi Paul,

Which defconfig file is this? I searched them off and there are a lot of them.

Thanks a lot for the hint.


Robert L Cochran wrote:

Hi Paul,

Which defconfig file is this? I searched them off and there are a lot of them.

Thanks a lot for the hint.

That would be the one you're using to compile the kernel. It will be omap3_beagle...something. You'll probably have only a few of these, so you could just make the changes in all of them if you're not sure.