I have recently installed EndeavourOS on a Raspberry Pi 4B, and am now trying to configure it for practical use as a desktop PC. The current problem is that the os seems to have ‘lost’ the Pi’s inbuilt stereo sound port, but only displays the HMDI port, which I use via an HDMI-VGA adapter to drive my non-HDMI Acer monitor, and need to use the audio output socket on the Pi to drive a pair of stereo speakers. EndeavourOS Systems Settings cannot see the stereo sound port either. I would be very grateful for any help forum users can give.
Hello,
Please send you system logs so that we can understand what’s going on
Have you tried
dtparam=audio=on
Adding it to your /boot/config.txt
Well, here’s the result:
[petern@localhost ~]$ journalctl -k -b -0 | eos-sendlog
==> ‘curl’ failed with code 22.
==> Info: 0x0 failed, trying dpaste …
https://dpaste.com/2PYAY2SDH
[petern@localhost ~]$
so what’s going on? Supplementary information, I don’t seem to have any boot folder on either ROOT or BOOT partition.
Sorry, I’m not a systems person.
So how is it possible your are booting… I do not see /dev/mmcblk0p1 getting mounted in your logs. Did you happen to change things there with your partitions. /etc/fstab should mount /boot by it’s correct UUID. There will be nothing in /boot in root until it is mounted. Mine as follows but it will not be correct for you sudo blkid /dev/mmcblk0p1 will give yours:
UUID=27E7-00CE /boot vfat defaults 0 0
This in your log disabling headphones:
snd_bcm2835.enable_headphones=0
sudo nano /boot/cmdline.txt and add/change to this:
snd_bcm2835.enable_headphones=1
Thanks for your post rsher. However, when I tried your suggestion, the result was:
[petern@localhost ~]$ sudo blkid /dev/mmcblk0p1
[sudo] password for petern:
/dev/mmcblk0p1: LABEL_FATBOOT="BOOT_ENOS" LABEL="BOOT_ENOS" UUID="046C-87D7" BLOCK_SIZE="512" TYPE="vfat" PART
LABEL="primary" PARTUUID="2bd3e4b5-9bdb-4167-ac56-bdbd5c26b974"
[petern@localhost ~]$
This doesn’t look much like your response to the command, and there’s no reference to /boot, so what’s going on?
That is exactly what it is supposed to say. That iis where you get the UUID that is supposed to say in /etc/fstab. Make sure the UUID there says 046C-87D7
I’m afraid I couldn’t do that, because there is no fstab in /etc! Where do I go from here?
Also, I tried to investigate BOOT/ENOS using Dolphin, and got a message:
The file or folder /boot does not exist
with an invitation “to create missing folder”, which I didn’t follow, in case it messed things up further.
I have no clue what you are doing or how you are doing it. /etc/fstab should exist. I have been using the pi4 image on my pi4 and there is nothing wrong with it. I have since converted it over for use on my pi5 and nvme. The RPi firmware looks for and uses the boot partition at very first boot to boot up. With out it being there it will not boot. Then /etc/fstab is used to mount drives at boot and on the basic EOS install it mounts the vfat boot partition on the root partition at /boot so userspace can use it.
If ls /boot shows no files after booting up then it is not mounted by the /etc/fstab file. If ls /boot returns No such file or directory then it means you have deleted it and need to create it for a place holder for mounting with sudo mkdir /boot. You can temporarily mount it after booting up with:
sudo mount -t vfat /dev/mmcblk0p1 /boot
Then you should see files there with ls /boot.
Then create /etc/fstab if it does not exist with this in it:
#/etc/fstab: static file system information.
#Use 'blkid' to print the universally unique identifier for a device; this may
#be used with UUID= as a more robust way to name devices that works even if
#disks are added and removed. See fstab(5).
#
UUID=046C-87D7 /boot vfat defaults 0 0
Make sure the correct UUID=046C-87D7 is in the file or it will not mount the boot partition. Then reboot your pi4.
Probably asked an ai first that hallucinated answers which they didn’t check the sources for
Just a guess but from what I have been seeing this a rising issue
Only thing so far that makes sense.
Yer people need to learn not to just copy what it says, it can be handy (even when wrong) but without looking at what is being referenced it is useless a lot of the time from my experience
This may not be what user is doing but by what I see…
Well I was about to give up on this thread but decided to give it one more shot first.
Yer we give em a go, they reached out, least we can do is reply and try help if we can
In response to the last few replies:
I don’t rely on AI agents for accurate information, and always aim for human sources, as for example this forum.
Not being a systems person, I was relying on Dolphin to give me an accurate overview of the filesystem, as has always been my experience in other distros, but for some reason which I do not understand, it did not show the critical folders/files which other posters referred to. However, using the terminal I was able to navigate the filesystem to find the necessary files. I made the suggested addition to /boot/cmdline.txt and re-booted. The built-in audio stereo port was detected by the Audio Volume widget, so this stream has ended with success. Thanks to all who have helped push me along the way.
yer cool, sorry for thinking you were using an agent
So did dtparam=audio=on work as I suggested by adding it to the /boot/config.txt? That was a human source btw.