@pseudonym A lots of timeouts is not normal output and
dmesgno change after insertion could mean that there is something wrong with the port or since power on the device is hanging, is there any other warning or error messages in your
dmesgoutputs I noticed a warning about ehci_hcd module which says:
Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
Causing some other errors:
pci 0000:00:12.0: quirk_usb_early_handoff+0x0/0x6c6 took 78473 usecs pci 0000:00:13.0: quirk_usb_early_handoff+0x0/0x6c6 took 71414 usecs pci 0000:00:14.5: quirk_usb_early_handoff+0x0/0x6c6 took 71438 usecs pci 0000:00:16.0: quirk_usb_early_handoff+0x0/0x6c6 took 71602 usecs QUIRK: Enable AMD PLL fix
Where I can find the modules list and reorder to not make my system “quirk”?
I’m getting this error on my dmesg output:
x86/CPU: CPU features have changed after loading microcode, but might not take effect. x86/CPU: Please consider either early loading through initrd/built-in or a potential BIOS update.
My CPU is an AMD FX8350, being an AMD CPU the microcode comes inside the
linux-firmwarepackage and as everybody knows, all motherboards of same era is EOL, so no more BIOS updates, my questions are:
- Is there any way to load the AMD microcode earlier and how could I do that?
- This could be considered an upstream bug?
Your drivers seems normal.
dmesgbefore insert the card then after insert the card can give some idea of what is wrong;
If no system reaction on
dmesgsometimes can be something stuck in the card reader slot like dust bunny or hair;
A lots of GUI based programs it just locked by design to NOT run as root;
Messing with file permissions will render a dead system as it seems your not familiar with *nix based systems;
Not being a programmer, any copy/paste script can be a hook to well deigned malware turning your rig a zombie for some botnet or mining cryptocurrency for someone else;
As @just said it’s feasible but be prepared to be a Bear Grylls for your rig as everything can go wrong depending on your knowledge level of *nix based programs.
I just built from AUR and set my theme to Adapta (my prefered is Adapta-Nokto) and look like this, but since I never learned CAD this is what I’ve got
It’s strange that doesn’t work for you, but I’m glad that you found a workaround .
For Eagle I think I can’t help, I built successfully from AUR but I don’t have any account to proceed
Hmmmm… After reading again your posts, did you tried to genarate an image from your Windows disk and tried to run from it? I know that is a shoot in the dark but after removing all passthrough devices the disk could be out of sync as the partition drivers fails to read and write hard locking the system.
Also iommu trees must be entirely passed to guest machines, passing one device can cause instabilities, to get your iommu group information I found a script on Gentoo wiki (https://wiki.installgentoo.com/index.php/PCI_passthrough) that collects information needed:
for iommu_group in $(find /sys/kernel/iommu_groups/ -maxdepth 1 -mindepth 1 -type d); do echo "IOMMU group $(basename "$iommu_group")"; for device in $(ls -1 "$iommu_group"/devices/); do echo -n $'\t'; lspci -nns "$device"; done; done
And also I found some information about nvidia in guests that if the driver detects that is inside of a vm will disable itself here: https://davidyat.es/2016/09/08/gpu-passthrough/
@quimkaos You and your logs don’t describe your rig, debugging software without hardware it’s almost impossible tell us what cpu, ram and graphics card please.
Sometimes the problem is hidden in something else, like yesterday, my wife ancient PC had a crash with openSUSE Tumbleweed software updater and gnome with xorg with discret radeon graphics stopped work giving garbled graphics and constant freezing falling back to gdm, the system was usable with wayland but had no video acceleration in browser, so, no way to watch youtube and similars, having that I convinced her to move to same distro as me turning my work more simple but after installing Antergos I got similar behaviour then I took about 2 hours to discover that the
xf86-video-atiwas the culprit, removing it was my solution but I installed
xf86-video-amdgpuas backup since there is no full documentation where one begins and ends when radeon driver is on, the only thing that I really know is that ati driver carries microcodes which I suppose that the compatible ones overwrites same address space causing the graphics card ring 0 to stall.
Well, as I said software depends on hardware, having that in mind
journalctloutputs can help to find the root of problem, so, more information here and more heads to think we can figure out together.