** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To
** Changed in: linux-raspi2 (Ubuntu)
Assignee: Ryan Finnie (fo0bar) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel
This is related to bug #1652504 and the answer #16 there is a more
detailed explanation of #65 above:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504/comments/16
As of 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
This might be related to bug #1791466
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notifications about this bug go
Just did a fresh install on RPi3 Model B.
Got struck by the `apt update & upgrade` bug, reinstalled and followed the
0x02008000 instructions successfully rebooted into an updated system.
After all updates, version is: 4.4.0-1086
Regards,
keijo!
--
You received this bug notification because
Sorry for the revival of this bug.
In this thread, I proposed solutions to unbreak the rpi3.
The truth is that I modified mine so much that it is stuck in version
4.4.0-1029-raspi2, although I have different "4.10-..." listed in my package
list.
I installed many things on it, and I do not want
There is no point getting narky about this. Yes its frustrating. This
bug should be assigned to the PPA Linux-firmware-raspi2 package, but
there is no facility to do that in Launchpad. You presumably have that
PPA enabled, therefore they (Ryan) are the only ones who can
automatically fix it.
Yes, as you can read I have managed to get it working but it is far
beyond capabilities of many users. They expect something different than
a regular update process unexpectedly bricking their devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For what it is worth I've been working on my own stuff
https://lists.ubuntu.com/archives/lubuntu-users/2017-August/011613.html
I don't use Ryan Finnie's server image, but to say it is unviable is
clearly untrue. A bit of user intervention is needed, but there is
nothing to stop you adding some
Adam Smith, I think we understand the risks of installing unofficial
image but there still could be something to think about in my comment
#23.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
@adamsmith
The patch you mention might be in image we download, but as soon as we
upgrade to a newer kernel with sudo apt-get dist-upgrade, this is when
we have the issue.
You say we shouldn't blame Ubuntu or Ryan, but someone is dropping the
ball on fixing this issue or submitting a patch
This bug hits rpi3 users who have downloaded an unofficial image. The
rpi packages you are using are from a PPA.
The official xenial versions of Flash-kernel and U-boot don't support
the rpi3. They do support the early versions of the rpi2 and for these
the original bug has been fixed.
Ryan
Meh! August 2017 - this is still an issue... looks like my brief
flirtation with Ubuntu on ARM is over - and back to Raspbian...
And JUST when I'd thought it was reliable and started running pi-hole on
it for a whole LAN :-(
--
You received this bug notification because you are a member of
The WiFi is not working because the firmware was removed from the
package. I already documented the problem in
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-
raspi2/+bug/1578745 but no reply and no fix also!
--
You received this bug notification because you are a member of Ubuntu
Note, after following Anthony's tip and doing an apt-get dist-upgrade,
wifi stops working :( - anyone have any ideas how to get wifi working on
the latest kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the RaspberryPi 3 Model B Vi.2
I installed the Lubuntu 16.04.2 from flavour-makers, because I want a graphic
interface for solving some problems sometimes...
Indeed, I think I read somewhere that the server version on this page was the
same than the one of Ryan Finnie... Sorry...
My
StatnMap, what RaspberryPi do you have? - I installed https://ubuntu-pi-
flavour-maker.org/download/ classic server 16.04 and ran apt-get update;
apt-get dist-upgrade and this has bricked by Raspberry Pi3.
Anthony's solution worked for me, thank you!
--
You received this bug notification
It seems that Ryan Finnie stopped maintaining this distro.
If you want to use (X)Ubuntu on your Raspi3, I recommend to install image of
ubuntu-pi-flavor-maker:
https://ubuntu-pi-flavour-maker.org/download/
It works greatly.
However, the use of boot is different from the one of Ryan Finnie, this
is now a bad time to say i've been apt updating for some time just fine
now, my previous instructions should still be accurate:
i can confirm that
To fix the uboot error, you have to change the config.txt lines:
# set extended DT area
#device_tree_address=0x100
#device_tree_end=0x8000
I consider this a dead distro. They SHOULD take it off the web
completely and save people a lot of time. Basically, it's a trap.
Someone, typically an Ubuntu user, is googling for a Raspberry distro
and this comes up in the results. Being a Ubuntu distro, it looks
trustworthy and familiar to the
We're seriously 4 months into a bug that renders a Pi completely
unusable and it's still not patched? Happened to me twice and it was
only after extensive Googling that I even found this bug.
Come on now, this is a critical issue.
--
You received this bug notification because you are a member
I take it this have not been fixed. I just tried installing ubuntu
again, ran apt-get upgrade; apt-get dist-upgrade, rebooted and it says:
ERROR: `server' not set. and Config file not found. and will not boot :(
Is there a permanent solution to this?
--
You received this bug notification
If you're stuck on "starting kernel", try replacing some of the files in
/system-boot/ with these: http://dl.free.fr/wqXsJ2Fq2 More details on
StatnMap's comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I followed the [corrected[ six steps of instructions. It failed to boot
at step #3 with the "SCRIPT FAILED" error and attempting to use TFTP. I
downloaded the original image again and repeated the instructions with
the same failure at step #3.
I attempted the test with both the image from:
Sorry, #6 should be done before #4. Just tested it, and it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage
... I assumed you can have a fresh install since you're mentioning
"first boot".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
Hi. Could you try to:
1) on first boot, hold packages that breakes our system:
$ sudo apt-mark hold linux-raspi2 linux-image-raspi2 linux-headers-raspi2
2) Do an upgrade:
$ sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade
3) Reboot:
$ sudo reboot
4) Unhold the packages
I had a non-conforming result:
I imaged an microSD card with ubuntu-16.04-preinstalled-server-
armhf+raspi3.img
I tested three methods of editing the config.txt file to apply the above
mentioned changes related to `device_tree_address=0x02008000`
Test #1: edited the file before first boot.
** Tags added: taipei-lab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notifications about this bug go to:
interresting Shuhao, a few week ago they where different!
http://web.archive.org/web/2016122818/https://ubuntu-pi-flavour-
maker.org/
They had a "minimal" and a "standard" server version and both were rpi2
and rpi3 compatible... damn...
--
You received this bug notification because you are
he images listed on ubuntu-pi-flavour-maker and the one listed on
https://wiki.ubuntu.com/ARM/RaspberryPi is exactly the same.
The same issue should exist on both systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I will definitely check it out.
Thank you very much, Andreas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage
I switch one of my pi3 to the server image from
https://ubuntu-pi-flavour-maker.org/
There you get pi3 support with working wifi and bluetooth. They do not include
any PPAs from Ubuntu, the do not use u-boot and boot like raspbian. You also
have to manually update your kernel via rpi-update.
I wonder how long it would take to issue official fix of a critical bug
when users already sorted it out themselves. The future of this
distribution looks very uncertain. That's the real message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can also confirm that editing config.txt worked, but I had to remove
the ppa (ppa:ubuntu-raspi2/ppa-rpi3) first.
If it can help somebody else, here is what I did.
I was stuck with the "starting kernel" message, just after boot.
1/ I removed the sd card from the raspberry and put it in another
I can confirm that editing the config.txt file BEFORE proceeding the
upgrade process solves it all. Very good job, sirs!
Unfortunately, one question remains. Is it really wise to invest time
into building and taking care of a system based on a distro that will
let you down and keep without any
I have looked a little deeper into the packages and have found the
script linux-firmware-raspi2.postinst inside linux-firmware-raspi2. The
script changes the device_tree_address in the config.txt from 0x0200
to 0x02008000
0x0200 is the value which is inside the config.txt on my raspi2.
i can confirm that
To fix the uboot error, you have to change the config.txt lines:
# set extended DT area
#device_tree_address=0x100
#device_tree_end=0x8000
device_tree_address=0x02008000
commented device_tree_end out and made sure device_tree_address was the
correct value (0x02008000)
fixes
Found it, in the system-boot partition. :) And it worked! Going to
unmark the 1040-kernel now on one of the cluster nodes now (easier to
just copy a node if something fails), to check if it boots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can i ask where this config.txt file is located?
I experience this bug now, so I dont know if it's related to the topic
here, or if its a new one. Haven't installed the "broken" kernels (1038
or newer), and it have working flawlessly - until I rebooted yesterday.
Now I'm stuck in this loop.
But,
** Changed in: linux-raspi2 (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 Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel
The problem is fixed for me. I did some tests with a fresh installation
on a rpi3 with the image from https://wiki.ubuntu.com/ARM/RaspberryPi.
The image did not boot after a simple apt-get update && apt-get upgrade.
The kernel was not updated, still version 1009 from the image.
The uboot error
I also have the same issue as everyone here. RPi 3, Ubuntu 16.04.
I have an image of memory card just before bricking it. But when I connect it
to the internet, almost immediately is taking security updates and want to
restart.
If I'm on the stage when ubuntu requesting the restart, executing
I also went down the root of https://bugs.launchpad.net/ubuntu/+source
/linux-raspi2/+bug/1652270/comments/27 without success
i note specifically also that the PPA (https://launchpad.net/~ubuntu-
raspi2/+archive/ubuntu/ppa-rpi3/) has updated packages for flash-kernel
and linux-firmware-raspi2
For me, it's a 1.1 model
[0.00] Machine model: Raspberry Pi 2 Model B Rev 1.1
CPUINFO :
Hardware: BCM2709
Revision: a01041
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think it's probably more likely that this is related to the changes to
the dtb address over in #1636838 (although after hacking at it for a
while trying to make those changes ad-hoc for verification, I wasn't
able to confirm that hunch for sure).
--
You received this bug notification because
I'm also facing this Bug with my RPi3. It does not boot with kernel >=
1038
Maybe it has something to do with the CPU? If this is the case, any new
RPi2 would have the same problem! Since board revision V1.2 RPi2 is
using the 64-bit BCM2837 processor from its newer sibling.
See:
I'm running a cluster of 3 RPi3 and 2 RPi2. For what I'm aware of,
there's only troubles with the RPi2. Both of mine RPi2s boots as
expected, so is the RPi2 bug you're referring to related to something
else?
I agree to the ETA part, it's frustrating to wait for a fix - and don't even
know if it
Ubuntu 16.04 for Rpi2 is a Official image :
https://wiki.ubuntu.com/ARM/RaspberryPi
And rpi2 is also impacted !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into
I understand your point and I generally agree. On the other hand, such
an effort can be counterproductive and easily can cause more problems
than benefits.
People install a distro in a good faith that it will work and that the
maintainer will maintain it. At least, keep it in a working not
Guys. Remember that this is a community build, and not officially
supported by Ubuntu. We need to thank those who's doing this work, as it
helps out with further development of Ubuntu itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yeah, this is definitely sad. I had to move to Raspbian, too. As this is
not the first time waiting too long for fixing a serious Ubuntu bug, I
am thinking of replacing Ubuntu also on my servers and desktops. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Can't believe this is still not fixed, had to move to Raspbian, but
probably a wise decision in the long run if something like this happens
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Any updates on this? - it's a critical issue that is bricking all
raspberry pi units out there without any user intervention...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could
Is it possible to let us know if/when this bug is going to be fixed?
Look, this is not a minor one, we have bricked devices and it happened
via official (automatic) distribution update process. I have never
experienced such a faux pas with another distro in 20+ yrs experience. I
think that a bug
I saw the same here, so I set the packages linux-raspi2 linux-image-raspi2 and
linux-headers-raspi2 to hold (as mentioned above) and reinstalled the last
working kernel 4.4.0-1034:
dpkg-reconfigure linux-image-4.4.0-1034-raspi2
My test with the latest version 4.4.0-1040 still shows the same
Unfortunately, all of mine have upgraded, but I only rebooted one of
them - and hoping the others will keep running until a fix is out. Or do
anyone know a step by step solution for this, that wont prevent further
updates later, ref: https://bugs.launchpad.net/ubuntu/+source/linux-
Same here, no human intervention of any kind. Had a working RPI before,
then suddenly one day stopped working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3
As a workaround for those that haven't bricked their Raspberry, run this
to prevent bricking until this is resolved:
sudo apt-mark hold linux-raspi2 linux-image-raspi2 linux-headers-raspi2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm having the same issue, linux-image-4.4.0-1009-raspi2 boots without
issues, upgrading to linux-image-4.4.0-1040-raspi2 and the Raspberry Pi
3 does not boot anymore :( - any solution except downgrading?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-raspi2 (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.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel
Critical bug making installations unbootable, still unassigned, looks
like it's time to move to another distro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3
Same with to kernel «1040» as well, I upgraded through «dist-upgrade»
today (11. january 2016). Tried to roll back by mounting the sd-card and
chroot (sudo proot -q qemu-arm -S /path/to/fs), then:
# ls /boot/
System.map-4.4.0-1009-raspi2 initrd.img
System.map-4.4.0-1040-raspi2
I got the breaking-update automatically via unattended-upgrades -- no
human intervention of any kind. Simply rebooted the RPi3 after the
holidays and it failed to come back up.
To fix it, I used "qemu-user-static"'s ARM emulation to get a chroot
into the SD card's system on my laptop, and then I
I did not have to issue apt install linux-*. In my case, apt update &&
apt dist-upgrade was enough to break the system as a new kernel had been
installed automatically. Some people reported that apt update followed
with apt upgrade break it too. This makes a big difference as the impact
of the bug
for those that are are in the unbeatable state - the way to recover
without data loss pending fixed kernel
either mount the ubuntu raspberry pi image or write it to another SD
card, copy the files from the small boot partition (i did all to be
safe) e.g. boot.scr vmlinuz etc to a folder on your
By image i mean the one available here:
https://wiki.ubuntu.com/ARM/RaspberryPi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
PI3 here too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notifications about this bug go to:
I'm having the same issue with a pi3. This started right before
Christmas for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage
The same here. Installed, upgraded (not a quick process), configured
during the update, rebooted, system lost. Hangs on "Starting kernel".
Completely breaking a working system via its own update process is a
critical bug, the importance level should be raised.
--
You received this bug
Any progress on this? I hit the same issue ("Starting kernel" then
nothing) when trying to boot a client image on the pi3. Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could
i note in removing these problem packages and downgrading to 1034 that
there appears to be different subversions of the 1038 build
root@piserver2:~# apt-get purge linux-image-4.4.0-1038-raspi2
linux-headers-4.4.0-1038-raspi2 linux-raspi2-headers-4.4.0-1038
Reading package lists... Done
Building
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (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/1652270
74 matches
Mail list logo
