[00:03] <capum321> hello
[00:07] <wxl> how can we help, capum321 ?
[00:10] <capum321> my wifi isn't working. nmcli connection outputs http://termbin.com/5iok
[00:10] <wxl> capum321: gimme `lspci -nnk` plz
[00:11] <capum321> http://termbin.com/lchc
[00:13] <wxl> capum321: you don't have onboard wifi?
[00:14] <capum321> yes, i used on windows and more recently on mint xfce. it worked from the "zero point"
[00:15] <capum321> look this
[00:15] <wxl> capum321: well i don't see a wifi device on your lspci list
[00:16] <lynorian> is it usb?
[00:16] <capum321> http://termbin.com/m5f4]
[00:16] <capum321> http://termbin.com/m5f4
[00:16] <wxl> ah i see
[00:16] <capum321> no it is a notebook full featured wireless
[00:16] <wxl> the ethernet device provides the wifi
[00:17] <capum321> never happen to know that!
[00:17] <wxl> never heard of that chip or that driver before, so will have to do some searching
[00:17] <capum321> wxl i remeber I had to adapter on windows one for cable, one for wireless
[00:17] <capum321> two!
[00:18] <wxl> here's an example of someone with that ethernet chip but also a separate network controller https://askubuntu.com/questions/618150/wifi-problem-in-ubuntu-14-04-intel-corporation-pro-wireless-4965-ag-or-agn-kedr
[00:18] <capum321> are you 100% sure it the same chip?
[00:19] <wxl> the pci id confirms it (11ab:4363)
[00:19] <capum321> i mean... same chip both ethernet and wireless!
[00:19] <wxl> except i don't see the separate wifi chip
[00:19] <wxl> on your list
[00:20] <wxl> yeah yours is usb!
[00:20] <wxl> now i'm seeing it
[00:20] <wxl> look at the bus info on the wireless http://termbin.com/m5f4 (usb@1:1)
[00:21] <wxl> give me `lsusb`
[00:22] <capum321> want to see the manual? http://suporte.itautec.com.br/eportaldownload_ptb/start.swe?SWERowId=2-AP7HXK&SWEField=s_3_2_28_1&SWERowIds=SWERowId0%3d2-AP7HXK&SWENeedContext=true&SWESP=false&SWEMethod=Drilldown&SWECmd=InvokeMethod&W=t&SWEVI=&SWEPOC=&SWETargetView=&SWEDIC=false&SWEReqRowId=1&SWEView=ITC+Driver+Download+TotalDrivers+Notebook+View&SWETVI=&SWEC=7&SWEM=&SWEBID=-1&SWESPa=&SRN=&SWEContainer=&SWETS=&SWETA=&SWEApplet=ITC+Drivers
[00:23] <wxl> yiiiiikes no thanks. `lsusb` will suffice. :)
[00:24] <capum321> http://termbin.com/3qyh
[00:24] <wxl> yep there it is
[00:24] <wxl> so you do have usb wireless
[00:25] <wxl> to put my mind at ease, give me the results of `rfkill`
[00:26] <capum321> 'rfkill wifi' ?
[00:26] <wxl> yeah that works
[00:27] <capum321> no
[00:27] <capum321> rfkill list wifi ?
[00:27] <wxl> argh yes
[00:27] <wxl> sorry getting old and forgetful
[00:28] <capum321> http://termbin.com/za3n
[00:28] <capum321> no you are very helpfull thanks a lot
[00:29] <wxl> so that's good
[00:29] <wxl> but clearly you're not getting a device id, so something's wrong with the kernel
[00:29] <wxl> well, kernel driver
[00:30] <wxl> do you still have the mint installation?
[00:30] <capum321> when installed. it didn't have internet connection because no dhcp is enable on my router. and i didn't check to install third party drivers
[00:31] <capum321> which especifies wifi driver among others
[00:31] <capum321> mint no.. did clean install
[00:31] <wxl> ah fooey
[00:31] <wxl> i'm not seeing any recent complaints about this
[00:31] <wxl> i did see back in 2008 or so people were using the xp driver but this was supposedly fixed shortly thereafter
[00:32] <wxl> and again, that would be in the kernel
[00:32] <wxl> so if mint worked, this should just work......
[00:32] <capum321> i can get the iso?
[00:32] <wxl> hm?
[00:32] <capum321> i saw some solution which you get the driver from the iso using synaptic ?!
[00:33] <capum321> let me find the page
[00:33] <wxl> you might be talking about the sort of thing you need to do with broadcom devices but this should not be the same
[00:33] <capum321> oh
[00:34] <capum321> i didn't understand you saying if mint worked, this should just work? what?
[00:35] <wxl> supposedly your card is supported since you find 0bda:8189 in `modinfo rtl8187 | grep 8189`
[00:35] <wxl> and that's the driver you're using
[00:36] <capum321> i never used modinfo?
[00:36] <capum321> but i can find 0bda:8189 part
[00:36] <wxl> it just gives you information on the specific kernel driver (module)
[00:37] <wxl> if you look at that one thing you sent (from hardinfo???) you're using the rtl8187 driver
[00:38] <wxl> maybe you have another conflicting driver on the system
[00:38] <wxl> let's try `lsmod | grep rtl`
[00:39] <capum321> lshw -C network if it matters
[00:39] <capum321> ok
[00:39] <wxl> yeah that's what it was. it doesn't but i couldn't remember :)
[00:41] <capum321> http://termbin.com/2sgd
[00:41] <capum321> could I say there is four devices using this driver?
[00:41] <capum321> are*
[00:41] <wxl> no these are just drivers
[00:42] <wxl> so if you look at `modinfo rtl8187 | grep depends` you can see those other drivers are requirements of this one
[00:42] <wxl> so in order to all work, they should all be there, which they are
[00:43] <wxl> and you don't appear to have any other drivers, so that's positive
[00:44] <capum321> something is missing ?
[00:45] <wxl> somewhere. just haven't found it :)
[00:45] <capum321> let me help helping me. what should be the keywork to lookup ?
[00:45] <capum321> keyword*
[00:46] <wxl> http://linuxwireless.org/en/users/Drivers/rtl8187/ seems to suggest rtl8187 is the right driver
[00:47] <wxl> if you search through logs (syslog, dmesg), do you see anything relevant? maybe search for rtl8187 and look around instances of it
[00:48] <wxl> as far as i can tell you have nothing obvious that should keep it from working. you have the right driver for the device. there are no obvious blocks or conflicts.
[00:48] <wxl> in fact what you may want to do is watch the logs while you restart the module
[00:48] <wxl> you can do `modprobe -r rtl8187` to unload the module
[00:49] <wxl> then open up two terminals
[00:49] <wxl> in one do `tail -f /var/log/{syslog,dmesg}` (that bracket syntax works in bash, which should be default)
[00:49] <wxl> then in the other, run `modprobe rtl8187`
[00:49] <wxl> oh and do those modprobes with sudo
[00:49] <wxl> (or be root)
[01:01] <wxl> capum321: i hope i have been helpful. i need to head home for the evening but feel free to ask questions. i'm sure someone else will be around
[01:02] <capum321> listen
[01:02] <capum321> what should i look for?
[01:02] <wxl> well if you do what i say with watching your logs while you re-load the module, you should be able to get some output and see what errors come up
[01:03] <capum321> the terminal with tail? Ctrl + C ?
[01:03] <wxl> ctrl-c to stop watching, yes
[01:04] <capum321> it connected !?
[01:04] <capum321> yes it is
[01:04] <capum321> why?
[01:04] <capum321> just unloading it?
[01:05] <wxl> if you unload it with modprobe -r
[01:05] <wxl> and then load it with modprobe
[01:05] <wxl> that's when it should give you errors
[01:09] <capum321> how to get the file?
[01:09] <capum321> just open /var/log/syslog ?
[01:09] <capum321> wxl ?
[01:18] <nmide> hi, does anyone have any experience with multi-head on lubuntu / lxde ? because of what in my opinion is just nvidia being jerks i can't get multiple monitors working on a single x screen
[01:18] <nmide> so i have screen 0 and screen 1 - but screen 1 seems to be completely unmanaged, no themes, no window management
[01:18] <nmide> it has the classic "X" shaped cursor that i remember seeing years ago when launching xfree86 manually without a window manager
[01:19] <nmide> i can export DISPLAY=":0.1" && <run program> to start applications on it but they are undecorated
[01:20] <nmide> i realize i won't be able to drag windows back and forth or do any of those convenient things that come from having multiple displays on one x screen but if anyone can point me in the right direction on how to have basically...the window manager actually running on screen 1 as well, would be much appreciated
[02:06] <capum321> NetworkManager[601]: <info>  [1467248557.5319] device (wlan0): interface index 4 renamed iface from 'wlan0' to 'wlx001122334455' why loading my driver with modeprobe rtl8187 does this rename to interface?
[07:33] <sat> hello
[10:07] <Dylan> Hello, can someone help me ?
[10:07] <Dylan> I just installed Lubuntu 16.04
[10:07] <leszek> Dylan: please just ask your question. Then you will see if someone is capable to help you
[10:07] <leszek> asking for asking is a bit redundant
[10:07] <Dylan> But i can't see my taskbar
[10:07] <leszek> :)
[10:08] <Dylan> I hope you understand what i try to say :s
[10:08] <leszek> Dylan: oh thats too bad. Is it maybe invisible ? Can you left click bottom left and see a menu popup ?
[10:08] <Dylan> It's not invisible
[10:08] <Dylan> if i click, nothing
[10:09] <Dylan> it's like i don't have after the installation
[10:09] <leszek> Dylan: can you make it appear again by alt+f2 and then typing in lxpanel
[10:09] <leszek> I hope the run window stuff appears on alt+f2
[10:10] <Dylan> yea on alt+f2 something appers
[10:10] <Dylan> but when i write lxpanel
[10:10] <Dylan> nothing
[10:10] <Dylan> just the pop up close
[10:10] <leszek> hmm... very strange
[10:10] <leszek> can you open lxterminal with alt+f2
[10:10] <Dylan> Yea i'm in
[10:11] <leszek> then type in lxpanel and see if it shows an error message
[10:11] <Dylan> There is already an instance of LXPanel. Now to exit
[10:11] <Dylan> terminal tell me that
[10:13] <Dylan> Even on google i didn't find any soluce
[10:13] <leszek> Dylan: that means it is running int he background somehow
[10:13] <leszek> can you enter killall lxpanel
[10:14] <leszek> to kill every instance and then try restarting it
[10:14] <Dylan> after the "killall lxpanel" and typing "lxpanel" i have :
[10:15] <Dylan> (lxpanel:4071): Wnck-WARNING **: Unhandled naction type _OB_WM_ACTION_UNDECORATE
[10:18] <Dylan> I tried : killall lxpanel && lxpanel --profile Lubuntu
[10:18] <Dylan> But that said "lxpanel : no one processus find"
[10:22] <Dylan> I have a question, if i have two television (or screen), on the second, can i see the taskbar?
[10:23] <Dylan> cause, i have an laptop but, my screen on it, is dead, so i'm navigate with the other, that maybe the problem
[11:12] <Dylan> sorry i bugged
[11:13] <leszek> Dylan: yeah that could explain the problem. The panel appears then on the wrong monitor. Can't you turn off the non working one in the settings and only use the working one as primary. You can install a tool like arandr which should be useful in creating such a config
[11:14] <Dylan> I don't know how do for unable the wrong monitor
[11:15] <Dylan> desactivate the wrong monitor*
[11:16] <Dylan> i'm isntaling arandr for try
[11:17] <Dylan> WELL man thank you <333
[11:17] <Dylan> you saved me
[11:17] <Dylan> that works!!
[11:17] <leszek> need to go now. Hopefully it works for you otherwise just ask the other people here in the chan they are able to help you
[11:17] <leszek> bye
[11:17] <Dylan> bye man :)
[11:17] <Dylan> see you
[12:17] <capum321> hello
[12:34] <Salmoneus> hi all, i got an update notice yesterday. it looked like system updates. i installed, but i've noticed that on startup the system appears a bit unstable and even slower than normal, losing handily to my windows 10 partition upon startup. anyone else with similar issues?
[17:59] <n-iCe> hi
[21:30] <capum321> hello
[21:37] <capum321> why my system doesn't have /etc/network/interfaces set up, and still I have connection on ethernet and wlan?
[21:39] <genii> Probably because "managed=true" in /etc/NetworkManager/NetworkManager.conf
[21:50] <capum321> genii: yes, it's true, what does it do?
[21:59] <capum321> https://wiki.debian.org/NetworkConfiguration "To create a network interface without an IP address" what's the obejctive here?
[22:01] <capum321> genii: https://wiki.debian.org/NetworkManager If you want NetworkManager to handle interfaces that are enabled in /etc/network/interfaces:   Set managed=true    -    but the file has only 'auto lo' interface populated!
[22:07] <capum321> 'modprobe rtl8187' load up log has this "wlx00aa11bb22cc: renamed from wlan0" why this happening?