=== qengho is now known as CardinalFang === CardinalFang is now known as qengho === peterrus- is now known as peterrus === siel_ is now known as siel === geheimni1` is now known as geheimnis` === DJones_ is now known as DJones === Kamilion|ZNC is now known as Kamilion === slacker_1l is now known as slacker_nl === qengho is now known as CardinalFang === CardinalFang is now known as qengho [12:26] Hiyas all [13:31] Good afternoon. === JanC_ is now known as JanC === Warrigal is now known as tswett === krabador is now known as Guest5329 [17:28] hello guys, just a question.. hoiw do you know which exasct driver are you using? (radeon, radeonsi, r600.....)? [17:29] my GPU is an AMD HD6750 === nopf_ is now known as nopf === maxb_ is now known as maxb [18:08] elhoir: lspci -k tells you. [18:08] Or lshw. [18:10] lspci -k says "radeon" [18:10] but, it says so even after purging xserver-xorg-video-radeon package [18:11] thATS WHY I AM NOT SURE [18:11] oooops [18:11] thats why i am not sure [18:25] elhoir: Did you reboot after purging the package? === dcmorton_ is now known as dcmorton === tsimonq2alt is now known as tsimonq2 === dcmorton_ is now known as dcmorton === funkyHat_ is now known as funkyHat === geheimni1` is now known as geheimnis` === locutus_ is now known as 14WABT0IJ === creichen is now known as Guest61415 === Nach0z is now known as 92AAB92AP [19:53] lordievader, cant remember... [19:53] elhoir: the kernel driver reported by 'lspci' is *not* the same thing as the X server video drivers [19:53] Well, if it is still loaded it points to a no. [19:54] That too. [19:54] TJ-, so... what th am i using? :P [19:54] elhoir: if nothing is currently depending on the kernel module it can be unloaded with "modprobe -r radeon" but I'd suspect it is driving the TTYs and therefore cannot be removed [19:56] elhoir: your question is too generic. "you" aren't using a driver, but some software components of the PC are. Which component you mean will require a different answer [19:57] elhoir: once an exectuable program, or library, is loaded into memory it will remain in-use and available whilst it is linked, even if you unlink (remove) the file it was loaded from. [19:57] ok... i mean my GPU [19:58] which driver is it using [19:58] radeon, radeonsi, r600.... [19:58] elhoir: in reality the file is still there, alive and well and being used. unlink-ing only makes it invisible in the file-system. Once no process has it in use *then* the file will be deleted [19:58] TJ-, yeah, i understand, you need a reboot to see the differences [19:58] The GPU kernel module driver for hardware access will be the one reported by 'lspci -k' [19:58] or a X restart [19:59] TJ-, it reports "radeon" [19:59] is it radeonsi? [19:59] The 'driver' (shared library) used by the X server will be reported in /var/log/Xorg.0.log [20:00] * elhoir is looking for it [20:00] [ 50.022] (II) RADEON(0): [DRI2] Setup complete [20:00] [ 50.022] (II) RADEON(0): [DRI2] DRI driver: r600 [20:00] [ 50.022] (II) RADEON(0): [DRI2] VDPAU driver: r600 [20:01] found (i think) [20:02] mesa-vdpau-drivers: /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0 [20:02] vdpau-va-driver: /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.syo [20:02] libgl1-mesa-dri: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so [20:08] and now, why is it using r600 instead of radeonsi? === elhoir is now known as elhoir|afk === tomaw- is now known as tomaw === tlyu_ is now known as tlyu === Bluefoxicy_ is now known as Bluefoxicy