惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
O
OpenAI News
Engineering at Meta
Engineering at Meta
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
月光博客
月光博客
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
GbyAI
GbyAI
T
The Blog of Author Tim Ferriss
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
云风的 BLOG
云风的 BLOG
罗磊的独立博客
S
SegmentFault 最新的问题
The Register - Security
The Register - Security
Hugging Face - Blog
Hugging Face - Blog
D
DataBreaches.Net
U
Unit 42
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
B
Blog
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
雷峰网
雷峰网
V
Visual Studio Blog
小众软件
小众软件
aimingoo的专栏
aimingoo的专栏
N
Netflix TechBlog - Medium
酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Y
Y Combinator Blog
博客园 - 【当耐特】
G
Google Developers Blog
L
LangChain Blog
Stack Overflow Blog
Stack Overflow Blog
I
InfoQ
Martin Fowler
Martin Fowler
F
Fortinet All Blogs
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog
AI
AI
Google Online Security Blog
Google Online Security Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
博客园 - Franky
Blog — PlanetScale
Blog — PlanetScale
Webroot Blog
Webroot Blog
PCI Perspectives
PCI Perspectives
爱范儿
爱范儿
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org

David Baron's Weblog

Software engineering, responsibility, and ownership Software engineering, responsibility, and ownership David Baron's weblog: Security and Inequality Running animations on the compositor thread David Baron's weblog: Tying ecosystems through browsers David Baron's weblog: Payments on the Web Thoughts on migrating to a secure Web David Baron's weblog: The need for government David Baron's weblog: Priority of constituencies How browser developers should seek feedback from Web developers A possible approach to shorter release cycles David Baron's weblog: Fifteen years Why debug builds (and assertions) are important Ten years of the Mozilla Foundation Open licensing at the W3C Why adding compositing and blending to CSS is harder than it looks How you can help with removing -moz- prefixes Moving bug history out of the primary display of a bug report Beware of locale-specific behavior in the C library Eating dogfood and shipping software Specification style and the future of the Web The bug system I wish I had CSS border-image changes and unprefixing Improving font size readability on Firefox for Android David Baron's weblog: CSS Animations, part 2 Hue-preserving color inversion with SVG filters Changes to handling of @-moz-keyframes David Baron's weblog: window.matchMedia() David Baron's weblog: CSS Animations What does a blur radius mean? Crash analysis in the future David Baron's weblog: calc() David Baron's weblog: colorDepth David Baron's weblog: Hidden complexity in specifications The most important field in a bug report: the summary WOFF font format submitted to W3C David Baron's weblog: :-moz-any() selector grouping setTimeout with a shorter delay Faster repainting in SVG foreignObject David Baron's weblog: Distributed Extensibility David Baron's weblog: Broadening crash analysis Correlating crashes with binary extensions or plugins David Baron's weblog: ex-HTML Downloadable font formats for the Web Web Accessibility as a Political Movement David Baron's weblog: CSS priorities David Baron's weblog: Bug priorities David Baron's weblog: Semi-vacation Some new CSS features in Firefox 3 David Baron's weblog: New selectors David Baron's weblog: The age of bugs Seeking a good Linux distribution David Baron's weblog: Teaching to the test David Baron's weblog: March 2008 David Baron's weblog: February 2008 David Baron's weblog: January 2008 David Baron's weblog: October 2007 David Baron's weblog: September 2007 David Baron's weblog: August 2007 David Baron's weblog: June 2007 David Baron's weblog: March 2007 David Baron's weblog: January 2007 David Baron's weblog: September 2006 David Baron's weblog: August 2006 David Baron's weblog: July 2006 David Baron's weblog: May 2006 David Baron's weblog: February 2006 David Baron's weblog: January 2006 David Baron's weblog: December 2005 David Baron's weblog: October 2005 David Baron's weblog: September 2005 David Baron's weblog: June 2005 David Baron's weblog: May 2005 David Baron's weblog: April 2005 David Baron's weblog: March 2005 David Baron's weblog: February 2005 David Baron's weblog: October 2004 David Baron's weblog: September 2004 David Baron's weblog: August 2004 David Baron's weblog: June 2004 David Baron's weblog: May 2004 David Baron's weblog: April 2004 David Baron's weblog: March 2004 David Baron's weblog: February 2004 David Baron's weblog: January 2004 David Baron's weblog: November 2003 David Baron's weblog: October 2003 David Baron's weblog: September 2003 David Baron's weblog: August 2003 David Baron's weblog: July 2003 David Baron's weblog: June 2003 David Baron's weblog: May 2003 David Baron's weblog: April 2003 David Baron's weblog: March 2003 David Baron's weblog: February 2003 David Baron's weblog: January 2003 David Baron's weblog: December 2002 David Baron's weblog: November 2002 David Baron's weblog: September 2002
David Baron's weblog: April 2007
David Baron · 2007-05-01 · via David Baron's Weblog

Video drivers (23:43 -0700)

For the past few Linux distro releases, I've found the most painful part of running Linux on the desktop to be video drivers. (It used to be wireless. But since NetworkManager made dealing with wireless mostly painless, except for the lack of any setup option for it in Fedora's installer, it's now video. Even counting the few regressions in the updates since FC6's release.)

My requirements are more than the median user's, but they're really not that complicated. I have an IBM T42 laptop with a 1400x1050 display. At work, I plug it into a dock that is connected to a 1920x1200 LCD monitor. I want to get the benefits of this monitor's high resolution when I'm at work.

With Fedora Core 4, I lived with what the open source drivers could offer. I prefer to stick to the open source drivers for a number of reasons. First, I'm more comfortable using software if I know people can read the source, even if I'm not the one doing the reading. Second, I've found using proprietary drivers tends to make my system less stable. This isn't surprising given what I've said about extensions and quality. And third, I'd like to improve the Linux desktop experience -- and that involves understanding it. If Linux on the desktop is ever to be taken seriously for the average user, the desktop Linux experience is what you're going to get when you install the distribution, without any hard-to-find and hard-to-install proprietary drivers.

This meant that I used my LCD monitor via the DVI port on my laptop's dock, but at 1400x1050 resolution.

But then, when I upgraded to Fedora Core 5, things got worse. My memory is that this was because they disabled part of the support for the driver because it crashed on some other variants of the card (although I can't find my source for that anymore). Worse in this case means that there was no longer any video output from my docking station. This pushed me to switch to the proprietary drivers from ATI.

Thanks to packaging done by Livna, this was actually reasonably painless (once I discovered Livna). I could power my DVI output again. I could even display at 1920x1200 (as long as the monitor was plugged in when I started X), and resize the display using xrandr when docking and undocking. I even had some extra hardware acceleration capabilities, although that stopped when I upgraded to Fedora Core 6, and I don't think they made a difference for anything I actually used (except for screensavers). I lost the ability to suspend-to-disk, but suspend-to-RAM still worked, and that was the main thing that mattered to me.

But after using Fedora Core 6 for a bit, I started (after some of the updates) running into problems on suspend/resume, where my computer would hang on resume. I reduced this to an upgrade in the proprietary ATI video drivers, which forced me into a cycle of avoiding ATI driver updates, which eventually forced me into avoiding kernel security updates, which wasn't a good idea.

But I found a solution for that problem. I now run the proprietary ATI drivers without the associated kernel module. The drivers work fine: I get all the functional benefits of the proprietary drivers without the stability or suspend/resume problems. Every time I get updated rpms from Livna, I just rpm -e --nodeps kmod-fglrx.

So I started thinking that the next time I get a laptop, I should make sure to get one with the Intel Graphics Card, since Intel is nice enough to develop their accelerated driver as an open-source driver. Unfortunately, Lenovo only sells that graphics card in laptops with a 1024x768 display; the 1400x1050 displays require the ATI card.

Last week I wrote a simple python script (works on my system only) to automate the stuff I do on dock / undock. However, it's managed to crash my X server twice; hopefully the sleep(1) will fix that by making things more like they used to be before it was automated.

But I'm somewhat pessimistic about whether this situation will improve, since most of the Linux developer types I run into seem to use the proprietary drivers. If nobody uses the free drivers, they'll never improve. Then again, who am I to talk? Maybe I should give them another try once F7 comes out.