I've been having trouble with this update.INXI report shows system trying to use three vid card drivers at once despite Driver Mngr showing NVIDIA 340 proprietary Driver checked and in use.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.
Reason:Topic automatically closed 6 months after creation. New replies are no longer allowed.
gm10 wrote: ⤴Mon Aug 06, 2018 3:28 pm
If your drive gets re-mounted as read-only that means it's got errors. GRUB's recovery options include fsck to check your file systems.
The ACPI errors would need a BIOS update to fix. They should not lead to crashes though, you likely had them with your previous kernel as well.
This old machine has had those ACPI errors listed since day1. The last line in the "errors" display is new,though.
The line in the INXI report for the vid driver should read:
Display Server:X.Org 1.18.4 drivers: nvidia (unloaded:vesa,fdev,nouveau)
Oh, the inxi thing is an inxi bug. Try updating to the current version:
Code: Select all
sudo rm /etc/inxi.conf;sudo inxi -U;sudo inxi -U
And the cinnamon segfault is in case of doubt due to the disk errors. If not then you can always switch back to the previous kernel via the GRUB menu.
During the Meltdown & Specter issues earlier this year,it was suggested that I execute that line code command but this machine is incapable of loading latest version. The ACPI errors don't really effect the performance of this machine,at all.The system trying to run 3 vid card drivers at the same time is an issue,though.The same thing happened when the 4.13 series of kernel's where first introduced to the machine.That problem was fixed.
I'm going to keep using 4.13.0-45 for the time being and maybe I'll have better luck with next kernel update coming soon.
Xorg will never run 3 drivers at once, this is certainly a bug in the inxi output. I don't know what's wrong with your inxi update but this here will work for sure:
It installs the latest version only locally for your user (run it like you always do).
Regarding the ACPI errors, you could also disable ACPI by adding acpi=off to the GRUB kernel options. Not saying you have to, just for your information.
Xorg will never run 3 drivers at once, this is certainly a bug in the inxi output. I don't know what's wrong with your inxi update but this here will work for sure:
It installs the latest version only locally for your user (run it like you always do).
Regarding the ACPI errors, you could also disable ACPI by adding acpi=off to the GRUB kernel options. Not saying you have to, just for your information.
Thanks. I'll give that line code a whirl.As far as "acpi=off",I tried that once and i didn't know the fan had a speed that high.I thought the machine was going to take off.I'm going to refrain from trying that,again.It got rid of the ACPI errors but the fan went nuts.
Yeah, you'd have to set power management parameters in the BIOS if you disable that. But as I said, you don't have to disable acpi, those errors won't break your system (as you know).
This is INXI report as displayed using kernel 4.13.0-45.The "Display Server" line of the INXI report reads as it should and the last line of the "errors" display isn't present as it is with INXI report using kernel 4.15.0-29.
Oh, inxi is providing the error output? I didn't even know it did that, what option does that?
Also ignore that I said about disk errors, that output is just the normal remount that occurs during boot, it's not an error. I had misunderstood it since it was listed within the other actual error messages. I'm not sure what that line is doing there.
gm10 wrote: ⤴Mon Aug 06, 2018 5:23 pm
Oh, inxi is providing the error output? I didn't even know it did that, what option does that?
Also ignore that I said about disk errors, that output is just the normal remount that occurs during boot, it's not an error. I had misunderstood it since it was listed within the other actual error messages. I'm not sure what that line is doing there.
This is an old shell script command I discovered out here one day on LMforums: inxi -F && dmesg | grep -i error
It does JeremyB. It's an inxi bug with the version he had, it was even discussed with the inxi dev on these forums here and then fixed.
Jeremy Mendes wrote: ⤴Mon Aug 06, 2018 5:35 pm
This is an old shell script command I discovered out here one day on LMforums: inxi -F && dmesg | grep -i error
Oh ok, that explains it. Thx.
Last edited by gm10 on Mon Aug 06, 2018 5:58 pm, edited 1 time in total.
To be precise, X.org or something related to it got a bug that double loaded drivers, and inxi pre version 3.0 had failed to handle that scenario/bug, since it should never have happened. As noted, inxi now works around this bug in X.org or whatever is creating that double loaded driver situation. This fix was not really practical to do in old inxi, but was fairly easy in new inxi. This is in general why distros that use inxi for support should not be using anything but current git master branch version of inxi in their repos, fixes can't be sent along to users unless new inxi is used.
the errors this poster shows aren't related to inxi, because each line in inxi has its logic before the line prints, not after, so when you see those last error lines, that's something else going on, particularly with the ext4 error, which I would personally be concerned about if I were that user.
h2-1 wrote: ⤴Wed Aug 08, 2018 3:33 pm
the errors this poster shows aren't related to inxi, because each line in inxi has its logic before the line prints, not after, so when you see those last error lines, that's something else going on, particularly with the ext4 error, which I would personally be concerned about if I were that user.
Hey h2-1, good to see you, I always meant to ask why inxi lists my webcam as a network device. Just kidding, this is not the place, so back on topic: those lines at the end are some dmesg output that he pasted at the end. That ext4 line isn't actually an error, it's just the normal rw remount happening during boot when the ro kernel option is set.
Oh, I thought it was the same terminal output, that's good, otherwise he'd have bigger problems, heh.
Feel free to post issues on github inxi, your input has been valuable. I don't check these forums that often, just now and then at random.
Re webcams, you can imagine my surprise when I discovered that my builtin lenovo t420 webcam was listed as a --usb device, at which point I realized, oh, man, I had no idea that internal stuff runs on the USB bus too. If you want to run a --debug 22 I'll take a look to see if I can figure that specific issue out however.
Driver Mngr. claims nvidia 340 is driver in use and is driver recommended for the hardware.
Last edited by Moem on Sat Aug 11, 2018 3:20 am, edited 1 time in total.
Reason:Swapped the [list] tags out for [code] tags; the code tags retain some formatting that makes your output easier to read.
Interesting, it's still listing two drivers despite the latest inxi, might still be a bug with inxi there. Since he was already in the thread, let me ping h2-1:
However, it shows that your nvidia driver failed to load, so it's not being used. Your /var/log/Xorg.0.log might have further information as to why it fails loading. I'm not an nvidia user myself so I'm not familiar with the common issues you run into with that driver. I know that people are pulling the newer versions from a PPA but I don't know if those versions actually still apply to your old GPU.
You can get two drivers active as far as Xorg is concerned, I see that all the time, for example, ati,radeon. When a driver in inxi is listed as a driver, it means it was loaded, and did not get unloaded, and did not fail. I don't actually know how xorg thinks about this internally, since it's quite common to see two drivers listed as the drivers. Could be two graphics devices, I really can't say.
One thing we can know for certain is that this nvidia driver FAILED, you also see it because there is no OpenGL data.
nvidia failed for one of several reasons:
1. failed to blacklist modesetting/nouveau in kernel boot parameters in grub
2. failed to use correct bus id in xorg.conf, usually it finds it itself, unless you have multiple gfx devices.
3. wrong driver, or driver that does not work with the kernel in use
4. improperly installed driver
Based on the output, my guess is that nouveau/modesetting were not blacklisted in grub conf, so those were loaded, and then made nvidia fail.
Just kidding, this is not the place, so back on topic: those lines at the end are some dmesg output that he pasted at the end. That ext4 line isn't actually an error, it's just the normal rw remount happening during boot when the ro kernel option is set.