You are not logged in.
Pages: 1
Hello,
After installing and fixing errors I still have some errors that I don't know how to fix.
These are the errors that appear in journalctl:
kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
systemd-vconsole-setup[453]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
NetworkManager[489]: <warn> [1587220135.2566] sup-iface: failed to cancel p2p connect: P2P cancel failed
blueman-mechani[856]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
It is a Lenovo Ideapad S145 laptop with AMD CPU / GPU, Kernel 5.6.6 and XFCE.
Thanks
Last edited by ElisardoNieves (2020-04-24 16:40:50)
Offline
What errors? Are there problems you are trying to fix?
It looks like your vconsole setup is incorrect, but other than that nothing seems out of sorts.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
How can I fix the vconsole error?
Can I ignore the other errors? Why are they leaving?
Offline
vconsole could just be a "broken" initrd, https://github.com/systemd/systemd/issues/6689
How can I fix
This is not how this works
a) don't post random lines out of context, that's meaningless
b) assuming your vconsole.conf was broken, we'd have to see it in order to make an informed comment
https://bbs.archlinux.org/viewtopic.php?id=57855
http://www.catb.org/~esr/faqs/smart-questions.html
Offline
Oops, nevermind the vconsole warning either - I just confirmed that's normal without any vconsole.conf.
You can ignore whatever you want - I'm just not sure why these lines out of the journal were of particular interest to you. The journal for my current boot is 18711 lines long. If yours is similar, would you already be "ignoring" the other 18705 of them?
That's why I asked in my first reply if there was a problem you were trying to fix. What are the symptoms? What's not working as you'd like?
In other words, you may want to bring your car to a mechanic if it's making an unusual noise, but there's no reason to bring it in just because it is making noise. That just means it's running.
Last edited by Trilby (2020-04-24 15:36:19)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I use this to look for errors, fails, bugs...
journalctl | grep "fail\|Fail\|FAIL\|warn\|Warn\|WARN\|miss\|Miss\|MISS\|error\|Error\|ERROR\|bug\|Bug\|BUG"
I believed that when there is an error, fail, bug... I have to fix it. So these errors are not relevant? Why do they come out if they are not relevant?
Last edited by ElisardoNieves (2020-04-24 15:48:52)
Offline
A bit OT, but you could probably benefit from looking at the -i flag in `man grep`.
More on topic: don't grep the journal. Context matters.
You definitely don't need to fix "fail" messages, nor really "bug" messages as if they are labeled as such it's someone else's job to patch it up. You could have a case for "error" messages, but that's debatbale. It's also a moot point as none of the messages you listed include an error.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I'm a beginner when it comes to Archlinux but I just checked my journalctl and I see a lot of errors there as well, but my system runs fine and
don't have any symptoms either. I think the well known principle/quote applies here: "Don't fix what ain't broke"
Last edited by f33dm3bits (2020-04-24 16:12:04)
Offline
OK. I think I get it. I shouldn't worry so much about mistakes like this.
The command I am executing is not correct? What command should I run if I want to know if there are startup, shutdown, system, application errors...?
I like to have a system that works as well as possible and that is "do it yourself". So I decided to switch to Arch Linux, but I am a little lost. I have been without Linux for almost 10 years.
Last edited by ElisardoNieves (2020-04-24 16:14:28)
Offline
FYI:
$ journalctl | grep "fail\|Fail\|FAIL\|warn\|Warn\|WARN\|miss\|Miss\|MISS\|error\|Error\|ERROR\|bug\|Bug\|BUG" | wc -l
6832
Of course this is less than meaningless. The following would be only merely meaningless:
$ journalctl -b | grep -i "fail\|warn\|miss\|error\|bug" | wc -l
57
Last edited by Trilby (2020-04-24 16:15:18)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
To filter journal messages by priority use the --priority= argument rather than piping through to grep like a caveperson
Jin, Jîyan, Azadî
Offline
I think I already understand.
Thank you very much for your help.
Offline
The wiki has a lot useful information
Last edited by f33dm3bits (2020-04-24 16:28:54)
Offline
Thank you! That section will not come yet.
Last edited by ElisardoNieves (2020-04-24 16:37:09)
Offline
Pages: 1