> Which release of Ubuntu are we talking about here? This is a clone of my RPi3 system (disco, IIRC it started out as bionic) that was upgraded to eoan (on the Pi3).
btw: I've upgraded(?) the EEPROM to the July version (https://static.raspberrypi.org/files/rpi-boot-eeprom- recovery-2019-07-15.zip). I don't think this changes anything, but wanted to mention it. Thanks for the suggestions. I'll experiment with my setup when I get home today and report back. I'm not sure at this moment if it didn't detect the SD card or if the device names somehow changed. Or if it's really just the armstub thingy. > Anyway, I don't *think* the Pi's bootloader is capable of dealing with > compressed kernel images in which case, when we do start compressing our > kernels, I'm afraid your boot sequence will suddenly break. Thanks for the headsup. I was planning to use u-boot again in the near future, anyways. The reason I stopped using it was that there were several changes of the DTB address about a year ago and there was a mismatch between the inofficial raspi2-pi3 PPA (0x200) and the default packages (0x0200000-something) and my config.txt (always had the wrong one). That broke things on my Raspberrys a few times so I switched to the u-boot-less config to not have to bother about DTB memory addresses anymore. Do you know if booting via u-boot makes the whole 4GB RAM accessible to the system or is there still a limit of 1GB? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
