Yes it has the console line.
Even if I wait an hour it will not show anything.
It is btw due to my own fault, before it did boot but the dhcp did not work, after some attempts due to underknowledgement on my side I seem to have broke something (hardware wise?)
But since I just got the console-vx today and was suprised it does show uboot and things actually seem ok.
So figured I could get it working but it does not tell me what is wrong.
My guess is that out of some frustration I was not carefull enough last time and damaged the ram orso, just would be nice to know for sure..
The mtest shows no error it seems..
And I can load a kernel over nfs.
Any clues/ideas are more then welcome, never really got to use this verdex...
----- Original Message -----
From: Craig Hughes
To: General mailing list for gumstix users.
Sent: Friday, August 31, 2007 8:24 PM
Subject: Re: [Gumstix-users] verdex stops at starting kernel...

On Aug 31, 2007, at 11:06 AM, Jean-Paul van de Plasse wrote:

Anyway I can find out what goes wrong if my verdex stops at "Starting kernel ..."
I tried a different kernel with some debugging enabled, but that does not show more.

Do you have the "console=ttyS0,115200n8" in your u-boot's bootargs?  If not, then it's probably running just fine, you're just not seeing any output because it's not being sent to the serial port.  If you wait a while, and still have the getty on ttyS0 in /etc/inittab, then eventually you'll get a login prompt.


This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

gumstix-users mailing list