Hi Daniel,

Thanks for the help

I am now able to login to my console system, but when I try to configure wireless as I did for the desktop image, and then use ifup wlan0
and so on to connect, nothing happens. when I scan for networks I see the blue light on for a sec during the scan, but I can't connect permanently.

Is there any difference I need to know about when configuring console rather than desktop images?



On 21 November 2011 20:13, Daniel Packard <daniel@roadnarrows.com> wrote:
Hi Nick,

On your SD card, check  /etc/inittab

For us, we found that line 31 of /etc/inittab needed to be changed to play nicely with our Overo Fire using version 2.6.34 of the kernel.

S:2345:respawn:/sbin/getty 115200 ttyO2
S:2345:respawn:/sbin/getty 115200 ttyS2

Hope that helps  you out!

Daniel Packard
RoadNarrows Robotics

On Sat, 2011-11-19 at 16:59 +0200, Nick Starzicki wrote:

I have recently been working on my gumstix with a desktop image, but
a project of mine runs really slow on it, and I therefor tried a console image instead.
The problem is that after I built my bootable sd card with the console image and wanted to start installing my files,
I got the image that can be seen in the attachment. From there I could not continue doing anything. What could be the problem?
Also, when I connect to an HDMI connection, I do see the login screen. However, I have no way of controlling anything there (have no usb keyboard to check).
Finally, via serial connection (in the window that i attached), I cannot type anything once it gets stuck on the screen.

Any Ideas?



All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
gumstix-users mailing list