On Thu, 21 Mar 2024 00:59:54 -0000, Fritz Hudnut wrote:
OK, it does seem like you have to bounce back and forth to get the ticket "escalated" to players that have chops . . . .
That has been an ongoing thing. I've found their support to generally be good, and it's not a system-breaking issue for me at this point. More a minor annoyance that I get messages saying there's firmware that needs to be updated.
I just re-read the first post and I had read it as "update" . . . I did run a firmware update a couple months back that apparently was waiting since September . . . didn't hit any errors on it . . . .
I could check whatever directories you are having problems with and see what's showing in my Pop install . . . if that would give you any help?? My system is still "jammy" based . . . .
I ran your command . . . .
[CODE] $ df -h /sys/firmware/efi/efivars/ Filesystem Size Used Avail Use% Mounted on efivarfs 64K 6.6K 53K 12% /sys/firmware/efi/efivars [/CODE]
Unless you're on a Thelio Major B3, the amount of free space is probably going to be different, as our firmwares are different. Based on that your efivars filesystem space is 64K and mine is 128K, it looks like we're on different systems. The filesystem in question is nvram, so the OS won't make a difference. (I can boot into Pop_OS - without GUI because that somehow got broken on my installation, and since I run TW as my daily driver, I haven't felt the need to try to fix the Pop installation). It's something in the firmware nvram storage that's the problem, and ultimately, just a free space issue. Partially seems to have to do with how fwupdmgr protects the system by not overwriting the existing files, but creating new ones, verifying the write was successful (it seems), and then deleting the old ones. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits