Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of dtoverlay and dtparam in config.txt #248

Open
ChaosNicro opened this issue Feb 12, 2024 · 1 comment
Open

Use of dtoverlay and dtparam in config.txt #248

ChaosNicro opened this issue Feb 12, 2024 · 1 comment

Comments

@ChaosNicro
Copy link

Heya,
I'm using this with FCOS 39, so that might affect things. I'm trying to disable the internal wifi as well as the two LEDs on boot. Unfortunately putting the relevant lines into config.txt inside the EFI-partition has no effect.
I did notice that the LEDs are identified as mmc0 and mmc1 instead of ACT and PWR in /sys/class/leds/. I also have a ralink wifi-usb connected, it's leds register and react correctly when writing directly to sysfs. They do however sporadically reset after a while.

Is EDK2 responsible for implementing the options in config.txt or are they exclusive to RPi-OS/Raspian?

@alsldlflglhljlk
Copy link

While you ARE using UEFI to boot Fedora (which may change a few things), I do not believe EDK II is responsible for implementing config.txt, as that is largely a Raspberry Pi specific thing to my knowledge. What you can try doing (untested idea) is reformatting the boot partition (if any) to FAT32 and renaming the running kernel to kernel8.img and booting directly from that without the use of UEFI and see if the issue persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants