Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 28, 2012 17:40 UTC (Sat) by dlang (✭ supporter ✭, #313)
Unfortunantly a couple of years ago (around the time of the last LTS release), the Intel drivers got really messed up for about 6 months and broke on a lot of people's systems.
Posted Apr 30, 2012 16:38 UTC (Mon) by nye (guest, #51576)
The nvidia blob has in my experience been the only solid, dependable video driver for Linux.
Okay, to be fair to the Intel driver, it is now basically functional and you can expect that your system won't crash these days, but it's hardly bug-free - for example, I've not yet met a system using Intel graphics which doesn't need the screen resolution to be set manually in xorg.conf.
If you actually look at all the cases where people are claiming problems with the nvidia blob, the vast majority don't stand up to scrutiny - typically a developer notices that the reporter is using the nvidia blob, then jumps straight to the assumption that it must be the cause of all problems because it doesn't have the magic OSS sauce.
Basically, it's just politics.
Posted Apr 30, 2012 17:44 UTC (Mon) by mathstuf (subscriber, #69389)
I've had lots of issues with the blob. Mainly when dealing with multiple monitors or WM compositing. I've not used it since around Fedora 10 or so on a day-to-day machine (I have it on a work laptop in an alternate install for OpenCL testing, but that hasn't been booted in months).
> I've not yet met a system using Intel graphics which doesn't need the screen resolution to be set manually in xorg.conf.
I have a desktop (19" 1440x900 monitor) and netbook (9" 1024x600) with Intel graphics that have never needed an xorg.conf for anything.
Posted May 1, 2012 10:57 UTC (Tue) by nye (guest, #51576)
> I have a desktop (19" 1440x900 monitor) and netbook (9" 1024x600) with Intel graphics that have never needed an xorg.conf for anything.
Interesting - does that also hold for GDM/KDM/WhateverDM, or do you not use one? Did it need any special kind of configuration?
In fact I can use KDE's system settings to configure the right resolution each time I log in, rather than writing an xorg.conf from scratch, but that doesn't help for the login manager so I wonder if there might be a way to configure that.
This was all so much easier in the days when all you had to do was uncomment the right line in the provided XF86Config.
Posted May 1, 2012 18:39 UTC (Tue) by dlang (✭ supporter ✭, #313)
Posted May 2, 2012 11:28 UTC (Wed) by nye (guest, #51576)
I can live with it since I don't re-log very often and I haven't motivated myself to write the xorg.conf yet. On the one system I have that's running Gnome though I couldn't figure out how to set the resolution (it comes with what seems to be a preconfigured list of useless options) so there I did have to resort to writing an xorg.conf.
Note that at least one machine detected the resolution correctly on 2.6.32, but no kernels I've tried before or since.
I haven't tried any kernel versions that are particularly recent since the rate of regressions in Linux has conditioned me to upgrade only when it's completely unavoidable.
(And as for monitor *hotplugging* in KDE...that's a pretty guaranteed way to render this laptop non-responsive and require a power cycle)
Posted May 2, 2012 13:51 UTC (Wed) by nye (guest, #51576)
Actually now that I think about it, I believe it was 2.6.26 which worked. Before that was probably the era of massive breakage, and from there I skipped to 2.6.29 which was apparently when KMS was introduced for Intel, which seems a likely candidate for the breakage.
Posted May 2, 2012 16:09 UTC (Wed) by mathstuf (subscriber, #69389)
Posted May 10, 2012 13:15 UTC (Thu) by nye (guest, #51576)
The two I currently have access to are an Atom integrated system with an 'N10 Family Integrated Graphics Controller', and a more standard laptop with a 'Mobile GM965/GL960 Integrated Graphics Controller'.
Those don't really mean a great deal to me, to be honest. I just know that they're both very low-performance and seemingly not brilliantly supported.
Posted May 1, 2012 19:05 UTC (Tue) by mathstuf (subscriber, #69389)
Posted May 1, 2012 19:29 UTC (Tue) by dlang (✭ supporter ✭, #313)
It doesn't require you to use KDM, it's a problem in the KDE screen management after KDE starts.
Posted May 1, 2012 19:56 UTC (Tue) by mathstuf (subscriber, #69389)
Posted May 1, 2012 16:19 UTC (Tue) by juliank (subscriber, #45896)
On all 4 laptops that I own or administrate, none needs an xorg.conf; and all of them use intel graphics (and 3 different generations of intel graphics).
On boot, the kernel detects the correct screen resolution for the panels and automatically sets the correct mode. When plugging in a screen, the screen is detected, and the correct mode is set automatically.
Posted May 2, 2012 11:29 UTC (Wed) by nye (guest, #51576)
Okay, you're making me feel motivated to take the risk of trying a new kernel version - what version are you using to get that?
Posted May 2, 2012 13:00 UTC (Wed) by juliank (subscriber, #45896)
Posted May 2, 2012 13:53 UTC (Wed) by nye (guest, #51576)
So the same versions that get it wrong on all my machines then :(. Oh well.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds