Here's an on-going thread over at snapcraft:
https://forum.snapcraft.io/t/support...-pi-4/11970/14
Nevermind this isn't about the core images.
Here's an on-going thread over at snapcraft:
https://forum.snapcraft.io/t/support...-pi-4/11970/14
Nevermind this isn't about the core images.
Last edited by deadflowr; October 19th, 2019 at 04:37 AM. Reason: epiphanies
Splat Double Splat Triple Splat
Earn Your Keep
Don't mind me, I'm only passing through.
Once in a blue moon, I'm actually helpful.
Another report here, under linux-raspi2 (Ubuntu): https://bugs.launchpad.net/ubuntu/+s...2/+bug/1848790
Cheers & Beers, uRock
[SIGPIC][/SIGPIC]
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/v...46766&start=25
The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/v...rt=50#p1517839
and the kernel patch was this one:
https://github.com/raspberrypi/linux...ment-520269280
Last edited by khowe; October 19th, 2019 at 10:30 PM.
Work around until kernel is patched:
Setting total_mem=3072 in /boot/firmware/usercfg.txt
If you mount the sd card in another computer the usercfg.txt is on the small vfat partition.
As a newbie, may I ask if it is practical to have a naming convention for the image that specifies "minor" release changes too? Right now, I am aware of the issues with the 4 GB model and USB for the image. I also understand that the these have been fixed and patches tested by the user(s) who reported the issues originally.
When can we expect the image to be refreshed?
Kind regards.
Bookmarks