Re: Issues with RPi4 and newer kernels
by Peter Robinson
> I agree with that, until it de-escalets into finger pointing (your fault, my fault) nonsense.. very little to be gained there! Doesn't matter who F'd up . Get several eyes on it and fix it . ...
I'm sorry, I'm not sure what you mean by finger pointing, I wasn't
pointing any fingers, people are busy, I was was just asking you if
you could detail issues in bug reports so we could improve things for
all users and have improvements for all.
> On Mon, Apr 29, 2024, 16:01 Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> Adding arm(a)lists.fedoraproject.org back as it was dropped at some point.
>>
>> > I've never filed bug report. This is free, open source software. WiFi failing to stay connected, failing to route to anything that's not in its own subnet Bind losing it's mind about what subnet it's on GUI Begins coming up, only to black and leave you with virtual terminals.
>>
>> We use a primarily upstream linus kernel, we've never had reports from
>> users of key things like this, and I've never seen it in my own
>> testing, so I would be interested in your usecase/configuration.
>>
>> > There's so much I could say. Rather than gripe about it, i'd much rather just roll up my sleeves and find a way to help as best as I can. Been writing C/C++ on UNIX/Linux for almost 25 years now. I think that's a more productive approach.. .
>>
>> To some degree report bugs is helping because it means we can fix it
>> for all Fedora users, even if your coding ends up fixing it, because
>> it means we can ensure the fixes are in place for all users, not just
>> a single user, I feel that's a productive approach hence the request
>> for bug reports :-)
>>
>> Peter
>>
>> >
>> > On Mon, Apr 29, 2024, 15:39 Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> >>
>> >> > I'm curious now. I use ethernet on mine and almost always build custom kernels. In the absence of anything more useful, I feel motivated to play with this and see what I can see. Had plenty of other issues with RPi (4b) and Fedora tho'. Contemplating migration to Manjaro......
>> >>
>> >> What sort of issues? Can you provide some details or links to some bug
>> >> reports please?
>> >>
>> >> > On Mon, Apr 29, 2024 at 12:33 PM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> > I have a couple of Raspberry Pi 4 systems running Fedora 39 (as headless
>> >> >> > servers), but I'm now hitting kernel update issues with both of them.
>> >> >> > I've opened RHBZs on both but haven't gotten any response (they're niche
>> >> >> > issues on a somewhat niche platform, so probably not much attention). I
>> >> >> > was wondering if anybody here might have any suggestions for working on
>> >> >> > getting these fixed.
>> >> >> >
>> >> >> > One issue started with kernel 6.7 on one Pi - about 30-60 seconds after
>> >> >> > boot, it crashes back to a uboot screen (had to hook up a monitor to see
>> >> >> > it). I have netconsole set up but it doesn't show anything. This Pi
>> >> >> > has a GPS HAT set up with PPS for a time source... I suspect it may be
>> >> >> > related to that? The boot-to-crash delay is probably around the time
>> >> >> > that it takes for the GPS/PPS to start up after boot. Kernel 6.6.13
>> >> >> > still works fine.
>> >> >> >
>> >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2264560
>> >> >> >
>> >> >> > The other issue started with kernel 6.8 on another Pi - this one loses
>> >> >> > the ability to connect to a WPA3-PSK wifi network. It can still connect
>> >> >> > to a WPA2-PSK network, and kernel 6.7 can connect to WPA3-PSK. I have
>> >> >> > other (x86_64) Fedora systems that can connect to the WPA3-PSK network
>> >> >> > with kernel 6.8.
>> >> >> >
>> >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2275835
>> >> >>
>> >> >> I replied on both of those bugs. While I maintain various pieces of
>> >> >> arm kernel I don't follow all kernel bugs as I don't have the
>> >> >> bandwidth so it's useful to ping here as you've done for awareness to
>> >> >> problems.
>> >> >>
>> >> >> P
>> >> >> --
>> >> >> _______________________________________________
>> >> >> arm mailing list -- arm(a)lists.fedoraproject.org
>> >> >> To unsubscribe send an email to arm-leave(a)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
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Randall DuCharme (Radio AD5GB)
>> >> > Powered by Open Source software.
>> >> >
20 hours, 50 minutes
Re: Issues with RPi4 and newer kernels
by Peter Robinson
Adding arm(a)lists.fedoraproject.org back as it was dropped at some point.
> I've never filed bug report. This is free, open source software. WiFi failing to stay connected, failing to route to anything that's not in its own subnet Bind losing it's mind about what subnet it's on GUI Begins coming up, only to black and leave you with virtual terminals.
We use a primarily upstream linus kernel, we've never had reports from
users of key things like this, and I've never seen it in my own
testing, so I would be interested in your usecase/configuration.
> There's so much I could say. Rather than gripe about it, i'd much rather just roll up my sleeves and find a way to help as best as I can. Been writing C/C++ on UNIX/Linux for almost 25 years now. I think that's a more productive approach.. .
To some degree report bugs is helping because it means we can fix it
for all Fedora users, even if your coding ends up fixing it, because
it means we can ensure the fixes are in place for all users, not just
a single user, I feel that's a productive approach hence the request
for bug reports :-)
Peter
>
> On Mon, Apr 29, 2024, 15:39 Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> > I'm curious now. I use ethernet on mine and almost always build custom kernels. In the absence of anything more useful, I feel motivated to play with this and see what I can see. Had plenty of other issues with RPi (4b) and Fedora tho'. Contemplating migration to Manjaro......
>>
>> What sort of issues? Can you provide some details or links to some bug
>> reports please?
>>
>> > On Mon, Apr 29, 2024 at 12:33 PM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> > I have a couple of Raspberry Pi 4 systems running Fedora 39 (as headless
>> >> > servers), but I'm now hitting kernel update issues with both of them.
>> >> > I've opened RHBZs on both but haven't gotten any response (they're niche
>> >> > issues on a somewhat niche platform, so probably not much attention). I
>> >> > was wondering if anybody here might have any suggestions for working on
>> >> > getting these fixed.
>> >> >
>> >> > One issue started with kernel 6.7 on one Pi - about 30-60 seconds after
>> >> > boot, it crashes back to a uboot screen (had to hook up a monitor to see
>> >> > it). I have netconsole set up but it doesn't show anything. This Pi
>> >> > has a GPS HAT set up with PPS for a time source... I suspect it may be
>> >> > related to that? The boot-to-crash delay is probably around the time
>> >> > that it takes for the GPS/PPS to start up after boot. Kernel 6.6.13
>> >> > still works fine.
>> >> >
>> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2264560
>> >> >
>> >> > The other issue started with kernel 6.8 on another Pi - this one loses
>> >> > the ability to connect to a WPA3-PSK wifi network. It can still connect
>> >> > to a WPA2-PSK network, and kernel 6.7 can connect to WPA3-PSK. I have
>> >> > other (x86_64) Fedora systems that can connect to the WPA3-PSK network
>> >> > with kernel 6.8.
>> >> >
>> >> > https://bugzilla.redhat.com/show_bug.cgi?id=2275835
>> >>
>> >> I replied on both of those bugs. While I maintain various pieces of
>> >> arm kernel I don't follow all kernel bugs as I don't have the
>> >> bandwidth so it's useful to ping here as you've done for awareness to
>> >> problems.
>> >>
>> >> P
>> >> --
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>> >> To unsubscribe send an email to arm-leave(a)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
>> >
>> >
>> >
>> > --
>> > Randall DuCharme (Radio AD5GB)
>> > Powered by Open Source software.
>> >
21 hours, 16 minutes
Issues with RPi4 and newer kernels
by Chris Adams
I have a couple of Raspberry Pi 4 systems running Fedora 39 (as headless
servers), but I'm now hitting kernel update issues with both of them.
I've opened RHBZs on both but haven't gotten any response (they're niche
issues on a somewhat niche platform, so probably not much attention). I
was wondering if anybody here might have any suggestions for working on
getting these fixed.
One issue started with kernel 6.7 on one Pi - about 30-60 seconds after
boot, it crashes back to a uboot screen (had to hook up a monitor to see
it). I have netconsole set up but it doesn't show anything. This Pi
has a GPS HAT set up with PPS for a time source... I suspect it may be
related to that? The boot-to-crash delay is probably around the time
that it takes for the GPS/PPS to start up after boot. Kernel 6.6.13
still works fine.
https://bugzilla.redhat.com/show_bug.cgi?id=2264560
The other issue started with kernel 6.8 on another Pi - this one loses
the ability to connect to a WPA3-PSK wifi network. It can still connect
to a WPA2-PSK network, and kernel 6.7 can connect to WPA3-PSK. I have
other (x86_64) Fedora systems that can connect to the WPA3-PSK network
with kernel 6.8.
https://bugzilla.redhat.com/show_bug.cgi?id=2275835
--
Chris Adams <linux(a)cmadams.net>
23 hours, 10 minutes
Lenovo X13s Firmware Load Issues on Kernel 6.8.7-300
by Andrew Spooner
Hi all,
I have been using Fedora 40 Beta on my Lenovo X13s (followed instructions on https://fedoraproject.org/wiki/Thinkpad_X13s, thanks for those, very helpful).
However, last couple of kernel updates have brought regressions which I think are due to failing to load firmware.
dmesg has lines like : -
[ 2.596550] remoteproc remoteproc0: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn failed with error -2
[ 2.606506] remoteproc remoteproc1: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn failed with error -2
This has the impact that the power monitor doesn't seem to be able to pull battery status (pd-mapper is installed and running)
Rebooting and selecting kernel 6.8.4-300.fc40.aarch64 and this issue disappears. Is this happening to any other X13s owner? Any help a debugging the issue/resolving it without downgrading kernel would be appreciated.
Thanks
Andrew Spooner
6 days, 9 hours
Error with arm-image-installer F39 Rpi4 IoT image on F38 Host
by Derek Atkins
I just tried to use arm-image-installer to build an Rpi4 IoT image using
the Fedora-39 IoT release image:
Fedora-IoT-39.20231103.1-20231103.1.aarch64.raw.xz
I asked the installer to resize the partition.
At the end of the run, I get:
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
e2fsck 1.46.5 (30-Dec-2021)
/dev/sdb3 has unsupported feature(s): FEATURE_C12
e2fsck: Get a newer version of e2fsck!
root: ********** WARNING: Filesystem still has errors **********
resize2fs 1.46.5 (30-Dec-2021)
Please run 'e2fsck -f /dev/sdb3' first.
I'm guessing the file system was created with a newer version of e2fsprogs
than that supported in F38 (and there is no update on F38) and it created
a new default feature in the filesystem, which isn't supported in the
older version. According to google, this might be the orphan_file
feature, but I have not verified that.
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
1 week, 6 days
Unsuscribe
by vbrugel＠laposte.net
Hello.
Is it possible to unsuscribe to your list?
Thanks for your answer.
Regards,
Vincent BRUGEL
2 weeks
Mapping GPIO Pins from Wandboard to Fedora/libpiod
by Derek Atkins
Hi Arm Team,
I have a Wandboard (yeah, I know, OLD Hardware) currently running a
project, and I'm trying to add some GPIO inputs to it. In previous GPIO
handling (on a different platform) I used the /sys/class/gpio interfaces
to set up the GPIO, but I've discovered this is now deprecated and removed
from Fedora. So I installed libgpiod and am trying to use it.
I'm using
https://download.technexion.com/development_resources/wandboard/wbquad-re...
as a reference for the board layout. Specifically, on page 27, it shows
me that the JP4 header connects to GPIO3_12, GPIO3_27, GPIO6_31, CPIO1_24,
GPIO7_8, GPIO3_26, GPIO_18, and GPIO_19.
I figure that GPIO_18 is going to be gpiochip0 line 18, and GPIO3_12 will
be gpiochip3 line 12.. Except that gpiodetect only tells me I have
gpiochip0 through gpiochip6, so I'm not sure where GPIO7_8 would get
mapped. That's the first issue I have.
The second issue is that the kernel does not have any named mappings, so
running gpioinfo just displays generic data, like:
gpiochip6 - 32 lines:
line 0: unnamed unused input active-high
line 1: unnamed unused input active-high
Except, of course, looking at gpiochip3 line 12 shows me:
gpiochip3 - 32 lines:
...
line 12: unnamed "scl" output active-high [used open-drain]
Which seems to imply that that GPIO3_12 is actually used for something
else -- or my mapping strategy is off.
I'd appreciate any guidance anyone might have on this subject.
Thanks,
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
2 weeks
