*** This bug is a duplicate of bug 1652270 ***
https://bugs.launchpad.net/bugs/1652270
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke
*** This bug is a duplicate of bug 1652270 ***
https://bugs.launchpad.net/bugs/1652270
As of upgrading between 16.04 and 18.04.2 the fdt_addr has changed
again, I was able to fix this via the following, first cat boot.scr on
the primary partition, there's a bunch of binary at the start of the
*** This bug is a duplicate of bug 1652270 ***
https://bugs.launchpad.net/bugs/1652270
modprobe bcm2835-v4l2 crashes the system. I tried various thinks but
same. I could not use openCV to capture the images. However
raspicam_node (https://github.com/fpasteau/raspicam_node) able is
capturing
*** This bug is a duplicate of bug 1652270 ***
https://bugs.launchpad.net/bugs/1652270
** This bug has been marked a duplicate of bug 1652270
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't know about the breakage, but I was just bitten by this bug after
an upgrade, and #16 fixed the issue for me, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates
Has anyone else noticed that the #16 fix to this breaks the bcm2835-v4l2
driver? modprobe bcm2835-v4l2 crashes the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent
I spent most of the day last weekend re-writing my sdcard over and over
again trying to come up with some magic apt-get upgrade combination that
didn't brick the pi. I ended up accidentally overwriting a card I have
stuff I care about on. I want to personally thank whoever added the code
that
workaround in #16 worked. Thanks @mbirth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about this bug go to:
Workaround in comment #16 worked also for me, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about
Yes! By also setting the `device_tree_end`, I'm getting the correct MAC
address now, too. Thanks again @mbirth!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke
I just got access to that Raspberry Pi 3 again. I saw that the expected
fdt address now changed to 0x02008000 in the boot script.
In the config.txt, it was set as:
# set extended DT area
device_tree_address=0x100
device_tree_end=0x8000
So I changed it to:
# set extended DT area
** Changed in: flash-kernel (Ubuntu)
Assignee: Paolo Pisati (p-pisati) => Ryan Finnie (fo0bar)
** Changed in: linux (Ubuntu)
Assignee: Paolo Pisati (p-pisati) => Ryan Finnie (fo0bar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: flash-kernel (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage
Same for me. Using Ubuntu 16.04.1 LTS on a RasPi3.
Adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
to /usr/share/flash-kernel/bootscript/bootscr.rpi3 helped me, too. Thanks
@mbirth!
Also, I have the same issue with the MAC address. I'm currently using
macchanger to set it
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: flash-kernel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
I don't have access to the RasPi3 at the moment (due to the changing MAC
screwing with DHCP and port forwardings). I'll see what I can do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What's the content of /boot/firmware/config.txt?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about this bug
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry
@markus: not sure, i dont know how the non snappy images set the MAC,
technically if they use similar uboot scripts the MAC should come from
the first dtb snippet that is read from the ROM/closed bootloader, that
part should not be related to the actual dtb address at all...
--
You received this
** Tags added: armel regression-update xenial yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Recent updates broke Ubuntu on Raspberry Pi 3
To manage notifications about this
Could the missing fdt at 0x0200 be the reason, the RasPi now has a
different MAC address on each and every boot? Because I noticed this
after I got the boot process working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the newer firmware (start.elf,fixup.dat and bootcode.bin) hard-requires
0x0200 because it initializes the hardware differently in the newer
version...
looks like linux-firmware-raspi2 was not properly updated alongside with
flash-kernel and the kernel itself, there is a hard lockstep between
Also the official flash-kernel_3.0~rc.4ubuntu64_armhf.deb sets the fdt
address to 0x100 whereas 3.0~rc.4ubuntu64.1.1 from yakkety-updates sets
it to 0x0200. So it seems to be a regression in that package.
Downgrading to 3.0~rc.4ubuntu64 and running "sudo flash-kernel" works.
(Don't know why it
Upon further inspection: The flash-kernel from the rpi3 PPA
https://launchpad.net/~ubuntu-raspi2/+archive/ubuntu/ppa-rpi3 is only
published for Xenial and there, the boot script sets the fdt address to
0x100 instead of 0x200. And that works without explicitly loading
the fdt.
So it seems I
Downgrading the kernel or recently upgraded packages flash-kernel or
linux-firmware-raspi2 didn't work for me. But you can fix this
temporarily by editing /usr/share/flash-kernel/bootscript/bootscr.rpi3
and adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
after the line
It seems the FDT isn't loaded properly. I can boot the system if I load
the FDT manually and do the remaining steps from the boot.scr manually:
fatload mmc 0:1 0x0200 bcm2710-rpi-3-b.dtb
fdt addr 0x0200
fatload mmc 0:1 0x0100 vmlinuz
fatload mmc 0:1 0x0210
The actual problem happens earlier in the process than depicted in the
screenshot above:
Found U-Boot script /boot.scr
reading /boot.scr
412 bytes read in 13 ms (30.3 KiB/s)
## Executing script at 0200
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address
Same here. The update to 1021 breaks the boot and the only way to
recover is to rename all *.bak files back so it boots the older kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
29 matches
Mail list logo
