[01:05] <Gr33ntea> Hello friends I am having trouble getting my wifi card to work : (, I have posted some system information as well as attempted solutions in the following paste. https://hastebin.com/bixicemiki.sql any ideas whats causing this? :(
[02:08] <Gr33ntea> I have submitted a post to the Ubuntu forum, so if anyone has an account and would like to reply if I'm gone the link is. https://ubuntuforums.org/showthread.php?t=2403551&p=13808094#post13808094
[02:37] <Gr33ntea> Hello sorry I do not mean to spam, I have mentioned before that my laptop cannot find my wifi card which is an intel 9560. I have made a forum post about it here https://ubuntuforums.org/showthread.php?t=2403551, and have also run the wireless script that is recommended in the forums. paste is here. http://paste.ubuntu.com/p/FCnySDKR44/ Im just reposting because I had been had been disconnected and have just returned. 
[03:14] <kinghat> does anyone here compile apps with Qt and know about Qt environment variables?
[11:34] <immu> hi, i need to file a issue please guide with software center
[13:02] <immu> how do i file issues with software center?
[16:06] <Gr33ntea> Hello my computer is having trouble finding my network adapter, I have made a ubuntu forum post about it here, https://ubuntuforums.org/showthread.php?t=2403551. And here is a direct paste of some system information. http://paste.ubuntu.com/p/FCnySDKR44/
[17:44] <mcar> hi everybody ! i went for Cosmic a few days ago and I've got a simple question some Cosmic and Bionic users might help me with
[17:47] <mcar> 'apt-get update' (and not 'upgrade') felt very slow... first I thought it was some bandwidth issue... but I looked and saw that just 'update' had to download like 35-36 Mo (I've got default install with universe/mutliverse/... rep)
[17:49] <mcar> I never had a look while on Bionic (cause it was just fast)... so my question : was it that huge already ? is it normal that 'update' needs so much downloading ?
[17:59] <Gr33ntea> Hello I need to change what firmware driver ubuntu is loading. I need to use firmware 34 according to the Intel site. I have an intel 9560 wifi card. And here is what Ubuntu is telling me is being loaded/requested. https://paste.ubuntu.com/p/Zdm2NsSh2g/
[17:59] <Gr33ntea> I dont see any mention of firmware 34
[17:59] <Gr33ntea> My card is the very first one listed on this site. https://www.intel.com/content/www/us/en/support/articles/000005511/network-and-i-o/wireless-networking.html
[18:08] <tsuzuku_> .
[18:57] <tomreyn> mcar: it may be this much the first time. but once you have this, follow-up downloads will be much smaller.
[19:12] <mcar> tomreyn : thanks. it wasn't my first update (a few daily ones since I installed Cosmic). but maybe download size of 'update' depends on diffs in the repos since the previous one. I'm not sure how that works.
[19:13] <tomreyn> exactly, there are diffs.
[19:15] <mcar> ok. so that would explain why these daily updates require that much downloading : lot of changes (still beta) in the repos : huge diffs... I guess
[19:18] <tomreyn> maybe there are no diffs for cosmic, yet, but more likely there are just a lot of updates.
[19:22] <mcar> yeah, that might explain why just checking for updates is taking that much time/downloading... I guess I'll see how it goes when the release comes...
[19:22] <mcar> thanks for your insight
[19:30] <tomreyn> mcar: so the contents file matches this download size http://archive.ubuntu.com/ubuntu/dists/cosmic/ for cosmic-updates, it will change (post release) and grow to roughly the same size.
[19:45] <mcar> tomreyn: interesting... that's indeed what checking for updates gave me : 38Mo of downloading... looks the same for bionic though http://archive.ubuntu.com/ubuntu/dists/bionic/
[19:52] <mcar> i'm not sure i understand :) I was used to have 'apt-get update' being just a blip of fast downloads in seconds... now it's minutes for me (mild connection) : these 38Mo. Yet contents is that huge as well for Bionic... sooo...
[19:56] <mcar> I will look deeper how it works and also look at content's size over a few days, to better understand this weird feeling I have
[19:57] <mcar> tomreyn: thank you for your time and pointing at me the contents file size
[22:46] <Gr33ntea> Hello I am unable to connect to wifi, and Ubuntu is not finding my WIreless Chip. Here is my system info. http://paste.ubuntu.com/p/FCnySDKR44/ I can verfiy that the correct driver and firmware are loaded, and its not listed as hard blocked. Any ideas?
[22:49] <TJ-> Gr33ntea: looking
[22:49] <Gr33ntea> TJ-: thank you very much : )
[22:50] <TJ-> Gr33ntea: I suspect the ideapad_wlan "Hard blocked: yes" is the problem. It also seems to apply to the bluetooth
[22:51] <Gr33ntea> hm i thought i didn't need that one. 
[22:51] <Gr33ntea> any idea how to unblock it?
[22:52] <TJ-> I'd suspect there is a hardware toogle, or hot-key combo
[22:53] <Gr33ntea> my laptop has an airplane more toggle but it doesn't do anything
[22:53] <Gr33ntea> other than that there is nothing
[22:53] <TJ-> Gr33ntea: can you show us "pastebinit <( dmesg )"
[22:54] <Gr33ntea> mhmm one sec
[22:56] <Gr33ntea> paste.ubuntu.com/p/hr64G8yWBR
[22:57] <Gr33ntea> TJ-: If you don't mind me asking what exactly are you looking for in that output? Just so i know for future reference 
[22:58] <TJ-> mentions of the "rfkill" handler
[22:58] <TJ-> Looks like you've done several suspend/resume cycles in that log
[22:59] <Gr33ntea> Yeah, i've been trying to fix this problem for 2 days now and most solutions require a restart
[22:59] <TJ-> you've also got a nasty stack trace ddue to the nvidia driver
[22:59] <TJ-> Gr33ntea: aha! so on a cold/warm boot it works fine?
[23:00] <TJ-> Gr33ntea: then you allow a suspend and on resume rfkill is permanently on?
[23:00] <Gr33ntea> sorry I worded that poorly, it  does not work on cold boot what i meant to say is that the solutions I have tried had me restart the computer they did not work, the wifi chip never gets found
[23:01] <Gr33ntea> so rfkill is always on
[23:01] <Gr33ntea> not only after suspend
[23:01] <TJ-> OK, for starters, the Wifi chip is found without a problem, and the driver is loaded
[23:01] <Gr33ntea> mhmm
[23:01] <TJ-> the issue is the RFKILL is on permanently
[23:02] <TJ-> can you show us "pastebinit <( for n in /sys/class/rfkill/*/*; do [ -f $n ] && echo $n=$(cat $n); done )"
[23:03] <Gr33ntea> sure, one sec. thank you for all the help btw! i really apprecite it
[23:06] <Gr33ntea> I seem to get an error from that
[23:06] <Gr33ntea> lemme try once more
[23:07] <TJ-> Gr33ntea: Hang on! I've found some Lenovo forum posted which say this is caused by changing the BIOS boot mode to Legacy - is that what you've done ?
[23:08] <Gr33ntea> nope, mine is in UEFI
[23:10] <Gr33ntea> paste.ubuntu.com/p/pJdrF7XpbZ
[23:11] <Gr33ntea> sorry that took so long im going back and forth between 2 laptops since im in the irc chat in a different machine in case i need to restart the other one
[23:11] <TJ-> Is it a Yoga 530 ?
[23:12] <Gr33ntea> Its a Lenovo Y530 the new one, that just came out
[23:12] <Gr33ntea> there is an older one from like 10 yrs back 
[23:13] <TJ-> Does anything happen when you toggle airplane mode because this looks like thats what it is - when you try toggling immediately check the tail of the kernel log in case it is reporting unknown key-code - which would tell us it doesn't know how to interpret the action, so it doesn't toggle ("dmesg | tail" )
[23:16] <Gr33ntea> paste.ubuntu.com/p/Pf6n3gN3W4
[23:16] <TJ-> Is airplane mode keys Fn + F7
[23:16] <Gr33ntea> Fn + F8
[23:18] <TJ-> That last log, the last timestamp is presumably when you pressed the keys "[  736.971817] r8169 0000:07:00.0 enp7s0: link up" ... that message is strange, since the r8169 is the wired ethernet device!
[23:19] <Gr33ntea> I just checked the output after pressing Fn + F8 2 times
[23:19] <Gr33ntea> and that doesn't change
[23:19] <TJ-> I'm wondering if this is an ACPI issue... there's a workaround that sometimes fixes strange issues like this. I've written a guide to it, here, which is worth trying: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html
[23:19] <Gr33ntea> in other words the ethernet never disconnects
[23:19] <TJ-> OK, so that was unrelated to the key-presses - good :)
[23:21] <Gr33ntea> i will try the script mentioned on ur workaround
[23:26] <TJ-> However, I'd highly recommend upgrading the PC firmware to the latest version, 8JCN44WW, released in September
[23:26] <TJ-> I think this is your model. You can check by entering the serial number into the support search pages. https://pcsupport.lenovo.com/gb/en/products/laptops-and-netbooks/legion-series/legion-y530-15ich/downloads/DS503758
[23:30] <Gr33ntea> So the script didn't work, i will try updating the firmware
[23:32] <TJ-> hang on, I think I've found another solution!
[23:32] <Gr33ntea> : O
[23:33] <TJ-> There's an AskUbuntu Q and A where it says the problem is the ideapad_laptop driver itself, and blacklisting it can solve this (on a Y910)
[23:34] <TJ-> It's worth a try: " sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"  " and reboot/test
[23:34] <Gr33ntea> Yeah i did see that, and tried it too
[23:34] <TJ-> this creates a file that prevents the module being automatically loaded at boot-time
[23:34] <Gr33ntea> i will try again though
[23:34] <TJ-> but right now the module is loaded, since we see it's product in the rfkill list
[23:35] <TJ-> if you do "lsmod | grep idea" is that module listed?
[23:35] <Gr33ntea> yeh I undid the blacklist after i tried it, so it should be listed
[23:35] <Gr33ntea> lemme check
[23:35] <TJ-> Ahhh
[23:35] <TJ-> Does the PC still have Windows on? does airplane mode unlock on that?
[23:36] <Gr33ntea> yes to both questions
[23:36] <TJ-> And if it is unlocked and working and the PC warm reboots to Ubuntu, the lock is on?
[23:36] <TJ-> as in, no wifi/bluetooth
[23:37] <Gr33ntea> yes
[23:38] <TJ-> it really sounds like a firmware bug, especially if blacklisting the ideapad_laptop module doesn't solve it, since that infers the PC starts in airplane mode and needs to be forced to unlock, rather than starting with it unlocked 
[23:39] <TJ-> Maybe the windows drivers 'knows' this bug and how to workaround it
[23:40] <TJ-> Interesting idea... when the PC is starting, BEFORE linux kernel begins to operate, try pressing the Fn+F7 combon once. Maybe tap Esc to get to the GRUB boot menu so it pauses for you to do that.
[23:40] <Gr33ntea> just tested the blacklist again and no bueno, so i will update the bios
[23:40] <Gr33ntea> ok
[23:41] <Gr33ntea> wait so i can do the combo at the grub menu? because it loads to the menu by default for me
[23:41] <TJ-> well, in theory the key combo might be picked up by the firmware and acted on before an OS takes over
[23:42] <Gr33ntea> okay about to try it
[23:42] <TJ-> most of these kind of devices are handled via the ACPI
[23:43] <Gr33ntea> this may be a silly question, but what reading material would you recommend to learn all this? x3
[23:44] <Gr33ntea> also just tried pressing the combo at the grub menu and no dice
[23:44] <TJ-> haha! there is none, it is all hard-won experience over many years, and deep-diving source-code, reverse-engineering ACPI and firmware
[23:44] <TJ-> I'm going to look at the Linux source-code for the ideapad module, in case anything gives a clue
[23:44] <Gr33ntea> Wait TJ i just noticed something weird
[23:45] <TJ-> OK
[23:45] <Gr33ntea> When I now boot into windows the wifi is off, gonna try it once more to check and see 
[23:45] <Gr33ntea> but it never used to be like that
[23:45] <Gr33ntea> used to connect right away
[23:45] <TJ-> which might mean the Fn+F7 you pressed di do something and was remembered
[23:46] <TJ-> I've seen instances where the logic is inverted. Another thing you could try is enabling airplane mode in Windows then rebooting to Linux ... be a laugh if it then worked :)
[23:48] <Gr33ntea> so i just rebooted into windows again, and yeah the wifi doesnt connect by default anymore
[23:48] <Gr33ntea> i will try enable airplane mode in windows and check ubuntu
[23:49] <Gr33ntea> nvm im a idiot, the automatically connect thing was unchecked
[23:49] <Gr33ntea> still gonna try the airplane mode idea tho
[23:51] <TJ-> Looking at the (latest) source-code for the module there is a table listing several devices that don't have an rfkill switch, including Y520 (almost the same model as yours) and so the rfkill report always shows the devices as blocked regardless of the state. I suspect that Y530 is in the same boat 
[23:51] <TJ-> In which case, chasing this line may be a red herring 
[23:52] <Gr33ntea> ah tht would make sense
[23:52] <Gr33ntea> they are very similar models
[23:52] <TJ-> So, we could try building that module for you with your model added to the table... from the way I read the code, if the rfkill erroneously reports it is blocked the wifi code won't try to connect
[23:52] <TJ-> let me see if I can pull just that module out and make a DKMS package from it you can install and test
[23:53] <Gr33ntea> you're the best ToT <3