[00:00] <IRCMonkey> Oh O.K.
[00:00] <Thete> anyone know by chance which version of gcc is default on 21.04?
[00:00] <Thete> is it 9 or 10?
[00:00] <IRCMonkey> Right now the store made 2 partitions: OS partition with 200 GB & 265 GB for my files, I'm not happy with this, I'd like one large partition.
[00:01] <tomreyn> Thete: 10
[00:01] <Thete> ty
[00:02] <jacke> how is ubuntu latest vs LTS? do you experience stability issues?
[00:02] <tomreyn> Theyou can check this for yourself on https://packages.ubuntu.com or with rmadison / dak ls
[00:02] <Bashing-om> IRCMonkey: My system as an example of a tight working install: https://termbin.com/sp48 .
[00:02] <tomreyn> Thete: ^
[00:03] <ezzieyguywuf> is there a flag for `apt get` that will auto-select `yes`?
[00:03] <ezzieyguywuf> ah, -y
[00:03] <ezzieyguywuf> nvm
[00:03] <IRCMonkey> Back -looking-
[00:04] <tomreyn> Thete: https://people.canonical.com/~ubuntu-archive/madison.cgi
[00:04] <Thete> I saw that, but for some reason my system was using gcc-9 by default
[00:04] <Thete> so I'm guessing I messed something up
[00:04] <Bashing-om> IRCMonkey: My partitions named: https://termbin.com/0ykq
[00:04] <Thete> which is why I was confused
[00:05] <tomreyn> https://people.canonical.com/~ubuntu-archive/madison.cgi?package=gcc&s=hirsute says 10.3.0
[00:05] <IRCMonkey> Oh c00
[00:05] <IRCMonkey> @ Bashing-om
[00:08] <IRCMonkey> I named my C:\ "Op Systems" & D:\ "Data"
[00:09] <Bashing-om> IRCMonkey: My booted system's disk usage: https://termbin.com/jc42 . As you can see the operating system does not need much room.
[00:10] <IRCMonkey> Brilliant !
[00:10] <Bashing-om> IRCMonkey: Ouch - in linux a space is seeen as a file delimiter - you will have a learning curve to deal with any spaces.
[00:11] <IRCMonkey> Do I select "Third-party" drivers during install for it to automatically detect & install Intel HD Graphics\ WiFi or will I have to provide the driver with the disk for it ?
[00:12] <jacke> yup
[00:12] <tomreyn> IRCMonkey: you need neither
[00:12] <Bashing-om> IRCMonkey: Neither - Intell drivers are in the kernel :)
[00:12] <IRCMonkey> File names cannot have spaces ??
[00:13] <IRCMonkey> Oh good
[00:13] <jacke> If you dont need them they wontbe installed
[00:13] <jacke> never have spaces in file names!!!!
[00:13] <IRCMonkey> OMG !
[00:13] <IRCMonkey> But I want my screen resolution to be 1366x768
[00:14] <IRCMonkey> What do I do with all my files in my USB sticks with spaces ?
[00:14] <Guest39> I installed Ubuntu 20.4 hoping for a miracle and no... Same issue on first boot. I'm gonna give up for today, I'll try again tomorrow.
[00:14] <Guest39> Thanks everyone for your help.
[00:15] <jacke> B4 you install any linux...run a live version to see if everything works...then install...
[00:15] <Guest39> The live install works perfectly fine
[00:15] <leftyfb> jacke: that doesn't always give you a good idea of how well it's going to run
[00:15] <Guest39> this is a video card issue
[00:16] <Bashing-om> IRCMonkey: Spaces: not what I implied - just that a space in a fike name takes extra care to cope with. Op Systems straight up will be seen as 2 files: "Op" and "Systems" also linux is case sensitive - op and Op are seen as 2 different files.
[00:16] <jacke> then you can make the install work just as well
[00:16] <Guest39> I think..
[00:16] <tomreyn> Guest39: :-/ sorry we couldn't help. one more thing that may be the diffference between live and install may be microcode updates.
[00:16] <IRCMonkey> Ohhh O.K.
[00:16] <IRCMonkey> No I don't plan on naming my drives or anything.
[00:16] <leftyfb> tomreyn: and hwe kernel and no running from squashfs and video drivers, etc
[00:16] <IRCMonkey> But filenames can contain spaces amirite ?
[00:17] <Guest39> jacke Probably yeah but I've been trying for the last ~6 hours with the help of people here and nothing worked so far so I'm done for the day :)
[00:17] <tomreyn> leftyfb: 21.04 has no hwe kernel by default
[00:17] <leftyfb> tomreyn: "<Guest39> I installed Ubuntu 20.4 hoping for a miracle and no"
[00:17] <tomreyn> Guest39: similar to "nomodeset" you can use "dis_ucode_ldr" to override the microcode loading
[00:17] <tomreyn> leftyfb: yes, but it was all about 21.04 before this.
[00:18] <leftyfb> ok, yeah, just joining now
[00:18] <Bashing-om> IRCMonkey: Yes file names "can" contain spaces but in use these spaces will have to be escaped so the system sees them as one file. A pain sometimes to keep track of.
[00:18] <Guest39> tomreyn No worries, really appreciate your inputs. Alright last test and I'm done for today ^^
[00:19] <tomreyn> Guest39: you're welcome
[00:20] <IRCMonkey> Oh O.K.
[00:20] <tomreyn> Guest39: yet another suggestion: this computer is old enough that it was probably shipped (and primarily tested) with classic bios booting by default. you could try switching to that (but need to reinstall then).
[00:23] <Guest39> The first install was with the BIOS option enable in BIOS. But I guess I also need to change the way I create my booting drive right?
[00:24] <tomreyn> if you make the bios boot in 'legacy' bios mode (rather than UEFI), then do a standard installation, you'll be set
[00:24] <tomreyn> but i'm not sure i got the question right
[00:26] <Guest39> Right now I'm using ventoy for my bootable drive using GPT partition. Do I need to create a more "old school" installation drive in addition to enabling Legacy BIOS?
[00:28] <oerheks> ventoy ... never heard of that before
[00:28] <tomreyn> i don't know for sure whether ventoy will be bale to boot in both uefi and bios mode, and whether it will be able to boot the ubuntu installer in either mode.
[00:28] <tomreyn> bale -> able
[00:29] <Guest39> I've got tons of usb drive I can just create another one the old school way
[00:29] <oerheks> Secure Boot was supported from Ventoy 1.0.07, but the solution is not perfect enough. So from ventoy 1.0.09, an option for secure boot is added in Ventoy2Disk.exe/Ventoy2Disk.sh and default is disabled. So by default, you need to disabled secure boot in BIOS before boot Ventoy in UEFI mode.
[00:29] <oerheks> hmmm, questionable tool it is..
[00:29] <oerheks> https://www.ventoy.net/en/doc_secure.html
[00:30] <Bashing-om> Guest39: Tje mode that you boot the installer in is the mode that will be used to install; Bios or UEFI.
[00:30] <oerheks> use mkusb, rufus ..
[00:30] <jacke> GPT for UEFI boot in bios
[00:30] <jacke> turn off secure boot
[00:31] <oerheks> secureboot is not a problem, fastboot is.
[00:31] <Guest39> I've used rufus before. Ventoy is more convenient, I can just drop a collection of ISOs on a key and install whatever I need
[00:31] <Guest39> secureboot is disabled. Fastboot is enable, I'm not sure how that could cause the issue I'm seeing
[00:31] <jacke> secureboot can be aproblemif he's booting an unsigned kernel
[00:31] <oerheks> Guest39, interesting, but you are here for hours now..
[00:32] <oerheks> omg .. fastboot enabled..
[00:33] <oerheks> take some time to read the UEFI manual
[00:33] <oerheks> !uefi
[00:35] <Guest39> It just says to disable it without any explanation why. I just disabled it and no change.
[00:36] <oerheks> we don't know either about that tool, it is not in our recommended list
[00:37] <oerheks> https://ubuntu.com/tutorials/create-a-usb-stick-on-windows
[00:38] <Guest39> tomreyn dis_ucode_ldr didn't help :(
[00:39] <tomreyn> Guest39: a pity. :-/ have a good night, more luck tomorrow!
[00:39] <Guest39> oerheks I mean at this point I'm willing to try anything but I don't see how just changing the tool I use to setup my install drive going to change anything. It works perfectly fine on live image, issue appears after install.
[00:40] <Guest39> tomreyn Thanks again, see you
[00:40] <IRCMonkey> O.K. that'll be all thanks Bashing-om, tomreyn & jushur for answering my woes.
[00:45] <oerheks> Guest39, good, try rufus and let us know.
[00:48] <me_> this is my first time using an irc
[00:49]  * jacke slaps myself with a trout..
[00:49]  * jacke slaps himself with a trout..
[00:50] <me_> /etc/apt/trusted.gpg
[00:50] <jacke> me_: Hi!
[00:51] <jacke> me_: dont paste things that can be used against you here!
[00:51] <jacke> ...even just a path
[00:51] <me_> ok
[00:56] <niksen> you have the right to remain pasteless
[01:01] <jacke> You have the right to remain pasteless. Anything you paste can be used against you in court. You have the right to talk to a linux user for advice before we ask you any questions. You have the right to have a linux user with you during questioning. If you cannot afford a  inux user, one will be appointed for you before any questioning if you wish. If you decide to answer questions now without a linux user present, you have the right to stop answering alt any
[01:01] <jacke> time.
[01:08] <leftyfb> jacke: please take it to #ubuntu-offtopic. This is a support channel
[01:22] <Guest39> oerheks Just used the ubuntu recommended way to create a install stick using Startup Disk Creator on Ubuntu (don't have access to a windows machine right now) and same issue..
[01:26] <maxh> I have several unity-scope packages preventing me from upgrading gir1.2-unity. I can safely remove them, right?
[01:27] <guiverc> Guest39, did you validate your ISO?  https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#0
[01:32] <Bashing-om> maxh: If ' apt show <package_name> ' shows as "optional"; then yes can safely be removed.
[01:34] <Guest39> guiverc just did all good
[01:36] <guiverc> I'd assume bad write to media then.. I find about 5-8% of writes are bad (usb-flash-media is made to cost and not quality), so I'd try booting it on other box; if it doesn't complete media validation there - likely a bad write.
[01:36] <guiverc> Guest39, ^
[01:40] <Guest39> guiverc Thanks for your input but this not my issue at all. I'm created 2 different install drive with 2 different method, the issue is the same. Live image is all good. Installed ubuntu "works" I just have display issue probably because of the Nvidia card.
[01:41] <Guest39> In any case I said I would stop troubleshooting for tonight, Just wanted to confirm that my way to create bootable drive had no issue..
[01:41] <guiverc> I didn't see your prior posts, your message I did see mentioned "used the ubuntu recommended way to create a install stick using Startup Disk Creator on Ubuntu... same issue" so my comment was based on that.
[01:43] <Guest39> got it my bad if I sounded snapy
[01:43] <guiverc> not a problem Guest39
[02:03] <SupremeKai> Hello! I've used "sudo dpkg --verify" to check if everything is fine and I got this output: https://paste.ubuntu.com/p/XTcNP2FNSC/ - what does this mean? those files were changed?
[02:03] <SupremeKai> as far as I know, dpkg --verify verifies the installed apps and other stuff right?
[02:58] <nsguest> I just discovered focuswriter, and it looks great, but I want a dead simple kid friendly write words over scanned background page for a kid with disgraphia. Focuswriter doesn't seem to do any sort of background image on the page (just around it) over
[02:59] <nsguest> Any suggestions?
[04:47] <IRCMonkey> Should I get Ubuntu Long-term-support or the latest one ?
[04:47] <IRCMonkey> Itching to try out the latest version […]
[04:48] <lotuspsychje> the users choice IRCMonkey
[04:48] <lotuspsychje> feel free to start a topic in #ubuntu-discuss
[04:49] <IRCMonkey> Alright, I'll go with the latest version —even my IRC client's beta build. :D
[04:50] <krytarik> lotuspsychje: Isn't that on-topic for here though?
[04:51] <Mekaneck> it is on topic imo
[04:51] <Mekaneck> it's a question about Ubuntu
[04:52] <lotuspsychje> i never said its offtopic, im suggesting he can discuss it further
[04:52] <Mekaneck> not needed in discuss :)
[04:53] <Mekaneck> IRCMonkey: long term support versus 9 month support, choose wisely
[04:53] <IRCMonkey> Alright thanks, I will !
[07:15] <bomzh1018> I want to open a terminal on startup, run a command in it, and then keep it open
[07:15] <bomzh1018> how can I do that?
[07:18] <bomzh1018> if I put `mate-terminal -x COMMAND` in "startup applications", will it stay open after running that command?
[07:20] <alkisg> mate-terminal --tab -e "command1" --tab -e "command2" --tab &
[07:20] <alkisg> That one opens 2 commands in two tabs, and a third tab with the prompt
[07:20] <alkisg> If you want just one, it's just one -e
[07:22] <bomzh1018> thanks alkisg!
[07:23] <bomzh1018> BRB, testing
[07:30] <bomzh1018> okay, I'm halfway there
[07:30] <bomzh1018> I rebooted, the terminal with the result of the command (less) was opened, but the issue is, when I exit less, the terminal closes, and I'd like it to remain open - is there a way to do this?
[07:30] <alkisg> bomzh1018: that would mean that you'd run bash, not a command
[07:30] <alkisg> So: mate-terminal -e "bash -c 'command'"
[07:31] <alkisg> Wait
[07:32] <alkisg> mate-terminal -e "bash -c 'less /etc/adduser.conf && exec bash'"
[07:32] <alkisg> This works, but it would be simpler to do it via a bash script, like mate-terminal my-session
[07:32] <alkisg> Then my-session would run less and then it would exec bash
[07:34] <bomzh1018> do I need to explicitly add `exec bash` to this new script?
[07:34] <alkisg> Yes, to specify that you want to read the user's stdin from that point on
[07:36] <bomzh1018> thanks, trying...
[07:41] <bomzh1018> not quite. Now I got a terminal, but it was empty, with no less output
[07:41] <bomzh1018> what I added to "Startup applications" was the following:
[07:41] <bomzh1018> mate-terminal ~/Estate/record_time.sh
[07:41] <bomzh1018> and record_time.sh is https://paste.ubuntu.com/p/sgTRRVZcpB/
[07:42] <oerheks> use full path
[07:43] <bomzh1018> BRB, trying
[07:46] <bomzh1018> nope, the same, empty terminal
[07:46] <alkisg> bomzh1018: you forgot the -e, `mate-terminal -e ...`
[07:46] <alkisg> Also did you chmod +x the shell script?
[07:46] <alkisg> You don't need to logout to test
[07:46] <alkisg> Just run the command in a terminal
[07:48] <bomzh1018> 1) got it
[07:48] <bomzh1018> 2) yes, I set a+x
[07:48] <bomzh1018> 3) works now in terminal, need to reboot to see if it works in real situation, BRB
[07:49] <alkisg> bomzh1018: sudo systemctl restart lightdm
[07:50] <alkisg> A faster test than reboot
[07:51] <bomzh1018> YES! Now it works exactly as I want it to. Thanks a lot, guys!
[07:51] <oerheks> have fun!
[08:55] <shibboleth> sarnold, oerheks, remember me? https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892
[08:56] <shibboleth> yeah, rmmod tpm works, the system now boots with recent/updated grub2. funny thing is, i have two identical boxes, neither have a tpm and only one is affected by this issue...
[08:58] <shibboleth> also, not an issue on grub2 2.02-2ubuntu8.21 (but on every following update)
[09:02] <oerheks> shibboleth, file a bugreport?
[09:02] <oerheks> !bug
[09:02] <shibboleth> it's the same as they existing one
[09:02] <shibboleth> also, same as https://bugzilla.redhat.com/show_bug.cgi?id=1833148
[09:02] <shibboleth> https://bugzilla.redhat.com/show_bug.cgi?id=1779611
[09:04] <oerheks> or confirm that one. comment #3 said 2.04-1ubuntu12.1 fixed it.
[09:05] <shibboleth> yeah, it did not
[09:05] <shibboleth> at least not on 1804, the thread is by a user on 1904
[09:35] <eFfeM> Hi, In my log (20.04) I see messages about gltlab-runsvdir.service being unable to start as there is no runsvdir-start file
[09:35] <eFfeM> actually I do not recall installing anything gitlab related. How do I get rid of this?
[09:37] <eFfeM> the only thing I have in /opt/gitlab/embedded/bin is a symlink prometheus linking to itself; not even sure what that is (or how I got /opt/gitlab in the first place)
[09:38] <TJ-> eFfeM: by installing something from outside the Ubuntu archives
[09:39] <eFfeM> TJ-: hmm, yes, but what (and how to find out what it is)
[09:39] <TJ-> eFfeM: only you can know that!
[09:39] <eFfeM> actually this system is updated over and over again from 12.04 or so
[09:40] <eFfeM> so it carries a lot of history :-)
[09:40] <TJ-> /opt/ is for optional non-distro packages
[09:40] <alkisg> What's the output of `dpkg -S /opt` ?
[09:40] <TJ-> eFfeM: maybe the timestamps on those directories will give you a clue?
[09:40] <oerheks> progs in /opt/ probably never updated
[09:41] <eFfeM> TJ-:  output is
[09:41] <eFfeM> signal-desktop, skypeforlinux, wine-stable-amd64, wine-stable-i386:i386, wine-stable, youtube-to-mp3, google-chrome-stable, net.downloadhelper.coapp, gitlab-ee, jd-gui, google-earth-stable: /opt
[09:41] <eFfeM> guess gitlab-ee is the bad guy, timestamp is from 2018
[09:55] <shibboleth> and here are a bunch of others: https://bugs.launchpad.net/snapd/+bug/1878541
[09:56] <shibboleth> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892
[09:56] <shibboleth> also affects debian. confirmed and unassigned since last year
[09:59] <TJ-> shibboleth: what architecture is the UEFI on your system? The only significant recent change that is in grub-2.04 is to add support for 32-bit UEFI
[09:59] <shibboleth> x86, haswell
[09:59] <TJ-> shibboleth: that is, enable tpm module on 32-bit firmwares
[10:00] <shibboleth> https://lists.gnu.org/archive/html/grub-devel/2019-10/msg00104.html
[10:01] <shibboleth> Mathieu Trudel-Lapierre wouldn't happen to work at canonical/ubuntu?
[10:01] <TJ-> shibboleth: I'm aware of that
[10:01] <shibboleth> since i have two identical boxes and only one is affected it is likely i might be able to help narrow down the exact cause
[10:04] <Lutin> People here running succesfully docker swarm on 21.04 ? I'm having swarm connection issues and I would like to know it's it's distro related
[10:06] <TJ-> shibboleth: at what point does the boot fail? before the linux kernel is loaded into memory, or after?
[10:07] <shibboleth> bios post->grub menu->black screen+cpu freeze after selecting/timing out
[10:09] <shibboleth> when menu -> c -> set debug=all -> esc -> select it freezes during.... disk/efi/efidisk.c reading 0x40 sector from sector... something
[10:10] <shibboleth> due to OOM if i've understood the threads
[10:11] <TJ-> shibboleth: have you tested using one of the Advanced sub-menu options where they write "Loading kernel..." "Loading initrd..." so you know which stage it reached?
[10:11] <TJ-> shibboleth: I do a lot of hacking on GRUB so may be able to narrow this down
[10:11] <shibboleth> the boxes are identical. call the alice and bob. bob always fails to boot with grub > grub2 2.02-2ubuntu8.2. i can take the drive from alice, also fails in bob. drive from bob works fine in alice
[10:12] <shibboleth> TJ-, please xplain the adv submenu stuff?
[10:14] <shibboleth> i was hit by this issue in after an apt-get upgrade eraly/mid May. only thing that worked was to replace the .efi binaries in /boot/efi/... with the ones from  grub2 2.02-2ubuntu8.2. issue persist on all of the... four grub2 updates released since
[10:14] <TJ-> shibboleth: if you can access the GRUB menu (tapping Esc key as GRUB starts) or set the config to show it by default (/etc/default/grub "GRUB_TIMEOUT_STYLE="menu"  "
[10:15] <TJ-> shibboleth: then the Advanced sub-menu lists Recovery boot options, and they report what stage the file loading has got to.
[10:15] <shibboleth> yeah, one sec
[10:15] <TJ-> Therefore, if using one of those you don't see "Loading Linux..." we know it is happening before or during that stage. By adding your own "echo 'Reached stage X' " in front of each line in a menuentry block, you can identify exactly where GRUB is getting to
[10:16] <shibboleth> ok, in advanced. do in just select the recovery option or do i add any flags?
[10:16] <TJ-> shibboleth: initially I'd add a line just before the 'linux ...' line saying "echo 'About to load Linux...' " then Ctrl+X to boot with that, and see what you get
[10:17] <shibboleth> there already is an echo "Loading $linuxkernelversion"
[10:18] <shibboleth> and a sep one for init
[10:18] <shibboleth> rd
[10:18] <TJ-> shibboleth: oh yeah, of course!
[10:18] <TJ-> shibboleth: ok, so just boot with that entry (I was thinking of the opposite of what I do when there are initrd.img problems and I add a line /after/ the intrd ... line to ensure it was loaded into memory
[10:19] <shibboleth> ok, loading linux $version, loading initial ramdisk -> freeze
[10:20] <TJ-> shibboleth: great... so now try again with my initrd process - add a line after "initrd ..." with "echo 'Loaded initrd, handing over to kernel now...' "
[10:23] <shibboleth> doesn't echo what i added after initrd
[10:23] <TJ-> shibboleth: good - so we know it fails during loading of the initrd
[10:24] <shibboleth> well, yeah. since the kernel is signed it would be bizarre otherwise :)
[10:24] <TJ-> shibboleth: can you tell me how large the initrd.img file is "ls -l /boot/initrd.img*"
[10:28] <TJ-> shibboleth: did you see the message written by this line? grub_error (GRUB_ERR_OUT_OF_MEMORY, "cannot allocate pages");
[10:29] <shibboleth> no, and now it froze doing ls -al (hd0,gpt2)/*
[10:30] <TJ-> shibboleth: so EFI didn't run out of memory. Secondly, can you put GRUB into debug mode and tell if/what this line reports as values " grub_dprintf ("linux", "[addr=0x%lx, size=0x%lx]\n", " - this is just before it calls the EFI loader for the initrd.img
[10:32] <shibboleth> ok, froze a second time doing ls -al (hd0,gpt2)/*
[10:32] <shibboleth> ten, the third time i did rmmod tpm, ls -al (hd0,gpt2)/*
[10:32] <shibboleth> now it lists and doesn't freeze
[10:33] <shibboleth> initrd: 59985151
[10:34] <shibboleth> unlikely to be the initrd itself since i actually get a cpu stall doing ls -al from grub shell  without rrmod ttpm
[10:35] <TJ-> shibboleth: OK, just checking, since I hit a size-related bug recently
[10:35] <shibboleth> without rmmod tpm it freezes after listing half the files/folders in /boot
[10:36] <shibboleth> cuts at x86_64-efi
[10:36] <TJ-> shibboleth: ok, you need to add "debug=linux" to the grub environment. You should be able to do that by, at the grub menu, pressing 'c' to get to the command-line, then typing "set debug=linux" then press 'Esc' to return to the menu, then go to the Advanced sub-menu and boot one of those entries again
[10:36] <TJ-> shibboleth: If I've got the correct you should get debug messages only related to loading Linux
[10:37] <TJ-> shibboleth: and bonus points for taking a photo of the resulting messages and uploading it for me!
[10:37] <shibboleth> yeah, nothing. freezes after loading linux $version, loading initrd
[10:38] <shibboleth> i tried adding debug=chain,secureboot,lb
[10:38] <shibboleth> and i got secureboot 0, setupmode 0 then freeze
[10:38] <TJ-> hmmm, then I think you will need to add the line "debug=linux" to the menuentry block itself in the Advanced menu. (press 'e' to edit the block as before, put that as the first line, then press Ctrl+X)
[10:39] <TJ-> shibboleth: do you have GRUB set to boot in graphical or text mode? text mode might help here
[10:39] <shibboleth> text
[10:40] <TJ-> good
[10:40] <shibboleth> is it possible to pipe the output from debug=all/debug=linux to a file?
[10:40] <shibboleth> then i could just pull the drive and upload
[10:40] <TJ-> add the 'linux' debug condition and try again
[10:40] <TJ-> shibboleth: no
[10:41] <TJ-> shibboleth: 'all' slows things down and is generally not a good thing - changes behaviour such as trying to catch race conditions
[10:42] <TJ-> shibboleth: you're seeing "setupmode 0" so that shows debug=secureboot is working at least
[10:43] <shibboleth> i'm downing a sandwich, brb
[10:43] <TJ-> I'm chasing flying ants!
[10:48] <shibboleth> ok, i'm back. trying menu -> c -> set debug=linux -> esc ->boot menuitem first
[10:51] <shibboleth> loader/i386/linux.c:669 trying linuxefi, loader/i386/linux.c:682 handing off to linuxefi -> freeze
[10:52] <shibboleth> set debug=linux doesn't produce any extra output when booting the recovery option, but produces the above for the "default" option
[10:54] <shibboleth> TJ-, but, eh... seriously. the grub binary completely *borks* doing a simple ls -al without rmmod tpm? what in the name of a lot that is holy?
[10:55] <shibboleth> it's not the file system of /boot. i've done fsck and it works totally fine in alice
[10:55] <TJ-> shibboleth: makes sense... GRUB asks EFI to read the file-system... which will contain files not signed
[10:56] <TJ-> and TPM tries to 'measure' (verify) file(s) and fails
[10:57] <shibboleth> well, these are consumer asus mobos with no tpm
[10:57] <TJ-> shibboleth: doesn't surprise me. Code originally added by mathew garret :)
[10:58] <shibboleth> dunno what that means :)
[10:58] <shibboleth> well, the name doesn't ring abell
[11:00] <TJ-> shibboleth: long history :)
[11:00] <TJ-> shibboleth: anyhow, try adding "debug=tpm..." to your list of debug conditions; let's see what the module /thinks/ it has found. I've just spotted a potential bug in handling of grub_tpm_handle_find
[11:01] <shibboleth> and what between 2.02-2ubuntu8.21 and 2.02-2ubuntu8.23 can have caused this? also, mind verifying that 8.23 hit main repos early/mid may?
[11:01] <shibboleth> ok, trying debug=tpm
[11:03] <shibboleth> menu -> c -> set debug=tpm -> esc ->boot menuitem -> black screen/freeze
[11:03] <shibboleth> no output
[11:03] <shibboleth> set debug=linux,tpm?
[11:03] <TJ-> shibboleth: mix in all the other you were using, just in case - it'd be good to know the entire debug= isn't being ignored
[11:04] <TJ-> shibboleth: and always use the Advanced sub-menu options so we should at least get those "Loading ..." messages
[11:06] <shibboleth> yeah, using any of the advanced options i only get loading linuxversion, loading initrd even if i added set debug=foo
[11:06] <shibboleth> set debug=chain,linux,tpm,secureboot and booting "default" i get  trying linuxefi, secureboot0, setupmode0, handing off to linuxefi ->freeze
[11:09] <TJ-> shibboleth: you see "efi" just after "handing off to linux" ?
[11:09] <shibboleth> loader/i386/linux.c:669 trying linuxefi, loader/i386/linux.c:682 handing off to linuxefi -> freeze
[11:09] <TJ-> or is "efi" part of your added message
[11:09] <TJ-> ahhh, that one
[11:09] <TJ-> shibboleth: AHA! "i386"
[11:10] <shibboleth> ok, lemme try the same on alice and see if it dosn't say i386
[11:11] <shibboleth> says i386 on alice as well
[11:11] <shibboleth> but it proceeds after those two lines
[11:11] <TJ-> shibboleth: in my source for 2.02 there is no "trying"
[11:12] <shibboleth> well, right now bob is on bionic grub2 latest, 2.04 something. otherwise there'd be no point in debuggin, eh?
[11:13] <shibboleth> how would that work? me: boots fine, you: ok
[11:13] <TJ-> none of those strings exist in upstream GRUB
[11:14] <shibboleth> there even are line numbers, 669 and 682
[11:14] <shibboleth> i doubt we're talking gremlins
[11:15] <TJ-> aha, Ubuntu patch  debian/patches/0076-ubuntu-Make-the-linux-command-in-EFI-grub-always-try.patch
[11:16] <TJ-> 118 line patch, too, and invasive for the 'linux' command
[11:25] <TJ-> the critical part based on our experiments so far is " initrdefi_cmd = grub_command_find ("initrdefi");" in grub-core/loader/i386/linux.c::grub_cmd_linux()
[11:27] <TJ-> shibboleth: right, another debug condition to add: "linuxefi" so we can monitor grub_cmd_initrd()
[11:29] <shibboleth> ok, that produced some more text, one moment
[11:32] <shibboleth> set debug=linux,chain,tpm,secureboot,linuxefi: loader/i386/linux.c:669 trying linuxefi, kern/efi/sb.c:46: secureboot: 0, kern/efi/sb.c:54: setupmode: 0, then several lines of loader/i386/efi/linux.c, then loader/i386/linux.c:682 handing off to linuxefi -> freeze
[11:32] <shibboleth> it's like fifteen lines, anything specific too look for or you need it all?
[11:44] <shibboleth> TJ-, ping
[11:50] <TJ-> shibboleth: sorry, attacking ants again!
[11:50] <TJ-> shibboleth: uf the last line i the 'handing off to linuxefi' I presume you're not now seeing the "Loading linux ..." echoed?
[11:51] <shibboleth> ok, something funky. on alice (the one that doesn't freeze), grub menu -> c -> ls -al (hd0,gpt2)/* also cuts at x86_64-efi but it doesn't freeze, returns to grub cmd. doesn't list the kernel, initramfs
[11:51] <shibboleth> lemme retry after rmmod tpm
[11:52] <shibboleth> nah, doesn't list kernel, initrd
[11:52] <shibboleth> TJ-, see pm
[11:53] <shibboleth> whereas on bob (the one that does freeze) it freezes after listing x86_64-efi, lists all (including kernel, initrd) after rmmod tpm
[11:56] <shibboleth> dunno if that matters at all, but... funky?
[11:57] <shibboleth> no, nothing after  loader/i386/linux.c:682 handing off to linuxefi
[12:04] <tomreyn> i'm not sure that grub's "ls" understands "-al"
[12:04] <shibboleth> set debug=linux,chain,tpm,secureboot,linuxefi <--- add initrdefi?
[12:04] <shibboleth> well, it does on bob
[12:06] <tomreyn> yes it does, i just tested as well
[12:06] <shibboleth> +initrdefi, same output as without
[12:06] <TJ-> shibboleth: no "initrdefi" - that is a command name. "linuxefi" is the condition
[12:07] <TJ-> shibboleth: at this stage I'd suggest building and testing without the debian/ubuntu patches since I've a strong feeling the interference that several of the Ubuntu patches is doing into this very area is the cause
[12:07] <TJ-> shibboleth: some of those patches are copied from RedHat too
[12:08] <shibboleth> ok, lemme read up on deps/procedure
[12:09] <shibboleth> but seriously, why doesn grub-efi on alice list vmlinuz, initrd?
[12:09] <shibboleth> whereas bob freezes unless rmmod tpm, lists vmlinuz, initrd after rmmod tom
[12:10] <shibboleth> this is like... imagine looking at a petri dish of bacteria in a microscope and seeing 300 hamsters doing the macarena
[12:10] <TJ-> shibboleth: interacting in slightly different ways with the firmware
[12:13] <shibboleth> well, does ls -al (hd0,foo)/* list vmlinuz, initrd on bionic at your end?
[12:15] <shibboleth> also, which repo should i clone?
[12:15] <TJ-> shibboleth: I don't use bionic, and don't have hardware free to test on
[12:16] <TJ-> shibboleth: I'd use the Ubuntu package source but remove the patches (they're applied using quilt so easy to reset the Quilt stack to no patches)
[12:18] <TJ-> shibboleth: it's a right mess; 238 patches!
[12:18] <shibboleth> http://archive.ubuntu.com/ubuntu/pool/main/g/grub2-unsigned/grub2-unsigned_2.04.orig.tar.xz ?
[12:19] <TJ-> shibboleth: "sudo apt-get build-dep grub2" and "apt-get source grub2" then "cd grub2-unsigned-2.04" then "export QUILT_PATCHES=debian/patches" ... then "quilt applied" will list all applied patches
[12:20] <TJ-> at that point you can test removing all patches with "quilt pop -a"
[12:20] <TJ-> shibboleth: no guarantee the package will build cleanly though
[12:23] <shibboleth> isn't  the point not to apply the patches?
[12:24] <TJ-> yes, that is what we're doing
[12:24] <TJ-> strangely I cannot get the build-dep's installed on 20.04!
[12:25] <TJ-> shibboleth: when extracting the Debianised sources the patches are already applied, so we have to use 'quilt pop -a' to unapply them
[12:35] <shibboleth> git clone -b ubuntu/bionic-updates https://git.launchpad.net/~usd-import-team/ubuntu/+source/grub2-unsigned
[12:35] <TJ-> shibboleth: solved that (custom kernels here) . Doing a teset build without patches
[12:35] <shibboleth> this will clone the sources for current bionic grub2 without patches
[12:35] <shibboleth> 2.04-1ubuntu44.1.2 (patches unapplied)
[12:40] <shibboleth> TJ-, hit a snag, pardon?
[12:47] <TJ-> shibboleth:  you hit a snag?
[12:47] <shibboleth> haven't built grub before, trying trying to find out how to get the raw .efi binary
[13:02] <shibboleth> tj: ok
[13:02] <shibboleth> i've built this: git clone -b ubuntu/bionic-updates https://git.launchpad.net/~usd-import-team/ubuntu/+source/grub2-unsign
[13:02] <shibboleth> should be what we're looking for, eh?
[13:03] <TJ-> shibboleth: doesn't that contain the ubuntu patches?
[13:03] <shibboleth> no, they're not applied
[13:03] <shibboleth> https://code.launchpad.net/~usd-import-team/ubuntu/+source/grub2-unsigned/+git/grub2-unsigned
[13:04] <shibboleth> applied/ubuntu/bionic-updates 	2021-06-07 	
[13:04] <shibboleth> 2.04-1ubuntu44.1.2 (patches applied)
[13:04] <shibboleth> ubuntu/bionic-updates 	2021-06-07 	
[13:04] <shibboleth> 2.04-1ubuntu44.1.2 (patches unapplied)
[13:04] <goddard> on my laptop it displays 3 power modes, but my desktop only shows 2.
[13:05] <shibboleth> i've got the .efi binary, i should replace grubx64.efi on bobs /boot/efi/etc?
[13:05] <TJ-> shibboleth: what command did you use to build it though? usually the tooling applies the patches automatically when doing the build
[13:06] <TJ-> shibboleth: in theory yes but you'll also need to matching modules installing
[13:06] <shibboleth>  /configure --prefix=/foo/grub2 --with-platform=efi
[13:06] <TJ-> unless you built with all modules built-in
[13:15] <aiena> is there a way to get the latest virtualbox on ubuntu without using oracle repositories?
[13:15] <aiena> or the deb
[13:15] <tomreyn> you could build it from source
[13:16] <aiena> hmm so all those options will be unsupported either way
[13:16] <aiena> except for the repo version
[13:16] <aiena> ubuntu
[13:17] <tomreyn> canonical would not support any of them, i guess. in ubuntu's repositories, virtualbox will be in universe
[13:18] <aiena> ok
[13:18] <tomreyn> i'm not sure what oracle offers supprot for
[13:18] <aiena> I don't think they'd care I actually prefer KVM but I am tryingo out genymotion for android and it prefers vvirtualbox
[13:19] <tomreyn> if you want vitualbox working on ubuntu, in my experience your best option is to use oracles' apt repositories on an Ubuntu LTS release
[13:20] <aiena> I am on 20.04.2 LTS focal
[13:25] <aiena> tomreyn: do you know if there is a way to find out and uninstall packages from a user added repor in apt source and then remove that line?
[13:25] <aiena> O had added a collabora repo which I no longer want but dnt want stray packages from it on my system in case they are still there
[13:26] <Habbie> aiena, apt-forktracer can be useful
[13:27] <Habbie> and aptitude search '~i(!~ODebian)'
[13:27] <Habbie> i got that one from https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.en.html
[13:27] <Habbie> but it should work on Ubuntu, perhaps replace the name, of course :)
[13:30] <rapid16> I'm trying to work with a project that requires PHP 8, but it seems Ubuntu only has 7.5.x
[13:30] <tomreyn> aiena: apt list --installed | grep ',local\]$'
[13:30] <rapid16> I'm using Focal Fossa, should I just grab PHP binaries and over-ride symlinks?
[13:31] <tomreyn> aiena: run the above after deactivating those 3rd party apt repositories + sudo apt update
[13:32] <aiena> tomreyn: so a local package is one which is not linked to any repo anymore? like a mnually installed .deb etc.
[13:32] <tomreyn> yes, aiena
[13:32] <aiena> thanks
[13:33] <tomreyn> more precisely, a package version not provided by any of your currentlöy active (and known, to apt's cache) apt repositories
[13:34] <aiena> will it work is package foo was from another repo but had the same name in the official ubuntu repos too
[13:35] <tomreyn> if the version differs to those available in ubuntu, then it's still a "local" / "foreign" version and will be listed by either this or apt-forktracer.
[13:35] <tomreyn> i would not recommend aptitude these days, but YMMV.
[13:36] <tomreyn> yet another approach is apt-show-versions as discussed at https://github.com/tomreyn/scripts#foreign_packages
[13:39] <ApostleInTriumph> Hello. how do I rename all files in my directory that ends with .obj.npz to .npz ?
[13:41] <alkisg> ApostleInTriumph:  for f in *.obj.npz; do echo mv "$f" "${f%.obj.npz}.npz"; done
[13:41] <alkisg> If this shows the correct thing, then remove the "echo" so that it does the actual mv
[13:42] <TJ-> ApostleInTriumph: the Perl 'rename' tool is the best option, with something like "rename --nono 's/.obj//' *.npz"
[13:42] <ApostleInTriumph> alkisg thanks!
[13:43] <ApostleInTriumph> TJ- thanks for your reply too. seems more easier
[13:43] <ApostleInTriumph> and what is s/ in the command?
[13:44] <tomreyn> the initiator of a so-called "regular expression"
[13:44] <TJ-> ApostleInTriumph: rename takes a Perl regular expression
[13:45] <ApostleInTriumph> Thanks!
[13:45] <TJ-> ApostleInTriumph: just be aware both these methods don't rename .something.obj.npz files (dot-files) - you'd need to set a shell opt to get those too (I often need to do this with build product)
[13:54] <MrSid> hello. i am having a problem with editing the network-config file. i have had it working in the past and i remember to get it working the indentation has to be just right... but this time i just can't get it right. if anyone has some advice i would be very appreciative to know it
[13:54] <MrSid> for installing to raspberry pi 3
[14:06] <ducasse> MrSid: please don't crosspost, your wasting people's time
[14:06] <ducasse> *you're
[14:07] <MrSid> ok . sorry . getting used to the rules
[14:14] <BluesKaj> Hi all
[14:14] <MrSid> hello
[14:37] <Guest67> how to avoid summary of directories listing and directory names?
[14:39] <Guest67> trying to compose ls command to list all files recursively and sorted by modification time, without interruptions by these pseudo directories . and .. and summaries
[14:40] <Guest67> i have ls -lRrt1 what is missing?
[14:47] <Guest67> looks like -1 is irrelevant, also -l can be replaced with -g for less noise
[14:48] <Guest67> sorry irrelevant i did not mean to ping you
[14:49] <leftyfb> Guest67: you should look into "tree" instead of ls
[14:51] <Guest67> isn't tree only for listing directories?
[14:51] <ioria> Guest67,  if you really want to use 'ls', you can try  grep -v /;   ' ls -gRrt | grep -v / '
[14:52] <leftyfb> Guest67: "tree -t" does exactly what you're looking for
[14:53] <leftyfb> Guest67: or -Dct if you want to display the modification time, not just sort them by it
[14:57] <Guest67> tree -Dct prints too much noise, like ascii vertical and horizontal lines
[14:58] <Guest67> i just wan ta plain list of files, sorted by modification time
[14:58] <leftyfb> Guest67: -i
[14:58] <leftyfb> Guest67: you need to read man pages
[14:59] <Guest67> just saying, i could have found -i perhaps on my own had i not been busy chatting here, but tree -Dcti returns me to original problem with ls, it prints directory names...
[15:01] <Guest67> "-i Don't print indentation lines."
[15:02] <Guest67> tree --help | grep indent
[15:02] <leftyfb> Guest67: find . -type f -printf "%T@ %Tc %p\n" | sort -n
[15:07] <Guest67> leftyfb this does it i think, still checking to verify
[15:08] <leftyfb> Guest67: you can write a script to pass basename or xargs and strip out the directory from the filename at the end. Gets a bit tricky with spaces in the names. Regardless, you'd get much better help in #bash
[15:26] <Guest67> thanks leftyfb this last command did the trick
[15:29] <Guest67> ioria the problem with your suggestion was similar to ls alone, i get these "total" summary lines and so on, and this also breaks the sorting, i only want a plain list of all the files, sorted, regardless where they are within dir hieracrchy
[15:30] <ioria> Guest67, well, just add 'total  ' to the ignore:   e.g.   ll -R | grep -v '/\|total '
[15:31] <ioria> but ,again, ls is not the tool for that (i guess)
[15:33] <Guest67> ioria what is that in front of -R?
[15:33] <ioria> ll = 'ls -l'
[15:34] <Guest67> ah... some kind of short? double l?
[15:34] <ioria> yep
[15:34] <Guest67> haha cool! and it works too! :D
[15:35] <RougeR> Heya
[15:36] <RougeR> Im struggling with using a portrait tertiary monitor in ubuntu 20.10
[15:36] <ioria> Guest67, truly  'll = ls -al '
[15:36] <RougeR> Whenever i set the monitor as portrait, it causes that screen and the adjacent screen to be severely misaligned
[15:37] <RougeR> the mouse/window alignement is off by the width of the window i think
[15:37] <RougeR> ive tried using arandr to set the monitor layour/orientation and have the same result
[15:38] <Mekaneck> RougeR: can't really help but know that 20.10 nears EOL on the 22nd of July, so you'd upgrade to 21.04
[15:38] <RougeR> Mekaneck, yeah i upgraded from 20.04 last week to try resolve some driver issues
[15:38] <RougeR> the multi monitor setup is only having issues due to me changing from AMD to Nvidia gpu
[15:39] <RougeR> i might try upgrade to 21.05
[15:39] <RougeR> i might try upgrade to 21.04
[15:39] <Guest67> thanks for the tip ioria. sadly while this does remove the "total" lines it still leaves empty lines between each group of files within any given sub-directory, and tit breaks the sorting.
[15:39] <RougeR> yeah for what its worth
[15:40] <RougeR> GPU: Nvidia 2070S, Monitors: 1200x1920 dell 24" (hdmi), 2x 2560x1600 HP 30" (displayu port)
[15:40] <RougeR> worked fine with my old AMD rx480
[15:41] <Guest67> so yeah, using ls (or double l ;) alone for this is probably not the best idea. i was originally hoping to find an option within ls that says something like "do not list directories", instead i found that the tree command has the "-d" option to "list directories only". not exactly what i wanted.
[15:41] <RougeR> i know its a known but, but its just weird that i cant find anyone else with the same issue as me. I wonder if its something to do with 16:10 2560x1600 monitors...having 2 of them is not common
[15:43] <RougeR> https://askubuntu.com/questions/1230570/cant-rotate-monitor-on-20-04
[15:43] <RougeR> aha
[15:43] <RougeR> yeah this is the same issue as me
[15:44] <RougeR> seems to not be exclusive to 20.10, same issue in 20.4
[15:48] <RougeR> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/187421
[15:56] <bewees> hi
[15:56] <bewees> if I download a package source files, where can I see the compile options Ubuntu uses or do the package source files don't contain those?
[15:57] <bewees> I want to check if the qemu package is compiled with virgl on ubuntu focal
[16:00] <alumno> hola
[16:01] <alumno> hi
[16:01] <tomreyn> hi alumno
[16:02] <alumno> hi HerbY_NL2
[16:04] <tomreyn> bewees: see the "rules" file in the tarball
[16:18] <bewees> tomreyn: thanks! found a rules file both in the tar.xz source file and also inside debian/rules using the downloaded source files with `apt-get source qemu-system-x86`. In neither I see virgl, so I assume it's not compiled with it by default :-)
[16:19] <RougeR> Mekaneck, I fixed it :)
[16:20] <RougeR> turned out i was using the opensource nouveau driver
[16:20] <RougeR> silly billy
[16:26] <bewees> I'm mistaken, seems like the source package from `apt-get source ...` doesn't have the same layout, better to use the tarball and see it all in rules
[16:27] <RougeR> im guna upgrade to 21.04 as well Mekaneck
[16:27] <RougeR> didnt realis it was EOS
[16:27] <Mekaneck> It will go EOL 22nd of July
[16:28] <Mekaneck> good you got it solved :)
[16:28] <RougeR> Ah okay, well i may as well upgrade now and deal with any potential issues
[16:28] <RougeR> Thanks, appreciated you replying even though you didnt have a fix
[16:29] <Mekaneck> you're welcome :)
[16:29] <RougeR> tbh i normnally just stick on the LTS release, but i was having issues with some drivers and was at my wits end to fix it
[16:29] <RougeR> When i finally get a non-realtek NIC then i might go back to 20.04...idk. What are the edge ubuntu releases like these days for stability?
[16:30] <RougeR> I pretty much need my pc to just work (use it for work)
[16:31] <tomreyn> then you should run an LTS release
[16:32] <Mekaneck> Interim releases can be as stable imho as a lts release, only they are supported for 9 months
[16:32] <RougeR> I agree, but yeah 20.04 was broken for me so i tried upgrading to fix it...and it worked
[16:32] <tomreyn> if the GA kernel doesn't work with your hardware, the HWE/LTSE one may, and if this also doesn't work for some reason there's still the OEM
[16:32] <Mekaneck> LTS doesn't mean Long Term Stability after all but Long Term Support
[16:32] <RougeR> Mekaneck, aye yeah i figured the Interim release might not be to bad
[16:33] <RougeR> tomreyn, im not sure what happened tbh...its a driver a lot of people have issues with and i think i updated something or something auto-updated
[16:33] <RougeR> I ended up with up with my network card not being picked up at all
[16:33] <tomreyn> (for the HWE kernel, there's also an -edge variant, which can be even newer, if that's really needed - usually only on brand new hardware)
[16:34] <RougeR> i still get occasional network drops even with a new NIC (still reatelk...all i could get locally short notice)
[16:35] <RougeR> I know its the driver/os not the card or my connections as its always rock solid under windows or on my laptop with ubuntu 20.04
[16:35] <RougeR> just going to do some research and find another well support PCI NIC
[16:35] <RougeR> upgrading now might drop off
[16:37] <tomreyn> if you'd like to get a second / third / ... opinion on whether you could likely get your previously problematic hardware to work on 20.04 LTS, post    lspci -knnv | nc termbin.com 9999     and   lsusb | nc termbin.com 9999   and    dmesg | nc termbin.com 9999
[16:37] <bewees> Where do I add --enable-virglrenderer in this debian/rules file? I guess somewhere inbetween here? https://dpaste.org/2jRT#L97,98,99,100,101,102,103
[16:45] <RougeR> tomreyn, you are welcome to look, but from what ive seen...a lot of the realtek cards are just more  hassle than worth
[16:46] <RougeR> Even after fixing the broken/mismatch driver-kernel and installing a pci-e card (still realtek based)....i still get drop outs
[16:46] <RougeR> https://termbin.com/dnho
[16:46] <RougeR> https://termbin.com/jr3l
[16:46] <RougeR> https://termbin.com/nt27w
[16:50] <RougeR> r8169 driver is infamous :s
[16:50] <RougeR> https://www.google.com/search?q=r8169+disconnects&oq=r8169+disconnects&aqs=chrome..69i57j33i160.3617j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8
[16:57] <tomreyn> RougeR: looking at your third paste, you're having a kernel oops during boot even on this newer kernel. you should probably make sure you have the latest bios. which might also help with getting more hardware working well.
[16:58] <RougeR> tomreyn, what line/paste is that
[16:58] <tomreyn> the kernel oops seems to be about the buggy rdrand
[16:58] <RougeR> tomreyn, fair point on the bios that might be something useful to check
[16:58] <RougeR> I hate this motherboard with a passion, but it was the only affordable option at the time
[16:58] <RougeR> had  to flash the bios for ryzen 5 when i got it
[16:58] <tomreyn> https://termbin.com/nt27w and look for ------------[ cut here ]------------
[16:59] <tomreyn> MS-7B89/B450M MORTAR (MS-7B89), BIOS 1.90 07/23/2019   is whaty ou have
[16:59] <RougeR> yeah
[16:59] <RougeR> let me see if there are any new bios versions
[17:00] <RougeR> tomreyn, ah yeah i started seeing a few issues recently r.e funky outputs
[17:00] <RougeR> not quite sure what it is
[17:02] <RougeR> https://www.phoronix.com/scan.php?page=news_item&px=Linux-RdRand-Sanity-Check
[17:02] <RougeR> https://arstechnica.com/gadgets/2019/10/how-a-months-old-amd-microcode-bug-destroyed-my-weekend/
[17:03] <tomreyn> it's a well known bug, you want the latest bios.
[17:03] <tomreyn> (+ microcode, too, but you should get that automatically on ubuntu)
[17:03] <RougeR> yeah it seems so, thanks for pointing it out to me. Was not something that i was aware of
[17:04] <RougeR> On the bright side, my motherboard does have a built bios flash util
[17:04] <RougeR> https://www.msi.com/Motherboard/support/b450m-mortar
[17:05] <tomreyn> https://www.msi.com/Motherboard/support/B450M-MORTAR#down-bios are the latest bios versions, you can choose between stable and beta. the beta has a newer video bios, amongst other.
[17:05] <tomreyn> i assume your 1.90 is what they call 7B89v19 on that page
[17:06] <tomreyn> bbl, good luck.
[17:06] <RougeR> no worries, and yeah i think so
[17:06] <RougeR> catchya in a bit
[17:06] <RougeR> looking into the bios update now
[17:07] <RougeR> might put it off till next week...got work in the mornign and need this machine
[17:08] <RougeR> flashing the bios on a sunday afternoon before work on monday morning aint one i feel like tackling this week
[17:08] <RougeR> I say this...but im here upgrading the OS, sticking in a new ZFS pool...and migrating ubuntu to a new SSD with a root partition resize
[17:09] <RougeR> oh and just threw in a new GPU and got that working lol
[17:18] <alkisg> RougeR: it's not very possible, but it doesn't hurt to say it: I had bad networking with realtek. Then I switched to intel and networking was fine, BUT it was connecting with 100 instead of 1000 mbps.
[17:18] <alkisg> At that point I realized that the problem was a bad connection in the UTP cable. After fixing it, both intel and realtek were fine and the connection was always gigabit
[17:20] <RougeR> alkisg, yeah i guess its possible that something weird is going on with the cat5 cable....got a box full of them guess it  doesnt hurt to switch it out
[17:20] <RougeR> it seems highly unlikely that windows would not have issues though and ubuntu would if that were the issue
[17:21] <RougeR> its a fair point though
[17:22] <alkisg> I think realtek drivers in windows are better than realtek drivers in linux, so I wouldn't consider that part impossible (to work in windows, maybe even in 100 mbps or maybe with retransmissions, and to fail in linux)
[17:23] <alkisg> Other than that single case, I haven't had any issues with wired realtek in thousands of installations. With wifi realtek, sure, a lot :D
[17:25] <RougeR> alkisg, yeah i agree i wouldnt consider it impossible either
[17:25] <RougeR> it makes logical sense although it is probably unlikely
[17:25] <RougeR> i have had issues with two different although albeit both realtek nics
[17:25] <RougeR> the 2nd  one has solid linux reviews mind
[17:26] <RougeR> the issue is...its super hard to diagnose if the bug is fixed
[17:26] <RougeR> because i might disconnect twice a day or once a week...
[17:26] <RougeR> side note...im installing  21.04 now
[17:27] <RougeR> been stuck  on "installed libdebconfclient0 (amd64)" for ages
[17:37] <RougeR> tomreyn, (or anyone else)
[17:37] <RougeR> How do i get the log output during a system upgrade?
[17:37] <RougeR> oh nvm
[17:37] <RougeR> ffs
[17:38] <RougeR> ffs, the installer silently popped up a "do you want to change x box"
[18:17] <RougeR> fekin r8168-dkms is the bane of my life
[18:17] <RougeR> upgrade to 21.04 threw error from it
[18:18] <RougeR> and sudo apt-get clean throws an error on it
[18:27] <RougeR> hmm purged r8168, r8169 should be the working driver
[18:27] <RougeR> f it
[18:28] <RougeR> guna reboot, getting no errors now and upgrade seems complete from lsb_release and apt-get dist-upgrade
[18:34] <RougeR> success?
[18:34] <RougeR> i think
[19:24] <Surkow|laptop> Good evening. My power supply recently died from my dell xps m1330 laptop. After getting a new power supply the cpu was stuck at 800mhz for a while because the bios didn't detect a security pin in the new power supply. A new power supply with the security pin resolved this. The last few days I noticed the ondemand cpu governor kept getting stuck at 800mhz, while the processor can get to 2.5ghz.
[19:24] <Surkow|laptop> Repeatedly setting the governor to performance and then back to ondemand sometimes appears to help getting it "unstuck" from 800mhz. Changing "/sys/devices/system/cpu/cpufreq/ondemand/up_threshold
[19:24] <Surkow|laptop> " from 95 to 75 also appeared to work...for a while. It makes the system a bit faster to respond. The problem right now is that it hangs with normal usage in even the browser with a low clock rate. cpupower frequency-info gives me:  hardware limits: 800 MHz - 2.50 GHz, current policy: frequency should be within 800 MHz and 800 MHz. Shouldn't that say "within 800 MHz and 2.50 Ghz" or is this simply how the ondemand governor work
[19:24] <Surkow|laptop> s?
[19:31] <tomreyn> Surkow|laptop: i'd expect it to say "within [some higher value than 800Mhz] and 2.50 Ghz". i think you still have a firmware or hardware issue there.
[19:32] <Surkow|laptop> my hardware issue is that I'll need to repaste the cpu ;)
[19:32] <Surkow|laptop> it gets quite hot
[19:32] <Surkow|laptop> and endured a bunch of thermal shutdowns already
[19:32] <tomreyn> "stuck at 800 MHz" seems to be a rather common search term for this dell model
[19:32] <Surkow|laptop> 800mhz has kept it nice and cool
[19:32] <Surkow|laptop> but recent chrome updates (and even firefox) make it unbearable
[19:33] <Surkow|laptop> it's like they rely on some kind of rendering pipeline that pegs the cpu all the time
[19:33] <Surkow|laptop> Yeah, I have found numerous topics where people suggest altering grub flags to disable the bios interfering with the frequency
[19:34] <Surkow|laptop> but now that the security pin is present in the power supply I suppose the bios doesn't trigger anything anymore
[19:34] <tomreyn> when you have thermal shutdowns happening that also means something is wrong in hardware (or firmware). concentrate on this. if you know it's the need to apply new thermal paste, do it.
[19:34] <Surkow|laptop> It's an old laptop with bad cooling
[19:35] <Surkow|laptop> the core problem is that even after repasting the cpu the problem will persist
[19:35] <Surkow|laptop> figured I'd throw it in the ubuntu channel to see if there was anyone knowledgeable about cpu scaling
[19:36] <Surkow|laptop> I apparently don't understand enough about why the cpu keeps getting throttled and why the frequency takes so long to change.
[19:38] <tomreyn> oh this is indeed old. core 2 duo cpu.
[19:38] <Surkow|laptop> yep!
[19:38] <Surkow|laptop> 12 years old now :D
[19:38] <Surkow|laptop> core2duo t9300 cpu
[19:39] <Surkow|laptop> I even had to buy the intel gpu variant of the same laptop because the nvidia gpu variant was guaranteed to kill your motherboard within a year
[19:39] <tomreyn> well, ask in ##hardware for hardware questions.
[19:40] <Surkow|laptop> hmm
[19:40] <tomreyn> chances are the exhauster is jammed and paste is gone.
[19:41] <tomreyn> and then the cpu will be less powerful now than it used to be due to the need to fix some of the cpu security vulnerabilities
[19:41] <Surkow|laptop> true, I've already repasted its brother, an xps 13 with a more modern first generation i7
[19:42] <Surkow|laptop> so I'm aware where the hardware part of the problem lies
[19:42] <Surkow|laptop> I cleaned out the whole laptop from dust and debris already and I use an external fan to keep it cool
[19:42] <Surkow|laptop> I'll join the hardware channel just in case
[19:42] <tomreyn> 1st gen i7 is not more modern, it's less close to the dinosaurs
[19:42] <Surkow|laptop> :D
[19:43] <Surkow|laptop> I had the third generation model as well
[19:43] <Surkow|laptop> sent it back due to hardware issues
[19:43] <Surkow|laptop> the problem with these laptops is always power management
[19:48] <shibboleth> TJ-, been throwing several sinks out the window, no joy thus far
[19:57] <knaccc> hi all, i'm finding this question surprisingly hard to google: will a rotational hard drive be able to tell if there is a bad sector/other read error simply by reading that part of the disk?
[19:58] <knaccc> or will it just silently deliver bad data?
[19:58] <knaccc> i assume it can discover bad sectors during writes because it must attempt to read back what it has just written?
[19:59] <shibboleth> smartctl -a /dev/foo
[20:01] <knaccc> shibboleth that will tell me if the disk has reported bad sectors, but i'm wondering how the disk can tell in the first place whether there was a bad sector
[20:02] <knaccc> from what i've found so far, i think maybe it can only tell a bad sector immediately after an attempted write operation, but cannot just tell from reading a sector written a long time ago
[20:02] <tomreyn> knaccc: if you were looking to have a scientific discussion or examination on the topic, this is probably not the place. there is #hardware, but i would not say it matches the scientific part either.
[20:03] <tomreyn> fisk firmwares are closed source, so for the very most part we don't actually know how they work or make decisions.
[20:03] <tomreyn> *disk
[20:04] <knaccc> tomreyn the reason i'm asking is that i'm wondering if i can tell if a raid 1 mdadm can actually tell if there is bit rot just by reading the entire contents of both rives
[20:04] <knaccc> so i'm just wondering if anyone knows in general whether drives have any ability to know when there is bit rot
[20:05] <knaccc> raid 1 was a bit of a red herring, i shouldn't have mentioned that
[20:07] <knaccc> the point is, if i have raid 1, and each of the pair of drives returns different data, how is mdadm supposed to know which is the bit rot and which is the good data?
[20:08] <knaccc> i apologize if this is was off topic
[20:08] <jmuriel> hello! curious if anyone knows why stterm gives weird input (like ^E) when scrolling the mousewheel at the shell. (it doesn't do this on other distros)
[20:17] <tomreyn> knaccc: mdadm won't know if there's no extra data to tell what should be in that block (such as with different raid levels and file system checksumming). a file system error will occur, and this will need to be solved.
[20:19] <knaccc> tomreyn thanks, yeah i guess this is quite a low-level question and i should expect this to differ between drive manufacturers regarding error detection
[21:23] <alumno> hola
[21:23] <alumno> hay alquin
[21:31] <Surkow|laptop> tomreyn, I had to disable the cpu sleep states. http://manpages.ubuntu.com/manpages/trusty/man1/cpupower-idle-set.1.html
[21:31] <Surkow|laptop> works properly without overheating now
[22:08] <Flac> hell
[22:08] <Flac> hello
[22:12] <gordonjcp> Flac: hi
[22:13] <Flac> how are you
[22:19] <Flac> https://imgur.com/E1gZvJL
[22:20] <Flac> install vmware
[22:21] <Flac> then when i opened it gave an error
[22:21] <Flac> I couldn't find a solution
[22:22] <Flac> https://imgur.com/E1gZvJL
[23:04] <tomreyn> Flac: sudo apt update && sudo apt install linux-headers-oem-20.04
[23:05] <tomreyn> Flac: i'm not sure whether vmware will support this kernel, though, but that's something to check with them.
[23:53] <Flac> tomreyn, thanks but already installed (linux-headers-oem-20.04)
[23:54] <Flac> not solved