[fedora-arm] Re: F38->F39
Wait another month or two. Otherwise make sure you have a bugzilla account and be prepared to write a bug report if it does not. I did what you suggested for F37-F38. It mostly worked. It broke my USB Ethernet which was fixed about a month later after I wrote a fairly detailed bug report. On Sat, Dec 30, 2023 at 4:16 AM David Legg wrote: > Is this likely to work, please? > > dnf install dnf-plugin-system-upgrade > dnf system-upgrade download --releasever=39 > dnf system-upgrade reboot > > I have the Fedora 38 minimal installed on a Raspberry Pi 4 with a few > extra packages. Thanks. > > :D > > -- > ___ > 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 > -- ___ 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: Pine64 RockPro doesn't boot with F38 Beta 1 nor branched 20230326 nightly composed
Have you tried any HAT's with those systems? I am looking to move away from PI as it is giving me supply chain issues and would like to settle on something a bit more plentiful and not made in China. On Thu, Mar 30, 2023 at 1:53 PM Dominik 'Rathann' Mierzejewski < domi...@greysector.net> wrote: > On Wednesday, 29 March 2023 at 19:42, Dennis Gilmore wrote: > [...] > > I can confirm that this works just fine. I have 2 RockPro64's running > > Fedora 37 here and using u-boot on SPI from there. It reminds me I should > > document how I built a Fedora based NAS with 10 drives using a RockPro64. > > It is not the most performant but suits me > > Yes, please do that. I'm keeping an eye out for a replacement of my > current Atom-based NAS and this could be it. Please include some > benchmarks and power consumption info. > > Regards, > Dominik > -- > Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org > There should be a science of discontent. People need hard times and > oppression to develop psychic muscles. > -- from "Collected Sayings of Muad'Dib" by the Princess Irulan > ___ > 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 > ___ 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: Le Potato?
I doubt it. ARM doesn't have a standardized layout for BIOS, memory maps etc. So you can't build ARN distros under the assumption they will work like a PC with a AMD or Intel processor. On Wed, Mar 29, 2023, 11:03 AM Richard Shaw wrote: > Google has failed me. Can I run Fedora on a Le Potato? If so, what target > do I use? > > Anything I need to do before writing the image? > > I plan to use eMMC if I can get it cheap enough due to the failure rate of > SD cards. > > Thanks, > Richard > ___ > 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 > ___ 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: Fedora Minimal 36 installation on raspberry pi 2B
DNF no longer has sufficient resources on my PI 3, after a recent update, to work anymore. The slooow creap of fixes, patches and related support elements to make ARM a well supported option on Fedora is taking its toll. I know microdnf has been discussed a few times, but here is another alternative which worked for me. Another way of dealing with dnf memory issues is to add swap space using a swap file on my Raspberry PI 3+ This corrects a memory deficit of about 200MB on my PI 3's working set of physical RAM pages, which kicks me out of the remote shell. Here is the steps I used to start using dnf again: I decided I would put the swap file off the /mnt so I made a directory for it: mkdir /mnt/swapfiles Then I made the swapfile I picked 5G, if you don't have that sort of space you might need to experiment with an appropriate size, maybe 2G? fallocate -l 5G /mnt/swapfiles/swpf1 An Alternative is to use dd to make the swp if you happen to be running a slimmed down installation and do not have fallocate installed. dd if=/dev/zero of=/mnt/swapfiles/swpf1 bs=1024 count=5048576 Set the access rights on the swapfile like so: chmod 600 /mnt/swapfiles/swpf1 Tell Linux about the swapfile: mkswap /mnt/swapfiles/swpf1 Activate the swapfile: swapon /mnt/swapfiles/swpf1 I only use the swap file when I am loading or patching with DNF, so I did not put the swapfile configuration into my fstab file. So I just execute a swapon before I do a "dnf update". My reason for doing so is to eliminate any unwanted writes to the sdcard that are not absolutely required. Which helps extend the life of the sdcard. If you want to add the swapfile so that it is always on, you have to add a line to the /etc/fstab file like so: /mnt/swapfiles/swpf1 swap swap defaults 0 0 i hope you found this helpful. I know I did. :-) On Fri, Jan 20, 2023 at 3:39 PM Irene Diez wrote: > Hello there, > > I'm trying to install Fedora-Minimal-36-1.5.armhfp.raw on my raspberry pi > 2B. Installation was a success but the device runs out of memory when > trying to install anything via dnf and I get kicked out of the shell. > > I've followed the installation instructions in > https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual, > which specify that this model is supported since Fedora 29; so, is it there > anything that I'm missing for Fedora to work? > > Thanks, > > Irene > ___ > 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 > ___ 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: Fedora-Minimal-36-1.5 on raspberry pi 2B
Oh thats a easy fix. Just dnf update a couple of packages at a time, don't try to do it all at once. i.e. don't do a "dnf update" Do a "dnf update kernel" for example. If you can't run dnf for even one package update I would install something else as you are going to run into more problems than just dnf. Thats just the START of your problems. On Fri, Jan 20, 2023 at 4:12 PM Troy Dawson wrote: > Unfortunately this isn't a matter of arm vs x86_64, it's a matter of the > dnf with it's repo's have gotten too big to fit in memory. > > This is the discussion on the devel list > "Heads-up / for discussion: dnf not working with 1G of RAM or less" > > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/CRREDQUPPJYWVRMA4DOKYU2KZZLKC4D5/#EGO43HCCD6F5Y5GFANFUNUNDEJTWZITU > > It's a bit of a long read. > I did see two or three work-arounds. > 1 - Add a swap partition and/or swapfile > 2 - Use microdnf (but you have to figure out how to install it. see > workaround 1) > 3 - Use dnf5 (see workaround 2, and it's still missing some features) > > There might be other workarounds that I missed. As I said, it's a bit of > a read. > > > On Fri, Jan 20, 2023 at 2:56 PM Gregory Carter > wrote: > >> >> https://developer.arm.com/documentation/ddi0464/f/Programmers-Model/About-the-programmers-model?lang=en >> >> https://docs.fedoraproject.org/en-US/quick-docs/raspberry-pi/ >> >> I do not believe that is supported platform for F37 out of the box. >> >> You may have to build a custom kernel/package set on something that small >> to run F37. >> >> 1Gig is really scraping the bottom of the barrel to run the default image >> you downloaded. >> >> Plus I would use the raw image, not the armhfp. >> >> But to start I would strip out all of the desktop components in the >> image like KDE/GNOME/X and Wayland. >> >> On Fri, Jan 20, 2023 at 3:42 PM Irene Diez wrote: >> >>> Hello there, >>> >>> I'm trying to install Fedora-Minimal-36-1.5.armhfp.raw on my raspberry >>> pi 2B. Installation was a success but the device runs out of memory >>> when trying to install anything via dnf and I get kicked out of the >>> shell. >>> >>> I've followed the installation instructions in >>> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual, >>> which specify that this model is supported since Fedora 29; so, is >>> there anything that I'm missing for Fedora to work? >>> >>> Thanks, >>> >>> Irene >>> ___ >>> 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 >>> >> ___ >> 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 >> > ___ > 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 > ___ 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: Fedora-Minimal-36-1.5 on raspberry pi 2B
https://developer.arm.com/documentation/ddi0464/f/Programmers-Model/About-the-programmers-model?lang=en https://docs.fedoraproject.org/en-US/quick-docs/raspberry-pi/ I do not believe that is supported platform for F37 out of the box. You may have to build a custom kernel/package set on something that small to run F37. 1Gig is really scraping the bottom of the barrel to run the default image you downloaded. Plus I would use the raw image, not the armhfp. But to start I would strip out all of the desktop components in the image like KDE/GNOME/X and Wayland. On Fri, Jan 20, 2023 at 3:42 PM Irene Diez wrote: > Hello there, > > I'm trying to install Fedora-Minimal-36-1.5.armhfp.raw on my raspberry > pi 2B. Installation was a success but the device runs out of memory > when trying to install anything via dnf and I get kicked out of the > shell. > > I've followed the installation instructions in > https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual, > which specify that this model is supported since Fedora 29; so, is > there anything that I'm missing for Fedora to work? > > Thanks, > > Irene > ___ > 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 > ___ 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: Watchdog and raspberrypi
For best results I use a out of band network device to cut power to devices and reboot them when they fail the watchdog criteria. Normally they stop pinging or a service isn't responding after a NAGIOS plugin attempt to restart. I would have a look at webpowerswitch.com I use this with PCS and a GFS2 cluster for enforcing and recovering fencing. Works well. On Sat, Jan 7, 2023 at 3:12 PM Pierre-Francois Renard wrote: > Hello guys, > > > I am running 6 RPI4s with fedora 37. K3S is powering this cluster and it > is working well :) > > But from time to time, 1 RPI is randomly hanging. > > I am thinking about implementing a watchdog : > > - software based, using embeded linux kernel > > - hardware based such as https://www.omzlo.com/articles/the-piwatcher > > > Do you have any experience on one of theses two solutions ? Do you have > alternatives ? > > > By the way your job is fantastic and it is a great pleasure to be able > to run F37 on aarch64 so easily ! > > > Thanks a lot > > ___ > 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 > ___ 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: Failures booting on Pi4
https://www.kernel.org/ Release 6 isn't done yet. Needs to bake a while. :-) On Wed, Aug 17, 2022 at 8:55 AM Steven A. Falco wrote: > On 8/17/22 09:08 AM, Peter Robinson wrote: > > Hi Steve, > > ... snip ... > > > I mentioned the HW rev above, the hex value tells me it's Rev 1.5 of > > the 2gb 4B. Since rev 1.4 they've been able to run at 1.8ghz like the > > RPi400 instead of the 1.5ghz of the older revs, but this came with > > some minor design changes, this in turn has caused issues in > > particular around the MMC stability, the device works using "firmware > > DT" but not the vanilla upstream kernel DT. > > > > I think we now have a fix headed upstream into U-Boot that should > > allow this to work, you can grab the latest U-Boot builds from koji > > and update them or it should be fixed in the next rawhide or F-37 > > generated images (probably tomorrow). > > Thanks for the reply. I'm no longer seeing the problem in my current > config. I'm using a USB-connected SSD at this point, and the U-Boot phase > is now solid. > > However, I'm seeing a number of different faults with the 5.20 and 6.0 > kernels. > > I tried the vmlinuz-5.20.0-0.rc0.20220812git7ebfc85e2cd7.10 kernel, and it > throws a lot of vc4_hdmi_write and vc4_hdmi_read errors, as shown in the > attached kernel-5.20_kernel_DT.log (starts around line 880). This log is > with the in-kernel DT. > > I then tried using the FW DT (please see kernel-5.20_FW_DT.log around line > 877) but it gets the same errors. > > The overall boot process with the 5.20 kernel takes around 100 seconds to > get to a login prompt. > > I then tried dropping back to the vmlinuz-5.19.0-65 kernel. I don't see > the errors, and I get a boot prompt in under 30 seconds. Log file is > kernel-5.19_kernel_DT.log. > > I then tried the 6.0 kernel, again with the kernel DT and the FW DT. In > log kernel_6.0_kernel_DT.log at line 342, we have a kernel Oops. In log > kernel_6.0_FW_DT.log at line 324 I get "rcu_preempt detected stalls". > > I'll stay with the 5.19 kernel for now. > > Steve > > ___ > 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 > ___ 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 (or something similar) cluster and GlusterFS - feedback?
I couldn't do such a thing without a 10Gig Ethernet to power the systems I use with Gluster and GFS. They both run pretty smoothly on such an environment. My application is a large iSCSi domain. For a very small network I would think it wouldn't be a problem. How small though you would have to try and see. Gluster/GFS thier ilk are not very forgiving on frugal systems. Beware. On Thu, Aug 11, 2022, 3:49 AM Philip Rhoades wrote: > People, > > For many years (after some nasty experiences) I have been in the habit > of using a Fedora Work Station (which stays on but gets rebooted fairly > frequently) and a separate Fedora server (email-MTA, some Web sites etc) > which stays on for very long periods of time and only gets rebooted > infrequently. I have other systems that get booted occasionally. My > habit has been to backup / rsync important / critical data between the > regular WS and the main server as appropriate - this has allowed me on a > number of occasions to recover happily when hardware has failed, to get > going temporarily again on one or the other machine while I sort out the > problem. > > More recently I have been thinking about building an ARM cluster with > Gluster that would hold all the data for both the WS and the main server > and any other WSs or servers I might need to run from time to time. I > would still make use of an off-site backup anyway but I like the idea of > just being able to add another ARM device + SATA drive to the cluster to > create more data space. I also thought I would go back to making use of > WSs that were basically just X-servers that booted from some sort of USB > stick but got the OS image from the cluster - this might be complicated > by the fact I now use Sway rather than X - but one problem at a time . . > > Has anyone here set up a cluster something like this? Have people any > suggestions about specific Fedora web pages / docs to look at? > > I have been tracking CEPH for some time and while it looks interesting, > it seems overkill for what I am thinking of doing and more technically > difficult to support / debug etc. I am thinking of starting the > exercise with 4 RPis each with an 8Tb SATA drive. > > Thanks, > > Phil. > -- > Philip Rhoades > > PO Box 896 > Cowra NSW 2794 > Australia > E-mail: p...@pricom.com.au > ___ > 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 > ___ 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: Fedora 36 ARM Issues on Startup
Okay so, I managed to get it to work, by using the --addkey option as you don't need a display once the pie is on the network. That being the case I would update the install image with a refresh. Wasted way way too much time and the documentation needs a refresh as well as it is a bit confusing. Most of the issues I had with F36 arm went away after a update. It is in evaluation phase now so if ti performs as well as F35 does I will probably move my hat over to it. On Thu, Jul 28, 2022 at 11:36 AM Gregory Carter wrote: > It would seem there are many different documentation locations for ARM > which I am trying to figure out which one is canonical. > > These two seem to differ: > > https://fedoraproject.org/wiki/Architectures/ARM/Installation (One I > tried first.) > > then this one > > https://docs.fedoraproject.org/en-US/iot/physical-device-setup/ > > Which one is the correct one? > > I will try that image out shortly. > > On Wed, Jul 27, 2022 at 8:37 AM Peter Robinson > wrote: > >> On Mon, Jul 25, 2022 at 6:16 PM Gregory Carter >> wrote: >> > >> > I downloaded the Fedora-Server-dvd-aarch64-36-1.5.iso and the used the >> > arm-image-installer to write the install image to a sdcard using the >> following installation options: >> > >> > --target=rpi3 --resizefs >> >> Download the raw image from the following link and repeat what you've >> done and I think you should be good: >> https://getfedora.org/en/server/download/ >> >> > I am trying Fedora36 out as the project I have is working fine on the >> other sdcard I have with Fedora34 on it. >> > >> > >> > >> > On Mon, Jul 25, 2022 at 10:01 AM Peter Robinson >> wrote: >> >> >> >> On Mon, Jul 25, 2022 at 5:58 PM Gregory Carter >> wrote: >> >> > >> >> > This is a new install. >> >> > >> >> > I downloaded the server image. >> >> >> >> Can you be explicit and provide the file name? Is it the installer >> >> image or the pre-canned server image? The later uses the web console >> >> not a GUI. >> >> >> >> > Hitting the alternate console I can see CMA errors being posted. >> >> > >> >> > On the primary console I get a mouse pointer, but its just a black >> screen. >> >> > >> >> > There seems to be GUI elements posted that I can't see as moving the >> mouse around changes the pointer from a arrow to a finger. >> >> > >> >> > The bootup looks like it went fine. Looks like it is at a post >> setup screen of some kind. >> >> > >> >> > If there is specific info needed I can post that would help? >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > On Sun, Jul 24, 2022 at 11:57 PM Peter Robinson < >> pbrobin...@gmail.com> wrote: >> >> >> >> >> >> Hi, >> >> >> >> >> >> > I seem to be getting a black screen on bootup. >> >> >> > >> >> >> > This is running on a Canakit PI3B+ >> >> >> >> >> >> Is this an update, new install, what Desktop image are you using? >> >> >> >> >> >> > Looks like a CMA error. >> >> >> > >> >> >> > What size screen was this public image tested on? The screen I >> connected was a 1920x1080 resolution. >> >> >> > >> >> >> > Does it need to be smaller than that? >> >> >> >> >> >> It should work with that. >> >> >> >> >> >> > Can you set the CMA higher before install time? If so what is the >> proper values for a 1920x1080 screen? >> >> >> >> >> >> Yes, you can edit the grub cmd line, it's also dependent on the >> >> >> desktop. It could be things other than CMA though, but you'll need >> to >> >> >> provide more detailed information. >> > ___ 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: Fedora 36 ARM Issues on Startup
It would seem there are many different documentation locations for ARM which I am trying to figure out which one is canonical. These two seem to differ: https://fedoraproject.org/wiki/Architectures/ARM/Installation (One I tried first.) then this one https://docs.fedoraproject.org/en-US/iot/physical-device-setup/ Which one is the correct one? I will try that image out shortly. On Wed, Jul 27, 2022 at 8:37 AM Peter Robinson wrote: > On Mon, Jul 25, 2022 at 6:16 PM Gregory Carter > wrote: > > > > I downloaded the Fedora-Server-dvd-aarch64-36-1.5.iso and the used the > > arm-image-installer to write the install image to a sdcard using the > following installation options: > > > > --target=rpi3 --resizefs > > Download the raw image from the following link and repeat what you've > done and I think you should be good: > https://getfedora.org/en/server/download/ > > > I am trying Fedora36 out as the project I have is working fine on the > other sdcard I have with Fedora34 on it. > > > > > > > > On Mon, Jul 25, 2022 at 10:01 AM Peter Robinson > wrote: > >> > >> On Mon, Jul 25, 2022 at 5:58 PM Gregory Carter > wrote: > >> > > >> > This is a new install. > >> > > >> > I downloaded the server image. > >> > >> Can you be explicit and provide the file name? Is it the installer > >> image or the pre-canned server image? The later uses the web console > >> not a GUI. > >> > >> > Hitting the alternate console I can see CMA errors being posted. > >> > > >> > On the primary console I get a mouse pointer, but its just a black > screen. > >> > > >> > There seems to be GUI elements posted that I can't see as moving the > mouse around changes the pointer from a arrow to a finger. > >> > > >> > The bootup looks like it went fine. Looks like it is at a post setup > screen of some kind. > >> > > >> > If there is specific info needed I can post that would help? > >> > > >> > > >> > > >> > > >> > > >> > On Sun, Jul 24, 2022 at 11:57 PM Peter Robinson > wrote: > >> >> > >> >> Hi, > >> >> > >> >> > I seem to be getting a black screen on bootup. > >> >> > > >> >> > This is running on a Canakit PI3B+ > >> >> > >> >> Is this an update, new install, what Desktop image are you using? > >> >> > >> >> > Looks like a CMA error. > >> >> > > >> >> > What size screen was this public image tested on? The screen I > connected was a 1920x1080 resolution. > >> >> > > >> >> > Does it need to be smaller than that? > >> >> > >> >> It should work with that. > >> >> > >> >> > Can you set the CMA higher before install time? If so what is the > proper values for a 1920x1080 screen? > >> >> > >> >> Yes, you can edit the grub cmd line, it's also dependent on the > >> >> desktop. It could be things other than CMA though, but you'll need to > >> >> provide more detailed information. > ___ 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: Fedora 36 ARM Issues on Startup
I downloaded the Fedora-Server-dvd-aarch64-36-1.5.iso and the used the arm-image-installer to write the install image to a sdcard using the following installation options: --target=rpi3 --resizefs I am trying Fedora36 out as the project I have is working fine on the other sdcard I have with Fedora34 on it. On Mon, Jul 25, 2022 at 10:01 AM Peter Robinson wrote: > On Mon, Jul 25, 2022 at 5:58 PM Gregory Carter > wrote: > > > > This is a new install. > > > > I downloaded the server image. > > Can you be explicit and provide the file name? Is it the installer > image or the pre-canned server image? The later uses the web console > not a GUI. > > > Hitting the alternate console I can see CMA errors being posted. > > > > On the primary console I get a mouse pointer, but its just a black > screen. > > > > There seems to be GUI elements posted that I can't see as moving the > mouse around changes the pointer from a arrow to a finger. > > > > The bootup looks like it went fine. Looks like it is at a post setup > screen of some kind. > > > > If there is specific info needed I can post that would help? > > > > > > > > > > > > On Sun, Jul 24, 2022 at 11:57 PM Peter Robinson > wrote: > >> > >> Hi, > >> > >> > I seem to be getting a black screen on bootup. > >> > > >> > This is running on a Canakit PI3B+ > >> > >> Is this an update, new install, what Desktop image are you using? > >> > >> > Looks like a CMA error. > >> > > >> > What size screen was this public image tested on? The screen I > connected was a 1920x1080 resolution. > >> > > >> > Does it need to be smaller than that? > >> > >> It should work with that. > >> > >> > Can you set the CMA higher before install time? If so what is the > proper values for a 1920x1080 screen? > >> > >> Yes, you can edit the grub cmd line, it's also dependent on the > >> desktop. It could be things other than CMA though, but you'll need to > >> provide more detailed information. > ___ 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: Fedora 36 ARM Issues on Startup
This is a new install. I downloaded the server image. Hitting the alternate console I can see CMA errors being posted. On the primary console I get a mouse pointer, but its just a black screen. There seems to be GUI elements posted that I can't see as moving the mouse around changes the pointer from a arrow to a finger. The bootup looks like it went fine. Looks like it is at a post setup screen of some kind. If there is specific info needed I can post that would help? On Sun, Jul 24, 2022 at 11:57 PM Peter Robinson wrote: > Hi, > > > I seem to be getting a black screen on bootup. > > > > This is running on a Canakit PI3B+ > > Is this an update, new install, what Desktop image are you using? > > > Looks like a CMA error. > > > > What size screen was this public image tested on? The screen I > connected was a 1920x1080 resolution. > > > > Does it need to be smaller than that? > > It should work with that. > > > Can you set the CMA higher before install time? If so what is the proper > values for a 1920x1080 screen? > > Yes, you can edit the grub cmd line, it's also dependent on the > desktop. It could be things other than CMA though, but you'll need to > provide more detailed information. > ___ 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] Fedora 36 ARM Issues on Startup
I seem to be getting a black screen on bootup. This is running on a Canakit PI3B+ Looks like a CMA error. What size screen was this public image tested on? The screen I connected was a 1920x1080 resolution. Does it need to be smaller than that? Can you set the CMA higher before install time? If so what is the proper values for a 1920x1080 screen? ___ 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
