Re: Debian Wheezy or Jessie install on Cubox-i4pro? -- Works!

[Karsten Merker <merker@debian.org>]

On Sat, Apr 04, 2015 at 05:03:55PM -0700, Rick Thomas wrote:
> On Apr 4, 2015, at 2:26 PM, Karsten Merker <merker@debian.org> wrote:

> > If this results in a working system, you can make this setting
> > permanent by running
> > 
> > setenv bootargs “console=ttymxc0,115200"; saveenv
> 
> Whoopie!
> 
> That did the trick.  It boots like a champ now!
> 
> Is there anything I can provide (log files, something else?) which will
> aid you-folks in your work?

Could you test a patch to the flash-kernel package? I have uploaded a
test-build of a modified flash-kernel package to

https://people.debian.org/~merker/flash-kernel/

To test the package, please perform the following steps:

- In the running linux system, install the following package:
  https://people.debian.org/~merker/flash-kernel/flash-kernel_3.35_armhf.deb

- Execute the "flash-kernel" command as root. This will update
  the boot script that is used to bring your system up.

- Reboot the system, stop the u-boot autoboot and run the follwing
  command at the u-boot prompt to remove the previously set
  bootargs variable: "setenv bootargs; saveenv"

- Reset the system.

If everything works as planned, the system should boot up normally
and not require setting the bootargs variable.

@Vagrant: I have done the same modification also to bootscr.wandboard
          as I assume that we will have the same problem there.
          Could you give it a try?  The diff to the flash-kernel
          package that is currently in the archive is at
          https://people.debian.org/~merker/flash-kernel/0001-Pass-console-variable-to-the-kernel-in-bootscr.cubox.patch

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.