[01:44] * tomreyn admires TJ-'s patience [02:50] good morning to all === not_phunyguy is now known as phunyguy [06:20] Good morning [08:21] !info kismet bionic [08:21] kismet (source: kismet): wireless sniffer and monitor - core. In component universe, is optional. Version 2016.07.R1-1.1~build1 (bionic), package size 1203 kB, installed size 4833 kB [10:51] Hi folks [14:21] Heya!!!! A cola demon! [14:23] WARNING! WARNING! This a cola free zone!!! [14:27] systemctrl status colad.service [14:27] lol [14:40] >:) [14:41] BluesKaj!!!! Hello!!!! [14:41] >:) [14:42] hi marcoagpinto [14:43] morning folks [14:43] 'Morning hggdh [14:43] hey hggdh [14:44] hey hggdh [15:07] "of Fire and Light" [15:07] :) [15:07] good metal [16:29] https://fedorapeople.org/~jwrdegoede/flickerfree-videos/workstation-bgrt-logo.webm [16:29] flickerfree on 19.10 to come [16:30] fedora ... you? [16:30] no, its linked from omgubuntu [16:31] News from omgubuntu: Ubuntu 19.10 Will Offer a Flicker Free Boot (For Some Users, Anyway) [16:36] While that's cool, it's way down my priority list... [17:03] Buaaaaaaaaaa... I need to reboot... my PhD software fragmented all the RAM :( [17:05] fragmented your RAM? [17:05] lol [17:05] pacman did it [17:14] o0 [17:24] back! [17:24] >:) [17:25] the tool is so heavy on system resources :((((( [17:25] 4 GB is too little for it [18:42] it must have been a boot sector virus! [18:42] on drive a: [18:52] tomreyn: ???? [18:56] i'm joking about old computer issues. [18:57] ahhhh [18:57] because A: and B: are floppy drives [18:57] :) [18:57] yes, and for the most part, boot sector viruses, are a thing of the past, too. [18:57] yes [18:57] at least currently. [19:02] https://serverfault.com/questions/133305/linux-memory-fragmentation [19:02] you're probably not using huge pages with 4 GB of total physical memory [19:10] tomreyn: It is Windows 10 not Ubuntu [19:10] :) [19:11] and I store most of the data in multidimensional arrays that eat all RAM [19:11] the software no longer works in 32-bit, but only in 64 [19:12] although I have removed a field from some of the arrays [19:12] :) [19:12] but they are still huge [19:12] then, they are also structured, for example: [19:13] field(1,5000,5000)\time [19:13] :) [19:14] anyway, I found a way of reducing RAM usage by removing a background image and replace it with a smaller picture, but the design guy made the GUI for free, so I can't ask much from him [19:14] it is my PhD afterall [20:18] marcoagpinto, reduce your screen resolution and reduce RAM use even more :-) [20:27] JimBuntu: What?! The software was suppose to use at least 1080p [20:27] :) [20:27] but I only have 1366x768 [20:27] so, part of the options are semi-cut in the window [21:55] hehe, TJ- is dealing with the same level of expertise in #ubuntu as i have been for the past 3 hours in #kubuntu [21:55] * tomreyn ran out of patience again [21:55] tomreyn: heh, you're both machines :) [21:56] machines would just do it, i want to shout right now [21:57] hm, maybe the computers scream back at us, but at 2ghz rather than 2khz where we could hear it.. [21:58] they just randomly draw more power to pay it back to us [21:59] hehe [21:59] and transfer out unique ad id and browser fingerprint over 2khz to our android phones, right [22:00] oh is *that* how that works.. [22:00] It all goes along with the implant in your brain [22:01] Have you noticed you can make 'smart' phones sulk if you cut off their network facilities, and refuse to allow 'fine' GPS service? [22:01] TJ-: figure out the grub issue from earlier today? [22:02] jeremy31: remind me which one! :D [22:02] oh... yeah... sheesh, so many things being juggled I'd entirely forgotten about that, seems like months ago [22:02] TJ-: I think is was USB and trying to use Legacy and EFI boot [22:03] there was someone claiming it was this way sounds transferred to android) on some security mailing list some 2 or so years ago. maybe this was around the badbios revelations, i don't rmemeber. [22:03] sarnold: ^ [22:03] jeremy31: grub-efi-amd64 Conflict/Replaces grub-pc but grub-efi-amd64-signed ... doesn't [22:03] I've heard about some ultrasonic advertising identifiers before.. [22:03] yes thats what i read, too [22:04] When your dogs start insisting on buying tat from Amazon you know there's ultrasonic ads! [22:04] but there didn't seem to be any hard evidence then [22:04] TJ-: Not sure what grub efi I have installed but the drive still works in Legacy and EFI mode [22:04] hehe tj [22:05] jeremy31: it works, but it annoyed me the -signed (which does the same thing as the unsigned) gets to co-install with grub-pc but unsigned doesn't [22:05] jeremy31: oh! you've made me realise I forgot something vital! I didn't check grubx64.efi was copied to the removable media boot path - doh! [22:06] TJ-: did a dpkg -l | grep grub and I see no sign of grub efi [22:06] jeremy31: grub-efi-amd64{,-signed} are the 2 required for UEFI boot [22:07] TJ-: It was installed first(grub-efi-amd64) and I added the bios_grub partition later [22:09] the installer only uses grub-efi-amd64 which is useless for 18.04 FDE (won't work) so I needed to replace the boot-loader with the locally built one, but that requires using "grub-install --no-uefi-secure-boot ..." [22:10] oops, s/only uses grub-efi-amd64-signed/ [22:12] I didn't try with FDE, I just was trying to get a SSD with a Linux install to work with an older laptop [22:16] interesting, booting the same installed USB device in a VM, it is blazing fast as an IDE disk but quite slothful as a virtio disk [22:16] also IDE is UEFI boot, VirtIO is BIOS but that shouldn't make a difference