/srv/irclogs.ubuntu.com/2010/03/14/#ubuntu-x.txt

=== Sinnerman is now known as Cobalt
=== yofel_ is now known as yofel
=== L3ttuce is now known as Cobalt
Sarvattok, how about a nonouveau (can anyone think of a better word?) boot option to blacklist the nouveau module so people can actually use vesa or nv without manually blacklisting it? noticing this is a pretty sore spot right now17:02
=== L3ttuce is now known as Cobalt
Sarvattoh, blacklist=nouveau directly from the kernel command line looks like a valid option now that I'm digging through initramfs-tools, didn't know that17:19
Sarvatthttp://bazaar.launchpad.net/~sarvatt/initramfs-tools/working/revision/163 is kind of pointless then if they can just do blacklist=nouveau, need to try that out17:36
Sarvatti'm thinking it might be handy to have say, failsafex or the old xforcevesa as boot arguements. we could blacklist all KMS drivers in initramfs-tools and have the gdm upstart job pick failsafeX if it matches because its already checking the kernel command line for inhibitors17:40
Sarvattthen we could just extend the kernel command line check in /etc/init/gdm.conf to check for the command and set env XORGCONFIG=/etc/X11/xorg.conf.vesa and ship a new stock vesa xorg.conf?17:44
Sarvattactually we could just make gdm exit1 if it matches, that'd automatically start a failsafe session17:46
verbalshadowwhat did i miss? booting with Mobility Radeon HD 4200 with KMS now freeze my system and won't boot with out disabling.17:53
Sarvattverbalshadow: mind filing a bug so we can look at your logs?18:14
Sarvattjust ubuntu-bug xserver-xorg-video-ati and subscribe Sarvatt if you dont mind18:15
Sarvattand whoa booting straight into failsafe is insanely fast compared to normal booting, menu was up in 11 seconds on this slow hdd netbook18:16
verbalshadowSarvatt: filing now18:22
verbalshadowok  now i need to file a bug on ubuntu-bug it thinks i don't have an internet connection and can't connect to the crash DB :(18:31
Sarvatthmm, not having any luck adding the xforcevesa option to initramfs-tools. i added the option to Init and had it set blacklist=drm,i915,nouveau,radeon and quiet=n, and also tried adding a check for xforcevesa to scripts/init-top/blacklist and blacklist those modules explicitly in there 19:20
Sarvattbut plymouth seems to be loading drm/i915 and such on its own19:21
Sarvattchanged the gdm upstart job to exit 1 if it sees xforcevesa in /proc/cmdline to load failsafe and that part works but its using fbdev on top of KMS of course because drm and such is loaded for plymouth19:22
Sarvattlooks like i need to either extend plymouth to recognize xforcevesa as well or remove splash from the cmdline if xforcevesa is used19:31
Sarvattno luck, removing splash doesn't stop i915 from loading. hmm20:02
=== radoe_ is now known as radoe
bjsnideris superm1 ever in here on weekends?20:06
Sarvattverbalshadow: https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/53809720:08
ubottuLaunchpad bug 538097 in launchpad "Apport cannot connect to crash database" [Undecided,Confirmed]20:08
Sarvattmaybe if you ping him and ask a question he might pop up :)20:09
bjsniderare there any useful dkms logs anywhere? there's one in /var/log but it's no help20:21
albert23bjsnider: there is a full build log like  /var/lib/dkms/nvidia/kernel-2.6.31-20-generic-x86_64/log/make.log20:26
bjsniderif the build didn't happen on that kernel that directory and log do not end up existing20:47
bjsniderall i get here is exit code 620:50
Sarvattanyone really familiar with compiz? i'm almost positive its one of our patches breaking resoluions where one side is the same as the max texture size, 010-disable-child-window-clipping.patch maybe? it's just 1 pixel thats the problem, 2047x1152 works for instance if the max texture size is 204822:36
RAOFI used to be a bit familiar with compiz.22:37
BUGabundoRAOF: used to ?22:41
RAOFCompiz *has* been around a while :).22:41
BUGabundoahh22:41
BUGabundowell, before compiz we had 22:41
Sarvattwe should probably adjust our max texture size checks in 060_move_checks_to_compiz.patch to max -1 though because people with 2048x1152 monitors are having all kinds of problems22:42
BUGabundo... what was it called? ....22:42
* BUGabundo blanks22:42
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/42876922:43
ubottuLaunchpad bug 428769 in xserver-xorg-video-intel "compiz starts with a blank screen on a 2048x1152 monitor" [Undecided,Confirmed]22:43
Sarvatti want to ask those people to try a fedora livecd and see if its different because they dont have most of our compiz patches :D22:43
RAOFWhich lucky bugger has a 2048x1152 monitor? :)22:43
Sarvattlots of mac people22:44
RAOFAaah.22:44
BUGabundoehe22:49
MarcoPauHello, I just put xserver-no-backfill ppa in my sources.list but I don't get anything upgraded out of it. Any hint? Using karmic23:39
libvjcristau: ?23:40
MarcoPauthe xorg-server package itself is not available23:40
libvjcristau: how does this affect compatibility over the different kernel versions?23:40
libv(from a separation pov, i like the move though, this drm/libdrm stuff is a right mess)23:41
libvnah, nm my question, the compat issue is just as bad from either side of the change23:49
libvthere are only two solutions to this compatibility issue anyway23:50
jcristaumeh.  whoever tries to make it work with different versions can fix things up23:50
libvyes :)23:51
libvit's an issue between developer and user, and the packager is between a rock and a hard place there23:51
libvunable to satisfy both in the current constellation23:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!