[12:21] <BluesKaj> Hey folks
[13:07] <mrpc> The repository 'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu xenial Release' does not have a Release file.
[13:27] <marlinc> Test
[13:41] <krabador> all right.
[15:12] <lotuspsychje> afternoon genii
[15:13]  * genii mumbles things and heads for the coffee
[16:29] <lotuspsychje> !info firefox
[16:29] <lotuspsychje> nice bot synced :p
[16:34] <Ian_Corne> !info dbus
[17:43] <tuxator> hi everyone, I'm currently running Ubuntu 16.04 and after the last update, my fglrx driver got removed. After some reading I found that, apparently, in Xenial there will be no fglrx driver but only amdgpu and the mesa/radeon driver. Is there some kind of workaround? The mesa/radeon driver doesn't even support OpenGL 4.2 yet (at least not in the official repo) and amdgpu seems more like a WIP to me than something belongi
[17:44] <tuxator> I tried installing the fglrx driver manually, but DKMS doesn't seem to like it.
[17:45] <lotuspsychje> tuxator: what does sudo lshw -C video show?
[17:45] <tuxator> I've a R9 270X if that's what you're asking for
[17:45] <tuxator> but here is the output:
[17:45] <tuxator> *-display UNGEFORDERT
[17:45] <tuxator>        Beschreibung: VGA compatible controller
[17:45] <tuxator>        Produkt: Curacao XT [Radeon R7 370 / R9 270X/370 OEM]
[17:45] <tuxator>        Hersteller: Advanced Micro Devices, Inc. [AMD/ATI]
[17:45] <tuxator>        Physische ID: 0
[17:45] <tuxator>        Bus-Informationen: pci@0000:02:00.0
[17:45] <tuxator>        Version: 00
[17:45] <tuxator>        Breite: 64 bits
[17:45] <tuxator>        Takt: 33MHz
[17:45] <tuxator>        Fähigkeiten: pm pciexpress msi vga_controller cap_list
[17:45] <tuxator>        Konfiguration: latency=0
[17:45] <tuxator>        Ressourcen: memory:c0000000-cfffffff memory:fe900000-fe93ffff ioport:d000(Größe=256) memory:fe940000-fe95ffff
[17:46] <lotuspsychje> tuxator: did you try the amd drivers from their website?
[17:46] <ezri> !paste
[17:46] <tuxator> uh yeah that was what I mean with 'installing the fglrx driver manually'
[17:46] <tuxator> ezri: sorry :(
[17:47] <tuxator> will do that next time
[17:47] <ezri> no worries, just for future reference :)
[17:47] <lotuspsychje> tuxator: maybe you should file a bug, togheter with that error you getting after install the amd driver
[17:48] <tuxator> I doubt that would work. It's not a bug that I can't install the fglrx driver, it's by design
[17:48] <tuxator> Look here: https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#fglrx
[17:48] <tuxator> [...] fglrx driver is now deprecated in Ubuntu 16.04[...]
[17:49] <lotuspsychje> tuxator: amdgpu as alternative is what i meant
[17:49] <tuxator> oh, ok.
[17:49] <tuxator> uhm, according to the (sparse) documentation I was able to find, it doesn't look like my GPU is supported by AMDGPU
[17:50] <lotuspsychje> try radeon then?
[17:50] <lotuspsychje> maybe in this testing stage, try both and see what happens
[17:50] <tuxator> then I don't have OpenGL 4.2/4.3/4.5
[17:50] <tuxator> and tbh I'm pretty sure amdgpu doesn't have OpenGL 4.5 either
[17:50] <tuxator> or 4.3 for that matter
[17:52] <lotuspsychje> tuxator: then bug that issue
[17:52] <lotuspsychje> tuxator: i would try both radeon or amdgpu, then see what happens and if errors occur= bug
[17:53] <lotuspsychje> tuxator: if you cant get your system properly working, the devs need to know bout this right
[17:53] <tuxator> hm, ok thank you :)
[17:53] <lotuspsychje> tuxator: so in april we have a nice clean xenial :p
[17:54] <tuxator> yeah, I'm pretty sure I know what's going to happen if I open that bugreport, but I'll do it anyway. And if it's only to vent my frustration ;)
[17:54] <tuxator> bye
[17:54] <lotuspsychje> bugs get solved you know :p
[18:04] <lotuspsychje> !info tmux xenial
[18:04] <lotuspsychje> !info tmux wily
[19:55] <tuxator> Hi again.
[19:56] <tuxator> I didn't submit a bugreport yet, but sent an email to the appropriate mailing list
[19:57] <tuxator> in any case, I gave up on trying to somehow get fglrx to run. But for some reason I can't even get the ati/radeon/amdgpu driver to run
[19:57] <tuxator> I can see that the radoen module is loaded, but the xserver doesn't even consider it.
[19:58] <tuxator> It only searches for the fglrx driver, the ati driver, the modset driver and the fbdev driver. I removed all of those and here comes the fun part: Xserver still manages to load fbdev, even though the .so file isn't even there.
[19:58] <tuxator> Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so <- that file does not exist
[20:00] <tuxator> any ideas why Xserver succeeds in loading it anyway?
[20:01] <tuxator> and why it doesn't load/try to load the correct driver?
[20:32] <tuxator> o_0
[20:32] <tuxator> now stuff gets interesting
[20:32] <tuxator> I've no Xorg.0.log but a GUI
[20:34] <tuxator> and inxi -G tells me that I do not have a driver loaded
[20:35] <tuxator> dmesg shows some radeon entries, but IIRC those were there previously, too
[20:35] <tuxator> oh, nope
[20:35] <tuxator> seems like radeon driver is loaded
[20:36] <tuxator> [drm] radeon: 2048M of VRAM memory ready <- that wasn't there before
[20:48] <ezri> No idea if Ubuntu has X11 running as non-root in Xenial (which would work for radeon but not fglrx if so). If they do, Xorg log would be in ~/.local/share/xorg
[20:53] <ChibaPet> FWIW I see xdm being run by root here, and I have /var/log/Xorg.0.log
[20:53] <ChibaPet> (nvidia)
[20:54] <ezri> nvidia and fglrx wouldn't do non-root Xorg
[20:54] <ezri> it'd be intel, nouveau, and radeon
[20:54] <ezri> (determining factor is KMS support)
[20:55] <ezri> anyways. Debian switched so that's why it's on my mind. I don't use Xenial so I could be completely wrong.
[20:55] <ChibaPet> Are you saying it might be flexible enough to do non-root X based on what's being used??
[20:56] <ezri> no idea how they're doing it, I just know it worked out of the box
[21:48] <claudiop> Hi. The nvidia driver is blocking the boot of my optimus system, no bumblebee yet, only nvidia driver and everything else is vanilla. How can I access a prompt to check what went wrong?
[21:59] <genii> Bumblebee is deprecated
[22:00] <k1l_> claudiop: is it booting? where does it stop?
[22:01] <k1l_> does it just need nomodeset?
[22:04] <claudiop> genii, Well, I thought it would be better than nvidia's solution since it implements powersaving. Either way it is still not installed in this system
[22:05] <claudiop> k1l_, It boots and shows plymouth stuff for a while, then the screen stops receiving a feed. Tried to plug an external monitor and the same happens
[22:06] <claudiop> k1l_, It needs that for nouveau because it will freeze without it, but it was booting fine only with intel_idle.max_cstate=7 due to a processor specific bug
[22:06] <k1l_> claudiop: bumblebee is a hack from reverse engeneering. nvidia-prime is the official nvidia tool for hybrid cards.
[22:07] <claudiop> k1l_, I know that. Im giving ubuntu a shot because bumblebee was a bloody mess and needed a trouble free system for casual gaming. 16.04 mostly due to drivers :)
[22:08] <claudiop> On #ubuntu I was told to, "<bprompt> claudiop:     remove like you would anything else, now, if it's not removing in the booted session due to locked files, then reboot, press Shift while booting to get the Grub menu, choose Recovery  from it, go to Root Console, remount the current system as "rw"  -> sudo mount -o remount,rw / <- and do the removal from there" to get rid of nvidia and be able to boot again, but even the recovery utility
[22:08] <claudiop> has several glitches
[22:09] <k1l_> did you try nomodeset?
[22:10] <k1l_> what does the logs say? like syslog or xorg.log?
[22:12] <claudiop> k1l_, Recovery mode has nomodeset by default and it couldn't boot if I resumed manually. I'll try again outside of recovery mode.
[22:12] <claudiop> Within recovery mode /var/log had two files, none of them Xorg.log and systemd logs also didn't had much to tell
[22:14] <claudiop> Yeah, nomodeset has trouble with Xorg. I can see the Xorg failure flashes with the prompt on its back
[22:14] <claudiop> At least can get to a tty with it
[22:17] <claudiop> What I belive to be the error was: "Failed to initialize glx  extension (Compatible NVIDIA X driver not found)"
[22:18] <claudiop> I installed the Nvidia driver from the fancy UI "additional drivers" which comes with ubuntu, not sure if the correct place, but it sure seems like it is
[22:18] <k1l_> that is the correct place. its just a frontend to the repo packages
[22:22] <claudiop> So I guess that I installed the proper supported driver, and I suppose it would be very very bad for an LTS to have buggy drivers (at least with some recent cards). Should I fill a bug or is there a proper way to report these issues for unreleased software?
[22:25] <claudiop> I just noticed something. It says that the supported chipset families are up to GTX 400 series, but I have a 900 series. This is 361 drivers, what is going on?
[22:26] <claudiop> Does ubuntu have two separate drivers for older and newer cards, both with the same version number? I noticed there were two drivers in the UI, but picked the first
[22:27] <k1l_> well, you are using a development release: look up the exact drivers and from which drivers your card is supported. then, if its a bug, report it so it could be fixed.
[22:27] <k1l_> !bug | claudiop
[22:43] <k1l_> uh: https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#fglrx
[22:43] <k1l_> The fglrx driver is now deprecated in 16.04, and we recommend its open source alternatives (radeon and amdgpu). AMD put a lot of work into the drivers, and we backported kernel code from Linux 4.5 to provide a better experience.
[22:45] <daxcat> that's AMD not nvidia tho
[22:45] <daxcat> or was that quote unrelated to previous discussion
[22:46] <k1l_> yeah. but i guess there will be a lot of "where is my fglrx package now" when 16.04 is been released :)
[22:46] <daxcat> indeed
[22:46] <daxcat> recommended reply: "to hell where it belongs". fglrx is/was terrible
[22:46] <k1l_> yeah, was just reading "the internet" and found that
[22:46] <daxcat> good at 3d gaming, worse than radeon at everything else, pain in the backside to troubleshoot installation problems with it
[22:54] <daxcat> spam test incoming
[22:54] <daxcat> THIS IS A TEST OF THE EMERGENCY BROADCAST SYSTEM. THIS IS ONLY A TEST,.
[22:54] <daxcat> THIS IS A TEST OF THE EMERGENCY BROADCAST SYSTEM. THIS IS ONLY A TEST,.
[22:54] <daxcat> THIS IS A TEST OF THE EMERGENCY BROADCAST SYSTEM. THIS IS ONLY A TEST,.
[22:54] <daxcat> THIS IS A TEST OF THE EMERGENCY BROADCAST SYSTEM. THIS IS ONLY A TEST,.