Mailinglist Archive: opensuse-factory (673 mails)

< Previous Next >
Re: [opensuse-factory] openSUSE and Ubuntu's BulletBroof X
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Sun, 21 Sep 2008 22:04:39 +0200 (CEST)
  • Message-id: <alpine.LSU.2.00.0809212153430.18331@xxxxxxxxxxxxxxxx>
Hash: SHA1

The Sunday 2008-09-21 at 18:49 +0200, Robert Kaiser wrote:

But being the of the mad and forgetful scientific type, I will forget
about the nvidia driver when YOU updates the kernel. As a matter of
fact, sax will not solve this particular problem, don't you think?

Actually, it would, in some way, as it would offer you a configuration with the open-source 2D driver, which at least would make the system working.

Dunno. Of course it is possible to change from nvidia to nv, if you do do know that is the problem. But I doubt if it currently offers that change automatically - and probably it doesn't just change that line, it probably will want to change modelines and whatnot.

Plus, there are many things that can crash the X system, which I can not
or will not predict but which I can often repair without Yast or sax.

You obviously haven't read my initial post, or you would have seen that my proposal would be to only do this if we failed to initialize the video driver, which we can detect from the X log easily. An X crash is something very different from a driver initialization failure.

Yes, I have read your initial mail. I may not remember every detail from it, though.

I prefer being dumped into a text terminal with an error message (or
none), than being dumped into sax2, without having being let time to
read the error message at my leisure.

I prefer to actually get an error message and explanation, even as an expert user, and that's what this instance of sax2 needs to provide anyway to be really helpful - along with a cancel button to let me drop into text mode without actually touching any configuration and recompile my nVidia driver if I can (i.e. people like us who know how to do it, given we are lucky and have a source package matching the kernel, which I currently don't have due to inconsistent Factory state - and I was happy I knew how to get up sax2 and have it propose and use a config with the OSS 2D driver for now).

I'd really prefer the cancel button before running sax, not after. It takes a long time here.

I have no objection to a text with a brief analysis of the problem, that would be nice; but I do object to firing sax automatically. I prefer having an option. If it has to be this way, then I would want a sysconfig variable to disable it.

- -- Cheers,
Carlos E. R.
Version: GnuPG v2.0.9 (GNU/Linux)

To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups