=== brainwash_ is now known as brainwash === twinsenaxe is now known as twinsenbrim [16:12] hello i have a questions [16:13] hello i might have answer, or pretend to have one. [16:13] !ask [16:13] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience [16:14] i notice my system doesnt use swap file at all it only use to much ram it is possible to combine swap and ram together to make the system faster [16:15] here i show [16:15] https://pasteboard.co/JhDlHBi.png [16:19] professor-mad: how much physical ram is installed? [16:19] professor-mad, the second your system is going to use swap, it will become very laggy. [16:20] so if you have enough RAM, don't even enable swap. [16:20] tomreyn, 6GB [16:20] and cat /proc/sys/vm/swappiness is? [16:21] diogenes_, so do you mean swap lag the system [16:21] ? [16:21] professor-mad, exactly. [16:21] not having swap, but swapping ram out to the disk will makes things feel slower most of the time [16:22] tomreyn, what is that file for? [16:22] professor-mad: that's not actually a file, but the currently running kernels' configuration for how happily it will swap out data to disk. [16:22] professor-mad, swap is ""useful"" only if you have 2GB of RAM. [16:22] so my system is good like that? [16:23] i always thought that swap file can make the system faster [16:23] that is not true [16:23] ? [16:23] i'm surprised oyu have 0 KB swapped out, but it shouldn't be more than 1 MB or so in this situation. [16:23] with default swappiness, that is. [16:24] and i think you're fine there. [16:24] so i was all wrong [16:25] or maybe swap become obsolete [16:25] now a days [16:25] right [16:25] ? [16:28] professor-mad: it's only really needed if you're generally too short of ram, or want to suspend-to-disk (hibernate) === coconut_ is now known as coconut [16:29] tomreyn, ok but if i have enough ram i have to make that partition how ever [16:29] ? [16:29] personally, on a desktop, i prefer the OOM killer kicking and terminate running software one by one rather than me running into a swapping situation. [16:30] professor-mad: no, and current desktop installers dont create it anymore [16:30] there's a swap file nowadays, a file located on the / file system [16:31] tomreyn, what is OOM? [16:32] i dont know what you mean with killer kicking [16:32] ? [16:32] "out of memory" [16:33] tomreyn, ok i got you [16:33] one more thing [16:33] the kernel will kill some processes to regain some memory when all available memory is taken (and there's no swap or this has run full as well), that's called the 'OOM killer' [16:34] i install xubuntu with uefi mode + GPT after the installation is complete what should i do next to make the system good? [16:34] that depends on what you think makes a system good [16:35] most people would probably install their favourite software [16:35] tomreyn, i mean there is nothing additional to install after full upgrade [16:35] ? [16:36] after a fresh install in eufi mode [16:36] why would there be? [16:38] tomreyn, ok tom look why i ask that questions and why i change to uefi mode [16:39] i gonna upload an image [16:39] of the issue [16:39] https://pasteboard.co/JhDwnfb.png [16:39] there said those cant be done in legacy mode [16:39] uefi is just a different boot mode than legacy bios, it doesn't have any relevant impact on which applications you can run. [16:40] so i made i uefi mode installation to make those [16:40] but even in eufi mode it cant be done [16:40] okay, this can be a notable exception to the abve [16:41] unfortunately only a couple vendors cooperate with this firmware upgrade framework so far [16:42] https://fwupd.org/lvfs/docs/users [16:42] rather this link https://fwupd.org/lvfs/devices/ [16:44] tomreyn, when i try to do that framework i get an error that my laptop doesnt support that firmware [16:44] so im stock in that [16:45] so? [16:46] tomreyn, so i guess because of that firmware is why i get some mce pcieport error [16:46] i guess if your goal is to carry out a mainboard firmware upgrade, then, unless your mainboard vendor supports fwupd/lvfs, which does not seem to be the case based on what you're saying, it means you 'll need to do it using whichever other method they provide [16:46] let me show you [16:46] !xy [16:46] The XY problem is when you need to do X, and you think you can use Y to do X, so you ask about how to do Y, when what you really should do is state what your X problem is. There may be a Z solution that is even better than Y, but nobody can suggest it if X is never mentioned. [16:46] ^ this just happened [16:47] please state the X direclty in the future [16:47] tomreyn, look here [16:47] https://paste.ubuntu.com/p/Dnr5FM96Bz/ [16:49] memory banks 6 and 7 are supposedly causing problems. but this can be unreliable. you'll need to cross test ram if you want a chance to get rid of those errors [16:51] tomreyn, so that have nothing to do with the framework [16:51] ? [16:52] it's hard to tell really, this coiuld just as well be a cpu, microcode, mainboard firmware related problem [16:52] context may help making a better bet, but you have not provided any [16:53] tomreyn, ok excuse me i new in linux i just know the basics [16:53] what you need [16:54] what info do you need [16:55] professor-mad: can you post a full journal? journalctl -b | nc termbin.com 9999 [16:55] professor-mad: and [16:56] here the journalctl [16:56] https://termbin.com/8lg3 [16:58] professor-mad: please ignore 'and' above. let's see the output of this as well (can take some minutes to gather all the logs): journalctl | grep 'Hardware Error' > /tmp/hwerr.log; cat /tmp/hwerr.log | nc termbin.com 9999 [17:01] tomreyn, ok here your output [17:01] https://termbin.com/jc20 [17:03] so you're two bios upgrades behind, possibly exposing the system to those (not only but primarily) intel cpu related vulnerabilities. [17:03] their changelogs don'T cite anything else, though [17:04] hmm looks like you've had those mce errors going for a while then [17:04] is jun 27 when you installed this system? [17:06] There's a chance that the updated microcode in combination with a non-upgraded bios causes these HW error reports, so doing the BIOS upgrade could surely help. [17:06] professor-mad: ^ [17:17] tomreyn, ok i back [17:17] tomreyn, yes i have those mce error since i installed the system [17:17] and the cpu vulnerabilities [17:18] tomreyn, i have to reinstall the system in orden to upgrade the bios [17:18] ?? [17:20] professor-mad: probably not, no [17:22] professor-mad: from what i read, there are two options: upgrade from a running windows installation (which could require reinstalling ubuntu), and from a running dos system (which, unlike a full windows installation, can also be booted from a usb key or other external storage media) [17:24] most likely they'll provide instructions on how to create such a DOS bootable usb stick and carry out the bios upgrade from there [17:34] tomreyn, ok but what about the cpu vulnerabilities [17:34] ? [17:34] how can be solve [17:34] ? [20:41] Hi. Quick question. Having accidently removed it, what is the <...> icon for in the right hand side of the top panel? [20:44] (Seen in Xubuntu 20.04) [21:07] Hi. What is the <...> icon for in the Xubuntu top panel. (I accidently removed it.) [21:08] Seburo: nm-applet (network manager) [21:09] Hi brainwash. Thanks. How could I put it back? [21:09] it appears in the status-notifier panel plugin, so maybe you removed that one? [21:10] it can fall back to "notification area" [21:10] hmmm... I put status-notifier, but I just get the up/down network arrows. [21:11] How do I link it to "notification area"? [21:11] uhm [21:11] did you change the icon theme? [21:11] No, standard defaults [21:12] panel size? [21:12] Standard default, not changed. [21:12] no idea then [21:14] nm-applet will prefer status-notifier over classic tray (notification area in panel) [21:16] Okay. Thank you for your time. [21:19] I think I have found the nm-applet option... [21:22] Going to try a restart, but thank you for your time [22:57] \quit