[Bug 1761611] Re: Incorrect dtb backup file

2018-04-10 Thread Adam Smith
Marking as invalid because on re-testing the server image I notice the
*2709*.bak is already in place.

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

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

Title:
  Incorrect dtb backup file

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761611] Re: Incorrect dtb backup file

2018-04-10 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1761611

** Tags added: iso-testing

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

Title:
  Incorrect dtb backup file

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761611] Re: Incorrect dtb backup file

2018-04-05 Thread Adam Smith
** Description changed:

  Testing the latest 18.04 raspberry server image on my pi 3.  I upgraded
  the kernel to the proposed version (from 4.13* to 4.15*).  Backups of
  the vmlinuz, initrd.img and dtb files were made on the system-boot
  partition automatically by flash-kernel.
  
  However, on closer inspection the bcm2709-rpi-2-b.dtb and
  bcm2709-rpi-2-b.dtb.bak files were the same file.  Similarly the
  bcm2710-rpi-2-b.dtb and bcm2710-rpi-2-b.dtb.bak were the same.  These
  files had changed between the 4.13* and 4.15* kernels and so they
- shouldn't be the same.  Both the .dtb and .dtb.bak are from the latest
- kernel (4.15*).
+ shouldn't be the same.  Both the *2710*.dtb and *2710*.dtb.bak are from
+ the latest kernel (4.15*).  Whereas the 2709 files are from the old
+ kernel (4.13*).
  
  The vmlinuz.bak and initrd.img.bak were correct.
+ 
+ This is possibly caused because I had to modify the server image to work
+ on the pi 3 (I manually copied the *2710*dtb file).  The problem may
+ correct itself on subsequent kernel upgrades.

** Description changed:

  Testing the latest 18.04 raspberry server image on my pi 3.  I upgraded
  the kernel to the proposed version (from 4.13* to 4.15*).  Backups of
  the vmlinuz, initrd.img and dtb files were made on the system-boot
  partition automatically by flash-kernel.
  
  However, on closer inspection the bcm2709-rpi-2-b.dtb and
  bcm2709-rpi-2-b.dtb.bak files were the same file.  Similarly the
- bcm2710-rpi-2-b.dtb and bcm2710-rpi-2-b.dtb.bak were the same.  These
+ bcm2710-rpi-3-b.dtb and bcm2710-rpi-3-b.dtb.bak were the same.  These
  files had changed between the 4.13* and 4.15* kernels and so they
  shouldn't be the same.  Both the *2710*.dtb and *2710*.dtb.bak are from
  the latest kernel (4.15*).  Whereas the 2709 files are from the old
  kernel (4.13*).
  
  The vmlinuz.bak and initrd.img.bak were correct.
  
  This is possibly caused because I had to modify the server image to work
  on the pi 3 (I manually copied the *2710*dtb file).  The problem may
  correct itself on subsequent kernel upgrades.

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

Title:
  Incorrect dtb backup file

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs