[01:40] <johnjbogle> tomreyn: hi, I now have a bootable usb with ubuntu 19.04 on it. I still have to download/update my bios, and apparently a dell driver pack. I'm not sure though what precisely and in what order I'm supposed to do, now that I have created a bootable ubuntu usb..? -thx 
[01:41] <lotuspsychje> johnjbogle: this channel is support for 19.10 actually
[01:41] <lotuspsychje> johnjbogle: if you like support for 19.04 join #ubuntu please
[01:42] <johnjbogle> ah ok sorry thanks
[04:12] <dax> Release Candidate (and testable!) Eoan Ermine builds ready to test - https://lists.ubuntu.com/archives/ubuntu-release/2019-October/004840.html
[04:13] <lotuspsychje> tnx for sharing dax
[10:49] <CarlenWhite> Against my better judgement, I've upgraded to Eoan Ermine on a computer I daily. And I've came across a nasty issue that causes a full-ish lockup precluded by intensifying graphical errors.
[10:52] <CarlenWhite> I can cause it to happen by quickly resizing Terminal which cause benign, brief black boxes to full on abstract art with Firefox if I open something moderately graphically intensive suchas YouTube.
[10:54] <CarlenWhite> After the site finishes loading, it sorts itself. But it's kinda a coin flip if the abstract art of pixels freezes the laptop. It doesn't feel like a complete lockup because the mouse can still be moved but there might be a reason behind this.
[10:56] <CarlenWhite> Is there a particular location on LaunchPad if there's no exact cause of the issue? I kinda want to pin it on amdgpu since this is what my laptop uses as a GPU and it's a graphical malfunction but it could be entirely something else.
[11:07] <tomreyn> CarlenWhite: that's a good visual description, and you mentioned amdgpu as well, but we'll need some more details: you say you upgraded - how did you do it, coming from which ubuntu releasE? are you using the default gnome-shell desktop or something else? which graphics card is this exactly? are you using default amdgpu (or radeon) drivers from ubuntu or the proprietary -pro overlay from AMD? how much ram does this system have installed?
[11:09] <tomreyn> also: if gnome-shell, does it still happen when you disable all of your gnome-shell-extensions? are you using Xorg or Wayland?
[11:11] <CarlenWhite> Upgraded using `do-release-upgrade -d` from 19.04, Disco Dingo. Using gnome-shell. AMD Radeon RX Vega 8 96 is used inside this Lenovo ThinkPad E585. Should be amdgpu since I had to nearly uninstall the system due to a botched install of AMD's official. 16GB of RAM.
[11:12] <CarlenWhite> I have a few extensions installed as a matter-of-fact but mostly something adding onto the upper-most bar. I'll check.
[11:14] <CarlenWhite> Yeah nothing that should be doing anything invasive. They're disabled now. I'm gonna finish a response to something and intentionally try making it happen.
[11:16] <tomreyn> to replace gnome-shell by a fresh copy: alt-f2, type 'r', press enter
[11:16] <tomreyn> works only on X, not wayland
[11:17] <tomreyn> also keep an eye on    journalctl -f
[11:18] <tomreyn> when # of gnome-shell-extension traces / minute reduces you're on the right track ;)
[11:20] <CarlenWhite> Of course when I want it to crash it doesn't want to.
[11:21] <tomreyn> fixed!
[11:21] <CarlenWhite> I'm getting some lovely brief glimpses of abstract art but no system lockup.
[11:22] <tomreyn> that's bad enough i'd say. can you do this with a freshly started gnome-shell on X, too?
[11:23] <TJ-> usually those kind of issues are due to the GPU rendering textures where it shouldn't. Sometimes it can be due to pressure on VRAM, but mostly it's a driver issue (possibly at the userspace (Xorg) layer, not kernel)
[11:25] <CarlenWhite> TJ-, Yeah the glitchiness does has that kinda 'We're pulling stuff directly from some random memory and you're gonna look at it for a moment'
[11:25] <CarlenWhite> Like there's a inarticulate pattern in it.
[11:26] <TJ-> CarlenWhite: does it affect a brand new user account as well?
[11:28] <CarlenWhite> TJ-, I haven't tested exhaustively. tomreyn, I assume logout-login?
[11:28] <TJ-> CarlenWhite: the reason I ask is it could be related to existing user's cached parts
[11:29] <CarlenWhite> I could give that a try in a few moments. Responding to something so I'll do it.
[11:29] <tomreyn> CarlenWhite: trying with a new user account seems like a good idea to me as well, and it's quite easy to do.
[11:33] <CarlenWhite> Logging out and--...forgot the user's account.
[11:34] <CarlenWhite> Now let's do it.
[11:34] <tomreyn> you can switch to a tty and create the other user account there
[11:35] <tomreyn> also loginctl terminate-user yourmainuseraccount
[11:40] <CarlenWhite> Seems like the effect isn't dependant on user.
[11:44] <TJ-> Good, that rules out a lot of possibilities
[11:46] <CarlenWhite> Okay, weird. The effect is attached to the window.
[11:46] <TJ-> makes sense
[11:47] <CarlenWhite> As in if I go to switch windows, I can see it's preview with the glitch still there. Return back to it and it'll return.
[11:48] <CarlenWhite> Yeah was even able to grab a screenshot of said effect too.
[11:49] <CarlenWhite> https://imgur.com/30w8imI
[11:50] <TJ-> Look for clues in $HOME/.xsession-errors and in $HOME/.local/share/xorg/
[11:50] <TJ-> Does switching away to a console TTY and back clear it?
[11:52] <lotuspsychje> those glitches look like my old amd x800 bug
[11:52] <TJ-> lotuspsychje: what was the cause?
[11:53] <CarlenWhite> TJ-, No errors. The logs show nothing of interest aside from it enumerating the devices it found and properties.
[11:53] <lotuspsychje> TJ-: it was across several ubuntu releases, i was never able to catch the real reason
[11:53] <TJ-> It *looks* like a compositor issue but I guess with Gnome that cannot be disabled?
[11:53] <CarlenWhite> Also the effect isn't localized on Firefox. Remmina shows this effect too.
[11:54] <CarlenWhite> https://imgur.com/DXeNg8k
[11:55] <lotuspsychje> TJ-: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1513801
[11:57] <TJ-> CarlenWhite: is it kernel v5.3 ?
[11:57] <CarlenWhite> `uname -r` => `5.3.0-18-generic`
[11:58] <CarlenWhite> I don't know how or why I remembered that command. I just knew.
[11:59] <tomreyn> in the end it's maybe just some missing firmware? shall we look at your    journalctl -b | nc termbin.com 9999   ?
[12:02] <CarlenWhite> Sure. Running a find-replace to omit my username since it's my real.
[12:02] <tomreyn> there can also be serial numbers i there if it matters
[12:03] <CarlenWhite> What's the gain of something like that?
[12:04] <tomreyn> something like what?
[12:04] <CarlenWhite> Nevermind. https://termbin.com/61sa
[12:04] <tomreyn> nouveau.modeset=0 ? do you also have an nvidia gpu in there?
[12:06] <lotuspsychje> CarlenWhite: on lenovo's its also a good idea to check if bios/firmware is up to date to latest
[12:06] <CarlenWhite> tomreyn, I hope not.
[12:07] <CarlenWhite> lotuspsychje, Yeah it's been probably way too long since the last BIOS update since I never gotten around to figuring out how that works in linux. I'm familar with it in Windows
[12:07] <CarlenWhite> Erp
[12:08] <lotuspsychje> CarlenWhite: you might want to look in software center, some lenovo models can firmware upgarde from there
[12:09] <tomreyn> or download and boot off the iso https://pcsupport.lenovo.com/de/en/products/laptops-and-netbooks/thinkpad-edge-laptops/thinkpad-e585-type-20kv/20kv/20kvcto1ww/downloads/DS503790
[12:11] <CarlenWhite> Wished I had a spare flash-drive sitting around.
[12:11] <tomreyn> maybe with the updated bios you'll also be able to drop the ivrs_ioapic and spec_store_bypass_disable kernel parameters which you probably added because of this? https://forums.lenovo.com/t5/Other-Linux-Discussions/ThinkPad-E485-E585-Firmware-bug-ACPI-IVRS-table/td-p/4191484
[12:12] <CarlenWhite> Hopefully.
[12:12] <TJ-> There's a bunch of unhandled IRQs there
[12:13] <tomreyn> i recommend to always have a separate storage with ubuntu installer / live image for the ubuntu release you're running around you.
[12:15] <CarlenWhite> tomreyn, You can say I like to live dangerous. But I have a multi-boot USB with a copy of Ubuntu. It's probably one or two versions behind but still useful. If all fails I have Windows 10 EDU occupying the SSD in the extra space in my laptop if I need something now.
[12:15] <TJ-> there's also a few " amdgpu 0000:05:00.0: remove_conflicting_pci_framebuffers"
[12:15] <TJ-> CarlenWhite: I'd recommend trying the acpi_osi= workaround in case it configures the system better
[12:16] <lotuspsychje> and some gnome-shell weirdy errors too
[12:16]  * CarlenWhite makes a shopping list of stuff to do.
[12:16] <TJ-> "conflicting framebuffers" sounds VERY close to the issue being seen 
[12:17] <CarlenWhite> tomreyn, To answer you question, Yes. ivrs_ioapic and spec_store_bypass_disable was used to get my system to start.
[12:17] <CarlenWhite> It was a painful hour trying to figure that out.
[12:21] <CarlenWhite> TJ-, That does kinda sound like what might be causing the issues. I can kinda imagine how problematic this is in a high-level sense.
[12:22] <lotuspsychje> CarlenWhite: what i also would advice is to compare this with a daily image live, see if you can reproduce this same way like your upgraded system
[12:22] <tomreyn> did we all spot this kernel trace? WARNING: CPU: 2 PID: 252 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1452 dcn_bw_update_from_pplib.cold+0x7f/0xa8 [amdgpu]
[12:23] <lotuspsychje> yeah tomreyn doesnt look healthy neither
[12:23] <CarlenWhite> lotuspsychje, Something for another day. I still need to get around to making a trip to WalMart to get a garbage stick for diagnostics.
[12:24] <lotuspsychje> oh, you dont have an usb handy?
[12:24] <CarlenWhite> tomreyn, Uh, I can't extract information from that message.
[12:24] <CarlenWhite> lotuspsychje, Correction, a USB I'm willing to wipe and load at the moment.
[12:26] <CarlenWhite> I could dd this current one just for the sake of not having to fuss trying to get it bootable again.
[12:29] <tomreyn> CarlenWhite: something about the "amdgpu" graphics drivers' "display core next" calculations has failed, based on the file name, but that's all i can tell from it as well. it's something you can searc the web for, though
[12:30] <tomreyn> there's also a good chance that handling the other issues will make this go away.
[12:30] <TJ-> https://bugzilla.kernel.org/show_bug.cgi?id=201285 
[12:31] <tomreyn> CarlenWhite: did you say you have a bootable windows system? then i guess i'd just use this to upgrade the bios first of all, then come back
[12:33] <CarlenWhite> Spooling it up in a VM to get the software ready.
[12:33] <TJ-> Also  https://bugs.freedesktop.org/show_bug.cgi?id=107296
[12:33]  * tomreyn bbl
[12:34] <CarlenWhite> Or...I guess I have to resign some drivers.
[12:47] <CarlenWhite> Nevermind. Vbox cannot compile it's own drivers for some reason.
[12:48] <CarlenWhite> Well off to Windows for a brief moment to update firmware.
[13:01] <tomreyn> virtualbox needs some additional patches (or their latest tesbuild) to accomodate for linux 5.3 
[13:02] <tomreyn> *tesTbuild
[13:03] <tomreyn> next vbox upstream builds should be released in two days, 15 October 2019, and support it.
[13:05] <CarlenWhite> Neato
[13:06] <CarlenWhite> Also updated my BIOS. Still need the ivrs_ioapic or my laptop will literally halt and catch fire.
[13:06] <CarlenWhite> Because the fan doesn't kick in at the speed it should run while in GRUB.
[13:07] <tomreyn> these parameters don't change how grub runs
[13:08] <tomreyn> they are passed to the linux kernel which is actually started by grub.
[13:09] <tomreyn> the acpi_osi= workaround discussed at the http://iam.tj/prototype/enhancements/Windows-acpi_osi.html may enable you to drop it.
[13:12] <tomreyn> on the other hand, ivrs_ioapic is, according to the documentation at https://www.kernel.org/doc/html/v5.3/admin-guide/kernel-parameters.html (search for "ivrs_ioapic") rather specific, so there should not be too many side effects, i assume.
[13:13] <tomreyn> TJ may know better
[13:13] <tomreyn> CarlenWhite: would you like to post another log?
[13:16] <CarlenWhite> In a moment, yeh.
[13:17] <CarlenWhite> Just updating the grub removing spec_store_bypass_disable since it's no longer required to start the system.
[13:17] <tomreyn> you should install package tpm2-tools which may then enable you to do firmware updates from ubuntu in the future, too.
[13:20] <CarlenWhite> Oh yeah I was going to mention. The firmware mentioned capsules and I recall this being somewhat doable in Linux.
[13:21] <tomreyn> UEFI capsules, a way for staging UEFI binaries to be executed on next power cycle, i think
[13:29] <tomreyn> hmm thinkpad E series don't seem to be supported yet https://fwupd.org/lvfs/search?value=Thinkpad
[13:29] <tomreyn> this is bios update mechanism integrated into ubuntu / the gnome-software GUI
[13:30]  * tomreyn bbl again
[13:40] <CarlenWhite> I really want to be able to use my yubikey if I just want to prevent cramping my hands after typing my password the hundredth time today.
[14:06] <lotuspsychje> CarlenWhite: any progress?
[14:29] <jeremy31> johnjbogle: can you do  a paste for   rfkill list
[14:31] <johnjbogle> jeremy31: ok
[14:32] <johnjbogle> I will post my discussion here first from the other thread, and then I'll paste the rfkill list. Is that ok?
[14:32] <lotuspsychje> just do the rfkill johnjbogle 
[14:33] <lotuspsychje> volunteers have readed your earlier post now
[14:33] <jeremy31> johnjbogle: you have a supported wifi device, the results from the other paste show it is disabled
[14:33] <johnjbogle> ok
[14:33] <ioria> johnjbogle, and check in lsmod if dell-laptop  module is loaded 
[14:42] <johnjbogle> https://pastebin.ubuntu.com/p/cQqDdNfDwN/
[14:42] <tomreyn> johnjbogle: please also post this:   cat /proc/mtrr | nc termbin.com 9999
[14:44] <tomreyn> johnjbogle: in case you'Re still juggling computers now it may be easier for you to install an openssh server on the computer and then use ssh to connect to it, or to use webchat.freenode.net on said computer to be able to copy + paste more easily.
[14:44] <johnjbogle> ioria: not sure if this is what you needed? https://pastebin.ubuntu.com/p/6QtrJK6Br8/
[14:45] <johnjbogle> tomreyn: lol 
[14:45] <ioria> johnjbogle, yes, you probably need to blacklist it  (echo "blacklist dell-laptop" | sudo tee -a /etc/modprobe.d/blacklist-dell.conf   and reboot)
[14:45] <tomreyn> jeremy31: do you know why there is both a phy0 and a dell-wifi device listed in the rfkill output? this puzzled me the other day.
[14:46] <jeremy31> tomreyn: Likely added by a dell module, ideapad-laptop does it also
[14:47] <johnjbogle> https://termbin.com/nh803
[14:47] <tomreyn> i see
[14:48] <tomreyn> johnjbogle: thanks. what about the bios upgrade, did you consider and discard the idea?
[14:49] <johnjbogle> just havent figured it out yet. Was able to figure out how to create a bootable usb stick so far, but thats all I got to. Sorry guys, major novice here :-/ 
[14:50] <lotuspsychje> johnjbogle: why did you linux guru buddy made you upgrade to 19.10 exactly?
[14:50] <johnjbogle> I will try the blacklist command now
[14:51] <johnjbogle> lotuspsychje: good question...I'll ask him 
[14:53] <johnjbogle> "to try to sort out the g**d**n mo*******ing wifi and audio jack issue"
[14:53] <TJ-> ahhh, the SHOTGUN approach
[14:53]  * TJ- prefers snipers
[14:53] <lotuspsychje> hehe
[14:54] <tomreyn> if you'll stay on this bios version (i would not recommend it) you should add these kernel parameters in /etc/default/grub: mtrr_gran_size=256M mtrr_chunk_size=256M
[14:54] <johnjbogle> "that's the only reason, because something f***ed it up, so, i figure doing a fresh upgrade to the new release would reset that s**t"
[14:54] <tomreyn> that's based on https://termbin.com/oscu and https://termbin.com/nh803 and my interpretation of http://my-fuzzy-logic.de/blog/index.php?/archives/41-Solving-linux-MTRR-problems.html
[14:54] <TJ-> johnjbogle: try this: "sudo modprobe -r dell-laptop" then try "rfkill list" once more... depending on which wifi device it is, we can then re-init it and (if that was the problem) wifi will work
[14:55] <lotuspsychje> johnjbogle: fresh upgrade to a devel version? did you figure that or your buddy? :p
[14:56] <johnjbogle> ok thanks so much for now guys n gals!!! I have to hop off now, wife needs her machine back to prep for her work day tommorow. Will try to pick this back up ASAP (maybe in a few hours). Many thanks
[14:57] <tomreyn> another thing where an ssh shell would help
[14:57] <TJ-> johnjbogle: it has Intel so you'd then do "sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" to reload it, then "rfkill list" and you MAY have wifi working
[14:57] <TJ-> The key is the "kernel: iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)" 
[16:49] <johnjbogle> tomreyn: thanks. I will try to upgrade my bios to A27 [currently A21], ASAP. Might be a couple/few days though? Hopefully sooner.
[16:49] <johnjbogle> TJ -: thanks. Done that now. https://pastebin.ubuntu.com/p/ksKv3SXshX/
[16:51] <johnjbogle> lotuspsychje: haa lol. Definately wasn't me that thought of that... I'm not that {smart|dumb}!! XD
[16:53] <lotuspsychje> johnjbogle: in most cases we highly advice to use developing versions with a clean install daily, to avoid messy upgrade bugs and give the developers unneeded work
[16:55] <johnjbogle> https://pastebin.ubuntu.com/p/MnyTgBRzn8/
[16:56] <johnjbogle> ok sounds like common sense. I'll pass on that message.
[16:56] <lotuspsychje> johnjbogle: wifi working after that command?
[16:58] <johnjbogle> Really doesn't seem to be, no.
[16:58] <johnjbogle> Nope. No way to connect with just wifi.
[16:58] <lotuspsychje> johnjbogle: does your laptop have a physical switch somewhere, or an Fn + F key combo to enable/disable?
[17:00] <johnjbogle> The physical switch on the side seems to be non-functional at this point. (It normally works, just not at all currently)
[17:00] <lotuspsychje> johnjbogle: was your wifi working on 19.04? or any other ubuntu version?
[17:01] <johnjbogle> fn+f didnt seem to do anything.
[17:01] <johnjbogle> Yes
[17:01] <lotuspsychje> johnjbogle: wich version?
[17:02] <johnjbogle> 18.04, 19.04
[17:03] <lotuspsychje> johnjbogle: but why did you update to 19.10 then? was it not to make wifi work?
[17:07] <lotuspsychje> johnjbogle: dpkg --list | grep linux-image     do you see multiple kernel versions there?
[17:12] <johnjbogle> apparently, yes. It was working fine before, but then my machine was dormant for almost 1or2 months while i was travelling. When I finally went to turn it on for the first time in a long time, it wouldn't turn on. Took it to a repair guy, he took it apart, tested it with some volt meters etc and magnifying goggles... said it was water damaged. (I was thinking how the heck did it get water damage, humidity maybe, but that's it). He put it back 
[17:12] <johnjbogle> together, tried it again, it wouldnt turn on. So about a week later, just of boredom/curiosity I pressed the power button, and THIS TIME for whatever weird reason, actually turned on, whereas before it wouldn't. The only thing though after I got it to turn on again, was I had to get someone to do/fix something with the bios or startup manager, I forget what though...possibly reset which was the startup/main harddrive...I'm not sure. Anyway, since 
[17:12] <johnjbogle> then, since turning it back on from after a month or 2 of travelling with it, the wifi and the audio jack have been glitchy. So (I think) that's why my friend told me to upgrade it to the latest ubuntu.
[17:13] <johnjbogle> yes I do see multiple kernal versions
[17:13] <lotuspsychje> johnjbogle: wich ones please
[17:15] <lotuspsychje> also upgrades wont fix humidity damage
[17:17] <johnjbogle> https://pastebin.ubuntu.com/p/v9mDT2jy4y/
[17:18] <lotuspsychje> johnjbogle: do you know howto boot a previous kernel with grub?
[17:19] <johnjbogle> Right, but would it have actually been humidity damage, since now the machine is working again (for the most part). Very odd that it wouldn't turn on for a while, but whatever ghost in cog it was seemed to have worked its way out.
[17:19] <johnjbogle> No, definately dont know that.
[17:20] <lotuspsychje> johnjbogle: reboot and HOLD shift at boot, to enter grub, then choose ubuntu recoverymode previous kernel and select a 4.18 kernel as a test
[17:23] <lotuspsychje> johnjbogle: you will see a screen like this: https://i.stack.imgur.com/Sv1aJ.jpg
[17:25] <johnjbogle> Ok tried holding shift at bootup, but the first time, it told me 
[17:26] <johnjbogle> No Bootable Devices Found
[17:26] <johnjbogle> and gave me 3 F# choices.
[17:26] <lotuspsychje> f choices?
[17:27] <johnjbogle> The 2nd and 3rd attempts both brought me to the normal username/password signin window, eventhough I was firmly holding shift.
[17:27] <lotuspsychje> johnjbogle: maybe try ESC then
[17:27] <johnjbogle> Like f1 for one thing, f5 for another, f9 for something else.
[17:27] <lotuspsychje> right
[17:28] <johnjbogle> Sorry dont remember what the options were.
[17:28] <johnjbogle> Hold esc?
[17:28] <lotuspsychje> yeah
[17:30] <johnjbogle> Well both attempts, first shift, then esc... both made the dell logo appear for like 10 times longer than it normally does... but then it just goes to the signin screen.
[17:31] <lotuspsychje> johnjbogle: you are holding shift? not pressing few times right?
[17:31] <johnjbogle> HOLDING firmly.
[17:36] <lotuspsychje> johnjbogle: normally any system should be able to enter grub, when ubuntu installed
[17:37] <lotuspsychje> johnjbogle: try holding shift, right after POST messages
[17:40] <johnjbogle> It just keeps loading into ubuntu
[17:40] <lotuspsychje> weird
[17:40] <lotuspsychje> johnjbogle: did you try that solution from ioria?
[17:41] <johnjbogle> Ahh thank-you for the reminder! I knew there was something I had forgetten to do
[17:47] <jeremy31> What model computer is this?
[17:48] <lotuspsychje> lemme get you his dmesg jeremy31 
[17:48] <johnjbogle> Entered the blacklist code, restarted, tested wifi [nothing], rebooted, held down shift from when I pressed the power button, still loaded into ubuntu login screen.
[17:48] <johnjbogle> Dell Latitude E7440.
[17:49] <lotuspsychje> jeremy31: https://termbin.com/oscu
[17:49] <lotuspsychje> johnjbogle: do you dualboot or singleboot ubuntu?
[17:50] <johnjbogle> 97.9% sure its just singleboot
[17:50] <lotuspsychje> legacy or uefi boot?
[17:50] <johnjbogle> But I do have 2 internal ssd's
[17:50] <johnjbogle> hmmm....not sure
[17:51] <lotuspsychje> uefi booting can influence hardware
[17:51] <jeremy31> johnjbogle: Is there a switch next to the headphone port?
[17:51] <johnjbogle> Yes, but this whole fiasco has it not functioning either.
[17:52] <johnjbogle> In fact the audio jack isn't working right now too.
[17:52] <lotuspsychje> and johnjbogle claiming his wifi was working on 18.04 and/or 19.04
[17:53] <jeremy31> johnjbogle: If that switch doesn't make any difference in rfkill list results, you might have to try putting a piece of tape on one pin of the wifi card
[17:53] <johnjbogle> Yes, it was working for a while on both. But now, no.
[17:53] <ioria> johnjbogle, have you blacklisted the module i said  ?  lsmod | grep dell
[17:54] <johnjbogle> I typed this in as 1 command: echo "blacklist dell-laptop" | sudo tee -a /etc/modprobe.d/blacklist-dell.conf
[17:54] <johnjbogle> Then rebooted.
[17:54] <ioria> johnjbogle, you missed 'echo'
[17:54] <lotuspsychje> johnjbogle: check ioria last command again, to doublecheck plz
[17:54] <johnjbogle> I did type "echo"
[17:55] <ioria> johnjbogle, sorry, lsmod | grep dell
[17:55] <johnjbogle> ahh, ok
[17:56] <johnjbogle> https://pastebin.ubuntu.com/p/kjFgwZ6JpB/
[17:57] <jeremy31> johnjbogle: I see dell_rbtn is loaded, try the FN keyboard combo and see if rfkill changes
[17:58] <ioria> johnjbogle, that ^ and paste again  rfkill list
[17:58] <johnjbogle> Sorry, do what?
[17:58] <lotuspsychje> johnjbogle: Fn button + F key for wifi
[17:59] <johnjbogle> ok then... type rfkill list?
[18:00] <ioria> yes and paste it
[18:02] <johnjbogle> https://pastebin.ubuntu.com/p/G9QtQCPWjy/
[18:03] <johnjbogle> ^ after I pressed fn+f.
[18:04] <jeremy31> johnjbogle: Is there something in BIOS about disabling wifi with ethernet connected?
[18:06] <lotuspsychje> i recall some machines with 'last state' wifi options that had this kind of behaviour
[18:07] <lotuspsychje> might be a good idea to go check bios johnjbogle and look for you uefi/legacy and wifi/eth options
[18:07] <johnjbogle> I believe there are 2 or 3 settings about wiffi, but I already played in there yesterday with another expert and didn't find anything to be it. I can check again though, how do I get to bios?
[18:07] <lotuspsychje> F2 or DEL
[18:07] <johnjbogle> ok
[18:07] <lotuspsychje> check at your bootup
[18:08] <ioria> johnjbogle, can you  press  again  Fn + F2  and   rerun  ' rfkill list all ' ?
[18:08] <johnjbogle> already in the bootup menu
[18:08] <ioria> ok
[18:10] <johnjbogle> Boot Sequence: Ubuntu [checked]. UEFI: Hard Drive
[18:10] <johnjbogle> [checked]
[18:11] <johnjbogle> Boot list Option: UEFI [checked]. Legacy [unchecked].
[18:11] <lotuspsychje> try booting legacy as a test
[18:12] <johnjbogle> Advanced Boot Options: Enable Legacy Option ROMs [checked].
[18:13] <johnjbogle> trying
[18:14] <johnjbogle> Invalid partition table!_
[18:14] <lotuspsychje> right, back to uefi then
[18:15] <jeremy31> johnjbogle: is there a power management section in BIOS?
[18:16] <johnjbogle> yes
[18:16] <jeremy31> check for wireless radio control
[18:16] <johnjbogle> i see it
[18:17] <jeremy31> are the options selected?
[18:17] <johnjbogle> Control WLAN radio [unchecked]. Control WWAN radio [unchecked].
[18:18] <jeremy31> hmm, at this point I would suggest blacklisting dell_rbtn
[18:18] <ioria> johnjbogle, the switch is on, right ?
[18:20] <johnjbogle> the physical switch?
[18:20] <ioria> yeah
[18:20] <johnjbogle> yes its in the on position
[18:23] <ioria> johnjbogle, try to blacklist the other module : echo "blacklist dell-rbtn" | sudo tee -a /etc/modprobe.d/blacklist-dell.conf  and reboot   (if it fails too we blacklist also dell_wmi)
[18:25] <johnjbogle> done, rebooted.
[18:26] <jeremy31> Paste results for    rfkill list; lsmod | grep dell
[18:28] <johnjbogle> https://pastebin.ubuntu.com/p/PqBMRW4jJH/
[18:30] <jeremy31> disconnect ethernet cable and see if it enables, you might actually need dell-laptop if that is blacklisted
[18:30] <ioria> johnjbogle, dell_rbtn  still loaded
[18:31] <ioria> no, sorry 
[18:31] <johnjbogle> unplugging cable did nothong
[18:32] <jeremy31> johnjbogle:   echo "blacklist dell-rbtn" | sudo tee  /etc/modprobe.d/blacklist-dell.conf  then reboot again
[18:33] <jeremy31> johnjbogle: paste contents of /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf
[18:35] <johnjbogle> done, rebooted
[18:36] <johnjbogle> ok, doing
[18:38] <johnjbogle> https://pastebin.ubuntu.com/p/dNGPjtSWw6/
[18:39] <ioria> johnjbogle, cat /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf | pastebinit
[18:41] <johnjbogle> https://paste.ubuntu.com/p/KG83fkggD9/
[18:42] <jeremy31> That looks standard, not sure why there were errors in dmesg
[18:45] <jeremy31> johnjbogle: have you tried 16.04 or 18.04 on it?
[18:45] <johnjbogle> not 16.04
[18:47] <jeremy31> If that hardware switch is broken the only way is to tape the one pin on the wifi card, or remove it and use a USB wifi
[18:48] <johnjbogle> It's not that it's broken... it's just it's not currently functional during this ordeal right now. Normally when everything is running fine, it works fine too.
[18:53] <jeremy31> johnjbogle: see https://www.youtube.com/watch?v=yzAKcmlaH1M
[18:55] <ioria> johnjbogle, echo "blacklist dell-wmi" | sudo tee -a /etc/modprobe.d/blacklist-dell.conf  ; reboot and run 'sudo rfkill unblock all'
[18:57] <TJ-> johnjbogle: reading back to where you were trying to interrupt GRUB as it boots... For UEFI you have to *tap* Esc key repeatedly, not just hold it down (this because UEFI only processes key-down/key-up events)
[19:00] <TJ-> Also... on many manufacturer's models the module(s) causing this issue are those related to WMI (Windows Management Instrumentation)
[19:00] <jeremy31> johnjbogle: cat /sys/kernel/debug/dell_laptop | pastebinit
[19:26] <johnjbogle> Sorry for delay, had to step away. I just entered grub, tapping esc.
[19:27] <johnjbogle> I see: *Ubuntu , Advanced options for Ubuntu , System setup.
[19:38] <johnjbogle> Backed out of grub, back into desktop. I typed in the blacklist dell wmi code,it said Too many arguments.
[19:38] <johnjbogle> https://pastebin.ubuntu.com/p/DS47XvHppW/
[19:40] <ioria> johnjbogle, just : echo "blacklist dell-wmi" | sudo tee -a /etc/modprobe.d/blacklist-dell.conf and when you reboot then run 'sudo rfkill unblock all' ; 
[19:42] <ioria> johnjbogle, is it clear ?
[19:50] <johnjbogle> 'sudo rfkill unblock all' ; 
[19:50] <johnjbogle> with quotes and semi-colon?
[19:50] <jeremy31> This model had working wifi in Ubuntu 14.04 but that kernel must not have had dell_rbtn  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1319791
[19:50] <ioria> johnjbogle, nope, just : sudo rfkill unblock all
[19:51] <johnjbogle> ok nothing happened
[19:51] <johnjbogle> jeremy31 thanks
[19:52] <jeremy31> johnjbogle: cat /sys/kernel/debug/dell_laptop | pastebinit
[19:52] <jeremy31> That should show what the Dell BIOS is reporting
[19:53] <johnjbogle> permission denied
[19:53] <jeremy31> johnjbogle:sudo cat /sys/kernel/debug/dell_laptop | pastebinit
[19:54] <johnjbogle> same message
[19:54] <jeremy31> johnjbogle: do a sudo -i    then run cat /sys/kernel/debug/dell_laptop | pastebinit
[19:55] <johnjbogle> "Youare trying to send an empty document, exiting."
[19:55] <johnjbogle> ok
[19:56] <jeremy31> I should boot my dell
[19:56] <johnjbogle> same message
[19:57] <johnjbogle> https://pastebin.ubuntu.com/p/9r56dhNgFt/
[20:04] <jeremy31> johnjbogle: do a sudo -i    then run cat /sys/kernel/debug/dell_laptop/rfkill | pastebinit
[20:05] <TJ-> johnjbogle: "You are trying to send an empty document" just means the file doesn't exist
[20:05] <jeremy31> the rfkill file should have the info
[20:05] <TJ-> johnjbogle: as in, it could be a directory or there may not be any such name at all
[20:06] <CarlenWhite> !! System Kernal Paniced and found our culprit.
[20:06] <CarlenWhite> Hush you.
[20:07] <CarlenWhite> Or maybe.
[20:07]  * CarlenWhite pours over journalctl's last boot.
[20:09] <jeremy31> johnjbogle: any luck with sudo cat /sys/kernel/debug/dell_laptop/rfkill | pastebinit
[20:12] <CarlenWhite> Looks like on my laptop something has gone wrong with swap. https://termbin.com/yrsy
[20:13] <CarlenWhite> Which is good that I've found what might be causing the panics, but not particular good because the swap part on this system isn't configured correctly.
[20:13] <CarlenWhite> Or rather given a correct size to be useful.
[20:18] <CarlenWhite> Really wishing I created my partitions a bit more sanely.
[20:19] <CarlenWhite> Because if I was real smart, /home would be on it's on part so I can drop into single user and resize it for situations like this and have a means to easily transplant my home if something goes really bad.