=== MagikEh_ is now known as MagikEh [03:02] hiya [03:03] i've been trying to get the keyboard backlights working on a fresh install of lubuntu 16.04 === Phy is now known as Guest23198 === Guest23198 is now known as PhyrexianProcess [03:03] i found the /sys/class/leds/ folder where the stuff relating to them seems to be store [03:03] but i'm not sure how to activate it [03:04] when i do xset q it says that the lights are on, but they clearly arent [03:17] alright, i got it working [08:33] hi, I'm having trouble installing lubuntu-16.04-desktop-amd64.iso from USB stick onto my EeePC 1001px. Basically, after choosing "Try Lubuntu", it gets stuck here - http://i.imgur.com/aO7tPV0.jpg [08:33] I'm not sure whether this is a bug, so I want to ask it here. If it is, I would be happy to create a bug report. === Caerus|Away is now known as Caerus === pavlushka_ is now known as pavlushka === Caerus is now known as Caerus|Away [12:29] confirmed working boot on xubuntu-16.04-desktop-amd64.iso and lubuntu-15.10-desktop-amd64.iso - so it must be a regression in Lubuntu 16.04 [12:30] lubuntu-16.04-desktop-amd64.iso boots, but only when nomodereset is set at Lubuntu boot menu. [14:18] hi [14:19] any idea how to get the rpi 3 work with hdmi and audio on lubuntu? [18:19] hello. I am using Lubuntu 14.04 64bits. How to make Compton compositor work from start? some say to add "@compton" to /etc/xdg/Lubuntu/autostart (wich was an empty file) but it does nothing at reboot, I added " @compton -c -r 16 -l -24 -t -12 -G -b" like www.lubuntu.me says, but still no special affects at start, how can I make it work from start? [18:20] administrador: wait for an answer. [18:21] administrador: there's a similar file in ~/.config. i'd use that instead [18:22] wxl I'll try that [18:22] administrador: also you don't need to reboot, just re-login. those are read when x starts. [18:22] well [18:22] the x session [18:27] wxl, It worked, thx [18:28] :) [18:28] administrador: np! [18:28] well, reboot is the ultimate test [18:28] :D [18:28] reboots are for windows users [18:29] ;) [19:19] [11:28:48] reboots are for windows users <--- and kamikazi users... but we have live migration. :3 [19:21] * Kamilion grubmles about xen not supporting kexec [23:22] is there anybody here who understands setting up sound from the kernel up [23:23] try the question and we'll see enon_ [23:28] Ok I upgraded from lubuntu 14.04 breaking my sound I use snd_cs46xx module which modprobe shows as loaded but I can not seem to connect with alsamixer or aplay but the snd_cs46xx is on blacklistoss I like to know where to put info such as descried at http://www.alsa-project.org/main/index.php/Matrix:Module-cs46xx#Introduction_for_Cirrus_Logic_CS46xx_soundcard [23:31] i've never heard of "blacklistoss" before [23:32] wxl: perhaps they mean /etc/modprobe.d/blacklist-oss.conf ? [23:32] yes sorry for being lazy [23:37] yikes is that still a thing? [23:39] yes itś a prehistoric IBM Thinkpad T22 - and in the hands of an unemployed homeless man [23:41] i am not sure i grok why it needs to be in the blacklist [23:41] to me that seems sort of counterintuitive [23:42] It is a bit tempermental but will work with enough love [23:44] was it blacklisted before? [23:45] not that I recall [23:45] harumph [23:46] so does lspci -nnk show the device and that it's using the right driver? [23:46] I figure with the proper placement of a ¨#¨ the blacklist shouldn´t be a problem [23:47] sure sure but maybe there IS some reason [23:47] as a general rule, not much uses OSS [23:47] and ALSA comes with tools to fool the kernel into thinking that it's accessing OSS devices that are actually ALSA devices [23:48] i've used a lot of obscure and sometimes archaic linux audio applications and i have never had an issue with ALSA (or JACK for that matter) [23:48] so i'd start with lspci which checks that the device (the hardware itself) is properly seen and that the driver is being used by the device [23:50] lspci show both deveic @ 00:05.0 and kernel module as snd_cs46xx [23:51] so that's good news [23:51] now it's a question of what's up with alsa [23:52] stupid question but have you tried reloading alsa? [23:58] I tried getting asla from ¨ppa:ubuntu-audio-dev/alsa-daily¨ [23:58] ough [23:58] i would not consider that a solution [23:58] but a potential way to create a problem ;) [23:58] maybe the instructions I followed were somehow wrong [23:59] wxl: do you know about hardware? [23:59] n-iCe: what's the question? [23:59] enon_: the problem is anything that is a "daily" means it's likely to break