[Bug 1026780] Re: 3.0~rc.4ubuntu4 doesn't honor bootargs from /boot/boot.script anymore

[Dave Jones]

Just going through the ancient bugs in flash-kernel and this is another
one I'm *fairly* sure was fixed at some point in the history (although
I'm unsure when). Anyway, the supported mechanism for injecting
parameters into the kernel cmdline via flash-kernel is to edit the
LINUX_KERNEL_CMDLINE or LINUX_KERNEL_CMDLINE_DEFAULTS parameters in
/etc/default/flash-kernel.

During its run flash-kernel *should* incorporate anything specified in
these variables into the kernel command line, typically by substituting
these values into the u-boot script prior to running mkimage.

There are a few cases where this *doesn't* happen, but they're largely
limited to those cases not using u-boot (the "Method: pi" case I added
is one such example, although there the kernel command line is a
trivially editable text file on the boot partition and I didn't want
people being surprised by their customization being overwritten so it
was a deliberate choice). Alternatively, there are some u-boot scripts
in f-k that don't contain the necessary substitution points.

Given this bug hasn't seen any activity for 8 years, and I'm fairly sure
it's fixed I'll set this to "Fix Released" but please set it back to
"New" if this is still an issue for you (and the aforementioned
variables in /etc/default/flash-kernel don't work in your case)!

** Changed in: flash-kernel (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/1026780

Title:
  3.0~rc.4ubuntu4 doesn't honor bootargs from /boot/boot.script anymore

Status in flash-kernel package in Ubuntu:
  Fix Released

Bug description:
  flag at ubuntu:~$ dpkg -l | grep flash
  ii  flash-kernel                     3.0~rc.4ubuntu4                utility to make certain embedded devices bootable

  flag at ubuntu:~$ cat /boot/boot.script
          fatload mmc 0:1 0x80000000 uImage
          fatload mmc 0:1 0x81600000 uInitrd
          setenv bootargs ro rootwait elevator=noop vram=40M mem=456M at 0x80000000 mem=512M at 0xA0000000 root=UUID=12e1a2ac-5c4e-41b0-94e3-0a4edeae18d1 fixrtc console=ttyO2,115200n8
          bootm 0x80000000 0x81600000

  flag at ubuntu:~$ sudo flash-kernel
  flash-kernel: installing version 3.4.0-201-omap4
  Generating kernel u-boot image... done.
  Taking backup of uImage.
  Installing new uImage.
  Generating initramfs u-boot image... done.
  Taking backup of uInitrd.
  Installing new uInitrd.
  Generating boot script u-boot image... done.
  Taking backup of boot.scr.
  Installing new boot.scr.

  flag at ubuntu:~$ sudo mount /dev/mmcblk0p1 /media

  flag at ubuntu:~$ cat /media/boot.scr
  'V�U�8mE3��dZ�boot script�fatload mmc 0:1 0x82000000 uImage
  fatload mmc 0:1 0x83000000 uInitrd
  setenv bootargs ro quiet splash
  bootm 0x82000000 0x83000000

  notice the absence of ALL the options i added to bootargs in
  /boot/boot.script like console to /media/boot.scr AFTER i ran flash-
  kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1026780/+subscriptions