[fedora-arm] Re: Wiki claims RPi 4 is not supported
> On 19 Sep 2021, at 11:17, Stefan Wahren wrote: > > Hi, > >> Am 18.09.21 um 21:58 schrieb Barry Scott: >> On this page it states that the RPi4 is not supported. >> >> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_4 > > yes the statement about hardware support isn't quite correct anymore. > But there is still a noticeable difference between the mainline kernel > (which Fedora uses) and the vendor kernel from the Raspberry Pi Foundation. > > Most notably are: > - audio support > - V3D support An update to say clearly that only server/headless worked then would better the. The blanket “it does not work”. I is only that I looked deeper that I found out that it might work. Oh and would need a warning that the boot is very slow. I see a black screen for a couple of minutes before I see any output from the kernel or systemd. > > A lot users doesn't accept this. Instead of blaming the vendor to focus > on its own kernel branch, they blame Fedora for using the mainline > kernel. So that's the reason to say it's not officially supported. > >> There a lots of messages in this mailing archieve showing that people are >> getting Fedora to work on RPi4. >> >> Is there still a reason to claim its not supported? >> If so what should I be watching out for/avoiding with the RPi4? > For a headless / server setup there shouldn't be no general issues. Food to know. Barry >> >> Barry >> >> >> ___ >> arm mailing list -- arm@lists.fedoraproject.org >> To unsubscribe send an email to arm-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure > ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[fedora-arm] Re: Heads-up / for discussion: dnf not working with 1G of RAM or less
> On 29 Aug 2022, at 04:25, Adam Williamson wrote: > > Hey folks! I apologize for the wide distribution, but this seemed like > a bug it'd be appropriate to get a wide range of input on. > > There's a bug that was proposed as an F37 Beta blocker: > https://bugzilla.redhat.com/show_bug.cgi?id=1907030 > > it's quite an old bug, but up until recently, the summary was > apparently accurate - dnf would run out of memory with 512M of RAM, but > was OK with 1G. However, as of quite recently, on F36 at least (not > sure if anyone's explicitly tested F37), dnf operations are commonly > failing on VMs/containers with 1G of RAM due to running out of RAM and > getting OOM-killed. > > There's some discussion in the bug about what might be causing this and > potential ways to resolve it, and please do dig into/contribute to that > if you can, but the other question here I guess is: how much do we care > about this? How bad is it that you can't reliably run dnf operations on > top of a minimal Fedora environment with 1G of RAM? > > This obviously has some overlap with our stated hardware requirements, > so here they are for the record: > > https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/welcome/Hardware_Overview/ > > that specifies 2GB as the minimum memory for "the default > installation", by which I think it's referring to a default Workstation > install, though this should be clarified. But then there's a "Low > memory installations" boxout, which suggests that "users with less than > 768MB of system memory may have better results performing a minimal > install and adding to it afterward", which kinda is recommending that > people do exactly the thing that doesn't work (do a minimal install > then use dnf on it), and implying it'll work. I have seen dnf fail to work on my 2GiB Rpi 4 with f36. What I did to workaround this was install the kernel on its own, then dnf update the rest. So it’s only 1GiB systems that are effected. I also have a 1GiB digital ocean VM that happens to not see this issue. I suspect it may be certain packages that make this more likely to fail. Barry > > After some consideration I don't think it makes sense to take this bug > as an F37 blocker, since it already affects F36, and that's what I'll > be suggesting at the next blocker review meeting. However, it does seem > a perfect candidate for prioritized bug status, and I've nominated it > for that. > > I guess if folks can chime in with thoughts here and/or in the bug > report, maybe a consensus will emerge on just how big of an issue this > is (and how likely it is to get fixed). There will presumably be a > FESCo ticket related to prioritized bug status too. > > Thanks folks! > -- > Adam Williamson > Fedora QA > IRC: adamw | Twitter: adamw_ha > https://www.happyassassin.net > > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: Details on Raspberry Pi 5 support timelines
> On 17 Mar 2024, at 18:23, Peter Robinson wrote: > > The TL;DR is that there won't be any way of even basic support > officially for F-40 GA. There are people asking for status on https://discuss.python.org/ and I have replied pointing to this thread. I will continue to help with the conversation on discuss. Barry -- ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: Details on Raspberry Pi 5 support timelines
> On 18 Mar 2024, at 08:14, Barry wrote: > > There are people asking for status on https://discuss.python.org/ Doh! Asking on https://discussion.fedoraproject.org/ I meant to say… Barry-- ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: Error with arm-image-installer F39 Rpi4 IoT image on F38 Host
> On 17 Apr 2024, at 00:45, Derek Atkins wrote: > > dev/sdb3 has unsupported feature(s): FEATURE_C12 If you do a web search for that error you will see lots of other people have report seeing it. Barry -- ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Add LUKS disk to an Raspberry Pi 4 install
I'm trying to build a RPi4 system that uses a LUKS encrypted disk.
But I cannot get the volume to be unlocked when the system boots.
I have install Fedora-Minimal-34-1.2.aarch64.raw.xz to with
arm-image-installer --target=rpi4 and that boots.
That I have added a new partition to that sdcard that I setup using this
command from Fedora 34 x86_86 system.
cryptsetup \
--type luks2 \
--cipher xchacha20,aes-adiantum-plain64 \
--hash sha256 \
--iter-time 5000 \
--pbkdf argon2i \
luksFormat ${DEVICE}
I got these settings from a blog on setting up crypt for debian on raspberry
pi.
I add an entry to /etc/crypttab for the volume.
When I boot the system I am not prompted for the password to unlock the
volume as I was expecting.
Looking in journalctl -b 0 I see these lines:
Apr 06 01:01:36 clef.chelsea.private systemd[1]: dev-disk-
by\x2duuid-8c2519ae\x2d78a9\x2d44b0\x2d871f\x2d0aa2422de03a.device: Job dev-
disk-by\x2duuid-8c2519ae\x2d78a9\x2d44b0\x2d871f\x2d0aa2422de03a.device/start
timed out.
Apr 06 01:01:36 clef.chelsea.private systemd[1]: Timed out waiting for device
/dev/disk/by-uuid/8c2519ae-78a9-44b0-871f-0aa2422de03a.
Apr 06 01:01:36 clef.chelsea.private systemd[1]: Dependency failed for
Cryptography Setup for clef-root.
Apr 06 01:01:36 clef.chelsea.private systemd[1]: Dependency failed for Local
Encrypted Volumes.
Once I log in I can open the volume and mount it
$ cryptsetup luksOpen /dev/mmcblk0p4 clef-root
$ mount /dev/mapper/clef-root /mnt
I have tried updating the initrd with:
dracut --force.
And also adding to the kernel command line:
# cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos2)/vmlinuz-5.11.12-300.fc34.aarch64
root=UUID=67ca2085-9dab-405b-a042-ff6269816fbc ro rhgb quiet console=tty0
rd.luks.uuid=8c2519ae-78a9-44b0-871f-0aa2422de03a
I have a other systems that use full disk encryption that work. But I have
failed to spot the difference between the RPi config and the working systems
config.
Do you know what is missing or not configured?
Hmm, just noticed that the kernel command says console is tty0.
But when I log in on the console its tty1.
Barry
Just not
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
[fedora-arm] Wiki claims RPi 4 is not supported
On this page it states that the RPi4 is not supported. https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_4 There a lots of messages in this mailing archieve showing that people are getting Fedora to work on RPi4. Is there still a reason to claim its not supported? If so what should I be watching out for/avoiding with the RPi4? Barry ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[fedora-arm] RPi4 and support for RTC DS3231
I have an RPi4 running Fedora 38 with kernel 6.5.6-200.fc38.aarch64. So far I figured out that I have to add this line to the config.txt [pi4] dtoverlay=i2c-rtc,ds3231 But after a reboot I am not seeing any /dev/rtc* devices. Also I'm not seeing any rtc drivers load in lsmod output. Should this work with the Fedora kernel? If so what do I need to do to make the RTC show up? Barry ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: RPi4 and support for RTC DS3231
> On 20 Oct 2023, at 12:01, Peter Robinson wrote: > > Sure, it's a wiki so feel free to just add it, maybe make it generic > to cover all RTCs. Let me know how you get on. Done. Barry ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: RPi4 and support for RTC DS3231
> On 19 Oct 2023, at 17:28, Peter Robinson wrote: > > You'll need to follow the general section for HAT support (it's > basically any HW that needs an overlay) and reboot and it should work: > https://fedoraproject.org/w/index.php?title=Architectures/ARM/Raspberry_Pi/HATs#General_configuration > > That RTC is supported by the rtc-ds1307 driver. I missed the link at the end of the config.txt that was Fedora specific. Maybe you could put that Fedora specific comment at the start of config.txt in a future release? I have followed the steps and the RTC is working. I would like to add a section on the RTC to the docs. If that is useful how do I go about doing that? But I have lost the HDMI console. I can ssh into the system and it is otherwise working. I see the boot sequence, u-boot, grub, last message on screen is the Fedoara kernel line announcing its version. After a few seconds where I would expect to see systemd messages instead the monitor goes into standby. Do I need to change setting in config.txt to make the HDMI work? Here is my config.txt: $ cat /boot/efi/config.txt | grep -v -e '^#' -e '^$' [pi4] dtoverlay=upstream-pi4 arm_boost=1 dtoverlay=vc4-kms-v3d-pi4 dtoverlay=cma,cma-256 max_framebuffers=2 dtoverlay=i2c-rtc,ds3231 [cm4] otg_mode=1 [all] arm_64bit=1 kernel=rpi-u-boot.bin dtoverlay=upstream enable_uart=1 bootcode_delay=1 gpu_mem=32 start_x=1 camera_auto_detect=1 display_auto_detect=1 hdmi_ignore_cec_init=1 Barry ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: RPi4 and support for RTC DS3231
> On 20 Oct 2023, at 12:01, Peter Robinson wrote: > > Nothing, it's actually broken ATM, it's a F-39 blocker and I'm hoping > to get it fixed today. There's a U-Boot thread on the mailing list and > once I have a fix I'll be posting a reply on that so keep an eye out > on the list for an update. Let me know if there is any testing I can do to help out. I have Rpi3 and Ppi4 hardware and can make a new sdcard for testing as needed. Barry ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: Raspberry Pi 5 support - how to contribute?
Peter, I just received my Pi 5 8GB board and wondered what the current situation is regarding Pi 5 state of kernels etc. If I can usefully help test anything I am happy to help out. Barry -- ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: RPi Kernel memory leak leads to OOM killer running on idle system.
> On 9 May 2024, at 10:03, Peter Robinson wrote: > > > > On Thu, 9 May 2024, 09:42 Barry Scott, <mailto:ba...@barrys-emacs.org>> wrote: >> A number of us are seeing a reproducible kernel memory leak on RPi. >> >> There is a bug https://bugzilla.redhat.com/show_bug.cgi?id=2279327 >> and a thread in discuss about it with additional >> details: >> https://discussion.fedoraproject.org/t/high-memory-usage-in-f40-on-rpi-4-unable-to-find-which-process-used-them/114598 >> >> Kernel 6.5.6 does not have a leak, but current kernels do. > > > Can you specify what you mean by "current kernels", I believe there is a > aarch64 memory leak fix in 6.8.9, which is currently in testing. There's more > info in the following bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=2275290 > Sorry should have provided a version 6.8.8 is what I have. I'll install the 6.8.9 kernel and test. Barry >> >> Anyone know if this is being looked at? >> >> Barry >> -- >> ___ >> arm mailing list -- arm@lists.fedoraproject.org >> <mailto:arm@lists.fedoraproject.org> >> To unsubscribe send an email to arm-le...@lists.fedoraproject.org >> <mailto:arm-le...@lists.fedoraproject.org> >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue -- ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] RPi Kernel memory leak leads to OOM killer running on idle system.
A number of us are seeing a reproducible kernel memory leak on RPi. There is a bug https://bugzilla.redhat.com/show_bug.cgi?id=2279327 and a thread in discuss about it with additional details: https://discussion.fedoraproject.org/t/high-memory-usage-in-f40-on-rpi-4-unable-to-find-which-process-used-them/114598 Kernel 6.5.6 does not have a leak, but current kernels do. Anyone know if this is being looked at? Barry -- ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
