qt.svg: Error while inflating gzip file: SVG format check failed
I’ve been googleing and I can’t find any solution except something related with the icon or with Qt. If it’s just that I wouldn’t worry because I don’t have the icon in use, but a glyph in the launcher bar. Could it be that?
Because I notice a bad performance in my Mabox I started to investigate what kind of problems I could have, I started using journactl to see the logs, I copy and search in google for answers that I can understand to see if I can get back to the good performance as usual, I have already ruled out RAM and Disk problems.
I’m going to post some things here in case you find something that might help me.
This problem seems to be associated with the realtek board, “r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control” Could my board be causing the problem or could it be a problem with the kernel?
I tried to revert to a previous kernel from the control center and it performs the whole process but still runs the same kernel, it does not replace the one running and does not give me the option to remove it.
Is it safe in Mabox to change the kernel as recommended by the Manjaro forum?
After googling for a while this other problem “at24 6-0050: supply vcc not found, using dummy regulator” seems to be a bug reported in kernel 6.1.0-10 associated with power management, should not have problems on a desktop PC, but maybe I misunderstood, I guess it’s not something I can fix.
This other error found
“intel_rng: FWH not detected”
apparently says I don’t have the right technology, also associated with the kernel as I understood I can disable it, if you help me with this it would save me a lot of time.
About “r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control”
The message indicates that the Realtek r8169 driver is unable to manage ASPM (Active State Power Management) for the network interface card (NIC) because the operating system does not have the necessary permissions or control over ASPM settings. This is a common issue with certain hardware and driver combinations, particularly in systems with specific BIOS configurations.
Understanding the Issue
ASPM Control: ASPM is a power management feature that allows devices to enter low-power states when not in use. If the OS cannot control ASPM, it may lead to suboptimal power management and potentially impact performance.
BIOS Settings: The BIOS may have settings that restrict the OS from managing ASPM. If ASPM is disabled in the BIOS or if the firmware indicates that ASPM should not be managed by the OS, you will see this message.
Driver Limitations: The r8169 driver may not support ASPM for your specific chipset or configuration, leading to this warning.
Potential Solutions
Check BIOS Settings:
Enter your BIOS/UEFI setup during boot and look for any settings related to power management or ASPM. Ensure that ASPM is enabled if available.
Look for options like “PCIe Power Management” or “ASPMLink State” and set them appropriately.
Some BIOS settings might have options labeled as “PCIe ASPM” or “Link State Power Management.” Make sure these are set to Enabled.
Kernel Parameters:
You can try adding kernel parameters to force enabling ASPM at boot:
Edit your GRUB configuration:
sudo nano /etc/default/grub
Modify GRUB_CMDLINE_LINUX_DEFAULT to include pcie_aspm=force. It should look something like this:
About at24 6-0050: supply vcc not found, using dummy regulator
This indicates that the system is unable to find a voltage supply (Vcc) for an AT24 EEPROM device, and as a fallback, it is using a dummy regulator. This message is generally not critical but can indicate a potential issue with hardware configuration or driver support for the EEPROM device.
Understanding the Message
AT24 EEPROM: The AT24 series includes various EEPROM devices that are often used for storing configuration settings or other small amounts of data. The message suggests that the driver expected to find a power supply for the EEPROM but could not.
Dummy Regulator: The use of a dummy regulator means that the driver will simulate power supply behavior, which may allow the device to function in a limited capacity. However, this may lead to suboptimal performance or functionality.
Again, enter your BIOS/UEFI settings and look for options related to I2C devices or power management. Ensure that any relevant settings are enabled.
Hi, @sng Thank you very much for your contributions, now I will dedicate myself to make the changes you propose and as for EEPROM I guess my machine lacks that technology because it is very old, from 2007. It only has two possibilities to receive electricity, one through the power supply, another through the Bios stack, it is not uefi. I will check this and if it has a solution I will apply it, in any case, once the work is finished I will post again to comment the results.
Something happened after the reboot, I checked the parameters inside the Bios and modified the power related, I enabled what was disabled like the Pcie case, previous to that I installed the r8168, but I couldn’t because of yay, it gave an orphaned so I selected the ones that were available and the change didn’t work, then through the software store I installed the rest. The PC took longer to boot and when it did it used an older kernel, it is now using 6.11.2-4-Manjaro, I guess because of the changes made, I will check that and then let you know what I find.
Hi @sng , I tried everything you indicated, some things were solved but when modifying the grub, the boot failed, appeared the message ‘No resume device found,exiting" but the process continued, slower but Mabox works, first boot changed the kernel, I had in use the 6.54 … now, with the new reboot it took the kernel 6.12.0-rc ie the experimental. Now I want to change it but I can’t do it through the control centre, i.e. it installs the other available kernels but only takes 6.12…
I edited grub again, commented out the two lines I added and the No resume… message disappeared but the experimental kernel remains.
I’m going to see how I can fix it through the terminal, and if I can’t I’ll try chroot from live.
Anyway I’m experimenting because I don’t have the knowledge to do it.
I’ve always solved everything with the help you give me, I trust this time will be no different.
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
#GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR='Mabox'
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=b6c8299f-6640-47b8-8545-24e0f88a4203 udev.log_priority=3"
#GRUB_CMDLINE_lINUX_DEFAULT="quiet splash intel_rng.no_fwh_detect=1"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=force"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
GRUB_BACKGROUND="/usr/share/grub/background-mabox.png"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
Everything seems to be in order, visually I have my desktop, my conky, my top bar as usual, Firefox is running, PCmanfm, and I have a leafpad open with the grub data so I can share it, the rest seems to be working properly, that’s why I don’t understand what’s going on.
It seems that every time I tried to install a kernel something happened and that’s why it gives so many installations, the thing is that I can’t remove them, I don’t know why.
You just have almost all of the currently supported kernels installed…
I would suggest you test two or three of them, and remove the others.
Test that your system works well with those 2-3 kernels, look at the image as to how to select the kernel to boot each time.
You may have a different grub theme, but the entries will be pretty much the same.
I believe you can remove more than one kernel at once (I haven’t tested that). If this is not the case, remove them one by one
sudo mhwd-kernel -r linux61-rt
sudo mhwd-kernel -r linux610-rt
sudo mhwd-kernel -r linux611-rt
sudo mhwd-kernel -r linux66-rt
Just make sure (uname -r) you do not try to remove the kernel you are running.
Now, which kernels should you retain?
I would suggest, given that your system is a bit older, you keep the latest lts kernels (linux515 , linux61 and linux66). This way, when you are done, you will end up running 6.6.54-2-MANJARO (linux66)
Yes, thank you very much, for that reason is that I put the grub in visible mode, I could select the best kernel for my machine, which I see is the 5.10.226-1 that has support until 2025, I will leave some of the line 6.xxxxxx for when this no longer receive more updates, the thing is that I can not remove the others, I do not know why, but the removal of kernels does not work, maybe now with this installed I can do it, I am also interested in removing the headers, I will try tomorrow to see what result I get.
Again, thank you very much for your patience and help.
