was also unable to boot Fedora
from the SD card (had to use a USB adapter instead). Same error as in
this thread, tried multiple cards (including a card from a Pi3), no
different.
--
Chris Adams
___
arm mailing list -- arm@lists.fedoraproject
es:
pps-gpio: probe of pps@4 failed with error -22
--
Chris Adams
___
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/pro
remember to swap back to the EFI-provided file
if I boot an older kernel)?
Sorry, this is my only Pi, so still learning about this side of things.
:)
--
Chris Adams
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubsc
tps://github.com/pftf/RPi4 in /boot/efi, and
the /boot/dtb symlink removed. The bcm2711-rpi-4-b.dtb file in
/boot/efi is from the RPi4_UEFI_Firmware_v1.32.zip file. I have a
config.txt in /boot/efi that references overlays in /boot/efi/overlays
from RPM bcm283x-overlays (like pps-gpio)..
I'm
SSHing in, I see in dmesg:
[drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0
Unable to handle kernel read from unreadable memory at virtual address
0348
and so on with a kernel Oops dump. So it seems the kernel-included
sing a Pi4
headless, so not having accelerated graphics doesn't affect me, but
there have been other issues (SD card and GPIO/PPS for me).
--
Chris Adams
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...
ese from the kernel:
mmc0: error -22 whilst initialising SD card
mmc0: invalid bus width
I'm not sure how you'd get different behavior with different images
though, because they're all the same kernel/initrd setup AFAIK.
--
Chris Adams
), but that needlessly uses up a USB port. Is there
a way to tell U-Boot "no really, ignore input from the serial port"?
--
Chris Adams
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedorap
7;t work. If I swap back to the
"server" uSD card, it sees the RTC.
The only difference I can see is that the original card is 32G and the
new card is 64G (so "SDXC")... would that be an issue to the firmware
loader?
--
Chris Adams
__
r" uSD card, and it loads the RTC overlay correctly.
--
Chris Adams
___
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/
Once upon a time, Peter Robinson said:
> On Wed, Aug 23, 2023 at 4:41 PM Chris Adams wrote:
> >
> > Once upon a time, Peter Robinson said:
> > > Ddi you follow this section of the HATs/Overlay docs?
> > > https://fedoraproject.org/w/index.php?title=Ar
ailable for this
particular use.
--
Chris Adams
___
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/
Once upon a time, Héctor Daniel Cortés González said:
> Understood.
>
> An USB dongle? There are with RTC, GPS and even for WWVB :-)
I've already bought a perfectly-functioning RTC... not looking for
suggestions for alternatives.
-
t the Xfce image, it does not.
On the Xfce image, if I also remove the /boot/dtb symlink, it sees the
RTC.
So there's some inconsistency between images (maybe it's just that the
Server image is not working as expected?), but I guess I have a working
set
to avoid confusion?
Thanks.
--
Chris Adams
___
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/
Lis
Once upon a time, Chris Adams said:
> Ahh, this was indeed it. I switched /boot on the XFCE image to XFS and
> it did indeed follow the config.txt entry for the RTC (so same as
> removing the /boot/dtb symlink).
Oh, but when I run the XFCE image (with ext4 /boot as shipped) and
remove
I (so I set them back to
as-shipped).
It's a 4B with 8G RAM. /sys/firmware/devicetree/base/model says rev 1.5
(I guess that's the right place to look?).
--
Chris Adams
___
arm mailing list -- arm@lists.fedoraproject.org
To u
have some spare time" which has been very little of late as I've
> been looking at other things.
So I think I read something along these lines here before, and that's
where I took the "don't touch /boot/dtb" idea from. Sorry about that
Once upon a time, Chris Adams said:
> Once upon a time, Peter Robinson said:
> > All the bits for screen enablement using upstream drivers should be
> > there by default. What else have you done to your config.txt? What
> > exactly is the revision of RPi?
>
> All I&#
devices.
> Also I'm not seeing any rtc drivers load in lsmod output.
Did you do this:
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi/HATs#General_configuration
--
Chris Adams
___
arm mailing list -- arm@lists.fedoraproject.org
stemd service depend on /dev/rtc not
existing?), as other RPi-targeted distros do. This isn't RPi-specific,
a number of the small boards have no RTC. I do typically add an RTC to
my Pis, but not always (for various reasons).
--
Chris Adams
___
a
k
with kernel 6.8.
https://bugzilla.redhat.com/show_bug.cgi?id=2275835
--
Chris Adams
--
___
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.
nks, I'll get those both updated after work today when I can gather
some more info.
I generally try to avoid pinging in multiple places; I know everybody
has lots going on, and try to respect that time. But I know that also
Bugzilla can be a LOT for som
23 matches
Mail list logo
