(05-13-2021, 03:53 PM)Frusty_the_snowman Wrote: So to dig over an old thread, but may be of use to someone else who is seeking enlightenment.
I've had this problem a couple of times with 7.2.x... I run my raspberry pi via a battery to act as a walkman when I'm a man about town. So occasionally there is an unexpected power out!
This can cause corruption of of the sdcard with the moode OS on.
The definitive symptom is the /boot/config.txt is an empty file. Why this file is affected I don't know, but there we go, if this file is empty (or wrong) its not going to work.
The automated disk-fixer may create an FSCK00xxxx file when it tries to recover a file system flagged as dirty, or so very dirty dirty... I inspected the contents of the latest FSCK file and it looked to be a complete config.txt. With some trepidation, I copied the FSCK file to config.txt, rebooted and it worked.
My /boot/config file is as below. Take care, I don't think a corrupt file here could damage your hardware, but use caution if you don't know what any effect of changes you make may have.
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=0
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=off
dtoverlay=iqaudio-dacplus
#dtoverlay=disable-wifi
#dtoverlay=disable-bt
max_usb_current=1
that fixed my sh!t too - and I'm not even a man-about-town, just a poor soul with a crappy switching power supply and a low voltage 'crash'.
Capital solution Frust, capital.
Also hats to whoever up there ↑ noted the dtparam=audio=off needs to be dtparam=audio=on. And in my case "ALSA max volume" had to be explicitly set to 100%.
