=== hggdh_ is now known as hggdh === Logan_ is now known as Guest14478 === Logan__ is now known as Logan_ [06:30] anyone know if this package is needed for anything gnome-session-fallback? [06:31] classic gnome look? [06:31] !notunity [06:31] Ubuntu 11.10 and higher use GNOME 3 with the !unity shell by default. To use GNOME Shell instead, install the "gnome-shell" package and investigate "gnome-tweak-tool". For GNOME Fallback mode, which is similar to GNOME 2, install "gnome-panel". Both packages will place entries in the Sessions dropdown. Using Natty? See !classic [06:32] thought it was going away in 13.04 [06:32] !info gnome-panel [06:32] gnome-panel (source: gnome-panel): launcher and docking facility for GNOME. In component universe, is optional. Version 1:3.6.2-0ubuntu3 (raring), package size 336 kB, installed size 1352 kB [06:33] so as long as i dont need to use classic gnome im ok without it [06:33] sure [06:34] thanks [06:35] its way too early to be thinking [06:42] !info gnome-session-fallback [06:42] gnome-session-fallback (source: gnome-session): GNOME Session Manager - GNOME fallback session. In component universe, is optional. Version 3.6.2-0ubuntu3 (raring), package size 3 kB, installed size 180 kB [14:23] Hi guys. I have a problem. Ubuntu always uses vesa drivers instead of AMD Catalyst FGLRX. Why is that so? it happens on 13.04 12.10 12.04 . Can you help me fix that [14:30] hmm, what AMD chip do you have? [14:33] christaras: you're jumping from channel to channel switching support question. [14:33] It is 6450 [14:34] Well iam in #ubuntu too but i was told to come here too (as i said it is Asus Ati radeon 6450 HD) [14:36] well if it fails in 13.04 I guess you can ask here! [14:37] christaras: However, it's not unusual for the binary drivers to be broken in alpha releases; so you're probably better to try and get it working in the release [14:38] Well it doesnt work in any other ubuntu version thats why asked in #ubuntu too [14:40] so propably i have to buy a new graphics card or hat :P? [14:40] what* [14:49] christaras: Shouln't need to, can you pastebin your /var/log/Xorg.0.log ? [14:50] of course [14:50] anyway, if you have an HD6xxx you don't want, I could do with upgrading my HD4xxx === LordOfTime is now known as TheLordOfTime [14:51] well my previus graphics card was nvidia 8400 GS [14:51] ahhhhhh [14:52] christaras: Have you done a full reinstall since swapping from the nvidia? [14:52] HAHHAHAHAHHAH ......HAHAHAHHAHHA at least 9 times .... [14:52] and it is driving me mad :) [14:52] http://pastebin.com/NwX231pp [14:53] oh ok, old installs with nvidia libs often mess things up [14:55] just something i forgot to mention i tried to install them with kernel 3.2/ 3.6/3.7/3.8 all of the have the same problem [14:55] christaras: So that log says fglrx is all great - what makes you think it's not using? [14:56] the fact that glxgears have 400 fps and ubuntu says that i use vesa 107 [14:56] where does it say vesa 107 ? [14:56] Also games run 10 times better under windows rather than linux (i mean native games not trough wine) [14:57] well my computer is in Greek now so... [14:57] and now you're delving into the offtopicness. [14:57] (for windows vs. linux) [14:57] I am not you go of topic [14:57] !offtopic | christaras [14:57] christaras: #ubuntu+1 handles support for the development version of Ubuntu. Please join #ubuntu for all other Ubuntu support. Chat in #ubuntu-offtopic. [14:57] TheLordOfTime: Woah hang on [14:57] penguin42, about his comparing windows v. linux [14:58] and gaming? [14:58] AT about this computer it says VESA:107 [14:58] thhat's on topic here? [14:58] christaras: So if in 13.04, you go to system settings-details waht does it say in Graphics in overview? [14:58] ... oops my 13.04 VM's imploding, time for a reinstall :P [14:58] The lord oftime can you PLEASE STOP IT. WHAT I MEANT IS THAT IT IS NOT WORKING CORRECTLY AND I SAID THAT IN ORDER TO SHOW IT! [14:58] TheLordOfTime: Well that was only one line! [14:59] penguin42, true, i was overly hasty. [14:59] * TheLordOfTime grabs the latest daily ISO [14:59] VESA: 107 [14:59] thats is what it reports at Details [15:00] christaras: and on the detail-graphics tab what does it say for Driver? [15:01] As i said DriverVESA 107 Enviroment: Normal [15:02] (keep in mind that i am translating these from GREEK-->ENGLISH so it may not be way too accurate) [15:02] I have to agree that's odd, my reading of the X log you gave me is that fglrx is happy [15:03] Well it seems to be because amd Catalyst control center is usable [15:03] for example i can enable v-Sync [15:03] And different settings affect performance of glxgears but still it is slow. [15:04] i know that glx gears is supposed to give way more fps than just 180 [15:05] And trine 2 is playable on my pc at HIGH settings. On linux i cant even play it at 800x600 LOWEST (thelordoftime dont say offtopic :P) [15:06] christaras: and what does glxgears -info say for GL_RENDERER? [15:06] GL_RENDERER = AMD Radeon HD 6450 GL_VERSION = 4.2.11903 Compatibility Profile Context GL_VENDOR = ATI Technologies Inc. [15:07] it is way too strange everything is like working but in fact it doesnt!!!!! [15:08] * penguin42 gets 2080 fps on glxgears with the open driver on his HD4350 - IFF I turn vblank sync off [15:08] christaras: Jus tto check, export vblank_mode=0 and then run glxgears? [15:09] it is off otherwise how could i get 189 fps [15:09] yeh, I thought I'd check anyway [15:10] 231 fps [15:10] 288 [15:10] 372 [15:11] christaras: So I dunno what's going on with that, the only thing I can think of is that you're hitting some weird power saving thing [15:11] christaras: What happens if you remove fglrx and fall back to the open ATI driver ? [15:11] same performance [15:11] everything works the exact same. also kernel 3.8 boot correctly then [15:12] odd [15:12] now i am using 3.7 because 3.8 is dead now :) [15:13] christaras: I'd also look at whether you're hitting some power or CPU limit somewhere - my reading of your X logs says it's happy [15:14] well glx geats takes around 10 cpu [15:15] my phone can outperform this XD [15:20] you swapped from nvidia to amd? [15:20] bjsnider: But reinstalled [15:20] i wouldn't do that even if the alternative was galactic armageddon [15:20] well i have already formated [15:20] Well you would do that if you had no money to spent on it [15:21] it was either that or an old nvidia for the same money thats sucked. [15:21] i want a gpu for gaming too not only for texting [15:21] gaming in windows? [15:22] No [15:22] Games for linux exist too [15:22] trine 2/xonotic steam desura. [15:23] yeah, i'm just wondering why you chose amd [15:24] it was cheap :) [15:24] so what does dkms status give you? [15:24] fglrx-updates, 9.000, 3.7.0-7-generic, i686: installed [15:25] and if you do modprobe is fglrx there? [15:25] i mean lsmod [15:25] obviously vesa is going to be there [15:25] bjsnider: http://pastebin.com/NwX231pp is his X log - looks good to me [15:26] yeah i was reading it already [15:26] have a look http://pastebin.com/B1U0E8xf [15:27] christaras: This is a fairly normal Ubuntu setup with just a single user that you created during install time [15:27] yes [15:29] the xorg log doesn't have the info necessary to check what's happening [15:29] maybe dmesg does [15:29] or maybe there's more info at the end [15:30] it loads fglrx, but then right at the end it says oops i have to use vesa [15:31] how can i give you dmesg because terminal isnt big enought to show all this info [15:31] did you just copy-paste our of a terminal? [15:31] the xorg log is a file [15:32] the terminal might not have the entire log [15:32] no this was the log files itself i am talking about dmesg output not [15:32] now* [15:34] dmesg > result [15:34] then you have a file called result [15:35] http://pastebin.com/Fihd14yB [15:36] oh, vesa is loaded first [15:37] so vesa is loaded and fglrx cant be loaded too and it just lets vesa to continue :P [15:37] sucks that you've got all of those hda-intel: spurious response messages spamming dmesg [15:37] looks like it [15:37] can i disable vesa protocol once and for all ? [15:38] you could blacklist the module [15:39] hmmm..? how [15:39] this is not a good idea [15:39] vesa is there in case all else fails [15:40] so if all else fails, you would just get a black screen with vesa blacklisted [15:40] well if you have no other idea i am willing to do so [15:41] i really don't think i want to be providing that advice [15:41] you can look it up though, it's not a secret [15:42] blacklisting vesa should not be considered a permanent solution to this problem even if it seems to work [15:43] Why not? [15:45] Well just to point out something, I dont know if this is normal but i can play trine 2 even with vesa (laggy of course) [15:47] because if you're a trapeze artist, you want a net beneath you in case something goes wrong [15:49] so will remove vesa and report back [15:49] :) [16:10] Well i removed vesa completely and it was still reported as the used driver. I uninstalled fglrx and returned to radeon and now i have 1800fps with glxgeats [16:10] glxgears [16:12] yeh! [16:12] christaras: What CPU do you have? [16:13] e2160 intel celeron dual core 1,8 GHZ [16:15] Going to install beta 12.11 and report back again :) [16:15] christaras, you mean 13.04 :P [16:16] no i mean 12.11 amd catalyst [16:16] oh i see [16:16] * TheLordOfTime misread [16:16] i am on 13.04 right now... :P [16:16] i only just reocnnected ;) [16:16] Ok :) [16:16] :O) cant install on kernel 3.8 [16:16] will reboot on 3.7 [16:16] I will be back :) [16:22] well i am on 3.7 and i have this error now... fglrx installation requires that the system have kernel headers. /lib/modules/3.7.0-7-generic/build/include/linux/version.h cannot be found on this system. [16:23] If anyone has any idea about how to fix that then just say it. i will try to fix it meanwhile [16:26] is the right linux-headers package installed? [16:27] i think so [16:27] Linux kernel headers for version 3.7.0 on 32 bit x86 SMP is installed [16:27] Generic Linux kernel headers too [16:28] the headers are in usr/src not /lib on my system [16:28] but I'm currently on 12.10 [16:28] i check these on synaptic package manager (the best) [16:29] well i will install any linux header available XD [16:30] are you using the fglrx package or upstreams? [16:30] excuse me ? [16:30] it would be weird when the package looks in the wrong place for the files [16:31] well i dont knwo what you mean but i had the same problem with OpenSuse [16:32] AMD SUCKS! i will not buy anything they create in future [16:33] so you aren't using a package? [16:33] What do you mean? [16:33] i am trying to install the latest driver downloaded from amd 12.11 with sudo sh amd.run [16:33] how are you installing fglrx? [16:34] sudo sh amd.run [16:34] ... [16:34] that can fail easily [16:34] indeed. [16:34] you can try symlinking the headers to the place it expects [16:34] Well how else can i install latest version? [16:34] what jtaylor said, try symlinking the headers to where it is looking for them. [16:35] that's the problem with precompiled .run files, no? you can't figure out what its looking for where until it errors [16:35] Well i am not an expert with ubuntu... but i will search for that :) [16:36] acctualy the whole path /lib/modules/3.7.0-7-generic/build/include/linux/ exists but version.h is missing [16:44] christaras: It's easier if you use ubuntu's jockey system to install AMD drivers [16:45] it installs an old version doesnt it? [16:45] christaras: Wouldn't you prefer a working version? [16:45] Well yes :) [16:46] i cant fix it anyway. [16:46] christaras: So be careful to uninstall the stuff you installed via AMD, reboot and then do jockey-text -l to list what's available, then use jockey-text -e to install it [16:48] isnt it the same trough synaptic ? [16:50] not sure what the package is called via that; (Actually I've not tried this on new ubuntu's - they used to have a GUI to do it - additional drivers - not sure what the way to do that now is, but the jockey-text should work) [16:50] Well i have no idea how jockey-text works so i will install it the user-friendly way with GUI [16:54] well it is downloading and will soon install (will take 2 mins to download) [16:58] !schedule [16:58] Raring Ringtail (13.04) release milestones can be found at https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule [17:01] the moment of truth is close rebooting. [17:19] just came back to report that it failed to work [17:22] catalyst installed through jockey and had low performance AGAIN because vesa was used instead (although i had it uninstalled O.o), Tried forcing installing catalyst 12.11 with --force over the old version and then i had no unity working and no hardware accelaration, I just uninstalled everything and now i have Radeon open source installed from kernel 3.8 which has increased perfomance for amd GPUs. Thank you all for trying to he [17:22] GoodNight :O) [17:59] he may have blacklisted vesa instead of vesafb [17:59] i think the module's kernel name is vesafb [20:59] anyone have working sound in dosbox? [21:29] boas