Re: Use netconsole to troubleshoot uBoot without a serial cable

beausoleil,

> root@debian:~# fw_printenv
> Warning: Bad CRC, using default environment
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
> ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:$
> {hostname}::off; bootm
> bootdelay=5
> baudrate=115200
> root@debian:~#
>

This is because you're running an older version of U-Boot. This version probably defines the envs at a different location than 0xC0000. At this point, you have 2 different options:

1. Update U-Boot to the current version by running Jeff's script, see http://projects.doozan.com/uboot. This will allow you to take advantage of newer features.
2. Find out where your U-Boot defines the envs and then modify /etc/fw_env.config. This is a very safe thing to do, since you already running Debian.

With no serial console, updating U-Boot has some small risk. However, Jeff's script is the most reliable way to update your u-Boot, so I would do that. Just remember don't reboot if you see any error during the script execution, post the log here if that happens. And also, your u-Boot envs will be very different, your netconsole will need to be set up again.

After updating u-Boot, setup netconsole right away before rebooting. Again, if anything goes wrong during updating u-Boot, you will need serial console.