Hang on , that does not make sense.
All the space within a partition is ‘allocated’
and
the fat filesystem will use surelyall the space in the partition… unless you recovered it from CZ onto a larger partition maybe?
So do you mean ‘unused’ space… that is harmless
1 Like
I quoted Gparted error message when I said unallocated. Let me check my EFI backup and see if it has the error.
Sheila
1 Like
My backup ext SSD with MX on it does not show that error when I load it in Gparted nor when I boot from it. Surely as I am still booting that is not an imperative "fix now,’ is it?
We had this BT issue occur on Sat when I first did some things recommended where later that day, same issue and BT would connect but not show up in pavucontrol to select as output. I used TS to roll back to Fri and it again worked.
But I can’t roll back to Fri until I get my TS working to ensure it did not remove all of those backups I had stored and used on Sat.
Sheila
1 Like
I think it may be a red herring.
You have more to attend to… ignore it
I need to convey this thought to you
Switchin back and forth between systemd and sysVinit is not a good idea. If you do an install under systemd, then switch to sysvinit, it may not work, and vv.
It way even be the source of your issues.
I think, given that pipewire requires systemd, you can either have
- PA + PW with systemd
- PA with sysvinit
and you had better settle on one and stick with it.
2 Likes
So for now, here is my plan:
a) make TS snapshot with my system & dot folders/files included on my ext SSD drive (since the ext HDD is not working)
b) reinstall MX and see that all is working sound-wise
c) compare what is different between the two; I have images on that ext HDD that could be restored with CZ that is IF CZ can access the drive OR restore the TS snapshot from today where sound was not working.
Worst case, I guess I have to reinstall all of my apps and settings since I no longer have access to my Timeshift snapshots to use as an older restore. That would not happen till this weekend as I do not have the time until then.
Sheila
4 Likes
When you get to that, decide on one init system. and stick to it. No switching.
I think I read somewhere that once you turn on systemd in MX you should not turn it off again… that may be the cause of your issues
1 Like
I have. I had forgotten that I started with sysV so I could learn it and when it took writing a script to get the calendar app working to sync with my phone, I gave up and went back to sysD and never even got the app runnning on MX (it is now on LM desktop).
So sysV it is.
Thanks
Sheila
2 Likes
OK. That is what MX installs as by default.
You will end up like my MX… pulseaudio and no pipewire.
Did you read the bit in my last reply about not turning systemd off once you turn it on? … that may be the cause of all this.
2 Likes
That’s not how I understood it worked. When I looked at my Advanced GRUB to try and find an older kernel to boot (remember I had none and had to install them), I was then booting systemD version of MX. When I looked at the only other kernel, I thought, “Why do I have the exact same kernel to boot?” Now I know that the sysV MX has no name at the end to signify init. Only sysD does. Once I switched to the one with nothing at the end of the name, I was in the sysV and it is then I found the "other’ one in Advanced GRUB that stated the name of the kernel with “system D” at the end.
So it was my understanding that you boot into the main MX and it has sysV. In order to switch, maybe I installed the sysD version, don’t remember.
But I will make sure that only the sysV is installed. AT least then our sound files should be the same.
Thanks for the heads up.
Sheila
3 Likes
OK, I misinterpreted that thing I read about switching to systemd.
What I understand now is
- when you first install MX it is sysV
- if you elect to switch to systemd, it makes another kernel, and gives it a .sysd suffix on its name
- you cant switch the .sysd kernel back to sysvinit, but you can obviously boot the sysvinit kernel
- both kernels share the same package installs and configs… that spells trouble to me
Given that, I dont know whether init system issues is responsible for your MX sound and disk issues… it is a guess… we will probably never know.
2 Likes
If it’s about reinstall: the system-wide configs are in /etc. Back it up as a whole. Your personal settings are mostly in -/.cconfig, but in your home. Back up your home as a whole.
I think when I redid my server I also saved /var/lib, bur not sure you will need that.
Do the reinstall, for borh the system and your apps.
Restore your home as a whole, all your settings will be there. If something needs to be reconfigured system-wide, the config for it will be in the backed up /etc dir. Don’t restore the etc as a whole, use only the pieces from the backup, which you need exactly. For example we use Samba in our LAN, I’d restore /etc/samba/smb.conf. But restoring /etc/fstab from the previous install would result in an unbootable system. So use only the portion you really need from tbat saved /etc.
How do you know you need something from there? You face a problem, something doesn’t work, look it up, and find it has to be configured in /etc/whatever. Just take the whatever from the saved /etc.
2 Likes
I suspect something was installed from the “test” repo, which caused the interfere.
For pulseaudio you need to install pulseaudio-module-bluetooth package.
Without that PA can’t work with BT.
It’s just Gparted not knowing Fat32. Install dosfstools package, and Gparted magically gets the power to handle Fat32.
4 Likes
Oh yes.
I thought it was irrelevant.
2 Likes
I got that wrong too, I seem to have pipewire
Audio:
Device-1: Intel C600/X79 series High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1d20 class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
So you should get PW + pipewire-pulse
Sorry, I am having trouble grasping all this
1 Like
That fixed it. Now It automatically selected the BT speaker as output without my assistance.
Thanks so much @kovacslt !
Sheila
4 Likes
I did find out how to use “Preserve /home” while preparing to install MX on the same partition.
Providing you do not have /home on a separate partition (I use ext HDD, but only for personal files; dot files/folders are in /home on the internal SSD), during the installer step where you choose the partition to use and assign its use (/) and format, under format there is an option to chose “Preserve /home” that means it will erase everything else except that. I am unsure how that will assist with the non-Linux apps that have to be reinstalled, but I figured it was worth giving it a try.
If after the install, sound is working, I may choose to just go through the User Installed packages tool in MX and deselect any I do not wish to reinstall and see how that works out.
Worst case, we go back and format the partition and reinstall fresh. I will need to run through the os-prober after install to ensure Garuda is back on MX GRUB menu.
Will update once completed.
UPDATE: For some reason, when using preserve /home option, it tries to go delete the rest of the OS but reported it was unsuccessful in doing so then exited the installer.
So now attempting with out saving dot files/folders.
That was fast. And forget os-prober, since it used the same EFI partition, the first boot to GRUB had the Garuda option and successfully booted as before.
Now onto testing sound, etc.
Sheila
1 Like
And we still have no sound from internal speakers. You can see the level surge while in pavucontrol while playing a wav file in VLC, but no sound is heard.
Let me get some specs to show on this fresh install and see if there was something installed from that user installed package list that differs here.
Sheila
1 Like
Additional issue is MX does not see the ext monitor I have always used with it. It says nvidia firmware and nvidia-detect is installed, but no 2nd monitor in display settings.
I need to get that fixed for my old eyes before I start working on speaker issue.
UPDATE:
I guess I assumed the purpose of using AHS version meant it would install a working driver for my Nvidia. It did not, apparently as choosing from MX Tools the Nvidia installer, it did so in terminal.
Now a reboot should fix that issue.
UPDATE:
It did not. Apparently a different driver is needed. But will get to that after testing other live sessions below.
Sheila
1 Like
Sorry, my browser was 4 levels of recursive entry into the forum page and not seeing updates… I missed all your action here.
So you have a fresh install of MX… and sound still has problems?
Is it still a raw install with no apps added?
I am starting to suspect ahs… its sound components may be too new and faulty?
Could you try a live flash drive of normal MX… see if it is going to work before trying to install it.
1 Like
Sure. I have installed no apps yet since wasn’t sure I am keeping this fresh install.
Let me boot live to a non-AHS version. Not sure I have one on the flash drive, so will download it.
Sheila
1 Like