| === michael_ is now known as michaellarabel | ||
| bryce__ | anyone know what causes xorg.conf to sometimes get truncated to 0? | 04:23 |
|---|---|---|
| === Amaranth__ is now known as Amaranth | ||
| tjaalton | bryce__: broken jaunty postinst | 06:23 |
| tjaalton | happens at least on a preseeded install | 06:25 |
| bryce__ | tjaalton, mvo fixed the upgrader to handle this case, but anything else we could/should do about it so it's not a problem for folks? | 07:05 |
| tjaalton | bryce__: for karmic, nothing | 07:58 |
| tjaalton | since karmic doesn't install one | 07:58 |
| tjaalton | bryce__: btw, did you pull the changes from xorg git before releasing? | 07:59 |
| bryce__ | tjaalton, I believe so | 07:59 |
| bryce__ | tjaalton, did I miss anything? | 07:59 |
| tjaalton | pushing, at least :) | 07:59 |
| bryce__ | aha there we go | 08:00 |
| tjaalton | there was only one commit after the -vmmouse one, removing it from other archs than x86-based ones | 08:00 |
| bryce__ | ok, different question | 08:00 |
| bryce__ | am I on crack, or did we use to have -fglrx (and -nvidia) on the CD up through Hardy, but starting with Intrepid it is no longer there on the cd? | 08:00 |
| tjaalton | it never was AIUI | 08:01 |
| bryce__ | are you sure? wasn't it in l-r-m, and that was on the CD? | 08:01 |
| tjaalton | only the kernel module was in lrm | 08:01 |
| tjaalton | but the driver had to be downloaded | 08:02 |
| tjaalton | I'm pretty sure, will check now | 08:02 |
| bryce__ | what was the non-kernel driver package called? | 08:02 |
| bryce__ | man, it's times like these I wish my memory didn't suck so bad | 08:02 |
| tjaalton | nvidia-glx-new et al | 08:04 |
| tjaalton | and yes. hardy livecd only had the lrm bits and drdsl from restricted, nothing else | 08:05 |
| tjaalton | well, at least 7.10 had | 08:05 |
| tjaalton | couldn't find the hardy cs | 08:05 |
| tjaalton | *cd | 08:05 |
| bryce__ | ok | 08:06 |
| tjaalton | btw, I'm thinking about answering to the "xorg release process" thread about how they are going to schedule the server release(s) | 08:08 |
| bryce__ | good | 08:08 |
| bryce__ | I hadn't been tracking the list this week | 08:09 |
| tjaalton | since it seems that x.x.0 is going to be released on late March/September from now on, it seems it's a bit late for us | 08:09 |
| tjaalton | _unless_ we get an exception like the gnome guys | 08:09 |
| tjaalton | that was discussed after XDC | 08:10 |
| bryce__ | oh hell, yeah that's about a month late for us | 08:11 |
| bryce__ | was afraid they were going to pick those two months, those are like the worst possible for us :-/ | 08:11 |
| tjaalton | although they are going to release a beta ~three months earlier, and the first RC a month after that | 08:11 |
| tjaalton | and it seems like the last three months are going to be only for bugfixing.. we'll see how that works out | 08:13 |
| bryce__ | so let me see if I understand the l-r-m thingee right... so when it was built, it created debs for the kernel portion (which was included on the LiveCD) and some non-kernel portions (which were only installable from the network). Correct? | 08:15 |
| tjaalton | correct | 08:16 |
| bryce__ | ok, wow | 08:16 |
| tjaalton | l-r-m (the binary package) included all the modules | 08:17 |
| tjaalton | but not all of them were usable, like the nvidia/fglrx ones | 08:17 |
| tjaalton | without the other part | 08:17 |
| Alexia_Death | Hm, Ill ask here, perhaps there is help. | 09:42 |
| Alexia_Death | Im having a problem with karmics x | 09:42 |
| Alexia_Death | It starts in failsafe foe no apparent reason on most coldboots | 09:42 |
| Alexia_Death | Im at a loss as to where I should even start debugging this | 09:45 |
| === crevette is now known as baptistemm | ||
| tjaalton | |Alexia_Death|: the log would be nice | 10:25 |
| |Alexia_Death| | tjaalton: there was no other log than the failsafe I think | 10:25 |
| === |Alexia_Death| is now known as Alexia_Death | ||
| tjaalton | check the gdm logfile then | 10:27 |
| Alexia_Death | I use kdm, but same thing. cheking | 10:28 |
| Alexia_Death | tjaalton: http://pastebin.com/d4a32ad11 | 10:33 |
| Alexia_Death | there is something there | 10:33 |
| Alexia_Death | xinit: unexpected signal 15. | 10:33 |
| Alexia_Death | what does that mean? | 10:34 |
| tjaalton | don't know | 10:35 |
| tjaalton | it doesn't start without a conffile? | 10:35 |
| tjaalton | I'm interested in that logfile | 10:35 |
| Alexia_Death | my KDM log? | 10:35 |
| tjaalton | no, xorg | 10:36 |
| Alexia_Death | for the failes session? | 10:36 |
| tjaalton | what failsafe do you mean btw? | 10:36 |
| tjaalton | failsafe KDE or xorg? | 10:36 |
| Alexia_Death | xorg | 10:36 |
| tjaalton | so get the logfile _before_ failsafe | 10:37 |
| Alexia_Death | you know, the low rez screen | 10:37 |
| tjaalton | that's not necessarily failsafe | 10:37 |
| tjaalton | if it's not forced to use vesa | 10:37 |
| Alexia_Death | it says so on the top of the box | 10:37 |
| tjaalton | well, try to salvage the logfile which has the original failure | 10:38 |
| Alexia_Death | and looks like warped garbage on my laptop pane | 10:38 |
| Alexia_Death | OK | 10:38 |
| Alexia_Death | I need to do it crom the command line sesson | 10:38 |
| Alexia_Death | The X log retantsion really should be longer than just the last session for a vt | 10:38 |
| tjaalton | maybe, but failsafe should save the old one with a different name | 10:40 |
| Alexia_Death | it should | 10:40 |
| Alexia_Death | ? | 10:40 |
| Alexia_Death | Let me see | 10:40 |
| Alexia_Death | What sort of different name? because theres certanly nothing in the Xorg.* variety that could be such a log. | 10:42 |
| tjaalton | there don't seem to be hooks for kdm | 10:46 |
| tjaalton | so just remove the conffile and start over | 10:46 |
| Alexia_Death | what conffile? | 10:47 |
| tjaalton | sigh | 10:47 |
| tjaalton | xorg.conf | 10:48 |
| tjaalton | created by failsafe? | 10:48 |
| Alexia_Death | OK | 10:48 |
| Alexia_Death | that would then be | 10:48 |
| Alexia_Death | sudo rm /etc/X11/xorg.conf.failsafe* | 10:49 |
| tjaalton | no | 10:49 |
| Alexia_Death | O_o | 10:49 |
| tjaalton | the server is using xorg.conf | 10:49 |
| Alexia_Death | yes. I need it. | 10:50 |
| tjaalton | those are backups created by failsafe | 10:50 |
| tjaalton | why? | 10:50 |
| Alexia_Death | nividia driver | 10:50 |
| tjaalton | heh | 10:50 |
| tjaalton | so most likely it's not installed properly | 10:50 |
| tjaalton | missing the kernel module etc | 10:50 |
| Alexia_Death | uh? | 10:50 |
| Alexia_Death | no. i works | 10:50 |
| tjaalton | and you claim it's using failsafe with vesa? | 10:51 |
| tjaalton | it's failing most likely because of nvidia | 10:51 |
| tjaalton | if it starts ok without xorg.conf, I'm right | 10:51 |
| Alexia_Death | It starts ok with it too | 10:51 |
| Alexia_Death | in 4 cases out of 10 | 10:51 |
| tjaalton | so why are we discussing then? | 10:52 |
| Alexia_Death | 4 cases that it does not | 10:52 |
| tjaalton | well, nvidia so.. meh | 10:52 |
| Alexia_Death | tjaalton: there is no alternative that actually works. | 10:53 |
| tjaalton | so if you restart kdm ten times in a row, it fails four times? | 10:53 |
| Alexia_Death | and I doubt nvidia is the problem. It oly happens on colld boots | 10:53 |
| Alexia_Death | no | 10:53 |
| tjaalton | blame kdm them | 10:54 |
| tjaalton | then | 10:54 |
| Alexia_Death | hmmm | 10:54 |
| Alexia_Death | interesiting option | 10:54 |
| Alexia_Death | but just cold boots? | 10:54 |
| tjaalton | no idea | 10:55 |
| Alexia_Death | on cold boots, ive had about 5 since the upgrade, 4 have failed 1 worked | 10:55 |
| Alexia_Death | kdm restart always works | 10:55 |
| tjaalton | my 8600gt works fine | 10:55 |
| tjaalton | never failed | 10:55 |
| tjaalton | but I use gnome | 10:56 |
| Alexia_Death | i had the same wit GDM I think | 10:57 |
| Alexia_Death | the first sessions I used gnome after upgrade | 10:57 |
| Alexia_Death | In jaunty I used GDM but now KDE user switching does not work with GDM any more | 10:58 |
| tjaalton | Alexia_Death: actually, it could be that the xserver tries to start too early, before the nvidia kernel module is usable | 11:19 |
| Alexia_Death | tjaalton: it does have the feeling of a timing issue | 11:19 |
| Alexia_Death | and with an heavily optimised boot thats entierly possible | 11:20 |
| tjaalton | if kdm uses upstart, it could be caused by the upstart job | 11:21 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!